Re: RPi Kernel Panic on Bookworm

开云体育

Hello Mike,

Again, thank you for the detailed email and I think this all helps in tracking down the real issue here.? I've been discussing this on the side with Bernard F6BVP who maintains FPAC (node) and FBB (BBS) and uses the ROSE protocol heavily.? He reported that he's "running three ROSE/FPAC nodes on a local network and I haven't observed any connections issues with Raspbian OS 64bit for a long time nor with Ubuntu (20.04)".? He showed months of uptime with LOTS of connections without either any panics or any orphaned AX.25 connections.? One key point he mentioned is that he does NOT have any RF connections, it's all via AXUDP and he also noted he's NOT using mkiss for linking the AXUDP to the kernel with kissattach.

--David

On 02/10/2024 12:27 PM, Michael Dunn wrote:

Show quoted text

? Hi everyone,

Been quiet on this topic recently as I haven't had much to report. ?I've had a lack of any crashes for over 12 days now, which seems to be related to disabling Pat in my environment. ?Please don't jump to conclusions here; this is a complex issue. ?As I've said in the past, Pat doesn't appear to be the cause of the crash, just the process that trips over the kernel garbage to trigger it.

Since I've had some time to think about this problem, here's what I've noticed:

? - Jon and I both run rmsgw. ?We both have crashes on the system running rmsgw.
? - The process that triggers the crash is mobile (beacon, pat, netstat), but is never rmsgw.
? - Jon and I both have few outside connections to rmsgw. ?My last outside connection was 10 days ago.
? - Jon has crashes in just a few hours; my crashes take days to weeks.
? - Jon frequently self checks his mail (possibly hourly? but I don't think he stated). ?I self check my mail infrequently (daily).

Based on these facts, my theory is this. ?rmsgw puts the kernel in some sort of bad state. ?This state is tripped over later by some unsuspecting process, causing the kernel crash.

To prove this out, I need to separate my rms server from my rms client. ?Unfortunately, I have only one radio, so I decided to take this test off-air. ?In my test setup, I built 2 Pi's, let's call them RMS and PAT to distinguish their roles. ?The Pis were built by imaging the SD card from PROD in the manner I've described previously.

Instead of connecting to a radio, I simply connected sound card to sound card using a pair of TRS cables (headphone to microphone in both directions). ?Direwolf was configured to match and PTT was disabled. ?RMS ran rmsgw from ax25d and a shell loop on PAT checked my mail every 30 minutes using pat -s (send only, as not to eat my actual inbox).

I let this setup run over night. ?In the morning, neither Pi had crashed, but I did notice that PAT was no longer able to connect to RMS. ?Tracking through the logs, it looks like about 7 hours after I setup the test, connections started failing. ?Digging into the RMS Pi, I found the netstat condition that Jon first reported. ?Note ax0 missing from the device column:

Dest ? ? ? Source ? ? Device ?State ? ? ? ?Vr/Vs ? ?Send-Q ?Recv-Q

* ? ? ? ? ?MYCALL-10 ? ? ? ? ?LISTENING ? ?000/000 ?0 ? ? ? 0

?
The kernel on RMS had been trashed, but the Pi was still operating. ?Checking the PAT Pi, netstat output looked normal. ?Realizing I still needed an AX25 event to trigger the crash, I used axcall on RMS ?to generate some traffic. ?The RMS Pi immediately crashed, blaming axcall as it went down:

[61160.353159] CPU: 1 PID: 130380 Comm: axcall Tainted: G ? ? ? WC ? ? ?6.1.0-rpi7-rpi-vB #1 Debian 1:6.1.63-1+rpt1

?
For me, this is great news. ?I have an off-air way to quickly show the problem. ?This also continues to show that the crash is mobile between processes and demonstrates an unrelated trigger event. ?Next steps are to reproduce the crash to ensure it is reliable. ?I'm also going to move RMS and PAT out of the RF environment (e.g. the other end of the house) to ensure there is no RFI element.

? Cheers
? Mike

Re: RPi Kernel Panic on Bookworm

#15623

I think using badly outdated software is the answer here.? I never thought I make that recommendation for stuff.

? No doubt, it definitely feels wrong. ?But, I think you have a different objective than I do, so it sounds like the best thing to do for your use case.

? Just a quick update, I did more testing and was able to crash the setup between RMS and PAT twice yesterday, so this is definitely repeatable. ?In a crash cycle, once I can demonstrate "kernel weirdness" with netstat output, it usually takes two ax.25 commands to crash the RMS Pi. ?In one instance I ran axcall twice, in another instance I ran beacon twice.

? I'm going to be away from the console of these test Pis for a few days, so it's a bit pointless to test a crash that only takes a few hours to happen. ?Instead, I'm going to remove rmsgw from ax25d and let the test cycle run while I'm away. ?PAT will try to connect to RMS, but fail; that's ok. ?If I don't see any "kernel weirdness" when I return, then it's safe to conclude that rmsgw is a required element of the crash.

? Cheers
? Mike

Re: RPi Kernel Panic on Bookworm

#15622

After moving my Pi3 down to Buster, kernel 4.19.50-v7+, running rmsgw has been extremely stable.? Beacon does its thing, the ax0 interface is stable in the netstat command, the ACI script doesn't complain about radios being up or down, and I took the Pi+Baofeng gateway to our monthly club meeting and turned our members loose on the device for testing.? Several of us finished making Nino TNC boards, so we had a lot of clients connecting.
The Pi+radio, connected to wifi of the meeting hall, held up like a champ.

I think using badly outdated software is the answer here.? I never thought I make that recommendation for stuff.

Re: RPi Kernel Panic on Bookworm

#15621

? Hi everyone,

Been quiet on this topic recently as I haven't had much to report. ?I've had a lack of any crashes for over 12 days now, which seems to be related to disabling Pat in my environment. ?Please don't jump to conclusions here; this is a complex issue. ?As I've said in the past, Pat doesn't appear to be the cause of the crash, just the process that trips over the kernel garbage to trigger it.

Since I've had some time to think about this problem, here's what I've noticed:

? - Jon and I both run rmsgw. ?We both have crashes on the system running rmsgw.
? - The process that triggers the crash is mobile (beacon, pat, netstat), but is never rmsgw.
? - Jon and I both have few outside connections to rmsgw. ?My last outside connection was 10 days ago.
? - Jon has crashes in just a few hours; my crashes take days to weeks.
? - Jon frequently self checks his mail (possibly hourly? but I don't think he stated). ?I self check my mail infrequently (daily).

Based on these facts, my theory is this. ?rmsgw puts the kernel in some sort of bad state. ?This state is tripped over later by some unsuspecting process, causing the kernel crash.

To prove this out, I need to separate my rms server from my rms client. ?Unfortunately, I have only one radio, so I decided to take this test off-air. ?In my test setup, I built 2 Pi's, let's call them RMS and PAT to distinguish their roles. ?The Pis were built by imaging the SD card from PROD in the manner I've described previously.

Instead of connecting to a radio, I simply connected sound card to sound card using a pair of TRS cables (headphone to microphone in both directions). ?Direwolf was configured to match and PTT was disabled. ?RMS ran rmsgw from ax25d and a shell loop on PAT checked my mail every 30 minutes using pat -s (send only, as not to eat my actual inbox).

I let this setup run over night. ?In the morning, neither Pi had crashed, but I did notice that PAT was no longer able to connect to RMS. ?Tracking through the logs, it looks like about 7 hours after I setup the test, connections started failing. ?Digging into the RMS Pi, I found the netstat condition that Jon first reported. ?Note ax0 missing from the device column:

Dest ? ? ? Source ? ? Device ?State ? ? ? ?Vr/Vs ? ?Send-Q ?Recv-Q

* ? ? ? ? ?MYCALL-10 ? ? ? ? ?LISTENING ? ?000/000 ?0 ? ? ? 0

?

The kernel on RMS had been trashed, but the Pi was still operating. ?Checking the PAT Pi, netstat output looked normal. ?Realizing I still needed an AX25 event to trigger the crash, I used axcall on RMS ?to generate some traffic. ?The RMS Pi immediately crashed, blaming axcall as it went down:

[61160.353159] CPU: 1 PID: 130380 Comm: axcall Tainted: G ? ? ? WC ? ? ?6.1.0-rpi7-rpi-vB #1 Debian 1:6.1.63-1+rpt1

?

For me, this is great news. ?I have an off-air way to quickly show the problem. ?This also continues to show that the crash is mobile between processes and demonstrates an unrelated trigger event. ?Next steps are to reproduce the crash to ensure it is reliable. ?I'm also going to move RMS and PAT out of the RF environment (e.g. the other end of the house) to ensure there is no RFI element.

? Cheers
? Mike

Re: VarAC and ARDOP on Pi 5 + WINE?

#15620

Disable Linux mode in the VarAC.ini file. It seems to have issue’s finding the emoji font, I let Irad know the issue.?

VarAC and ARDOP on Pi 5 + WINE?

#15619

开云体育

Good morning all.

I’ve been continuing with my testing on my Pi 5. Winlink + VARA HF or FM are working pretty well. Stability isn’t as rock solid as I'd like, but I can always fire up Winlink Express and send/receive emails reliably. (If I leave it running for hours, as I need to for Winlink Wednesday, the Winlink Express process croaks at some point, every single time.)

Two things I have not had ANY success with, though. ARDOP TNC and VarAC.

For the life of me, I can’t get the ARDOP TNC to initialize. I’ve compared the configuration settings side by side with my windows (ptui!) system, where it runs just fine. The ARDOP and TNC windows open just fine, but the TNC fails to initialize on 127.0.0.1. When I configure the TNC window manually do launch on 127.0.0.1:8200, that configuration fails to persist. Next launch, it’s gone again.

And then there’s VarAC. I installed it using the installer. I installed the fonts recommended on the VarAC web site. I enabled Linux mode in the VarAC.ini file.

It launched and seemed to run once for me, and since then, every time I launch it, the VARA HF window opens, then the VarAC window opens, but the fields are black and the window is unresponsive.

Has anyone else run into similar issues? Were you able to resolve them? Suggestions?

Cheers,

Ken van Wyk

Armata Scientia

signature.asc

Re: Intro - newbie

#15618

开云体育

Thanks David.

Never a sysadmin so for me an interesting look at history.? For those who don't want the history, skip to about the last ten minutes when Wayland is explained.

Ray vk2tv

On 9/2/24 07:46, David Ranch wrote:

Show quoted text

To add on to Ray's response, I recently saw this excellent video on Youtube about Xwindows history and it's dead-end future:

??

There is some fascinating details in there and I bet there are some tidbits that even the the most senior "grey beard" sysadmins might not know.? Good stuff.

--David
KI6ZHD

On 02/07/2024 04:37 PM, Ray Wells wrote:

Maybe some useful info here ....

Ray vk2tv

On 8/2/24 10:52, N5XMT wrote:

Unfortunately, bookworm isn't returning to anything. X is being replaced by all distros with Wayland as the display manager. Not sure why, because X worked just fine.

Get

On Feb 7, 2024, at 09:03, mike <pencoys@...> wrote:
Hi, G8NXD here, been running RPi since the first board release and have a box full of old RPi's sitting waiting for Godot.
Been using RPi for local and remote QRSS and? WSPR reporting for ages., also GP desktop applications.
I've just aquired a couple of RPi5 8Gb but hate the OS for it so staying on Bullseye and RPi4 until Bookworm returns to sanity.

I've just joined looking for help on why certain distros, Ubuntu and DV as examples, dont recognise my Monitor but Raspbian of all colours seem quite happy with it.
It does'nt appear to be video drive level, #hdmi_drive=2 and dmi_force_hotplug=1, may be depreciated in modern Config.txt configurations, it does'nt seem to work these days.
The monitor is an ASUS VE247.
I have a feeling that the problematic distros assume a 4k monitor when first booting, but not sure about that and have no idea how to reject that option and default to a more antique resolution.

Ideas on a ?5 note please :-) 73 Mike

Re: Intro - newbie

#15617

开云体育

To add on to Ray's response, I recently saw this excellent video on Youtube about Xwindows history and it's dead-end future:

??

There is some fascinating details in there and I bet there are some tidbits that even the the most senior "grey beard" sysadmins might not know.? Good stuff.

--David
KI6ZHD

On 02/07/2024 04:37 PM, Ray Wells wrote:

Show quoted text

Maybe some useful info here ....

Ray vk2tv

On 8/2/24 10:52, N5XMT wrote:

Unfortunately, bookworm isn't returning to anything. X is being replaced by all distros with Wayland as the display manager. Not sure why, because X worked just fine.

Get

On Feb 7, 2024, at 09:03, mike <pencoys@...> wrote:
Hi, G8NXD here, been running RPi since the first board release and have a box full of old RPi's sitting waiting for Godot.
Been using RPi for local and remote QRSS and? WSPR reporting for ages., also GP desktop applications.
I've just aquired a couple of RPi5 8Gb but hate the OS for it so staying on Bullseye and RPi4 until Bookworm returns to sanity.

I've just joined looking for help on why certain distros, Ubuntu and DV as examples, dont recognise my Monitor but Raspbian of all colours seem quite happy with it.
It does'nt appear to be video drive level, #hdmi_drive=2 and dmi_force_hotplug=1, may be depreciated in modern Config.txt configurations, it does'nt seem to work these days.
The monitor is an ASUS VE247.
I have a feeling that the problematic distros assume a 4k monitor when first booting, but not sure about that and have no idea how to reject that option and default to a more antique resolution.

Ideas on a ?5 note please :-) 73 Mike

