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

Troubleshooting
,
1

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:TLOGab1 T I:W~)","voltage":3.9765625}

What is this?

Thanks!

2

Hi @timjoh,

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

Rob

3

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

4

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

5

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.

6

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

Rob

7

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

8

Sharing log files via email to Blues support.

9

Looks like this was related to having trace enabled.

Thanks for the help!

3 Likes