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

tests/kernel/mutex/mutex/ FAILED @ esp32 #1242

Closed
inakypg opened this issue Aug 24, 2017 · 6 comments
Closed

tests/kernel/mutex/mutex/ FAILED @ esp32 #1242

inakypg opened this issue Aug 24, 2017 · 6 comments
Assignees
Labels
bug The issue is a bug, or the PR is fixing a bug priority: high High impact/importance bug

Comments

@inakypg
Copy link
Contributor

inakypg commented Aug 24, 2017

toolchain: espressif
Zephyr: caa3779

***** BOOTING ZEPHYR OS v1.9.0-rc1 (delayed boot 1000ms) - BUILD: Aug 23 2017 19:23:27 *****
Done LOCKING!  Current priority = 5
Testing recursive locking
Recursive locking tests successful
PASS - regression_task.
===================================================================
===================================================================
RunID: ci-170823-1622-32:i0kn
PROJECT EXECUTION SUCCESSFUL
*** Unhandled exception ****
Exception cause 0 (illegal instruction):
  EPC1     : 0x4008281e EXCSAVE1 : 0x3d3d3d3d EXCVADDR : 0x00000000
Program state (PS):
  INTLEVEL : 03 EXCM    : 0 UM  : 1 RING : 0 WOE : 1
  OWB      : 04 CALLINC : 2
Current thread ID = 0x3ffb1698
Faulting instruction address = 0xdeaddead
Fatal fault in essential thread! Spinning...

@nashif nashif added the bug The issue is a bug, or the PR is fixing a bug label Aug 24, 2017
@lpereira
Copy link
Collaborator

I can't reproduce this on caa3779: I get the "PROJECT EXECUTION SUCCESSFUL" message, and no exceptions are thrown after that. Are you getting the crash immediately after the test ends, or does it take some time for it to happen? I've let it running here over a minute and nothing happened.

@lpereira
Copy link
Collaborator

Can't reproduce on 83088a2 (current HEAD at the moment) either.

@nashif
Copy link
Member

nashif commented Aug 24, 2017

I also was not able to reproduce

@inakypg
Copy link
Contributor Author

inakypg commented Aug 24, 2017

It's hard to tell, but it is happening consistently on the automation results. My first hunch would be it'd be an artifact of the power down process -- but then it'd affect other testcases, and it does not.

One thing I missed is esp-idf.git is v2.0-rc1-956-g81f98c0

@inakypg
Copy link
Contributor Author

inakypg commented Aug 24, 2017

Leandro: timing wise, it is hard/er to know; if you guys can't reproduce, let's let it run a few more times--maybe it got fixed by something else.

@linkmeyer linkmeyer added the priority: high High impact/importance bug label Oct 23, 2017
@lpereira
Copy link
Collaborator

Closing as this cannot be reproduced on current HEAD.

nagineni pushed a commit to nagineni/zephyr that referenced this issue Nov 20, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug The issue is a bug, or the PR is fixing a bug priority: high High impact/importance bug
Projects
None yet
Development

No branches or pull requests

4 participants