mbox on bmc doesn't respond correctly to hostboot loader in the mpipl path

[rajadas2]

The OPAL is up in the system runtime, here we have software hacks to crash opal, which will trigger S0/S1 interrupts on SBE while going down. Basis those interrupts SBE run the mpipl isteps (which is the same path as Phyp TI)

Mpipl Start Path Istep - 1) istepStartMpipl 2) p9_suspend_powman 3) p9_query_core_access_state 4) istepMpiplRstClrTpmBits 5) p9_sbe_check_quiesce 6) p9_l2_flush 7) p9_l3_flush 8) p9_sbe_sequence_drtm

Mpipl Continue path - 1) istepMpiplSetFunctionalState 2) mpipl_dump_reg 3) mpipl_query_quad_access_state 4) mpipl_hcd_core_stopclocks 5) mpipl_hcd_cache_stopclocks 6) p9_quad_power_off

After this SBE Runs the istep 4& 5 on the Master core, which will trigger the hostbootloader again to start the initial sequence of fetching data from Pnor via Mbox.

Here Mbox fails to réspond like it did in the first boot. May be because it doesn't know the host has gone down and came up again and asking the same questions which he has answered before. (this is as per design to keep bmc agnostic of the host state other than runtime/standby).

Need to see why mbox doesn't respond to initial messages from hostboot loader the second time.

[ghost]

this should probably be filed against the open-power/op-build project and/or openbmc/mboxbridge

[rajadas2]

I have opened the issue in the op build now https://github.com/open-power/op-build/issues/1945, closing this one.