VOGONS


Anomalies in the Intel® Processor Specification Updates

Topic actions

Reply 200 of 220, by red-ray

User metadata
Rank Oldbie
Rank
Oldbie
PARKE wrote on 2025-06-18, 09:28:

I can't find relevant/thrustworthy info on these L2's.

All the Sandy Bridge-EP are <n> * 256KB where <n> is the number of cores just like all the Sandy Bridge-E. Would you like me to post several SIV screen shots that prove this?

SLB5G E0 01067Ah 2.27GHz/1066MHz Core 2 Mobile Penryn 2 x 6MB m-FCPGA 45 1066 2266.00 Intel Spec Update 32012108.pdf 14,15,16
SLB5J E0 01067Ah 2.53GHz/1066MHz Core 2 Mobile Penryn 2 x 6MB m-FCPGA 45 1066 2533.00 Intel Spec Update 32012108.pdf 14,15,16

In the above 2 Penryn should be Penryn-QC, see https://en.wikipedia.org/wiki/List_of_I ... 22_(45_nm)

I think 1 x 256KB/1x256KB are silly and should just be 256KB, do you or should I teak the parsing?

I have adjusted the L2/L3 parsing and think all the issues are in your data.

I know you don't have Pentium, what do you wish to do about SL23X? https://www.cpu-world.com/sspec/SL/SL23X.html says Pentium

file.php?id=221801

Reply 201 of 220, by PARKE

User metadata
Rank Oldbie
Rank
Oldbie

I believe you on your word; all the stuff you mentioned is updated/corrected.

I found a table with Pentiums that I once made. How is your format of the CPUID ?

Reply 202 of 220, by red-ray

User metadata
Rank Oldbie
Rank
Oldbie
PARKE wrote on 2025-06-18, 10:46:

How is your format of the CPUID ?

I am unclear as to what you are asking, the i486 + Pentium + PentiumPro CPUID is the same as all other CPUIDs.

Please may I have the corrected file as it's easier for my testing when there are fewer issues.

red-ray wrote on 2025-06-17, 00:40:

Mobile Pentium 4 533MHz fsb should have Prescott

I made a typo, Mobile Pentium 4 533MHz fsb should have Northwood

Last edited by red-ray on 2025-06-18, 11:45. Edited 2 times in total.

Reply 203 of 220, by PARKE

User metadata
Rank Oldbie
Rank
Oldbie
red-ray wrote on 2025-06-18, 11:01:
I am unclear as to what you are asking, the i486 + Pentium + PentiumPro CPUID is the same as all other CPUIDs. Please may I hav […]
Show full quote
PARKE wrote on 2025-06-18, 10:46:

How is your format of the CPUID ?

I am unclear as to what you are asking, the i486 + Pentium + PentiumPro CPUID is the same as all other CPUIDs.
Please may I have the corrected file as it's easier for my testing when there are fewer issues.

red-ray wrote on 2025-06-17, 00:40:

Mobile Pentium 4 533MHz fsb should have Prescott

I made a typo, Mobile Pentium 4 533MHz fsb should have Northwood

The Pentium CPUID info is divided over three single digit columns: type, family and model. Should they be joined plus with a zero in front and an 'h' behind it ?

Do you have a L2 ' key' for the Sandy Bridge-EN ?

Reply 204 of 220, by red-ray

User metadata
Rank Oldbie
Rank
Oldbie

Five more, maybe the last five for existing entries!

Mobile Pentium 2 + CPUID 065n should have Tonga, see https://en.wikipedia.org/wiki/Pentium_II#Tonga
Mobile Pentium 2 + CPUID 066n should have Dixon, see https://en.wikipedia.org/wiki/Pentium_II#Dixon
Core 2 Mobile Extreme should have Penryn
Core 2 Mobile should have Penryn
Pentium Dual-Core E2000 should have Allendale, https://www.cpu-world.com/sspec/SL/SLA3H.html

PARKE wrote on 2025-06-18, 11:40:

The Pentium CPUID info is divided over three single digit columns: type, family and model. Should they be joined plus with a zero in front and an 'h' behind it ?

Do you have a L2 ' key' for the Sandy Bridge-EN ?

for CPUID TFMS then T is type, F is family, M is model and S is stepping number. If you wish to add h then do so, attached are a few.

Sandy Bridge-EN is the same as Sandy Bridge-EP, the same is also the case for Ivy Bridge-E/EN/EP/EX + Haswell-E/EN/EP/EX + Broadwell-E/EN/EP/EX

Reply 205 of 220, by PARKE

User metadata
Rank Oldbie
Rank
Oldbie

Intel's naming convention is pretty crazy. If the car industry had followed the same system we would by now have Chevrolet Corvettes with 20+ different fish names.

The attachment SIV18-6-2.txt is no longer available

Reply 206 of 220, by red-ray

User metadata
Rank Oldbie
Rank
Oldbie
PARKE wrote on 2025-06-18, 12:29:

Intel's naming convention is pretty crazy. If the car industry had followed the same system we would by now have Chevrolet Corvettes with 20+ different fish names.

Thank you, the car industry is much the same, looking at https://en.wikipedia.org/wiki/Ford_Cortina#:~ … 20door%20models. there is

Engine
1.2 L "Kent" I4
1.3 L "Kent" I4
1.3 L Crossflow I4
1.5 L Kent I4
1.6 L "Crossflow" I4
1.6 L Twin-Cam I4
2.5 L Essex V6
3.0 L Essex V6

Then you get onto the GXL, GT, Ghia, ... suffixes

Reply 207 of 220, by red-ray

User metadata
Rank Oldbie
Rank
Oldbie
red-ray wrote on 2025-06-18, 11:49:
Mobile Pentium 2 + CPUID 065n should have Tonga, see https://en.wikipedia.org/wiki/Pentium_II#Tonga Mobile Pentium 2 + CPUID 066 […]
Show full quote

Mobile Pentium 2 + CPUID 065n should have Tonga, see https://en.wikipedia.org/wiki/Pentium_II#Tonga
Mobile Pentium 2 + CPUID 066n should have Dixon, see https://en.wikipedia.org/wiki/Pentium_II#Dixon
Core 2 Mobile Extreme should have Penryn
Core 2 Mobile should have Penryn
Pentium Dual-Core E2000 should have Allendale, https://www.cpu-world.com/sspec/SL/SLA3H.html

It's getting close again:

Why is there a space in SL9VA(1 )?
SLBN3 should be 2009, see https://en.wikipedia.org/wiki/List_of_I ... 22_(45_nm)
SLBQK as far as I can tell this does not exist.
SR070 should be Q0, see https://en.wikipedia.org/wiki/List_of_I ... processor) + https://www.cpu-world.com/sspec/SR/SR070.html
SR0G0 is CPUID 0206A7, https://en.wikipedia.org/wiki/List_of_I ... processor) says [D2] which is CPUID 0206A7.
SR3L2 has a typo, 13,75MB should be 13.75MB

I feel you should add these
[Check CPU S-Spec] <- SIV32L - System Information Viewer V5.82 Beta-04 RED::ray

SIV32L - Checkout of S-Spec on \\RED - Windows 10 x64 Enterprise V10.00 Build 19045 22H2

CPUID Processor S-Spec Expected Actual CPUID Reason Description