Re: Intro - newbie

#15616

On Wednesday, February 7th, 2024 at 15:52, N5XMT <dacooley@...> wrote:

Unfortunately, bookworm isn't returning to anything. X is being replaced by all distros with Wayland as the display manager. Not sure why, because X worked just fine.

X works just fine, but nobody's actually working on it anymore.? The codebase is

so old that the best anybody's been able to do is the odd patch to ensure it still

compiles against modern environments.? Wayland is supposed to be the next

generation environment, with an architecture that's more modern and easier to

work on.

The Doctor [412/724/301/703/415/510]

WWW: https://drwho.virtadpt.net/

Don't be mean. You don't have to be mean.

Re: Seeking case compatible with Pi 5 + Pimoroni NVMe BASE

#15615

开云体育

Got my PiMoroni Pi bottom NVME hat.

The 3D printed case I found for the pineberry pi bottom hat also works with the pimoroni NVME bottom hat and Pi5 active cooler

Get

On Feb 5, 2024, at 05:13, "Kenneth R. van Wyk" <ken@...> wrote:

Show quoted text

Hmmm, I might have answered my own question. After looking at a few of the online Pi shops without success, I searched broader and found a couple of 3D cases that should work.

This one looks excellent:?

Cheers,

Ken van Wyk
Armata Scientia

