netipmid consumes much CPU when obmc-console socket is shutdown

[Heyi Guo]

Hi all,

We found netipmid will consumes much CPU when SOL is activated but 
obmc-console socket is shutdown by some reason (can simply shutdown 
obmc-console by systemctl stop ....).

After obmc-console socket is closed, the async_wait() in 
startHostConsole() is always triggered, and consoleInputHandler() will 
read empty data (readSize == 0 and readDataLen == 0), but all the ec 
condition check will NOT hit!

 From boost reference, it is said the function read_some() will:

The function call will block until one or more bytes of data has been 
read successfully, or until an error occurs.

Is it a bug of boost? Or is there anything wrong in ipmi-net? And how 
can we make netipmid more robust on obmc-console socket shutdown?

Thanks,

Heyi