0650 Deschutes-266 [dA0] SL2QE Pentium II 512K @ 512M - Unknown
06A4 Cascades-900 [B0] QAK9 Pentium III Xeon 2M @ 64G - Unknown
0680 Coppermine-500 [cA0] SL3US Pentium IIIE 256K - Unknown
0683 Coppermine-700 [B0] SL4EG Intel Celeron 128K - Unknown
068A Coppermine-766 [D0] SL5EA Intel Celeron 128K - Unknown
06B1 Tualatin-1200 [A1] QHF3 Intel Celeron 256K - Unknown
06B4 Tualatin-1133 [tB1] SL6C4 Pentium III 256K - Unknown
06B4 Tualatin-1200 [tB1] SL6C3 Pentium III 256K - Unknown
06B4 Tualatin-1333 [tB1] SL6BZ Pentium III 256K - Unknown
06B4 Tualatin-1400 [tB1] SL6C2 Pentium III 256K - Unknown
06F6 Merom-1600 [B2] QVMC Intel Celeron 500 M 1M - Unknown
10661 Merom-2266 [A1] SLA2C Intel Celeron 500 P 1M - Unknown
0F25 Gallatin-3200 [M0] SL7GC Pentium 4 512K + 2M - Unknown
0F25 Gallatin-3400 [M0] SL7RR Pentium 4 512K + 2M - Unknown
0F27 Northwood-2500 [C1] SL6EB Pentium 4 512K - Unknown
0F27 Northwood-2500 [C1] SL6GT Pentium 4 512K - Unknown
0F27 Northwood-2600 [C1] SL6GU Pentium 4 512K - Unknown
0F27 Northwood-2600 [C1] SL6HB Pentium 4 512K - Unknown
0F27 Northwood-2666 [C1] SL6DX Pentium 4 512K - Unknown
0F27 Northwood-2666 [C1] SL6EH Pentium 4 512K - Unknown
0F29 Northwood-2500 [D1] SL6PN Pentium 4 512K - Unknown
0F29 Northwood-3200 [D1] SL792 Pentium 4 512K - Unknown
0F29 Northwood-3400 [D1] SL7KV Pentium 4 512K - Unknown
0F47 Smithfield-3200 [B0] SL8FJ Pentium Extreme 2 x 1M - Unknown
0F65 Presler-3466 [D0] SL9K6 Pentium Extreme 2 x 2M - Unknown
0F48 Paxville-3000 [A0] QHBB Intel Xeon 2 x 2M - Unknown
06E8 Yonah-1500 [C0] SL92C Intel Core Solo 2M - Unknown
06E8 Yonah-1733 [C0] SL99U Intel Core Solo 2M - Unknown
06E8 Yonah-2000 [C0] SL92W Intel Core Solo 2M - Unknown
06E8 Yonah-1600 [C0] SL9BN Intel Core Duo 2M - Unknown
06FD Merom-2000 [M0] QGFV Intel Core 2 Duo M 2M - Unknown
06FD Merom-2000 [M0] SLAXH Intel Core 2 Duo M 2M - Unknown
10676 Penryn-1400 [M0] SLGHN Intel Core 2 Duo M 3M - Unknown
1067A Penryn-1300 [R0] SLGS6 Intel Core 2 Duo M 3M - Unknown
1067A Penryn-1300 [R0] SLGYV Intel Core 2 Duo M 3M - Unknown
1067A Penryn-1600 [R0] SLGEX Intel Core 2 Duo M 3M - Unknown
1067A Penryn-QC-2000 [E0] SLGEJ Intel Core 2 Quad M 2 x 3M - Unknown
10676 Yorkfield-2500 [M0] SLAMX Intel Core 2 Quad 2 x 3M - Unknown
10676 Yorkfield-2666 [C0] SLAN6 Intel Core 2 Quad 2 x 6M - Unknown
10676 Yorkfield-2833 [C0] SLAN4 Intel Core 2 Quad 2 x 6M - Unknown
10676 Yorkfield-3200 [C0] SLAN2 Intel Core 2 Quad 2 x 6M - Unknown
10677 Yorkfield-3000 [C1] SLAWN Intel Core 2 Quad 2 x 6M - Unknown
1067A Yorkfield-3166 [E0] SLBBU Intel Core 2 Quad 2 x 6M - Unknown
06E8 Sossaman-2166 [C0] SL9HM Intel Xeon 2M - Unknown
06F7 Clovertown-3000 [B3] SLAC3 Intel Xeon 2 x 4M - Unknown
06FB Clovertown-3000 [G0] SLAED Intel Xeon 2 x 4M - Unknown
106A4 Bloomfield-2666 [C0] SLBCH Core i7 4 x 256K + 8M - Unknown
106A4 Bloomfield-2933 [C0] SLBCK Core i7 4 x 256K + 8M - Unknown
106A4 Bloomfield-3200 [C0] SLBCJ Core i7 4 x 256K + 8M - Unknown
106A5 Bloomfield-2666 [D0] SLBEJ Core i7 4 x 256K + 8M - Unknown
106A5 Bloomfield-2800 [D0] SLBKP Core i7 4 x 256K + 8M - Unknown
106A5 Bloomfield-3066 [D0] SLBEN Core i7 4 x 256K + 8M - Unknown
106A5 Bloomfield-3200 [D0] SLBEU Core i7 4 x 256K + 8M - Unknown
106A5 Bloomfield-3333 [D0] SLBEQ Core i7 4 x 256K + 8M - Unknown
Show last 20 lines
206C2  Gulftown-3200 [B1]         SLBVF                                                                Core i7 970 6 x 256K + 12M - Unknown
206C2 Gulftown-3333 [B1] SLBUZ Core i7 980X 6 x 256K + 12M - Unknown
206C2 Gulftown-3333 [B1] SLBYU Core i7 980 6 x 256K + 12M - Unknown
206C2 Gulftown-3466 [B1] SLBVZ Core i7 990X 6 x 256K + 12M - Unknown
906E9 Kaby Lake-X-4000 [B0] SR3FR Core i5 7640X 4 x 256K + 6M - Unknown
906E9 Kaby Lake-X-4300 [B0] SR3FP Core i7 7740X 4 x 256K + 8M - Unknown
206C2 Westmere-3200 [B1] SLC2E Xeon 5600 6 x 256K + 12M - Unknown
206D7 Sandy Bridge-EP-2800 [M1] SR0RM Xeon E5-1 4 x 256K + 10M - Unknown
206D7 Sandy Bridge-EP-1800 [C2] SR0JW Xeon E5-1 6 x 256K + 15M - Unknown
206D7 Sandy Bridge-EP-1800 [C2] SR0JV Xeon E5-2 6 x 256K + 15M - Unknown
206D7 Sandy Bridge-EP-1800 [C2] SR0JU Xeon E5-2 8 x 256K + 20M - Unknown
206D7 Sandy Bridge-EP-1400 [C2] SR0R1 Xeon E5-2 8 x 256K + 20M - Unknown
206D7 Sandy Bridge-EP-1800 [M1] SR0M1 Xeon E5-2 4 x 256K + 10M - Unknown
206D6 Sandy Bridge-EP-2100 [C1] SR0HG Xeon E5-2 8 x 256K + 20M - Unknown
206D6 Sandy Bridge-EP-2400 [C1] SR0HB Xeon E5-2 8 x 256K + 20M - Unknown
206D6 Sandy Bridge-EP-2600 [C1] SR0HD Xeon E5-2 8 x 256K + 20M - Unknown
206D6 Sandy Bridge-EP-3100 [C1] SR0GX Xeon E5-2 8 x 256K + 20M - Unknown
206D6 Sandy Bridge-EP-1800 [C1] SR0HE Xeon E5-2 8 x 256K + 20M - Unknown
206D7 Sandy Bridge-EP-1800 [C2] SR0LY Xeon E5-2 6 x 256K + 15M - Unknown
206D7 Sandy Bridge-EP-2600 [C2] SR0L6 Xeon E5-2 8 x 256K + 20M - Unknown

