[BUG] [ESP32-C3][lock-app] kernel panic

[mmt-10]

Reproduction steps

cd ${MATTER}/examples/lock-app/esp32
idf.py set-target esp32c3
idf.py build
idf.py erase_flash flash

esp32-c3 shows kernel panic and reboot.

Bug prevalence

always

GitHub hash of the SDK that was being used

commit 2e0737c (HEAD -> master, origin/master, origin/HEAD)

Platform

esp32

Platform Version(s)

No response

Anything else?

Log

20230208-esp32.txt

Environment

Host OS : Ubuntu 20.04
ESP-IDF : ESP-IDF Release v4.4.4
ZAP : v2023.02.03-nightly

update info

below environment is no problem, ESP32-C3 is working.
Matter SDK : commit bba4182 (HEAD)
ESP-IDF : ESP-IDF Release v4.4.4
ZAP : v2023.01.19-nightly

[bzbarsky-apple]

From the log:

E (1448) chip[DL]: Chip stack locking error at './third_party/connectedhomeip/src/app/util/attribute-storage.cpp:510'. Code is unsafe/racy

That assert is at the top of emAfReadOrWriteAttribute.

@mmt-10 since you have a working and broken changeset, would you be willing to bisect to find out what changeset introduced the problem?

@shubhamdp @dhrishi

[bzbarsky-apple]

Alternately, @mmt-10 if there is a way to get a stack to the assert, that would pretty much immediately pinpoint the problem, since the problem is some code that is trying to access attributes on the wrong thread.

[mmt-10]

I assume there is a problem with the change after commit id bba4182 at Jan/20.

I'm sorry, I do not know how do I debug it.

[shubhamdp]

@mmt-10 I can reproduce this issue, will look into it.

[dhrishi]

Fixed with #25895