[coreboot] Strange failure - help?

Myles Watson mylesgw at gmail.com
Tue Mar 17 22:27:37 CET 2009

I have two coreboot trees.  As far as I can tell they're identical.
One produces working ROM images, and the other reboots when it jumps
to the payload.

These are the only differences from the .map files:

0000b03d A _binary_coreboot_ram_rom_size
0010b03d A _eiseg
fffeb03d A _x
fffeb03d D _binary_coreboot_ram_rom_end
fffeb03d D _eliseg
fffeb03d D _eram

0000b222 A _binary_coreboot_ram_rom_size
0010b222 A _eiseg
fffeb222 A _x
fffeb222 D _binary_coreboot_ram_rom_end
fffeb222 D _eliseg
fffeb222 D _eram

The broken one has a path of:
The working one's path is:

They were both working until yesterday.  I've tried everything I can
think of.  I've removed the non-functional one's build directory
completely.  The payloads are bit-for-bit identical.

The only difference in the boot log before the reboot is this line:
Wrote coreboot table at: 00000500 - 00000788  checksum 5385

Wrote coreboot table at: 00000500 - 0000076c  checksum 4fd2

diffing the hexdump of the ROM files shows that the payload is identical.

Any ideas?

It is true that I have a working tree, but if I didn't I'd be hosed so
I'd like to know the real cause.


More information about the coreboot mailing list