Bitcoin Forum
May 22, 2024, 05:33:57 AM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: S17e hash board powering off, updated  (Read 63 times)
Tony2o6 (OP)
Newbie
*
Offline Offline

Activity: 4
Merit: 0


View Profile
March 09, 2021, 11:47:59 PM
Last edit: March 11, 2021, 11:26:46 PM by frodocooper
 #1

I decided to switch mining pools from f2pool to slushpool and this is when all the problems started arising. When I switched pools, the first problem was one of my hashboards started not hashing again. I thought a simple reboot would fix it, but it didnt. I rebooted a few more times and the problem was still there. I disconnected the power for a few minutes then plugged it back in and it still wouldn’t work. After doing this a few times, now one of my hashboards doesn’t show up under miner status AND one of my hashboards is not hashing as well. So two hashboards don’t work and only one works. Two show up under miner status, only one works, and one isn’t showing up.



Update:

So I was able to mess around with the cables and got two of the hash boards working, and one is still showing the message “chain 3 only find 134 asic, will power off hash board 3”. Does this mean that the last chip, 135 is bad or the heat shield is bad and needs resoldering? If so, could someone show me a map of which one is the 135th chip or heat shield that needs to be resoldered? I will be removing my hash board and bringing it to someone who knows how to solder to have it fixed so I would need a good picture to show him which one needs to be checked.

Here is the kernel code, for some reason I can’t fit the whole code in. Thank you!

Code:
Booting Linux on physical CPU 0x0
Linux version 4.6.0-xilinx-gff8137b-dirty (lzq@armdev2) (gcc version 4.8.3 20140320 (prerelease) (Sourcery CodeBench Lite 2014.05-23) ) #25 SMP PREEMPT Fri Nov 23 15:30:52 CST 2018
CPU: ARMv7 Processor [413fc090] revision 0 (ARMv7), cr=18c5387d
CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
Machine model: Xilinx Zynq
cma: Reserved 16 MiB at 0x0e000000
Memory policy: Data cache writealloc
On node 0 totalpages: 61440
free_area_init_node: node 0, pgdat c0b39280, node_mem_map cde10000
  Normal zone: 480 pages used for memmap
  Normal zone: 0 pages reserved
  Normal zone: 61440 pages, LIFO batch:15
percpu: Embedded 12 pages/cpu @cddf1000 s19776 r8192 d21184 u49152
pcpu-alloc: s19776 r8192 d21184 u49152 alloc=12*4096
pcpu-alloc: [0] 0 [0] 1
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 60960
Kernel command line: mem=240M console=ttyPS0,115200 ramdisk_size=33554432 root=/dev/ram rw earlyprintk
PID hash table entries: 1024 (order: 0, 4096 bytes)
Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
Memory: 195688K/245760K available (6345K kernel code, 231K rwdata, 1896K rodata, 1024K init, 223K bss, 33688K reserved, 16384K cma-reserved, 0K highmem)
Virtual kernel memory layout:
    vector  : 0xffff0000 - 0xffff1000   (   4 kB)
    fixmap  : 0xffc00000 - 0xfff00000   (3072 kB)
    vmalloc : 0xcf800000 - 0xff800000   ( 768 MB)
    lowmem  : 0xc0000000 - 0xcf000000   ( 240 MB)
    pkmap   : 0xbfe00000 - 0xc0000000   (   2 MB)
    modules : 0xbf000000 - 0xbfe00000   (  14 MB)
      .text : 0xc0008000 - 0xc090c424   (9234 kB)
      .init : 0xc0a00000 - 0xc0b00000   (1024 kB)
      .data : 0xc0b00000 - 0xc0b39fe0   ( 232 kB)
       .bss : 0xc0b39fe0 - 0xc0b71c28   ( 224 kB)
Preemptible hierarchical RCU implementation.
Build-time adjustment of leaf fanout to 32.
RCU restricting CPUs from NR_CPUS=4 to nr_cpu_ids=2.
RCU: Adjusting geometry for rcu_fanout_leaf=32, nr_cpu_ids=2
NR_IRQS:16 nr_irqs:16 16
efuse mapped to cf800000
ps7-slcr mapped to cf802000
L2C: platform modifies aux control register: 0x72360000 -> 0x72760000
L2C: DT/platform modifies aux control register: 0x72360000 -> 0x72760000
L2C-310 erratum 769419 enabled
L2C-310 enabling early BRESP for Cortex-A9
L2C-310 full line of zeros enabled for Cortex-A9
L2C-310 ID prefetch enabled, offset 1 lines
L2C-310 dynamic clock gating enabled, standby mode enabled
L2C-310 cache controller enabled, 8 ways, 512 kB
L2C-310: CACHE_ID 0x410000c8, AUX_CTRL 0x76760001
zynq_clock_init: clkc starts at cf802100
Zynq clock init
sched_clock: 64 bits at 333MHz, resolution 3ns, wraps every 4398046511103ns
clocksource: arm_global_timer: mask: 0xffffffffffffffff max_cycles: 0x4ce07af025, max_idle_ns: 440795209040 ns
Switching to timer-based delay loop, resolution 3ns
clocksource: ttc_clocksource: mask: 0xffff max_cycles: 0xffff, max_idle_ns: 537538477 ns
ps7-ttc #0 at cf80a000, irq=18
Console: colour dummy device 80x30
Calibrating delay loop (skipped), value calculated using timer frequency.. 666.66 BogoMIPS (lpj=3333333)
pid_max: default: 32768 minimum: 301
Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
CPU: Testing write buffer coherency: ok
CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
Setting up static identity map for 0x100000 - 0x100058
CPU1: failed to boot: -1
Brought up 1 CPUs
SMP: Total of 1 processors activated (666.66 BogoMIPS).
CPU: All CPU(s) started in SVC mode.
devtmpfs: initialized
VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4
clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
pinctrl core: initialized pinctrl subsystem
NET: Registered protocol family 16
DMA: preallocated 256 KiB pool for atomic coherent allocations
cpuidle: using governor menu
hw-breakpoint: found 5 (+1 reserved) breakpoint and 1 watchpoint registers.
hw-breakpoint: maximum watchpoint size is 4 bytes.
zynq-ocm f800c000.ps7-ocmc: ZYNQ OCM pool: 256 KiB @ 0xcf880000
vgaarb: loaded
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
media: Linux media interface: v0.10
Linux video capture interface: v2.00
pps_core: LinuxPPS API ver. 1 registered
pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
PTP clock support registered
EDAC MC: Ver: 3.0.0
Advanced Linux Sound Architecture Driver Initialized.
clocksource: Switched to clocksource arm_global_timer
NET: Registered protocol family 2
TCP established hash table entries: 2048 (order: 1, 8192 bytes)
TCP bind hash table entries: 2048 (order: 2, 16384 bytes)
TCP: Hash tables configured (established 2048 bind 2048)
UDP hash table entries: 256 (order: 1, 8192 bytes)
UDP-Lite hash table entries: 256 (order: 1, 8192 bytes)
NET: Registered protocol family 1
RPC: Registered named UNIX socket transport module.
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
PCI: CLS 0 bytes, default 64
Trying to unpack rootfs image as initramfs...
rootfs image is not initramfs (no cpio magic); looks like an initrd
Freeing initrd memory: 20648K (cc6d7000 - cdb01000)
hw perfevents: enabled with armv7_cortex_a9 PMU driver, 7 counters available
futex hash table entries: 512 (order: 3, 32768 bytes)
workingset: timestamp_bits=28 max_order=16 bucket_order=0
jffs2: version 2.2. (NAND) (SUMMARY)  � 2001-2006 Red Hat, Inc.
io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered (default)
dma-pl330 f8003000.ps7-dma: Loaded driver for PL330 DMAC-241330
dma-pl330 f8003000.ps7-dma: DBUFF-128x8bytes Num_Chans-8 Num_Peri-4 Num_Events-16
e0000000.serial: ttyPS0 at MMIO 0xe0000000 (irq = 158, base_baud = 6249999) is a xuartps
console [ttyPS0] enabled
xdevcfg f8007000.ps7-dev-cfg: ioremap 0xf8007000 to cf86e000
[drm] Initialized drm 1.1.0 20060810
brd: module loaded
loop: module loaded
CAN device driver interface
gpiod_set_value: invalid GPIO
libphy: MACB_mii_bus: probed
macb e000b000.ethernet eth0: Cadence GEM rev 0x00020118 at 0xe000b000 irq 31 (00:0a:35:00:00:00)
Generic PHY e000b000.etherne:00: attached PHY driver [Generic PHY] (mii_bus:phy_addr=e000b000.etherne:00, irq=-1)
e1000e: Intel(R) PRO/1000 Network Driver - 3.2.6-k
e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
ehci-pci: EHCI PCI platform driver
usbcore: registered new interface driver usb-storage
mousedev: PS/2 mouse device common for all mice
i2c /dev entries driver
Xilinx Zynq CpuIdle Driver started
sdhci: Secure Digital Host Controller Interface driver
sdhci: Copyright(c) Pierre Ossman
sdhci-pltfm: SDHCI platform and OF driver helper
mmc0: SDHCI controller on e0100000.ps7-sdio [e0100000.ps7-sdio] using ADMA
ledtrig-cpu: registered to indicate activity on CPUs
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
nand: device found, Manufacturer ID: 0x2c, Chip ID: 0xda
nand: Micron MT29F2G08ABAGAWP
nand: 256 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 128
nand: WARNING: pl35x-nand: the ECC used on your system is too weak compared to the one required by the NAND chip
Bad block table found at page 131008, version 0x01
Bad block table found at page 130944, version 0x01
6 ofpart partitions found on MTD device pl35x-nand
Creating 6 MTD partitions on "pl35x-nand":
0x000000000000-0x000002800000 : "BOOT.bin-env-dts-kernel"
0x000002800000-0x000004800000 : "ramfs"
0x000004800000-0x000005000000 : "configs"
0x000005000000-0x000006000000 : "reserve"
0x000006000000-0x000008000000 : "ramfs-bak"
0x000008000000-0x000010000000 : "reserve1"
NET: Registered protocol family 10
sit: IPv6 over IPv4 tunneling driver
NET: Registered protocol family 17
can: controller area network core (rev 20120528 abi 9)
NET: Registered protocol family 29
can: raw protocol (rev 20120528)
can: broadcast manager protocol (rev 20120528 t)
can: netlink gateway (rev 20130117) max_hops=1
zynq_pm_ioremap: no compatible node found for 'xlnx,zynq-ddrc-a05'
zynq_pm_late_init: Unable to map DDRC IO memory.
Registering SWP/SWPB emulation handler
hctosys: unable to open rtc device (rtc0)
ALSA device list:
  No soundcards found.
RAMDISK: gzip image found at block 0
EXT4-fs (ram0): couldn't mount as ext3 due to feature incompatibilities
EXT4-fs (ram0): mounted filesystem without journal. Opts: (null)
VFS: Mounted root (ext4 filesystem) on device 1:0.
devtmpfs: mounted
Freeing unused kernel memory: 1024K (c0a00000 - c0b00000)
EXT4-fs (ram0): re-mounted. Opts: block_validity,delalloc,barrier,user_xattr
random: dd urandom read with 0 bits of entropy available
ubi0: attaching mtd2
ubi0: scanning is finished
ubi0: attached mtd2 (name "configs", size 8 MiB)
ubi0: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
ubi0: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
ubi0: VID header offset: 2048 (aligned 2048), data offset: 4096
ubi0: good PEBs: 64, bad PEBs: 0, corrupted PEBs: 0
ubi0: user volume: 1, internal volumes: 1, max. volumes count: 128
ubi0: max/mean erase counter: 28/11, WL threshold: 4096, image sequence number: 2636279313
ubi0: available PEBs: 0, total reserved PEBs: 64, PEBs reserved for bad PEB handling: 40
ubi0: background thread "ubi_bgt0d" started, PID 708
UBIFS (ubi0:0): background thread "ubifs_bgt0_0" started, PID 711
UBIFS (ubi0:0): UBIFS: mounted UBI device 0, volume 0, name "configs"
UBIFS (ubi0:0): LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
UBIFS (ubi0:0): FS size: 1396736 bytes (1 MiB, 11 LEBs), journal size 888833 bytes (0 MiB, 5 LEBs)
UBIFS (ubi0:0): reserved for root: 65970 bytes (64 KiB)
UBIFS (ubi0:0): media format: w4/r0 (latest is w4/r0), UUID A5E2E817-94FA-4998-90AB-D2C873A8EBA9, small LPT model
ubi1: attaching mtd5
ubi1: scanning is finished
ubi1: attached mtd5 (name "reserve1", size 128 MiB)
ubi1: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
ubi1: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
ubi1: VID header offset: 2048 (aligned 2048), data offset: 4096
ubi1: good PEBs: 1020, bad PEBs: 4, corrupted PEBs: 0
ubi1: user volume: 1, internal volumes: 1, max. volumes count: 128
ubi1: max/mean erase counter: 8314/6097, WL threshold: 4096, image sequence number: 614900815
ubi1: available PEBs: 0, total reserved PEBs: 1020, PEBs reserved for bad PEB handling: 36
ubi1: background thread "ubi_bgt1d" started, PID 720
UBIFS (ubi1:0): background thread "ubifs_bgt1_0" started, PID 723
UBIFS (ubi1:0): UBIFS: mounted UBI device 1, volume 0, name "reserve1"
UBIFS (ubi1:0): LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
UBIFS (ubi1:0): FS size: 123039744 bytes (117 MiB, 969 LEBs), journal size 6221824 bytes (5 MiB, 49 LEBs)
UBIFS (ubi1:0): reserved for root: 4952683 bytes (4836 KiB)
UBIFS (ubi1:0): media format: w4/r0 (latest is w4/r0), UUID 91DF6B3D-1A99-4241-87C7-EB25097110C1, small LPT model
IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
macb e000b000.ethernet eth0: unable to generate target frequency: 25000000 Hz
macb e000b000.ethernet eth0: link up (100/Full)
IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
In axi fpga driver!
request_mem_region OK!
AXI fpga dev virtual address is 0xcfb54000
*base_vir_addr = 0xb023
In fpga mem driver!
request_mem_region OK!
fpga mem virtual address is 0xd2000000
2021-03-10 04:34:06:thread.c:1555:create_bitmain_soc_init_thread: create thread
2021-03-10 04:34:06:driver-btm-api.c:682:init_freq_mode: This is scan-user version
2021-03-10 04:34:06:driver-btm-api.c:2518:bitmain_soc_init: Miner compile time: Fri Jan  8 22:31:06 CST 2021 type: Antminer S17e
2021-03-10 04:34:06:driver-btm-api.c:2519:bitmain_soc_init: commit version: 37668c9 2021-01-08 18:20:11, build by: jenkins 2021-01-08 22:35:52
2021-03-10 04:34:06:driver-btm-api.c:2520:bitmain_soc_init: opt_multi_version     = 1
2021-03-10 04:34:06:driver-btm-api.c:2521:bitmain_soc_init: opt_bitmain_ab        = 1
2021-03-10 04:34:06:driver-btm-api.c:2522:bitmain_soc_init: mid_auto_gen          = 0
2021-03-10 04:34:06:driver-btm-api.c:2523:bitmain_soc_init: work_mode             = 0
2021-03-10 04:34:06:driver-btm-api.c:2524:bitmain_soc_init: power_feedback_en     = true
2021-03-10 04:34:06:driver-btm-api.c:2067:show_sn: no SN got, please write SN to /config/sn
2021-03-10 04:34:06:driver-btm-api.c:1384:miner_device_init: Detect 256MB control board of XILINX
2021-03-10 04:34:06:driver-btm-api.c:1325:init_fan_parameter: fan_eft : 0  fan_pwm : 0
2021-03-10 04:34:12:driver-btm-api.c:1309:init_miner_version: miner ID : 8004cc481540885c
2021-03-10 04:34:12:driver-btm-api.c:1315:init_miner_version: FPGA Version = 0xB023
2021-03-10 04:34:17:auto_adapt.c:100:_get_board_info: chain[1] board bin: 1, chip bin: 1, chip ft: A4V4, chip version: AB
2021-03-10 04:34:17:auto_adapt.c:100:_get_board_info: chain[2] board bin: 1, chip bin: 1, chip ft: A4V4, chip version: AB
2021-03-10 04:34:17:auto_adapt.c:100:_get_board_info: chain[3] board bin: 1, chip bin: 1, chip ft: A4V4, chip version: AB
2021-03-10 04:34:17:driver-btm-api.c:2164:get_calibration_voltage: calibration voltage flag is error data.
2021-03-10 04:34:17 voltage[1] = 1850
2021-03-10 04:34:17 voltage[2] = 1850
2021-03-10 04:34:17 voltage[3] = 1850
2021-03-10 04:34:17:auto_adapt.c:273:is_sweep_failed_before: open sweep tag failed
voltage_ref = 1850
2100  2100  2100  2100  2100  2100  
2100  2100  2100  2100  2100  2100  
2100  2100  2100  2100  2090  2050  
2100  2090  2080  2060  2030  1960  
2080  2060  2030  2010  1960  1910  

