AP_Logger: stuck thread()

Blue Robotics Vehicles BlueBoat
1

Hello, I am testing the Ardurover firmware on SITL from a Raspberry Pi 4 B with BlueOS 1.1.1 and QGroundControl v4.3.0. After installing Ardurover Firmware version 4.2.3 (STABLE) on SITL and loading the default parameters from the BlueOS web interface, I encounter the error: AP_Logger: stuck thread(), and the yellow message ‘Not Ready.’ Additionally, the vehicle configurations are not the same as those for the BlueBoat. I would like to know if there is a way to correct this or if it is due to some limitation in SITL for simulating the flight controller for the BlueBoat. Attached are some images of the configuration I made and the error that appears.

Captura de pantalla 2023-12-07 082206
Captura de pantalla 2023-12-07 0822061920×1080 231 KB

2

Are you still running into this issue?

I just encountered something similar with BlueOS and ArduSub SITL on a Raspberry Pi. I’m getting about 4 "Critical: AP_Logger: stuck thread ()" errors per minute.

My setup:

  • Pi 4B 8GB
  • ArduSub 4.5 BETA SITL
  • BlueOS 1.2 beta 8
  • GCS is QGC daily build, I also tried Cockpit and got the same result

There are a bunch of software layers between the AP file system and the actual SD card, this might be a challenge to track down.

3

This happens when the logging thread starves for IO. Either there’s something using a lot of disk IO in the system, or you could have a not-great sd card, see this issue.

I think that could also happen if you configure ardusub to generate a lot of logs, say with LOG_REPLAY=1.

2 Likes
Upgraded my BLUEROV2-R3-RP
4

I imaged a new 32GB SD card and I am still seeing this on 4.5 beta 1. The same cards work great on 4.1.2.

I have not seen this w/ the same software running on live ROVs, which is good. Just an annoyance.

5

Just wondering if anybody has any new info about this. I am having the same issue with the Blue Boat. My card is 256 gb, with 150 mb/s write and 205 mb/s read speed. I am using the latest stable firmware (as of this date) and QGC. How can I check how much IO usage there is?

6

For the total usage and a detailed breakdown you can run iotop in the BlueOS Terminal.

As a friendlier overview, BlueOS 1.5 (currently in beta) includes a rough estimate of disk write speed as part of the Disk header bar widget.

Noting that BlueOS master also now has functionality to test the disk speed capacity, which I believe should end up included in BlueOS 1.5.