S9i keeps restarting

[mortadeli]

Hi there.

One of my S9i's keeps restarting. Tried restarting, different power/ethernet cables, latest firmware, software/hardware reset, different power/hash rate settings.

Any thoughts?

Code:

[    0.000000] Booting Linux on physical CPU 0x0
[    0.000000] Linux version 3.14.0-xilinx-g16220c3 (lzq@armdev2) (gcc version 4.8.3 20140320 (prerelease) (Sourcery CodeBench Lite 2014.05-23) ) #83 SMP PREEMPT Thu Jul 12 11:42:53 CST 2018
[    0.000000] CPU: ARMv7 Processor [413fc090] revision 0 (ARMv7), cr=18c5387d
[    0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
[    0.000000] Machine model: Xilinx Zynq
[    0.000000] cma: CMA: reserved 128 MiB at 16800000
[    0.000000] Memory policy: Data cache writealloc
[    0.000000] On node 0 totalpages: 126976
[    0.000000] free_area_init_node: node 0, pgdat c074ac00, node_mem_map debd8000
[    0.000000]   Normal zone: 992 pages used for memmap
[    0.000000]   Normal zone: 0 pages reserved
[    0.000000]   Normal zone: 126976 pages, LIFO batch:31
[    0.000000] PERCPU: Embedded 8 pages/cpu @debc1000 s9088 r8192 d15488 u32768
[    0.000000] pcpu-alloc: s9088 r8192 d15488 u32768 alloc=8*4096
[    0.000000] pcpu-alloc: [0] 0 [0] 1 
[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 125984
[    0.000000] Kernel command line: noinitrd mem=496M console=ttyPS0,115200 root=ubi0:rootfs ubi.mtd=1 rootfstype=ubifs rw rootwait
[    0.000000] PID hash table entries: 2048 (order: 1, 8192 bytes)
[    0.000000] Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
[    0.000000] Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
[    0.000000] Memory: 364316K/507904K available (5057K kernel code, 284K rwdata, 1928K rodata, 204K init, 258K bss, 143588K reserved, 0K highmem)
[    0.000000] Virtual kernel memory layout:
[    0.000000]     vector  : 0xffff0000 - 0xffff1000   (   4 kB)
[    0.000000]     fixmap  : 0xfff00000 - 0xfffe0000   ( 896 kB)
[    0.000000]     vmalloc : 0xdf800000 - 0xff000000   ( 504 MB)
[    0.000000]     lowmem  : 0xc0000000 - 0xdf000000   ( 496 MB)
[    0.000000]     pkmap   : 0xbfe00000 - 0xc0000000   (   2 MB)
[    0.000000]     modules : 0xbf000000 - 0xbfe00000   (  14 MB)
[    0.000000]       .text : 0xc0008000 - 0xc06da8ac   (6987 kB)
[    0.000000]       .init : 0xc06db000 - 0xc070e380   ( 205 kB)
[    0.000000]       .data : 0xc0710000 - 0xc0757138   ( 285 kB)
[    0.000000]        .bss : 0xc0757144 - 0xc0797bfc   ( 259 kB)
[    0.000000] Preemptible hierarchical RCU implementation.
[    0.000000] 	Dump stacks of tasks blocking RCU-preempt GP.
[    0.000000] 	RCU restricting CPUs from NR_CPUS=4 to nr_cpu_ids=2.
[    0.000000] RCU: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=2
[    0.000000] NR_IRQS:16 nr_irqs:16 16
[    0.000000] ps7-slcr mapped to df802000
[    0.000000] zynq_clock_init: clkc starts at df802100
[    0.000000] Zynq clock init
[    0.000014] sched_clock: 64 bits at 333MHz, resolution 3ns, wraps every 3298534883328ns
[    0.000293] ps7-ttc #0 at df804000, irq=43
[    0.000599] Console: colour dummy device 80x30
[    0.000630] Calibrating delay loop... 1332.01 BogoMIPS (lpj=6660096)
[    0.090240] pid_max: default: 32768 minimum: 301
[    0.090448] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
[    0.090467] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
[    0.092648] CPU: Testing write buffer coherency: ok
[    0.092963] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
[    0.093019] Setting up static identity map for 0x4cb118 - 0x4cb170
[    0.093237] L310 cache controller enabled
[    0.093257] l2x0: 8 ways, CACHE_ID 0x410000c8, AUX_CTRL 0x72760000, Cache size: 512 kB
[    0.170984] CPU1: Booted secondary processor
[    0.260216] CPU1: thread -1, cpu 1, socket 0, mpidr 80000001
[    0.260345] Brought up 2 CPUs
[    0.260364] SMP: Total of 2 processors activated.
[    0.260373] CPU: All CPU(s) started in SVC mode.
[    0.261030] devtmpfs: initialized
[    0.263465] VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4
[    0.264666] regulator-dummy: no parameters
[    0.272064] NET: Registered protocol family 16
[    0.274338] DMA: preallocated 256 KiB pool for atomic coherent allocations
[    0.276606] cpuidle: using governor ladder
[    0.276619] cpuidle: using governor menu
[    0.284002] syscon f8000000.ps7-slcr: regmap [mem 0xf8000000-0xf8000fff] registered
[    0.285523] hw-breakpoint: found 5 (+1 reserved) breakpoint and 1 watchpoint registers.
[    0.285537] hw-breakpoint: maximum watchpoint size is 4 bytes.
[    0.285648] zynq-ocm f800c000.ps7-ocmc: ZYNQ OCM pool: 256 KiB @ 0xdf880000
[    0.307477] bio: create slab <bio-0> at 0
[    0.308871] vgaarb: loaded
[    0.309557] SCSI subsystem initialized
[    0.310823] usbcore: registered new interface driver usbfs
[    0.310999] usbcore: registered new interface driver hub
[    0.311682] usbcore: registered new device driver usb
[    0.312206] media: Linux media interface: v0.10
[    0.312369] Linux video capture interface: v2.00
[    0.312617] pps_core: LinuxPPS API ver. 1 registered
[    0.312629] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
[    0.312752] PTP clock support registered
[    0.313103] EDAC MC: Ver: 3.0.0
[    0.314294] Advanced Linux Sound Architecture Driver Initialized.
[    0.317011] DMA-API: preallocated 4096 debug entries
[    0.317025] DMA-API: debugging enabled by kernel config
[    0.317097] Switched to clocksource arm_global_timer
[    0.337367] NET: Registered protocol family 2
[    0.338082] TCP established hash table entries: 4096 (order: 2, 16384 bytes)
[    0.338139] TCP bind hash table entries: 4096 (order: 3, 32768 bytes)
[    0.338224] TCP: Hash tables configured (established 4096 bind 4096)
[    0.338271] TCP: reno registered
[    0.338288] UDP hash table entries: 256 (order: 1, 8192 bytes)
[    0.338319] UDP-Lite hash table entries: 256 (order: 1, 8192 bytes)
[    0.338556] NET: Registered protocol family 1
[    0.338905] RPC: Registered named UNIX socket transport module.
[    0.338919] RPC: Registered udp transport module.
[    0.338927] RPC: Registered tcp transport module.
[    0.338935] RPC: Registered tcp NFSv4.1 backchannel transport module.
[    0.338947] PCI: CLS 0 bytes, default 64
[    0.339384] hw perfevents: enabled with ARMv7 Cortex-A9 PMU driver, 7 counters available
[    0.341386] futex hash table entries: 512 (order: 3, 32768 bytes)
[    0.343453] jffs2: version 2.2. (NAND) © 2001-2006 Red Hat, Inc.
[    0.343646] msgmni has been set to 967
[    0.344409] io scheduler noop registered
[    0.344422] io scheduler deadline registered
[    0.344462] io scheduler cfq registered (default)
[    0.356278] dma-pl330 f8003000.ps7-dma: Loaded driver for PL330 DMAC-2364208
[    0.356298] dma-pl330 f8003000.ps7-dma: 	DBUFF-128x8bytes Num_Chans-8 Num_Peri-4 Num_Events-16
[    0.481033] e0001000.serial: ttyPS0 at MMIO 0xe0001000 (irq = 82, base_baud = 3124999) is a xuartps
[    1.048280] console [ttyPS0] enabled
[    1.052537] xdevcfg f8007000.ps7-dev-cfg: ioremap 0xf8007000 to df866000
[    1.060187] [drm] Initialized drm 1.1.0 20060810
[    1.077199] brd: module loaded
[    1.086573] loop: module loaded
[    1.095996] e1000e: Intel(R) PRO/1000 Network Driver - 2.3.2-k
[    1.101973] e1000e: Copyright(c) 1999 - 2013 Intel Corporation.
[    1.109848] libphy: XEMACPS mii bus: probed
[    1.114215] ------------- phy_id = 0x3625e62
[    1.119160] xemacps e000b000.ps7-ethernet: pdev->id -1, baseaddr 0xe000b000, irq 54
[    1.127806] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[    1.134430] ehci-pci: EHCI PCI platform driver
[    1.141665] zynq-dr e0002000.ps7-usb: Unable to init USB phy, missing?
[    1.148487] usbcore: registered new interface driver usb-storage
[    1.155314] mousedev: PS/2 mouse device common for all mice
[    1.161432] i2c /dev entries driver
[    1.168351] zynq-edac f8006000.ps7-ddrc: ecc not enabled
[    1.173830] cpufreq_cpu0: failed to get cpu0 regulator: -19
[    1.179757] Xilinx Zynq CpuIdle Driver started
[    1.184595] sdhci: Secure Digital Host Controller Interface driver
[    1.190721] sdhci: Copyright(c) Pierre Ossman
[    1.195033] sdhci-pltfm: SDHCI platform and OF driver helper
[    1.201919] mmc0: no vqmmc regulator found
[    1.205930] mmc0: no vmmc regulator found
[    1.247125] mmc0: SDHCI controller on e0100000.ps7-sdio [e0100000.ps7-sdio] using ADMA
[    1.255800] usbcore: registered new interface driver usbhid
[    1.261320] usbhid: USB HID core driver
[    1.266007] nand: device found, Manufacturer ID: 0x2c, Chip ID: 0xda
[    1.272302] nand: Micron MT29F2G08ABAEAWP
[    1.276273] nand: 256MiB, SLC, page size: 2048, OOB size: 64
[    1.282226] Bad block table found at page 131008, version 0x01
[    1.288466] Bad block table found at page 130944, version 0x01
[    1.294514] 3 ofpart partitions found on MTD device pl353-nand
[    1.300287] Creating 3 MTD partitions on "pl353-nand":
[    1.305394] 0x000000000000-0x000002000000 : "BOOT.bin-env-dts-kernel"
[    1.313466] 0x000002000000-0x00000b000000 : "angstram-rootfs"
[    1.320788] 0x00000b000000-0x000010000000 : "upgrade-rootfs"
[    1.331539] TCP: cubic registered
[    1.334776] NET: Registered protocol family 17
[    1.339488] Registering SWP/SWPB emulation handler
[    1.345356] regulator-dummy: disabling
[    1.349680] UBI: attaching mtd1 to ubi0
[    1.870975] UBI: scanning is finished
[    1.882628] UBI: attached mtd1 (name "angstram-rootfs", size 144 MiB) to ubi0
[    1.889705] UBI: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
[    1.896449] UBI: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
[    1.903152] UBI: VID header offset: 2048 (aligned 2048), data offset: 4096
[    1.910010] UBI: good PEBs: 1152, bad PEBs: 0, corrupted PEBs: 0
[    1.915978] UBI: user volume: 1, internal volumes: 1, max. volumes count: 128
[    1.923110] UBI: max/mean erase counter: 19/9, WL threshold: 4096, image sequence number: 990710654
[    1.932141] UBI: available PEBs: 0, total reserved PEBs: 1152, PEBs reserved for bad PEB handling: 40
[    1.941356] UBI: background thread "ubi_bgt0d" started, PID 1084
[    1.941362] drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
[    1.945321] ALSA device list:
[    1.945325]   No soundcards found.
[    1.961689] UBIFS: background thread "ubifs_bgt0_0" started, PID 1086
[    1.990551] UBIFS: recovery needed
[    2.074124] UBIFS: recovery completed
[    2.077813] UBIFS: mounted UBI device 0, volume 0, name "rootfs"
[    2.083741] UBIFS: LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
[    2.092880] UBIFS: FS size: 128626688 bytes (122 MiB, 1013 LEBs), journal size 9023488 bytes (8 MiB, 72 LEBs)
[    2.102760] UBIFS: reserved for root: 0 bytes (0 KiB)
[    2.107800] UBIFS: media format: w4/r0 (latest is w4/r0), UUID D1A277C9-C3A8-4BCB-B6A3-DCFCD33ECA2A, small LPT model
[    2.119079] VFS: Mounted root (ubifs filesystem) on device 0:11.
[    2.126244] devtmpfs: mounted
[    2.129370] Freeing unused kernel memory: 204K (c06db000 - c070e000)
[    2.965345] random: dd urandom read with 1 bits of entropy available
[    3.347146] 
[    3.347146] bcm54xx_config_init
[    4.417149] 
[    4.417149] bcm54xx_config_init
[    8.417985] xemacps e000b000.ps7-ethernet: Set clk to 24999999 Hz
[    8.424079] xemacps e000b000.ps7-ethernet: link up (100/FULL)
[   23.885760] In axi fpga driver!
[   23.888852] request_mem_region OK!
[   23.892216] AXI fpga dev virtual address is 0xdf9fe000
[   23.897346] *base_vir_addr = 0xc51e
[   23.911684] In fpga mem driver!
[   23.914999] request_mem_region OK!
[   23.918609] fpga mem virtual address is 0xe2000000
[   24.696492] 
[   24.696492] bcm54xx_config_init
[   25.806373] 
[   25.806373] bcm54xx_config_init
[   29.806789] xemacps e000b000.ps7-ethernet: Set clk to 24999999 Hz
[   29.812809] xemacps e000b000.ps7-ethernet: link up (100/FULL)
log_level = 4
This is XILINX board. Totalram:       507486208
Detect 512MB control board of XILINX
mmap axi_fpga_addr = 0xb6fc8000
axi_fpga_addr data = 0xc51e
mmap fpga_mem_addr = 0xb5dc1000
forceFreq=-1 forceFlag=0
min work minertest[0]:912


DETECT HW version=0000c51e
miner ID : 807c9c007850481c
Miner Type = S9
AsicType = 1387
real AsicNum = 63
use critical mode to search freq...
get PLUG ON=0x000000e0
Find hashboard on Chain[5]
Find hashboard on Chain[6]
Find hashboard on Chain[7]
Check chain[5] PIC fw version=0x03
Check chain[6] PIC fw version=0x03
Check chain[7] PIC fw version=0x03
read pic freq and badcore num...
chain[5]: [63:255] [63:255] [63:255] [63:255] [63:255] [63:255] [63:255] [63:255]
has freq in PIC, will disable freq setting.
chain[5] has freq in PIC and will jump over...
Chain[5] has core num in PIC
Chain[5] ASIC[26] has core num=1
Chain[5] ASIC[33] has core num=1
Chain[5] ASIC[43] has core num=1
Chain[5] ASIC[52] has core num=1
Check chain[5] PIC fw version=0x03
read pic freq and badcore num...
chain[6]: [63:255] [63:255] [63:255] [63:255] [63:255] [63:255] [63:255] [63:255]
has freq in PIC, will disable freq setting.
chain[6] has freq in PIC and will jump over...
Chain[6] has core num in PIC
Chain[6] ASIC[12] has core num=1
Chain[6] ASIC[15] has core num=1
Chain[6] ASIC[16] has core num=1
Chain[6] ASIC[24] has core num=1
Chain[6] ASIC[29] has core num=1
Chain[6] ASIC[35] has core num=1
Chain[6] ASIC[41] has core num=1
Chain[6] ASIC[50] has core num=1
Chain[6] ASIC[54] has core num=1
Chain[6] ASIC[58] has core num=1
Check chain[6] PIC fw version=0x03
read pic freq and badcore num...
chain[7]: [63:255] [63:255] [63:255] [63:255] [63:255] [63:255] [63:255] [63:255]
has freq in PIC, will disable freq setting.
chain[7] has freq in PIC and will jump over...
Chain[7] has core num in PIC
Chain[7] ASIC[4] has core num=2
Chain[7] ASIC[8] has core num=1
Chain[7] ASIC[13] has core num=3
Chain[7] ASIC[15] has core num=5
Chain[7] ASIC[16] has core num=2
Chain[7] ASIC[17] has core num=3
Chain[7] ASIC[19] has core num=1
Chain[7] ASIC[20] has core num=1
Chain[7] ASIC[21] has core num=1
Chain[7] ASIC[22] has core num=9
Chain[7] ASIC[23] has core num=6
Chain[7] ASIC[25] has core num=2
Chain[7] ASIC[26] has core num=3
Chain[7] ASIC[29] has core num=4
Chain[7] ASIC[31] has core num=1
Chain[7] ASIC[32] has core num=1
Chain[7] ASIC[36] has core num=1
Chain[7] ASIC[38] has core num=1
Chain[7] ASIC[40] has core num=8
Chain[7] ASIC[41] has core num=1
Chain[7] ASIC[42] has core num=1
Chain[7] ASIC[43] has core num=2
Chain[7] ASIC[44] has core num=1
Chain[7] ASIC[47] has core num=2
Chain[7] ASIC[50] has core num=3
Chain[7] ASIC[52] has core num=4
Chain[7] ASIC[53] has core num=6
Chain[7] ASIC[55] has core num=1
Chain[7] ASIC[56] has core num=1
Chain[7] ASIC[57] has core num=1
Chain[7] ASIC[58] has core num=1
Check chain[7] PIC fw version=0x03
get PIC voltage=91 on chain[5], value=890
get PIC voltage=91 on chain[6], value=890
get PIC voltage=91 on chain[7], value=890
chain[5] temp offset record: 62,0,0,0,0,0,35,28
chain[5] temp chip I2C addr=0x98
chain[5] has no middle temp, use special fix mode.
chain[6] temp offset record: 62,0,0,0,0,0,35,28
chain[6] temp chip I2C addr=0x98
chain[6] has no middle temp, use special fix mode.
chain[7] temp offset record: 62,0,0,0,0,0,35,28
chain[7] temp chip I2C addr=0x98
chain[7] has no middle temp, use special fix mode.
total_exist_chain_num = 3
single_board_frq_tuning enter
min_rate, des_rate, fix_volt:13800, 14000, 880
force_freq not set, don't need tuning
restart Miner chance num=2
waiting for receive_func to exit!
waiting for pic heart to exit!
bmminer not found= 1826 root       0:00 grep bmminer

bmminer not found, restart bmminer ...
This is user mode for mining
Detect 512MB control board of XILINX
Miner Type = S9
Miner compile time: Fri May 31 11:01:56 CST 2019 type: Antminer S9i
miner ID : 807c9c007850481c
Checking fans...
get fan[4] speed=6120
get fan[5] speed=6000
get fan[4] speed=6120
get fan[5] speed=6000
get fan[4] speed=6120
get fan[5] speed=6000
chain[5]: [63:255] [63:255] [63:255] [63:255] [63:255] [63:255] [63:255] [63:255]
last_freq: 0x00 0x7d 0x00 0x4e 0x00 0x4e 0x04 0x4e 0x0e 0x4e 0x00 0x4e 0x03 0x4e 0x03 0x4e 0x03 0x4e 0x03 0x4e 0x03 0x4e 0x03 0x4e 0x01 0x4e 0x01 0x4e 0x0f 0x4e 0x0f 0x4e 0x0f 0x4e 0x0f 0x4e 0x05 0x4e 0x06 0x4e 0x23 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 
Detect: use voltage limit rules on single board!
Detect: S9_63 use voltage level=1 : 1
Chain[J6] has backup chain_voltage=860
No scan based on domain
Check chain[5] PIC fw version=0x03
chain[6]: [63:255] [63:255] [63:255] [63:255] [63:255] [63:255] [63:255] [63:255]
last_freq: 0x00 0x7d 0x00 0x4e 0x00 0x4e 0x04 0x4e 0x0e 0x4e 0x00 0x4e 0x03 0x4e 0x03 0x4e 0x03 0x4e 0x03 0x4e 0x03 0x4e 0x03 0x4e 0x01 0x4e 0x01 0x4e 0x0f 0x4e 0x0f 0x4e 0x0f 0x4e 0x0f 0x4e 0x05 0x4e 0x07 0x4e 0x23 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 
Detect: use voltage limit rules on single board!
Detect: S9_63 use voltage level=1 : 1
Chain[J7] has backup chain_voltage=870
No scan based on domain
Check chain[6] PIC fw version=0x03

[BitMaxz]

Reattach the power supply and cables and then run it for a while 15 min to 30 min to warm up the miner then check it again.
It sometimes needs to warm up first before the miner will work properly.

If it didn't work you can now copy the kernel logs and paste it here don't forget to use the code button you can find it while you are making a post here

Like this one

Code:

Kernel logs here

[tim-bc]

You should test the miner with a known good PSU if you haven't already.

[mikeywith]

I would try a different pool , if ( as you mentioned) that you tried a working psu, resetting and all the other normal procedures, then it's only one out of two possibilities, connection problem ( pool , router firewall not allowing the miner to connect to pool etc,) or simply the control board has gone bad.

[mortadeli]

I would try a different pool , if ( as you mentioned) that you tried a working psu, resetting and all the other normal procedures, then it's only one out of two possibilities, connection problem ( pool , router firewall not allowing the miner to connect to pool etc,) or simply the control board has gone bad.

I am currently using slushpool and the interesting thing is this is only happening to my S9 machines, and they stopped restarting however they have a very high stale rate, while at the same time my s11 machines have no problem

What is a good pool you suggest other than slushpool?

[BitMaxz]

What is a good pool you suggest other than slushpool?

Slushpool is fine there's nothing wrong with this pool.

Anyway, you can try ckpool you can find their official thread from here https://bitcointalk.org/index.php?topic=1876330.0

Or Kano pool official thread from here https://bitcointalk.org/index.php?topic=789369.0

They are both good.

If changing pool doesn't work can you try this below?

Changing fan speed to 90 to 100% then set the frequency to 550m then test the miner again.

To find the secret menu where you can customize the fan speed and frequency follow this step https://bitcointalk.org/index.php?topic=2690140.0

[mikeywith]

I have some of my gears on Slushpool havn't seen a problem in a long time, you could try the pools Bitmaxz suggested, currently I use Slushpool , Viabtc and Cksolo , non of them is having a bad time, the stale shares however can very well be a connection problem.

 i don't know about your networking background but you should monitor the packets going to and out of the miners , cables , latency and etc.. but all of this is not needed unless all the other pools mentioned here give you the same issue.

Also always use a pool server closest to your location, you can ping the server using CMD with ping -t and let it run for 15 mins see if you get any packed loss or not.

[mortadeli]

I switched to viabtc and no issues for now, its weird for some reason wasnt able to try antpool at all and slushpool kept giving issues

[mikeywith]

Don't mine on antpool , just a friendly advice.

anyhow, how long has your miner been running on viabtc without an issue ? I would like to assume that it has to do with your internet, you probably have a terrible connection and slushpool server's seems to be way too far and hard to reach , simply as good as dead.

what you could try is simply open cmd and type

Code:

ping slushpool.com -t

and you will get something like this >



if the average time is high , say above 200-300 then your connection is bad and you shouldn't mine on that pool, you want a pool that you can ping in <100 ms , indeed not antpool tho  

[BitMaxz]

No, you can't ping them just like that without port included because you are just pinging the whole website and you can't ping them with a port in windows.

What he needs to do is to choose another pool in slush pool you should choose the correct one so if you are living in Singapore you should use this pool

Code:

stratum+tcp://sg.stratum.slushpool.com:3333

to get a lower ping or if you are living in Japan you should use the Japan pool

Code:

stratum+tcp://jp.stratum.slushpool.com:3333

so that you can get a stable mining.

To get the list of other slushpool servers you can find it from here https://slushpool.com/help/bitcoin-setup/

If nothing works then I think staying on viabtc is fine they are also a good pool.

[mortadeli]

I have S11s running on slushpool on the same internet connection, how can it work fine for S11 and not for S9?!

[Raymond_B]

I have S11s running on slushpool on the same internet connection, how can it work fine for S11 and not for S9?!

I don't use Slush and this might already have been fixed, but could you be running in to something like this? What firmware are you running? Maybe you need to change to one that does not have issues?

https://www.ccn.com/slush-pool-dont-upgrade-your-bitcoin-miners-to-bitmains-asicboost-patch/

[mikeywith]

No, you can't ping them just like that without port included because you are just pinging the whole website...

This is wrong , very wrong actually .

first of all, you can't ping a port , it's not windows that doesn't allow this, it's the IP protocol that doesn't let you do so, you can only telnet a port to see if it's listening/open or not, this is way off topic , but felt the need to correct you.

back on topic now, the ping command does not work how you imagine it, when you ping a domain name, you don't simply ping the whole website, there is no whole website, it does not work that way, many pools give you a universal link and then the DNS will handle it, you usually access the nearest server the pool has to your location , just like when you access www.google.com or youtube.com  , it's not a single server that everybody has to access , you don't see JP.youtube or EU.youtube , that's exactly what happens with pools like Slushpool.

This is so much details, but look at the image below and you will get it.



above is pining slushpool.com  from different location , you can see that it pings a different IP address ( a different server ) .

to sum up , whatever you get on your CMD ping command is whatever your miner will have , so if the ping is fine your miner will do just fine and the opposite  is correct.

[Raymond_B]

You've got some networking things mixed up here, but to keep this post on subject slushpool.com is a group of load balanced web servers and NOT the pool servers (which are load balanced themselves). Below are Slush's pool servers from their website.



And using the PsPing command voila we see a pool server (Thanks Kano for this info on *your* pool page https://kano.is/index.php)

[mortadeli]

Ive been testing Kano and viabtc lately and so far none of the issues related to slushpool is happening

[mikeywith]

Non of what you mentioned is wrong, but i was mainly talking about the general pool address, try pinging it from a different location and you will see that you are getting a reply from a different IP address, assuming you have the same speed from the different locations you ping from, the result will be very close.

It is however advisable to use the one closest to your location, but overall, if you do ping the pool and get terrible results it means you should find another pool.

OP can try the urls you provided and use the one nearest to him, chances are he will still face the same problem.