2021-03-10 04:34:17:thread.c:1523:create_read_nonce_reg_thread: create thread
2021-03-10 04:34:17:driver-btm-api.c:698:dump_pcb_bom_version: Chain [1] PCB Version: 0x0128
2021-03-10 04:34:17:driver-btm-api.c:699:dump_pcb_bom_version: Chain [1] BOM Version: 0x0100
2021-03-10 04:34:17:driver-btm-api.c:698:dump_pcb_bom_version: Chain [2] PCB Version: 0x0128
2021-03-10 04:34:17:driver-btm-api.c:699:dump_pcb_bom_version: Chain [2] BOM Version: 0x0100
2021-03-10 04:34:17:driver-btm-api.c:698:dump_pcb_bom_version: Chain [3] PCB Version: 0x0128
2021-03-10 04:34:17:driver-btm-api.c:699:dump_pcb_bom_version: Chain [3] BOM Version: 0x0100
2021-03-10 04:34:24:driver-btm-api.c:2344:bitmain_board_init: Fan check passed.
2021-03-10 04:34:25:board.c:81:jump_and_app_check_restore_pic: chain[1] PIC jump to app
2021-03-10 04:34:27:board.c:94:jump_and_app_check_restore_pic: Check chain[1] PIC fw version=0xb9
2021-03-10 04:34:28:board.c:81:jump_and_app_check_restore_pic: chain[2] PIC jump to app
2021-03-10 04:34:30:board.c:94:jump_and_app_check_restore_pic: Check chain[2] PIC fw version=0xb9
2021-03-10 04:34:31:board.c:81:jump_and_app_check_restore_pic: chain[3] PIC jump to app
2021-03-10 04:34:33:board.c:94:jump_and_app_check_restore_pic: Check chain[3] PIC fw version=0xb9
2021-03-10 04:34:33:thread.c:1518:create_pic_heart_beat_thread: create thread
2021-03-10 04:34:35:power_api.c:241:power_init: power type version: 0x0042
2021-03-10 04:34:36:power_api.c:259:power_init: Power init:
2021-03-10 04:34:36:power_api.c:260:power_init: current_voltage_raw     = 2002
2021-03-10 04:34:36:power_api.c:261:power_init: highest_voltage_raw     = 2000
2021-03-10 04:34:36:power_api.c:262:power_init: working_voltage_raw     = 1800
2021-03-10 04:34:36:power_api.c:263:power_init: higher_voltage_raw      = 1850
2021-03-10 04:34:36:power_api.c:264:power_init: check_asic_voltage_raw  = 1800
2021-03-10 04:34:36:driver-btm-api.c:2354:bitmain_board_init: Enter 60s sleep to make sure power release finish.
2021-03-10 04:35:38:driver-btm-api.c:1123:check_asic_number_until_volt_balance: THIS is No.1 time boost asic:
2021-03-10 04:35:38:power_api.c:334:modify_check_asic_voltage: check_asic_voltage_raw  = 1800
2021-03-10 04:35:41:power_api.c:298:set_to_check_asic_voltage_by_steps: Set to voltage raw 1800, step by step.
2021-03-10 04:36:04:uart.c:69:set_baud: set UART baud to 115200
chain 1, IO_DRIVE_STRENGTH_CONFIGURATION reg = 0x 7777777
2021-03-10 04:36:09:driver-btm-api.c:1035:check_asic_number_with_power_on: Chain[1]: find 135 asic, times 0
chain 2, IO_DRIVE_STRENGTH_CONFIGURATION reg = 0x 7777777
2021-03-10 04:36:13:driver-btm-api.c:1035:check_asic_number_with_power_on: Chain[2]: find 135 asic, times 0
chain 3, IO_DRIVE_STRENGTH_CONFIGURATION reg = 0x 7777777
2021-03-10 04:36:17:driver-btm-api.c:1035:check_asic_number_with_power_on: Chain[3]: find 134 asic, times 0
2021-03-10 04:36:19:board.c:81:jump_and_app_check_restore_pic: chain[3] PIC jump to app
2021-03-10 04:36:21:board.c:94:jump_and_app_check_restore_pic: Check chain[3] PIC fw version=0xb9
chain 3, IO_DRIVE_STRENGTH_CONFIGURATION reg = 0x 7777777
2021-03-10 04:36:25:driver-btm-api.c:1035:check_asic_number_with_power_on: Chain[3]: find 134 asic, times 1
2021-03-10 04:36:26:board.c:81:jump_and_app_check_restore_pic: chain[3] PIC jump to app
2021-03-10 04:36:28:board.c:94:jump_and_app_check_restore_pic: Check chain[3] PIC fw version=0xb9
chain 3, IO_DRIVE_STRENGTH_CONFIGURATION reg = 0x 7777777
2021-03-10 04:36:32:driver-btm-api.c:1035:check_asic_number_with_power_on: Chain[3]: find 134 asic, times 2
2021-03-10 04:36:33:board.c:81:jump_and_app_check_restore_pic: chain[3] PIC jump to app
2021-03-10 04:36:35:board.c:94:jump_and_app_check_restore_pic: Check chain[3] PIC fw version=0xb9
chain 3, IO_DRIVE_STRENGTH_CONFIGURATION reg = 0x 7777777
2021-03-10 04:36:39:driver-btm-api.c:1035:check_asic_number_with_power_on: Chain[3]: find 134 asic, times 3
2021-03-10 04:36:41:board.c:81:jump_and_app_check_restore_pic: chain[3] PIC jump to app
2021-03-10 04:36:43:board.c:94:jump_and_app_check_restore_pic: Check chain[3] PIC fw version=0xb9
2021-03-10 04:36:43:driver-btm-api.c:1217:check_asic_number: Chain 3 only find 134 asic, will power off hash board 3
2021-03-10 04:36:44:driver-btm-api.c:1163:check_asic_number_until_volt_balance: PASS: volt balance at No.1 time boost asic.
2021-03-10 04:36:44:power_api.c:364:set_to_highest_voltage_by_steps: Set to voltage raw 2000, step by step.
2021-03-10 04:37:19:driver-hash-chip.c:876:set_uart_relay: set uart relay to 0x390003
2021-03-10 04:37:19:driver-hash-chip.c:1264:set_ldo_ctrl: Set LDO to 0x2000203
2021-03-10 04:37:20:driver-hash-chip.c:737:dump_adc_voltage_v2: get ADC_DATAOUT from chain 1 with 0 regs timeout.
chain 1 domain  0:   d0 0.334,   d1 0.331,   d2 0.330,   d3 0.334,   sum = 1.329590
chain 1 domain  1:   d0 0.338,   d1 0.336,   d2 0.335,   d3 0.334,   sum = 1.342977
chain 1 domain  2:   d0 0.321,   d1 0.324,   d2 0.325,   d3 0.330,   sum = 1.299601
chain 1 domain  3:   d0 0.339,   d1 0.333,   d2 0.333,   d3 0.338,   sum = 1.343302
chain 1 domain  4:   d0 0.333,   d1 0.333,   d2 0.331,   d3 0.333,   sum = 1.330241
chain 1 domain  5:   d0 0.341,   d1 0.337,   d2 0.337,   d3 0.335,   sum = 1.349162
chain 1 domain  6:   d0 0.331,   d1 0.328,   d2 0.327,   d3 0.330,   sum = 1.314941
chain 1 domain  7:   d0 0.337,   d1 0.335,   d2 0.334,   d3 0.336,   sum = 1.341675
chain 1 domain  8:   d0 0.321,   d1 0.318,   d2 0.320,   d3 0.319,   sum = 1.277506
chain 1 domain  9:   d0 0.326,   d1 0.323,   d2 0.326,   d3 0.323,   sum = 1.299072
chain 1 domain 10:   d0 0.324,   d1 0.326,   d2 0.330,   d3 0.331,   sum = 1.311157
chain 1 domain 11:   d0 0.324,   d1 0.319,   d2 0.317,   d3 0.318,   sum = 1.278076
chain 1 domain 12:   d0 0.329,   d1 0.330,   d2 0.329,   d3 0.326,   sum = 1.313517
chain 1 domain 13:   d0 0.330,   d1 0.330,   d2 0.330,   d3 0.335,   sum = 1.324178
chain 1 domain 14:   d0 0.324,   d1 0.321,   d2 0.321,   d3 0.325,   sum = 1.290487
2021-03-10 04:37:20:driver-hash-chip.c:737:dump_adc_voltage_v2: get ADC_DATAOUT from chain 2 with 0 regs timeout.
chain 2 domain  0:   d0 0.349,   d1 0.335,   d2 0.346,   d3 0.335,   sum = 1.366048
chain 2 domain  1:   d0 0.351,   d1 0.346,   d2 0.346,   d3 0.344,   sum = 1.386719
chain 2 domain  2:   d0 0.332,   d1 0.333,   d2 0.332,   d3 0.336,   sum = 1.332479
chain 2 domain  3:   d0 0.324,   d1 0.319,   d2 0.317,   d3 0.315,   sum = 1.275024
chain 2 domain  4:   d0 0.327,   d1 0.327,   d2 0.325,   d3 0.327,   sum = 1.305379
chain 2 domain  5:   d0 0.328,   d1 0.323,   d2 0.323,   d3 0.321,   sum = 1.295085
chain 2 domain  6:   d0 0.329,   d1 0.328,   d2 0.329,   d3 0.331,   sum = 1.316813
chain 2 domain  7:   d0 0.328,   d1 0.326,   d2 0.326,   d3 0.326,   sum = 1.306315
chain 2 domain  8:   d0 0.318,   d1 0.316,   d2 0.317,   d3 0.315,   sum = 1.266724
chain 2 domain  9:   d0 0.331,   d1 0.333,   d2 0.334,   d3 0.331,   sum = 1.328857
chain 2 domain 10:   d0 0.323,   d1 0.325,   d2 0.326,   d3 0.323,   sum = 1.296427
chain 2 domain 11:   d0 0.328,   d1 0.328,   d2 0.327,   d3 0.328,   sum = 1.310872
chain 2 domain 12:   d0 0.335,   d1 0.336,   d2 0.335,   d3 0.335,   sum = 1.341471
chain 2 domain 13:   d0 0.328,   d1 0.322,   d2 0.324,   d3 0.329,   sum = 1.302328
chain 2 domain 14:   d0 0.327,   d1 0.323,   d2 0.325,   d3 0.329,   sum = 1.304118
2021-03-10 04:37:20:driver-hash-chip.c:493:check_adc_voltage: PASS domainn volt check: request 0.800 (index 0, open_core)
2021-03-10 04:37:22:temperature.c:272:calibrate_temp_sensor_one_chain: chain 1 temp sensor NCT218
2021-03-10 04:37:23:temperature.c:272:calibrate_temp_sensor_one_chain: chain 2 temp sensor NCT218
2021-03-10 04:37:29:driver-btm-api.c:311:check_bringup_temp: Bring up temperature is 31
2021-03-10 04:37:29:uart.c:69:set_baud: set UART baud to 6000000
2021-03-10 04:37:29 voltage[1] = 1850
2021-03-10 04:37:29 voltage[2] = 1850
2021-03-10 04:37:29:power_api.c:272:set_working_voltage_raw: working_voltage_raw = 1850
2021-03-10 04:37:29:thread.c:1538:create_check_miner_status_thread: create thread
2021-03-10 04:37:29:thread.c:1528:create_show_miner_status_thread: create thread
2021-03-10 04:37:29:thread.c:1503:create_temperature_monitor_thread: create thread
2021-03-10 04:37:29:thread.c:1580:create_fan_monitor_thread: create thread
2021-03-10 04:37:29:frequency.c:578:inc_freq_with_fixed_vco: chain = 255, freq = 380, is_higher_voltage = true
2021-03-10 04:37:35:frequency.c:623:inc_freq_with_fixed_vco: get pcb 32 ~ 33, chip_temp 36 ~ 40, now 6.0s, target 40.0
2021-03-10 04:37:36:frequency.c:623:inc_freq_with_fixed_vco: get pcb 32 ~ 34, chip_temp 36 ~ 40, now 7.0s, target 40.2
2021-03-10 04:37:37:frequency.c:623:inc_freq_with_fixed_vco: get pcb 32 ~ 34, chip_temp 36 ~ 40, now 8.0s, target 40.3
2021-03-10 04:37:38:frequency.c:623:inc_freq_with_fixed_vco: get pcb 32 ~ 33, chip_temp 36 ~ 40, now 9.0s, target 40.5
2021-03-10 04:37:39:frequency.c:623:inc_freq_with_fixed_vco: get pcb 32 ~ 34, chip_temp 36 ~ 41, now 10.0s, target 40.7
2021-03-10 04:37:39:frequency.c:644:inc_freq_with_fixed_vco: heat speed too fast! current_temp 41 > 40.7 target_temp.
2021-03-10 04:37:45:frequency.c:623:inc_freq_with_fixed_vco: get pcb 32 ~ 35, chip_temp 37 ~ 42, now 16.0s, target 41.7
2021-03-10 04:37:45:frequency.c:644:inc_freq_with_fixed_vco: heat speed too fast! current_temp 42 > 41.7 target_temp.
2021-03-10 04:37:51:frequency.c:623:inc_freq_with_fixed_vco: get pcb 33 ~ 36, chip_temp 37 ~ 44, now 22.0s, target 42.7
2021-03-10 04:37:51:frequency.c:644:inc_freq_with_fixed_vco: heat speed too fast! current_temp 44 > 42.7 target_temp.
2021-03-10 04:37:57:frequency.c:623:inc_freq_with_fixed_vco: get pcb 34 ~ 36, chip_temp 38 ~ 45, now 28.0s, target 43.7
2021-03-10 04:37:57:frequency.c:644:inc_freq_with_fixed_vco: heat speed too fast! current_temp 45 > 43.7 target_temp.
2021-03-10 04:38:03:frequency.c:623:inc_freq_with_fixed_vco: get pcb 34 ~ 37, chip_temp 39 ~ 45, now 34.0s, target 44.7
2021-03-10 04:38:03:frequency.c:644:inc_freq_with_fixed_vco: heat speed too fast! current_temp 45 > 44.7 target_temp.
2021-03-10 04:38:09:frequency.c:623:inc_freq_with_fixed_vco: get pcb 35 ~ 38, chip_temp 39 ~ 47, now 40.0s, target 45.7
2021-03-10 04:38:09:frequency.c:644:inc_freq_with_fixed_vco: heat speed too fast! current_temp 47 > 45.7 target_temp.
2021-03-10 04:38:15:frequency.c:623:inc_freq_with_fixed_vco: get pcb 35 ~ 38, chip_temp 40 ~ 47, now 46.0s, target 46.7
2021-03-10 04:38:15:frequency.c:644:inc_freq_with_fixed_vco: heat speed too fast! current_temp 47 > 46.7 target_temp.
2021-03-10 04:38:21:frequency.c:623:inc_freq_with_fixed_vco: get pcb 36 ~ 39, chip_temp 41 ~ 47, now 52.0s, target 47.7
2021-03-10 04:38:22:frequency.c:623:inc_freq_with_fixed_vco: get pcb 36 ~ 40, chip_temp 41 ~ 47, now 53.0s, target 47.8
2021-03-10 04:38:23:frequency.c:623:inc_freq_with_fixed_vco: get pcb 36 ~ 39, chip_temp 41 ~ 48, now 54.0s, target 48.0
2021-03-10 04:38:24:frequency.c:623:inc_freq_with_fixed_vco: get pcb 36 ~ 40, chip_temp 41 ~ 48, now 55.0s, target 48.2
2021-03-10 04:38:25:frequency.c:623:inc_freq_with_fixed_vco: get pcb 37 ~ 39, chip_temp 41 ~ 47, now 56.0s, target 48.3
2021-03-10 04:38:26:frequency.c:623:inc_freq_with_fixed_vco: get pcb 36 ~ 39, chip_temp 41 ~ 48, now 57.0s, target 48.5
2021-03-10 04:38:27:frequency.c:623:inc_freq_with_fixed_vco: get pcb 36 ~ 39, chip_temp 41 ~ 48, now 58.0s, target 48.7
2021-03-10 04:38:28:frequency.c:623:inc_freq_with_fixed_vco: get pcb 36 ~ 40, chip_temp 41 ~ 48, now 59.0s, target 48.8
2021-03-10 04:38:29:frequency.c:623:inc_freq_with_fixed_vco: get pcb 37 ~ 40, chip_temp 42 ~ 49, now 60.0s, target 49.0
2021-03-10 04:38:30:frequency.c:623:inc_freq_with_fixed_vco: get pcb 37 ~ 40, chip_temp 42 ~ 49, now 61.0s, target 49.2
2021-03-10 04:38:31:frequency.c:623:inc_freq_with_fixed_vco: get pcb 38 ~ 40, chip_temp 42 ~ 49, now 62.0s, target 49.3
2021-03-10 04:38:32:frequency.c:623:inc_freq_with_fixed_vco: get pcb 37 ~ 40, chip_temp 42 ~ 49, now 63.0s, target 49.5
2021-03-10 04:38:33:frequency.c:623:inc_freq_with_fixed_vco: get pcb 37 ~ 40, chip_temp 42 ~ 48, now 64.0s, target 49.7
2021-03-10 04:38:34:frequency.c:623:inc_freq_with_fixed_vco: get pcb 37 ~ 40, chip_temp 42 ~ 48, now 65.0s, target 49.8
2021-03-10 04:38:35:frequency.c:623:inc_freq_with_fixed_vco: get pcb 37 ~ 40, chip_temp 43 ~ 49, now 66.1s, target 50.0
2021-03-10 04:38:36:frequency.c:623:inc_freq_with_fixed_vco: get pcb 37 ~ 40, chip_temp 42 ~ 49, now 67.1s, target 50.2
2021-03-10 04:38:37:frequency.c:623:inc_freq_with_fixed_vco: get pcb 38 ~ 40, chip_temp 43 ~ 50, now 68.1s, target 50.4
2021-03-10 04:38:38:frequency.c:623:inc_freq_with_fixed_vco: get pcb 38 ~ 41, chip_temp 43 ~ 50, now 69.1s, target 50.5
2021-03-10 04:38:39:frequency.c:623:inc_freq_with_fixed_vco: get pcb 38 ~ 41, chip_temp 43 ~ 50, now 70.1s, target 50.7
2021-03-10 04:38:40:frequency.c:623:inc_freq_with_fixed_vco: get pcb 38 ~ 41, chip_temp 43 ~ 49, now 71.1s, target 50.9
2021-03-10 04:38:41:frequency.c:623:inc_freq_with_fixed_vco: get pcb 38 ~ 41, chip_temp 43 ~ 50, now 72.1s, target 51.0
2021-03-10 04:38:42:frequency.c:623:inc_freq_with_fixed_vco: get pcb 38 ~ 41, chip_temp 43 ~ 50, now 73.1s, target 51.2
2021-03-10 04:38:43:frequency.c:623:inc_freq_with_fixed_vco: get pcb 38 ~ 41, chip_temp 43 ~ 50, now 74.1s, target 51.4
2021-03-10 04:38:44:frequency.c:623:inc_freq_with_fixed_vco: get pcb 38 ~ 41, chip_temp 43 ~ 50, now 75.1s, target 51.5
2021-03-10 04:38:45:frequency.c:623:inc_freq_with_fixed_vco: get pcb 38 ~ 42, chip_temp 44 ~ 49, now 76.1s, target 51.7
2021-03-10 04:38:45:frequency.c:657:inc_freq_with_fixed_vco: [0] _POSTDIV1 = 7, _POSTDIV2 = 7, USER_DIV = 1, freq = 61
2021-03-10 04:38:45:frequency.c:665:inc_freq_with_fixed_vco: set to 61M, get pcb 38 ~ 42, chip_temp 44 ~ 49
2021-03-10 04:38:45:power_api.c:376:set_to_voltage_by_steps: Set to voltage raw 2100, step by step.
2021-03-10 04:39:00:frequency.c:671:inc_freq_with_fixed_vco: freq_mode 1=1 FREQ_MODE_USER, Conf.Check_Clock_Cnt=0
2021-03-10 04:39:00:driver-btm-api.c:1941:check_clock_counter_domain_last_core: freq 61 clock_counter_limit 6, no check, skip.
2021-03-10 04:39:08:frequency.c:623:inc_freq_with_fixed_vco: get pcb 40 ~ 44, chip_temp 47 ~ 53, now 99.0s, target 55.5
2021-03-10 04:39:08:frequency.c:657:inc_freq_with_fixed_vco: [1] _POSTDIV1 = 7, _POSTDIV2 = 6, USER_DIV = 1, freq = 72
2021-03-10 04:39:08:frequency.c:665:inc_freq_with_fixed_vco: set to 72M, get pcb 40 ~ 44, chip_temp 47 ~ 53
2021-03-10 04:39:08:frequency.c:671:inc_freq_with_fixed_vco: freq_mode 1=1 FREQ_MODE_USER, Conf.Check_Clock_Cnt=0
2021-03-10 04:39:08:driver-btm-api.c:1941:check_clock_counter_domain_last_core: freq 72 clock_counter_limit 8, no check, skip.
2021-03-10 04:39:16:frequency.c:623:inc_freq_with_fixed_vco: get pcb 40 ~ 46, chip_temp 48 ~ 54, now 107.0s, target 56.8
2021-03-10 04:39:16:frequency.c:657:inc_freq_with_fixed_vco: [2] _POSTDIV1 = 6, _POSTDIV2 = 6, USER_DIV = 1, freq = 84
2021-03-10 04:39:16:frequency.c:665:inc_freq_with_fixed_vco: set to 84M, get pcb 40 ~ 46, chip_temp 48 ~ 54
2021-03-10 04:39:16:frequency.c:671:inc_freq_with_fixed_vco: freq_mode 1=1 FREQ_MODE_USER, Conf.Check_Clock_Cnt=0
2021-03-10 04:39:16:driver-btm-api.c:1941:check_clock_counter_domain_last_core: freq 84 clock_counter_limit 10, no check, skip.
2021-03-10 04:39:24:frequency.c:623:inc_freq_with_fixed_vco: get pcb 41 ~ 47, chip_temp 49 ~ 56, now 115.0s, target 58.2
2021-03-10 04:39:24:frequency.c:657:inc_freq_with_fixed_vco: [3] _POSTDIV1 = 7, _POSTDIV2 = 5, USER_DIV = 1, freq = 86
2021-03-10 04:39:24:frequency.c:665:inc_freq_with_fixed_vco: set to 86M, get pcb 41 ~ 47, chip_temp 49 ~ 56
2021-03-10 04:39:24:frequency.c:671:inc_freq_with_fixed_vco: freq_mode 1=1 FREQ_MODE_USER, Conf.Check_Clock_Cnt=0
2021-03-10 04:39:24:driver-btm-api.c:1941:check_clock_counter_domain_last_core: freq 86 clock_counter_limit 10, no check, skip.
2021-03-10 04:39:32:frequency.c:623:inc_freq_with_fixed_vco: get pcb 41 ~ 48, chip_temp 50 ~ 57, now 123.0s, target 59.5
2021-03-10 04:39:32:frequency.c:657:inc_freq_with_fixed_vco: [4] _POSTDIV1 = 6, _POSTDIV2 = 5, USER_DIV = 1, freq = 101
2021-03-10 04:39:32:frequency.c:665:inc_freq_with_fixed_vco: set to 101M, get pcb 41 ~ 48, chip_temp 50 ~ 57
2021-03-10 04:39:32:frequency.c:671:inc_freq_with_fixed_vco: freq_mode 1=1 FREQ_MODE_USER, Conf.Check_Clock_Cnt=0
2021-03-10 04:39:32:driver-btm-api.c:1941:check_clock_counter_domain_last_core: freq 101 clock_counter_limit 13, no check, skip.
2021-03-10 04:39:40:frequency.c:623:inc_freq_with_fixed_vco: get pcb 42 ~ 49, chip_temp 52 ~ 59, now 131.0s, target 60.8
2021-03-10 04:39:41:frequency.c:623:inc_freq_with_fixed_vco: get pcb 41 ~ 50, chip_temp 52 ~ 59, now 132.0s, target 61.0
2021-03-10 04:39:41:frequency.c:657:inc_freq_with_fixed_vco: [5] _POSTDIV1 = 7, _POSTDIV2 = 4, USER_DIV = 1, freq = 108
2021-03-10 04:39:41:frequency.c:665:inc_freq_with_fixed_vco: set to 108M, get pcb 41 ~ 50, chip_temp 52 ~ 59
2021-03-10 04:39:41:frequency.c:671:inc_freq_with_fixed_vco: freq_mode 1=1 FREQ_MODE_USER, Conf.Check_Clock_Cnt=0
2021-03-10 04:39:41:driver-btm-api.c:1941:check_clock_counter_domain_last_core: freq 108 clock_counter_limit 14, no check, skip.
2021-03-10 04:39:49:frequency.c:623:inc_freq_with_fixed_vco: get pcb 42 ~ 51, chip_temp 53 ~ 61, now 140.1s, target 62.3
2021-03-10 04:39:50:frequency.c:623:inc_freq_with_fixed_vco: get pcb 42 ~ 51, chip_temp 53 ~ 61, now 141.1s, target 62.5
2021-03-10 04:39:51:frequency.c:623:inc_freq_with_fixed_vco: get pcb 42 ~ 51, chip_temp 54 ~ 61, now 142.1s, target 62.7
2021-03-10 04:39:52:frequency.c:623:inc_freq_with_fixed_vco: get pcb 42 ~ 52, chip_temp 54 ~ 61, now 143.1s, target 62.8
2021-03-10 04:39:53:frequency.c:623:inc_freq_with_fixed_vco: get pcb 43 ~ 52, chip_temp 54 ~ 61, now 144.1s, target 63.0
2021-03-10 04:39:53:frequency.c:657:inc_freq_with_fixed_vco: [6] _POSTDIV1 = 5, _POSTDIV2 = 5, USER_DIV = 1, freq = 121
2021-03-10 04:39:53:frequency.c:665:inc_freq_with_fixed_vco: set to 121M, get pcb 43 ~ 52, chip_temp 54 ~ 61
2021-03-10 04:39:53:frequency.c:671:inc_freq_with_fixed_vco: freq_mode 1=1 FREQ_MODE_USER, Conf.Check_Clock_Cnt=0
2021-03-10 04:39:53:driver-btm-api.c:1941:check_clock_counter_domain_last_core: freq 121 clock_counter_limit 16, no check, skip.
2021-03-10 04:40:01:frequency.c:623:inc_freq_with_fixed_vco: get pcb 43 ~ 54, chip_temp 56 ~ 63, now 152.1s, target 64.3
2021-03-10 04:40:02:frequency.c:623:inc_freq_with_fixed_vco: get pcb 43 ~ 54, chip_temp 57 ~ 64, now 153.1s, target 64.5
2021-03-10 04:40:03:frequency.c:623:inc_freq_with_fixed_vco: get pcb 43 ~ 55, chip_temp 56 ~ 64, now 154.1s, target 64.7
2021-03-10 04:40:04:frequency.c:623:inc_freq_with_fixed_vco: get pcb 43 ~ 55, chip_temp 56 ~ 64, now 155.1s, target 64.8
2021-03-10 04:40:05:frequency.c:623:inc_freq_with_fixed_vco: get pcb 43 ~ 55, chip_temp 56 ~ 64, now 156.1s, target 65.0
2021-03-10 04:40:06:frequency.c:623:inc_freq_with_fixed_vco: get pcb 43 ~ 54, chip_temp 56 ~ 64, now 157.1s, target 65.2
2021-03-10 04:40:07:frequency.c:623:inc_freq_with_fixed_vco: get pcb 43 ~ 55, chip_temp 56 ~ 65, now 158.1s, target 65.3
2021-03-10 04:40:08:frequency.c:623:inc_freq_with_fixed_vco: get pcb 43 ~ 55, chip_temp 56 ~ 65, now 159.1s, target 65.5
2021-03-10 04:40:09:frequency.c:623:inc_freq_with_fixed_vco: get pcb 44 ~ 55, chip_temp 56 ~ 65, now 160.1s, target 65.7
2021-03-10 04:40:10:frequency.c:623:inc_freq_with_fixed_vco: get pcb 42 ~ 56, chip_temp 55 ~ 65, now 161.1s, target 65.8
2021-03-10 04:40:11:frequency.c:623:inc_freq_with_fixed_vco: get pcb 43 ~ 55, chip_temp 56 ~ 66, now 162.1s, target 66.0
2021-03-10 04:40:12:frequency.c:623:inc_freq_with_fixed_vco: get pcb 43 ~ 56, chip_temp 56 ~ 65, now 163.1s, target 66.2
2021-03-10 04:40:13:frequency.c:623:inc_freq_with_fixed_vco: get pcb 43 ~ 56, chip_temp 56 ~ 65, now 164.1s, target 66.3
2021-03-10 04:40:14:frequency.c:623:inc_freq_with_fixed_vco: get pcb 42 ~ 56, chip_temp 55 ~ 66, now 165.1s, target 66.5
2021-03-10 04:40:15:frequency.c:623:inc_freq_with_fixed_vco: get pcb 43 ~ 56, chip_temp 55 ~ 66, now 166.1s, target 66.7
2021-03-10 04:40:16:frequency.c:623:inc_freq_with_fixed_vco: get pcb 43 ~ 56, chip_temp 55 ~ 66, now 167.1s, target 66.8
2021-03-10 04:40:17:frequency.c:623:inc_freq_with_fixed_vco: get pcb 42 ~ 57, chip_temp 55 ~ 66, now 168.1s, target 67.0
2021-03-10 04:40:18:frequency.c:623:inc_freq_with_fixed_vco: get pcb 43 ~ 57, chip_temp 55 ~ 66, now 169.1s, target 67.2
2021-03-10 04:40:19:frequency.c:623:inc_freq_with_fixed_vco: get pcb 43 ~ 57, chip_temp 55 ~ 66, now 170.1s, target 67.3
2021-03-10 04:40:20:frequency.c:623:inc_freq_with_fixed_vco: get pcb 42 ~ 57, chip_temp 55 ~ 66, now 171.1s, target 67.5
2021-03-10 04:40:21:frequency.c:623:inc_freq_with_fixed_vco: get pcb 43 ~ 57, chip_temp 54 ~ 66, now 172.1s, target 67.7
2021-03-10 04:40:22:frequency.c:623:inc_freq_with_fixed_vco: get pcb 42 ~ 56, chip_temp 54 ~ 66, now 173.1s, target 67.8
2021-03-10 04:40:23:frequency.c:623:inc_freq_with_fixed_vco: get pcb 43 ~ 58, chip_temp 54 ~ 66, now 174.1s, target 68.0
2021-03-10 04:40:23:frequency.c:657:inc_freq_with_fixed_vco: [7] _POSTDIV1 = 6, _POSTDIV2 = 4, USER_DIV = 1, freq = 126
2021-03-10 04:40:23:frequency.c:665:inc_freq_with_fixed_vco: set to 126M, get pcb 43 ~ 58, chip_temp 54 ~ 66
2021-03-10 04:40:23:frequency.c:671:inc_freq_with_fixed_vco: freq_mode 1=1 FREQ_MODE_USER, Conf.Check_Clock_Cnt=0
2021-03-10 04:40:23:driver-btm-api.c:1941:check_clock_counter_domain_last_core: freq 126 clock_counter_limit 17, no check, skip.
2021-03-10 04:40:31:frequency.c:623:inc_freq_with_fixed_vco: get pcb 42 ~ 58, chip_temp 53 ~ 66, now 182.1s, target 69.4
2021-03-10 04:40:31:frequency.c:657:inc_freq_with_fixed_vco: [8] _POSTDIV1 = 7, _POSTDIV2 = 3, USER_DIV = 1, freq = 144
2021-03-10 04:40:31:frequency.c:665:inc_freq_with_fixed_vco: set to 144M, get pcb 42 ~ 58, chip_temp 53 ~ 66
2021-03-10 04:40:31:frequency.c:671:inc_freq_with_fixed_vco: freq_mode 1=1 FREQ_MODE_USER, Conf.Check_Clock_Cnt=0
2021-03-10 04:40:31:driver-btm-api.c:1941:check_clock_counter_domain_last_core: freq 144 clock_counter_limit 20, no check, skip.
2021-03-10 04:40:39:frequency.c:623:inc_freq_with_fixed_vco: get pcb 41 ~ 58, chip_temp 53 ~ 67, now 190.1s, target 70.7
2021-03-10 04:40:39:frequency.c:657:inc_freq_with_fixed_vco: [9] _POSTDIV1 = 5, _POSTDIV2 = 4, USER_DIV = 1, freq = 151
2021-03-10 04:40:39:frequency.c:665:inc_freq_with_fixed_vco: set to 151M, get pcb 41 ~ 58, chip_temp 53 ~ 67
2021-03-10 04:40:39:frequency.c:671:inc_freq_with_fixed_vco: freq_mode 1=1 FREQ_MODE_USER, Conf.Check_Clock_Cnt=0
2021-03-10 04:40:39:driver-btm-api.c:1941:check_clock_counter_domain_last_core: freq 151 clock_counter_limit 21, no check, skip.
2021-03-10 04:40:47:frequency.c:623:inc_freq_with_fixed_vco: get pcb 41 ~ 57, chip_temp 53 ~ 66, now 198.1s, target 72.0
2021-03-10 04:40:47:frequency.c:657:inc_freq_with_fixed_vco: [10] _POSTDIV1 = 6, _POSTDIV2 = 3, USER_DIV = 1, freq = 168
2021-03-10 04:40:47:frequency.c:665:inc_freq_with_fixed_vco: set to 168M, get pcb 41 ~ 57, chip_temp 53 ~ 66
2021-03-10 04:40:47:frequency.c:671:inc_freq_with_fixed_vco: freq_mode 1=1 FREQ_MODE_USER, Conf.Check_Clock_Cnt=0
2021-03-10 04:40:47:driver-btm-api.c:1941:check_clock_counter_domain_last_core: freq 168 clock_counter_limit 23, no check, skip.
2021-03-10 04:40:55:frequency.c:623:inc_freq_with_fixed_vco: get pcb 40 ~ 58, chip_temp 54 ~ 66, now 206.1s, target 69.4
2021-03-10 04:40:55:frequency.c:657:inc_freq_with_fixed_vco: [11] _POSTDIV1 = 4, _POSTDIV2 = 4, USER_DIV = 1, freq = 189
2021-03-10 04:40:55:frequency.c:665:inc_freq_with_fixed_vco: set to 189M, get pcb 40 ~ 58, chip_temp 54 ~ 66
2021-03-10 04:40:55:frequency.c:671:inc_freq_with_fixed_vco: freq_mode 1=1 FREQ_MODE_USER, Conf.Check_Clock_Cnt=0
2021-03-10 04:40:55:driver-btm-api.c:1941:check_clock_counter_domain_last_core: freq 189 clock_counter_limit 27, no check, skip.
2021-03-10 04:41:03:frequency.c:623:inc_freq_with_fixed_vco: get pcb 40 ~ 57, chip_temp 55 ~ 66, now 214.1s, target 70.7
2021-03-10 04:41:03:frequency.c:657:inc_freq_with_fixed_vco: [12] _POSTDIV1 = 5, _POSTDIV2 = 3, USER_DIV = 1, freq = 202
2021-03-10 04:41:03:frequency.c:665:inc_freq_with_fixed_vco: set to 202M, get pcb 40 ~ 57, chip_temp 55 ~ 66
2021-03-10 04:41:03:frequency.c:671:inc_freq_with_fixed_vco: freq_mode 1=1 FREQ_MODE_USER, Conf.Check_Clock_Cnt=0
2021-03-10 04:41:03:driver-btm-api.c:1941:check_clock_counter_domain_last_core: freq 202 clock_counter_limit 29, no check, skip.
2021-03-10 04:41:11:frequency.c:623:inc_freq_with_fixed_vco: get pcb 40 ~ 57, chip_temp 56 ~ 66, now 222.2s, target 72.0
2021-03-10 04:41:11:frequency.c:657:inc_freq_with_fixed_vco: [13] _POSTDIV1 = 7, _POSTDIV2 = 2, USER_DIV = 1, freq = 216
2021-03-10 04:41:11:frequency.c:665:inc_freq_with_fixed_vco: set to 216M, get pcb 40 ~ 57, chip_temp 56 ~ 66
2021-03-10 04:41:11:frequency.c:671:inc_freq_with_fixed_vco: freq_mode 1=1 FREQ_MODE_USER, Conf.Check_Clock_Cnt=0
2021-03-10 04:41:11:driver-btm-api.c:1941:check_clock_counter_domain_last_core: freq 216 clock_counter_limit 31, no check, skip.
2021-03-10 04:41:19:frequency.c:623:inc_freq_with_fixed_vco: get pcb 40 ~ 57, chip_temp 57 ~ 66, now 230.2s, target 69.4
2021-03-10 04:41:19:frequency.c:657:inc_freq_with_fixed_vco: [14] _POSTDIV1 = 4, _POSTDIV2 = 3, USER_DIV = 1, freq = 253
2021-03-10 04:41:19:frequency.c:665:inc_freq_with_fixed_vco: set to 253M, get pcb 40 ~ 57, chip_temp 57 ~ 66
2021-03-10 04:41:19:frequency.c:671:inc_freq_with_fixed_vco: freq_mode 1=1 FREQ_MODE_USER, Conf.Check_Clock_Cnt=0
2021-03-10 04:41:19:driver-btm-api.c:1941:check_clock_counter_domain_last_core: freq 253 clock_counter_limit 37, no check, skip.
2021-03-10 04:41:27:frequency.c:623:inc_freq_with_fixed_vco: get pcb 39 ~ 56, chip_temp 59 ~ 67, now 238.2s, target 70.7
2021-03-10 04:41:27:frequency.c:657:inc_freq_with_fixed_vco: [15] _POSTDIV1 = 6, _POSTDIV2 = 2, USER_DIV = 1, freq = 253
2021-03-10 04:41:27:frequency.c:665:inc_freq_with_fixed_vco: set to 253M, get pcb 39 ~ 56, chip_temp 59 ~ 67
2021-03-10 04:41:27:frequency.c:671:inc_freq_with_fixed_vco: freq_mode 1=1 FREQ_MODE_USER, Conf.Check_Clock_Cnt=0
2021-03-10 04:41:27:driver-btm-api.c:1941:check_clock_counter_domain_last_core: freq 253 clock_counter_limit 37, no check, skip.
2021-03-10 04:41:35:frequency.c:623:inc_freq_with_fixed_vco: get pcb 40 ~ 57, chip_temp 59 ~ 66, now 246.2s, target 72.0
2021-03-10 04:41:35:frequency.c:657:inc_freq_with_fixed_vco: [16] _POSTDIV1 = 5, _POSTDIV2 = 2, USER_DIV = 1, freq = 303
2021-03-10 04:41:35:frequency.c:665:inc_freq_with_fixed_vco: set to 303M, get pcb 40 ~ 57, chip_temp 59 ~ 66
2021-03-10 04:41:35:power_api.c:376:set_to_voltage_by_steps: Set to voltage raw 2050, step by step.
2021-03-10 04:41:49:driver-hash-chip.c:737:dump_adc_voltage_v2: get ADC_DATAOUT from chain 1 with 0 regs timeout.
chain 1 domain  0:   d0 0.345,   d1 0.340,   d2 0.339,   d3 0.341,   sum = 1.364380
chain 1 domain  1:   d0 0.346,   d1 0.340,   d2 0.339,   d3 0.339,   sum = 1.364054
chain 1 domain  2:   d0 0.342,   d1 0.340,   d2 0.339,   d3 0.342,   sum = 1.362589
chain 1 domain  3:   d0 0.346,   d1 0.339,   d2 0.337,   d3 0.341,   sum = 1.363810
chain 1 domain  4:   d0 0.342,   d1 0.338,   d2 0.336,   d3 0.339,   sum = 1.355713
chain 1 domain  5:   d0 0.347,   d1 0.340,   d2 0.339,   d3 0.338,   sum = 1.363770
chain 1 domain  6:   d0 0.339,   d1 0.335,   d2 0.332,   d3 0.336,   sum = 1.341960
chain 1 domain  7:   d0 0.343,   d1 0.337,   d2 0.336,   d3 0.339,   sum = 1.355143
chain 1 domain  8:   d0 0.333,   d1 0.328,   d2 0.327,   d3 0.329,   sum = 1.317057
chain 1 domain  9:   d0 0.338,   d1 0.331,   d2 0.330,   d3 0.332,   sum = 1.331339
chain 1 domain 10:   d0 0.334,   d1 0.331,   d2 0.331,   d3 0.334,   sum = 1.330119
chain 1 domain 11:   d0 0.332,   d1 0.324,   d2 0.323,   d3 0.326,   sum = 1.305135
chain 1 domain 12:   d0 0.330,   d1 0.327,   d2 0.326,   d3 0.326,   sum = 1.309814
chain 1 domain 13:   d0 0.333,   d1 0.327,   d2 0.327,   d3 0.331,   sum = 1.318197
chain 1 domain 14:   d0 0.335,   d1 0.330,   d2 0.328,   d3 0.333,   sum = 1.324585
2021-03-10 04:41:50:driver-hash-chip.c:737:dump_adc_voltage_v2: get ADC_DATAOUT from chain 2 with 0 regs timeout.
chain 2 domain  0:   d0 0.347,   d1 0.342,   d2 0.359,   d3 0.355,   sum = 1.403036
chain 2 domain  1:   d0 0.349,   d1 0.344,   d2 0.342,   d3 0.342,   sum = 1.377360
chain 2 domain  2:   d0 0.341,   d1 0.339,   d2 0.338,   d3 0.340,   sum = 1.357544
chain 2 domain  3:   d0 0.337,   d1 0.331,   d2 0.329,   d3 0.329,   sum = 1.325399
chain 2 domain  4:   d0 0.334,   d1 0.332,   d2 0.328,   d3 0.331,   sum = 1.325317
chain 2 domain  5:   d0 0.339,   d1 0.332,   d2 0.331,   d3 0.333,   sum = 1.335002
chain 2 domain  6:   d0 0.340,   d1 0.337,   d2 0.336,   d3 0.338,   sum = 1.350586
chain 2 domain  7:   d0 0.340,   d1 0.336,   d2 0.335,   d3 0.337,   sum = 1.348226
chain 2 domain  8:   d0 0.332,   d1 0.329,   d2 0.328,   d3 0.330,   sum = 1.319661
chain 2 domain  9:   d0 0.338,   d1 0.334,   d2 0.334,   d3 0.334,   sum = 1.339681
chain 2 domain 10:   d0 0.330,   d1 0.329,   d2 0.328,   d3 0.329,   sum = 1.315674
chain 2 domain 11:   d0 0.330,   d1 0.324,   d2 0.324,   d3 0.326,   sum = 1.304118
chain 2 domain 12:   d0 0.331,   d1 0.328,   d2 0.327,   d3 0.328,   sum = 1.314290
chain 2 domain 13:   d0 0.333,   d1 0.327,   d2 0.327,   d3 0.330,   sum = 1.316244
chain 2 domain 14:   d0 0.337,   d1 0.334,   d2 0.333,   d3 0.337,   sum = 1.340820
2021-03-10 04:41:50:driver-hash-chip.c:493:check_adc_voltage: PASS domainn volt check: request 0.800 (index 0, open_core)
2021-03-10 04:41:50:frequency.c:671:inc_freq_with_fixed_vco: freq_mode 1=1 FREQ_MODE_USER, Conf.Check_Clock_Cnt=0
2021-03-10 04:41:50:driver-btm-api.c:1941:check_clock_counter_domain_last_core: freq 303 clock_counter_limit 45, no check, skip.
2021-03-10 04:41:52:driver-hash-chip.c:737:dump_adc_voltage_v2: get ADC_DATAOUT from chain 1 with 0 regs timeout.
chain 1 domain  0:   d0 0.343,   d1 0.339,   d2 0.338,   d3 0.341,   sum = 1.360758
chain 1 domain  1:   d0 0.344,   d1 0.339,   d2 0.338,   d3 0.339,   sum = 1.360840
chain 1 domain  2:   d0 0.342,   d1 0.339,   d2 0.338,   d3 0.343,   sum = 1.361450
chain 1 domain  3:   d0 0.345,   d1 0.338,   d2 0.338,   d3 0.341,   sum = 1.361654
chain 1 domain  4:   d0 0.340,   d1 0.337,   d2 0.336,   d3 0.339,   sum = 1.352254
chain 1 domain  5:   d0 0.345,   d1 0.338,   d2 0.338,   d3 0.338,   sum = 1.359456
chain 1 domain  6:   d0 0.339,   d1 0.334,   d2 0.333,   d3 0.335,   sum = 1.341105
chain 1 domain  7:   d0 0.342,   d1 0.336,   d2 0.336,   d3 0.338,   sum = 1.352539
chain 1 domain  8:   d0 0.333,   d1 0.328,   d2 0.328,   d3 0.330,   sum = 1.318929
chain 1 domain  9:   d0 0.338,   d1 0.331,   d2 0.331,   d3 0.332,   sum = 1.332479
chain 1 domain 10:   d0 0.334,   d1 0.331,   d2 0.332,   d3 0.334,   sum = 1.331584
chain 1 domain 11:   d0 0.333,   d1 0.325,   d2 0.324,   d3 0.327,   sum = 1.308716
chain 1 domain 12:   d0 0.330,   d1 0.327,   d2 0.327,   d3 0.327,   sum = 1.310872
chain 1 domain 13:   d0 0.334,   d1 0.328,   d2 0.328,   d3 0.331,   sum = 1.320923
chain 1 domain 14:   d0 0.335,   d1 0.330,   d2 0.329,   d3 0.333,   sum = 1.327474
2021-03-10 04:41:53:driver-hash-chip.c:737:dump_adc_voltage_v2: get ADC_DATAOUT from chain 2 with 0 regs timeout.
chain 2 domain  0:   d0 0.345,   d1 0.341,   d2 0.358,   d3 0.355,   sum = 1.399333
chain 2 domain  1:   d0 0.347,   d1 0.342,   d2 0.341,   d3 0.341,   sum = 1.370850
chain 2 domain  2:   d0 0.340,   d1 0.338,   d2 0.337,   d3 0.339,   sum = 1.354452
chain 2 domain  3:   d0 0.336,   d1 0.331,   d2 0.328,   d3 0.330,   sum = 1.325033
chain 2 domain  4:   d0 0.334,   d1 0.332,   d2 0.329,   d3 0.331,   sum = 1.325155
chain 2 domain  5:   d0 0.338,   d1 0.332,   d2 0.331,   d3 0.332,   sum = 1.333740
chain 2 domain  6:   d0 0.339,   d1 0.337,   d2 0.335,   d3 0.337,   sum = 1.347494
chain 2 domain  7:   d0 0.340,   d1 0.336,   d2 0.334,   d3 0.337,   sum = 1.346069
chain 2 domain  8:   d0 0.332,   d1 0.330,   d2 0.328,   d3 0.330,   sum = 1.319214
chain 2 domain  9:   d0 0.337,   d1 0.334,   d2 0.333,   d3 0.333,   sum = 1.336833
chain 2 domain 10:   d0 0.330,   d1 0.329,   d2 0.328,   d3 0.328,   sum = 1.315552
chain 2 domain 11:   d0 0.330,   d1 0.325,   d2 0.324,   d3 0.326,   sum = 1.305705
chain 2 domain 12:   d0 0.332,   d1 0.329,   d2 0.328,   d3 0.329,   sum = 1.317301
chain 2 domain 13:   d0 0.334,   d1 0.327,   d2 0.327,   d3 0.330,   sum = 1.318156
chain 2 domain 14:   d0 0.337,   d1 0.334,   d2 0.333,   d3 0.336,   sum = 1.340129
2021-03-10 04:41:53:driver-hash-chip.c:493:check_adc_voltage: PASS domainn volt check: request 0.800 (index 0, open_core)
2021-03-10 04:41:59:frequency.c:623:inc_freq_with_fixed_vco: get pcb 39 ~ 56, chip_temp 60 ~ 66, now 270.2s, target 72.0
2021-03-10 04:41:59:frequency.c:657:inc_freq_with_fixed_vco: [17] _POSTDIV1 = 4, _POSTDIV2 = 2, USER_DIV = 1, freq = 379
2021-03-10 04:41:59:frequency.c:665:inc_freq_with_fixed_vco: set to 379M, get pcb 39 ~ 56, chip_temp 60 ~ 66
2021-03-10 04:41:59:power_api.c:376:set_to_voltage_by_steps: Set to voltage raw 1960, step by step.
2021-03-10 04:42:13:driver-hash-chip.c:737:dump_adc_voltage_v2: get ADC_DATAOUT from chain 1 with 0 regs timeout.
chain 1 domain  0:   d0 0.328,   d1 0.323,   d2 0.324,   d3 0.325,   sum = 1.300171
chain 1 domain  1:   d0 0.330,   d1 0.323,   d2 0.324,   d3 0.324,   sum = 1.301310
chain 1 domain  2:   d0 0.326,   d1 0.323,   d2 0.325,   d3 0.328,   sum = 1.302083
chain 1 domain  3:   d0 0.330,   d1 0.322,   d2 0.324,   d3 0.326,   sum = 1.302002
chain 1 domain  4:   d0 0.326,   d1 0.322,   d2 0.323,   d3 0.323,   sum = 1.293416
chain 1 domain  5:   d0 0.330,   d1 0.324,   d2 0.324,   d3 0.323,   sum = 1.300334
chain 1 domain  6:   d0 0.324,   d1 0.319,   d2 0.319,   d3 0.321,   sum = 1.282267
chain 1 domain  7:   d0 0.328,   d1 0.321,   d2 0.322,   d3 0.322,   sum = 1.293131
chain 1 domain  8:   d0 0.318,   d1 0.313,   d2 0.314,   d3 0.315,   sum = 1.259562
chain 1 domain  9:   d0 0.323,   d1 0.316,   d2 0.317,   d3 0.317,   sum = 1.272990
chain 1 domain 10:   d0 0.319,   d1 0.315,   d2 0.318,   d3 0.319,   sum = 1.272217
chain 1 domain 11:   d0 0.318,   d1 0.310,   d2 0.309,   d3 0.311,   sum = 1.248210
chain 1 domain 12:   d0 0.315,   d1 0.312,   d2 0.312,   d3 0.312,   sum = 1.251221
chain 1 domain 13:   d0 0.318,   d1 0.312,   d2 0.313,   d3 0.315,   sum = 1.258952
chain 1 domain 14:   d0 0.319,   d1 0.314,   d2 0.314,   d3 0.318,   sum = 1.265422
2021-03-10 04:42:13:driver-hash-chip.c:737:dump_adc_voltage_v2: get ADC_DATAOUT from chain 2 with 0 regs timeout.
chain 2 domain  0:   d0 0.330,   d1 0.326,   d2 0.343,   d3 0.342,   sum = 1.340780
chain 2 domain  1:   d0 0.332,   d1 0.327,   d2 0.326,   d3 0.327,   sum = 1.312948
chain 2 domain  2:   d0 0.325,   d1 0.322,   d2 0.324,   d3 0.324,   sum = 1.295125
chain 2 domain  3:   d0 0.322,   d1 0.315,   d2 0.315,   d3 0.314,   sum = 1.266357
chain 2 domain  4:   d0 0.318,   d1 0.315,   d2 0.315,   d3 0.316,   sum = 1.264689
chain 2 domain  5:   d0 0.323,   d1 0.317,   d2 0.317,   d3 0.318,   sum = 1.274780
chain 2 domain  6:   d0 0.324,   d1 0.321,   d2 0.322,   d3 0.322,   sum = 1.289103
chain 2 domain  7:   d0 0.325,   d1 0.320,   d2 0.321,   d3 0.321,   sum = 1.287354
chain 2 domain  8:   d0 0.317,   d1 0.314,   d2 0.315,   d3 0.315,   sum = 1.261678
chain 2 domain  9:   d0 0.323,   d1 0.319,   d2 0.319,   d3 0.319,   sum = 1.279460
chain 2 domain 10:   d0 0.315,   d1 0.314,   d2 0.314,   d3 0.314,   sum = 1.257772
chain 2 domain 11:   d0 0.315,   d1 0.310,   d2 0.310,   d3 0.311,   sum = 1.246582
chain 2 domain 12:   d0 0.316,   d1 0.313,   d2 0.313,   d3 0.313,   sum = 1.255005
chain 2 domain 13:   d0 0.318,   d1 0.312,   d2 0.313,   d3 0.315,   sum = 1.258464
chain 2 domain 14:   d0 0.322,   d1 0.318,   d2 0.319,   d3 0.321,   sum = 1.280029
2021-03-10 04:42:13:driver-hash-chip.c:493:check_adc_voltage: PASS domainn volt check: request 0.800 (index 0, open_core)
2021-03-10 04:42:13:frequency.c:671:inc_freq_with_fixed_vco: freq_mode 1=1 FREQ_MODE_USER, Conf.Check_Clock_Cnt=0
2021-03-10 04:42:13:driver-btm-api.c:1941:check_clock_counter_domain_last_core: freq 379 clock_counter_limit 57, no check, skip.
2021-03-10 04:42:16:driver-hash-chip.c:737:dump_adc_voltage_v2: get ADC_DATAOUT from chain 1 with 0 regs timeout.
chain 1 domain  0:   d0 0.326,   d1 0.321,   d2 0.323,   d3 0.324,   sum = 1.294556
chain 1 domain  1:   d0 0.328,   d1 0.322,   d2 0.323,   d3 0.323,   sum = 1.295858
chain 1 domain  2:   d0 0.326,   d1 0.323,   d2 0.324,   d3 0.327,   sum = 1.299194
chain 1 domain  3:   d0 0.329,   d1 0.321,   d2 0.324,   d3 0.324,   sum = 1.298218
chain 1 domain  4:   d0 0.324,   d1 0.320,   d2 0.322,   d3 0.322,   sum = 1.288249
chain 1 domain  5:   d0 0.328,   d1 0.321,   d2 0.323,   d3 0.321,   sum = 1.293905
chain 1 domain  6:   d0 0.323,   d1 0.318,   d2 0.319,   d3 0.320,   sum = 1.279541
chain 1 domain  7:   d0 0.326,   d1 0.320,   d2 0.321,   d3 0.321,   sum = 1.288615
chain 1 domain  8:   d0 0.318,   d1 0.313,   d2 0.314,   d3 0.315,   sum = 1.259888
chain 1 domain  9:   d0 0.323,   d1 0.315,   d2 0.317,   d3 0.317,   sum = 1.272664
chain 1 domain 10:   d0 0.319,   d1 0.315,   d2 0.318,   d3 0.319,   sum = 1.271973
chain 1 domain 11:   d0 0.318,   d1 0.310,   d2 0.311,   d3 0.312,   sum = 1.250366
chain 1 domain 12:   d0 0.315,   d1 0.312,   d2 0.313,   d3 0.312,   sum = 1.251546
chain 1 domain 13:   d0 0.319,   d1 0.312,   d2 0.314,   d3 0.316,   sum = 1.260783
chain 1 domain 14:   d0 0.319,   d1 0.315,   d2 0.315,   d3 0.318,   sum = 1.267660
2021-03-10 04:42:17:driver-hash-chip.c:737:dump_adc_voltage_v2: get ADC_DATAOUT from chain 2 with 0 regs timeout.
chain 2 domain  0:   d0 0.327,   d1 0.324,   d2 0.342,   d3 0.340,   sum = 1.333984
chain 2 domain  1:   d0 0.330,   d1 0.325,   d2 0.324,   d3 0.324,   sum = 1.302979
chain 2 domain  2:   d0 0.324,   d1 0.321,   d2 0.322,   d3 0.323,   sum = 1.289469
chain 2 domain  3:   d0 0.320,   d1 0.315,   d2 0.314,   d3 0.314,   sum = 1.263387
chain 2 domain  4:   d0 0.318,   d1 0.315,   d2 0.315,   d3 0.315,   sum = 1.262411
chain 2 domain  5:   d0 0.322,   d1 0.316,   d2 0.317,   d3 0.317,   sum = 1.271281
chain 2 domain  6:   d0 0.322,   d1 0.319,   d2 0.321,   d3 0.321,   sum = 1.283081
chain 2 domain  7:   d0 0.324,   d1 0.318,   d2 0.320,   d3 0.320,   sum = 1.282511
chain 2 domain  8:   d0 0.316,   d1 0.313,   d2 0.314,   d3 0.314,   sum = 1.258138
chain 2 domain  9:   d0 0.321,   d1 0.317,   d2 0.318,   d3 0.317,   sum = 1.273438
chain 2 domain 10:   d0 0.315,   d1 0.313,   d2 0.314,   d3 0.313,   sum = 1.254801
chain 2 domain 11:   d0 0.315,   d1 0.309,   d2 0.311,   d3 0.311,   sum = 1.245565
chain 2 domain 12:   d0 0.316,   d1 0.313,   d2 0.314,   d3 0.313,   sum = 1.255493
chain 2 domain 13:   d0 0.318,   d1 0.312,   d2 0.313,   d3 0.315,   sum = 1.257690
chain 2 domain 14:   d0 0.321,   d1 0.317,   d2 0.319,   d3 0.320,   sum = 1.276978
2021-03-10 04:42:17:driver-hash-chip.c:493:check_adc_voltage: PASS domainn volt check: request 0.800 (index 0, open_core)
2021-03-10 04:42:17:frequency.c:717:inc_freq_with_fixed_step: chain = 1, freq_start = 380, freq_end = 380, freq_step = 5, is_higher_voltage = true
2021-03-10 04:42:17:frequency.c:717:inc_freq_with_fixed_step: chain = 2, freq_start = 380, freq_end = 380, freq_step = 5, is_higher_voltage = true
2021-03-10 04:42:17:power_api.c:376:set_to_voltage_by_steps: Set to voltage raw 1910, step by step.
2021-03-10 04:42:29:driver-hash-chip.c:737:dump_adc_voltage_v2: get ADC_DATAOUT from chain 1 with 0 regs timeout.
chain 1 domain  0:   d0 0.318,   d1 0.314,   d2 0.315,   d3 0.316,   sum = 1.262899
chain 1 domain  1:   d0 0.320,   d1 0.314,   d2 0.315,   d3 0.315,   sum = 1.264120
chain 1 domain  2:   d0 0.318,   d1 0.315,   d2 0.315,   d3 0.318,   sum = 1.266805
chain 1 domain  3:   d0 0.321,   d1 0.314,   d2 0.315,   d3 0.317,   sum = 1.266113
chain 1 domain  4:   d0 0.316,   d1 0.313,   d2 0.313,   d3 0.315,   sum = 1.257406
chain 1 domain  5:   d0 0.321,   d1 0.314,   d2 0.315,   d3 0.314,   sum = 1.262939
chain 1 domain  6:   d0 0.315,   d1 0.310,   d2 0.310,   d3 0.312,   sum = 1.247477
chain 1 domain  7:   d0 0.318,   d1 0.313,   d2 0.313,   d3 0.314,   sum = 1.257853
chain 1 domain  8:   d0 0.310,   d1 0.306,   d2 0.305,   d3 0.307,   sum = 1.227865
chain 1 domain  9:   d0 0.315,   d1 0.308,   d2 0.308,   d3 0.309,   sum = 1.240641
chain 1 domain 10:   d0 0.311,   d1 0.308,   d2 0.310,   d3 0.311,   sum = 1.239543
chain 1 domain 11:   d0 0.310,   d1 0.302,   d2 0.302,   d3 0.304,   sum = 1.218058
chain 1 domain 12:   d0 0.307,   d1 0.304,   d2 0.304,   d3 0.304,   sum = 1.219604
chain 1 domain 13:   d0 0.311,   d1 0.304,   d2 0.305,   d3 0.308,   sum = 1.228434
chain 1 domain 14:   d0 0.311,   d1 0.307,   d2 0.307,   d3 0.309,   sum = 1.234131
2021-03-10 04:42:30:driver-hash-chip.c:737:dump_adc_voltage_v2: get ADC_DATAOUT from chain 2 with 0 regs timeout.
chain 2 domain  0:   d0 0.320,   d1 0.309,   d2 0.331,   d3 0.334,   sum = 1.294027
chain 2 domain  1:   d0 0.323,   d1 0.317,   d2 0.318,   d3 0.317,   sum = 1.275146
chain 2 domain  2:   d0 0.316,   d1 0.314,   d2 0.316,   d3 0.316,   sum = 1.261230
mikeywith
Legendary
*
Offline Offline

