qemu-armv7: code execution out of RAM or ROM using latest QEMU

[Piotr Król]

Hi all,
I tried to boot coreboot using latest qemu and figured out that it fails
with:

qemu: fatal: Trying to execute code outside RAM or ROM at 0x04000000

R00=00000002 R01=00000000 R02=00000000 R03=00000000
R04=00000000 R05=00000000 R06=00000000 R07=00000000
R08=00000000 R09=00000000 R10=00000000 R11=00000000
R12=00000000 R13=0007fed0 R14=6001032f R15=04000000
PSR=600000d3 -ZC- A svc32
(...)

I was able to narrow down qemu commit that breaks coreboot booting.

Bisection points to 75c9a1a 'target-arm: Implement vCPU reset via
KVM_ARM_VCPU_INIT for 32-bit CPUs':

http://git.qemu.org/?p=qemu.git;a=commit;h=75c9a1a0473cc5ca9756d11b236c715c7...

It was changed by someone from Linaro, can we assume that this change is
ok and problem is on coreboot side ?

If the problem is on coreboot side than have you got any ideas how to
fix it (or where to dig) ?

Best Regards,
Piotr Król

qemu-armv7: code execution out of RAM or ROM using latest QEMU

[ron minnich]

You can't assume much of anything. That commit seems not that harmful.
What would help is if you tell us more about when the problem happens.
There's just not enough info in your note, but I'd love to try to
help.

Thanks!

ron

On Sun, Aug 10, 2014 at 12:57 PM, Piotr Król  wrote:
> Hi all,
> I tried to boot coreboot using latest qemu and figured out that it fails
> with:
>
> qemu: fatal: Trying to execute code outside RAM or ROM at 0x04000000
>
> R00=00000002 R01=00000000 R02=00000000 R03=00000000
> R04=00000000 R05=00000000 R06=00000000 R07=00000000
> R08=00000000 R09=00000000 R10=00000000 R11=00000000
> R12=00000000 R13=0007fed0 R14=6001032f R15=04000000
> PSR=600000d3 -ZC- A svc32
> (...)
>
> I was able to narrow down qemu commit that breaks coreboot booting.
>
> Bisection points to 75c9a1a 'target-arm: Implement vCPU reset via
> KVM_ARM_VCPU_INIT for 32-bit CPUs':
>
> http://git.qemu.org/?p=qemu.git;a=commit;h=75c9a1a0473cc5ca9756d11b236c715c7...
>
> It was changed by someone from Linaro, can we assume that this change is
> ok and problem is on coreboot side ?
>
> If the problem is on coreboot side than have you got any ideas how to
> fix it (or where to dig) ?
>
> Best Regards,
> Piotr Król