开云体育Hello Michael, Following up on this issue, I've had a couple of more kernel panics since my last message. ?Unfortunately, I couldn't dedicate my monitor to troubleshooting, so I missed the first panic text output. ?However, since I had disabled beacon prior to the crash, I at least know it wasn't involved in this one. I don't think there are any known issues with the Linux AX.25 stack and UI (aka unconnected) packets.? There *are* known issues with connected-mode sessions though. ? I strung up a serial console and ran "apt upgrade-full" to continue troubleshooting. ?The second crash happened this afternoon, from which I was able to capture the console messages below. ?It looks like Pat made the call that triggered the panic. ?I think that lets me rule out the user space AX-25 tools. Not necessarily but I do suspect the issue is the in-kernel AX.25 stack but can be provoked by user-space I/O coming through libax25
That though process is incorrect here.? Pat is just an userland-based application and depending on configured it to make AX.25 packet connections, it will either do it via the Linux in-kernel AX.25 support of via an AGW connection (offered via say Direwolf, G8BPQ Qtsoundmodem, etc).? btw.. the Rpi4/5 eeprom firmware is really more for hardware initialization and booting level stuff..? not OS/software related function. ?I thought about replacing libax25 with VE7FET's version, but I note that Pat isn't linked against libax25: I don't think that's accurate as Pat is a modular Go program and the one binary might not link in stuff like this.? If you look at the package dependencies, they are there: ?? I would recommend this sequence: ?? 1. reboot your pi, start up the whole Linux AX.25 stack however you do that (script, system, etc).? Now bring DOWN the entire AX.25 stack.? Now bring the stack back up again, try Pat, and now try to reproduce the issue again (might take days as you said before) If you still eventually hit the kernel panic again, now try these steps: ?? 2. uninstall the old OS provided ax25-apps, ax25-tools, libax25 packages ?? 3. download, compile, and install the VE7FET, ax25-apps, ax25-tools, libax25 packages ?? 4. Bring up the AX.25 stack and try to reproduce the panic again If you still eventually hit the kernel panic again, try doing the #1 work around and see if it helps (works around a known issue of ANSWERING an incoming AX.25 connected-mode session which will panic the kernel on Ubuntu 20.04 hosts using the 5.15.0-xx kernel. --David KI6ZHD |
