I am testing oprofile version 1.0.0 out on two almost identical machines. On one it works perfectly on the other it does not collect any data at all. Oprofile was downloaded as source and compiled and installed on each box - with same version of all libraries/compiler etc
As root I am running and exiting with recommended CTRL-c
operf --system-wide
Kernel on both boxes is
2.6.32-279.el6.x86_64 #1 SMP Fri Jun 22 12:19:21 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux
There is a difference in CPU's - this is working operf box
vendor_id : GenuineIntel
cpu family : 6
model : 15
model name : Intel(R) Xeon(R) CPU 5160 # 3.00GHz
stepping : 6
cpu MHz : 2992.426
This is non working box
vendor_id : GenuineIntel
cpu family : 15
model : 4
model name : Intel(R) Xeon(TM) CPU 3.80GHz
stepping : 10
cpu MHz : 3790.625
Even if the 2nd CPU is not supporting hardware profiling (not sure what flags to look for) is there a way to make it work - This mentions OPROFILE can't get performance data using timer mode but opcontrol is gone in version 1.0
Working operf.log file results
Profiling started at Mon Oct 6 14:22:33 2014
Profiling stopped at Mon Oct 6 14:23:56 2014
-- OProfile/operf Statistics --
Nr. non-backtrace samples: 1264859
Nr. kernel samples: 628924
Nr. user space samples: 635935
Nr. samples lost due to sample address not in expected range for domain: 0
Nr. lost kernel samples: 0
Nr. samples lost due to sample file open failure: 0
Nr. samples lost due to no permanent mapping: 682
Nr. user context kernel samples lost due to no app info available: 0
Nr. user samples lost due to no app info available: 0
Nr. backtraces skipped due to no file mapping: 0
Nr. hypervisor samples dropped due to address out-of-range: 0
Nr. samples lost reported by perf_events kernel: 0
Non working operf.log file results
Profiling started at Tue Oct 7 11:44:38 2014
Profiling stopped at Tue Oct 7 11:45:34 2014
-- OProfile/operf Statistics --
Nr. non-backtrace samples: 0
Nr. kernel samples: 0
Nr. user space samples: 0
Nr. samples lost due to sample address not in expected range for domain: 0
Nr. lost kernel samples: 0
Nr. samples lost due to sample file open failure: 0
Nr. samples lost due to no permanent mapping: 0
Nr. user context kernel samples lost due to no app info available: 0
Nr. user samples lost due to no app info available: 0
Nr. backtraces skipped due to no file mapping: 0
Nr. hypervisor samples dropped due to address out-of-range: 0
Nr. samples lost reported by perf_events kernel: 0
Related
I have a cloud in the digital ocean where it has 1 GB of ram.
I need to install a docker, laravel, mysql, nginx environment, I found the laradock and installed it normally but when running the composer in the container I am returning a memory limit error.
Error running: composer install
root#b9864446a1e1:/var/www/site# composer install
Loading composer repositories with package information
Updating dependencies (including require-dev)
mmap() failed: [12] Cannot allocate memory
mmap() failed: [12] Cannot allocate memory
PHP Fatal error: Out of memory (allocated 677388288) (tried to allocate 4096 bytes) in phar:///usr/local/bin/composer/src/Composer/DependencyResolver/RuleWatchGraph.php on line 52
Fatal error: Out of memory (allocated 677388288) (tried to allocate 4096 bytes) in phar:///usr/local/bin/composer/src/Composer/DependencyResolver/RuleWatchGraph.php on line 52
Error when trying to change memory.
WARNING: Your kernel does not support swap limit capabilities or the
cgroup is not mounted. Memory limited without swap.
This could be happening because the VPS runs out of memory and has no Swap space enabled.
free -m
total used free shared buffers cached
Mem: xxxx xxx xxxx x x xxx
-/+ buffers/cache: xxx xxxx
Swap: 0 0 0
To enable the swap you can use for example:
/bin/dd if=/dev/zero of=/var/swap.1 bs=1M count=1024
/sbin/mkswap /var/swap.1
/sbin/swapon /var/swap.1
You can make a permanent swap file following this tutorial from DigitalOcean.
I have a gateway device with MT7620a in MIPS architecture. The device has installed OpenWRT. If I connect to device via UART with the goal of flashing new firmware I see something I don't understand, MCU loading two version U-Boot.
U-Boot 1.1.3
Ralink UBoot Version: 4.3.0.0
Here is Log System after start
U-Boot 1.1.3 (Apr 27 2015 - 13:54:38)
Board: Ralink APSoC DRAM: 128 MB
relocate_code Pointer at: 87fb8000
enable ephy clock...done. rf reg 29 = 5
SSC disabled.
spi_wait_nsec: 29
spi device id: 1c 70 18 1c 70 (70181c70)
find flash: EN25QH128A
raspi_read: from:30000 len:1000
*** Warning - bad CRC, using default environment
============================================
Ralink UBoot Version: 4.3.0.0
--------------------------------------------
ASIC 7620_MP (Port5<->None)
DRAM component: 1024 Mbits DDR, width 16
DRAM bus: 16 bit
Total memory: 128 MBytes
Flash component: SPI Flash
Date:Apr 27 2015 Time:13:54:38
Of course I have a few additional questions in this issue:
What is different between these U-Boot ?
Why does my device need two versions U-Boot ?
Whether this u-boots need separate *.bin image or these is together
in one image *.bin ? In my device is only one partition for u-boot image and one partition for variables:
mtd0: 00030000 00010000 "u-boot"
mtd1: 00010000 00010000 "u-boot-env"
As Alexandre Belloni said, there is probably only one version of U-Boot on your device, it just has two different version identifiers.
The reason for this is that manufacturers often need to modify the U-Boot source code in order to get it to operate on their device, or to add features.
On your device, it looks like the version of U-Boot that Ralink pulled from the official U-Boot source code repository is 1.1.3. Ralink's own internal version number that they use for tracking their internal modifications is 4.3.0.0.
There is probably only one u-boot and "Ralink UBoot Version: 4.3.0.0" is an internal u-boot version for Ralink.
I am facing below exception while launching the Oculus SDK 0.6.0.1 demo program.
**Exception Info
Exception report file: C:\Users\Exception Report (2015-06-26 12.41.23).txt
Exception minidump file: C:\Users\Exception Minidump (2015-06-26 12.41.23).mdmp
Time (GMT): 2015/06/26 12:41:23
Time (local): 2015/06/26 18:11:23
Thread name: (not available)
Thread handle: 0x000000d8
Thread sys id: 976 (0x3d0)
Exception instruction address: 0x0ff4f677 (see callstack below)
Exception description: ACCESS_VIOLATION reading address 0x00000000
Exception location: ovr_WaitTillTime (59911)**
below is my app and system Info :
App Info
Process path: C:\Users\Downloads\ovr_sdk_win_0.6.0.0\OculusSDK\Samples\OculusWorldDemo\Release\OculusWorldDemo.exe
App format: 32 bit
App version info not present
System Info
OS name: Windows 7, version: 6.1 build 7601, 32 bit, platform id: 2, service pack: Service Pack 1
Debugger present: no
Processor count: 4
Processor type: x86
Processor level: 6
Processor revision: 10759
Memory load: 87%
Total physical memory: 3240 MiB
Available physical memory: 389 MiB
Total page file memory: 6480 MiB
Available page file memory: 2323 MiB
Total virtual memory: 2047 MiB
Free virtual memory: 1974 MiB
Can someone help me to understand what to do, to fix this issue :(
You didn't include any info about your video hardware & drivers; the first thing I'd try is upgrading them. Also try upgrading to the latest Oculus 0.7.0.1 runtime.
I am using Fedora and when I execute $ hackrf_info in the terminal, this is displayed:
Found HackRF board.
Board ID Number: 2 (HackRF One)
Firmware Version: 2014.08.1
Part ID Number: 0xa000cb3c 0x006c4757
Serial Number: 0x00000000 0x00000000 0x14d463dc 0x2f908de1
In the log section at the bottom in gnuradio-companion, HackRFOne is not displaying after debugging as an execute device.
Is there a problem with VID and PID of new versions and old hardware versions — for example statically hard-coded numbers in gnuradio-companion? D
I see this device:
Bus 002 Device 021: ID 1d50:6089 OpenMoko, Inc.
Where is the problem?
In the source code for GNU-Radio Companion, in which file/files can I edit information for detecting HackRFOne hardware?
Sorry, it's ok, I make upgrade from Fedora 20 to Fedora 21 and it's fine!
I have a Dell Precision Rack running Ubuntu Precise and featuring two Tesla C2075 plus a Quadro 600 which is the display device. I have recently finished some tests on my desktop-computer and now tried to port stuff to the workstation.
Since CUDA was not present I installed it according to this guide and adapted the SDK Makefiles according to this suggestions.
What I am now facing is that not a single sample (I did test like 10 different ones) is running. Those are the errors I am getting:
[deviceQuery] starting...
./deviceQuery Starting...
CUDA Device Query (Runtime API) version (CUDART static linking)
cudaGetDeviceCount returned 10
-> invalid device ordinal
[deviceQuery] test results...
FAILED
> exiting in 3 seconds: 3...2...1...done!
[MonteCarloMultiGPU] starting...
CUDA error at MonteCarloMultiGPU.cpp:235 code=23510 (cudaErrorInvalidDevice) "cudaGetDeviceCount(&GPU_N)"MonteCarloMultiGPU
==================
Parallelization method = threaded
Problem scaling = weak
Number of GPUs = 0
Total number of options = 0
Number of paths = 262144
main(): generating input data...
main(): starting 0 host threads...
Floating point exception (core dumped)
[reduction] starting...
reduction.cpp(124) : cudaSafeCallNoSync() Runtime API error 10 : invalid device ordinal.
[simplePrintf] starting...
simplePrintf.cu(193) : CUDA Runtime API error 10: invalid device ordinal.
As you can see most of the errors are pointing towards a problem with the cudaGetDeviceCount call which return error code 10. According to the manual the problem is:
cudaErrorInvalidDevice: This indicates that the device ordinal supplied by the user does not correspond to a valid CUDA device.
Unfortunately, the only solution I was able to find suggested to check the devices power plugs. I did that and there was nothing wrong with it. Restarting the workstation does not help either.
I'd be happy to supply more details on my configuration. Just leave a comment!
Due to the comments to my original question I was able to find a solution. I followed this guide to learn how to set up the rc.local correctly (don't forget to chmod your script).