Hi Kyösti,
I will try to boot again with 6276+6238 with the current build and I
will inform the result.
Regards,
- Eli
On 03/05/18 20:07, Kyösti Mälkki wrote:
> On Thu, May 3, 2018 at 8:57 PM, Elisenda Cuadros wrote:
>> Finally I acquired another 6276 CPU (it was the fastest and cheapest
>>
On Thu, May 3, 2018 at 8:57 PM, Elisenda Cuadros wrote:
> Finally I acquired another 6276 CPU (it was the fastest and cheapest
> option).
>
> It works perfect.
>
Maybe not related, but KGPE-D16 was affected by a regression [1] on
SMP init. That was present on master from Aug 2017 to Apr 2018.
[1
Finally I acquired another 6276 CPU (it was the fastest and cheapest
option).
It works perfect.
If I can try (in the future) another different 16-core CPU, I will
report the result.
Thank you for you kind support.
Regards,
- Eli
On 11/04/18 21:30, Timothy Pearson wrote:
> This may be a genera
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
That should work, yes. It's the very early init code that is getting
confused with the differing core counts, likely related to APIC setup or
similar.
On 04/11/2018 03:26 PM, taii...@gmx.com wrote:
> But it would be possible to have two CPU's with th
But it would be possible to have two CPU's with the same core count but
differing frequencies?
Thanks
0xDF372A17.asc
Description: application/pgp-keys
--
coreboot mailing list: coreboot@coreboot.org
https://mail.coreboot.org/mailman/listinfo/coreboot
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
This may be a general coreboot limitation at the moment. The
compatibility sections for mixed CPUs in the BKDG are more concerned
with total power delivery and proper P-state setup than anything else.
If I recall correctly, coreboot assumes both CPUs
Thank you for your reply Timothy.
Vendor Bios doesn't print any special message regarding this.
In fact it shows a total of 28 cores (16+12).
I thought mixing CPUs from same families was supported.
Regards,
- Eli
On 11/04/18 20:44, Timothy Pearson wrote:
> I don't know if coreboot has support
-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 wi
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
9 matches
Mail list logo
