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.
Zheng
--------------------------------------- coreboot-2.0.0-r623M_tilapia_fam10_Fallback Fri Oct 9 13:15:49 CST 2009 starting...
BSP Family_Model: 00100f42 *sysinfo range: [000cc000,000cf360] bsp_apicid = 00 cpu_init_detectedx = 00000000 microcode: equivalent rev id = 0x1041, current patch id = 0x00000000 microcode: patch id to apply = 0x01000086 microcode: updated to patch id = 0x01000086 success
cpuSetAMDMSR done Enter amd_ht_init() AMD_CB_EventNotify() event class: 05 event: 2006 data: 04 00 00 00 Exit amd_ht_init() cpuSetAMDPCI 00 done Prep FID/VID Node:00 F3x80: e600a681 F3x84: a0e641e6 F3xD4: c8810f24 F3xD8: 03001816 F3xDC: 00005322 Wait all core0s started Wait all core0s started done start_other_cores() init node: 00 cores: 03 Start other core - nodeid: 00 cores: 03 started ap apicid: cccooorrreeexxx::: --------- {{{ AAAPPPIIICCC IIIDDD === 000312 NNNOOODDDEEEIIIDDD === 000000 CCCOOORRREEEIIIDDD === 000321}} } ---------
APmmm isiictccrarrorootccceoooddddeee:::: 0ee1eqqAquuPui iivsvvataalallereetnnnetttd rrr:e uuuvvv0 2 iiAiddPd s =t== a 0r00xtxxe111d000:444 111,,,0 3ccc 000000rrrrseee7nn8ntt0t _ ppepaaaatrttclcchyhh_ siiiedddt ===u p(000)xxx u 000g000e000t00_000c000p0 _
attv EAmmmiXiic=cc0rrrxoooccc1ooo0ddd0eeef:::4 2 pp.paa 0x tcccChhPh U i iidRdd e tvtt oooi saaa ppppppKlll8yyy_ 1==0= . 00 t xx000f1011a00m0001000000_808o686p im
upimmiciizrccorracootocciooodddneee(:::) hh uuppdrdsada7tat8et0dee_ ddpt oott oorp _appiaatnittctcch ss iiid dd === 0 0x00xx001011000000000080886 66 sussucuccceccesesss
cccpuppuSuSSeteetAtAAMDMMDDMMSMSRSR R FFIFIXIMXXsEbMM!7EE0!! 0 C_CCPePPUUU a VrVVeleeryrrs_s kknioeionto unnup n(uuk)nn nnooowsbwwnnn 7 o0oor0rr _ nd noenotvot it sc suesupsup_ppoppproootrrre_ttieedndd!i!! t (
d FdI !0 ooXsnnMbeeE7 0 inC_inPdiiUet v_tVif_ecifredisvds_ivipdioodn_ar _ap_up(insnk(tinsatot(wag)nge: e1 o1)Sr) M a r3e,opiutics ci idDsd:eu: vp 0ip02co Fe t V: IdFBD!IDV DFI P!P0DD- FI 2oo0nXn- M 0AEA V : : C 0P02U3 e edsion unknSoMwBnu so rc onnottr oslulpepro rteenda!b l kn,F IsXbM Er!e CvPiUs iVoenr siiso nA 12u own or snbo70t0 _sudpepviocretesd_!po r oiFnIiXtME(!) : CIPDU EV eDervsiiocne, unBkDFn:ow0n- 20o-r 1n vt supposrb7t0e0d!_ de tiFIcXesM_E!p oCr_PiUn Viet(r)s:io nLP Cu nkDneoviwcne o,r BDnFo:t 0s-u20p-p3or ed! 2IXsMbE7!00 _CdPUe vViceerssi_oponr _unikninto(wn) :o Pr2 Pno tBr isdupgpeo, rBtDedF!: 0- n0 d-4o e ATit_fsidbv70i0d__daepv(sitceasg_e1p)o ra_ipniciitd():: 0 1S 8 AFI DDVevIiDc oen, BADPF: :00-11 -0 sb700_pmio_por_init()
Begin FIDVID MSR 0xc0010071 0x30b200c3 0x40035c40 FIDVID on BSP, APIC_id: 00 BSP fid = 10600 Wait for AP stage 1: ap_apicid = 1 readback = 1010601 common_fid(packed) = 10600 Wait for AP stage 1: ap_apicid = 2 readback = 2010601 common_fid(packed) = 10600 Wait for AP stage 1: ap_apicid = 3 readback = 3010601 common_fid(packed) = 10600 common_fid = 10600 FID Change Node:00, F3xD4: c8810f26 End FIDVIDMSR 0xc0010071 0x30b200c3 0x38035c40 rs780_htinit cpu_ht_freq=b. rs780_htinit: HT3 mode ...WARM RESET...
coreboot-2.0.0-r623M_tilapia_fam10_Fallback Fri Oct 9 13:15:49 CST 2009 starting...
BSP Family_Model: 00100f42 *sysinfo range: [000cc000,000cf360] bsp_apicid = 00 cpu_init_detectedx = 00000000 microcode: equivalent rev id = 0x1041, current patch id = 0x00000000 microcode: patch id to apply = 0x01000086 microcode: updated to patch id = 0x01000086 success
cpuSetAMDMSR done Enter amd_ht_init() AMD_CB_EventNotify() event class: 05 event: 2006 data: 04 00 00 00 Exit amd_ht_init() cpuSetAMDPCI 00 done Prep FID/VID Node:00 F3x80: e600a681 F3x84: a0e641e6 F3xD4: c8810f26 F3xD8: 03001816 F3xDC: 00005322 Wait all core0s started Wait all core0s started done start_other_cores() init node: 00 cores: 03 Start other core - nodeid: 00 cores: 03 started ap apicid: cccooorrreeexxx::: --------- {{{ AAAPPPIIICCC IIIDDD === 000132 NNNOOODDDEEEIIIDDD === 000000 CCCOOORRREEEIIIDDD === 000123}} } ---------
APmmm isiitcccarrrroootccceooodddd:eee :::0 eee1qqqAuuuPiii vvvsaaatlllaeeernnntttte d rr:re cccvv0v 2 iiAiddPd s =t== a 0r00xtxx1e110d004:441 110,,,3 000000rrrrsrrr7eee8nnn0ttt_ epppaaaartttccclhhhy _iiisddde t===u p(000)xxx u 000g000e000t000_000c000p
tttev EAmmmiiXicc=c0rrroooxccc1ooo0ddd0eeef:::4 2ppp.aaa xxxcccChPhh U i iidRdd e tvtto ooi saaa pppKppp8lll_yyy1 0===. 000 t 000fa111m00000010000000_888o666p
immmmiiiicczcrrarootoccicooooddndee(e::): hhhuppprsddd7aaa8ttt0eeeddd_ ptttoooor _pppiaaanittttccc iiiddd === 000xxx000111000000000000888666 sssuuucccccceeessssss
cccpppuuuSSSeeetttAAAMMMDDDMMMSSSRRR
On Fri, Oct 9, 2009 at 12:10 AM, Bao, Zheng Zheng.Bao@amd.com 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.
Hi Zheng,
There has been a lot of work with CBFS and with Kconfig in the last few weeks. Myles and Patrick have been testing in system and in SimNow so it should work. Can you try updating your platform to use them?
Marc
Does it mean the buildtarget is obsolete?
Zheng
-----Original Message----- From: Marc Jones [mailto:marcj303@gmail.com] Sent: Friday, October 09, 2009 11:34 PM To: Bao, Zheng Cc: coreboot@coreboot.org Subject: Re: [coreboot] coreboot hangs on my AMD fam10 board.
On Fri, Oct 9, 2009 at 12:10 AM, Bao, Zheng Zheng.Bao@amd.com 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.
Hi Zheng,
There has been a lot of work with CBFS and with Kconfig in the last few weeks. Myles and Patrick have been testing in system and in SimNow so it should work. Can you try updating your platform to use them?
Marc
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
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
On Fri, Oct 9, 2009 at 7:16 PM, Carl-Daniel Hailfinger c-d.hailfinger.devel.2006@gmx.net wrote:
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}} } ---------
The stacks shouldn't be overlapping but the decompression location might (I havn't looked at the implementation yet). We may need to look at CBFS more closely wrt AP startup.
Marc
-
Bao, Zheng -
Carl-Daniel Hailfinger -
Marc Jones