> f) However, I found that the frontend program still consistently failed with this error when the trigger rate
> was above the maximum sustainable:
>
> Deferred transition. First call of wait_buffer_empty. Stopping run
> [feov1725MTI00,ERROR] [v1725CONET2.cxx:685:ReadEvent,ERROR] Communication error: -2
> [feov1725MTI00,ERROR] [feoV1725.cxx:654:link_thread,ERROR] Readout routine error on thread 0 (module 0)
> [feov1725MTI00,ERROR] [feoV1725.cxx:655:link_thread,ERROR] Exiting thread 0 with error
> Stopped chronobox run; status = 0
> Segmentation fault
I sort of 'fix' this problem. There is some sort of problems between the V1725 readout thread and the system call
to esper-tools to stop the run. Some collision between the system resources for these two calls causes the readout
thread ReadEvent call to fail. I 'fix' the problem by adding in the end_of_run part a 500us pause of the readout
threads before I make the system call to esper-tool.
Odd. In principle I think that the system calls and the readout threads are running on different cores. So not
clear what the problem was. Should figure out better diagnosis and fix problem properly. |