Facing issues while launching demo for Oculus SDK 0.6.0.1 - oculus

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.

Related

install openshift on google cloud ( You need to enable virtualization)?

virtualization is enable i've created machine with
gcloud compute instances create openshift-server --enable-nested-virtualization --zone=europe-north1-a --machine-type=e2-standard-4 --image-family=centos-stream-8 --image-project=centos-cloud
i've add libvirt
sudo yum install libvirt
control the cpu virtual active
You need to enable virtualization in BIOS
[n_turri#openshift-server crc-linux-2.9.0-amd64]$ lscpu
Architecture: x86_64
CPU op-mode(s): 32-bit, 64-bit
Byte Order: Little Endian
CPU(s): 4
On-line CPU(s) list: 0-3
Thread(s) per core: 2
Core(s) per socket: 2
Socket(s): 1
NUMA node(s): 1
Vendor ID: GenuineIntel
CPU family: 6
Model: 79
Model name: Intel(R) Xeon(R) CPU # 2.20GHz
Stepping: 0
CPU MHz: 2200.214
BogoMIPS: 4400.42
Hypervisor vendor: KVM
Virtualization type: full
L1d cache: 32K
L1i cache: 32K
L2 cache: 256K
L3 cache: 56320K
NUMA node0 CPU(s): 0-3
but when run the setup
You need to enable virtualization in BIOS ??????
n_turri#openshift-server crc-linux-2.9.0-amd64]$ ./crc setup
INFO Using bundle path /home/n_turri/.crc/cache/crc_libvirt_4.11.3_amd64.crcbundle
INFO Checking if running as non-root
INFO Checking if running inside WSL2
INFO Checking if crc-admin-helper executable is cached
INFO Checking for obsolete admin-helper executable
INFO Checking if running on a supported CPU architecture
INFO Checking minimum RAM requirements
INFO Checking if crc executable symlink exists
INFO Checking if Virtualization is enabled
INFO Setting up virtualization
You need to enable virtualization in BIOS

Memory limit on composer installation

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.

Octave 4.4.1 fails to start on 32 bit Windows 7

Octave 4.0.0 works on Windows 7 32 bit. I have just downloaded 4.4.1 and it has never worked.
Following information:
Problem signature:
Problem Event Name: APPCRASH
Application Name: octave-gui.exe
Application Version: 0.0.0.0
Application Timestamp: 00000000
Fault Module Name: Qt5Core.dll
Fault Module Version: 5.11.0.0
Fault Module Timestamp: 00000000
Exception Code: 40000015
Exception Offset: 002e8696
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 3081
Additional Information 1: d1e0
Additional Information 2: d1e00fdc0b78c108f75564157f84c2f0
Additional Information 3: f785
Additional Information 4: f7855e1e76ad3f0614cfa9b98110597e
Found a vaguely similar problem, failing to start GUI on Windows 10, applied suggested solution of setting "Disable display scaling on high DPI settings" under Compatibility tab of executable Properties.
If you download GNU octave from octave.org you'll see a list:
Windows-64 (recommended)
octave-4.4.1-w64-installer.exe (~ 238 MB) [signature]
octave-4.4.1-w64.7z (~ 267 MB) [signature]
octave-4.4.1-w64.zip (~ 481 MB) [signature]
Windows-32 (old computers)
octave-4.4.1-w32-installer.exe (~ 238 MB) [signature]
octave-4.4.1-w32.7z (~ 267 MB) [signature]
octave-4.4.1-w32.zip (~ 481 MB) [signature]
Of couse a 64bit built will NOT run on a Windoze7 32bit so you have to get octave-4.4.1-w32-installer.exe and install this

Why boot system, load two versions of u-boot?

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.

Oprofile operf is not collecting any data

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