Activity: 2240
Merit: 6405


be constructive or S.T.F.U


View Profile
March 10, 2021, 12:49:20 AM
 #2

While I don't like Slushpool at all, I don't think it's the cause of your problem, it's likely just a terrible coincide.

Code:
2021-03-09 21:23:23:driver-btm-api.c:1217:check_asic_number: Chain 0 only find 134 asic, will power off hash board 0
2021-03-09 21:23:52:driver-btm-api.c:1217:check_asic_number: Chain 1 only find 0 asic, will power off hash board 1

The S17e uses 135 Asics on each hashboarrd, your board 0 (usually the most left when facing the miner's front-side) shows 0 asics, and chain 1 which is the middle board is showing only 134 (so it's missing a single asic), this problem is very common with all the 17 series, the heatsinks solder they use on those is pretty bad and eventually, chips start dying.

There is a good chance that your board 1 will come back to normal after a couple of reboots, chances are slim for board 0, some times people get lucky with custom firmware so you might check if any trusted devs have the S17e on their list.

And please, use the code tag when posting Kernel logs.

█▀▀▀











█▄▄▄
▀▀▀▀▀▀▀▀▀▀▀
e
▄▄▄▄▄▄▄▄▄▄▄
█████████████
████████████▄███
██▐███████▄█████▀
█████████▄████▀
███▐████▄███▀
████▐██████▀
█████▀█████
███████████▄
████████████▄
██▄█████▀█████▄
▄█████████▀█████▀
███████████▀██▀
████▀█████████
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
c.h.
▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄
▀▀▀█











▄▄▄█
▄██████▄▄▄
█████████████▄▄
███████████████
███████████████
███████████████
███████████████
███░░█████████
███▌▐█████████
█████████████
███████████▀
██████████▀
████████▀
▀██▀▀
Tony2o6 (OP)
Newbie
*
Offline Offline

Activity: 4
Merit: 0


View Profile
March 10, 2021, 12:56:10 AM
Last edit: March 11, 2021, 11:27:23 PM by frodocooper
 #3

Hello, Thank you for your response! So I started switching out the cables on the control board and two boards started working again and one only found 134 asics. I am upgrading my firmware again to see if it fixes the problem. When I switch the cables around, a different hashboard only finds 134 asics, not the hashboard from before which is weird. I will include the log in a second.

I will also add the code tag, sorry I couldn’t find it before hehe.
mikeywith
Legendary
*
Offline Offline

Activity: 2240
Merit: 6405


be constructive or S.T.F.U


View Profile
March 10, 2021, 01:15:34 AM
Last edit: March 11, 2021, 11:28:05 PM by frodocooper
 #4

When I switch the cables around, a different hashboard only finds 134 asics, not the hashboard from before which is weird.

This is normal nothing is weird about the result, it's a bit confusing but let me try to explain.

Board 0 is bad
Board 2 is good

