Hypfer / Hypfer/i7z

Problem on systems with many cores

Open
#32 1 comment 0 reactions 0 assignees View on GitHub
auto-migrated Priority-Medium Type-Defect
Dominant language
C
Stars
1
Forks
0
PR merge metrics
No merged PRs in 30d

Description

```
What steps will reproduce the problem?
1. ./i7z on my 8 socket 8 core E7 (westmere-ex)

What is the expected output? What do you see instead? If possible do paste
the output

Expected: work
Actual:
# ./i7z
i7z DEBUG: i7z version: svn-r50-(1-1-2011)
i7z DEBUG: Found Intel Processor
i7z DEBUG: Stepping 2
i7z DEBUG: Model f
i7z DEBUG: Family 6
i7z DEBUG: Processor Type 0
i7z DEBUG: Extended Model 2
i7z DEBUG: msr = Model Specific Register
i7z DEBUG: Detected a Xeon MP - 32nm (E7 series)
i7z DEBUG: msr device files exist /dev/cpu/*/msr
i7z DEBUG: You have write permissions to msr device files
i7z: helper_functions.c:669: construct_CPU_Heirarchy_info: Assertion
`it_processor_num < 32' failed.
Aborted

What version of the product are you using (the download version or the svn
version and which one)? On what operating system?
BTW is it a 32-bit or a 64-bit OS/Kernel?

0.27 downloaded on a CentOS-5.7(2.6.18-274.el5) x86_64

Please provide any additional information below (helpful will be platform
information like number and types of cpus, motherboard and a copy of
/proc/cpuinfo)

8 socket 8 core (ht off) total 64 cores

```

Original issue reported on code.google.com by `peter.kj...@gmail.com` on 1 Sep 2011 at 4:22

Contributor guide

No contributing guide indexed for this repository

Research direction

Start with helper_functions.c:669, where construct_CPU_Heirarchy_info asserts that the processor number is below 32. Reproduce with ./i7z on the reported 64-core, 8-socket system and inspect the CPU hierarchy handling. Done means i7z no longer aborts on this topology and produces its expected output.

Written by the indexing model from the issue text.

Assessment

Tech stack
c
Domain
operating-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.