OPAL returns OPAL_WRONG_STATE for XSCOM operations done to read any core FIR which is sleeping, offline.
On Friday 27 January 2017 05:47 AM, Michael Ellerman wrote:
Vipin K Parashar <vi...@linux.vnet.ibm.com> writes:Added check for OPAL_WRONG_STATE error code returned from OPAL. Currently Linux flashes "unexpected error" over console for this error. This will avoid throwing such message and return I/O error for such OPAL failures.Why do we expect to get OPAL_WRONG_STATE ? cheers
