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

0 CPUs reported on Quad G5 running YellowDog Linux 6.2 #2

Closed
GoogleCodeExporter opened this issue May 7, 2015 · 3 comments · Fixed by #41
Closed

0 CPUs reported on Quad G5 running YellowDog Linux 6.2 #2

GoogleCodeExporter opened this issue May 7, 2015 · 3 comments · Fixed by #41

Comments

@GoogleCodeExporter
Copy link

What steps will reproduce the problem?
1. Download and decompress
2. Comment out graphics test per instructions in README
3. execute make
4. execute Run

What is the expected output? What do you see instead?
Quad-core G5 has 4 CPUs, but 0 CPUs are reported. Please see additional info 
below.

What version of the product are you using? On what operating system?
v5.1.2 on YDL 6.2 (2.6.29-3.ydl61.4)

Please provide any additional information below.

Output snippet:
========================================================================
   BYTE UNIX Benchmarks (Version 5.1.2)

   System: sorrel: GNU/Linux
   OS: GNU/Linux -- 2.6.29-3.ydl61.4 -- #1 SMP Mon Sep 7 14:50:27 PDT 2009
   Machine: ppc64 (ppc64)
   Language: en_US.utf8 (charmap="UTF-8", collate="UTF-8")
   09:51:37 up 18:57,  2 users,  load average: 0.22, 0.70, 0.70; runlevel 3

------------------------------------------------------------------------
Benchmark Run: Tue Nov 09 2010 09:51:37 - 10:19:32
0 CPUs in system; running 1 parallel copy of tests

Dhrystone 2 using register variables        5749777.3 lps   (10.0 s, 7 samples)
Double-Precision Whetstone                     1246.8 MWIPS (9.7 s, 7 samples)
Execl Throughput                               2021.4 lps   (30.0 s, 2 samples)
File Copy 1024 bufsize 2000 maxblocks        190662.5 KBps  (30.0 s, 2 samples)
File Copy 256 bufsize 500 maxblocks           57739.1 KBps  (30.0 s, 2 samples)
File Copy 4096 bufsize 8000 maxblocks        474500.7 KBps  (30.0 s, 2 samples)
Pipe Throughput                              401805.7 lps   (10.0 s, 7 samples)
Pipe-based Context Switching                 120129.4 lps   (10.0 s, 7 samples)
Process Creation                               6058.6 lps   (30.0 s, 2 samples)
Shell Scripts (1 concurrent)                   3675.4 lpm   (60.0 s, 2 samples)
Shell Scripts (8 concurrent)                   1057.4 lpm   (60.0 s, 2 samples)
System Call Overhead                         567026.7 lps   (10.0 s, 7 samples)

System Benchmarks Index Values               BASELINE       RESULT    INDEX
Dhrystone 2 using register variables         116700.0    5749777.3    492.7
Double-Precision Whetstone                       55.0       1246.8    226.7
Execl Throughput                                 43.0       2021.4    470.1
File Copy 1024 bufsize 2000 maxblocks          3960.0     190662.5    481.5
File Copy 256 bufsize 500 maxblocks            1655.0      57739.1    348.9
File Copy 4096 bufsize 8000 maxblocks          5800.0     474500.7    818.1
Pipe Throughput                               12440.0     401805.7    323.0
Pipe-based Context Switching                   4000.0     120129.4    300.3
Process Creation                                126.0       6058.6    480.8
Shell Scripts (1 concurrent)                     42.4       3675.4    866.8
Shell Scripts (8 concurrent)                      6.0       1057.4   1762.3
System Call Overhead                          15000.0     567026.7    378.0
                                                                   ========
System Benchmarks Index Score                                         490.6

Original issue reported on code.google.com by stiles.w...@gmail.com on 9 Nov 2010 at 3:37

@GoogleCodeExporter
Copy link
Author

Could you provide some information on your system hardware? If you have lshw 
installed, try running lshw -C cpu and report the results of that. If not, try 
running dmidecode -t 4.


Original comment by kdlu...@gmail.com on 14 Jan 2011 at 6:10

  • Changed state: Accepted

@STH-Dev
Copy link

STH-Dev commented Mar 24, 2016

This is happening on ARM boards as well. Here is the lshw -C cpu example from a Qualcomm Dragonboard 410c arm64 development board:
root@Dragonboard410c1:/# lshw -C cpu
*-cpu:0
description: CPU
product: cpu
physical id: 0
bus info: cpu@0
size: 1209MHz
capacity: 1209MHz
capabilities: cpufreq
*-cpu:1 DISABLED
description: CPU
product: cpu
physical id: 1
bus info: cpu@1
size: 1209MHz
capacity: 1209MHz
capabilities: cpufreq
*-cpu:2 DISABLED
description: CPU
product: cpu
physical id: 2
bus info: cpu@2
size: 1209MHz
capacity: 1209MHz
capabilities: cpufreq
*-cpu:3 DISABLED
description: CPU
product: cpu
physical id: 3
bus info: cpu@3
size: 1209MHz
capacity: 1209MHz
capabilities: cpufreq

The same error can be reproduced on the Raspberry Pi 3, HiKey LeMaker 1GB and etc as well.

@gstrauss
Copy link
Collaborator

related to #4 and #16

gstrauss added a commit to gstrauss/byte-unixbench that referenced this issue Sep 18, 2016
gstrauss added a commit to gstrauss/byte-unixbench that referenced this issue Sep 18, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants