I do have a serial console attached to the Pi-1
? Sorry, I misread your message ... At least I didn't post an amazon link to an adapter :) .
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
? Cool, so between the two of us we have 4 Pis on 6.1.0 that crash. ?If you get a crash after you disable beacon, grab the crash string; I'm very curious to know what process it blames. ?
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.
I had the same thought about beacon, but was disappointed to see another process trigger the crash; reverting to an earlier release may be your only solid work around right now.
So I heard you say that prior crashes happened every 1-2 days and it looks like this crash happened after only 3.5 hours. ?My systems have varied between 4 - 6 days between crashes. ?I have a theory that the crash happens after the kernel processes a certain amount of AX.25 traffic. ?It could explain why your Pi crashes faster than my Pi. ?My packet channel is pretty quiet; sometimes 2 - 3 minutes go by without even a single transmission. ?Would you say your packet channel is busier than this? ?Maybe I should trend the packet count from ifconfig ...
? Cheers
? Mike