On Feb 5, 2024, at 7:26?AM, Kenneth R. van Wyk <ken@...> wrote:

I plan on adding my Pi 5 to my portable rig. It’s currently caseless, however, as the Pimoroni NVM3 base board doesn’t seem happy in other cases.

Anyone know of a case that can accommodate this configuration, while still allowing access to the external ports?

Re: Pineberry Pi SSD HATs

#15614

This case also works perfectly with the pimoroni NVME bottom hat as well, and also with the Pi5 active cooler

Get

On Jan 27, 2024, at 13:57, David Cooley <dacooley@...> wrote:

Show quoted text

here's the link to the model for the pi5 with pineberry bottom drive HAT case

On Sat, Jan 27, 2024 at 1:44?PM Jerry Rector - K4OAM <kb4oam@...> wrote:

Would you be able to share a link to that .stl file?

On Sat, Jan 27, 2024 at 6:41?PM N5XMT <dacooley@...> wrote:

There isn't anything commercially available, but I found the STL (3D model) of one and 3D printed it myself.? Works perfectly!

Get

On Jan 27, 2024, at 08:07, John <radio@...> wrote:

Hi Ed,

I have the BOT Pineberry card I received in late December, but I'm still awaiting the 8gb Pi-5 kit I ordered in September from SparkFun.

