search

Gwinel / likwid

Automatically exported from code.google.com/p/likwid
GNU General Public License v3.0
0 stars 0 forks source link

Ubuntu 12.04 compatibility #60

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
# likwid-perfctr -a
WARNING
PCI Uncore events not supported for single socket SNB.
ERROR
failed to open pci device: No such file or directory!

What is the expected output? What do you see instead?

What version of the product are you using? On what operating system?
Ubuntu 12.04 , likwid v2, Intel(R) Core(TM) i7-3960X CPU @ 3.30GHz

Please provide any additional information below.

open("/proc/bus/pci/7f/10.0", O_RDWR)   = -1 ENOENT (No such file or directory)
write(2, "ERROR\n", 6ERROR
)                  = 6
write(2, "failed to open pci device: No su"..., 54failed to open pci device: No 
such file or directory!
) = 54
exit_group(127)

Original issue reported on code.google.com by freekmas...@gmail.com on 14 Aug 2012 at 2:47

GoogleCodeExporter commented 9 years ago 
The SandyBridge Uncore is under current development. The Uncore is now partly 
programmed using PCI devices. These can only be written as root (I will provide 
a proxy solution to that) to allow users to still use it. 

As far as I know these Uncore PCI devices are not exposed in the desktop 
variants of SandyBridge. But I will check on that.

The released stable version will diable the Uncore part for the Desktop 
variants.

Original comment by jan.trei...@gmail.com on 14 Aug 2012 at 2:53

GoogleCodeExporter commented 9 years ago

Original comment by jan.trei...@gmail.com on 30 Sep 2012 at 1:31

GoogleCodeExporter commented 9 years ago

Original comment by jan.trei...@gmail.com on 30 Sep 2012 at 11:06

GoogleCodeExporter commented 9 years ago

Original comment by jan.trei...@gmail.com on 30 Sep 2012 at 11:17

GoogleCodeExporter commented 9 years ago

Original comment by jan.trei...@gmail.com on 30 Sep 2012 at 11:25

GoogleCodeExporter commented 9 years ago 
This issue was closed by revision f145c16abf3f.

Original comment by jan.trei...@gmail.com on 27 Nov 2012 at 4:58