file.php?id=221813

Last edited by red-ray on 2025-06-19, 07:24. Edited 1 time in total.

Reply 208 of 220, by red-ray

User metadata
Rank Oldbie
Rank
Oldbie

I was only 99.42% sure the Paxville-3000 QHBB information was correct so I played "musical CPUs" and and am now 100% sure.

file.php?id=221827

I think this is the first time I have booted when sine 2011!, the system usually has 4 x SL9HA.

Last edited by red-ray on 2025-06-19, 06:36. Edited 1 time in total.

Reply 209 of 220, by H3nrik V!

User metadata
Rank Oldbie
Rank
Oldbie
red-ray wrote on 2025-06-18, 20:47:

I think this is the first time I have booted when sine 2011!, the system usually has 4 x SL9HA.

How cool it would be if vogons formatted sSpecs as hyperlinks to CPU-world, as CPU-world does ... 😀

[edit] Posted this in the “New forum suggestions/Feedback” thread as well ...

If it's dual it's kind of cool ... 😎

--- GA586DX --- P2B-DS --- BP6 ---

Please use the "quote" option if asking questions to what I write - it will really up the chances of me noticing 😀

Reply 210 of 220, by PARKE

User metadata
Rank Oldbie
Rank
Oldbie
red-ray wrote on 2025-06-18, 13:21:
It's getting close again: cut>< I feel you should add these[ SIV32L - Checkout of S-Spec on \\RED - Windows 10 x64 Enterprise V […]
Show full quote

