From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: CPU microcode reported wrong in /proc/cpuinfo
Date: Wed, 10 Jun 2020 15:45:19 -0600 [thread overview]
Message-ID: <2c720f82-8d58-6b87-3b6c-287d0810c303@SystematicSw.ab.ca> (raw)
In-Reply-To: <DM6PR09MB4043B0780831BF37F817980FA5830@DM6PR09MB4043.namprd09.prod.outlook.com>
On 2020-06-10 09:34, Lavrentiev, Anton (NIH/NLM/NCBI) [C] via Cygwin wrote:
>> also have to look for Update Signature
>
> It's Windows 7 here (Windows 10 uses newer registry key names, with the word "Revision" in them, instead).
>
>> Could you please run:
>
> $ head /proc/version
> CYGWIN_NT-6.1-7601 version 3.1.4-340.x86_64 (corinna@calimero) (gcc version 7.4.0 20181206 (Fedora Cygwin 7.4.0-1) (GCC) ) 2020-02-19 08:49 UTC
>
> $ regtool list -v "/proc/registry/HKEY_LOCAL_MACHINE/SOFTWARE/Microsoft/Windows NT/CurrentVersion/" | fgrep =
> CurrentVersion (REG_SZ) = "6.1"
> CurrentBuild (REG_SZ) = "7601"
> SoftwareType (REG_SZ) = "System"
> CurrentType (REG_SZ) = "Multiprocessor Free"
> InstallDate (REG_DWORD) = 0x54373393 (1412903827)
> RegisteredOrganization (REG_SZ) = ""
> RegisteredOwner (REG_SZ) = "ANTON"
> SystemRoot (REG_SZ) = "C:\Windows"
> InstallationType (REG_SZ) = "Client"
> EditionID (REG_SZ) = "HomePremium"
> ProductName (REG_SZ) = "Windows 7 Home Premium"
> ProductId (REG_SZ) = "00359-OEM-8702121-81656"
> DigitalProductId (REG_BINARY) = a4 00 00 00 03 00 00 00
> DigitalProductId4 (REG_BINARY) = f8 04 00 00 04 00 00 00
> CurrentBuildNumber (REG_SZ) = "7601"
> BuildLab (REG_SZ) = "7601.win7sp1_ldr_escrow.200102-1707"
> BuildLabEx (REG_SZ) = "7601.24545.amd64fre.win7sp1_ldr_escrow.200102-1707"
> BuildGUID (REG_SZ) = "3b42db76-c1db-4ecd-8368-b2e532306b4a"
> CSDBuildNumber (REG_SZ) = "1130"
> PathName (REG_SZ) = "C:\Windows"
> CSDVersion (REG_SZ) = "Service Pack 1"
> UBR (REG_DWORD) = 0x00005fe2 (24546)
>
> $ regtool list -v /proc/registry/HKEY_LOCAL_MACHINE/HARDWARE/DESCRIPTION/System/CentralProcessor/0/
> Component Information (REG_BINARY) = 00 00 00 00 00 00 00 00
> Identifier (REG_SZ) = "Intel64 Family 6 Model 23 Stepping 10"
> Configuration Data (REG_FULL_RESOURCE_DESCRIPTOR) = ?
> ProcessorNameString (REG_SZ) = "Intel(R) Xeon(R) CPU X5470 @ 3.33GHz"
> VendorIdentifier (REG_SZ) = "GenuineIntel"
> FeatureSet (REG_DWORD) = 0x215b3ffe (559628286)
> ~MHz (REG_DWORD) = 0x00000d04 (3332)
> Update Signature (REG_BINARY) = 00 00 00 00 0e 0a 00 00
> Update Status (REG_DWORD) = 0x00000007 (7)
> Previous Update Signature (REG_BINARY) = 00 00 00 00 0e 0a 00 00
> Platform ID (REG_DWORD) = 0x00000040 (64)
>
> P.S. I have since updated the microcode to version 0xA0E (from 0xA0B that used to show in my last email).
Thanks for that info.
I think I may now have an approach that will work across all known microcode
registry values, but having testing problems.
--
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
[Data in IEC units and prefixes, physical quantities in SI.]
next prev parent reply other threads:[~2020-06-10 21:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-10 15:34 Lavrentiev, Anton (NIH/NLM/NCBI) [C]
2020-06-10 21:45 ` Brian Inglis [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-07-16 20:41 Lavrentiev, Anton (NIH/NLM/NCBI) [C]
2020-07-16 20:36 Lavrentiev, Anton (NIH/NLM/NCBI) [C]
2020-06-10 20:23 Lavrentiev, Anton (NIH/NLM/NCBI) [C]
2020-06-10 21:45 ` Brian Inglis
2020-07-10 1:27 ` Brian Inglis
2020-07-16 14:56 ` Lavrentiev, Anton (NIH/NLM/NCBI) [C]
2020-07-16 19:46 ` Brian Inglis
2020-07-16 20:13 ` Brian Inglis
2020-05-31 15:07 Lavrentiev, Anton (NIH/NLM/NCBI) [C]
2020-06-02 20:11 ` Brian Inglis
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2c720f82-8d58-6b87-3b6c-287d0810c303@SystematicSw.ab.ca \
--to=brian.inglis@systematicsw.ab.ca \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).