[coreboot] Data in memory changes unexpectedly in initialize_cpus

Bao, Zheng Zheng.Bao at amd.com
Wed Feb 10 11:24:48 CET 2010


I am debugging the fam10+RS780+SB700. Now I am facing a problem which
troubles me for quite a long time. It came up since CBFS play its role.
The data in memory changes unexpectedly. The printk_debug can not help
to narrow down the point where the writing happens.

So I set the memory address which changes during booting as a breakpoint
trigger. Anyone writes data to this address will cause a breakpoint. But
unfortunately nothing can be captured. So I had to set breakpoint in the
whole process to narrow down. Now I narrow down to the initialize_cpus
in src/cpu/x86/lapic/. The functions called in initialize_cpus are
static which can not find a symbol in the coreboot.map. I need to
disassemble the binary to find out why. Before that, I need to guess
what on earth happens.

It seems to have something to do with the SMP. It seems that other cores
write data into the memory which is not belong to them. Do you think it
can happen?


Zheng





More information about the coreboot mailing list