Ping. What is the way to solve this?
I can NOT merge the CBFS to our code for a long time.
Zheng -----Original Message----- From: coreboot-bounces@coreboot.org [mailto:coreboot-bounces@coreboot.org] On Behalf Of Bao, Zheng Sent: Saturday, October 10, 2009 10:12 AM To: coreboot@coreboot.org; Carl-Daniel Hailfinger Subject: Re: [coreboot] coreboot hangs on my AMD fam10 board (update debugmessage).
I update the code. It hangs at somewhere else. It seems to be what Carl-Daniel said. Is there any workaround way to skip this and let do my own job?
Zheng
-----Original Message----- From: Carl-Daniel Hailfinger [mailto:c-d.hailfinger.devel.2006@gmx.net] Sent: Saturday, October 10, 2009 9:16 AM To: Bao, Zheng Cc: coreboot@coreboot.org Subject: Re: [coreboot] coreboot hangs on my AMD fam10 board.
On 09.10.2009 08:10, Bao, Zheng wrote:
Current coreboot seems to hang somewhere. Before the 60th anniversary
of
People's Republic of China, I always disable the CBFS when I worked on my fam10 board, otherwise it would be error. But now, I can not find where I can disable it. It seems to stop at waiting AP cores.
I am wondering if it is caused by CBFS and if it happens on other
board.
If any one can test it, I will be appreciating.
We have not solved the SMP startup printk locking yet. That explains the mangled log messages. Unless I'm mistaken we still decompress some parts multiple times concurrently to the same address and that can crash the code. Overlapping stack might also crash the code during lzma decompression. Decompression of AP code should happen on the BSP or on exactly one AP, but not on all APs.
coreboot-2.0.0-r623M_tilapia_fam10_Fallback Fri Oct 9 13:15:49 CST
2009
starting... [...] Start other core - nodeid: 00 cores: 03 started ap apicid: cccooorrreeexxx::: --------- {{{ AAAPPPIIICCC IIIDDD === 000312 NNNOOODDDEEEIIIDDD === 000000 CCCOOORRREEEIIIDDD === 000321}} } ---------
Regards, Carl-Daniel