[coreboot] H8QME-2+ boot problems on different machines.

Knut Kujat knuku at gap.upv.es
Wed Apr 28 13:31:01 CEST 2010


Hi,

I have a strange problem trying to install/flash my Coreboot to several
machines in the cluster some worked just fine and other hang at a really
early moment.
The machines are identical: H8QME-2+ with 16 GB RAM and 4 quadcore AMD
Opterons 8350.

I guess that from the point where it hangs that it must be some kind of
CPU issue (I haven't switched CPUs yet).

here the serial output:

coreboot-4.0-r5224M Wed Apr 28 12:50:59 CEST 2010 starting...

BSP Family_Model: 00100f22
*sysinfo range: [000cc000,000cdfa0]
bsp_apicid = 00
cpu_init_detectedx = 00000000
After Set_sysinfo_in_ram
microcode: equivalent rev id  = 0x1022, current patch id = 0x00000000
microcode: patch id to apply = 0x01000095
microcode: updated to patch id = 0x01000095  success

After update_microcode
cpuSetAMDMSR  done
After cpuSetAMDMSR
Enter amd_ht_init()
AMD_CB_EventNotify()
 event class: 05
 event: 1004
 data:  04  00  00  01
AMD_CB_EventNotify()
 event class: 05
 event: 1004
 data:  04  00  01  02
AMD_CB_EventNotify()
 event class: 05
 event: 1004
 data:  04  01  01  03
AMD_CB_ManualBUIDSwapList()
AMD_CB_EventNotify()
 event class: 05
 event: 2006
 data:  04  00  02  ff
AMD_CB_ManualBUIDSwapList()
AMD_CB_EventNotify()
 event class: 05
 event: 2006
 data:  04  01  02  00
Exit amd_ht_init()
After amd_ht_init
cpuSetAMDPCI 00 done
cpuSetAMDPCI 01 done
cpuSetAMDPCI 02 done
cpuSetAMDPCI 03 done
Prep FID/VID Node:00
  F3x80: e600a681
  F3x84: a0e641e6
  F3xD4: c3310f24
  F3xD8: 03001815
  F3xDC: 00005428
Prep FID/VID Node:01
  F3x80: e600a681
  F3x84: a0e641e6
  F3xD4: c3310f24
  F3xD8: 03001815
  F3xDC: 00005428
Prep FID/VID Node:02
  F3x80: e600a681
  F3x84: a0e641e6
  F3xD4: c3310f24
  F3xD8: 03001815
  F3xDC: 00005428
Prep FID/VID Node:03
  F3x80: e600a681
  F3x84: a0e641e6
  F3xD4: c3310f24
  F3xD8: 03001815
  F3xDC: 00005428
setup_remote_node: 01 done
Start node 01 done.
se tucpor_ere0:mo t e--_-no {de    : A 0PI2C IdoDn =e
0S4 tNarODt EnIDod =e  0012  dCOoRnEeI. Dc
or=see 00t0u: }p _ -r---e-m- o{t
    emi _cnAProIdocCeo:IDd 0e =3:   ed08oqu nieNOvD
alESetIDna rt =tr  0en2ov d iCed OR 0E3 =I Dd  o0=nx1 e c.0020o2
}re,A -0 fct-: ue- rrr
--efmi-nicn t{ ra    lpoc iatzoAPcedeIh_:nC Ii oDddeq e u_== is
e0v0ctxal u00peNO0ntD0
0 EArIF00eDT0Ev =R i
 d 0m si3  ecrtC= ouOR0cpo_Ex1dmID0eb _2:2 =r,ep 0 sato0cucu} rhr-cr
ei-end-t
 tM
 poema sicstaprcapgoh leco iy dAd =e=
 :0  Mxee0x0squs010ia000vg0e0a0l0 90e0052nt0
 

rMmeeimiscvcsr oiracgdo coe  ode=0de: 30: ux
 pp1M0eada2stct2shae,d  g ecidt ur0 o r4tope
anttaMce pphspasl itay dcg=e h=    0i0x04d b0x0=101
0M000x0e0s0090s00a5950g
 0e  0m0is004curccoc
c
emioMsscdesreo:
sca
ogupdece dpu:0atS 4edeptadA
t tMMcheoDM s psSidaaR  tgcet d oh  o0a5inepd p


Can someone please give me an advice on even how to start to narrow down
the problem? I already started to put a 0 in Config Logical CPUs but no
changes. :(

Thx,

Knut Kujat.






More information about the coreboot mailing list