CPU QDF s-spec string

RolloZ170

Well-Known Member
i need to know where the s-spec or QDF string is come from.
i..e.  [font=verdana, helvetica, arial, sans-serif]SR2P0 or [/font]QK3E(intel qualitying sample)
Is that read out of the processor (found no info at cpuid instruction)?
or generated by some specifications of the processor ?
or is that just a table.

thanks for reply
 
It's from a table based on several criteria. AFAIK the only CPUs that have the SSPEC/QDF stored in the chip are EX-series Xeons (E7).
 
Martin said:
It's from a table based on several criteria. AFAIK the only CPUs that have the SSPEC/QDF stored in the chip are EX-series Xeons (E7).

many thanks.
i have a Xeon E5-2630L v4 QS stepping R0 cpuid 406F1, HWinfo shows s-spec as QK3K(ES2)
 
If your base (HFM) clock is 1.7 GHz (not 1.8 GHz), then it's not E5-2630L v4. The 1.7 GHz was just an intermediate ES that doesn't have an official processor name.
 
Martin said:
If your base (HFM) clock is 1.7 GHz (not 1.8 GHz), then it's not E5-2630L v4. The 1.7 GHz was just an intermediate ES that doesn't have an official processor name.
thanks again. just ask how that QK3K is build from.
sure it is not exact the 2630L v4 but is has same turbo rates as retail, thats curious.
1 core  x29
2 cores x29
3 cores x27
4 cores x26
5 cores x25
6 cores x24
7 cores x23
8 cores x22
9 cores x21
10 cores x20
with same cpuid and stepping should be declared as pre-QS not ES2 thought.
 
No, the CPUID does not determine the exact ES-phase. A single ID can be shared by multiple phases including production.
QK3K is ES2.
 
Martin said:
No, the CPUID does not determine the exact ES-phase. A single ID can be shared by multiple phases including production.
QK3K is ES2.
I now got a skylake-sp(lga3647) ES2 labeled as QLH2, but HWinfo shows as QDF just an empty string .
Do i need a internet connection for database/table update or comes the HWinfo.exe with the complete table ???
 
No internet connection is required.
Please post the HWiNFO Debug File and I will check if this is some bug in HWiNFO.
 
Martin said:
No internet connection is required.
Please post the HWiNFO Debug File and I will check if this is some bug in HWiNFO.

here is the debug file from the QLH2

by the way, my other cpu(1.80Ghz 16C) labeled as QL1M is found as "QLCY,QL2P (ES2)"  :blush:
is it possible there is a difference sspec result in dual cpu config. ? i have only a SuperMicro X11SPM-F.
 

Attachments

  • HWiNFO64.DBG
    1.3 MB · Views: 6
Thanks. I checked and for both SKUs, there's a bug in recognition in HWiNFO. It will be fixed in the next build.
 
Martin said:
Thanks. I checked and for both SKUs, there's a bug in recognition in HWiNFO. It will be fixed in the next build.

Works now ! thanks
 

Attachments

  • capture_001_26062018_210644.jpg
    capture_001_26062018_210644.jpg
    79.4 KB · Views: 16
Martin said:
Thanks for the feedback.

as you see in the screenshot the memory modules are not shown there.
at first i thought thats normal because the spd is caught by the bmc/ipmi for
thermal sensor readout (i have found no bios settings for polling etc)
yesterday i had to check some memory modules and i startet memtest86 v7.4(UEFI)
this tool shows the module names(SK Hynix / HMA41GR7AFR8N-TF ) !!
any chance to see the memory modules in HWinfo ?
if needed you can check the debug file from the QLh2 above for that.
 
I think memory module names are read from SMBIOS DMI, but that doesn't provide true SPD content, only very limited information.
 
Martin said:
I think memory module names are read from SMBIOS DMI, but that doesn't provide true SPD content, only very limited information.

obviously... memtest86 shows no serial numbers. OK, thanks for checking.
 
Martin said:
I think memory module names are read from SMBIOS DMI, but that doesn't provide true SPD content, only very limited information.

looked just for fun into the memtest logfile and found more information.
this may help to support supermicro boards, its a x11spm-f

2018-12-03 15:38:57 - Failed to retrieve SPD info. Enumerating PCI bus...
2018-12-03 15:38:57 - Scanning PCI for devices:
.............
2018-12-03 15:38:58 -  VID:8086 DID:A1A1 Bus:00 Dev:1F Fun:02 IO Add:0000 IO (2) Add:0000 MMIO Add:0 PCI Add:{00:00:00:0000} Rev:09 [Intel Unknown]
2018-12-03 15:38:58 - Found device with SMBUS class code.
............
2018-12-03 15:39:02 - Finished searching PCI for SMBus Controller
2018-12-03 15:39:02 - Getting SMBIOS Memory Device info...
2018-12-03 15:39:02 - Found 6 Memory Devices
2018-12-03 15:39:02 - DEBUG: Get SMB mem device Struct 0
2018-12-03 15:39:02 - DEBUG: Get SMB mem device Struct Get strings (FormattedLen=40, iTotalLen=68)
2018-12-03 15:39:02 - [Slot 0] TotalWidth: 0, DataWidth: 0, Size: 0, FormFactor: 9, DeviceSet: 0, MemoryType: 2, Speed: 0, Attributes: 0, ExtendedSize: 0, ConfiguredMemoryClockSpeed: 0, MinimumVoltage: 1200, MaximumVoltage: 1200, ConfiguredVoltage: 1200
2018-12-03 15:39:02 - [Slot 0] DeviceLocator: DIMMA1, BankLocator: P0_Node0_Channel0_Dimm0, Manufacturer: NO DIMM, S/N: NO DIMM, AssetTag: NO DIMM, PartNumber: NO DIMM
2018-12-03 15:39:02 - DEBUG: Get SMB mem device Struct 1
2018-12-03 15:39:02 - DEBUG: Get SMB mem device Struct Get strings (FormattedLen=40, iTotalLen=8C)
2018-12-03 15:39:02 - [Slot 1] TotalWidth: 72, DataWidth: 64, Size: 32767, FormFactor: 9, DeviceSet: 0, MemoryType: 26, Speed: 2400, Attributes: 4, ExtendedSize: 65536, ConfiguredMemoryClockSpeed: 2400, MinimumVoltage: 1200, MaximumVoltage: 1200, ConfiguredVoltage: 1200
2018-12-03 15:39:02 - [Slot 1] DeviceLocator: DIMMB1, BankLocator: P0_Node0_Channel1_Dimm0, Manufacturer: SK Hynix, S/N: 921E3CCC, AssetTag: DIMMB1_AssetTag (date:17/43), PartNumber: HMAA8GL7MMR4N-UH    
2018-12-03 15:39:02 - DEBUG: Get SMB mem device Struct 2
2018-12-03 15:39:02 - DEBUG: Get SMB mem device Struct Get strings (FormattedLen=40, iTotalLen=68)
2018-12-03 15:39:02 - [Slot 2] TotalWidth: 0, DataWidth: 0, Size: 0, FormFactor: 9, DeviceSet: 0, MemoryType: 2, Speed: 0, Attributes: 0, ExtendedSize: 0, ConfiguredMemoryClockSpeed: 0, MinimumVoltage: 1200, MaximumVoltage: 1200, ConfiguredVoltage: 1200
2018-12-03 15:39:02 - [Slot 2] DeviceLocator: DIMMC1, BankLocator: P0_Node0_Channel2_Dimm0, Manufacturer: NO DIMM, S/N: NO DIMM, AssetTag: NO DIMM, PartNumber: NO DIMM
2018-12-03 15:39:02 - DEBUG: Get SMB mem device Struct 3
2018-12-03 15:39:02 - DEBUG: Get SMB mem device Struct Get strings (FormattedLen=40, iTotalLen=68)
2018-12-03 15:39:02 - [Slot 3] TotalWidth: 0, DataWidth: 0, Size: 0, FormFactor: 9, DeviceSet: 0, MemoryType: 2, Speed: 0, Attributes: 0, ExtendedSize: 0, ConfiguredMemoryClockSpeed: 0, MinimumVoltage: 1200, MaximumVoltage: 1200, ConfiguredVoltage: 1200
2018-12-03 15:39:02 - [Slot 3] DeviceLocator: DIMMD1, BankLocator: P0_Node1_Channel0_Dimm0, Manufacturer: NO DIMM, S/N: NO DIMM, AssetTag: NO DIMM, PartNumber: NO DIMM
2018-12-03 15:39:02 - DEBUG: Get SMB mem device Struct 4
2018-12-03 15:39:02 - DEBUG: Get SMB mem device Struct Get strings (FormattedLen=40, iTotalLen=68)
2018-12-03 15:39:02 - [Slot 4] TotalWidth: 0, DataWidth: 0, Size: 0, FormFactor: 9, DeviceSet: 0, MemoryType: 2, Speed: 0, Attributes: 0, ExtendedSize: 0, ConfiguredMemoryClockSpeed: 0, MinimumVoltage: 1200, MaximumVoltage: 1200, ConfiguredVoltage: 1200
2018-12-03 15:39:02 - [Slot 4] DeviceLocator: DIMME1, BankLocator: P0_Node1_Channel1_Dimm0, Manufacturer: NO DIMM, S/N: NO DIMM, AssetTag: NO DIMM, PartNumber: NO DIMM
2018-12-03 15:39:02 - DEBUG: Get SMB mem device Struct 5
2018-12-03 15:39:02 - DEBUG: Get SMB mem device Struct Get strings (FormattedLen=40, iTotalLen=68)
2018-12-03 15:39:02 - [Slot 5] TotalWidth: 0, DataWidth: 0, Size: 0, FormFactor: 9, DeviceSet: 0, MemoryType: 2, Speed: 0, Attributes: 0, ExtendedSize: 0, ConfiguredMemoryClockSpeed: 0, MinimumVoltage: 1200, MaximumVoltage: 1200, ConfiguredVoltage: 1200
2018-12-03 15:39:02 - [Slot 5] DeviceLocator: DIMMF1, BankLocator: P0_Node1_Channel2_Dimm0, Manufacturer: NO DIMM, S/N: NO DIMM, AssetTag: NO DIMM, PartNumber: NO DIMM
2018-12-03 15:39:02 - Getting memory controller info
2018-12-03 15:39:02 - find_mem_controller - Could not find controller, enumerating PCI bus...
2018-12-03 15:39:02 - Scanning PCI for devices:
 
Martin said:
Thanks for the feedback.

I now got a cascade lake ES labeled as QQ8M(ES2?), but HWinfo shows QQU1(QS)
[attachment=3411]

here is the Debug file.
[attachment=3412]
 

Attachments

  • capture_003_02052019_205842.jpg
    capture_003_02052019_205842.jpg
    88.7 KB · Views: 18
  • HWiNFO64.DBG
    1.5 MB · Views: 2
Thanks. These two are quite similar except TDP. Shall be fixed in the next HWiNFO build.
 
Martin said:
Thanks. These two are quite similar except TDP. Shall be fixed in the next HWiNFO build.

qspec is correct now, thank you.
[attachment=3419]
 

Attachments

  • capture_001_11052019_204448.jpg
    capture_001_11052019_204448.jpg
    89.4 KB · Views: 12
Back
Top