Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Platform] M5Stack: No response to Sigma3, Failed to post event to CHIP Platform event queue #26019

Closed
kpark-apple opened this issue Apr 7, 2023 · 5 comments
Labels

Comments

@kpark-apple
Copy link
Contributor

Reproduction steps

  1. Commission M5.
  2. Add another fabric over CASE of the first commissioned fabric
  3. Open a new CASE session over the new fabric
  4. Complete commissioning of the new fabric

Platform

esp32

Platform Version(s)

No response

Type

Manually tested with SDK

(Optional) If manually tested please explain why this is only manually tested

The steps above were exercised.

Anything else?

On M5 log, there were lots of Failed to post event to CHIP Platform event queue messages and one after receiving the Sigma3 message as well. So suspecting resource issue.

I (59199) chip[EM]: <<< [E:13002r S:0 M:38815149 (Ack:13084043)] (U) Msg TX to 0:0000000000000000 [0000] --- Type 0000:10 (SecureChannel:StandaloneAck)
I (59219) chip[IN]: (U) Sending msg 38815149 to IP address 'UDP:[FE80::18DD:660:1490:E11A%st1]:51277'
I (59219) chip[SC]: Received Sigma3 msg
E (59229) chip[SC]: The device does not support GetClock_RealTimeMS() API: 6c.  Falling back to Last Known Good UTC Time
E (60179) chip[DL]: Failed to post event to CHIP Platform event queue
E (60179) chip[CSL]: Failed to queue CHIP System Layer lambda event: 1000000
E (60199) chip[DL]: Failed to post event to CHIP Platform event queue
E (60199) chip[CSL]: Failed to queue CHIP System Layer lambda event: 1000000
...
I (75569) chip[FS]: Fail-safe timer expired
E (75569) chip[SVR]: Failsafe timer expired
E (75569) chip[SVR]: Commissioning failed (attempt 1): 32

M5_pairing_failed_accessory_log_21A220a.txt

@bzbarsky-apple
Copy link
Contributor

@kpark-apple Which SHA is the M5 using? Is it something after 77e39a6?

This could also be similar to #25833 (note the lower-memory non-default configuration file that was added in #25935), and is likely the same as #24418 and #23258

@shah-kartik
Copy link

The SHA used here was
0f1fc1b

@bzbarsky-apple
Copy link
Contributor

OK, so that's after 77e39a6

@stale
Copy link

stale bot commented Oct 15, 2023

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

@stale stale bot added the stale Stale issue or PR label Oct 15, 2023
@bzbarsky-apple bzbarsky-apple removed the stale Stale issue or PR label Oct 16, 2023
@dhrishi
Copy link
Contributor

dhrishi commented Oct 25, 2024

The queue size has been increased to from 25 to 40: https://github.com/project-chip/connectedhomeip/blob/master/config/esp32/components/chip/Kconfig#L385

@dhrishi dhrishi closed this as completed Oct 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants