Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

i7z on Xeon E5-2620v2 - unknown CPU #80

Open
GoogleCodeExporter opened this issue Mar 4, 2015 · 0 comments
Open

i7z on Xeon E5-2620v2 - unknown CPU #80

GoogleCodeExporter opened this issue Mar 4, 2015 · 0 comments

Comments

@GoogleCodeExporter
Copy link

I may be slow in responding to issues till the end of June 2013.

Step 1. What steps will reproduce the problem?

Run i7z on a Xeon E5-2xxx v2 system.

Step 2. What version of the product are you using (the download version or
the svn
version and which one)?

i7z-0.27.2

Step 3. If this is an enhancement or suggestion, skip this step (except if
its related to a particular OS or architecture). On what operating system?
BTW is it a 32-bit or a 64-bit OS/Kernel?



Step 4. Do provide information if bug/enhancement is related to a
particular OS/Processor. Please provide any additional information below
(helpful will be platform
information like number and types of cpus, motherboard and a copy of
/proc/cpuinfo)

i7z DEBUG: i7z version: svn-r77-(20-Nov-2011)
i7z DEBUG: Found Intel Processor
i7z DEBUG:    Stepping 4
i7z DEBUG:    Model e
i7z DEBUG:    Family 6
i7z DEBUG:    Processor Type 0
i7z DEBUG:    Extended Model 3
i7z DEBUG: msr = Model Specific Register
i7z DEBUG: detected a newer model of ivy bridge processor
i7z DEBUG: my coder doesn't know about it, can you send the following info to 
him?
i7z DEBUG: model e, extended model 3, proc_family 6
i7z DEBUG: msr device files exist /dev/cpu/*/msr
i7z DEBUG: You have write permissions to msr device files


Step 5. If the program crashes. Can you also paste the
output of ls -lt /dev/cpu/*/msr?



Step 6. If the program crashed OR if this is for a new i7 chip. Can you
also run the following commands? They read various registers
and if those registers cannot be read the tool fails ungracefully. You will
have to sudo
each commmand and probably also do sudo modprobe msr (before running the
programs)

rdmsr 0x19c
rdmsr 0x1a2
rdmsr 0x38d
rdmsr 778
rdmsr 779
rdmsr 1020
rdmsr 1021


Original issue reported on code.google.com by [email protected] on 25 Dec 2013 at 7:10

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant