Bitcoin Forum>Bitcoin>Mining>Mining support
Author

Topic: ANTMINER S9 reporting extremely low hashrate (Read 231 times)

barszczewski
newbie
Activity: 4
Merit: 0
ANTMINER S9 reporting extremely low hashrate
December 20, 2020, 11:26:08 AM
#13
Quote from: BitMaxz on December 18, 2020, 07:20:35 PM
[...]

Switched to slushpool - problem is persisting.

Quote from: mikeywith on December 19, 2020, 06:07:53 PM
So this is unlikely to be caused by the pool/firmware/network or anything that hasn't changed, I am still leaning towards physical problems with the miner, I am almost sure that if he leaves chain chain 7 alone, the pool will report 1/3 of the total hashrate and it would be consistent.

I will look into hardware issues today. Thanks again gais.
mikeywith
legendary
Activity: 2394
Merit: 6581
be constructive or S.T.F.U
Re: ANTMINER S9 reporting extremely low hashrate
December 19, 2020, 06:07:53 PM
#12
Quote from: BitMaxz on December 18, 2020, 07:20:35 PM
What pool exactly telling that it's rebooting every 5min?

I think he means the hashrate reported on the pool appears like the miner reboots every 5 mins, not like he is getting an email from the pool which states so.

Quote from: BitMaxz on December 18, 2020, 07:20:35 PM
Try to mine to another pool like ViaBTC or try the ASICboost pool on Nicehash it looks like this.

I think at least 90% of btc mining pool are Asicboost compatible, Poolin is indeed (based on personal experince) Asicboost "friendly".

Quote from: BitMaxz on December 18, 2020, 07:20:35 PM
stratum+tcp://sha256asicboost.eu.nicehash.com:3368

This will only fix the connectivty issue where pool shows dead, which doesn't seem to be the case here, also nothing has changed on poolin and nicehash so whichever issue is related to the miner itself because OP mentioned.

So this is unlikely to be caused by the pool/firmware/network or anything that hasn't changed, I am still leaning towards physical problems with the miner, I am almost sure that if he leaves chain chain 7 alone, the pool will report 1/3 of the total hashrate and it would be consistent.
BitMaxz
legendary
Activity: 3374
Merit: 3095
Playbet.io - Crypto Casino and Sportsbook
Re: ANTMINER S9 reporting extremely low hashrate
December 18, 2020, 07:20:35 PM
#11
Quote from: barszczewski on December 18, 2020, 09:24:03 AM
Ah, well you see - There's no sign of rebooting where I'm sitting. That is to say the miner sounds normal and the logs read fine, aside from the occasional DHCP check.

However, my pools are telling me that it's rebooting every 5 minutes or so. Also in the middle of the night it might go through a cycle or two where it reboots 2-3 times in 5 min.

What pool exactly telling that it's rebooting every 5min?
Are you still mining on Nicehash?

Try to mine to another pool like ViaBTC or try the ASICboost pool on Nicehash it looks like this.

Code:
stratum+tcp://sha256asicboost.eu.nicehash.com:3368

You can replace EU to USA.

Or try other pool that support ASICboost.

I remember someone having the same issue before that every 5 minutes the miner stop mining and solve his issue after switching to ASICboost pools or any pool that support ASICboost.
mikeywith
legendary
Activity: 2394
Merit: 6581
be constructive or S.T.F.U
Re: ANTMINER S9 reporting extremely low hashrate
December 18, 2020, 03:29:02 PM
#10
Could you unplug chain 5 as I don't seem to like this part in the kernel log, only chip [29] and [57] are reporting hashrate, which isn't how it should be.

Quote from: barszczewski on December 18, 2020, 09:24:03 AM
get RT hashrate from Chain[5]: (asic index start from 1-63)
Asic[01]=0.00000 Asic[02]=0.00000 Asic[03]=0.00000 Asic[04]=0.00000 Asic[05]=0.00000 Asic[06]=0.00000 Asic[07]=0.00000 Asic[08]=0.00000
Asic[09]=0.00000 Asic[10]=0.00000 Asic[11]=0.00000 Asic[12]=0.00000 Asic[13]=0.00000 Asic[14]=0.00000 Asic[15]=0.00000 Asic[16]=0.00000
Asic[17]=0.00000 Asic[18]=0.00000 Asic[19]=0.00000 Asic[20]=0.00000 Asic[21]=0.00000 Asic[22]=0.00000 Asic[23]=0.00000 Asic[24]=0.00000
Asic[25]=0.00000 Asic[26]=0.00000 Asic[27]=0.00000 Asic[28]=0.00000 Asic[29]=131.030 Asic[30]=0.00000 Asic[31]=0.00000 Asic[32]=0.00000
Asic[33]=0.00000 Asic[34]=0.00000 Asic[35]=0.00000 Asic[36]=0.00000 Asic[37]=0.00000 Asic[38]=0.00000 Asic[39]=0.00000 Asic[40]=0.00000
Asic[41]=0.00000 Asic[42]=0.00000 Asic[43]=0.00000 Asic[44]=0.00000 Asic[45]=0.00000 Asic[46]=0.00000 Asic[47]=0.00000 Asic[48]=0.00000
Asic[49]=0.00000 Asic[50]=0.00000 Asic[51]=0.00000 Asic[52]=0.00000 Asic[53]=0.00000 Asic[54]=0.00000 Asic[55]=0.00000 Asic[56]=0.00000
Asic[57]=123.966 Asic[58]=0.00000 Asic[59]=0.00000 Asic[60]=0.00000 Asic[61]=0.00000 Asic[62]=0.00000 Asic[63]=0.00000

Chain 6 doesn't look that healthy either, but chain 7 looks perfect, so I would start by removing chain 5, run the miner for 10 hours, see how it goes, if all good, then chain 5 is bad, if not - remove chain 6 as well and re-test.

I would also set a static ip address just to make sure, and reboot the router/switch.
barszczewski
newbie
Activity: 4
Merit: 0
Re: ANTMINER S9 reporting extremely low hashrate
December 18, 2020, 09:24:03 AM
#9
Ah, well you see - There's no sign of rebooting where I'm sitting. That is to say the miner sounds normal and the logs read fine, aside from the occasional DHCP check.

However, my pools are telling me that it's rebooting every 5 minutes or so. Also in the middle of the night it might go through a cycle or two where it reboots 2-3 times in 5 min.
mikeywith
legendary
Activity: 2394
Merit: 6581
be constructive or S.T.F.U
Re: ANTMINER S9 reporting extremely low hashrate
December 17, 2020, 12:08:54 PM
#8
Quote from: barszczewski on December 16, 2020, 10:23:50 PM
Code:
read_temp_func Done!
CRC error counter=0

Everything looks ok in the kernel, all three hash boards show 63 Asics (which is how it has to be), although chain 5 might be the cause, but too early to judge.

Quote
Sadly I just came back from weekend trip and I'm still having hashrate issues after leaving it on the entire time.

You forget to mention a very important thing. When you came back from your trip, was the miner run time equal to the time it was left to mine? in other words, did it reboot?
barszczewski
newbie
Activity: 4
Merit: 0
Re: ANTMINER S9 reporting extremely low hashrate
December 16, 2020, 10:23:50 PM
#7
I like MikeyWith's theory so far. One fan broke in transit very recently so I had to swap out with an old one so I'll give the hardware a good once-over and update this thread once I replace fans or something.
Sadly I just came back from weekend trip and I'm still having hashrate issues after leaving it on the entire time.

@ thread, I already tried to reboot. The status page just happens to be after a fresh boot (my bad)

Here's the log

Thanks for looking into this m8s

Code:
[    0.000000] Booting Linux on physical CPU 0x0
[    0.000000] Machine model: Xilinx Zynq
[    0.000000] Linux version 3.14.0-xilinx-ga36f3af-dirty (lzq@ubuntu) (gcc version 4.8.3 20140320 (prerelease) (Sourcery CodeBench Lite 2014.05-23) ) #90 SMP PREEMPT Thu Jun 20 15:01:47 CST 2019
[    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] cma: CMA: reserved 128 MiB at 17000000
[    0.000000] Memory policy: Data cache writealloc
[    0.000000] On node 0 totalpages: 126976
[    0.000000] free_area_init_node: node 0, pgdat c0629a40, node_mem_map d6bd9000
[    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 @d6bc2000 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: 365496K/507904K available (4238K kernel code, 1142K rwdata, 732K rodata, 200K init, 246K bss, 142408K 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 - 0xc04e2d8c   (4972 kB)
[    0.000000]       .init : 0xc04e3000 - 0xc0515380   ( 201 kB)
[    0.000000]       .data : 0xc0516000 - 0xc0633928   (1143 kB)
[    0.000000]        .bss : 0xc0633934 - 0xc06711e4   ( 247 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.000278] ps7-ttc #0 at df804000, irq=43
[    0.000563] Console: colour dummy device 80x30
[    0.000592] Calibrating delay loop... 1332.01 BogoMIPS (lpj=6660096)
[    0.090235] pid_max: default: 32768 minimum: 301
[    0.090436] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
[    0.090454] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
[    0.092479] CPU: Testing write buffer coherency: ok
[    0.092795] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
[    0.092887] Setting up static identity map for 0x40a3a8 - 0x40a400
[    0.093099] L310 cache controller enabled
[    0.093117] l2x0: 8 ways, CACHE_ID 0x410000c8, AUX_CTRL 0x72460000, Cache size: 512 kB
[    0.170938] CPU1: Booted secondary processor
[    0.260213] CPU1: thread -1, cpu 1, socket 0, mpidr 80000001
[    0.260339] Brought up 2 CPUs
[    0.260357] SMP: Total of 2 processors activated.
[    0.260366] CPU: All CPU(s) started in SVC mode.
[    0.261011] devtmpfs: initialized
[    0.263237] VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4
[    0.264569] regulator-dummy: no parameters
[    0.271318] NET: Registered protocol family 16
[    0.273522] DMA: preallocated 256 KiB pool for atomic coherent allocations
[    0.275771] cpuidle: using governor ladder
[    0.275785] cpuidle: using governor menu
[    0.282646] syscon f8000000.ps7-slcr: regmap [mem 0xf8000000-0xf8000fff] registered
[    0.284118] hw-breakpoint: found 5 (+1 reserved) breakpoint and 1 watchpoint registers.
[    0.284131] hw-breakpoint: maximum watchpoint size is 4 bytes.
[    0.284236] zynq-ocm f800c000.ps7-ocmc: ZYNQ OCM pool: 256 KiB @ 0xdf880000
[    0.298138] bio: create slab  at 0
[    0.299762] SCSI subsystem initialized
[    0.300858] pps_core: LinuxPPS API ver. 1 registered
[    0.300871] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti 
[    0.301018] PTP clock support registered
[    0.304422] DMA-API: preallocated 4096 debug entries
[    0.304436] DMA-API: debugging enabled by kernel config
[    0.304511] Switched to clocksource arm_global_timer
[    0.324562] NET: Registered protocol family 2
[    0.325192] TCP established hash table entries: 4096 (order: 2, 16384 bytes)
[    0.325249] TCP bind hash table entries: 4096 (order: 3, 32768 bytes)
[    0.325334] TCP: Hash tables configured (established 4096 bind 4096)
[    0.325378] TCP: reno registered
[    0.325396] UDP hash table entries: 256 (order: 1, 8192 bytes)
[    0.325426] UDP-Lite hash table entries: 256 (order: 1, 8192 bytes)
[    0.325642] NET: Registered protocol family 1
[    0.325678] PCI: CLS 0 bytes, default 64
[    0.326078] hw perfevents: enabled with ARMv7 Cortex-A9 PMU driver, 7 counters available
[    0.328168] futex hash table entries: 512 (order: 3, 32768 bytes)
[    0.328237] audit: initializing netlink subsys (disabled)
[    0.328290] audit: type=2000 audit(0.319:1): initialized
[    0.330059] jffs2: version 2.2. (NAND) © 2001-2006 Red Hat, Inc.
[    0.330237] msgmni has been set to 969
[    0.331306] io scheduler noop registered
[    0.331319] io scheduler deadline registered
[    0.331357] io scheduler cfq registered (default)
[    0.335700] dma-pl330 f8003000.ps7-dma: Loaded driver for PL330 DMAC-2364208
[    0.335720] dma-pl330 f8003000.ps7-dma: 	DBUFF-128x8bytes Num_Chans-8 Num_Peri-4 Num_Events-16
[    0.456507] e0001000.serial: ttyPS0 at MMIO 0xe0001000 (irq = 82, base_baud = 3124999) is a xuartps
[    0.976144] console [ttyPS0] enabled
[    0.980369] xdevcfg f8007000.ps7-dev-cfg: ioremap 0xf8007000 to df868000
[    0.999025] brd: module loaded
[    1.008100] loop: module loaded
[    1.017284] e1000e: Intel(R) PRO/1000 Network Driver - 2.3.2-k
[    1.023034] e1000e: Copyright(c) 1999 - 2013 Intel Corporation.
[    1.030855] libphy: XEMACPS mii bus: probed
[    1.035254] ------------- phy_id = 0x3625e62
[    1.039866] xemacps e000b000.ps7-ethernet: invalid address, use assigned
[    1.046596] xemacps e000b000.ps7-ethernet: MAC updated 16:33:e1:99:29:e3
[    1.053316] xemacps e000b000.ps7-ethernet: pdev->id -1, baseaddr 0xe000b000, irq 54
[    1.062503] mousedev: PS/2 mouse device common for all mice
[    1.068720] i2c /dev entries driver
[    1.073691] cpufreq_cpu0: failed to get cpu0 regulator: -19
[    1.079585] Xilinx Zynq CpuIdle Driver started
[    1.086048] nand: device found, Manufacturer ID: 0x2c, Chip ID: 0xda
[    1.092318] nand: Micron MT29F2G08ABAEAWP
[    1.096403] nand: 256MiB, SLC, page size: 2048, OOB size: 64
[    1.102261] Bad block table found at page 131008, version 0x01
[    1.108482] Bad block table found at page 130944, version 0x01
[    1.114558] 3 ofpart partitions found on MTD device pl353-nand
[    1.120303] Creating 3 MTD partitions on "pl353-nand":
[    1.125449] 0x000000000000-0x000002000000 : "BOOT.bin-env-dts-kernel"
[    1.133367] 0x000002000000-0x00000b000000 : "angstram-rootfs"
[    1.140595] 0x00000b000000-0x000010000000 : "upgrade-rootfs"
[    1.149695] In fpga mem driver!
[    1.152763] request_mem_region OK!
[    1.156316] fpga mem virtual address is 0xe2000000
[    1.161426] In axi fpga driver!
[    1.164489] request_mem_region OK!
[    1.167908] AXI fpga dev virtual address is 0xdf870000
[    1.172990] *g_base_vir_addr = 0xc51e
[    1.177477] ipip: IPv4 over IPv4 tunneling driver
[    1.183034] TCP: cubic registered
[    1.186396] NET: Registered protocol family 10
[    1.191766] sit: IPv6 over IPv4 tunneling driver
[    1.197355] NET: Registered protocol family 17
[    1.201728] 8021q: 802.1Q VLAN Support v1.8
[    1.205943] NET: Registered protocol family 41
[    1.210660] Registering SWP/SWPB emulation handler
[    1.216551] regulator-dummy: disabling
[    1.220823] UBI: attaching mtd1 to ubi0
[    1.750413] UBI: scanning is finished
[    1.762218] UBI: attached mtd1 (name "angstram-rootfs", size 144 MiB) to ubi0
[    1.769293] UBI: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
[    1.776062] UBI: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
[    1.782726] UBI: VID header offset: 2048 (aligned 2048), data offset: 4096
[    1.789603] UBI: good PEBs: 1152, bad PEBs: 0, corrupted PEBs: 0
[    1.795584] UBI: user volume: 1, internal volumes: 1, max. volumes count: 128
[    1.802692] UBI: max/mean erase counter: 33/15, WL threshold: 4096, image sequence number: 1113221046
[    1.811907] UBI: available PEBs: 0, total reserved PEBs: 1152, PEBs reserved for bad PEB handling: 40
[    1.821124] UBI: background thread "ubi_bgt0d" started, PID 1004
[    1.821129] drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
[    1.835111] UBIFS: background thread "ubifs_bgt0_0" started, PID 1006
[    1.864329] UBIFS: recovery needed
[    1.930762] UBIFS: recovery completed
[    1.934420] UBIFS: mounted UBI device 0, volume 0, name "rootfs"
[    1.940361] UBIFS: LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
[    1.949499] UBIFS: FS size: 128626688 bytes (122 MiB, 1013 LEBs), journal size 9023488 bytes (8 MiB, 72 LEBs)
[    1.959360] UBIFS: reserved for root: 0 bytes (0 KiB)
[    1.964386] UBIFS: media format: w4/r0 (latest is w4/r0), UUID E8A4479F-B15D-4C7A-964D-0F246E2BB6ED, small LPT model
[    1.976152] VFS: Mounted root (ubifs filesystem) on device 0:11.
[    1.983328] devtmpfs: mounted
[    2.094793] Freeing unused kernel memory: 200K (c04e3000 - c0515000)
[    3.325235] random: dd urandom read with 1 bits of entropy available
[    4.254538] 
[    4.254538] bcm54xx_config_init
[    6.074529] 
[    6.074529] bcm54xx_config_init
[   10.075537] xemacps e000b000.ps7-ethernet: Set clk to 124999998 Hz
[   10.081644] xemacps e000b000.ps7-ethernet: link up (1000/FULL)
[   29.013938] 
[   29.013938] bcm54xx_config_init
[   30.863786] 
[   30.863786] bcm54xx_config_init
[   35.864032] xemacps e000b000.ps7-ethernet: Set clk to 124999998 Hz
[   35.870136] xemacps e000b000.ps7-ethernet: link up (1000/FULL)
main.c:13992: log_level = 4
main.c:14019: This is XILINX board. Totalram:       508690432
main.c:14031: Detect 512MB control board of XILINX
driver-bitmain.c:1776: mmap axi_fpga_addr = 0xb6f66000
driver-bitmain.c:1781: axi_fpga_addr data = 0xc51e
driver-bitmain.c:1797: mmap fpga_mem_addr = 0xb5d0f000
driver-bitmain.c:994: forceFreq=-1 forceFlag=0
driver-bitmain.c:1696: min work minertest[0]:912


main.c:8570: DETECT HW version=0000c51e
main.c:14064: miner ID : 815cedce2c00881c
main.c:14089: Miner Type = S9
main.c:14101: AsicType = 1387
main.c:14104: real AsicNum = 63
main.c:14197: use critical mode to search freq...
driver-bitmain.c:1876: get PLUG ON=0x000000e0
driver-bitmain.c:1946: Find hashboard on Chain[5]
driver-bitmain.c:1946: Find hashboard on Chain[6]
driver-bitmain.c:1946: Find hashboard on Chain[7]
main.c:2282: Check chain[5] PIC fw version=0x03
main.c:2282: Check chain[6] PIC fw version=0x03
main.c:2282: Check chain[7] PIC fw version=0x03
main.c:8940: read pic freq and badcore num...
main.c:8961: chain[5]: [63:255] [63:255] [63:255] [63:255] [63:255] [63:255] [63:255] [63:255]
main.c:9003: has freq in PIC, will disable freq setting.
main.c:9099: chain[5] has freq in PIC and will jump over...
main.c:9103: Chain[5] has core num in PIC
main.c:9113: Chain[5] ASIC[14] has core num=1
main.c:2282: Check chain[5] PIC fw version=0x03
main.c:8940: read pic freq and badcore num...
main.c:8961: chain[6]: [63:255] [63:255] [63:255] [63:255] [63:255] [63:255] [63:255] [63:255]
main.c:9003: has freq in PIC, will disable freq setting.
main.c:9099: chain[6] has freq in PIC and will jump over...
main.c:9103: Chain[6] has core num in PIC
main.c:2282: Check chain[6] PIC fw version=0x03
main.c:8940: read pic freq and badcore num...
main.c:8961: chain[7]: [63:255] [63:255] [63:255] [63:255] [63:255] [63:255] [63:255] [63:255]
main.c:9003: has freq in PIC, will disable freq setting.
main.c:9099: chain[7] has freq in PIC and will jump over...
main.c:9103: Chain[7] has core num in PIC
main.c:9113: Chain[7] ASIC[15] has core num=15
main.c:2282: Check chain[7] PIC fw version=0x03
main.c:9183: get PIC voltage=91 on chain[5], value=890
main.c:9183: get PIC voltage=91 on chain[6], value=890
main.c:9183: get PIC voltage=91 on chain[7], value=890
main.c:9349: chain[5] temp offset record: 62,0,0,0,0,0,39,28
main.c:9366: chain[5] temp chip I2C addr=0x9c
main.c:9372: chain[5] has no middle temp, use special fix mode.
main.c:9349: chain[6] temp offset record: 62,0,0,0,0,0,39,28
main.c:9366: chain[6] temp chip I2C addr=0x9c
main.c:9372: chain[6] has no middle temp, use special fix mode.
main.c:9349: chain[7] temp offset record: 62,0,0,0,0,0,39,28
main.c:9366: chain[7] temp chip I2C addr=0x9c
main.c:9372: chain[7] has no middle temp, use special fix mode.
main.c:13956: total_exist_chain_num = 3
main.c:9562: CRC error counter=0
main.c:9577: set command mode to VIL
main.c:9649: 
--- check asic number
main.c:9745: After Get ASIC NUM CRC error counter=0
main.c:9768: set_baud=0
main.c:10693: The min freq=700
main.c:10695: set real timeout 52, need sleep=379392
main.c:12825: After TEST CRC error counter=0
main.c:14236: search freq for 1 times, completed chain = 3, total chain num = 3 
board_frq_tuning.c:628: single_board_frq_tuning enter
board_frq_tuning.c:629: min_rate, des_rate, fix_volt:13800, 14000, 880
board_frq_tuning.c:254: force_freq not set, don't need tuning
main.c:14645: restart Miner chance num=2
main.c:14685: waiting for receive_func to exit!
main.c:14699: waiting for pic heart to exit!
main.c:13927: bmminer not found= 1869 root       0:00 grep bmminer

main.c:14758: bmminer not found, restart bmminer ...
driver-btm-c5.c:12243:bitmain_c5_init: This is user mode for mining
driver-btm-c5.c:12292:bitmain_c5_init: Detect 512MB control board of XILINX
driver-btm-c5.c:12313:bitmain_c5_init: Miner Type = S9
driver-btm-c5.c:12324:bitmain_c5_init: Miner compile time: Wed Jul 31 16:18:27 CST 2019 type: Antminer S9
driver-btm-c5.c:12414:bitmain_c5_init: miner ID : 815cedce2c00881c
driver-btm-c5.c:12571:bitmain_c5_init: Checking fans...
driver-btm-c5.c:3006:check_fan_beforeInit: get fan[4] speed=30600
driver-btm-c5.c:3006:check_fan_beforeInit: get fan[5] speed=6120
driver-btm-c5.c:3006:check_fan_beforeInit: get fan[4] speed=30600
driver-btm-c5.c:3006:check_fan_beforeInit: get fan[5] speed=6120
driver-btm-c5.c:3006:check_fan_beforeInit: get fan[4] speed=30600
driver-btm-c5.c:3006:check_fan_beforeInit: get fan[5] speed=6120
driver-btm-c5.c:13108:bitmain_c5_init: chain[5]: [63:255] [63:255] [63:255] [63:255] [63:255] [63:255] [63:255] [63:255]
driver-btm-c5.c:13122:bitmain_c5_init: last_freq: 0x00 0x7d 0x00 0x48 0x00 0x48 0x04 0x48 0x08 0x48 0x00 0x48 0x03 0x48 0x03 0x48 0x03 0x48 0x03 0x48 0x01 0x48 0x01 0x48 0x01 0x48 0x01 0x48 0x0f 0x48 0x0f 0x48 0x0f 0x48 0x0f 0x48 0x05 0x48 0x09 0x48 0x23 0x48 0x00 0x48 0x00 0x48 0x00 0x48 0x00 0x48 0x00 0x48 0x00 0x48 0x00 0x48 0x00 0x48 0x00 0x48 0x00 0x48 0x00 0x48 0x00 0x48 0x00 0x48 0x00 0x48 0x00 0x48 0x00 0x48 0x00 0x48 0x00 0x48 0x00 0x48 0x00 0x48 0x00 0x48 0x00 0x48 0x00 0x48 0x00 0x48 0x00 0x48 0x00 0x48 0x00 0x48 0x00 0x48 0x00 0x48 0x00 0x48 0x00 0x48 0x00 0x48 0x00 0x48 0x00 0x48 0x00 0x48 0x00 0x48 0x00 0x48 0x00 0x48 0x00 0x48 0x00 0x48 0x00 0x48 0x00 0x48 0x00 0x48 
driver-btm-c5.c:13171:bitmain_c5_init: Chain[J6] has backup chain_voltage=890
driver-btm-c5.c:13188:bitmain_c5_init: No scan based on domain
driver-btm-c5.c:1899:jump_to_app_CheckAndRestorePIC: Check chain[5] PIC fw version=0x03
driver-btm-c5.c:13108:bitmain_c5_init: chain[6]: [63:255] [63:255] [63:255] [63:255] [63:255] [63:255] [63:255] [63:255]
driver-btm-c5.c:13122:bitmain_c5_init: last_freq: 0x00 0x7d 0x00 0x48 0x00 0x48 0x04 0x48 0x08 0x48 0x00 0x48 0x03 0x48 0x03 0x48 0x03 0x48 0x03 0x48 0x01 0x48 0x01 0x48 0x01 0x48 0x01 0x48 0x0f 0x48 0x0f 0x48 0x0f 0x48 0x0f 0x48 0x05 0x48 0x09 0x48 0x23 0x48 0x00 0x48 0x00 0x48 0x00 0x48 0x00 0x48 0x00 0x48 0x00 0x48 0x00 0x48 0x00 0x48 0x00 0x48 0x00 0x48 0x00 0x48 0x00 0x48 0x00 0x48 0x00 0x48 0x00 0x48 0x00 0x48 0x00 0x48 0x00 0x48 0x00 0x48 0x00 0x48 0x00 0x48 0x00 0x48 0x00 0x48 0x00 0x48 0x00 0x48 0x00 0x48 0x00 0x48 0x00 0x48 0x00 0x48 0x00 0x48 0x00 0x48 0x00 0x48 0x00 0x48 0x00 0x48 0x00 0x48 0x00 0x48 0x00 0x48 0x00 0x48 0x00 0x48 0x00 0x48 0x00 0x48 0x00 0x48 0x00 0x48 
driver-btm-c5.c:13171:bitmain_c5_init: Chain[J7] has backup chain_voltage=890
driver-btm-c5.c:13188:bitmain_c5_init: No scan based on domain
driver-btm-c5.c:1899:jump_to_app_CheckAndRestorePIC: Check chain[6] PIC fw version=0x03
driver-btm-c5.c:13108:bitmain_c5_init: chain[7]: [63:255] [63:255] [63:255] [63:255] [63:255] [63:255] [63:255] [63:255]
driver-btm-c5.c:13122:bitmain_c5_init: last_freq: 0x00 0x7d 0x00 0x48 0x00 0x48 0x04 0x48 0x08 0x48 0x00 0x48 0x03 0x48 0x03 0x48 0x03 0x48 0x03 0x48 0x01 0x48 0x01 0x48 0x01 0x48 0x01 0x48 0x0f 0x48 0x0f 0x48 0x0f 0x48 0x0f 0x48 0x05 0x48 0x09 0x48 0x23 0x48 0x00 0x48 0x00 0x48 0x00 0x48 0x00 0x48 0x00 0x48 0x00 0x48 0x00 0x48 0x00 0x48 0x00 0x48 0x00 0x48 0x00 0x48 0x00 0x48 0x00 0x48 0x00 0x48 0x00 0x48 0x00 0x48 0x00 0x48 0x00 0x48 0x00 0x48 0x00 0x48 0x00 0x48 0x00 0x48 0x00 0x48 0x00 0x48 0x00 0x48 0x00 0x48 0x00 0x48 0x00 0x48 0x00 0x48 0x00 0x48 0x00 0x48 0x00 0x48 0x00 0x48 0x00 0x48 0x00 0x48 0x00 0x48 0x00 0x48 0x00 0x48 0x00 0x48 0x00 0x48 0x00 0x48 0x00 0x48 0x00 0x48 
driver-btm-c5.c:13171:bitmain_c5_init: Chain[J8] has backup chain_voltage=890
driver-btm-c5.c:13188:bitmain_c5_init: No scan based on domain
driver-btm-c5.c:1899:jump_to_app_CheckAndRestorePIC: Check chain[7] PIC fw version=0x03
driver-btm-c5.c:12195:init_exist_chain_table: total_exist_chain_num = 3
driver-btm-c5.c:13303:bitmain_c5_init: Chain[J6] orignal chain_voltage_pic=91 value=890
driver-btm-c5.c:13303:bitmain_c5_init: Chain[J7] orignal chain_voltage_pic=91 value=890
driver-btm-c5.c:13303:bitmain_c5_init: Chain[J8] orignal chain_voltage_pic=91 value=890
driver-btm-c5.c:13421:bitmain_c5_init: Chain[J6] has 63 asic
driver-btm-c5.c:13421:bitmain_c5_init: Chain[J7] has 63 asic
driver-btm-c5.c:13421:bitmain_c5_init: Chain[J8] has 63 asic
driver-btm-c5.c:4531:set_frequency: Chain[J6] has core num in PIC
driver-btm-c5.c:4541:set_frequency: Chain[J6] ASIC[14] has core num=1
driver-btm-c5.c:4531:set_frequency: Chain[J7] has core num in PIC
driver-btm-c5.c:4531:set_frequency: Chain[J8] has core num in PIC
driver-btm-c5.c:4541:set_frequency: Chain[J8] ASIC[15] has core num=15
driver-btm-c5.c:4571:set_frequency: miner total rate=13651GH/s ideal_total_hash_rate = 13500GH/s
driver-btm-c5.c:4596:set_frequency: read PIC voltage=940 on chain[5]
driver-btm-c5.c:4598:set_frequency: Chain:5 chipnum=63
driver-btm-c5.c:4618:set_frequency: Chain[J6] voltage added=0.0V
driver-btm-c5.c:4768:set_frequency: Chain:5 temp offset=0
driver-btm-c5.c:4773:set_frequency: Chain:5 base freq=637
Asic[ 0]:637 Asic[ 1]:637 Asic[ 2]:637 Asic[ 3]:637 Asic[ 4]:637 Asic[ 5]:637 Asic[ 6]:637 Asic[ 7]:637 
Asic[ 8]:637 Asic[ 9]:637 Asic[10]:637 Asic[11]:637 Asic[12]:637 Asic[13]:637 Asic[14]:637 Asic[15]:637 
Asic[16]:637 Asic[17]:637 Asic[18]:637 Asic[19]:637 Asic[20]:637 Asic[21]:637 Asic[22]:637 Asic[23]:637 
Asic[24]:637 Asic[25]:637 Asic[26]:637 Asic[27]:637 Asic[28]:637 Asic[29]:637 Asic[30]:637 Asic[31]:637 
Asic[32]:637 Asic[33]:637 Asic[34]:637 Asic[35]:637 Asic[36]:637 Asic[37]:637 Asic[38]:637 Asic[39]:637 
Asic[40]:637 Asic[41]:637 Asic[42]:637 Asic[43]:637 Asic[44]:637 Asic[45]:637 Asic[46]:637 Asic[47]:637 
Asic[48]:637 Asic[49]:637 Asic[50]:637 Asic[51]:637 Asic[52]:637 Asic[53]:637 Asic[54]:637 Asic[55]:637 
Asic[56]:637 Asic[57]:637 Asic[58]:637 Asic[59]:637 Asic[60]:637 Asic[61]:637 Asic[62]:637 
driver-btm-c5.c:4809:set_frequency: Chain:5 max freq=637
driver-btm-c5.c:4810:set_frequency: Chain:5 min freq=637

driver-btm-c5.c:4596:set_frequency: read PIC voltage=940 on chain[6]
driver-btm-c5.c:4598:set_frequency: Chain:6 chipnum=63
driver-btm-c5.c:4618:set_frequency: Chain[J7] voltage added=0.0V
driver-btm-c5.c:4768:set_frequency: Chain:6 temp offset=0
driver-btm-c5.c:4773:set_frequency: Chain:6 base freq=637
Asic[ 0]:637 Asic[ 1]:637 Asic[ 2]:637 Asic[ 3]:637 Asic[ 4]:637 Asic[ 5]:637 Asic[ 6]:637 Asic[ 7]:637 
Asic[ 8]:637 Asic[ 9]:637 Asic[10]:637 Asic[11]:637 Asic[12]:637 Asic[13]:637 Asic[14]:637 Asic[15]:637 
Asic[16]:637 Asic[17]:637 Asic[18]:637 Asic[19]:637 Asic[20]:637 Asic[21]:637 Asic[22]:637 Asic[23]:637 
Asic[24]:637 Asic[25]:637 Asic[26]:637 Asic[27]:637 Asic[28]:637 Asic[29]:637 Asic[30]:637 Asic[31]:637 
Asic[32]:637 Asic[33]:637 Asic[34]:637 Asic[35]:637 Asic[36]:637 Asic[37]:637 Asic[38]:637 Asic[39]:637 
Asic[40]:637 Asic[41]:637 Asic[42]:637 Asic[43]:637 Asic[44]:637 Asic[45]:637 Asic[46]:637 Asic[47]:637 
Asic[48]:637 Asic[49]:637 Asic[50]:637 Asic[51]:637 Asic[52]:637 Asic[53]:637 Asic[54]:637 Asic[55]:637 
Asic[56]:637 Asic[57]:637 Asic[58]:637 Asic[59]:637 Asic[60]:637 Asic[61]:637 Asic[62]:637 
driver-btm-c5.c:4809:set_frequency: Chain:6 max freq=637
driver-btm-c5.c:4810:set_frequency: Chain:6 min freq=637

driver-btm-c5.c:4596:set_frequency: read PIC voltage=940 on chain[7]
driver-btm-c5.c:4598:set_frequency: Chain:7 chipnum=63
driver-btm-c5.c:4618:set_frequency: Chain[J8] voltage added=0.0V
driver-btm-c5.c:4768:set_frequency: Chain:7 temp offset=0
driver-btm-c5.c:4773:set_frequency: Chain:7 base freq=637
Asic[ 0]:637 Asic[ 1]:637 Asic[ 2]:637 Asic[ 3]:637 Asic[ 4]:637 Asic[ 5]:637 Asic[ 6]:637 Asic[ 7]:637 
Asic[ 8]:637 Asic[ 9]:637 Asic[10]:637 Asic[11]:637 Asic[12]:637 Asic[13]:637 Asic[14]:637 Asic[15]:637 
Asic[16]:637 Asic[17]:637 Asic[18]:637 Asic[19]:637 Asic[20]:637 Asic[21]:637 Asic[22]:637 Asic[23]:637 
Asic[24]:637 Asic[25]:637 Asic[26]:637 Asic[27]:637 Asic[28]:637 Asic[29]:637 Asic[30]:637 Asic[31]:637 
Asic[32]:637 Asic[33]:637 Asic[34]:637 Asic[35]:637 Asic[36]:637 Asic[37]:637 Asic[38]:637 Asic[39]:637 
Asic[40]:637 Asic[41]:637 Asic[42]:637 Asic[43]:637 Asic[44]:637 Asic[45]:637 Asic[46]:637 Asic[47]:637 
Asic[48]:637 Asic[49]:637 Asic[50]:637 Asic[51]:637 Asic[52]:637 Asic[53]:637 Asic[54]:637 Asic[55]:637 
Asic[56]:637 Asic[57]:637 Asic[58]:637 Asic[59]:637 Asic[60]:637 Asic[61]:637 Asic[62]:637 
driver-btm-c5.c:4809:set_frequency: Chain:7 max freq=637
driver-btm-c5.c:4810:set_frequency: Chain:7 min freq=637


driver-btm-c5.c:4819:set_frequency: Miner fix freq ...
driver-btm-c5.c:4263:ProcessFixFreqForChips: totalRate = 13651, fixed_totalRate = 13635
driver-btm-c5.c:4854:set_frequency: read PIC voltage=940 on chain[5]
driver-btm-c5.c:4855:set_frequency: Chain:5 chipnum=63
driver-btm-c5.c:4874:set_frequency: Chain[J6] voltage added=0.0V
driver-btm-c5.c:5058:set_frequency: Chain:5 temp offset=0
driver-btm-c5.c:5063:set_frequency: Chain:5 base freq=637
Asic[ 0]:631 Asic[ 1]:631 Asic[ 2]:631 Asic[ 3]:631 Asic[ 4]:631 Asic[ 5]:631 Asic[ 6]:631 Asic[ 7]:631 
Asic[ 8]:631 Asic[ 9]:631 Asic[10]:631 Asic[11]:637 Asic[12]:637 Asic[13]:637 Asic[14]:637 Asic[15]:637 
Asic[16]:637 Asic[17]:637 Asic[18]:637 Asic[19]:637 Asic[20]:637 Asic[21]:637 Asic[22]:637 Asic[23]:637 
Asic[24]:637 Asic[25]:637 Asic[26]:637 Asic[27]:637 Asic[28]:637 Asic[29]:637 Asic[30]:637 Asic[31]:637 
Asic[32]:637 Asic[33]:637 Asic[34]:637 Asic[35]:637 Asic[36]:637 Asic[37]:637 Asic[38]:637 Asic[39]:637 
Asic[40]:637 Asic[41]:637 Asic[42]:637 Asic[43]:637 Asic[44]:637 Asic[45]:637 Asic[46]:637 Asic[47]:637 
Asic[48]:637 Asic[49]:637 Asic[50]:637 Asic[51]:637 Asic[52]:637 Asic[53]:637 Asic[54]:637 Asic[55]:637 
Asic[56]:637 Asic[57]:637 Asic[58]:637 Asic[59]:637 Asic[60]:637 Asic[61]:637 Asic[62]:637 
driver-btm-c5.c:5110:set_frequency: Chain:5 max freq=637
driver-btm-c5.c:5111:set_frequency: Chain:5 min freq=631

driver-btm-c5.c:4854:set_frequency: read PIC voltage=940 on chain[6]
driver-btm-c5.c:4855:set_frequency: Chain:6 chipnum=63
driver-btm-c5.c:4874:set_frequency: Chain[J7] voltage added=0.0V
driver-btm-c5.c:5058:set_frequency: Chain:6 temp offset=0
driver-btm-c5.c:5063:set_frequency: Chain:6 base freq=637
Asic[ 0]:631 Asic[ 1]:631 Asic[ 2]:631 Asic[ 3]:631 Asic[ 4]:631 Asic[ 5]:631 Asic[ 6]:631 Asic[ 7]:631 
Asic[ 8]:631 Asic[ 9]:631 Asic[10]:631 Asic[11]:637 Asic[12]:637 Asic[13]:637 Asic[14]:637 Asic[15]:637 
Asic[16]:637 Asic[17]:637 Asic[18]:637 Asic[19]:637 Asic[20]:637 Asic[21]:637 Asic[22]:637 Asic[23]:637 
Asic[24]:637 Asic[25]:637 Asic[26]:637 Asic[27]:637 Asic[28]:637 Asic[29]:637 Asic[30]:637 Asic[31]:637 
Asic[32]:637 Asic[33]:637 Asic[34]:637 Asic[35]:637 Asic[36]:637 Asic[37]:637 Asic[38]:637 Asic[39]:637 
Asic[40]:637 Asic[41]:637 Asic[42]:637 Asic[43]:637 Asic[44]:637 Asic[45]:637 Asic[46]:637 Asic[47]:637 
Asic[48]:637 Asic[49]:637 Asic[50]:637 Asic[51]:637 Asic[52]:637 Asic[53]:637 Asic[54]:637 Asic[55]:637 
Asic[56]:637 Asic[57]:637 Asic[58]:637 Asic[59]:637 Asic[60]:637 Asic[61]:637 Asic[62]:637 
driver-btm-c5.c:5110:set_frequency: Chain:6 max freq=637
driver-btm-c5.c:5111:set_frequency: Chain:6 min freq=631

driver-btm-c5.c:4854:set_frequency: read PIC voltage=940 on chain[7]
driver-btm-c5.c:4855:set_frequency: Chain:7 chipnum=63
driver-btm-c5.c:4874:set_frequency: Chain[J8] voltage added=0.0V
driver-btm-c5.c:5058:set_frequency: Chain:7 temp offset=0
driver-btm-c5.c:5063:set_frequency: Chain:7 base freq=637
Asic[ 0]:637 Asic[ 1]:637 Asic[ 2]:637 Asic[ 3]:637 Asic[ 4]:637 Asic[ 5]:637 Asic[ 6]:637 Asic[ 7]:637 
Asic[ 8]:637 Asic[ 9]:637 Asic[10]:637 Asic[11]:637 Asic[12]:637 Asic[13]:637 Asic[14]:637 Asic[15]:637 
Asic[16]:637 Asic[17]:637 Asic[18]:637 Asic[19]:637 Asic[20]:637 Asic[21]:637 Asic[22]:637 Asic[23]:637 
Asic[24]:637 Asic[25]:637 Asic[26]:637 Asic[27]:637 Asic[28]:637 Asic[29]:637 Asic[30]:637 Asic[31]:637 
Asic[32]:637 Asic[33]:637 Asic[34]:637 Asic[35]:637 Asic[36]:637 Asic[37]:637 Asic[38]:637 Asic[39]:637 
Asic[40]:637 Asic[41]:637 Asic[42]:637 Asic[43]:637 Asic[44]:637 Asic[45]:637 Asic[46]:637 Asic[47]:637 
Asic[48]:637 Asic[49]:637 Asic[50]:637 Asic[51]:637 Asic[52]:637 Asic[53]:637 Asic[54]:637 Asic[55]:637 
Asic[56]:637 Asic[57]:637 Asic[58]:637 Asic[59]:637 Asic[60]:637 Asic[61]:637 Asic[62]:637 
driver-btm-c5.c:5110:set_frequency: Chain:7 max freq=637
driver-btm-c5.c:5111:set_frequency: Chain:7 min freq=637

driver-btm-c5.c:5119:set_frequency: max freq = 637
driver-btm-c5.c:4162:ProcessFixFreq: totalRate = 13636, fixed_totalRate = 13500
driver-btm-c5.c:9604:init_uart_baud: set baud=1
driver-btm-c5.c:6593:calibration_sensor_offset: Chain[J6] PIC temp offset: 62,0,0,0,0,0,39,28,0,0,0,0,0,0,0,0,0,0,
driver-btm-c5.c:6627:calibration_sensor_offset: chain[6] temp chip I2C addr=0x9c
driver-btm-c5.c:6635:calibration_sensor_offset: chain[6] has no middle temp, use special fix mode.
driver-btm-c5.c:6660:calibration_sensor_offset: Chain[J6] chip[244] use PIC middle temp offset=0 typeID=55
driver-btm-c5.c:6384:do_calibration_sensor_offset: New offset Chain[6] chip[244] local:28 remote:31 offset:27 
driver-btm-c5.c:6753:calibration_sensor_offset: Chain[J6] chip[244] get middle temp offset=27 typeID=55
driver-btm-c5.c:6593:calibration_sensor_offset: Chain[J7] PIC temp offset: 62,0,0,0,0,0,39,28,0,0,0,0,0,0,0,0,0,0,
driver-btm-c5.c:6627:calibration_sensor_offset: chain[7] temp chip I2C addr=0x9c
driver-btm-c5.c:6635:calibration_sensor_offset: chain[7] has no middle temp, use special fix mode.
driver-btm-c5.c:6660:calibration_sensor_offset: Chain[J7] chip[244] use PIC middle temp offset=0 typeID=55
driver-btm-c5.c:6384:do_calibration_sensor_offset: New offset Chain[7] chip[244] local:30 remote:33 offset:27 
driver-btm-c5.c:6753:calibration_sensor_offset: Chain[J7] chip[244] get middle temp offset=27 typeID=55
driver-btm-c5.c:6593:calibration_sensor_offset: Chain[J8] PIC temp offset: 62,0,0,0,0,0,39,28,0,0,0,0,0,0,0,0,0,0,
driver-btm-c5.c:6627:calibration_sensor_offset: chain[8] temp chip I2C addr=0x9c
driver-btm-c5.c:6635:calibration_sensor_offset: chain[8] has no middle temp, use special fix mode.
driver-btm-c5.c:6660:calibration_sensor_offset: Chain[J8] chip[244] use PIC middle temp offset=0 typeID=55
driver-btm-c5.c:6384:do_calibration_sensor_offset: New offset Chain[8] chip[244] local:29 remote:33 offset:26 
driver-btm-c5.c:6753:calibration_sensor_offset: Chain[J8] chip[244] get middle temp offset=26 typeID=55
driver-btm-c5.c:13657:bitmain_c5_init: miner rate=13501 voltage limit=900 on chain[5]
driver-btm-c5.c:13688:bitmain_c5_init: get PIC voltage=890 on chain[5], check: must be < 900
driver-btm-c5.c:13657:bitmain_c5_init: miner rate=13501 voltage limit=900 on chain[6]
driver-btm-c5.c:13688:bitmain_c5_init: get PIC voltage=890 on chain[6], check: must be < 900
driver-btm-c5.c:13657:bitmain_c5_init: miner rate=13501 voltage limit=900 on chain[7]
driver-btm-c5.c:13688:bitmain_c5_init: get PIC voltage=890 on chain[7], check: must be < 900
driver-btm-c5.c:12103:set_working_voltage: setting to working voltage...
driver-btm-c5.c:12083:slowly_downgrade_voltage_all_chain: chain[5] set voltage to 930
driver-btm-c5.c:12083:slowly_downgrade_voltage_all_chain: chain[6] set voltage to 930
driver-btm-c5.c:12083:slowly_downgrade_voltage_all_chain: chain[7] set voltage to 930
driver-btm-c5.c:12083:slowly_downgrade_voltage_all_chain: chain[5] set voltage to 920
driver-btm-c5.c:12083:slowly_downgrade_voltage_all_chain: chain[6] set voltage to 920
driver-btm-c5.c:12083:slowly_downgrade_voltage_all_chain: chain[7] set voltage to 920
driver-btm-c5.c:12083:slowly_downgrade_voltage_all_chain: chain[5] set voltage to 910
driver-btm-c5.c:12083:slowly_downgrade_voltage_all_chain: chain[6] set voltage to 910
driver-btm-c5.c:12083:slowly_downgrade_voltage_all_chain: chain[7] set voltage to 910
driver-btm-c5.c:12083:slowly_downgrade_voltage_all_chain: chain[5] set voltage to 900
driver-btm-c5.c:12083:slowly_downgrade_voltage_all_chain: chain[6] set voltage to 900
driver-btm-c5.c:12083:slowly_downgrade_voltage_all_chain: chain[7] set voltage to 900
driver-btm-c5.c:12083:slowly_downgrade_voltage_all_chain: chain[5] set voltage to 890
driver-btm-c5.c:12083:slowly_downgrade_voltage_all_chain: chain[6] set voltage to 890
driver-btm-c5.c:12083:slowly_downgrade_voltage_all_chain: chain[7] set voltage to 890
driver-btm-c5.c:13954:bitmain_c5_init: start thread for read temp
setStartTimePoint total_tv_start_sys=160 total_tv_end_sys=161
driver-btm-c5.c:10320:check_system_work: restartNum = 2 , auto-reinit enabled...
driver-btm-c5.c:8727:read_temp_func: bring_up_pcb_temp = 45
do read_temp_func once...

get RT hashrate from Chain[5]: (asic index start from 1-63)
Asic[01]=0.00000 Asic[02]=0.00000 Asic[03]=0.00000 Asic[04]=0.00000 Asic[05]=0.00000 Asic[06]=0.00000 Asic[07]=0.00000 Asic[08]=0.00000 
Asic[09]=0.00000 Asic[10]=0.00000 Asic[11]=0.00000 Asic[12]=0.00000 Asic[13]=0.00000 Asic[14]=0.00000 Asic[15]=0.00000 Asic[16]=0.00000 
Asic[17]=0.00000 Asic[18]=0.00000 Asic[19]=0.00000 Asic[20]=0.00000 Asic[21]=0.00000 Asic[22]=0.00000 Asic[23]=0.00000 Asic[24]=0.00000 
Asic[25]=0.00000 Asic[26]=0.00000 Asic[27]=0.00000 Asic[28]=0.00000 Asic[29]=131.030 Asic[30]=0.00000 Asic[31]=0.00000 Asic[32]=0.00000 
Asic[33]=0.00000 Asic[34]=0.00000 Asic[35]=0.00000 Asic[36]=0.00000 Asic[37]=0.00000 Asic[38]=0.00000 Asic[39]=0.00000 Asic[40]=0.00000 
Asic[41]=0.00000 Asic[42]=0.00000 Asic[43]=0.00000 Asic[44]=0.00000 Asic[45]=0.00000 Asic[46]=0.00000 Asic[47]=0.00000 Asic[48]=0.00000 
Asic[49]=0.00000 Asic[50]=0.00000 Asic[51]=0.00000 Asic[52]=0.00000 Asic[53]=0.00000 Asic[54]=0.00000 Asic[55]=0.00000 Asic[56]=0.00000 
Asic[57]=123.966 Asic[58]=0.00000 Asic[59]=0.00000 Asic[60]=0.00000 Asic[61]=0.00000 Asic[62]=0.00000 Asic[63]=0.00000 

get RT hashrate from Chain[6]: (asic index start from 1-63)
Asic[01]=0.00000 Asic[02]=0.00000 Asic[03]=0.00000 Asic[04]=4.29400 Asic[05]=0.00000 Asic[06]=0.00000 Asic[07]=0.00000 Asic[08]=0.00000 
Asic[09]=0.00000 Asic[10]=0.00000 Asic[11]=0.00000 Asic[12]=0.00000 Asic[13]=0.00000 Asic[14]=8.58900 Asic[15]=0.00000 Asic[16]=0.00000 
Asic[17]=0.00000 Asic[18]=0.00000 Asic[19]=0.00000 Asic[20]=0.00000 Asic[21]=0.00000 Asic[22]=4.29400 Asic[23]=0.00000 Asic[24]=0.00000 
Asic[25]=0.00000 Asic[26]=0.00000 Asic[27]=4.29400 Asic[28]=0.00000 Asic[29]=122.825 Asic[30]=4.29400 Asic[31]=4.29400 Asic[32]=0.00000 
Asic[33]=4.29400 Asic[34]=0.00000 Asic[35]=0.00000 Asic[36]=4.29400 Asic[37]=0.00000 Asic[38]=0.00000 Asic[39]=4.29400 Asic[40]=0.00000 
Asic[41]=0.00000 Asic[42]=0.00000 Asic[43]=0.00000 Asic[44]=4.29400 Asic[45]=8.58900 Asic[46]=0.00000 Asic[47]=4.29400 Asic[48]=0.00000 
Asic[49]=4.29400 Asic[50]=0.00000 Asic[51]=0.00000 Asic[52]=0.00000 Asic[53]=0.00000 Asic[54]=4.29400 Asic[55]=4.29400 Asic[56]=0.00000 
Asic[57]=116.484 Asic[58]=8.58900 Asic[59]=4.29400 Asic[60]=4.29400 Asic[61]=0.00000 Asic[62]=0.00000 Asic[63]=0.00000 

get RT hashrate from Chain[7]: (asic index start from 1-63)
Asic[01]=10.7370 Asic[02]=73.0140 Asic[03]=11.2740 Asic[04]=64.4240 Asic[05]=77.3090 Asic[06]=55.8340 Asic[07]=51.5390 Asic[08]=20.4010 
Asic[09]=60.1290 Asic[10]=98.7840 Asic[11]=7.51600 Asic[12]=9.39500 Asic[13]=30.8700 Asic[14]=9.66300 Asic[15]=9.12600 Asic[16]=12.0790 
Asic[17]=9.12600 Asic[18]=68.7190 Asic[19]=60.1290 Asic[20]=81.6040 Asic[21]=81.6040 Asic[22]=60.1290 Asic[23]=77.3090 Asic[24]=77.3090 
Asic[25]=77.3090 Asic[26]=64.4240 Asic[27]=60.1290 Asic[28]=9.39500 Asic[29]=128.463 Asic[30]=85.8990 Asic[31]=81.6040 Asic[32]=73.0140 
Asic[33]=64.4240 Asic[34]=55.8340 Asic[35]=17.7160 Asic[36]=81.6040 Asic[37]=10.2000 Asic[38]=77.3090 Asic[39]=8.32100 Asic[40]=8.58900 
Asic[41]=98.7840 Asic[42]=11.2740 Asic[43]=68.7190 Asic[44]=98.7840 Asic[45]=10.2000 Asic[46]=103.079 Asic[47]=94.4890 Asic[48]=13.4210 
Asic[49]=8.32100 Asic[50]=11.8110 Asic[51]=68.7190 Asic[52]=60.1290 Asic[53]=7.51600 Asic[54]=9.93200 Asic[55]=68.7190 Asic[56]=68.7190 
Asic[57]=121.316 Asic[58]=12.3480 Asic[59]=64.4240 Asic[60]=9.39500 Asic[61]=8.85800 Asic[62]=77.3090 Asic[63]=90.1940 
Check Chain[J6] ASIC RT error: (asic index start from 1-63)
Asic[29]=131.030000
Asic[57]=123.966000
Check Chain[J7] ASIC RT error: (asic index start from 1-63)
Asic[29]=122.825000
Asic[57]=116.484000
Check Chain[J8] ASIC RT error: (asic index start from 1-63)
Asic[29]=128.463000
Asic[46]=103.079000
Asic[57]=121.316000
Done check_asic_reg
Chain[5] Chip[244] pcb temperature=44
Chain[5] Chip[62] junction temperature=33
Special fix Chain[5] Chip[62] middle Temp = 59
Done read temp on Chain[5]
Chain[6] Chip[244] pcb temperature=45
Chain[6] Chip[62] junction temperature=33
Special fix Chain[6] Chip[62] middle Temp = 60
Done read temp on Chain[6]
Chain[7] Chip[244] pcb temperature=42
Chain[7] Chip[62] junction temperature=31
Special fix Chain[7] Chip[62] middle Temp = 57
Done read temp on Chain[7]
Max pcb temp : 45
set FAN speed according to: temp_highest=45 temp_top1[PWM_T]=45 temp_top1[TEMP_POS_LOCAL]=45 temp_change=45 fix_fan_steps=0
set normal FAN speed...
pwm_percent = 40
FAN PWM: 40
read_temp_func Done!
CRC error counter=0
mikeywith
legendary
Activity: 2394
Merit: 6581
be constructive or S.T.F.U
Re: ANTMINER S9 reporting extremely low hashrate
December 15, 2020, 11:31:57 AM
#6
It must be the old firmware that does that? the recent firmware versions will not start hasing if both fans are not in great "shape".

The 30,000 rpm it shows is kind of pretty normal for non-stock fans, i had the same readings on many used S9s, but your point makes sense, i would still check the fans, the miner seems to be rebooting and thus anything from a bad fan to a dirty psu will do that.
NotFuzzyWarm
legendary
Activity: 3822
Merit: 2703
Evil beware: We have waffles!
Re: ANTMINER S9 reporting extremely low hashrate
December 14, 2020, 01:18:34 PM
#5
Another possibility is that 1 fan is dead. When I used to run s9's I came across this problem fairly often. Most often the exhaust fan dies but is seen still spinning - but only because the 1 working fan is moving air through it. 1 fan is not enough and every 1/2 hr or so the miners would restart after doing an overtemp shutdown.

Fan5 is reporting over 30krpm which is obviously wrong...
mikeywith
legendary
Activity: 2394
Merit: 6581
be constructive or S.T.F.U
Re: ANTMINER S9 reporting extremely low hashrate
December 14, 2020, 12:03:17 PM
#4
Quote from: BitMaxz on December 13, 2020, 06:39:43 PM
The issue might be in the pool server or your internet, high ping or slow internet can affect your reported hashrate on the pool.
So, try to use other pool servers that are closest to your location.

I would keep this, at last, it's unlikely that OP is facing a connection/network related issue, and here is my reasoning:

- Two different mining pools reporting the same problem
- It was a sudden problem and nothing new (according to my understanding of his words).

based on that, the issue seems to be constant rebooting, when the miner goes into a reboot cycle, the hashrate on the pool will be really low, this is the first suspect, what gives this theory more strength is the fact that the miner's run time is pretty small.
BitMaxz
legendary
Activity: 3374
Merit: 3095
Playbet.io - Crypto Casino and Sportsbook
Re: ANTMINER S9 reporting extremely low hashrate
December 13, 2020, 06:39:43 PM
#3
The screenshot doesn't show anything and it looks like the miner status report is showing fine with 2 hardware errors.

The issue might be in the pool server or your internet, high ping or slow internet can affect your reported hashrate on the pool.
So, try to use other pool servers that are closest to your location.

Or follow my method to check the pool ping from this link below.
- https://bitcointalksearch.org/topic/m.52084230

and use this as reference:

Quote from: philipma1957 on August 06, 2019, 06:59:38 PM
Ping guide

300 or more = bad

100 to 300 will be somewhat inconsistent

100 or lower = good

I don’t mine on 300+ pings.
mikeywith
legendary
Activity: 2394
Merit: 6581
be constructive or S.T.F.U
Re: ANTMINER S9 reporting extremely low hashrate
December 13, 2020, 04:23:23 PM
#2
Quote from: barszczewski on December 13, 2020, 11:17:47 AM
Hey guys, I've been running my S9 for about a month without any real issues. Only thing is that lately my pool reported hashrate will be anywhere between 1-12 TH/s. This issue is occurring with both Nicehash and Poolin. 

First thing you to do, avoid nicehash, at least while troubleshooting the miner, and then post the kernel log using the code function

Code:
kernel log goes here

I also noticed that the runtime is only 22 mins in the image you uploaded, did you manually reboot the miner?
barszczewski
newbie
Activity: 4
Merit: 0
Re: ANTMINER S9 reporting extremely low hashrate
December 13, 2020, 11:17:47 AM
#1
Hey guys, I've been running my S9 for about a month without any real issues. Only thing is that lately my pool reported hashrate will be anywhere between 1-12 TH/s. This issue is occurring with both Nicehash and Poolin.
I've already attempted a soft/hard reboot, firmware reflash, and psu swap.

miner status page: https://imgur.com/a/bjMpO7J

Any advice this board can give me would be much appreciated. Thanks!
Bitcoin Forum>Bitcoin>Mining>Mining support
Jump to: