Mystery segmentation fault: Raspberry Pi 5 #997
Comments
|
I saw a conversation in discord from 2 months ago that was similar to what you're reporting. The v4 drivers that came with raspbian might be out of date and don't work with v4 but did with v3. The comment was: "It's because of the v4-compatible drivers, and where they are sourced from. I don't think they're normally available in any raspi distros as of yet, but SDR Trunk essentially has them built-in." Might be worth checking you have the latest drivers that support the v4? |
|
I have been running TrunkRecorder on three RPi5's since July 2024. I've had one instance of seg fault on one of the Pi's during that entire time. Sorry that I don't have an answer, but I do have a shot in the dark that worked for me. Like your first recorder, I had one of my RTL-SDRs (Nooelec NESDR-SMArt) set to a "long" center frequency for a system where the system frequencies were 4 decimal places at the most. I rounded the center frequencies down to a single decimal place (853500000 - [853.500000]) and have not seen that problem since. One of my RPi5's is on system that uses 5 decimal places, so all of the center frequencies for that system are set to 5 decimal places as well. Again, this was just a shot in the dark that worked for me, but I have not seen the problem since, and that was back before Thanksgiving. |
I did try manually installing the latest drivers according to the RTL-SDR guide, but that seemed to cause some other dependency issues. I figured it was worth trying to solve the issue with the default recommended packages to better identify the issue. Perhaps I'll try that again if I can't resolve it some other way.
I'll definitely give that a try as well. If I had to guess, there might be something a little more in-depth happening, since it seems to seg-fault within a few seconds of booting up most of the time. I figured it also might be worth trying to disconnect the antennas to see if the error occurs when a particular transmission is being processed, or if it just happens due to some background process. |
I'm running the latest version of Trunk Recorder as of the time of writing, installed via the documentation at https://trunkrecorder.com/docs/Install/INSTALL-PI
I'm using a Raspberry Pi 5 (6.6.74+rpt-rpi-2712) with two RTL-SDR v4.
I'm using a known-good configuration file from a previous installation (which worked reliably for weeks at a time). Here's the configuration contents:
{ "ver": 2, "sources": [{ "center": 855059375, "rate": 2400000, "error": 2000, "gain": 50, "debugRecorders": 0, "digitalRecorders": 4, "driver": "osmosdr", "device": "rtl=0" }, { "center": 861350000, "rate": 2400000, "error": 2000, "gain": 50, "debugRecorders": 0, "digitalRecorders": 4, "driver": "osmosdr", "device": "rtl=1" }], "systems": [{ "control_channels": [855212500, 856037500, 860787500, 860912500], "type": "p25", "shortName": "OhioMARCS", "talkgroupsFile": "./talkgroup.csv", "modulation": "qpsk" }] }trunk-recordstarts just fine, and begins scanning the configured frequencies, but it will abruptly seg-fault anywhere from 10 seconds to a couple minutes after starting. Here's an example of the console output during such a scenario:I followed the steps at https://trunkrecorder.com/docs/DEBUG in hopes of diagnosing the issue. Here's the output of
gdb trunk-recorder core:I've tried re-compiling as well as several restarts. The OS is a clean install, and the only changes are those explained in the documentation. Any idea on what my next steps should be?
The text was updated successfully, but these errors were encountered: