Closed GoogleCodeExporter closed 9 years ago
Hi, the current solution for Uncore is a bit fragile as it relies on PCI
address space registers. And these are relying on proper behaviour of the BIOS
and the OS kernel to be accessible in a save way. So these devices might be
missing on your machine, you can check this with lspci command.
Another reason for your error could be that you did not enable the SandyBridge
Uncore in config.mk. The option is called ENABLE_SNB_UNCORE. Default is
disabled because of the reasons above. Also note that if you enable the Uncore
the marker API might have a significant overhead on SandyBridge-EP as currently
all counters are read. This will be resolved in the upcoming release.
Original comment by jan.trei...@gmail.com
on 20 Mar 2013 at 9:24
[deleted comment]
Thanks for your help ,maybe some of devices is missing in this server.
How can I know which devices is missing through lspci command ?
I enable SandyBridge Uncore support.
#likwid-perfctr -C 0 -g MEM ls -l
INFO
This system has no support for PCI based Uncore counters.
This means you cannot use performance groups as MEM, which require Uncore counters.
ERROR
failed to open pci device: No such file or directory!
Here is the lspci info:
# lspci
00:00.0 Host bridge: Intel Corporation Xeon E5/Core i7 DMI2 (rev 07)
00:01.0 PCI bridge: Intel Corporation Xeon E5/Core i7 IIO PCI Express Root Port
1a (rev 07)
00:02.0 PCI bridge: Intel Corporation Xeon E5/Core i7 IIO PCI Express Root Port
2a (rev 07)
00:03.0 PCI bridge: Intel Corporation Xeon E5/Core i7 IIO PCI Express Root Port
3a in PCI Express Mode (rev 07)
00:03.2 PCI bridge: Intel Corporation Xeon E5/Core i7 IIO PCI Express Root Port
3c (rev 07)
00:04.0 System peripheral: Intel Corporation Xeon E5/Core i7 DMA Channel 0 (rev
07)
00:04.1 System peripheral: Intel Corporation Xeon E5/Core i7 DMA Channel 1 (rev
07)
00:04.2 System peripheral: Intel Corporation Xeon E5/Core i7 DMA Channel 2 (rev
07)
00:04.3 System peripheral: Intel Corporation Xeon E5/Core i7 DMA Channel 3 (rev
07)
00:04.4 System peripheral: Intel Corporation Xeon E5/Core i7 DMA Channel 4 (rev
07)
00:04.5 System peripheral: Intel Corporation Xeon E5/Core i7 DMA Channel 5 (rev
07)
00:04.6 System peripheral: Intel Corporation Xeon E5/Core i7 DMA Channel 6 (rev
07)
00:04.7 System peripheral: Intel Corporation Xeon E5/Core i7 DMA Channel 7 (rev
07)
00:05.0 System peripheral: Intel Corporation Xeon E5/Core i7 Address Map,
VTd_Misc, System Management (rev 07)
00:05.2 System peripheral: Intel Corporation Xeon E5/Core i7 Control Status and
Global Errors (rev 07)
00:11.0 PCI bridge: Intel Corporation C600/X79 series chipset PCI Express
Virtual Root Port (rev 06)
00:1a.0 USB controller: Intel Corporation C600/X79 series chipset USB2 Enhanced
Host Controller #2 (rev 06)
00:1c.0 PCI bridge: Intel Corporation C600/X79 series chipset PCI Express Root
Port 1 (rev b6)
00:1c.7 PCI bridge: Intel Corporation C600/X79 series chipset PCI Express Root
Port 8 (rev b6)
00:1d.0 USB controller: Intel Corporation C600/X79 series chipset USB2 Enhanced
Host Controller #1 (rev 06)
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev a6)
00:1f.0 ISA bridge: Intel Corporation C600/X79 series chipset LPC Controller
(rev 06)
00:1f.2 SATA controller: Intel Corporation C600/X79 series chipset 6-Port SATA
AHCI Controller (rev 06)
00:1f.3 SMBus: Intel Corporation C600/X79 series chipset SMBus Host Controller
(rev 06)
01:00.0 PCI bridge: Renesas Technology Corp. SH7757 PCIe Switch [PS]
02:00.0 PCI bridge: Renesas Technology Corp. SH7757 PCIe Switch [PS]
02:01.0 PCI bridge: Renesas Technology Corp. SH7757 PCIe Switch [PS]
03:00.0 PCI bridge: Renesas Technology Corp. SH7757 PCIe-PCI Bridge [PPB]
04:00.0 VGA compatible controller: Matrox Electronics Systems Ltd. G200eR2
06:00.0 Ethernet controller: Intel Corporation I350 Gigabit Network Connection
(rev 01)
06:00.1 Ethernet controller: Intel Corporation I350 Gigabit Network Connection
(rev 01)
06:00.2 Ethernet controller: Intel Corporation I350 Gigabit Network Connection
(rev 01)
06:00.3 Ethernet controller: Intel Corporation I350 Gigabit Network Connection
(rev 01)
0c:00.0 Serial Attached SCSI controller: LSI Logic / Symbios Logic SAS2008
PCI-Express Fusion-MPT SAS-2 [Falcon] (rev 03)
11:00.0 Serial Attached SCSI controller: LSI Logic / Symbios Logic SAS2008
PCI-Express Fusion-MPT SAS-2 [Falcon] (rev 03)
1b:00.0 Serial Attached SCSI controller: LSI Logic / Symbios Logic SAS2004
PCI-Express Fusion-MPT SAS-2 [Spitfire] (rev 03)
80:00.0 PCI bridge: Intel Corporation Xeon E5/Core i7 DMI2 in PCI Express Mode
(rev 07)
80:02.0 PCI bridge: Intel Corporation Xeon E5/Core i7 IIO PCI Express Root Port
2a (rev 07)
80:04.0 System peripheral: Intel Corporation Xeon E5/Core i7 DMA Channel 0 (rev
07)
80:04.1 System peripheral: Intel Corporation Xeon E5/Core i7 DMA Channel 1 (rev
07)
80:04.2 System peripheral: Intel Corporation Xeon E5/Core i7 DMA Channel 2 (rev
07)
80:04.3 System peripheral: Intel Corporation Xeon E5/Core i7 DMA Channel 3 (rev
07)
80:04.4 System peripheral: Intel Corporation Xeon E5/Core i7 DMA Channel 4 (rev
07)
80:04.5 System peripheral: Intel Corporation Xeon E5/Core i7 DMA Channel 5 (rev
07)
80:04.6 System peripheral: Intel Corporation Xeon E5/Core i7 DMA Channel 6 (rev
07)
80:04.7 System peripheral: Intel Corporation Xeon E5/Core i7 DMA Channel 7 (rev
07)
80:05.0 System peripheral: Intel Corporation Xeon E5/Core i7 Address Map,
VTd_Misc, System Management (rev 07)
80:05.2 System peripheral: Intel Corporation Xeon E5/Core i7 Control Status and
Global Errors (rev 07)
Original comment by 01jay...@gmail.com
on 22 Mar 2013 at 7:36
Hi,
your system is missing the Performance Monitoring PCI devices. See the attached
file for an example (relevant are the devices starting with 7f and ff). To fix
that you might need to enable performance monitoring in the BIOS or use a more
recent kernel (still I do not know exactly since what kernel version those SNB
devices are supported, our system used a 3.0.51 kernel). It might be necessary
to update the BIOS (this depends on your mainboard vendor).
Original comment by jan.trei...@gmail.com
on 22 Mar 2013 at 7:51
Attachments:
Original comment by jan.trei...@gmail.com
on 8 May 2013 at 8:27
Original issue reported on code.google.com by
01jay...@gmail.com
on 18 Mar 2013 at 5:24