[Skiboot] [PATCH] FSP: Notify FSP of Platform Log ID after Host Initiated Reset Reload

Stewart Smith stewart at linux.vnet.ibm.com
Wed May 10 15:26:52 AEST 2017


Stewart Smith <stewart at linux.vnet.ibm.com> writes:
> Trigging a Host Initiated Reset (when the host detects the FSP has gone
> out to lunch and should be rebooted), would cause "Unknown Command" messages
> to appear in the OPAL log.
>
> This patch implements those messages
>
> How to trigger FSP RR(HIR):
>
> $ putmemproc 300000f8 0x00000000deadbeef
> s1	k0:n0:s0:p00
> ecmd_ppc putmemproc 300000f8 0x00000000deadbeef
>
> Log showing unknown command:
> / # cat /sys/firmware/opal/msglog | grep -i ,3
> [  110.232114723,3] FSP: fsp_trigger_reset() entry
> [  188.431793837,3] FSP #0: Link down, starting R&R
> [  464.109239162,3] FSP #0: Got XUP with no pending message !
> [  466.340598554,3] FSP-DPO: Unknown command 0xce0900
> [  466.340600126,3] FSP: Unhandled message ce0900
>
> The message we need to handle is "Get PLID after host initiated FipS
> reset/reload". When the FSP comes back from HIR, it asks "hey, so, which
> error log explains why you rebooted me?". So, we tell it.
>
> Reported-by: Pridhiviraj Paidipeddi <ppaidipe at linux.vnet.ibm.com>
> Signed-off-by: Stewart Smith <stewart at linux.vnet.ibm.com>

Merged to master as of f3a5741408a11be6992cf8779f2eae10b08c020a

-- 
Stewart Smith
OPAL Architect, IBM.



More information about the Skiboot mailing list