todxx / teamredminer Goto Github PK

Hi todxx,
Great to hear the new release but I am a bit confused about new setting especially interleave? I tried to read at bitcoin org but is not easy to filter the right content bcos some ppl will post e.g L24+24, some posted with * 16*14 but Power usage increased by 7% ( a lot). Some also posted new 1220 Gpu clock ? is this for CNR?
I do hope u gives a message in the help file / OR update the First page the bitcoin org on wht shd be use (simple estimated guideline ).
Some also posted what is this? --CL 19 --RAS 30 --RCDRD 12 --RCDWR 6 --RC 44 --RP 13 --RRDS 5 --RRDL 5 --RTP 4 --FAW 18 --CWL 6 --WTRS 4 --WTRL 9 --WR 15 --WRRD 1 --RDWR 18 --REF 12800 --RFC 248 ?? really confusing.

Hope for new config for 0.44- updated help and config setting.. Pls.
I am still using 0.40 for better pool hash/ stability for my Vega /RX550 rigs.
P/S: any changes for 0.44 on RX550? and can i assumed tht TRM default are using keepalive? do i need to add a parameter?

Pls Advice.

In CNV8_TUNING.txt you give an example of an RX 470 4GB that is starting with 8+8 intensity config.
When I try to start my cards with the same config I get these errors in dmesg:

