Qemu-target ROM freeze/crash with current v2 HEAD (CBFS-enabled)

[Cristi Magherusan]

Hello,

I'm getting this output when running a qemu ROM compiled using latest v2
tree, and my AVATT payload - with KVM support in qemu/kernel it freezes,
and without, it crashes:

Crash:
http://pastebin.com/m830348a

The freeze occurs just after the "Jumping to boot code at 10000" message
is displayed.

If anyone has a clue, please help me.

Thanks,
Cristi

[GSoC] Qemu-target ROM freeze/crash with current v2 HEAD (CBFS-enabled)

[ron minnich]

On Mon, Jul 27, 2009 at 4:42 PM, Cristi
Magherusan wrote:
> Hello,
>
> I'm getting this output when running a qemu ROM compiled using latest v2
> tree, and my AVATT payload - with KVM support in qemu/kernel it freezes,
> and without, it crashes:
>
> Crash:
> http://pastebin.com/m830348a
>
> The freeze occurs just after the "Jumping to boot code at 10000" message
> is displayed.

I'd still like to know why it's going to 10000. That is not what I
ever used when I had a LAB payload.
ron

[GSoC] Qemu-target ROM freeze/crash with current v2 HEAD (CBFS-enabled)

[Cristi Magherusan]

On Mon, 2009-07-27 at 19:03 -0700, ron minnich wrote:
> On Mon, Jul 27, 2009 at 4:42 PM, Cristi
> Magherusan wrote:
> > Hello,
> >
> > I'm getting this output when running a qemu ROM compiled using latest v2
> > tree, and my AVATT payload - with KVM support in qemu/kernel it freezes,
> > and without, it crashes:
> >
> > Crash:
> > http://pastebin.com/m830348a
> >
> > The freeze occurs just after the "Jumping to boot code at 10000" message
> > is displayed.
>
> I'd still like to know why it's going to 10000. That is not what I
> ever used when I had a LAB payload.
> ron

Hello,

I still haven't found the solution. If there's anyone who can afford to
take a look, I'd really appreciate it.

Here are my payloads:
http://panzer.utcluj.ro/~alien/coreboot/AVATT/freeze/
The ROM image was created using the buildroot-payload.elf f

Thanks!
Cristi

[GSoC] Qemu-target ROM freeze/crash with current v2 HEAD (CBFS-enabled)

[Myles Watson]

> > > The freeze occurs just after the "Jumping to boot code at 10000"
>
> message
> > > is displayed.

This looks like the SeaBIOS problem with the latest qemu.  That failure
happens because qemu has marked 0xf0000-0x100000 as read only, so after the
payload gets copied there it is read back as zeros.
> > I'd still like to know why it's going to 10000. That is not what I
> > ever used when I had a LAB payload.
> > ron

Have you tried a different address, or a different payload at the same
address?

Thanks,
Myles

[GSoC] Qemu-target ROM freeze/crash with current v2 HEAD (CBFS-enabled)

[ron minnich]

I think it's the use of mkelfimage among other things, we're going to
take a new approach

ron

[GSoC] Qemu-target ROM freeze/crash with current v2 HEAD (CBFS-enabled)

[Peter Stuge]

ron minnich wrote:
> I think it's the use of mkelfimage among other things, we're going
> to take a new approach

I am really curious to know if it works to just use vmlinux as
payload. It might. See also http://coreboot.org/Initramfs

//Peter