Have you found a case yet that works with the Pi-5 and BOT together?? I would like one that encloses the sides and bottom of the BOT with openings for cooling.

Have you seen such a case yet?

Best regards,

John,? WoGN

On 2023-12-27 14:32, Edward Seeliger wrote:

[Edited Message Follows]
Thanks David.
After I posted my question I searched again and found a review of the Pineberry Pi boards posted yesterday on Toms Hardware by Les Pounder that shows a picture of the Bottom Board connected to the RPI5. Yes, the mount for the SSD requires removal from the RPI5 board. Another problem is the SD card slot is hidden by the PCIe connecting cable between the RPI5 and the Bottom Hat. To change / remove the SSD card you must also remove the Bottom Hat from the RPI5.
I am looking for a case to mount the RPI5 / Bottom Board in to protect the SSD - I have two on order from Amazon arriving tomorrow to try. - They are both simple top / bottom plexiglass with standoffs.
Thanks again.
Happy New Year.
Edd - KD5M

Re: Intro - newbie

#15613

开云体育

Maybe some useful info here ....

Ray vk2tv

On 8/2/24 10:52, N5XMT wrote:

Show quoted text

Unfortunately, bookworm isn't returning to anything. X is being replaced by all distros with Wayland as the display manager. Not sure why, because X worked just fine.

Get

On Feb 7, 2024, at 09:03, mike <pencoys@...> wrote:
Hi, G8NXD here, been running RPi since the first board release and have a box full of old RPi's sitting waiting for Godot.
Been using RPi for local and remote QRSS and? WSPR reporting for ages., also GP desktop applications.
I've just aquired a couple of RPi5 8Gb but hate the OS for it so staying on Bullseye and RPi4 until Bookworm returns to sanity.

I've just joined looking for help on why certain distros, Ubuntu and DV as examples, dont recognise my Monitor but Raspbian of all colours seem quite happy with it.
It does'nt appear to be video drive level, #hdmi_drive=2 and dmi_force_hotplug=1, may be depreciated in modern Config.txt configurations, it does'nt seem to work these days.
The monitor is an ASUS VE247.
I have a feeling that the problematic distros assume a 4k monitor when first booting, but not sure about that and have no idea how to reject that option and default to a more antique resolution.

Ideas on a ?5 note please :-) 73 Mike

Re: Intro - newbie

#15612

Unfortunately, bookworm isn't returning to anything. X is being replaced by all distros with Wayland as the display manager. Not sure why, because X worked just fine.

Get

On Feb 7, 2024, at 09:03, mike <pencoys@...> wrote:

Show quoted text

Hi, G8NXD here, been running RPi since the first board release and have a box full of old RPi's sitting waiting for Godot.
Been using RPi for local and remote QRSS and? WSPR reporting for ages., also GP desktop applications.
I've just aquired a couple of RPi5 8Gb but hate the OS for it so staying on Bullseye and RPi4 until Bookworm returns to sanity.

I've just joined looking for help on why certain distros, Ubuntu and DV as examples, dont recognise my Monitor but Raspbian of all colours seem quite happy with it.
It does'nt appear to be video drive level, #hdmi_drive=2 and dmi_force_hotplug=1, may be depreciated in modern Config.txt configurations, it does'nt seem to work these days.
The monitor is an ASUS VE247.
I have a feeling that the problematic distros assume a 4k monitor when first booting, but not sure about that and have no idea how to reject that option and default to a more antique resolution.

Ideas on a ?5 note please :-) 73 Mike

Re: Seeking case compatible with Pi 5 + Pimoroni NVMe BASE

#15611

I got the Geekworm Rpi 5 case. They have the Active Cooler and NVMe hat for a SSD. All fit and work good together. They also have the 5A power supplies.?

Greg
KE5DXA?

Re: RPi Kernel Panic on Bookworm

#15610

If you read the linux-ham@... archives (
 ), you can see how
various patches have been submitted and accepted in w/o any testing or
validation.  These patches have been "fixing" potential race conditions
found by automated tools, security issues, and also changing out various
legacy kernel data structures for new ones.  What that has created is a
moving target where we cannot just backout the changes as the AX.25 and
surrounding kernel code has moved forward and is now incompatible.  <sigh>

--David
KI6ZHD
I figured that would be the case if it were indeed not possible.  Thank
you for the clarification.

-73 de Chris KQ6UP

Re: RPi Kernel Panic on Bookworm

#15609

开云体育

Hey Chris,

Well if the cause is/was bad patches, I am wondering if a frankenstein

kernel would work with the old AX.25 code "grafted in" to the new
kernel.  I am wondering what kind of mess that would make.  Not a kernel
programmer, so I am not sure what all would be involved.  I think
compiling an old slackware distro for a R-Pi 3 would be interesting too.

If you read the linux-ham@... archives ( ), you can see how various patches have been submitted and accepted in w/o any testing or validation.? These patches have been "fixing" potential race conditions found by automated tools, security issues, and also changing out various legacy kernel data structures for new ones.? What that has created is a moving target where we cannot just backout the changes as the AX.25 and surrounding kernel code has moved forward and is now incompatible.? <sigh>

--David
KI6ZHD

Re: RPi Kernel Panic on Bookworm

#15608

On Wed, Feb 07, 2024 at 08:33:04AM -0800, David Ranch wrote:

Hey Jon,

I saw both of your emails and I think this great work and your observation
of the missing AX.25 device like "ax0" from the output of "netstat -A ax25
-an" is an interesting one.  I'll look for that as well.

Beyond that, if you're looking for a solid AX.25 stack for your Raspberry Pi
1 or Raspberry Pi 2 hardware, I'd have to recommend using a VERY old release
like Jessie with the 4.14 kernel.  Making that recommendation really pains
me as it's EOL, known insecure, etc. but bad patches started getting
integrated into the Linux kernel around the 4.17 time frame.

You can see some of this hardware compatibility vs. OS version detail
captured here:

   

--David
KI6ZHD




Well if the cause is/was bad patches, I am wondering if a frankenstein
kernel would work with the old AX.25 code "grafted in" to the new
kernel.  I am wondering what kind of mess that would make.  Not a kernel
programmer, so I am not sure what all would be involved.  I think
compiling an old slackware distro for a R-Pi 3 would be interesting too.

73 de Chris KQ6UP

Intro - newbie

#15607

Hi, G8NXD here, been running RPi since the first board release and have a box full of old RPi's sitting waiting for Godot.
Been using RPi for local and remote QRSS and? WSPR reporting for ages., also GP desktop applications.
I've just aquired a couple of RPi5 8Gb but hate the OS for it so staying on Bullseye and RPi4 until Bookworm returns to sanity.

I've just joined looking for help on why certain distros, Ubuntu and DV as examples, dont recognise my Monitor but Raspbian of all colours seem quite happy with it.
It does'nt appear to be video drive level, #hdmi_drive=2 and dmi_force_hotplug=1, may be depreciated in modern Config.txt configurations, it does'nt seem to work these days.
The monitor is an ASUS VE247.
I have a feeling that the problematic distros assume a 4k monitor when first booting, but not sure about that and have no idea how to reject that option and default to a more antique resolution.

Ideas on a ?5 note please :-) 73 Mike

Re: RPi Kernel Panic on Bookworm

#15606

开云体育

Hey Jon,