The control board connects to hash boards this way

0 control board > 0 hash board >Bad
1 control board > 1 hash board >NA
2 contorl board > 2 hash board >Good

Say you switchboard 2 and 0, the reading on the contorl board which is what you see in the kernel will be

0 control board > 2 hash board >Good
1 control board > 1 hash board >NA
2 contorl board > 0 hash board >Bad

Notice that despite the fact the reference on the control board has changed, the control board numbering remains the same, board 0 is still bad, if however, you get this

0 control board > 2 hash board >Bad
1 control board > 1 hash board >NA
2 contorl board > 0 hash board >Good

That's good news, it means both boards 0 and 2 are fine and something is wrong with the wires or the PSU busbars, and that is very, very unlikely to be the case, so good luck.

█▀▀▀











█▄▄▄
▀▀▀▀▀▀▀▀▀▀▀
e
▄▄▄▄▄▄▄▄▄▄▄
█████████████
████████████▄███
██▐███████▄█████▀
█████████▄████▀
███▐████▄███▀
████▐██████▀
█████▀█████
███████████▄
████████████▄
██▄█████▀█████▄
▄█████████▀█████▀
███████████▀██▀
████▀█████████
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
c.h.
▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄
▀▀▀█











▄▄▄█
▄██████▄▄▄
█████████████▄▄
███████████████
███████████████
███████████████
███████████████
███░░█████████
███▌▐█████████
█████████████
███████████▀
██████████▀
████████▀
▀██▀▀
Tony2o6 (OP)
Newbie
*
Offline Offline

