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

Thanks, and good info to know.? The first release of Slack for ARM started at the 3.x kernel, so I don't think there is a realistic path to getting a 2.6 on bare metal Pi hardware.
My Pi-3 running the 2019 image of Buster kernel 4.19.50-v7+ is still running.? Plenty of ax25 packets through it, and no weird system messages.? So far, this looks good.

All the repos for ancient distros I work with are still out there.? The URL has changed, but the content is there.

I think I need to deploy this RMS Gateway on the 4.x kernel and patiently wait for the ax25 code to catch up, or someone writes it in userspace.? I just learned about JNOS2 which sounds like userspace ax25.? More research needed.

开云体育

When I pick this up again, I'm looking at the 2022-04-04 release of Bullseye, which should have the 5.15.xx kernel.? Buster has a release of 4.19 kernel I'll test also.
Describe "works okay" for your environment.? Where does it fall apart and what are you using?
I used to run 64 bit only Slackware 13.

That is funny you mention that. I have settled on Slackware 13.37 as my AX.25 distro. I also have a R-Pi 3 that I could play with old distros. What R-Pi version would be the

equivalent of Slack 13.37? And how would you do repositories since I am sure they are all dried up by now. That is one of the cool things about Slackware is that no matter

what the distro, you can always get at least the latest updates before EOL. And almost all the software is available for what you need on the DVD when you do a full install.

I had thoughts of trying to compile 13.37 for a Raspberry Pi, but I am thinking that would be a ton of work to even get a bootable system. I know there are projects to run

RISK processor versions of Slackware on other flavors of that platform like the Orange (or Banana) hardware. But those are newer releases of Slackware. I think the earliest

is 14.2, and it is now EOL. 14.2 is not too bad. I always had issues with it when I was shutting down the system. It would be fine running, but always kernel panic on system

shutdown. David Ranch had a fix with bringing the AX.25 stuff down before system shutdown, but think I was just happy with running 13.37 and not having to mess with it.

- VY 73 es GL de Chris KQ6UP SK ..

开云体育

?? 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

Absolutely! That's called out in the release notes for the images available on rapsberrypi.org site.?
Pi-2 added January 2015, Pi-3B+ added in March 2018,? Pi-4 added in June 2019,? Pi-5 added in October 2023.

开云体育

Hello Jon,

Beware of the major caveat that you must use older Raspberry Pi hardware that's compatible with those older OS versions (bootloader / firmware support).? Using a Raspberry Pi 3 should be ok for very old releases.

--David
KI6ZHD
?

Be sure to use all the CPU cores... like I did.

FYI... it takes 2851 minutes to compile the linux kernel on a Raspberry Pi-1.
47.5 hours.

2019-06-20-raspbian-buster-lite.img, Pi-3, did not "apt update;apt upgrade", the system is 32bit, will investigate what kernel versions live in the repos later.

Linux Pi3-2019 4.19.50-v7+ #896 SMP Thu Jun 20 16:11:44 BST 2019 armv7l GNU/Linux

Needed this to allow "oldoldstable" repositories.
apt-get update --allow-releaseinfo-change

The dependency packages to compile rmsgw install cleanly, and the app builds without any issues.
the rmsgw_aci python script runs and updates just fine.? Send/Get over VHF works.? The timer is started.

When I pick this up again, I'm looking at the 2022-04-04 release of Bullseye, which should have the 5.15.xx kernel.? Buster has a release of 4.19 kernel I'll test also.
Describe "works okay" for your environment.? Where does it fall apart and what are you using?
I used to run 64 bit only Slackware 13.?

开云体育

I know I am jumping in late here, but the AX.25 stuff mostly works on kernel version 4.19, and does ok on 5.15 with some patches.? Version 6 just seems to explode.? I am running my linux/AX.25 on an old version of Slackware (13.37) that runs kernel version 2.6, and it is running perfectly for all the stuff I am using.? It is kind of sad that this has been neglected for that long.

-Chris KQ6UP

Used the rpi-update to get onto 6.1.y kernel branch, which is 6.1.74-v8+.
The system was up for about 2h 24m.? I connected to the gateway twice and exchanged mail.

First I got a kernel message about rmsgw, shortly after I connected and sent mail.
Feb 03 19:14:00 rpi3-dev rmsgw[1191]: sendrf(): [; KK6VLO de WA6BGS-10 SK
Feb 03 19:14:00 rpi3-dev rmsgw[1191]: sendrf(): wrote 25 of 25 characters
Feb 03 19:14:00 rpi3-dev rmsgw[1191]: Logout KK6VLO??? tx:63 rx:9902 173.0s 57.6 Bytes/s (0)
Feb 03 19:14:00 rpi3-dev rmsgw[1191]: CMS Disconnected
Feb 03 19:14:00 rpi3-dev kernel: ------------[ cut here ]------------
Feb 03 19:14:00 rpi3-dev kernel: refcount_t: underflow; use-after-free.
Feb 03 19:14:00 rpi3-dev kernel: WARNING: CPU: 2 PID: 1191 at lib/refcount.c:28 refcount_warn_saturate+0xf8/0x148
Feb 03 19:14:00 rpi3-dev kernel: Modules linked in: mkiss ax25 cmac algif_hash aes_arm64 aes_generic algif_skcipher af_alg bnep vc4 brcmfmac snd_soc_hdmi_codec drm_display_helper cec drm_dma_helper drm_kms_helper brcmutil binfmt_misc snd_soc_core hci_uart btbcm bluetooth cfg80211 snd_compress snd_pcm_dmaengine fb_sys_fops syscopyarea cdc_acm sysfillrect raspberrypi_hwmon sysimgblt bcm2835_codec(C) bcm2835_isp(C) bcm2835_v4l2(C) v4l2_mem2mem bcm2835_mmal_vchiq(C) videobuf2_dma_contig videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_common snd_bcm2835(C) videodev i2c_bcm2835 snd_pcm ecdh_generic ecc rfkill libaes snd_timer mc snd vc_sm_cma(C) raspberrypi_gpiomem uio_pdrv_genirq uio fuse drm dm_mod drm_panel_orientation_quirks backlight ip_tables x_tables ipv6
Feb 03 19:14:00 rpi3-dev kernel: CPU: 2 PID: 1191 Comm: rmsgw Tainted: G???????? C???????? 6.1.74-v8+ #1725
Feb 03 19:14:00 rpi3-dev kernel: Hardware name: Raspberry Pi 3 Model B Rev 1.2 (DT)
Feb 03 19:14:00 rpi3-dev kernel: pstate: 40000005 (nZcv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--)
Feb 03 19:14:00 rpi3-dev kernel: pc : refcount_warn_saturate+0xf8/0x148
Feb 03 19:14:00 rpi3-dev kernel: lr : refcount_warn_saturate+0xf8/0x148



Then it crashed a few minutes later on beacon...
Feb 03 19:20:01 rpi3-dev kernel: ------------[ cut here ]------------
Feb 03 19:20:01 rpi3-dev kernel: refcount_t: saturated; leaking memory.
Feb 03 19:20:01 rpi3-dev kernel: WARNING: CPU: 3 PID: 873 at lib/refcount.c:22 refcount_warn_saturate+0x78/0x148
Feb 03 19:20:01 rpi3-dev kernel: Modules linked in: mkiss ax25 cmac algif_hash aes_arm64 aes_generic algif_skcipher af_alg bnep vc4 brcmfmac snd_soc_hdmi_codec drm_display_helper cec drm_dma_helper drm_kms_helper brcmutil binfmt_misc snd_soc_core hci_uart btbcm bluetooth cfg80211 snd_compress snd_pcm_dmaengine fb_sys_fops syscopyarea cdc_acm sysfillrect raspberrypi_hwmon sysimgblt bcm2835_codec(C) bcm2835_isp(C) bcm2835_v4l2(C) v4l2_mem2mem bcm2835_mmal_vchiq(C) videobuf2_dma_contig videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_common snd_bcm2835(C) videodev i2c_bcm2835 snd_pcm ecdh_generic ecc rfkill libaes snd_timer mc snd vc_sm_cma(C) raspberrypi_gpiomem uio_pdrv_genirq uio fuse drm dm_mod drm_panel_orientation_quirks backlight ip_tables x_tables ipv6
Feb 03 19:20:01 rpi3-dev kernel: CPU: 3 PID: 873 Comm: beacon Tainted: G??????? WC???????? 6.1.74-v8+ #1725
Feb 03 19:20:01 rpi3-dev kernel: Hardware name: Raspberry Pi 3 Model B Rev 1.2 (DT)
Feb 03 19:20:01 rpi3-dev kernel: pstate: 40000005 (nZcv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--)
Feb 03 19:20:01 rpi3-dev kernel: pc : refcount_warn_saturate+0x78/0x148
Feb 03 19:20:01 rpi3-dev kernel: lr : refcount_warn_saturate+0x78/0x148


And strangely it still had enough to run one more cron entry.
Feb 03 19:42:01 rpi3-dev CRON[1246]: pam_unix(cron:session): session opened for user rmsgw(uid=999) by (uid=0)
Feb 03 19:42:01 rpi3-dev CRON[1247]: (rmsgw) CMD (/usr/local/bin/rmsgw_aci > /dev/null 2>&1)
Feb 03 19:42:01 rpi3-dev rmsgw_aci[1248]: WA6BGS-10 - Linux RMS Gateway ACI 2.5.1 Feb? 3 2024 (DM12ms)
Feb 03 19:42:01 rpi3-dev rmsgw_aci[1248]: shm_init(): shmkey = 159412 (0x26eb4)
Feb 03 19:42:01 rpi3-dev rmsgw_aci[1248]: shm_init(): shmid = 0 (0x0)
Feb 03 19:42:01 rpi3-dev rmsgw_aci[1248]: Channel update interval = 7140
Feb 03 19:42:01 rpi3-dev rmsgw_aci[1248]: Using channel file '/etc/rmsgw/channels.xml
Feb 03 19:42:01 rpi3-dev rmsgw_aci[1248]: Channel file '/etc/rmsgw/channels.xml' age? 8109
Feb 03 19:42:01 rpi3-dev rmsgw_aci[1248]: Channel: WA6BGS-10 on radio (145070000 Hz, mode 0)
Feb 03 19:42:01 rpi3-dev rmsgw_aci[1248]: /usr/local/bin/rmschanstat ax25 radio WA6BGS-10 reports unavailable
Feb 03 19:42:01 rpi3-dev rmsgw_aci[1248]: Channel: WA6BGS-10 on radio is DOWN -- not updated
Feb 03 19:42:01 rpi3-dev rmsgw_aci[1248]: Channel Stats: 1 read, 1 active, 1 down, 0 updated, 0 errors
Feb 03 19:42:01 rpi3-dev rmsgw_aci[1248]: Version update interval = 86400
Feb 03 19:42:01 rpi3-dev rmsgw_aci[1248]: Version file '/usr/local/etc/rmsgw/stat/.version.WA6BGS-10' age 7578
Feb 03 19:42:01 rpi3-dev CRON[1246]: pam_unix(cron:session): session closed for user rmsgw


On the serial console, this appears.
[ 8670.831800] Call trace:
[ 8670.834290]? ax25cmp+0x14/0x60 [ax25]
[ 8670.838066]? ax25_bind+0x244/0x278 [ax25]
[ 8670.842194]? __sys_bind+0xe0/0x118
[ 8670.845668]? __arm64_sys_bind+0x28/0x38
[ 8670.849581]? invoke_syscall+0x4c/0x110
[ 8670.853409]? el0_svc_common.constprop.3+0x9c/0x100
[ 8670.858295]? do_el0_svc+0x34/0xd0
[ 8670.861679]? el0_svc+0x2c/0x78
[ 8670.864796]? el0t_64_sync_handler+0x98/0xc0
[ 8670.869059]? el0t_64_sync+0x18c/0x190
[ 8670.872800] Code: d503201f d2800002 d503233f 38626803 (38626824)
[ 8670.879001] ---[ end trace 0000000000000000 ]---


It's getting worse.
Time to find a release of Raspbian that will run 5.15, and while I work on that...? I'm going to load an x86_64 system and see if its any better.

I think I see now.? It makes a backup of /boot/firmware and installs the updated kernel*.img files
I'm used to seeing multiple kernels available in the GRUB menu, the RPi doesn't do this.

I did not know this existed.? Tons of warnings, upgrade first, read release notes later.? Thanks for the info!

I did this on Pi-3 and it took way less time than custom compile.? Now I have this version.
Linux rpi3-dev 6.1.74-v8+ #1725 SMP PREEMPT Mon Jan 22 13:35:32 GMT 2024 aarch64 GNU/Linux
Will load up rmsgw and see if we get more than 17 hours uptime.

And I'm a bit puzzled as to what that program did.? The boot commandline doesn't match the kernel.

??

The stable branch looks like 5.10.103, which predates the patch. ?If you are compiling from --branch=stable, I'd be careful here.

? Cheers
? Mike

? This link is into the stable branch; I'll agree that one looks unpatched. ?But if you are compiling the stable branch, you may not end up on 6.1.
You should look at what Git actually downloaded. ?When I get clone the default or with --branch rpi-6.1.y, I received patched versions.

? Cheers
? Mike

downloaded whatever version this brings? (which looks like it is rpi-6.1.y)
git clone --depth=1
It does have the ax25 patch.?

Downloaded this
git clone --depth=1 --branch=stable
And it does NOT have the patches.
Based on the links given in the KM4ACK-PI group, this seems like a reasonable path to gain stability. ?
I'm looking for a reliable answer on where raspbian gets their kernel source and what branch it is.?

If this fails, I'll be getting the 5.15 kernel