[Gems-users] Received multiple read physical memory exception when running Opal

[Yu-Ju Hong <yuru.hong@xxxxxxxxx>]

Hi,

I got several warnings during simulation of some of the applications using opal.
 warning: pstate_t::readPhysicalMemory: Exception: Physical memory read raised exception (address: 0x300008be210 size: 4)
(All these warnings had similar addresses -- 0x30000xxxxxx)

The simulation continued even with the warnings, but I don't know if opal was behaving correctly in this situation. In the readPhysicalMemory function in pstate.C, there is a comment saying that this kind of warning should never happen.
    // CM: There never should be exceptions on read physical memory.
    //     ANY that occur are bad signs & should be investigated.

Will this warning cause any incorrectness in the simulation? Does anybody have any idea what might have caused these warnings and how to fix them? Thanks!

Yu-Ju