In case of FINDA flickering, the selector might have refused to move to a new position. However, surrounding code was expecting, that the selector accepted the request. Surrounding code was waiting for the selector performing a task which never started -> nice "deadlock".
This is now fixed, or at least worked around. In case the selector refuses to move, an error of FINDA_DIDNT_SWITCH_OFF is raised. It may be a bit counter intuitive at first, but it describes the real problem well.
[x] Still, since this has been an extremely rare issue, unit tests need to be added for it (nobody can reliably say if the fix worked just by looking at the MMU while printing).
[x] The correct name for this kind of errors must be specified
In case of FINDA flickering, the selector might have refused to move to a new position. However, surrounding code was expecting, that the selector accepted the request. Surrounding code was waiting for the selector performing a task which never started -> nice "deadlock".
This is now fixed, or at least worked around. In case the selector refuses to move, an error of FINDA_DIDNT_SWITCH_OFF is raised. It may be a bit counter intuitive at first, but it describes the real problem well.
MMU-176