Ahh, well, there's been work done since kernel 5.15, I think it was kernel 6.2 I was trying, and that was for a different reason than crashing..
The bug description sounds more like a disconnect bug David was describing a few weeks ago. ?This doesn't look related to our kernel panic. ?Still I was curious ...
I used?
apt-get source linux-image-$(uname -r) to pull the source for my kernel, which resulted in a linux-6.1.69 source tree. ?Down under net/ax25, I manually verified that 3 of the patches had been applied and a 4th applied at include/net/ax25.h . ?Seems like this has been patched in the source version for my system.
The only thing I couldn't figure out is why apt loads 6.1.69 source, when dmesg shows the running kernel is 6.1.63 . ?I guess the distro maintainers have moved on from .63, but I haven't updated yet. ?I'm a bit reluctant to update since the bug is currently reproducible. ?Instead, I pulled the 6.1.63 source from kernel.org and directly verified the ax.25 patch, so I know these fixes are in my running kernel. ?The patch was made for 5.15 a kernel and there are minor code differences with the 6.1.x kernels. ?However, it's very apparent the patch was applied to the running kernel version.
? Cheers
? Mike
??
there was an issue with axip/axudp links going dead and I found that kernel 6.2 seemed to resolve this issue, but I'm not sure if any of the recent patches address all problems, or just a few hi...
On 2024-02-03 1:53 a.m., Jon Bousselot KK6VLO wrote:
JJ, how far back must we go to get a Raspbian release where this isn't broken?
First to get an install of ax25 that doesn't crash while I work on doing a custom kernel on Bookworm.
The kernel.org links seem to indicate this is a problem for ax25 on all linux platforms, not just the Pi.? Is that correct?
-Jon
Correct.