[TTM] Failed to find memory space for buffer 0x00000000324b2151 eviction
[TTM] No space for 00000000324b2151 (524288 pages, 2097152K, 2048M)
[TTM]   placement[0]=0x00010002 (1)
[TTM]     has_type: 1
[TTM]     use_type: 1
[TTM]     flags: 0x0000000A
[TTM]     gpu_offset: 0x00000000
[TTM]     size: 1048576
[TTM]     available_caching: 0x00070000
[TTM]     default_caching: 0x00010000
[TTM]  0x0000000000000400-0x0000000000000401: 1: used
[TTM]  0x0000000000000401-0x0000000000000405: 4: used
[TTM]  0x0000000000000405-0x0000000000000407: 2: used
[TTM]  0x0000000000000407-0x0000000000000409: 2: used
[TTM]  0x0000000000000409-0x000000000000040b: 2: used
[TTM]  0x000000000000040b-0x000000000000040d: 2: used
[TTM]  0x000000000000040d-0x000000000000040f: 2: used
[TTM]  0x000000000000040f-0x0000000000000411: 2: used
[TTM]  0x0000000000000411-0x0000000000000413: 2: used
[TTM]  0x0000000000000413-0x0000000000000415: 2: used
[TTM]  0x0000000000000415-0x0000000000000417: 2: used
[TTM]  0x0000000000000417-0x0000000000000418: 1: used
[TTM]  0x0000000000000418-0x0000000000000518: 256: used
[TTM]  0x0000000000000518-0x0000000000000519: 1: used
[TTM]  0x0000000000000519-0x000000000000051a: 1: used
[TTM]  0x000000000000051a-0x000000000000051b: 1: used
[TTM]  0x000000000000051b-0x000000000000051c: 1: used
[TTM]  0x000000000000051c-0x000000000000051d: 1: used
[TTM]  0x000000000000051d-0x000000000000051e: 1: used
[TTM]  0x000000000000051e-0x000000000000051f: 1: used
[TTM]  0x000000000000051f-0x0000000000000520: 1: used
[TTM]  0x0000000000000520-0x0000000000000522: 2: used
[TTM]  0x0000000000000522-0x0000000000000524: 2: used
[TTM]  0x0000000000000524-0x0000000000000525: 1: used
[TTM]  0x0000000000000525-0x0000000000000526: 1: used
[TTM]  0x0000000000000526-0x0000000000000527: 1: used
[TTM]  0x0000000000000527-0x0000000000000528: 1: used
[TTM]  0x0000000000000528-0x0000000000000529: 1: used
[TTM]  0x0000000000000529-0x000000000000052a: 1: used
[TTM]  0x000000000000052a-0x00000000000005c7: 157: used
[TTM]  0x00000000000005c7-0x00000000000006c7: 256: used
[TTM]  0x00000000000006c7-0x0000000000010000: 63801: free
[TTM]  total: 64512, used 711 free 63801
[TTM]  man size:1048576 pages, gtt available:523527 pages, usage:2050MB
[drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring comp_1.1.0 timeout, last signaled seq=48181, last emitted seq=48182
[drm] IP block:gmc_v8_0 is hung!
[drm] IP block:tonga_ih is hung!
[drm] IP block:gfx_v8_0 is hung!
[drm] IP block:sdma_v3_0 is hung!
[drm] GPU recovery disabled.
[drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring sdma1 timeout, last signaled seq=178441, last emitted seq=178443
[drm] IP block:gmc_v8_0 is hung!
[drm] IP block:tonga_ih is hung!
[drm] IP block:gfx_v8_0 is hung!
[drm] IP block:sdma_v3_0 is hung!
[drm] GPU recovery disabled.

The max intensity configuration that's working is 8+7.

log isnt created.
0.3.10 works wine

So im running RX 550's underclocked on the gpu core and undervolted on mem/core you can see the levels in the logs. For whatever reason after the miner detects a GPU failure it trys to run the watchdog script to reboot but seems it never gets to it and just locks up. I can still submit kernel commands so I'm not sure whats breaking. If i try to reboot the Kernel reports the process is hung and im forced to do a hard shutdown. Ive tested the watchdog script using the test parameter and works fine before a GPU failure. See my logs below. Search for DEAD.

Mar 27 02:29:23 rig2 mine.sh[1099]: [2019-03-27 02:29:23] Stats Uptime: 0 days, 00:17:31
Mar 27 02:29:23 rig2 mine.sh[1099]: [2019-03-27 02:29:23] GPU 0 monitor: temp=44, fan=28%, 2484 rpm, 915 coreclk, 2000 memclk, 0.856 vddc
Mar 27 02:29:23 rig2 mine.sh[1099]: [2019-03-27 02:29:23] GPU 1 monitor: temp=51, fan=28%, 1045 rpm, 915 coreclk, 2000 memclk, 0.843 vddc
Mar 27 02:29:23 rig2 mine.sh[1099]: [2019-03-27 02:29:23] GPU 2 monitor: temp=48, fan=28%, 2395 rpm, 915 coreclk, 2000 memclk, 0.862 vddc
Mar 27 02:29:23 rig2 mine.sh[1099]: [2019-03-27 02:29:23] GPU 3 monitor: temp=46, fan=28%, 2627 rpm, 915 coreclk, 2000 memclk, 0.850 vddc
Mar 27 02:29:23 rig2 mine.sh[1099]: [2019-03-27 02:29:23] GPU 4 monitor: temp=44, fan=28%, 2333 rpm, 915 coreclk, 2000 memclk, 0.856 vddc
Mar 27 02:29:23 rig2 mine.sh[1099]: [2019-03-27 02:29:23] GPU 5 monitor: temp=46, fan=28%, 2406 rpm, 915 coreclk, 2000 memclk, 0.856 vddc
Mar 27 02:29:23 rig2 mine.sh[1099]: [2019-03-27 02:29:23] GPU 6 monitor: temp=40, fan=0%, 0 rpm, 915 coreclk, 2000 memclk, 0.868 vddc
Mar 27 02:29:23 rig2 mine.sh[1099]: [2019-03-27 02:29:23] GPU 0 [44C, fan 28%] cnr: 505.1 h/s, avg 502.5 h/s, pool 430.8 h/s a:6 r:0 hw:0
Mar 27 02:29:23 rig2 mine.sh[1099]: [2019-03-27 02:29:23] GPU 1 [51C, fan 28%] cnr: 505.4 h/s, avg 502.2 h/s, pool 646.3 h/s a:9 r:0 hw:0
Mar 27 02:29:23 rig2 mine.sh[1099]: [2019-03-27 02:29:23] GPU 2 [48C, fan 28%] cnr: 505.6 h/s, avg 502.3 h/s, pool 359.1 h/s a:5 r:0 hw:0
Mar 27 02:29:23 rig2 mine.sh[1099]: [2019-03-27 02:29:23] GPU 3 [46C, fan 28%] cnr: 505.7 h/s, avg 502.4 h/s, pool 862.1 h/s a:12 r:0 hw:0
Mar 27 02:29:23 rig2 mine.sh[1099]: [2019-03-27 02:29:23] GPU 4 [44C, fan 28%] cnr: 505.3 h/s, avg 502.2 h/s, pool 503.0 h/s a:7 r:0 hw:0
Mar 27 02:29:23 rig2 mine.sh[1099]: [2019-03-27 02:29:23] GPU 5 [46C, fan 28%] cnr: 505.2 h/s, avg 502.3 h/s, pool 934.2 h/s a:13 r:0 hw:0
Mar 27 02:29:23 rig2 mine.sh[1099]: [2019-03-27 02:29:23] GPU 6 [40C, fan 0%] cnr: 506.0 h/s, avg 502.3 h/s, pool 431.3 h/s a:6 r:0 hw:0
Mar 27 02:29:23 rig2 mine.sh[1099]: [2019-03-27 02:29:23] Total cnr: 3.538kh/s, avg 3.516kh/s, pool 4.167kh/s a:58 r:0 hw:0
Mar 27 02:29:23 rig2 mine.sh[1099]: [2019-03-27 02:29:23] Watchdog check.
Mar 27 02:29:23 rig2 mine.sh[1099]: [2019-03-27 02:29:23] Watchdog GPU 0: 4992 new hashes, has thread in enqueue: yes, stuck in init: no, state: 1
Mar 27 02:29:23 rig2 mine.sh[1099]: [2019-03-27 02:29:23] Watchdog GPU 1: 4992 new hashes, has thread in enqueue: yes, stuck in init: no, state: 1
Mar 27 02:29:23 rig2 mine.sh[1099]: [2019-03-27 02:29:23] Watchdog GPU 2: 5376 new hashes, has thread in enqueue: yes, stuck in init: no, state: 1
Mar 27 02:29:23 rig2 mine.sh[1099]: [2019-03-27 02:29:23] Watchdog GPU 3: 5376 new hashes, has thread in enqueue: yes, stuck in init: no, state: 1
Mar 27 02:29:23 rig2 mine.sh[1099]: [2019-03-27 02:29:23] Watchdog GPU 4: 5376 new hashes, has thread in enqueue: yes, stuck in init: no, state: 1
Mar 27 02:29:23 rig2 mine.sh[1099]: [2019-03-27 02:29:23] Watchdog GPU 5: 4992 new hashes, has thread in enqueue: yes, stuck in init: no, state: 1
Mar 27 02:29:23 rig2 mine.sh[1099]: [2019-03-27 02:29:23] Watchdog GPU 6: 4608 new hashes, has thread in enqueue: yes, stuck in init: no, state: 1
Mar 27 02:29:33 rig2 mine.sh[1099]: [2019-03-27 02:29:33] Watchdog check.
Mar 27 02:29:33 rig2 mine.sh[1099]: [2019-03-27 02:29:33] Watchdog GPU 0: 4992 new hashes, has thread in enqueue: yes, stuck in init: no, state: 1
Mar 27 02:29:33 rig2 mine.sh[1099]: [2019-03-27 02:29:33] GPU 0 monitor: temp=44, fan=28%, 2495 rpm, 915 coreclk, 2000 memclk, 0.856 vddc
Mar 27 02:29:33 rig2 mine.sh[1099]: [2019-03-27 02:29:33] GPU 1 monitor: temp=51, fan=28%, 1044 rpm, 915 coreclk, 2000 memclk, 0.843 vddc
Mar 27 02:29:33 rig2 mine.sh[1099]: [2019-03-27 02:29:33] GPU 2 monitor: temp=48, fan=28%, 2385 rpm, 915 coreclk, 2000 memclk, 0.862 vddc
Mar 27 02:29:33 rig2 mine.sh[1099]: [2019-03-27 02:29:33] GPU 3 monitor: temp=46, fan=28%, 2623 rpm, 915 coreclk, 2000 memclk, 0.850 vddc
Mar 27 02:29:33 rig2 mine.sh[1099]: [2019-03-27 02:29:33] GPU 4 monitor: temp=45, fan=28%, 2368 rpm, 915 coreclk, 2000 memclk, 0.856 vddc
Mar 27 02:29:33 rig2 mine.sh[1099]: [2019-03-27 02:29:33] GPU 5 monitor: temp=46, fan=28%, 2403 rpm, 915 coreclk, 2000 memclk, 0.856 vddc
Mar 27 02:29:33 rig2 mine.sh[1099]: [2019-03-27 02:29:33] GPU 6 monitor: temp=38, fan=0%, 0 rpm, 915 coreclk, 2000 memclk, 0.868 vddc
Mar 27 02:29:33 rig2 mine.sh[1099]: [2019-03-27 02:29:33] Watchdog GPU 1: 5376 new hashes, has thread in enqueue: yes, stuck in init: no, state: 1
Mar 27 02:29:33 rig2 mine.sh[1099]: [2019-03-27 02:29:33] Watchdog GPU 2: 4992 new hashes, has thread in enqueue: yes, stuck in init: no, state: 1
Mar 27 02:29:33 rig2 mine.sh[1099]: [2019-03-27 02:29:33] Watchdog GPU 3: 4992 new hashes, has thread in enqueue: yes, stuck in init: no, state: 1
Mar 27 02:29:33 rig2 mine.sh[1099]: [2019-03-27 02:29:33] Watchdog GPU 4: 4992 new hashes, has thread in enqueue: yes, stuck in init: no, state: 1
Mar 27 02:29:33 rig2 mine.sh[1099]: [2019-03-27 02:29:33] Watchdog GPU 5: 5376 new hashes, has thread in enqueue: yes, stuck in init: no, state: 1
Mar 27 02:29:33 rig2 mine.sh[1099]: [2019-03-27 02:29:33] Watchdog GPU 6: 0 new hashes, has thread in enqueue: yes, stuck in init: no, state: 1
Mar 27 02:29:33 rig2 mine.sh[1099]: [2019-03-27 02:29:33] Watchdog GPU 6: stuck in enqueue, reporting.
Mar 27 02:29:33 rig2 mine.sh[1099]: [2019-03-27 02:29:33] Pool pool.supportxmr.com share accepted. (GPU5) (a:59 r:0) (49 ms)
Mar 27 02:29:43 rig2 mine.sh[1099]: [2019-03-27 02:29:43] Watchdog check.
Mar 27 02:29:43 rig2 mine.sh[1099]: [2019-03-27 02:29:43] Watchdog GPU 0: 5376 new hashes, has thread in enqueue: yes, stuck in init: no, state: 1
Mar 27 02:29:43 rig2 mine.sh[1099]: [2019-03-27 02:29:43] GPU 0 monitor: temp=44, fan=28%, 2508 rpm, 915 coreclk, 2000 memclk, 0.856 vddc
Mar 27 02:29:43 rig2 mine.sh[1099]: [2019-03-27 02:29:43] GPU 1 monitor: temp=51, fan=28%, 1044 rpm, 915 coreclk, 2000 memclk, 0.843 vddc
Mar 27 02:29:43 rig2 mine.sh[1099]: [2019-03-27 02:29:43] GPU 2 monitor: temp=48, fan=28%, 2382 rpm, 915 coreclk, 2000 memclk, 0.862 vddc
Mar 27 02:29:43 rig2 mine.sh[1099]: [2019-03-27 02:29:43] GPU 3 monitor: temp=46, fan=28%, 2615 rpm, 915 coreclk, 2000 memclk, 0.850 vddc
Mar 27 02:29:43 rig2 mine.sh[1099]: [2019-03-27 02:29:43] GPU 4 monitor: temp=45, fan=28%, 2336 rpm, 915 coreclk, 2000 memclk, 0.856 vddc
Mar 27 02:29:43 rig2 mine.sh[1099]: [2019-03-27 02:29:43] GPU 5 monitor: temp=46, fan=28%, 2412 rpm, 915 coreclk, 2000 memclk, 0.856 vddc
Mar 27 02:29:43 rig2 mine.sh[1099]: [2019-03-27 02:29:43] GPU 6 monitor: temp=38, fan=0%, 0 rpm, 915 coreclk, 2000 memclk, 0.868 vddc
Mar 27 02:29:43 rig2 mine.sh[1099]: [2019-03-27 02:29:43] Watchdog GPU 1: 4992 new hashes, has thread in enqueue: yes, stuck in init: no, state: 1
Mar 27 02:29:43 rig2 mine.sh[1099]: [2019-03-27 02:29:43] Watchdog GPU 2: 4992 new hashes, has thread in enqueue: yes, stuck in init: no, state: 1
Mar 27 02:29:43 rig2 mine.sh[1099]: [2019-03-27 02:29:43] Watchdog GPU 3: 4992 new hashes, has thread in enqueue: yes, stuck in init: no, state: 1
Mar 27 02:29:43 rig2 mine.sh[1099]: [2019-03-27 02:29:43] Watchdog GPU 4: 4992 new hashes, has thread in enqueue: yes, stuck in init: no, state: 1
Mar 27 02:29:43 rig2 mine.sh[1099]: [2019-03-27 02:29:43] Watchdog GPU 5: 4992 new hashes, has thread in enqueue: yes, stuck in init: no, state: 1
Mar 27 02:29:43 rig2 mine.sh[1099]: [2019-03-27 02:29:43] Watchdog GPU 6: 0 new hashes, has thread in enqueue: yes, stuck in init: no, state: 2
Mar 27 02:29:43 rig2 mine.sh[1099]: [2019-03-27 02:29:43] Watchdog GPU 6: stuck in enqueue, reporting.
Mar 27 02:29:43 rig2 mine.sh[1099]: [2019-03-27 02:29:43] GPU 6: detected DEAD (10:00.0), will execute restart script watchdog.sh
Mar 27 02:30:10 rig2 kernel: usb 1-14: USB disconnect, device number 21
Mar 27 02:30:11 rig2 kernel: usb 1-14: new low-speed USB device number 22 using xhci_hcd
Mar 27 02:30:11 rig2 kernel: usb 1-14: New USB device found, idVendor=04f2, idProduct=0939
Mar 27 02:30:11 rig2 kernel: usb 1-14: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Mar 27 02:30:11 rig2 kernel: usb 1-14: Product: USB Optical Mouse
Mar 27 02:30:11 rig2 kernel: usb 1-14: Manufacturer: PixArt
Mar 27 02:30:11 rig2 kernel: input: PixArt USB Optical Mouse as /devices/pci0000:00/0000:00:14.0/usb1/1-14/1-14:1.0/0003:04F2:0939.0015/input/input35
Mar 27 02:30:11 rig2 kernel: hid-generic 0003:04F2:0939.0015: input,hidraw2: USB HID v1.11 Mouse [PixArt USB Optical Mouse] on usb-0000:00:14.0-14/input0
Mar 27 02:31:09 rig2 systemd[1]: Starting Message of the Day...
Mar 27 02:31:10 rig2 50-motd-news[1736]: * Ubuntu's Kubernetes 1.14 distributions can bypass Docker and use containerd
Mar 27 02:31:10 rig2 50-motd-news[1736]: directly, see https://bit.ly/ubuntu-containerd or try it now with
Mar 27 02:31:10 rig2 50-motd-news[1736]: snap install microk8s --channel=1.14/beta --classic
Mar 27 02:31:10 rig2 systemd[1]: Started Message of the Day.
Mar 27 02:31:11 rig2 kernel: usb 1-14: USB disconnect, device number 22
Mar 27 02:31:13 rig2 kernel: usb 1-14: new low-speed USB device number 23 using xhci_hcd
Mar 27 02:31:13 rig2 kernel: usb 1-14: New USB device found, idVendor=04f2, idProduct=0939
Mar 27 02:31:13 rig2 kernel: usb 1-14: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Mar 27 02:31:13 rig2 kernel: usb 1-14: Product: USB Optical Mouse
Mar 27 02:31:13 rig2 kernel: usb 1-14: Manufacturer: PixArt
Mar 27 02:31:13 rig2 kernel: input: PixArt USB Optical Mouse as /devices/pci0000:00/0000:00:14.0/usb1/1-14/1-14:1.0/0003:04F2:0939.0016/input/input36
Mar 27 02:31:13 rig2 kernel: hid-generic 0003:04F2:0939.0016: input,hidraw2: USB HID v1.11 Mouse [PixArt USB Optical Mouse] on usb-0000:00:14.0-14/input0
Mar 27 02:32:13 rig2 kernel: usb 1-14: USB disconnect, device number 23
Mar 27 02:32:15 rig2 kernel: usb 1-14: new low-speed USB device number 24 using xhci_hcd
Mar 27 02:32:15 rig2 kernel: usb 1-14: New USB device found, idVendor=04f2, idProduct=0939
Mar 27 02:32:15 rig2 kernel: usb 1-14: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Mar 27 02:32:15 rig2 kernel: usb 1-14: Product: USB Optical Mouse
Mar 27 02:32:15 rig2 kernel: usb 1-14: Manufacturer: PixArt
Mar 27 02:32:15 rig2 kernel: input: PixArt USB Optical Mouse as /devices/pci0000:00/0000:00:14.0/usb1/1-14/1-14:1.0/0003:04F2:0939.0017/input/input37
Mar 27 02:32:15 rig2 kernel: hid-generic 0003:04F2:0939.0017: input,hidraw2: USB HID v1.11 Mouse [PixArt USB Optical Mouse] on usb-0000:00:14.0-14/input0
Mar 27 02:33:15 rig2 kernel: usb 1-14: USB disconnect, device number 24
Mar 27 02:33:16 rig2 kernel: usb 1-14: new low-speed USB device number 25 using xhci_hcd
Mar 27 02:33:17 rig2 kernel: usb 1-14: New USB device found, idVendor=04f2, idProduct=0939
Mar 27 02:33:17 rig2 kernel: usb 1-14: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Mar 27 02:33:17 rig2 kernel: usb 1-14: Product: USB Optical Mouse
Mar 27 02:33:17 rig2 kernel: usb 1-14: Manufacturer: PixArt
Mar 27 02:33:17 rig2 kernel: input: PixArt USB Optical Mouse as /devices/pci0000:00/0000:00:14.0/usb1/1-14/1-14:1.0/0003:04F2:0939.0018/input/input38
Mar 27 02:33:17 rig2 kernel: hid-generic 0003:04F2:0939.0018: input,hidraw2: USB HID v1.11 Mouse [PixArt USB Optical Mouse] on usb-0000:00:14.0-14/input0
Mar 27 02:33:25 rig2 kernel: INFO: task teamredminer:1402 blocked for more than 120 seconds.
Mar 27 02:33:25 rig2 kernel: Tainted: G OE 4.15.0-46-generic #49-Ubuntu
Mar 27 02:33:25 rig2 kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Mar 27 02:33:25 rig2 kernel: teamredminer D 0 1402 1099 0x00000000
Mar 27 02:33:25 rig2 kernel: Call Trace:
Mar 27 02:33:25 rig2 kernel: __schedule+0x291/0x8a0
Mar 27 02:33:25 rig2 kernel: schedule+0x2c/0x80
Mar 27 02:33:25 rig2 kernel: rwsem_down_read_failed+0xee/0x150
Mar 27 02:33:25 rig2 kernel: call_rwsem_down_read_failed+0x18/0x30
Mar 27 02:33:25 rig2 kernel: ? call_rwsem_down_read_failed+0x18/0x30
Mar 27 02:33:25 rig2 kernel: down_read+0x20/0x40
Mar 27 02:33:25 rig2 kernel: __do_page_fault+0x43d/0x4d0
Mar 27 02:33:25 rig2 kernel: ? SyS_futex+0x13b/0x180
Mar 27 02:33:25 rig2 kernel: do_page_fault+0x2e/0xe0
Mar 27 02:33:25 rig2 kernel: ? page_fault+0x2f/0x50
Mar 27 02:33:25 rig2 kernel: page_fault+0x45/0x50
Mar 27 02:33:25 rig2 kernel: RIP: 0033:0x7f9d1fb7aa70
Mar 27 02:33:25 rig2 kernel: RSP: 002b:00007f9ccb7fddd0 EFLAGS: 00010203
Mar 27 02:33:25 rig2 kernel: RAX: 00000000000000a1 RBX: 0000000000000004 RCX: 00007f9d1fb7aa66
Mar 27 02:33:25 rig2 kernel: RDX: 0000000000001000 RSI: 00007f9d20913204 RDI: 0000000000000000
Mar 27 02:33:25 rig2 kernel: RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000000
Mar 27 02:33:25 rig2 kernel: R10: 0000000000000000 R11: 0000000000000246 R12: 00007f9d20913204
Mar 27 02:33:25 rig2 kernel: R13: 0000000000001000 R14: 0000000000000000 R15: 0000000000004600
Mar 27 02:33:25 rig2 kernel: INFO: task teamredminer:1404 blocked for more than 120 seconds.
Mar 27 02:33:25 rig2 kernel: Tainted: G OE 4.15.0-46-generic #49-Ubuntu
Mar 27 02:33:25 rig2 kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Mar 27 02:33:25 rig2 kernel: teamredminer D 0 1404 1099 0x00000000
Mar 27 02:33:25 rig2 kernel: Call Trace:
Mar 27 02:33:25 rig2 kernel: __schedule+0x291/0x8a0
Mar 27 02:33:25 rig2 kernel: schedule+0x2c/0x80
Mar 27 02:33:25 rig2 kernel: rwsem_down_read_failed+0xee/0x150
Mar 27 02:33:25 rig2 kernel: call_rwsem_down_read_failed+0x18/0x30
Mar 27 02:33:25 rig2 kernel: ? call_rwsem_down_read_failed+0x18/0x30
Mar 27 02:33:25 rig2 kernel: down_read+0x20/0x40
Mar 27 02:33:25 rig2 kernel: __do_page_fault+0x43d/0x4d0
Mar 27 02:33:25 rig2 kernel: do_page_fault+0x2e/0xe0
Mar 27 02:33:25 rig2 kernel: ? page_fault+0x2f/0x50
Mar 27 02:33:25 rig2 kernel: page_fault+0x45/0x50
Mar 27 02:33:25 rig2 kernel: RIP: 0033:0x7f9d1fb3c9da
Mar 27 02:33:25 rig2 kernel: RSP: 002b:00007f9cca7fb950 EFLAGS: 00010207
Mar 27 02:33:25 rig2 kernel: RAX: 0000000000000000 RBX: 00007f9cca7fba50 RCX: 00007f9d1fb3c9d0
Mar 27 02:33:25 rig2 kernel: RDX: 0000000000000001 RSI: 00007f9cca7fba50 RDI: 0000000000000001
Mar 27 02:33:25 rig2 kernel: RBP: 00007f9cca7fba50 R08: 0000000000000000 R09: 00007f9d209be748
Mar 27 02:33:25 rig2 kernel: R10: 0000000000000000 R11: 0000000000000297 R12: 0000000000000003
Mar 27 02:33:25 rig2 kernel: R13: 0000000000000003 R14: 0000000000000001 R15: 0000000000000003
Mar 27 02:33:25 rig2 kernel: INFO: task teamredminer:1405 blocked for more than 120 seconds.
Mar 27 02:33:25 rig2 kernel: Tainted: G OE 4.15.0-46-generic #49-Ubuntu
Mar 27 02:33:25 rig2 kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Mar 27 02:33:25 rig2 kernel: teamredminer D 0 1405 1099 0x00000000
Mar 27 02:33:25 rig2 kernel: Call Trace:
Mar 27 02:33:25 rig2 kernel: __schedule+0x291/0x8a0
Mar 27 02:33:25 rig2 kernel: schedule+0x2c/0x80
Mar 27 02:33:25 rig2 kernel: schedule_timeout+0x1cf/0x350
Mar 27 02:33:25 rig2 kernel: ? memcg_kmem_charge_memcg+0x7d/0xb0
Mar 27 02:33:25 rig2 kernel: dma_fence_default_wait+0x1c7/0x260
Mar 27 02:33:25 rig2 kernel: ? dma_fence_release+0xa0/0xa0
Mar 27 02:33:25 rig2 kernel: kcl_fence_default_wait+0x12/0x20 [amdkcl]
Mar 27 02:33:25 rig2 kernel: dma_fence_wait_timeout+0x3e/0xf0
Mar 27 02:33:25 rig2 kernel: reservation_object_wait_timeout_rcu+0x17d/0x370
Mar 27 02:33:25 rig2 kernel: amdgpu_mn_invalidate_range_start_gfx+0xa0/0x100 [amdgpu]
Mar 27 02:33:25 rig2 kernel: __mmu_notifier_invalidate_range_start+0x58/0x80
Mar 27 02:33:25 rig2 kernel: copy_page_range+0x650/0x6a0
Mar 27 02:33:25 rig2 kernel: ? memcg_kmem_get_cache+0x5d/0x160
Mar 27 02:33:25 rig2 kernel: ? kmem_cache_alloc+0x158/0x1b0
Mar 27 02:33:25 rig2 kernel: ? anon_vma_fork+0x97/0x130
Mar 27 02:33:25 rig2 kernel: copy_process.part.35+0xd93/0x1b00
Mar 27 02:33:25 rig2 kernel: _do_fork+0xdf/0x400
Mar 27 02:33:25 rig2 kernel: ? SyS_futex+0x13b/0x180
Mar 27 02:33:25 rig2 kernel: ? _cond_resched+0x19/0x40
Mar 27 02:33:25 rig2 kernel: ? task_work_run+0x46/0xc0
Mar 27 02:33:25 rig2 kernel: SyS_clone+0x19/0x20
Mar 27 02:33:25 rig2 kernel: do_syscall_64+0x73/0x130
Mar 27 02:33:25 rig2 kernel: entry_SYSCALL_64_after_hwframe+0x3d/0xa2
Mar 27 02:33:25 rig2 kernel: RIP: 0033:0x7f9d1fb3cb1c
Mar 27 02:33:25 rig2 kernel: RSP: 002b:00007f9cc9ffad50 EFLAGS: 00000246 ORIG_RAX: 0000000000000038
Mar 27 02:33:25 rig2 kernel: RAX: ffffffffffffffda RBX: 00007f9cc9ffad50 RCX: 00007f9d1fb3cb1c
Mar 27 02:33:25 rig2 kernel: RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000001200011
Mar 27 02:33:25 rig2 kernel: RBP: 00007f9cc9ffadc0 R08: 00007f9cc9ffb700 R09: 0000000000000000
Mar 27 02:33:25 rig2 kernel: R10: 00007f9cc9ffb9d0 R11: 0000000000000246 R12: 0000000000000000
Mar 27 02:33:25 rig2 kernel: R13: 0000000000000020 R14: 0000000000000001 R15: 00007f9d207f5118
Mar 27 02:34:17 rig2 kernel: usb 1-14: USB disconnect, device number 25
Mar 27 02:34:18 rig2 kernel: usb 1-14: new low-speed USB device number 26 using xhci_hcd
Mar 27 02:34:18 rig2 kernel: usb 1-14: New USB device found, idVendor=04f2, idProduct=0939
Mar 27 02:34:18 rig2 kernel: usb 1-14: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Mar 27 02:34:18 rig2 kernel: usb 1-14: Product: USB Optical Mouse
Mar 27 02:34:18 rig2 kernel: usb 1-14: Manufacturer: PixArt
Mar 27 02:34:18 rig2 kernel: input: PixArt USB Optical Mouse as /devices/pci0000:00/0000:00:14.0/usb1/1-14/1-14:1.0/0003:04F2:0939.0019/input/input39
Mar 27 02:34:18 rig2 kernel: hid-generic 0003:04F2:0939.0019: input,hidraw2: USB HID v1.11 Mouse [PixArt USB Optical Mouse] on usb-0000:00:14.0-14/input0

t

Windows 10, 1709. Driver 18.5.1 RX550, buffin ,compute 10. OC Core 1185/2000M. currently 440h with Stak.

I tried your TRM and it BSOD upon launching the sw. it managed to initialize all 12 GPus but crash after 15 sec. I hv lowered Core all the way to 1135 but still failed.
Need to look into these. Thanks.

Encountering an initialization failure with 0.4.2 on Ubuntu 16.04 w/rocm:
me@main:/workspace/trm/miner$ ./teamredminer --algo=cnv8_dbl -o stratum+tcp://xcash.luckypool.io:4477 -u 'address' --rig_id='rig id' --devices=0,1 --cn_config=12+12,12+12
Team Red Miner version 0.4.2
[2019-03-16 17:29:17] Auto-detected AMD OpenCL platform 0
[2019-03-16 17:29:17] Failed to initialize device idx 0 (-30)
[2019-03-16 17:29:17] Successful clean shutdown.
me@main:/workspace/trm/miner$ ./teamredminer --list_devices
Team Red Miner version 0.4.2
[2019-03-16 17:29:24] Auto-detected AMD OpenCL platform 0
[2019-03-16 17:29:24] Detected 2 devices, listed in OpenCL order:
[2019-03-16 17:29:24] Miner Platform OpenCL BusId Name Model Nr CUs
[2019-03-16 17:29:24] ----- -------- ------ -------- ------------- ------------------------- ------
[2019-03-16 17:29:24] 0 0 0 03:00.0 gfx900 Vega 10 XT [Radeon RX Veg 64
[2019-03-16 17:29:24] 1 0 1 08:00.0 gfx900 Vega 10 XT [Radeon RX Veg 64
[2019-03-16 17:29:24] Successful clean shutdown.

both clinfo and rocminfo shows the devices and I can get a newly built xmr-stak to run. Any suggestions on debugging steps I can follow to help diagnose this issue?

Hi, would it be possible to add support for cryptonight-pico, Turtlecoin cryptonight variant?

Hi.
I saw this message 20 mins ago (from my posting time) for all my rigs. It was fine yesterday. Can u reconnect after 10 or 30 minutes later else my rigs will be running slow.
The connection closed by your pool. So pls look into tht

Ubuntu, latest AMD driver (amdgpu-pro-18.30-641594):

          Team Red Miner version 0.3.2
failed to build program.
[2018-10-01 20:23:26] Failed to initialize device number 0.

Command:

./teamredminer --algo=lyra2z --url=stratum+tcp://lyra2z.in.nicehash.com:3365 --user=USER --pass=x --platform=0 -d 0

Works correctly with tdxminer.

I am running the miner 0.3.8 under HiveOS using custom package (only 0.3.7 is officially supported). The miner works but logs the "Dev pool failed to connect," message. The rig is behind NAT, but all the internet is accessible from this machine.

Can you suggest what should I check to resolve the issue. I don't have any special firewall rules, but you deserve to get some fee. Please suggest.

Hi @todxx, thanks for your good work,
i'm wondering if you can please provide verification hashes your releases?
It's very important because it's closed sourced code.

teamredminer-v0.4.2-win.zip
SHA256 : 35A36F24A3F2478A70D86FA33484FF1752060829BAFD1FF11C1ED4211BE33D9A
MD5 : E8BECBDAA37FE8108777CFE53523F9E0

Is this correct?

Thanks!

what to do?
This issue is on motherboards with an AMD CPU only

Hello.

Is TRM going to support in the near future the upcoming Graft algorithm change?

https://www.graft.network/2019/01/23/nicehash-attacks-update/

hellow guys ,my 45 devices useing 12 Sapphrie rx550 (12CU) got a problem .normally the hashrate of a single card is about 510h,but some cards' hashrate reduce to 380h with hours running without frequency reduction.the frequency, the temp and the fan speed is all stable.all my devices have got this problem .On average, there are about 3 or 4 of the 12 cards for each machine get this situation.

Not sure if it's my machine or not but version 4.2 seems to be freezing my machines more often on initialization than 4.1 was. On win 10.

Please add bus to gpu information

https://miningpoolstats.stream/uplexa

Initialize error, unknown device name: 'gfx906'

Any plans to support Monero's RandomX?

https://www.reddit.com/r/Monero/comments/b50mfy/logs_from_the_25_hr_dev_meeting_on_moneros_pow/

I cannot use this miner with miningrigrentals on lyra2rev3 algorithm.

First of all, I would like to thank you for your hard work and improvements.
The miner does work for 5 minutes excellently then after 3-5 minutes, it keeps keeps keeps on crashing my windows 10. I do not know the reason why ?!!

My miner commands for GPUs was RX 460:RX550:Vega64 = 4+3 : 4+3 : 15+13

Note that my Vega 64 does not like 16:14 so I had to reduce it to work. but I am happy.
I am not happy than TeamRedminer keeps on crashing my windows.
Please, is there a fix for that?

hi guys
I set api, but unable to monitor on another computer.
teamredminer.exe -a cnv8_rwz -o stratum+tcp://graft.miner.rocks:5005 -u abcd --api_listen=0.0.0.0:12345

example --api_listen=127.0.0.1:12345 or 127.0.0.1:4028 or 0.0.0.0:4028
I've tried them all. I can't monitor them.
Please help me. How should I set it? Thanks.

Hi,
I notice that the Dev pool connects via port 443
Does that mean the dev pool is connecting over TLS/SSL? or is 443 just used by the dev pool to trick firewalls without SSL/TLS actually being used?

If so, is there anyway to similarly enable TLS/SSL for mining pools like supportXMR ?
I tried 443 with SupportXMR with teamredminer, but the pool instantly shuts down the connection.
443 works with other miners like XMRStak just fine with TLS enabled.

Thank you!

VERY LOW hashrate on NEW Vega cards with sgminer - https://github.com/bitbandi/sgminer-timetravel

My Vega64 hashrate - 18 Mh. At the same time, it is not loaded at all.

Please add kernel for Bitmark(Timetravel10)

Know CL files
time10.zip

This may not be a bug/issue. Just thought I would document my experiment.

Distributor ID: Ubuntu
Description: Ubuntu 18.04.1 LTS
Release: 18.04
Codename: bionic

Uninstalled amdgpu-pro-18.40-676022-ubuntu-18.04
Installed ROCm Version: 2.0 (recently released)

clinfo reconized GPUs
teamredminer v0.3.8 did not

Uninstalled ROCm Version: 2.0
Installed amdgpu-pro-18.50-708488-ubuntu-18.04

Back up and running

Is it possible to implement a intensity flag? It would help me to get things stable by lowering intensity on some of my cards.

API failed writing client response.

why?

Pls hello t look into this. Tks bro.

Hi,
I have been testing 0.37 on Win10,1803 , 18.6.1 for the last 3 days. Apparently it crashes on oneof my Vega 56 to 0 hash but the miner still running which is fine. I tried Ctrl c, Ctrl break to stop your mining sw but it got lock up on tht crash Gpu. Task Mgr showing 100%, Sending data as shown in Ethernet port. I force close the cmd screen of trm mining sw but no luck. I hv to poweroff the windows since proper windows shutdown will stuck too.
Anyway, good job and keep up the good work. I do like your miners. lower power consumption and better hash than srb 1.70,xmrig and stak. Most importantly, it is showing more or accurate hash on pool dashboard as compares to SRB.. ya SRB. At least I know tht your mining sw not connecting to your dev pool quietly

1. Need status api on mining sw, I cant even press H to chk hash, connection, fan speed and temp.
2. improve on Stability.
3. Does it allow 2 or mirror pool in bat file?
4. Shutting down properly.

A section in the README stating what are the hashrates that we can expect at certain clock speeds would be helpful.
Thanks.

--help message says "--rigid" but teamredminer implemented "--rig_id". There are no documents using rig identifier so it's better to fix help message.

Hey there again Todxx,

Ubuntu 18.04 | 4.15 | amdgpu-pro 18.30 | Vega Frontier

          Team Red Miner version 0.3.4
[2018-10-30 04:14:00] Dev pool connected and ready.
[2018-10-30 04:14:01] Successfully initialized GPU 0: Vega with 64 CU (PCIe 47:00.0) (CN 16+14)
[2018-10-30 04:14:01] Successfully initialized GPU 1: Vega with 64 CU (PCIe 44:00.0) (CN 16+14)
[2018-10-30 04:14:01] Successfully initialized GPU 2: Vega with 64 CU (PCIe 0f:00.0) (CN 16+14)
[2018-10-30 04:14:02] Successfully initialized GPU 3: Vega with 64 CU (PCIe 0c:00.0) (CN 16+14)
[2018-10-30 04:14:30] Stats GPU 0 - cnv8:   0.0 h/s, avg   0.0 h/s, pool   0.0 h/s 0/0
[2018-10-30 04:14:30] Stats GPU 1 - cnv8:   0.0 h/s, avg   0.0 h/s, pool   0.0 h/s 0/0
[2018-10-30 04:14:30] Stats GPU 2 - cnv8:   0.0 h/s, avg   0.0 h/s, pool   0.0 h/s 0/0
[2018-10-30 04:14:30] Stats GPU 3 - cnv8:   0.0 h/s, avg   0.0 h/s, pool   0.0 h/s 0/0
[2018-10-30 04:14:30] Stats Total - cnv8:   0.0 h/s, avg   0.0 h/s, pool   0.0 h/s

Rig currently working with other miners, what could be responsible?

Hi, would it be possible to add support for cryptonight-ryo !
https://miningpoolstats.stream/ryo
https://ryo-currency.com/
https://github.com/ryo-currency/ryo-currency
https://discord.gg/ryD9bdb
https://www.coingecko.com/en/coins/ryo

Aren't you have plans to open your sources?

Team Red 0.3.6 showing 0 hashrate and crashing system after closing it. Bug appears only on CryptonightV8 algo.

Quake4/MindMiner#269

Details:

GPU0 is PCIe 02:00.0
GPU1 is PCIe 01:00.0

Edit:
Is this supposed to work like this? Adding --bus_reorder reverted to the expected behavior.

Hello.

Please add a simple TCP monitoring API, at least global hashrate. I have a script that updates algo changes based on hashrate, I need it to run benchmarks.

And thanks for your great miner! 🥇

Hey Todxx,

Ubuntu 4.18/4.19 | ROCm 1.9.1 | Vega Frontier

Same settings used in v0.3.1 segfaullts in v0.3.3. Any changes to be aware of? Faults regardless of algo.

./lux: line 1: 3797 Segmentation fault (core dumped)

I have 7 RX580's and 1 Vega 64 (I know, weird setup). First run was running great, then the next time I ran the miner the Vega64 disappeared from both Device Managers (checked hidden) and is nowhere to be found. Weird... Anyone have a similar experience before I reinstall drivers?

I've tried the 3 rpc commands but they either make hashrate go to 0 or do nothing at all

Been trying to figure out for hours with no luck.
Would appreciate a mac version with installer style setup. ( a linux noob ).
Hope to see it asap. Am ready when you are! : )

Hi,
Hash from miner lower than previous cnv8 from 524 to 499 which is not too bad but pool reporting only +-460. My vega’s rigs all works fine even after deducted the dev fee and report accordingly. Pls help to look into some tuning of your next release for 550 2gb. Using the same L2+3. 1159core /2000 mem

Tks

Ubuntu, testing on AMD driver (amdgpu-pro-18.30-641594, amdgpu-pro-18.40-676022):

          Team Red Miner version 0.3.4
failed to create kernel.
[2018-10-30 21:35:46] Failed to initialize device number 0.

Command:

./teamredminer -a cnv8 -o stratum+tcp://xmr-eu2.nanopool.org:14444 \
    -u USER -p x -d 0 --cn_config 14+14

I try with --platform=1 but I see error Platform argument is outside of range of available OpenCL platforms.

Works correctly with phi algo.

$ clinfo
Number of platforms:				 1
  Platform Profile:				 FULL_PROFILE
  Platform Version:				 OpenCL 2.1 AMD-APP (2679.0)
  Platform Name:				 AMD Accelerated Parallel Processing
  Platform Vendor:				 Advanced Micro Devices, Inc.
  Platform Extensions:				 cl_khr_icd cl_amd_event_callback


  Platform Name:				 AMD Accelerated Parallel Processing
Number of devices:				 1
  Device Type:					 CL_DEVICE_TYPE_GPU
  Vendor ID:					 1002h
  Board name:					 Vega [Radeon RX Vega]
  Device Topology:				 PCI[ B#3, D#0, F#0 ]
  Max compute units:				 56
  Max work items dimensions:			 3
    Max work items[0]:				 1024
    Max work items[1]:				 1024
    Max work items[2]:				 1024
  Max work group size:				 256
  Preferred vector width char:			 4
  Preferred vector width short:			 2
  Preferred vector width int:			 1
  Preferred vector width long:			 1
  Preferred vector width float:			 1
  Preferred vector width double:		 1
  Native vector width char:			 4
  Native vector width short:			 2
  Native vector width int:			 1
  Native vector width long:			 1
  Native vector width float:			 1
  Native vector width double:			 1
  Max clock frequency:				 1590Mhz
  Address bits:					 64
  Max memory allocation:			 7287183769
  Image support:				 Yes
  Max number of images read arguments:		 128
  Max number of images write arguments:		 8
  Max image 2D width:				 16384
  Max image 2D height:				 16384
  Max image 3D width:				 2048
  Max image 3D height:				 2048
  Max image 3D depth:				 2048
  Max samplers within kernel:			 26751
  Max size of kernel argument:			 1024
  Alignment (bits) of base address:		 1024
  Minimum alignment (bytes) for any datatype:	 128
  Single precision floating point capability
    Denorms:					 Yes
    Quiet NaNs:					 Yes
    Round to nearest even:			 Yes
    Round to zero:				 Yes
    Round to +ve and infinity:			 Yes
    IEEE754-2008 fused multiply-add:		 Yes
  Cache type:					 Read/Write
  Cache line size:				 64
  Cache size:					 16384
  Global memory size:				 8573157376
  Constant buffer size:				 7287183769
  Max number of constant args:			 8
  Local memory type:				 Scratchpad
  Local memory size:				 65536
  Max pipe arguments:				 16
  Max pipe active reservations:			 16
  Max pipe packet size:				 2992216473
  Max global variable size:			 7287183769
  Max global variable preferred total size:	 8573157376
  Max read/write image args:			 64
  Max on device events:				 1024
  Queue on device max size:			 8388608
  Max on device queues:				 1
  Queue on device preferred size:		 262144
  SVM capabilities:
    Coarse grain buffer:			 Yes
    Fine grain buffer:				 Yes
    Fine grain system:				 No
    Atomics:					 No
  Preferred platform atomic alignment:		 0
  Preferred global atomic alignment:		 0
  Preferred local atomic alignment:		 0
  Kernel Preferred work group size multiple:	 64
  Error correction support:			 0
  Unified memory for Host and Device:		 0
  Profiling timer resolution:			 1
  Device endianess:				 Little
  Available:					 Yes
  Compiler available:				 Yes
  Execution capabilities:
    Execute OpenCL kernels:			 Yes
    Execute native function:			 No
  Queue on Host properties:
    Out-of-Order:				 No
    Profiling :					 Yes
  Queue on Device properties:
    Out-of-Order:				 Yes
    Profiling :					 Yes
  Platform ID:					 0x7f89aabe6df0
  Name:						 gfx900
  Vendor:					 Advanced Micro Devices, Inc.
  Device OpenCL C version:			 OpenCL C 2.0
  Driver version:				 2679.0 (HSA1.1,LC)
  Profile:					 FULL_PROFILE
  Version:					 OpenCL 1.2
  Extensions:					 cl_khr_fp64 cl_khr_global_int32_base_atomics cl_khr_global_int32_extended_atomics cl_khr_local_int32_base_atomics cl_khr_local_int32_extended_atomics cl_khr_int64_base_atomics cl_khr_int64_extended_atomics cl_khr_3d_image_writes cl_khr_byte_addressable_store cl_khr_fp16 cl_khr_gl_sharing cl_amd_device_attribute_query cl_amd_media_ops cl_amd_media_ops2 cl_khr_subgroups cl_khr_depth_images cl_amd_copy_buffer_p2p cl_amd_assembly_program

after update to cnr,my rx550 2g work on ubuntu 18.04 and amdgpu-pro 18.5 only offer about 350 hash rate ,it can be about 500 at cnv8, are there some bug in this version?

All rigs with ASUS ROG RX580 have initialization Issues and the miner starts successfully only about one in ten times. Also cards ASUS ROG RX570 work fully successfully.
Please correct!