bugdmidecode - Bugs: bug #47947, "Socket Designation" can...

 
 

bug #47947: "Socket Designation" can show garbage values

Submitted by:  -Deleted Account- <xorg>
Submitted on:  Tue 17 May 2016 06:41:11 PM UTC  
 
Category: NoneSeverity: 2 - Minor
Item Group: NoneStatus: Invalid
Privacy: PublicAssigned to: Jean Delvare <khali>
Open/Closed: Closed

Add a New Comment(Rich Markup)
   

You are not logged in

Please log in, so followups can be emailed to you.

 

Thu 19 May 2016 07:21:40 AM UTC, comment #3:

I have no idea what you are talking about, sorry. And this is not a support forum.

Jean Delvare <khali>
Project AdministratorIn charge of this item.
Wed 18 May 2016 05:15:47 PM UTC, comment #2:

Thank for your quick answer and these explanations.

Do you thing there is a way to find CPU socket without using a database-like system?

-Deleted Account- <xorg>
Wed 18 May 2016 09:14:10 AM UTC, comment #1:

The "Socket Designation" string is provided by the BIOS. It can be set to anything that is sufficient to uniquely identify the socket on the board. On single CPU socket machines, it can be set to literally anything.

dmidecode is printing what the BIOS provides. There's nothing more it can or should do.

The purpose of the "Socket Designation" string is not to describe the socket format. That is the purpose of the "Upgrade" field. However in practice, for new socket formats that have not made it into the SMBIOS specification yet, it is common that vendors set the Upgrade field to "Other" and (ab)use the "Socket Designation" string to mention the socket format.

Jean Delvare <khali>
Project AdministratorIn charge of this item.
Tue 17 May 2016 06:41:11 PM UTC, original submission:

Hi,

It seems with dmidecode, "Socket Designation" in type 4 can print garbage values.
I can read the raw DMI value with 'hexdump -C /sys/firmware/dmi/entries/4-0/raw' after loading dmi-sysfs Linux module.

The attached file 'hexdump_2500k.txt' shows the hexdump values for an Intel Core i5 2500K, and dmidecode recognizes LGA1155 socket perfectly (see file 'dmidecode_2500k.txt').

But but some CPUs, like Intel Atom N270, this information is unavailable (see file 'hexdump_n270.txt').

On various CPUs, "Socket Designation" print a random string, like "CPU" or "Microprocessor". The attached file 'dmidecode_various.txt' is a good example.

-Deleted Account- <xorg>

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach File(s):
   
   
Comment:
   

Attached Files
file #37188:  hexdump_2500k.txt added by xorg (942B - text/plain)
file #37189:  hexdump_n270.txt added by xorg (555B - text/plain)
file #37190:  dmidecode_2500k.txt added by xorg (2KiB - text/plain)
file #37191:  dmidecode_various.txt added by xorg (896B - text/plain)

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -unavailable- added by khali (Posted a comment)
  • -unavailable- added by xorg (Submitted the item)
  •  

    Do you think this task is very important?
    If so, you can click here to add your encouragement to it.
    This task has 0 encouragements so far.

    Only logged-in users can vote.

     

    Please enter the title of George Orwell's famous dystopian book (it's a date):

     

     

    Follow 8 latest changes.

    Date Changed By Updated Field Previous Value => Replaced By
    Wed 18 May 2016 09:14:10 AM UTCkhaliSeverity3 - Normal=>2 - Minor
      StatusNone=>Invalid
      Assigned toNone=>khali
      Open/ClosedOpen=>Closed
    Tue 17 May 2016 06:41:11 PM UTCxorgAttached File-=>Added hexdump_2500k.txt, #37188
      Attached File-=>Added hexdump_n270.txt, #37189
      Attached File-=>Added dmidecode_2500k.txt, #37190
      Attached File-=>Added dmidecode_various.txt, #37191

    Back to the top


    Powered by Savane 3.1-cleanup1