Xmr Stops working , hwloc: memory pinned but memory access error

Running 4.13.0-kali1-amd64 #1 SMP Debian 4.13.13-1kali1 (2017-11-17) x86_64 GNU/Linux

self complied from latest rel source::

-- The C compiler identification is Clang 4.0.1 -- The CXX compiler identification is Clang 4.0.1 -- Check for working C compiler: /usr/bin/clang-4.0 -- Check for working C compiler: /usr/bin/clang-4.0 -- works -- Detecting C compiler ABI info -- Detecting C compiler ABI info - done -- Detecting C compile features -- Detecting C compile features - done -- Check for working CXX compiler: /usr/bin/clang++-4.0 -- Check for working CXX compiler: /usr/bin/clang++-4.0 -- works -- Detecting CXX compiler ABI info -- Detecting CXX compiler ABI info - done -- Detecting CXX compile features -- Detecting CXX compile features - done -- Set miner currency to 'monero' and 'aeon' -- Looking for pthread.h -- Looking for pthread.h - found -- Looking for pthread_create -- Looking for pthread_create - not found -- Looking for pthread_create in pthreads -- Looking for pthread_create in pthreads - not found -- Looking for pthread_create in pthread -- Looking for pthread_create in pthread - found -- Found Threads: TRUE
-- Found CUDA: /usr/local/cuda (found suitable version "8.0", minimum required is "7.5") -- Found OpenSSL: /usr/lib/x86_64-linux-gnu/libcrypto.so (found version "1.1.0g") fatal: Kein Git-Repository (oder irgendein Elternverzeichnis): .git fatal: Kein Git-Repository (oder irgendein Elternverzeichnis): .git -- Configuring done -- Generating done -- Build files have been written to: /root/xmr-stak-2.0.0/build root@H4XU:~/xmr-stak-2.0.0/build# make install Scanning dependencies of target xmr-stak-c [ 3%] Building C object CMakeFiles/xmr-stak-c.dir/xmrstak/backend/cpu/crypto/c_blake256.c.o [ 6%] Building C object CMakeFiles/xmr-stak-c.dir/xmrstak/backend/cpu/crypto/c_groestl.c.o [ 10%] Building C object CMakeFiles/xmr-stak-c.dir/xmrstak/backend/cpu/crypto/c_jh.c.o [ 13%] Building C object CMakeFiles/xmr-stak-c.dir/xmrstak/backend/cpu/crypto/c_keccak.c.o [ 16%] Building C object CMakeFiles/xmr-stak-c.dir/xmrstak/backend/cpu/crypto/c_skein.c.o [ 20%] Linking C static library bin/libxmr-stak-c.a [ 20%] Built target xmr-stak-c Scanning dependencies of target xmr-stak-backend [ 23%] Building CXX object CMakeFiles/xmr-stak-backend.dir/xmrstak/jconf.cpp.o /root/xmr-stak-2.0.0/xmrstak/jconf.cpp:161:1: warning: control may reach end of non-void function [-Wreturn-type] } ^ 1 warning generated. [ 26%] Building CXX object CMakeFiles/xmr-stak-backend.dir/xmrstak/version.cpp.o [ 30%] Building CXX object CMakeFiles/xmr-stak-backend.dir/xmrstak/backend/cpu/hwlocMemory.cpp.o [ 33%] Building CXX object CMakeFiles/xmr-stak-backend.dir/xmrstak/backend/cpu/jconf.cpp.o [ 36%] Building CXX object CMakeFiles/xmr-stak-backend.dir/xmrstak/backend/cpu/minethd.cpp.o [ 40%] Building CXX object CMakeFiles/xmr-stak-backend.dir/xmrstak/backend/backendConnector.cpp.o [ 43%] Building CXX object CMakeFiles/xmr-stak-backend.dir/xmrstak/backend/globalStates.cpp.o [ 46%] Building CXX object CMakeFiles/xmr-stak-backend.dir/xmrstak/backend/cpu/crypto/cryptonight_common.cpp.o [ 50%] Building CXX object CMakeFiles/xmr-stak-backend.dir/xmrstak/http/httpd.cpp.o [ 53%] Building CXX object CMakeFiles/xmr-stak-backend.dir/xmrstak/http/webdesign.cpp.o [ 56%] Building CXX object CMakeFiles/xmr-stak-backend.dir/xmrstak/misc/console.cpp.o [ 60%] Building CXX object CMakeFiles/xmr-stak-backend.dir/xmrstak/misc/executor.cpp.o [ 63%] Building CXX object CMakeFiles/xmr-stak-backend.dir/xmrstak/misc/telemetry.cpp.o [ 66%] Building CXX object CMakeFiles/xmr-stak-backend.dir/xmrstak/misc/utility.cpp.o [ 70%] Building CXX object CMakeFiles/xmr-stak-backend.dir/xmrstak/net/jpsock.cpp.o [ 73%] Building CXX object CMakeFiles/xmr-stak-backend.dir/xmrstak/net/socket.cpp.o [ 76%] Linking CXX static library bin/libxmr-stak-backend.a [ 76%] Built target xmr-stak-backend Scanning dependencies of target xmrstak_cuda_backend [ 80%] Building CXX object CMakeFiles/xmrstak_cuda_backend.dir/xmrstak/backend/nvidia/nvcc_code/cuda_core.cu.o [ 83%] Building CXX object CMakeFiles/xmrstak_cuda_backend.dir/xmrstak/backend/nvidia/nvcc_code/cuda_extra.cu.o [ 86%] Building CXX object CMakeFiles/xmrstak_cuda_backend.dir/xmrstak/backend/nvidia/jconf.cpp.o [ 90%] Building CXX object CMakeFiles/xmrstak_cuda_backend.dir/xmrstak/backend/nvidia/minethd.cpp.o [ 93%] Linking CXX shared library bin/libxmrstak_cuda_backend.so [ 93%] Built target xmrstak_cuda_backend Scanning dependencies of target xmr-stak [ 96%] Building CXX object CMakeFiles/xmr-stak.dir/xmrstak/cli/cli-miner.cpp.o [100%] Linking CXX executable bin/xmr-stak [100%] Built target xmr-stak Install the project... -- Install configuration: "Release" xmr-stak installed to folder 'bin'

-----> STARTING XMR:

xmr-stak 2.0.0 79154f7

Brought to you by fireice_uk and psychocrypt under GPLv3. Based on CPU mining code by wolf9466 (heavily optimized by fireice_uk). Based on NVIDIA mining code by KlausT and psychocrypt.

Configurable dev donation level is set to 0.0%

You can use following keys to display reports: 'h' - hashrate 'r' - results 'c' - connection

[2017-11-22 20:54:46] : Start mining: MONERO [2017-11-22 20:54:46] : Starting NVIDIA GPU thread 0, affinity: 0. [2017-11-22 20:54:46] : hwloc: memory pinned [2017-11-22 20:54:46] : Starting single thread, affinity: 1. [2017-11-22 20:54:46] : hwloc: memory pinned [2017-11-22 20:54:46] : Starting single thread, affinity: 2. [2017-11-22 20:54:46] : hwloc: memory pinned [2017-11-22 20:54:46] : Starting single thread, affinity: 3. [2017-11-22 20:54:46] : hwloc: memory pinned Speicherzugriffsfehler (means mem access error)

tried all suggested changes and Settings: setting sudo sysctl -w vm.nr_hugepages=128" add following lines to /etc/security/limits.conf - " soft memlock 262144" and "* hard memlock 262144". does not help changing affinity is not working setting use_slow_mem to warn or no_mlck or always is not working setting deamon ist not working i really tried all possible setting changes now , it gives still the same error ... rebooting , running as root is also not helping. Please help

-------------------------->cpu.txt

Thread configuration for each thread. Make sure it matches the number above.
low_power_mode - This mode will double the cache usage, and double the single thread performance. It will
consume much less power (as less cores are working), but will max out at around 80-85% of
the maximum performance.
no_prefetch - Some sytems can gain up to extra 5% here, but sometimes it will have no difference or make
things slower.
affine_to_cpu - This can be either false (no affinity), or the CPU core number. Note that on hyperthreading
systems it is better to assign threads to physical cores. On Windows this usually means selecting
even or odd numbered cpu numbers. For Linux it will be usually the lower CPU numbers, so for a 4
physical core CPU you should select cpu numbers 0-3.
On the first run the miner will look at your system and suggest a basic configuration that will work,
you can try to tweak it from there to get the best performance.
A filled out configuration should look like this:
"cpu_threads_conf" :
[
{ "low_power_mode" : false, "no_prefetch" : true, "affine_to_cpu" : 0 },
{ "low_power_mode" : false, "no_prefetch" : true, "affine_to_cpu" : 1 },
], */