Activity: 4
Merit: 0


View Profile
March 10, 2021, 01:27:57 AM
Last edit: March 11, 2021, 11:28:28 PM by frodocooper
 #5

Okay so I think I figured it out... I’ve tested multiple times now and it seems like one of my hashboards is only finding 134 asics.. is this repairable? I am currently in China so if it is repairable I would have to get it professionally soldered.. or is there something else I can do to did this? And is it normal that this happened after I powered it off and powered it on? Because it was working perfectly fine before I powered it off which is weird.
mikeywith
Legendary
*
Offline Offline

Activity: 2240
Merit: 6405


be constructive or S.T.F.U


View Profile
March 10, 2021, 01:11:38 PM
Last edit: March 11, 2021, 11:29:05 PM by frodocooper
 #6

I am currently in China so if it is repairable I would have to get it professionally soldered

I believe China is the best place to get your miners fixed, check Zeusbtc they have repair centers there, you could also send it to Bitmain although someone mentioned they told him they can't ship the gear back and they offered him some coupons instead, and a buyer for those coupons lol.

And is it normal that this happened after I powered it off and powered it on?

Yes pretty normal, it will work sometimes and won't on the others, eventually, it will just die.

█▀▀▀











█▄▄▄
▀▀▀▀▀▀▀▀▀▀▀
e
▄▄▄▄▄▄▄▄▄▄▄
█████████████
████████████▄███
██▐███████▄█████▀
█████████▄████▀
███▐████▄███▀
████▐██████▀
█████▀█████
███████████▄
████████████▄
██▄█████▀█████▄
▄█████████▀█████▀
███████████▀██▀
████▀█████████
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
c.h.
▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄
▀▀▀█











▄▄▄█
▄██████▄▄▄
█████████████▄▄
███████████████
███████████████
███████████████
███████████████
███░░█████████
███▌▐█████████
█████████████
███████████▀
██████████▀
████████▀
▀██▀▀
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!