Re: tgtd CPU 100% problem

Thanks very much for reply. I think it may be better to assert failed to exit problem than run the endless loop after receivered DEVICE_REMOVAL event. Or we can sleep 5 ms to check if the conn->h.state is STATE_FULL. Note that neither of the CC'd lists are the correct list for stgt, you

Re: tgtd CPU 100% problem

Thanks very much for reply. I think it may be better to assert failed to exit problem than run the endless loop after receivered DEVICE_REMOVAL event. Or we can sleep 5 ms to check if the conn->h.state is STATE_FULL. 2017-07-11 16:29 GMT+08:00 Sagi Grimberg : > > > On 11/07/17

Re: tgtd CPU 100% problem

On 11/07/17 10:51, 李春 wrote: We have meet a problem of tgtd CPU 100%. the infinband network card was negotiate as eth mode by mistake, after we change it to ib mode and restart opensmd for correct State（Active） the tgtd using 100% of CPU. and when we connect to it using tgtadm, tgtadm hang

tgtd CPU 100% problem

We have meet a problem of tgtd CPU 100%. the infinband network card was negotiate as eth mode by mistake, after we change it to ib mode and restart opensmd for correct State（Active） the tgtd using 100% of CPU. and when we connect to it using tgtadm, tgtadm hang forever. # how to repeat * tgtd