<html><head></head><body><div style="font-family:Helvetica Neue, Helvetica, Arial, sans-serif;font-size:13px;"><div></div>
<div><br></div><div>Having trouble with the latest code: Qemu -m pseries -cpu power8</div><div><br></div><div>SLOF **********************************************************************<br>QEMU Starting<br> Build Date = Jan 9 2018 16:32:41<br> FW Version = git-a523d1b0cd6e96cf<br>qemu-system-ppc64: Trying to execute code outside RAM or ROM at 0x00000000386364d4<br>This usually means one of the following happened:<br><br>(1) You told QEMU to execute a kernel for the wrong machine type, and it crashed on startup (eg trying to run a raspberry pi kernel on a versatilepb QEMU machine)<br>(2) You didn't give QEMU a kernel or BIOS filename at all, and QEMU executed a ROM full of no-op instructions until it fell off the end<br>(3) Your guest kernel has a bug and crashed by jumping off into nowhere<br><br>This is almost always one of the first two, so check your command line and that you are using the right type of kernel for this machine.<br>If you think option (3) is likely then you can try debugging your guest with the -d debug options; in particular -d guest_errors will cause the log to include a dump of the guest register state at this point.<br><br>Execution cannot continue; stopping here.<br><br>LOF **********************************************************************<br>QEMU Starting<br> Build Date = Jan 9 2018 16:32:41<br> FW Version = git-a523d1b0cd6e96cf<br>qemu-system-ppc64: Trying to execute code outside RAM or ROM at 0x00000000386364d4<br>This usually means one of the following happened:<br><br>(1) You told QEMU to execute a kernel for the wrong machine type, and it crashed on startup (eg trying to run a raspberry pi kernel on a versatilepb QEMU machine)<br>(2) You didn't give QEMU a kernel or BIOS filename at all, and QEMU executed a ROM full of no-op instructions until it fell off the end<br>(3) Your guest kernel has a bug and crashed by jumping off into nowhere<br><br>This is almost always one of the first two, so check your command line and that you are using the right type of kernel for this machine.<br>If you think option (3) is likely then you can try debugging your guest with the -d debug options; in particular -d guest_errors will cause the log to include a dump of the guest register state at this point.<br><br>Execution cannot continue; stopping here.<br><br><br></div>
<div id="yahoo_quoted_5548613181" class="yahoo_quoted">
<div style="font-family:'Helvetica Neue', Helvetica, Arial, sans-serif;font-size:13px;color:#26282a;">
<div>
On Friday, January 5, 2018, 6:21:39 AM EST, Jd Lyons <lyons_dj@yahoo.com> wrote:
</div>
<div><br></div>
<div><br></div>
<div><div dir="ltr"><div class="yqt6037388387" id="yqtfd55868">> <br clear="none">> Doesn’t seem to be a load word in this commit?</div><br clear="none">> <br clear="none"><br clear="none">Does anyone know where the load word is defined in SLOF source, I can’t seem to find it?<br clear="none"><br clear="none">Also, what is the best way to index/search source code on Linux, I keep the code on the macOS as spotlight does an ok job of being able to quickly find most anything I’m looking for.</div></div>
</div>
</div></div></body></html>