It's getting close again:
cut><
I feel you should add these[
SIV32L - Checkout of S-Spec on \\RED - Windows 10 x64 Enterprise V10.00 Build 19045 22H2
CPUID Processor S-Spec Expected Actual CPUID Reason Description

Yes, it looks ok, thanks again.
Adding more does not appeal to me, I feel I have already gone to deep into the rabbit hole. This simple format does not support the more complex data of the later generations- that is probably also the reason why the Intel update sheets seem to become more deplete with the quad cores.
And I really feel that some of the older listings at the top of your list never made it into the wild read: existed only on paper.

Reply 211 of 220, by red-ray

User metadata
Rank Oldbie
Rank
Oldbie
H3nrik V! wrote on 2025-06-19, 06:01:

How cool it would be if vogons formatted sSpecs as hyperlinks to CPU-world, as CPU-world does ... 😀

It's easy enough to add links, I was just lazy.

I would really like to get SIV to link to CPU World, I added the code, but CPU World blocked the access !, see https://www.cpu-world.com/forum/viewtopic.php … p=329193#329193

Reply 212 of 220, by H3nrik V!

User metadata
Rank Oldbie
Rank
Oldbie
red-ray wrote on 2025-06-19, 06:50:
H3nrik V! wrote on 2025-06-19, 06:01:

How cool it would be if vogons formatted sSpecs as hyperlinks to CPU-world, as CPU-world does ... 😀

It's easy enough to add links, I was just lazy.

I would really like to get SIV to link to CPU World, I added the code, but CPU World blocked the access !, see https://www.cpu-world.com/forum/viewtopic.php … p=329193#329193

I know, but on cpu-world it's done automagically. And I'm aware of the fact that external linking to a high extend is blocked, hence "How cool it would be" 😉

If it's dual it's kind of cool ... 😎

--- GA586DX --- P2B-DS --- BP6 ---

Please use the "quote" option if asking questions to what I write - it will really up the chances of me noticing 😀

Reply 213 of 220, by red-ray

User metadata
Rank Oldbie
Rank
Oldbie
PARKE wrote on 2025-06-19, 06:35:

Adding more does not appeal to me, I feel I have already gone to deep into the rabbit hole. This simple format does not support the more complex data of the later generations- that is probably also the reason why the Intel update sheets seem to become more deplete with the quad cores.

I am not talking about earlier or later generations only filling in the gaps. Below are the 97 S-Specs that fall into this category and AFAIK most of them exist. SIV has 546 that are either pre Pentium-II or Ivy Bridge-EP or later and are a different matter.

I would like to have a screen with just the 15 duplicate s-spec listed.

The lack of data in later Intel S-Spec updates is really Intel becoming more secretive, later datasheets also have way less information than they used to have.

file.php?id=221845

Reply 214 of 220, by red-ray

User metadata
Rank Oldbie
Rank
Oldbie

I have added a new panel which currently reports:

file.php?&id=221859

I feel the titles in your file could/should be improved.
Speeds such as 2266.00 clearly should be 2266.66.
There are lots of s-specs similar to PMF26602001AA, AFAIK these are not s-specs, what are they? SIV just ignores them.
Using this panel I added the few that I think exist that SIV did not have and SIV now reports:

file.php?id=221857

The raw data for the new additions is:

SLBNL C2 020652h 1.87GHz Pentium P4000 2MB PGA 35 Intel Spec Update 32445617US.pdf 1,3,4,6,7,8
SLBUX K0 020655h 2GHz Pentium P4000 2MB PGA 35 Intel Spec Update 32445617US.pdf 1,3,4,6,7,8
SLBZY K0 020655h 2GHz Pentium P4000 2MB PGA 35 Intel Spec Update 32445617US.pdf 1,3,4,6,7,8
SLBSM K0 020655h 1.33GHz Mobile U5000 3MB BGA 18 Intel Spec Update 32387408.pdf ultra low voltage 1,4,5,6,7
SLBUH K0 020655h 1.2GHz Mobile U5000 3MB BGA 18 Intel Spec Update 32387408.pdf ultra low voltage 1,4,5,6,7
Q4CT K0 020655h 2.27GHz Pentium P6000 3MB PGA 35 Intel Spec Update 32387408.pdf 2,3,5,6,8
SLBU8 K0 020655h 2.27GHz Pentium P6000 3MB PGA 35 Intel Spec Update 32387408.pdf 2,3,5,6,8
SLBWB C2 020652h 1.87GHz Pentium P6000 3MB PGA 35 Intel Spec Update 32387408.pdf 2,3,5,6,8

I noted:

They should all have Arrandale.
All the Arrandale L2 cache are <n> * 256KB where <n> is the number of cores. AFAIK this is the case for most post Core 2 CPUs up to at least Skylake.
P4000 are Celeron not Pentium, see https://www.cpu-world.com/sspec/SL/SLBNL.html
Your SLBUX speed is incorrect, see https://www.cpu-world.com/sspec/SL/SLBUX.html
You failed to add SLBQB through to SLBUA, see https://en.wikipedia.org/wiki/List_of_I ... CP,_32_nm)
I don't think SLGT5 exists, see https://www.google.com/search?q=Intel+%22SLGT5%22. I suspect it's a SLGU5 typo.
I suspect SLBQK does not exist, please post a link to one.

I feel I need a fixed file from you, when might there be one please?

Reply 215 of 220, by PARKE

User metadata
Rank Oldbie
Rank
Oldbie

Part of these comments are redundant because I am working on this thing too. The 'PMF' entries are product tracking codes wich I parked in the S-Spec column for later care - see attached.
But this is more like working, I was merely interested in finding anomalies and updating my file a bit. The line that I draw in the sand ends where quad core starts - they don't interest me and too much of the data does not fit in my ' box'..... so better teach SIV to ignore what I don't have.

The attachment 24530624.pdf is no longer available
The attachment reduns.png is no longer available
Last edited by PARKE on 2025-06-19, 14:48. Edited 1 time in total.

Reply 216 of 220, by red-ray

User metadata
Rank Oldbie
Rank
Oldbie
PARKE wrote on 2025-06-19, 14:32:

better teach SIV to ignore what I don't have.

I have already stopped SIV reporting pre Pentium-II and Ivy Bridge-EP and later.

It's not that easy, it would be trivial for SIV not to report what you "don't have" and I have considered this, but this would mean things that you "should have" would not get reported.

I have always assumed that if you have any CPUs of a given generation you should have all of them.

At the moment you have such as Xeon Gulftown, but not Core i7 Gulftown, why? There are currently only 104 missing.

Thinking about this I feel you are 95% or more there, but if you wish to give up it's your call.

Reply 217 of 220, by PARKE

User metadata
Rank Oldbie
Rank
Oldbie

It is not a matter of 'giving up' . This thing was once started because I wanted an easy access to cpu's that interested me and the Intel sheets are the backbone. It didn't need to be 100% complete and it still doesn't..... it is an excerpt of the Intel sheets, never meant to be more and simple to put together. Adding individual listings from the web like from CPUW, Wiki etc is >>extremely tedious<< and I have been in such a rabbit hole before. In some past I wanted a full pedigree of one of my sighthounds and ended up with a pedigree database with over 200.000 entries which in the end were not useful in any way and at which I have not looked for years.

The attachment pedigree.jpg is no longer available

Frequencies that turn up like 1666.00 are the result of the database software adding [ .00 ] to an integer when a db format is conversed to txt - it just needs some setting changed ' somewhere' to turn up as 1.666. These are actually entered into the table as [1666] text, not [1.666] numerical.

Reply 218 of 220, by red-ray

User metadata
Rank Oldbie
Rank
Oldbie
red-ray wrote on 2025-06-19, 13:44:

Speeds such as 2266.00 clearly should be 2266.66.

PARKE wrote on 2025-06-20, 09:17:

Frequencies that turn up like 1666.00 are the result of the database software adding [ .00 ] to an integer when a db format is conversed to txt - it just needs some setting changed ' somewhere' to turn up as 1.666. These are actually entered into the table as [1666] text, not [1.666] numerical.

OK, I should have specified "clearly should be 2266.66 or 2266", either way were it my database I would have fixed it and posted a new .TSV file.

How come fsb is OK?

Further given the 2.27GHz I wonder, why 2266 rather than 2267?

Reply 219 of 220, by PARKE

User metadata
Rank Oldbie
Rank
Oldbie
red-ray wrote on 2025-06-20, 10:42:

OK, I should have specified "clearly should be 2266.66 or 2266", either way were it my database I would have fixed it and posted a new .TSV file.

If it bothers you open the file in notepad and replace [.00] with []
Thanks for the interesting trip and for sharing your knowledge.