"cpu_threads_conf" : [ { "low_power_mode" : false, "no_prefetch" : true, "affine_to_cpu" : 0 }, { "low_power_mode" : false, "no_prefetch" : true, "affine_to_cpu" : 1 }, { "low_power_mode" : false, "no_prefetch" : true, "affine_to_cpu" : 2 },

---------------------------------> nvidia.txt

GPU configuration. You should play around with threads and blocks as the fastest settings will vary.
index - GPU index number usually starts from 0.
threads - Number of GPU threads (nothing to do with CPU threads).
blocks - Number of GPU blocks (nothing to do with CPU threads).
bfactor - Enables running the Cryptonight kernel in smaller pieces.
Increase if you want to reduce GPU lag. Recommended setting on GUI systems - 8
bsleep - Insert a delay of X microseconds between kernel launches.
Increase if you want to reduce GPU lag. Recommended setting on GUI systems - 100
affine_to_cpu - This will affine the thread to a CPU. This can make a GPU miner play along nicer with a CPU miner.
On the first run the miner will look at your system and suggest a basic configuration that will work,
you can try to tweak it from there to get the best performance.
A filled out configuration should look like this:
"gpu_threads_conf" :
[
{ "index" : 0, "threads" : 17, "blocks" : 60, "bfactor" : 0, "bsleep" : 0, "affine_to_cpu" : false},
], */

"gpu_threads_conf" : [ // gpu: GeForce GTX 570 architecture: 20 // memory: 987/1218 MiB // smx: 15 { "index" : 0, "threads" : 14, "blocks" : 30, "bfactor" : 8, "bsleep" : 100, "affine_to_cpu" : false, },

---------------------------> config.txt

pool_address - Pool address should be in the form "pool.supportxmr.com:3333". Only stratum pools are supported.
wallet_address - Your wallet, or pool login.
pool_password - Can be empty in most cases or "x".
use_nicehash - Limit the nonce to 3 bytes as required by nicehash.
use_tls - This option will make us connect using Transport Layer Security.
tls_fingerprint - Server's SHA256 fingerprint. If this string is non-empty then we will check the server's cert against it.
pool_weight - Pool weight is a number telling the miner how important the pool is. Miner will mine mostly at the pool
with the highest weight, unless the pool fails. Weight must be an integer larger than 0.
We feature pools up to 1MH/s. For a more complete list see M5M400's pool list at www.moneropools.com */ "pool_list" : [ {"pool_address" : "mine.moneropool.com:3333", "wallet_address" : "42XnjKQ7Lj38XWddgvXMs31XSq6cpu5TpPnv1LLcZpe5hykcWzac5YwZ6wmDeKvBQkhBwcwsF1pHcBUbK52T6P5PQPGsBkT", "pool_password" : "x", "use_nicehash" : false, "use_tls" : false, "tls_fingerprint" : "", "pool_weight" : 1 }, ],

currency to mine
allowed values: 'monero' or 'aeon' */ "currency" : "monero",

Network timeouts.
Because of the way this client is written it doesn't need to constantly talk (keep-alive) to the server to make
sure it is there. We detect a buggy / overloaded server by the call timeout. The default values will be ok for
nearly all cases. If they aren't the pool has most likely overload issues. Low call timeout values are preferable -
long timeouts mean that we waste hashes on potentially stale jobs. Connection report will tell you how long the
server usually takes to process our calls.
call_timeout - How long should we wait for a response from the server before we assume it is dead and drop the connection.
retry_time - How long should we wait before another connection attempt.
Both values are in seconds.
giveup_limit - Limit how many times we try to reconnect to the pool. Zero means no limit. Note that stak miners
don't mine while the connection is lost, so your computer's power usage goes down to idle. */ "call_timeout" : 10, "retry_time" : 30, "giveup_limit" : 0,

Output control.
Since most people are used to miners printing all the time, that's what we do by default too. This is suboptimal
really, since you cannot see errors under pages and pages of text and performance stats. Given that we have internal
performance monitors, there is very little reason to spew out pages of text instead of concise reports.
Press 'h' (hashrate), 'r' (results) or 'c' (connection) to print reports.
verbose_level - 0 - Don't print anything.
1 - Print intro, connection event, disconnect event
2 - All of level 1, and new job (block) event if the difficulty is different from the last job
3 - All of level 1, and new job (block) event in all cases, result submission event.
4 - All of level 3, and automatic hashrate report printing
print_motd - Display messages from your pool operator in the hashrate result. */ "verbose_level" : 3, "print_motd" : true,

Automatic hashrate report
h_print_time - How often, in seconds, should we print a hashrate report if verbose_level is set to 4.
This option has no effect if verbose_level is not 4. */ "h_print_time" : 60,

Manual hardware AES override
Some VMs don't report AES capability correctly. You can set this value to true to enforce hardware AES or
to false to force disable AES or null to let the miner decide if AES is used.
WARNING: setting this to true on a CPU that doesn't support hardware AES will crash the miner. */ "aes_override" : null,

LARGE PAGE SUPPORT
Large pages need a properly set up OS. It can be difficult if you are not used to systems administration,
but the performance results are worth the trouble - you will get around 20% boost. Slow memory mode is
meant as a backup, you won't get stellar results there. If you are running into trouble, especially
on Windows, please read the common issues in the README.
By default we will try to allocate large pages. This means you need to "Run As Administrator" on Windows.
You need to edit your system's group policies to enable locking large pages. Here are the steps from MSDN
1. On the Start menu, click Run. In the Open box, type gpedit.msc.
1. On the Local Group Policy Editor console, expand Computer Configuration, and then expand Windows Settings.
1. Expand Security Settings, and then expand Local Policies.
1. Select the User Rights Assignment folder.
1. The policies will be displayed in the details pane.
1. In the pane, double-click Lock pages in memory.
1. In the Local Security Setting – Lock pages in memory dialog box, click Add User or Group.
1. In the Select Users, Service Accounts, or Groups dialog box, add an account that you will run the miner on
1. Reboot for change to take effect.
Windows also tends to fragment memory a lot. If you are running on a system with 4-8GB of RAM you might need
to switch off all the auto-start applications and reboot to have a large enough chunk of contiguous memory.
On Linux you will need to configure large page support "sudo sysctl -w vm.nr_hugepages=128" and increase your
ulimit -l. To do do this you need to add following lines to /etc/security/limits.conf - "* soft memlock 262144"
and "* hard memlock 262144". You can also do it Windows-style and simply run-as-root, but this is NOT
recommended for security reasons.
Memory locking means that the kernel can't swap out the page to disk - something that is unlikely to happen on a
command line system that isn't starved of memory. I haven't observed any difference on a CLI Linux system between
locked and unlocked memory. If that is your setup see option "no_mlck". */

use_slow_memory defines our behaviour with regards to large pages. There are three possible options here:
always - Don't even try to use large pages. Always use slow memory.
warn - We will try to use large pages, but fall back to slow memory if that fails.
no_mlck - This option is only relevant on Linux, where we can use large pages without locking memory.
It will never use slow memory, but it won't attempt to mlock
never - If we fail to allocate large pages we will print an error and exit. */ "use_slow_memory" : "warn",

TLS Settings
If you need real security, make sure tls_secure_algo is enabled (otherwise MITM attack can downgrade encryption
to trivially breakable stuff like DES and MD5), and verify the server's fingerprint through a trusted channel.
tls_secure_algo - Use only secure algorithms. This will make us quit with an error if we can't negotiate a secure algo. */ "tls_secure_algo" : true,

Daemon mode
If you are running the process in the background and you don't need the keyboard reports, set this to true.
This should solve the hashrate problems on some emulated terminals. */ "daemon_mode" : false,

Buffered output control.
When running the miner through a pipe, standard output is buffered. This means that the pipe won't read
each output line immediately. This can cause delays when running in background.
Set this option to true to flush stdout after each line, so it can be read immediately. */ "flush_stdout" : false,

Output file
output_file - This option will log all output to a file.
*/ "output_file" : "",

Built-in web server
I like checking my hashrate on my phone. Don't you?
Keep in mind that you will need to set up port forwarding on your router if you want to access it from
outside of your home network. Ports lower than 1024 on Linux systems will require root.
httpd_port - Port we should listen on. Default, 0, will switch off the server. */ "httpd_port" : 0,

HTTP Authentication
This allows you to set a password to keep people on the Internet from snooping on your hashrate.
Keep in mind that this is based on HTTP Digest, which is based on MD5. To a determined attacker
who is able to read your traffic it is as easy to break a bog door latch.
http_login - Login. Empty login disables authentication.
http_pass - Password. */ "http_login" : "", "http_pass" : "",

prefer_ipv4 - IPv6 preference. If the host is available on both IPv4 and IPv6 net, which one should be choose?
This setting will only be needed in 2020's. No need to worry about it now. */ "prefer_ipv4" : true,

fireice-uk / xmr-stak

Xmr Stops working , hwloc: memory pinned but memory access error #210

-----> STARTING XMR:

You can use following keys to display reports: 'h' - hashrate 'r' - results 'c' - connection