You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
"TeeConnect failed" error is observed with continuous or repeated usage of CSDK binary built with intel® CSE option. It may happen when the CSDK binary is forcefully terminated (without giving time to exit gracefully).
To Reproduce
Occurs sporadically.
Expected behavior
"TeeConnect failed" error is not observed.
Workaround to fix
Wait for few minutes or rebooting the system will resolve this issue.
Screenshots
sudo ./build/cse-clear
TeeConnect failed!
HECI init failed!!
TeeWrite failed (10) [attempted 12 cmd bytes]
HECI CLEAR DEVICE STATUS failed!!
TeeWrite failed (10) [attempted 12 cmd bytes]
HECI CLEAR OVH failed!!
Cleared Device Status and OVH from CSE!!
Test Environment
Provide details about your test environment.
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered:
tajnisha
changed the title
[BUG] Sporadic failure with continuous usage of CSDK built with intel® CSE
[BUG] Sporadic failure with continuous usage of CSDK built with Intel® CSE
Apr 25, 2023
Describe the bug
"TeeConnect failed" error is observed with continuous or repeated usage of CSDK binary built with intel® CSE option. It may happen when the CSDK binary is forcefully terminated (without giving time to exit gracefully).
To Reproduce
Occurs sporadically.
Expected behavior
"TeeConnect failed" error is not observed.
Workaround to fix
Wait for few minutes or rebooting the system will resolve this issue.
Screenshots
sudo ./build/cse-clear
TeeConnect failed!
HECI init failed!!
TeeWrite failed (10) [attempted 12 cmd bytes]
HECI CLEAR DEVICE STATUS failed!!
TeeWrite failed (10) [attempted 12 cmd bytes]
HECI CLEAR OVH failed!!
Cleared Device Status and OVH from CSE!!
Test Environment
Provide details about your test environment.
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: