Intel Xeon Platinum 8273CL Complete Info Guide

Notice: Page may contain affiliate links for which we may earn a small commission through services like Amazon Affiliates or Skimlinks.

dracocephalum

New Member
Sep 20, 2019
29
8
3
I have pretty much learned all these through the "hard way" a.k.a failures. Not pleasant experience, but for the sake of anyone who is still interested in this processor, I hope this thread can give out some info to avoid going through the same pain I had gone through.

Some background: I was trying to use this CPU in a 4-way configuration in a Supermicro 8049U-E1CR4T, without success. Here are some highlights:

1. Xeon 8273CL has been locked down to S2S (2-way) only

This is a dead end, well, at least for me. If you are trying to put 4x 8273CL on a X11QPH+, during POST it will stuck at BIOS code A3. This is a pretty mysterious code, and there are only few Supermicro Q&A mentioned this (e.g. FAQ Entry | Online Support | Support - Super Micro Computer, Inc.) Since I am using all same model CPUs rather than like mentioned in the Q&A, I believe this code has a more general meaning like "CPU layout configuration / init" stuff. Note that if you are using an older version of BIOS like 3.0a, it will stuck without display output. Newer BIOS like 3.8a/4.0 will report code A3. My initial suspect was something wrong with UPI connectivity, and confirmed that Intel has locked these 8273CL down to "S2S" (2-way) physically from the HWiNFO64 report, even though Platinum SKUs are usually "S8S".

Anyway, this is a show stopper for me - I wanted to use them in a 4-way configuration. End result was... returning the CPUs....:confused:

2. Xeon 8273CL requires special microcode revision (0x05000014)

I spent some time to play around with 2-way, since I believe others could be interested in this more common configuration. There are already a lot of posts mentioned that, with Supermicro motherboards, only 3.0a version of BIOS can work, and any older ones (e.g. I tried 3.0c) would result in POST stuck at code 79. I can confirm this is the same for X11QPH+.

The interesting thing is, I extracted the microcode from BIOS 3.0a (e.g. cpu50657_platBF_ver05000014_2018-12-17_PRD_E1FFC46B) and injected it to BIOS 4.0, and the modded BIOS worked fine. So obviously the code 79 issue was caused by microcode rather than other content in the BIOS. I think this is relatively a good news, because even we have to use an older revision of microcode, we can use any version of BIOS we want in Suprtmicro systems, which can guarantee at least other modules, such as ME / UEFI drivers etc. are the up to date.

If you look closely at those microcode files, you can see that the microcode files would "shrink" in size from time to time, which looks like Intel was "purging" something from the microcode files. I suspect that Intel had put everything, including support of OEM CPUs, into the initial microcode, but a while later (e.g. BIOS v3.0b/c) Intel purged these OEM specific support from their newer version of microcode files. Therefore later versions of BIOS in Supermicro systems can no longer spin up those OEM CPUs properly, causing code 79 stuck. This could be applicable to other CPUs like 8272CL / 8275CL etc. as well.

Code:
...
cpu50657_platBF_ver05000013_2018-12-03_PRD_3B5B26B8 => 48KB
cpu50657_platBF_ver05000014_2018-12-17_PRD_E1FFC46B => 48KB
cpu50657_platBF_ver05000021_2019-02-27_PRD_14AE68DF => 46KB
...
cpu50657_platBF_ver05003006_2020-12-31_PRD_B36FD6DE => 52KB
cpu50657_platBF_ver05003101_2021-01-15_PRD_40827521 => 30KB
...
This has an interesting implication: 8273CL could theoretically work with ANY motherboard! As long as the correct microcode present in the BIOS, I think 8273CL at least can work nicely with any Supermicro systems in 1-way/2-way.

UPDATE: thanks @RolloZ170 confirming that 0x0500001C can also work, see replies below.

3. 8237CL is optimized for Machine Learning and has a higher AVX2/AVX512 clock than 8276L under full load


We often compare 8273CL with 8276L as they are really close in terms of specs. I once was wondering why the lower CPU clock compare to 8276L, besides it could be from a lower bin. It turns out that under 28-core 100% workload, 8273CL has a slightly higher AVX2/AVX512 clock than 8276L, which is obviously tuned for Machine Learning workload. See attached HWiNFO64 report. (comparing to 8276L data: Xeon Platinum 8276L - Intel - WikiChip)

4. Microcode revision 0x05000014 or 0x05003003 !?!?

