Author

Topic: S9 not hashing after power failure (Read 199 times)

member
Activity: 166
Merit: 82
EET/NASA intern 2013 Bitmain/MicroBT/IPC cert
August 30, 2022, 07:13:55 AM
#10
Step one is always check your power. You should watch your 12 V power supply output for fluctuations until your log reports zero ASIC. There are like four mini power supplies on the control board to check. And finally each hashboard has a buck 10v and a boost 14v voltage that need to be confirmed.

Given your strange results, low pic voltage, surprising number of single core ASIC, etc. I suspect you have a failing supply somewhere although it is not out right dead.

I agree these boards are worth repairing as long as you can avoid the labor lol at this point with BTC at the bottom converting electricity into coin is probably wise until (and for when)it goes back up.
legendary
Activity: 2170
Merit: 6279
be constructive or S.T.F.U
August 24, 2022, 10:33:24 PM
#9
Take out the boards on 7 and 8 connector (2 and 3 from left to right).

You should always assume that the arrangement might have changed at some point, I think the best practice I try to stick to when trying to help someone identify which board is which is to ensure that I mention "if the arrangement is factory default" so really, the best way to tell would be to check where the ribbon is going to/from, that way you won't unplug a good hashboard and leave the bad one in.
newbie
Activity: 11
Merit: 4
August 24, 2022, 03:32:34 AM
#8
Hi

Take out the boards on 7 and 8 connector (2 and 3 from left to right).
Move the 6 board to 7 or 8, start the miner with this one board. If its still 0 asics, this board has isues.
Live the miner with 2 board till you get the 3rd.
legendary
Activity: 2170
Merit: 6279
be constructive or S.T.F.U
August 15, 2022, 07:08:43 PM
#7
In a normal world I would assume it's a dead hashboard, but since this happened after a power cut/failure -- it could very well be your PSU.

First thing first, visually inspect the 6 pin connectors on you Chain[J6], you can follow the ribbon cables going into the control board to identify which one is J6, if it's the default arangment this should be the board on the left side when you facing the miner, now if the 6 pin connectors are good, then simply unplug the other two hash boards, saw the connectors and the data/ribbon cables from another board and test this one board alone.

Also, in many cases, a simple Sd-card flash can fix many of these issues, your control board might have had some issues during the power failure and just needs fresh firmware, so don't discard that.
legendary
Activity: 3234
Merit: 2943
Block halving is coming.
August 12, 2022, 05:22:53 PM
#6
I don't think if this is the hashboard issue you need to check and verify first if this is actually the hashboard issue.

Look at this logs

Code:
main.c:9183: get PIC voltage=6 on chain[5], value=940
main.c:9183: get PIC voltage=142 on chain[6], value=860
main.c:9183: get PIC voltage=125 on chain[7], value=870

I noticed abnormal power on Chain[5] it might be a PSU issue, not the hashboard since you said earlier that there had been a power failure recently mostly affected are PSU.

What I would like you to do is try to swap PSU cables and ribbon cables of that hashboard then test them one by one to make sure if one hashboard is broken. If you don't know how to test them one by one check this link below.

- https://support.bitmain.com/hc/en-us/articles/226142788-Test-Hash-Board-one-by-one
legendary
Activity: 4102
Merit: 7765
'The right to privacy matters'
August 12, 2022, 09:43:06 AM
#5
Look at this:
https://www.zeusbtc.com/articles/maintenance-and-operation/1218-miner-normal-operating-temperature-range
Normal working range of S9 miner: PCB max. 90
But in your log it shows like this:
Code:
max pcb temperature: 94, fan num: 2, error counter: 1
max pcb temperature: 99, fan num: 2, error counter: 2
Fatal error, turning off hash boards power...
max pcb temperature : 99, fan num : 2
driver-btm-c5.c:9037:read_temp_func: Do not clear run bit
Fatal Error: Temperature is too high!
max pcb temperature: 99, fan num: 2, error counter: 3
Fatal error, turning off hash boards power...
max pcb temperature : 99, fan num : 2
driver-btm-c5.c:9037:read_temp_func: Do not clear run bit
Fatal Error: Temperature is too high!

That's why there is no hash. So, maybe one of the hashboards is broken:

Code:
driver-btm-c5.c:13421:bitmain_c5_init: Chain[J6] has 0 asic
driver-btm-c5.c:13449:bitmain_c5_init: retry Chain[J6] has 0 asic
driver-btm-c5.c:13449:bitmain_c5_init: retry Chain[J6] has 0 asic
driver-btm-c5.c:13449:bitmain_c5_init: retry Chain[J6] has 0 asic
driver-btm-c5.c:13449:bitmain_c5_init: retry Chain[J6] has 0 asic
driver-btm-c5.c:13449:bitmain_c5_init: retry Chain[J6] has 0 asic
driver-btm-c5.c:13449:bitmain_c5_init: retry Chain[J6] has 0 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

If you have a test fixture, you can use the test fixture to test this board.

So is the hashboard repairable or will I have to get a new one?

Note you did a follow up so I gave you a merit.

I am USA based I have s9 parts all over my house and my mine.  If you are in USA contact me I may be able to help out with spare parts.
legendary
Activity: 3458
Merit: 6231
Crypto Swap Exchange
August 12, 2022, 08:56:22 AM
#4
So is the hashboard repairable or will I have to get a new one?

Yes it IS repairable but it's probably not worth it.
Depending on where in the world you are located you can easily get an entire S9 delivered to you for under $200
Shipping it to someone to fix it paying them to fix it and then paying to get it shipped back will cost you....

Post here: https://bitcointalk.org/index.php?board=75.0 and ask for a board. Let people know what country you are in. You can most likely get one cheap out of of someones parts bin. Also make sure you let them know the model. S9 vs S9j vs S9k and so on.

-Dave
newbie
Activity: 3
Merit: 1
August 12, 2022, 07:06:31 AM
#3
Look at this:
https://www.zeusbtc.com/articles/maintenance-and-operation/1218-miner-normal-operating-temperature-range
Normal working range of S9 miner: PCB max. 90
But in your log it shows like this:
Code:
max pcb temperature: 94, fan num: 2, error counter: 1
max pcb temperature: 99, fan num: 2, error counter: 2
Fatal error, turning off hash boards power...
max pcb temperature : 99, fan num : 2
driver-btm-c5.c:9037:read_temp_func: Do not clear run bit
Fatal Error: Temperature is too high!
max pcb temperature: 99, fan num: 2, error counter: 3
Fatal error, turning off hash boards power...
max pcb temperature : 99, fan num : 2
driver-btm-c5.c:9037:read_temp_func: Do not clear run bit
Fatal Error: Temperature is too high!

That's why there is no hash. So, maybe one of the hashboards is broken:

Code:
driver-btm-c5.c:13421:bitmain_c5_init: Chain[J6] has 0 asic
driver-btm-c5.c:13449:bitmain_c5_init: retry Chain[J6] has 0 asic
driver-btm-c5.c:13449:bitmain_c5_init: retry Chain[J6] has 0 asic
driver-btm-c5.c:13449:bitmain_c5_init: retry Chain[J6] has 0 asic
driver-btm-c5.c:13449:bitmain_c5_init: retry Chain[J6] has 0 asic
driver-btm-c5.c:13449:bitmain_c5_init: retry Chain[J6] has 0 asic
driver-btm-c5.c:13449:bitmain_c5_init: retry Chain[J6] has 0 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

If you have a test fixture, you can use the test fixture to test this board.

So is the hashboard repairable or will I have to get a new one?
jr. member
Activity: 56
Merit: 12
August 12, 2022, 04:38:05 AM
#2
Look at this:
https://www.zeusbtc.com/articles/maintenance-and-operation/1218-miner-normal-operating-temperature-range
Normal working range of S9 miner: PCB max. 90
But in your log it shows like this:
Code:
max pcb temperature: 94, fan num: 2, error counter: 1
max pcb temperature: 99, fan num: 2, error counter: 2
Fatal error, turning off hash boards power...
max pcb temperature : 99, fan num : 2
driver-btm-c5.c:9037:read_temp_func: Do not clear run bit
Fatal Error: Temperature is too high!
max pcb temperature: 99, fan num: 2, error counter: 3
Fatal error, turning off hash boards power...
max pcb temperature : 99, fan num : 2
driver-btm-c5.c:9037:read_temp_func: Do not clear run bit
Fatal Error: Temperature is too high!

That's why there is no hash. So, maybe one of the hashboards is broken:

Code:
driver-btm-c5.c:13421:bitmain_c5_init: Chain[J6] has 0 asic
driver-btm-c5.c:13449:bitmain_c5_init: retry Chain[J6] has 0 asic
driver-btm-c5.c:13449:bitmain_c5_init: retry Chain[J6] has 0 asic
driver-btm-c5.c:13449:bitmain_c5_init: retry Chain[J6] has 0 asic
driver-btm-c5.c:13449:bitmain_c5_init: retry Chain[J6] has 0 asic
driver-btm-c5.c:13449:bitmain_c5_init: retry Chain[J6] has 0 asic
driver-btm-c5.c:13449:bitmain_c5_init: retry Chain[J6] has 0 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

If you have a test fixture, you can use the test fixture to test this board.
newbie
Activity: 3
Merit: 1
August 12, 2022, 03:37:46 AM
#1
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.000295] ps7-ttc #0 at df804000, irq=43
[    0.000597] Console: colour dummy device 80x30
[    0.000627] Calibrating delay loop... 1332.01 BogoMIPS (lpj=6660096)
[    0.090245] pid_max: default: 32768 minimum: 301
[    0.090451] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
[    0.090472] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
[    0.092638] CPU: Testing write buffer coherency: ok
[    0.092944] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
[    0.093001] Setting up static identity map for 0x4cb118 - 0x4cb170
[    0.093222] L310 cache controller enabled
[    0.093242] l2x0: 8 ways, CACHE_ID 0x410000c8, AUX_CTRL 0x72760000, Cache size: 512 kB
[    0.170990] CPU1: Booted secondary processor
[    0.260221] CPU1: thread -1, cpu 1, socket 0, mpidr 80000001
[    0.260350] Brought up 2 CPUs
[    0.260369] SMP: Total of 2 processors activated.
[    0.260377] CPU: All CPU(s) started in SVC mode.
[    0.261046] devtmpfs: initialized
[    0.263475] VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4
[    0.264657] regulator-dummy: no parameters
[    0.272002] NET: Registered protocol family 16
[    0.274218] DMA: preallocated 256 KiB pool for atomic coherent allocations
[    0.276481] cpuidle: using governor ladder
[    0.276493] cpuidle: using governor menu
[    0.283835] syscon f8000000.ps7-slcr: regmap [mem 0xf8000000-0xf8000fff] registered
[    0.285349] hw-breakpoint: found 5 (+1 reserved) breakpoint and 1 watchpoint registers.
[    0.285361] hw-breakpoint: maximum watchpoint size is 4 bytes.
[    0.285472] zynq-ocm f800c000.ps7-ocmc: ZYNQ OCM pool: 256 KiB @ 0xdf880000
[    0.307261] bio: create slab at 0
[    0.308631] vgaarb: loaded
[    0.309327] SCSI subsystem initialized
[    0.310245] usbcore: registered new interface driver usbfs
[    0.310898] usbcore: registered new interface driver hub
[    0.311174] usbcore: registered new device driver usb
[    0.311691] media: Linux media interface: v0.10
[    0.311855] Linux video capture interface: v2.00
[    0.312092] pps_core: LinuxPPS API ver. 1 registered
[    0.312104] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti
[    0.312225] PTP clock support registered
[    0.312585] EDAC MC: Ver: 3.0.0
[    0.313775] Advanced Linux Sound Architecture Driver Initialized.
[    0.316497] DMA-API: preallocated 4096 debug entries
[    0.316511] DMA-API: debugging enabled by kernel config
[    0.316578] Switched to clocksource arm_global_timer
[    0.336537] NET: Registered protocol family 2
[    0.337489] TCP established hash table entries: 4096 (order: 2, 16384 bytes)
[    0.337547] TCP bind hash table entries: 4096 (order: 3, 32768 bytes)
[    0.337631] TCP: Hash tables configured (established 4096 bind 4096)
[    0.337674] TCP: reno registered
[    0.337691] UDP hash table entries: 256 (order: 1, 8192 bytes)
[    0.337721] UDP-Lite hash table entries: 256 (order: 1, 8192 bytes)
[    0.337959] NET: Registered protocol family 1
[    0.338304] RPC: Registered named UNIX socket transport module.
[    0.338317] RPC: Registered udp transport module.
[    0.338326] RPC: Registered tcp transport module.
[    0.338334] RPC: Registered tcp NFSv4.1 backchannel transport module.
[    0.338346] PCI: CLS 0 bytes, default 64
[    0.338771] hw perfevents: enabled with ARMv7 Cortex-A9 PMU driver, 7 counters available
[    0.340765] futex hash table entries: 512 (order: 3, 32768 bytes)
[    0.342805] jffs2: version 2.2. (NAND) © 2001-2006 Red Hat, Inc.
[    0.342994] msgmni has been set to 967
[    0.343756] io scheduler noop registered
[    0.343769] io scheduler deadline registered
[    0.343808] io scheduler cfq registered (default)
[    0.356382] dma-pl330 f8003000.ps7-dma: Loaded driver for PL330 DMAC-2364208
[    0.356402] dma-pl330 f8003000.ps7-dma: DBUFF-128x8bytes Num_Chans-8 Num_Peri-4 Num_Events-16
[    0.479008] e0001000.serial: ttyPS0 at MMIO 0xe0001000 (irq = 82, base_baud = 3124999) is a xuartps
[    1.045966] console [ttyPS0] enabled
[    1.050241] xdevcfg f8007000.ps7-dev-cfg: ioremap 0xf8007000 to df866000
[    1.057843] [drm] Initialized drm 1.1.0 20060810
[    1.074779] brd: module loaded
[    1.084155] loop: module loaded
[    1.093571] e1000e: Intel(R) PRO/1000 Network Driver - 2.3.2-k
[    1.099548] e1000e: Copyright(c) 1999 - 2013 Intel Corporation.
[    1.107350] libphy: XEMACPS mii bus: probed
[    1.111719] ------------- phy_id = 0x3625e62
[    1.116419] xemacps e000b000.ps7-ethernet: pdev->id -1, baseaddr 0xe000b000, irq 54
[    1.125061] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[    1.131709] ehci-pci: EHCI PCI platform driver
[    1.138936] zynq-dr e0002000.ps7-usb: Unable to init USB phy, missing?
[    1.145727] usbcore: registered new interface driver usb-storage
[    1.152626] mousedev: PS/2 mouse device common for all mice
[    1.158743] i2c /dev entries driver
[    1.165621] zynq-edac f8006000.ps7-ddrc: ecc not enabled
[    1.171149] cpufreq_cpu0: failed to get cpu0 regulator: -19
[    1.177041] Xilinx Zynq CpuIdle Driver started
[    1.181897] sdhci: Secure Digital Host Controller Interface driver
[    1.188034] sdhci: Copyright(c) Pierre Ossman
[    1.192330] sdhci-pltfm: SDHCI platform and OF driver helper
[    1.199198] mmc0: no vqmmc regulator found
[    1.203209] mmc0: no vmmc regulator found
[    1.246597] mmc0: SDHCI controller on e0100000.ps7-sdio [e0100000.ps7-sdio] using ADMA
[    1.255260] usbcore: registered new interface driver usbhid
[    1.260768] usbhid: USB HID core driver
[    1.265463] nand: device found, Manufacturer ID: 0x2c, Chip ID: 0xda
[    1.271765] nand: Micron MT29F2G08ABAEAWP
[    1.275730] nand: 256MiB, SLC, page size: 2048, OOB size: 64
[    1.281668] Bad block table found at page 131008, version 0x01
[    1.287888] Bad block table found at page 130944, version 0x01
[    1.293937] 3 ofpart partitions found on MTD device pl353-nand
[    1.299727] Creating 3 MTD partitions on "pl353-nand":
[    1.304812] 0x000000000000-0x000002000000 : "BOOT.bin-env-dts-kernel"
[    1.312868] 0x000002000000-0x00000b000000 : "angstram-rootfs"
[    1.320172] 0x00000b000000-0x000010000000 : "upgrade-rootfs"
[    1.330900] TCP: cubic registered
[    1.334138] NET: Registered protocol family 17
[    1.338834] Registering SWP/SWPB emulation handler
[    1.344694] regulator-dummy: disabling
[    1.349016] UBI: attaching mtd1 to ubi0
[    1.873875] UBI: scanning is finished
[    1.885467] UBI: attached mtd1 (name "angstram-rootfs", size 144 MiB) to ubi0
[    1.892549] UBI: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
[    1.899311] UBI: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
[    1.905975] UBI: VID header offset: 2048 (aligned 2048), data offset: 4096
[    1.912853] UBI: good PEBs: 1152, bad PEBs: 0, corrupted PEBs: 0
[    1.918833] UBI: user volume: 1, internal volumes: 1, max. volumes count: 128
[    1.925941] UBI: max/mean erase counter: 2/0, WL threshold: 4096, image sequence number: 1754858191
[    1.934984] UBI: available PEBs: 0, total reserved PEBs: 1152, PEBs reserved for bad PEB handling: 40
[    1.944200] UBI: background thread "ubi_bgt0d" started, PID 1084
[    1.944205] drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
[    1.948139] ALSA device list:
[    1.948143]   No soundcards found.
[    1.964484] UBIFS: background thread "ubifs_bgt0_0" started, PID 1086
[    1.993424] UBIFS: recovery needed
[    2.082310] UBIFS: recovery completed
[    2.085977] UBIFS: mounted UBI device 0, volume 0, name "rootfs"
[    2.091924] UBIFS: LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
[    2.101031] UBIFS: FS size: 128626688 bytes (122 MiB, 1013 LEBs), journal size 9023488 bytes (8 MiB, 72 LEBs)
[    2.110920] UBIFS: reserved for root: 0 bytes (0 KiB)
[    2.115949] UBIFS: media format: w4/r0 (latest is w4/r0), UUID 7024E062-5923-42D9-8915-DFE72B38FE49, small LPT model
[    2.127249] VFS: Mounted root (ubifs filesystem) on device 0:11.
[    2.134416] devtmpfs: mounted
[    2.137547] Freeing unused kernel memory: 204K (c06db000 - c070e000)
[    2.968780] random: dd urandom read with 1 bits of entropy available
[    3.356621]
[    3.356621] bcm54xx_config_init
[    4.426622]
[    4.426622] bcm54xx_config_init
[    7.427449] xemacps e000b000.ps7-ethernet: Set clk to 24999999 Hz
[    7.433542] xemacps e000b000.ps7-ethernet: link up (100/FULL)
[   21.028430] In axi fpga driver!
[   21.031498] request_mem_region OK!
[   21.034888] AXI fpga dev virtual address is 0xdf9fe000
[   21.040028] *base_vir_addr = 0xc51e
[   21.054671] In fpga mem driver!
[   21.058063] request_mem_region OK!
[   21.061571] fpga mem virtual address is 0xe2000000
[   21.856595]
[   21.856595] bcm54xx_config_init
[   22.946620]
[   22.946620] bcm54xx_config_init
[   25.947442] xemacps e000b000.ps7-ethernet: Set clk to 24999999 Hz
[   25.953459] xemacps e000b000.ps7-ethernet: link up (100/FULL)
main.c:13992: log_level = 4
main.c:14019: This is XILINX board. Totalram:       507486208
main.c:14031: Detect 512MB control board of XILINX
driver-bitmain.c:1776: mmap axi_fpga_addr = 0xb6f87000
driver-bitmain.c:1781: axi_fpga_addr data = 0xc51e
driver-bitmain.c:1797: mmap fpga_mem_addr = 0xb5d80000
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 : 8062240005904814
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:22] [63:5] [63:24] [63:25] [63:49] [63:37] [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[0] has core num=1
main.c:9113: Chain[5] ASIC[2] has core num=1
main.c:9113: Chain[5] ASIC[3] has core num=2
main.c:9113: Chain[5] ASIC[4] has core num=1
main.c:9113: Chain[5] ASIC[5] has core num=2
main.c:9113: Chain[5] ASIC[6] has core num=1
main.c:9113: Chain[5] ASIC[7] has core num=1
main.c:9113: Chain[5] ASIC[8] has core num=1
main.c:9113: Chain[5] ASIC[9] has core num=1
main.c:9113: Chain[5] ASIC[10] has core num=1
main.c:9113: Chain[5] ASIC[11] has core num=1
main.c:9113: Chain[5] ASIC[12] has core num=1
main.c:9113: Chain[5] ASIC[13] has core num=1
main.c:9113: Chain[5] ASIC[14] has core num=2
main.c:9113: Chain[5] ASIC[15] has core num=1
main.c:9113: Chain[5] ASIC[16] has core num=1
main.c:9113: Chain[5] ASIC[17] has core num=2
main.c:9113: Chain[5] ASIC[18] has core num=2
main.c:9113: Chain[5] ASIC[19] has core num=1
main.c:9113: Chain[5] ASIC[20] has core num=1
main.c:9113: Chain[5] ASIC[21] has core num=1
main.c:9113: Chain[5] ASIC[22] has core num=1
main.c:9113: Chain[5] ASIC[23] has core num=1
main.c:9113: Chain[5] ASIC[24] has core num=1
main.c:9113: Chain[5] ASIC[25] has core num=1
main.c:9113: Chain[5] ASIC[26] has core num=1
main.c:9113: Chain[5] ASIC[27] has core num=1
main.c:9113: Chain[5] ASIC[28] has core num=1
main.c:9113: Chain[5] ASIC[29] has core num=3
main.c:9113: Chain[5] ASIC[30] has core num=1
main.c:9113: Chain[5] ASIC[31] has core num=1
main.c:9113: Chain[5] ASIC[32] has core num=1
main.c:9113: Chain[5] ASIC[33] has core num=2
main.c:9113: Chain[5] ASIC[34] has core num=1
main.c:9113: Chain[5] ASIC[35] has core num=1
main.c:9113: Chain[5] ASIC[36] has core num=2
main.c:9113: Chain[5] ASIC[37] has core num=1
main.c:9113: Chain[5] ASIC[38] has core num=2
main.c:9113: Chain[5] ASIC[39] has core num=2
main.c:9113: Chain[5] ASIC[40] has core num=2
main.c:9113: Chain[5] ASIC[41] has core num=1
main.c:9113: Chain[5] ASIC[42] has core num=2
main.c:9113: Chain[5] ASIC[43] has core num=1
main.c:9113: Chain[5] ASIC[45] has core num=1
main.c:9113: Chain[5] ASIC[46] has core num=2
main.c:9113: Chain[5] ASIC[47] has core num=1
main.c:9113: Chain[5] ASIC[48] has core num=1
main.c:9113: Chain[5] ASIC[49] has core num=1
main.c:9113: Chain[5] ASIC[50] has core num=1
main.c:9113: Chain[5] ASIC[51] has core num=1
main.c:9113: Chain[5] ASIC[52] has core num=1
main.c:9113: Chain[5] ASIC[53] has core num=1
main.c:9113: Chain[5] ASIC[54] has core num=1
main.c:9113: Chain[5] ASIC[55] has core num=1
main.c:9113: Chain[5] ASIC[56] has core num=1
main.c:9113: Chain[5] ASIC[57] has core num=1
main.c:9113: Chain[5] ASIC[58] has core num=1
main.c:9113: Chain[5] ASIC[59] has core num=1
main.c:9113: Chain[5] ASIC[60] has core num=1
main.c:9113: Chain[5] ASIC[61] has core num=2
main.c:9113: Chain[5] ASIC[62] 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:9113: Chain[6] ASIC[7] has core num=1
main.c:9113: Chain[6] ASIC[9] has core num=1
main.c:9113: Chain[6] ASIC[29] has core num=1
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[37] has core num=15
main.c:9113: Chain[7] ASIC[45] has core num=1
main.c:2282: Check chain[7] PIC fw version=0x03
main.c:9183: get PIC voltage=6 on chain[5], value=940
main.c:9183: get PIC voltage=142 on chain[6], value=860
main.c:9183: get PIC voltage=125 on chain[7], value=870
main.c:9349: chain[5] temp offset record: 62,0,0,0,0,0,33,0
main.c:9366: chain[5] temp chip I2C addr=0x98
main.c:9349: chain[6] temp offset record: 62,0,0,0,0,0,35,28
main.c:9366: chain[6] temp chip I2C addr=0x98
main.c:9372: chain[6] has no middle temp, use special fix mode.
main.c:9349: chain[7] temp offset record: 62,-76,0,0,0,0,33,0
main.c:9366: chain[7] temp chip I2C addr=0x98
main.c:13956: total_exist_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= 1829 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:17:30 CST 2019 type: Antminer S9j
driver-btm-c5.c:12414:bitmain_c5_init: miner ID : 8062240005904814
driver-btm-c5.c:12571:bitmain_c5_init: Checking fans...
driver-btm-c5.c:3006:check_fan_beforeInit: get fan[4] speed=4560
driver-btm-c5.c:3006:check_fan_beforeInit: get fan[4] speed=4560
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=4560
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=4560
driver-btm-c5.c:3006:check_fan_beforeInit: get fan[5] speed=6120
driver-btm-c5.c:13108:bitmain_c5_init: chain[5]: [63:22] [63:5] [63:24] [63:25] [63:49] [63:37] [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 0x03 0x48 0x03 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:13149:bitmain_c5_init: Detect: use voltage limit rules on single board!
driver-btm-c5.c:13155:bitmain_c5_init: Detect: S9_63 use voltage level=1 : 1
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 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
driver-btm-c5.c:13149:bitmain_c5_init: Detect: use voltage limit rules on single board!
driver-btm-c5.c:13155:bitmain_c5_init: Detect: S9_63 use voltage level=1 : 1
driver-btm-c5.c:13171:bitmain_c5_init: Chain[J7] has backup chain_voltage=860
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 0x0f 0x4c 0x0c 0x4c 0x04 0x4c 0x0c 0x4c 0x00 0x4c 0x03 0x4c 0x03 0x4c 0x03 0x4c 0x03 0x4c 0x03 0x4c 0x03 0x4c 0x01 0x4c 0x01 0x4c 0x0f 0x4c 0x0f 0x4c 0x0f 0x4c 0x0f 0x4c 0x05 0x4c 0x07 0x4c 0x23 0x4c 0x00 0x4c 0x00 0x4c 0x00 0x4c 0x00 0x4c 0x00 0x4c 0x00 0x4c 0x00 0x4c 0x00 0x4c 0x00 0x4c 0x00 0x4c 0x00 0x4c 0x00 0x4c 0x00 0x4c 0x00 0x4c 0x00 0x4c 0x00 0x4c 0x00 0x4c 0x00 0x4c 0x00 0x4c 0x00 0x4c 0x00 0x4c 0x00 0x4c 0x00 0x4c 0x00 0x4c 0x00 0x4c 0x00 0x4c 0x00 0x4c 0x00 0x4c 0x00 0x4c 0x00 0x4c 0x00 0x4c 0x00 0x4c 0x00 0x4c 0x00 0x4c 0x00 0x4c 0x00 0x4c 0x00 0x4c 0x00 0x4c 0x00 0x4c 0x00 0x4c 0x00 0x4c 0x00 0x4c 0x00 0x4c
driver-btm-c5.c:13149:bitmain_c5_init: Detect: use voltage limit rules on single board!
driver-btm-c5.c:13155:bitmain_c5_init: Detect: S9_63 use voltage level=1 : 1
driver-btm-c5.c:13171:bitmain_c5_init: Chain[J8] has backup chain_voltage=870
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=6 value=940
driver-btm-c5.c:13320:bitmain_c5_init: Chain[J6] will use backup chain_voltage_pic=890 [91]
driver-btm-c5.c:13330:bitmain_c5_init: Chain[J6] get working chain_voltage_pic=91
driver-btm-c5.c:13303:bitmain_c5_init: Chain[J7] orignal chain_voltage_pic=142 value=860
driver-btm-c5.c:13303:bitmain_c5_init: Chain[J8] orignal chain_voltage_pic=125 value=870
driver-btm-c5.c:13421:bitmain_c5_init: Chain[J6] has 0 asic
driver-btm-c5.c:13449:bitmain_c5_init: retry Chain[J6] has 0 asic
driver-btm-c5.c:13449:bitmain_c5_init: retry Chain[J6] has 0 asic
driver-btm-c5.c:13449:bitmain_c5_init: retry Chain[J6] has 0 asic
driver-btm-c5.c:13449:bitmain_c5_init: retry Chain[J6] has 0 asic
driver-btm-c5.c:13449:bitmain_c5_init: retry Chain[J6] has 0 asic
driver-btm-c5.c:13449:bitmain_c5_init: retry Chain[J6] has 0 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[J7] has core num in PIC
driver-btm-c5.c:4541:set_frequency: Chain[J7] ASIC[7] has core num=1
driver-btm-c5.c:4541:set_frequency: Chain[J7] ASIC[9] has core num=1
driver-btm-c5.c:4541:set_frequency: Chain[J7] ASIC[29] has core num=1
driver-btm-c5.c:4531:set_frequency: Chain[J8] has core num in PIC
driver-btm-c5.c:4541:set_frequency: Chain[J8] ASIC[37] has core num=15
driver-btm-c5.c:4541:set_frequency: Chain[J8] ASIC[45] has core num=1
driver-btm-c5.c:4571:set_frequency: miner total rate=9524GH/s ideal_total_hash_rate = 9500GH/s
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=675
Asic[ 0]:675 Asic[ 1]:675 Asic[ 2]:675 Asic[ 3]:675 Asic[ 4]:675 Asic[ 5]:675 Asic[ 6]:675 Asic[ 7]:675
Asic[ 8]:675 Asic[ 9]:675 Asic[10]:675 Asic[11]:675 Asic[12]:675 Asic[13]:675 Asic[14]:675 Asic[15]:675
Asic[16]:675 Asic[17]:675 Asic[18]:675 Asic[19]:675 Asic[20]:675 Asic[21]:675 Asic[22]:675 Asic[23]:675
Asic[24]:675 Asic[25]:675 Asic[26]:675 Asic[27]:675 Asic[28]:675 Asic[29]:675 Asic[30]:675 Asic[31]:675
Asic[32]:675 Asic[33]:675 Asic[34]:675 Asic[35]:675 Asic[36]:675 Asic[37]:675 Asic[38]:675 Asic[39]:675
Asic[40]:675 Asic[41]:675 Asic[42]:675 Asic[43]:675 Asic[44]:675 Asic[45]:675 Asic[46]:675 Asic[47]:675
Asic[48]:675 Asic[49]:675 Asic[50]:675 Asic[51]:675 Asic[52]:675 Asic[53]:675 Asic[54]:675 Asic[55]:675
Asic[56]:675 Asic[57]:675 Asic[58]:675 Asic[59]:675 Asic[60]:675 Asic[61]:675 Asic[62]:675
driver-btm-c5.c:4809:set_frequency: Chain:6 max freq=675
driver-btm-c5.c:4810:set_frequency: Chain:6 min freq=675

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=-4
driver-btm-c5.c:4773:set_frequency: Chain:7 base freq=662
Asic[ 0]:662 Asic[ 1]:662 Asic[ 2]:662 Asic[ 3]:662 Asic[ 4]:662 Asic[ 5]:662 Asic[ 6]:662 Asic[ 7]:662
Asic[ 8]:662 Asic[ 9]:662 Asic[10]:662 Asic[11]:662 Asic[12]:662 Asic[13]:662 Asic[14]:662 Asic[15]:662
Asic[16]:662 Asic[17]:662 Asic[18]:662 Asic[19]:662 Asic[20]:662 Asic[21]:662 Asic[22]:662 Asic[23]:662
Asic[24]:662 Asic[25]:662 Asic[26]:662 Asic[27]:662 Asic[28]:662 Asic[29]:662 Asic[30]:662 Asic[31]:662
Asic[32]:662 Asic[33]:662 Asic[34]:662 Asic[35]:662 Asic[36]:662 Asic[37]:662 Asic[38]:662 Asic[39]:662
Asic[40]:662 Asic[41]:662 Asic[42]:662 Asic[43]:662 Asic[44]:662 Asic[45]:662 Asic[46]:662 Asic[47]:662
Asic[48]:662 Asic[49]:662 Asic[50]:662 Asic[51]:662 Asic[52]:662 Asic[53]:662 Asic[54]:662 Asic[55]:662
Asic[56]:662 Asic[57]:662 Asic[58]:662 Asic[59]:662 Asic[60]:662 Asic[61]:662 Asic[62]:662
driver-btm-c5.c:4809:set_frequency: Chain:7 max freq=662
driver-btm-c5.c:4810:set_frequency: Chain:7 min freq=662


driver-btm-c5.c:4819:set_frequency: Miner fix freq ...
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=675
Asic[ 0]:675 Asic[ 1]:675 Asic[ 2]:675 Asic[ 3]:675 Asic[ 4]:675 Asic[ 5]:675 Asic[ 6]:675 Asic[ 7]:675
Asic[ 8]:675 Asic[ 9]:675 Asic[10]:675 Asic[11]:675 Asic[12]:675 Asic[13]:675 Asic[14]:675 Asic[15]:675
Asic[16]:675 Asic[17]:675 Asic[18]:675 Asic[19]:675 Asic[20]:675 Asic[21]:675 Asic[22]:675 Asic[23]:675
Asic[24]:675 Asic[25]:675 Asic[26]:675 Asic[27]:675 Asic[28]:675 Asic[29]:675 Asic[30]:675 Asic[31]:675
Asic[32]:675 Asic[33]:675 Asic[34]:675 Asic[35]:675 Asic[36]:675 Asic[37]:675 Asic[38]:675 Asic[39]:675
Asic[40]:675 Asic[41]:675 Asic[42]:675 Asic[43]:675 Asic[44]:675 Asic[45]:675 Asic[46]:675 Asic[47]:675
Asic[48]:675 Asic[49]:675 Asic[50]:675 Asic[51]:675 Asic[52]:675 Asic[53]:675 Asic[54]:675 Asic[55]:675
Asic[56]:675 Asic[57]:675 Asic[58]:675 Asic[59]:675 Asic[60]:675 Asic[61]:675 Asic[62]:675
driver-btm-c5.c:5110:set_frequency: Chain:6 max freq=675
driver-btm-c5.c:5111:set_frequency: Chain:6 min freq=675

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=-4
driver-btm-c5.c:5063:set_frequency: Chain:7 base freq=662
Asic[ 0]:662 Asic[ 1]:662 Asic[ 2]:662 Asic[ 3]:662 Asic[ 4]:662 Asic[ 5]:662 Asic[ 6]:662 Asic[ 7]:662
Asic[ 8]:662 Asic[ 9]:662 Asic[10]:662 Asic[11]:662 Asic[12]:662 Asic[13]:662 Asic[14]:662 Asic[15]:662
Asic[16]:662 Asic[17]:662 Asic[18]:662 Asic[19]:662 Asic[20]:662 Asic[21]:662 Asic[22]:662 Asic[23]:662
Asic[24]:662 Asic[25]:662 Asic[26]:662 Asic[27]:662 Asic[28]:662 Asic[29]:662 Asic[30]:662 Asic[31]:662
Asic[32]:662 Asic[33]:662 Asic[34]:662 Asic[35]:662 Asic[36]:662 Asic[37]:662 Asic[38]:662 Asic[39]:662
Asic[40]:662 Asic[41]:662 Asic[42]:662 Asic[43]:662 Asic[44]:662 Asic[45]:662 Asic[46]:662 Asic[47]:662
Asic[48]:662 Asic[49]:662 Asic[50]:662 Asic[51]:662 Asic[52]:662 Asic[53]:662 Asic[54]:662 Asic[55]:662
Asic[56]:662 Asic[57]:662 Asic[58]:662 Asic[59]:662 Asic[60]:662 Asic[61]:662 Asic[62]:662
driver-btm-c5.c:5110:set_frequency: Chain:7 max freq=662
driver-btm-c5.c:5111:set_frequency: Chain:7 min freq=662

driver-btm-c5.c:5119:set_frequency: max freq = 675
driver-btm-c5.c:4162:ProcessFixFreq: totalRate = 9524, fixed_totalRate = 9500
driver-btm-c5.c:9604:init_uart_baud: set baud=1
driver-btm-c5.c:6593:calibration_sensor_offset: Chain[J7] PIC temp offset: 62,0,0,0,0,0,35,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=0x98
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:46 remote:49 offset:29
driver-btm-c5.c:6753:calibration_sensor_offset: Chain[J7] chip[244] get middle temp offset=29 typeID=55
driver-btm-c5.c:6593:calibration_sensor_offset: Chain[J8] PIC temp offset: 62,-76,0,0,0,0,33,0,0,0,0,0,0,0,0,0,0,0,
driver-btm-c5.c:6627:calibration_sensor_offset: chain[8] temp chip I2C addr=0x98
driver-btm-c5.c:6660:calibration_sensor_offset: Chain[J8] chip[244] use PIC middle temp offset=-76 typeID=1a
driver-btm-c5.c:6377:do_calibration_sensor_offset: Warning: Chain[7] chip[244] local:47 remote:123 offset:-43, will fixed offset=27
driver-btm-c5.c:6384:do_calibration_sensor_offset: New offset Chain[8] chip[244] local:47 remote:123 offset:27
driver-btm-c5.c:6753:calibration_sensor_offset: Chain[J8] chip[244] get middle temp offset=27 typeID=1a
driver-btm-c5.c:12103:set_working_voltage: setting to working voltage...
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[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[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[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[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:12083:slowly_downgrade_voltage_all_chain: chain[6] set voltage to 880
driver-btm-c5.c:12083:slowly_downgrade_voltage_all_chain: chain[7] set voltage to 880
driver-btm-c5.c:12083:slowly_downgrade_voltage_all_chain: chain[6] set voltage to 870
driver-btm-c5.c:12083:slowly_downgrade_voltage_all_chain: chain[7] set voltage to 870
driver-btm-c5.c:12083:slowly_downgrade_voltage_all_chain: chain[6] set voltage to 860
driver-btm-c5.c:13954:bitmain_c5_init: start thread for read temp
setStartTimePoint total_tv_start_sys=167 total_tv_end_sys=168
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 = 69
driver-btm-c5.c:12103:set_working_voltage: setting to working voltage...
driver-btm-c5.c:10487:check_system_work: voltage_check_done
max pcb temperature:94, fan num:2, error counter:1
max pcb temperature:99, fan num:2, error counter:2
Fatal error, turning off hash boards power...
max pcb temperature : 99, fan num : 2
driver-btm-c5.c:9037:read_temp_func: Do not clear run bit
Fatal Error: Temperature is too high!
max pcb temperature:99, fan num:2, error counter:3
Fatal error, turning off hash boards power...
max pcb temperature : 99, fan num : 2
driver-btm-c5.c:9037:read_temp_func: Do not clear run bit
Fatal Error: Temperature is too high!
do read_temp_func once...

get RT hashrate from Chain[6]: (asic index start from 1-63)

get RT hashrate from Chain[7]: (asic index start from 1-63)
Check Chain[J7] ASIC RT error: (asic index start from 1-63)
Check Chain[J8] ASIC RT error: (asic index start from 1-63)
Done check_asic_reg
read failed on Chain[6] Chip[62] middle Temp old value:109
Special fix Chain[6] Chip[62] middle Temp = 109
Done read temp on Chain[6]
read failed on Chain[7] Chip[62] middle Temp old value:114
Special fix Chain[7] Chip[62] middle Temp = 114
Done read temp on Chain[7]
Max pcb temp : 99
Read temp failed, set fixed full fan speed
FAN PWM: 100
read_temp_func Done!
CRC error counter=0

Here is the log.. this happened after electricity failure at my small farm..

I tried to search for answers here but couldn't find a proper one, some said the hashboard died, some said it's a fan issue. Help needed thank you.
Jump to: