From 822b64b03c079e9a56fd2befe84af2b4f9841745 Mon Sep 17 00:00:00 2001 From: Masamichi Takagi Date: Mon, 15 Feb 2021 16:01:41 +0900 Subject: [PATCH] docs: add limitation related to Fujitsu TCS xos_hwb Change-Id: I83a1ecd7a0b6d3bcde2b902cd526dfd4feb9e23a --- docs/users.rst | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/docs/users.rst b/docs/users.rst index d2646180..32a6ba9e 100644 --- a/docs/users.rst +++ b/docs/users.rst @@ -202,3 +202,15 @@ Limitations 28. munlockall() is not supported and returns zero. 29. scheduling behavior is not Linux compatible. For example, sometimes one of the two processes on the same CPU continues to run after yielding. + +30. (Fujitsu TCS-only) A job following the one in which __mcctrl_os_read_write_cpu_register() returns ``-ETIME`` fails because xos_hwb related CPU state isn't finalized. You can tell if the function returned ``-ETIME`` by checking if the following line appeared in the Linux kernel message: + + :: + + __mcctrl_os_read_write_cpu_register: ERROR sending IKC msg: -62 + + You can re-initialize xos_hwb related CPU state by the following command: + + :: + + sudo systemctl restart xos_hwb