Hello, In the process of upgrading our fleet of devices to v6.2.5 LTS and/or v8.1.4 LTS. We caught a device on v8.1.4 checking in to Notehub with _health.qo looking like: {"text":"boot (*** mutexLock nested! file.c:216. mutex:127 [17149] [3.0] G:Gp:W~ M:Mp:W900 U:W0 R:Rp:W0 S:Sps:NS:FSwnopen:TLOG…

Hi @timjoh , Do you have trace logging enabled on this Notecard? If so, how long has it been active? Rob

Hi Rob, I’m told that we do not have trace logging enabled. I also see that v8.1.4 LTS is no longer available on the list of available Notecard firmware upgrades. Thanks, Tim

Hi @timjoh - Is the Notecard functional/responding to requests?

Hi Rob - I’m told that the specific Notecard this was seen on, did not seem to transmit as expected during the periods it was reporting the mutexLock nested message. However, I am not the engineer who is/was closest to that specific device or its operation.

Ok thanks for that information. We will follow up with next steps soon. Rob

Hi @timjoh - Would it be possible for you to run the following request on the Notecard and let us know the response? {"req":"card.trace"} Thanks, Rob

Sharing log files via email to Blues support.

Error condition spotted on v8.1.4 LTS - mutexLock nested! file.c:216. mutex:127 in _health.qo

Troubleshooting

timjoh August 4, 2025, 6:43pm 9

Looks like this was related to having trace enabled.

Thanks for the help!

3 Likes

Topic		Replies	Views
Unexpected log messages Troubleshooting	7	759	March 20, 2021
Swan MCU locking up? Troubleshooting	8	139	August 23, 2024
Health logs in Notehub on each sync from card.attn Notehub.io	2	20	February 18, 2026
Resetting Notecard I2C communications. Sequence number mismatch	10	269	December 13, 2023
Latest LTS firmware in docs not available for OTA Firmware	1	306	May 19, 2023

Error condition spotted on v8.1.4 LTS - mutexLock nested! file.c:216. mutex:127 in _health.qo

Related topics