-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I don't know if coreboot has support for differing CPUs in the same
mainboard; it's not something I can recall testing at any point.

The failure is occurring far before memory initialization, in CAR, in
core setup.  I'd guess it has something to do with the two CPUs you have
installed having different core counts.

Does the vendor BIOS print a message about the core count being limited
on one of the CPUs for compatibility reasons?

On 04/11/2018 12:57 PM, Elisenda Cuadros wrote:
> Hello,
> 
> After testing the board for some weeks I bought another CPU (6276). I
> installed this into CPU1 slot and a 6238 in CPU2.
> 
> I checked that both CPUs are shining and also the memory (Micron
> MT18JSF25672PDZ-1G4F1DD, populated in A2/C2/E2/G2 slots).
> 
> The problem is that Coreboot seems to hang at the beginning. I attach
> console.log.
> 
> I reinstalled all the devices twice, checked the vendor manual, docs in
> coreboot.org, messages in mailing list, but I don't know what is causing
> the problem.
> 
> Last test I've done is booting with vendor bios, and it boots without
> problem.
> 
> Any ideas?
> 
> Thank you for your help.
> 
> Regards,
> 
> - Eli
> 
> 
> 
> 


- -- 
Timothy Pearson
Raptor Engineering
+1 (415) 727-8645 (direct line)
+1 (512) 690-0200 (switchboard)
https://www.raptorengineering.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQEcBAEBAgAGBQJazleSAAoJEK+E3vEXDOFbrFcH/i6xBhUGli6lYBXFM4d29CW7
UH6Z1Ksr2bD5jNfoKd1bmLx61w0KdG6Fyt/AmFr4dNXmAxTzuudw1ZZxauZe21Sk
neJfuoMtctq/YQTaliMhPawO+6vARiVdNUYaMmDZO6cf4h9252WdpBU99JCJsbhC
BkcIApR+0resb6iO2XpbPelnMA4yjitpgonXqKbVI6OvdYz5b3NViytCKcHunyzc
7H/GzpS93K1hWs7kLdNCJ7J7M0BtUSh2pGu/uaqr1ZSXWZgwBeQGESMG7etpT1Ju
LP+e8C9dm0iLiTS8FIond8WUu4Q4bt7ebAqohrNQoMRpYlmyHWgEVSzecddqMJM=
=ke+3
-----END PGP SIGNATURE-----

-- 
coreboot mailing list: coreboot@coreboot.org
https://mail.coreboot.org/mailman/listinfo/coreboot

Reply via email to