Agent said to report this trace. Also, `ASSERTION FAIL` after upgrading to 14.2.1

[Sheldon-Cole]

Yesterday, July 1, I had an issue where the left-half of the keyboard starting locking up randomly after cleaning the key caps. I assumed it was because I pushed some awkward combo of keys. So, I rebooted the keyboard and the left-half was still unresponsive. So, I decided to upgrade the firmware thinking I stumbled on a bug that might have been fixed in a newer firmware. So, I upgraded the keyboard to 14.2.0; both halves were connected via bridge cable. The left-half showed it was updating via the agent but was showing 0.0.0 for the firmware version. Once I reset the right-half via the RESET button on the back of the keyboard, the left-half started communicating again and I was able to update both halves to 14.2.0.

Today, July 2, I saw that 14.2.1 had been released and decided to upgrade for the battery percentage fix. After upgrading to 14.2.1, the left-half became unresponsive but I was able to get it back with the reboot macro. However, the keyboard started lagging. So I downgraded to 14.0.1, disconnected the bridge cable and rebooted the keyboard. Then, upgraded the firmware back to 14.2.0, and rebooted the keyboard via reboot macro. The trace output below was spit out by the agent.

Trace 1 14.2.0

Printing trace buffer because: Looks like the firmware freezed. If that is the case, please report bellow trace to the devs:

Last EV: 512
Trace:
)s2r2Os2r2Os2r2Os2r2Os2r2Os2r2Os2r2Os2r2Os2r2Os2r2Os2r2Os2r2Os2r
2Os2r2Os2r2Os2r2Os2r2Os2r2Os2r2Os2r2Os2r2Os2r2Os2r2Os2r2Os2r2Os2
r2Os2r2OI2,2,6,1679(<>l6u1u2v3w0w1x1x2x3x4w2w3w4w5w6ve3u7u8l8)(l
6u1u2v2u3u6u7u8)()(l6u1u2v3w0w1w2w3w4w5w6ve3u7u8)s2r2O()s2r2Os2(

ASSERTION FAIL @ WEST_TOPDIR/zephyr/subsys/bluetooth/host/hci_core.c:430
os: r0/a1:  0x00000003  r1/a2:  0x00000000  r2/a3:  0x2000f3e0
os: r3/a4:  0x00000003 r12/ip:  0x2000f4b0 r14/lr:  0x00039461
os:  xpsr:  0x01000000
os: r4/v1:  0x20039b54  r5/v2:  0x00000000  r6/v3:  0x00002010
os: r7/v4:  0x200337d0  r8/v5:  0x200337d4  r9/v6:  0x00000c7d
os: r10/v7: 0x200122a0  r11/v8: 0x00000000    psp:  0x200337b0
os: EXC_RETURN: 0x0
os: Faulting instruction address (r15/pc): 0x00039470
os: >>> ZEPHYR FATAL ERROR 3: Kernel oops on CPU 0
os: Current thread: 0x2000f3e0 (main)
fatal_error: Resetting system

Rebooting the keyboard again did not produce the same issue. So, I moved on to updating the keyboard to 14.2.1 again. Again, I upgraded the keyboard without the bridge cable attached. However, as the upgrade finished agent spit out another trace.

Trace 2 14.2.1

ASSERTION FAIL @ WEST_TOPDIR/zephyr/subsys/bluetooth/host/hci_core.c:430
os: r0/a1:  0x00000003  r1/a2:  0x00000000  r2/a3:  0x2000f3f0
os: r3/a4:  0x00000003 r12/ip:  0x2000f4c0 r14/lr:  0x0003953d
os:  xpsr:  0x01000000
os: r4/v1:  0x20039f7c  r5/v2:  0x00000000  r6/v3:  0x00002010
os: r7/v4:  0x20033810  r8/v5:  0x20033814  r9/v6:  0x00000c05
os: r10/v7: 0x200122b0  r11/v8: 0x00000000    psp:  0x200337f0
os: EXC_RETURN: 0x0
os: Faulting instruction address (r15/pc): 0x0003954c
os: ]]] ZEPHYR FATAL ERROR 3: Kernel oops on CPU 0
os: Current thread: 0x2000f3f0 (main)
===== PANIC =====
Printing trace buffer because: crash/panic
EV: 393730
Tag: v14.2.1
Trace:
[i1][i1][i1][i1][i1][i1][i1][i1][i1][i1][i1][i1][i1][i1][i1][i1]
[i1][i1][i1][i1][i1][i1][i1][i1][i1][i1][i1][i1][i1][i1][i1][i1]
[i1][i1][i1][i1][i1][i1][i1][i1][i1][i1][i1][i1][i1][i1][i1][i1]
[i1][i1][i1][i1][i1][i1][i1][i1][i1][i1][i1][i1][i1][i1][i1][i1]
fatal_error: Resetting system

After coping the trace message and again, rebooting the keyboard via the reboot macro, everything seems to be in working order.