I saw both of your emails and I think this great work and your observation of the missing AX.25 device like "ax0" from the output of "netstat -A ax25 -an" is an interesting one.? I'll look for that as well.?

Beyond that, if you're looking for a solid AX.25 stack for your Raspberry Pi 1 or Raspberry Pi 2 hardware, I'd have to recommend using a VERY old release like Jessie with the 4.14 kernel.? Making that recommendation really pains me as it's EOL, known insecure, etc. but bad patches started getting integrated into the Linux kernel around the 4.17 time frame.

You can see some of this hardware compatibility vs. OS version detail captured here:

??

--David
KI6ZHD

On 01/31/2024 09:43 PM, Jon Bousselot KK6VLO wrote:

Show quoted text

Mike and David,? all great input and I didn't consider 32/64 for application stability.? I chose 32 because if anyone in our club has a Pi-1 or Pi-2, they will be choosing the 32 bit release and rmsgw is such a light weight app and compiles from source...? I started with the most compatible release.???
The Pi-1 is a pilot project for our club, and the gateway and client radios are all within my house.? I've told others to finish soldering their TNC kit and connect, but so far I'm the only one.? I will attempt to monitor the number of ax25 packets that travel through the host.? I am usually checking winmail twice a day, and don't always have a lot of mail to get/send.? The quantity of packets on that interface are probably small, even for 1200 baud.

The Pi-1 crashed on its own today without the beacon app, after 1d 3h 47m uptime.? Here is what it cried out when going down.
[100075.375841] CPU: 0 PID: 3001 Comm: netstat Tainted: G???????? C???????? 6.1.0-rpi7-rpi-v6 #1? Raspbian 1:6.1.63-1+rpt1

Netstat, while not part of the ax25 tools, does query the ax25 interface statistics.? You might be onto something with the ax25 packet count theory.? I wasn't home when it crashed so I did not run netstat.
The rmsgw_aci is set to run on cron and it does call the netstat command several times, one specifically for the ax25 protocol.??? See for yourself.??? The -o is the output log file.
strace -ormsgw_aci.strace-log -fvtTq -s1024 /usr/local/bin/rmsgw_aci

I'm going to downgrade the Pi-1 to Bullseye, patch it thoroughly, and drop this config on it again and include beacon running every 35 minutes.?

I'll re-image my Pi-3 and load a 64bit Bookworm release and get it queued up for a second round of tests.? The two Pi's will swap roles for monitoring the serial console to catch the panic strings when the other goes crazy

We're collecting quite a few variables to test here.? This could take a while if crashes only happen every few days.
32 or 64 bit?
Bullseye or Bookworm?
How many ax25 packets until the system becomes unstable?
Beacon or no-beacon?

Re: RPi Kernel Panic on Bookworm

#15605

On 2/6/2024 9:28 AM, David Ranch wrote:

?? Bookworm / Debian 12 based:? kernel: 6.1.73
?? Bullseye / Debian 11 based:? kernel: 6.1.21
?? Stretch? / Debian 9 based:?? kernel: 4.19.66
?? Jessie?? / Debian 8 based:?? kernel: 4.14.71
?? Wheezy?? / Debian 7 based:?? kernel: 3.18.0

Per Brian N1URO (sk), he thought the last rock solid version of AX.25 was Wheezy but I had found Jessie to have a reliable AX.25 stack.? I have been trying to solicit help from various people to see if we can get some known Ax.25 fixes applied to both the upstream Linus tree kernel as well as the Raspberry Pi's versions of their kernels but so far, no bites.? I you know of anyone in the inner-circles of Linux kernel development that you think can help, please let me (or them) know we need some help!

--David
KI6ZHD

I managed to get a patch back ported by issuing a bug report. The whole thread is in the build-a-pi email group.? People were having issues with the socket not releasing using PAT, so I told them how to patch and recompile the kernel for a Pi.? For giggles I decided to report the lack of a patch that fixes the socket release problem as a bug, and it got put in for version 5.15.* at some point.? I forget the exact version, but it the thread should still be there if you are interested in the details.

-Chris KQ6UP