I noticed that in the HWiNFO64 report, the actual detected microcode was 0x5003003, which is a bit surprising, because I believe the microcode I injected into the BIOS must be 0x05000014. I guess it could be either of the following:
  1. Windows has loaded 0x5003003 microcode after startup. Operating systems can dynamically load microcode after POST, so I think to fix critical issues, Windows has patched the microcode because verison 0x05000014 was simply too old. This is also a bit confusing because I can't explain why 0x5003003 would cause code 79 stuck during POST. Could it be once the 8273CL CPU has gone past POST, then newer microcode can work? If so, then this CPU can potentially be used in production, e.g. we use older microcode 0x05000014 to start the machine, then once OS is loaded, we further patch the CPU with latest microcode like 0x05003604...via tools like this => VMware CPU Microcode Update Driver
  2. I possibly did put 0x5003003 int he BIOS..... !? I don't know, maybe you can try that out yourself if you are feeling adventurous :)
 

Attachments

Last edited:

RolloZ170

Well-Known Member
Apr 24, 2016
6,721
2,075
113
This could applicable to other CPUs like 8272CL / 8275CL etc.
no. afaik only 8273CL affected.
update on this:
Platinum 8259CL: is working but huge performance loss with microcodes later than 500001C
I noticed that in the HWiNFO64 report, the actual detected microcode was 0x5003003, which is a bit surprising, because I believe the microcode I injected into the BIOS must be 0x05000014
Windows has loaded 0x5003003 microcode after startup
Plat 8273CL HWinfo MCU after.jpg
you can investigate the actual loaded MC in the BIOS.
 
Last edited:

RolloZ170

Well-Known Member
Apr 24, 2016
6,721
2,075
113
2. Xeon 8273CL requires special microcode revision (0x05000014)
we have tested the following BIOS rev with X11SPA-TF

BIOS 3.0b MCU B1 rev 500001C - working ( unofficial BIOS from supermicro support )
BIOS 3.0c MCU B1 rev 5000021 - not working, code 79 ( unofficial BIOS from supermicro support )
BIOS 3.5 MCU B1 rev 5003103 - not working, code 79
 

dracocephalum

New Member
Sep 20, 2019
29
8
3
we have tested the following BIOS rev with X11SPA-TF

BIOS 3.0b MCU B1 rev 500001C - working ( unofficial BIOS from supermicro support )
BIOS 3.0c MCU B1 rev 5000021 - not working, code 79 ( unofficial BIOS from supermicro support )
BIOS 3.5 MCU B1 rev 5003103 - not working, code 79
hmmm, so looks like the max. point would be 500001C, then starting from 5000021 something must be changed.
 

computably

New Member
Aug 8, 2022
26
11
3
Actually regarding microcode, any clues on how to detect what is the microcode version of a Dell BIOS? They're packaged only as a single .exe file unfortunately so I've no idea how to unpack it.

I'm trying to get a 6268CL to work with a Dell 7920, and if the requirement is actually that the BIOS have an older microcode, maybe that was the issue? Mine came with 2.4.1: https://www.dell.com/support/home/e...=biosa&productcode=precision-7820-workstation but the oldest one that I could consider using is 2.3.1: https://www.dell.com/support/home/e...=biosa&productcode=precision-7820-workstation since I am planning to use Optane pmem. I do see 2.4.1 is fixing a bunch of Intel's security vulnerabilities so that might be an indication of a microcode update...?
 

RolloZ170

Well-Known Member
Apr 24, 2016
6,721
2,075
113
I'm trying to get a 6268CL to work with a Dell 7920, and if the requirement is actually that the BIOS have an older microcode, maybe that was the issue?
maybe, just a guess. will be make sense.
all of these should work.
7X20T_2.1.4.exe => 0x500001C
7X20T_2.0.5.exe => 0x500001C
7X20T_2.0.4.exe => 0x500001C
but 7X20T_2.3.1 NOT, microcode rev too high.
 
  • Like
Reactions: computably

computably

New Member
Aug 8, 2022
26
11
3
OK, looks like 2.4.1 has 500002B so there actually was a microcode update... But if 2.3.1's microcode is already too high, then I'm a bit stuck. It sounds like it might be possible to patch 2.3.1 with the older microcode? However I don't know if newer microcode is necessary for Optane DCPMM support.
 

dracocephalum

New Member
Sep 20, 2019
29
8
3
However I don't know if newer microcode is necessary for Optane DCPMM support.
I think older micro code should work with DCPMM, but it is more about the BIOS feature that Dell provides e.g. even the microcode supports DCPMM, if you cannot manage the DCPMM via BIOS, then you can't create namespace etc., I guess....

Not sure if Dell BIOS could be modded though.... not too much info on the web about this topic.... >_<
 

computably

New Member
Aug 8, 2022
26
11
3
Well, I'd like to validate the 6268CL I already got, so if I can do at least that before my eBay return window ends that's something. :)

My plan B was getting an HP z6/z8 g4. At least it seems it should be easier to get it working as I've seen several scattered reports on benchmark sites with 6258CL/6253CL on z6/z8. Now I guess I'll have to also investigate if there's an HP BIOS which both supports DCPMM and has the older microcode.