<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
Finally I acquired another 6276 CPU (it was the fastest and cheapest
option).<br>
<br>
It works perfect.<br>
<br>
If I can try (in the future) another different 16-core CPU, I will
report the result.<br>
<br>
Thank you for you kind support.<br>
<br>
Regards,<br>
<br>
- Eli<br>
<br>
On 11/04/18 21:30, Timothy Pearson wrote:<br>
<blockquote type="cite">This may be a general coreboot limitation at
the moment. The<br>
compatibility sections for mixed CPUs in the BKDG are more
concerned<br>
with total power delivery and proper P-state setup than anything
else.<br>
<br>
If I recall correctly, coreboot assumes both CPUs have the same
core<br>
count when setting up APICs and such. There are a number of
places that<br>
would need to be modified to remove this assumption; it's a
leftover<br>
from the original K8 code and would take some significant work to
fix.<br>
This also needs to be verified as I am going from memory here from
a<br>
couple of years ago.<br>
<br>
On 04/11/2018 02:12 PM, Elisenda Cuadros wrote:<br>
> Thank you for your reply Timothy.<br>
<br>
> Vendor Bios doesn't print any special message regarding this.<br>
<br>
> In fact it shows a total of 28 cores (16+12).<br>
<br>
> I thought mixing CPUs from same families was supported.<br>
<br>
> Regards,<br>
<br>
> - Eli<br>
<br>
> On 11/04/18 20:44, Timothy Pearson wrote:<br>
>> I don't know if coreboot has support for differing CPUs
in the same<br>
>> mainboard; it's not something I can recall testing at any
point.<br>
>><br>
>> The failure is occurring far before memory
initialization, in CAR, in<br>
>> core setup. I'd guess it has something to do with the
two CPUs you have<br>
>> installed having different core counts.<br>
>><br>
>> Does the vendor BIOS print a message about the core count
being limited<br>
>> on one of the CPUs for compatibility reasons?<br>
>><br>
>> On 04/11/2018 12:57 PM, Elisenda Cuadros wrote:<br>
>>> Hello,<br>
>><br>
>>> After testing the board for some weeks I bought
another CPU (6276). I<br>
>>> installed this into CPU1 slot and a 6238 in CPU2.<br>
>><br>
>>> I checked that both CPUs are shining and also the
memory (Micron<br>
>>> MT18JSF25672PDZ-1G4F1DD, populated in A2/C2/E2/G2
slots).<br>
>><br>
>>> The problem is that Coreboot seems to hang at the
beginning. I attach<br>
>>> console.log.<br>
>><br>
>>> I reinstalled all the devices twice, checked the
vendor manual, docs in<br>
>>> coreboot.org, messages in mailing list, but I don't
know what is causing<br>
>>> the problem.<br>
>><br>
>>> Last test I've done is booting with vendor bios, and
it boots without<br>
>>> problem.<br>
>><br>
>>> Any ideas?<br>
>><br>
>>> Thank you for your help.<br>
>><br>
>>> Regards,<br>
>><br>
>>> - Eli<br>
>><br>
>><br>
>><br>
>><br>
>><br>
>><br>
<br>
<br>
<br>
<br>
</blockquote>
<span style="white-space: pre-wrap; display: block; width: 98vw;">>
</span><br>
<br>
</body>
</html>