Title: Antminer S17e's strange problem
Post by: jonaeljoni on January 23, 2021, 01:05:35 PM
My Miner's hashrate is only 2/3
Common problem, yes I have read but I didn't find issue like this.
But my antminer finds all chains and it shows that all ASIC chips are 00000 00000 00000.....
All three green lights are on on control board.
I have upgraded latest firmware.
I have changed cords between hashboard and control board. The fault isn't in cords I think. If change J1 cord to J4 on control board problem follows. Miner stats only shows Chain#4 instead of chain#1 after that. Which is a good thing I guess.
Is it still possible that hashboard is broken or asic chips?
I have stat pic https://www.imgpaste.net/image/jZ0wb
and kernel log here https://pastebin.com/7AKnD3Fk
Sorry for establishing new thread and thanks for any answers
Title: Re: Antminer S17e's strange problem
Post by: danieleither on January 23, 2021, 03:46:58 PM
Overheating perhaps? Your fans are practically running at 100%.
Also noted this at the end of your kernel log:
2021-01-23 11:55:07:thread.c:309:is_temp_reopen_core: current chip max temperature(86) is too high, >= 86
Title: Re: Antminer S17e's strange problem
Post by: jonaeljoni on January 23, 2021, 03:58:13 PM
Okay, I can try add more cooling features. I tried to read kernel log also. I don't understand much about it. But I noticed these: :32:driver-hash-chip.c:486:check_adc_voltage: FAIL domain volt check: chain 0 domain 11 volt 0.000 less then request 0.800 (index 0) 2021-01-23 11:11:32:driver-hash-chip.c:486:check_adc_voltage: FAIL domain volt check: chain 0 domain 12 volt 0.000 less then request 0.800 (index 0) 2021-01-23 11:11:32:driver-hash-chip.c:486:check_adc_voltage: FAIL domain volt check: chain 0 domain 13 volt 0.000 less then request 0.800 (index 0) 2021-01-23 11:11:32:driver-hash-chip.c:486:check_adc_voltage: FAIL domain volt check: chain 0 domain 14 volt 0.000 less then request 0.800 (index 0) 2021-01-23 11:11:32:driver-btm-api.c:2379:bitmain_board_init: FAULT: check_asic_number_until_volt_balance PASS but bitmain_board_config_init FAIL!!!
31:driver-hash-chip.c:591:recalc_invalid_volt: chain 0 domain 10 column 01 single core_domain: no useful core domain volt: 0.00 0.00 0.00 0.00. 2021-01-23 11:11:31:driver-hash-chip.c:591:recalc_invalid_volt: chain 0 domain 10 column 02 single core_domain: no useful core domain volt: 0.00 0.00 0.00 0.00. 2021-01-23 11:11:31:driver-hash-chip.c:591:recalc_invalid_volt: chain 0 domain 10 column 03 single core_domain: no useful core domain volt: 0.00 0.00 0.00 0.00. 2021-01-23 11:11:31:driver-hash-chip.c:591:recalc_invalid_volt: chain 0 domain 10 column 04 single core_domain: no useful core domain volt: 0.00 0.00 0.00 0.00. 2021-01-23 11:11:31:driver-hash-chip.c:591:recalc_invalid_volt: chain 0 domain 10 column 05 single core_domain: no useful core domain volt: 0.00 0.00 0.00 0.00. 2021-01-23 11:11:31:driver-hash-chip.c:591:recalc_invalid_volt: chain 0 domain 10 column 06 single core_domain: no useful core domain volt: 0.00 0.00 0.00 0.00. 2021-01-23 11:11:31:driver-hash-chip.c:591:recalc_invalid_volt: chain 0 domain 10 column 07 single core_domain: no useful core domain volt: 0.00 0.00 0.00 0.00. 2021-01-23 11:11:31:driver-hash-chip.c:591:recalc_invalid_volt: chain 0 domain 10 column 08 single core_domain: no useful core domain volt: 0.00 0.00 0.00 0.00. 2021-01-23 11:11:31:driver-hash-chip.c:591:recalc_invalid_volt: chain 0 domain 11 column 00 single core_domain: no useful core domain volt: 0.00 0.00 0.00 0.00. 2021-01-23 11:11:31:driver-hash-chip.c:591:recalc_invalid_volt: chain 0 domain 11 column 01 single core_domain: no useful core domain volt: 0.00 0.00 0.00 0.00. 2021-01-23 11:11:31:driver-hash-chip.c:591:recalc_invalid_volt: chain 0 domain 11 column 02 single core_domain: no useful core domain volt: 0.00 0.00 0.00 0.00. 2021-01-23 11:11:31:driver-hash-chip.c:591:recalc_invalid_volt: chain 0 domain 11 column 03 single core_domain: no useful core domain volt: 0.00 0.00 0.00 0.00. 2021-01-23 11:11:31:driver-hash-chip.c:591:recalc_invalid_volt: chain 0 domain 11 column 04 single core_domain: no useful core domain volt: 0.00 0.00 0.00 0.00. 2021-01-23 11:11:31:driver-hash-chip.c:591:recalc_invalid_volt: chain 0 domain 11 column 05 single core_domain: no useful core domain volt: 0.00 0.00 0.00 0.00. 2021-01-23 11:11:31:driver-hash-chip.c:591:recalc_invalid_volt: chain 0 domain 11 column 06 single core_domain: no useful core domain volt: 0.00 0.00 0.00 0.00. 2021-01-23 11:11:31:driver-hash-chip.c:591:recalc_invalid_volt: chain 0 domain 11 column 07 single core_domain: no useful core domain volt: 0.00 0.00 0.00 0.00. 2021-01-23 11:11:31:driver-hash-chip.c:591:recalc_invalid_volt: chain 0 domain 11 column 08 single core_domain: no useful core domain volt: 0.00 0.00 0.00 0.00. 2021-01-23 11:11:31:driver-hash-chip.c:591:recalc_invalid_volt: chain 0 domain 12 column 00 single core_domain: no useful core domain volt: 0.00 0.00 0.00 0.00. 2021-01-23 11:11:31:driver-hash-chip.c:591:recalc_invalid_volt: chain 0 domain 12 column 01 single core_domain: no useful core domain volt: 0.00 0.00 0.00 0.00. 2021-01-23 11:11:31:driver-hash-chip.c:591:recalc_invalid_volt: chain 0 domain 12 column 02 single core_domain: no useful core domain volt: 0.00 0.00 0.00 0.00. 2021-01-23 11:11:31:driver-hash-chip.c:591:recalc_invalid_volt: chain 0 domain 12 column 03 single core_domain: no useful core domain volt: 0.00 0.00 0.00 0.00. 2021-01-23 11:11:31:driver-hash-chip.c:591:recalc_invalid_volt: chain 0 domain 12 column 04 single core_domain: no useful core domain volt: 0.00 0.00 0.00 0.00. 2021-01-23 11:11:31:driver-hash-chip.c:591:recalc_invalid_volt: chain 0 domain 12 column 05 single core_domain: no useful core domain volt: 0.00 0.00 0.00 0.00. 2021-01-23 11:11:31:driver-hash-chip.c:591:recalc_invalid_volt: chain 0 domain 12 column 06 single core_domain: no useful core domain volt: 0.00 0.00 0.00 0.00. 2021-01-23 11:11:31:driver-hash-chip.c:591:recalc_invalid_volt: chain 0 domain 12 column 07 single core_domain: no useful core domain volt: 0.00 0.00 0.00 0.00. 2021-01-23 11:11:31:driver-hash-chip.c:591:recalc_invalid_volt: chain 0 domain 12 column 08 single core_domain: no useful core domain volt: 0.00 0.00 0.00 0.00. 2021-01-23 11:11:31:driver-hash-chip.c:591:recalc_invalid_volt: chain 0 domain 13 column 00 single core_domain: no useful core domain volt: 0.00 0.00 0.00 0.00. 2021-01-23 11:11:31:driver-hash-chip.c:591:recalc_invalid_volt: chain 0 domain 13 column 01 single core_domain: no useful core domain volt: 0.00 0.00 0.00 0.00. 2021-01-23 11:11:31:driver-hash-chip.c:591:recalc_invalid_volt: chain 0 domain 13 column 02 single core_domain: no useful core domain volt: 0.00 0.00 0.00 0.00. 2021-01-23 11:11:31:driver-hash-chip.c:591:recalc_invalid_volt: chain 0 domain 13 column 03 single core_domain: no useful core domain volt: 0.00 0.00 0.00 0.00. 2021-01-23 11:11:31:driver-hash-chip.c:591:recalc_invalid_volt: chain 0 domain 13 column 04 single core_domain: no useful core domain volt: 0.00 0.00 0.00 0.00. 2021-01-23 11:11:31:driver-hash-chip.c:591:recalc_invalid_volt: chain 0 domain 13 column 05 single core_domain: no useful core domain volt: 0.00 0.00 0.00 0.00. 2021-01-23 11:11:31:driver-hash-chip.c:591:recalc_invalid_volt: chain 0 domain 13 column 06 single core_domain: no useful core domain volt: 0.00 0.00 0.00 0.00. 2021-01-23 11:11:31:driver-hash-chip.c:591:recalc_invalid_volt: chain 0 domain 13 column 07 single core_domain: no useful core domain volt: 0.00 0.00 0.00 0.00. 2021-01-23 11:11:31:driver-hash-chip.c:591:recalc_invalid_volt: chain 0 domain 13 column 08 single core_domain: no useful core domain volt: 0.00 0.00 0.00 0.00. 2021-01-23 11:11:31:driver-hash-chip.c:591:recalc_invalid_volt: chain 0 domain 14 column 00 single core_domain: no useful core domain volt: 0.00 0.00 0.00 0.00. 2021-01-23 11:11:31:driver-hash-chip.c:591:recalc_invalid_volt: chain 0 domain 14 column 01 single core_domain: no useful core domain volt: 0.00 0.00 0.00 0.00. 2021-01-23 11:11:31:driver-hash-chip.c:591:recalc_invalid_volt: chain 0 domain 14 column 02 single core_domain: no useful core domain volt: 0.00 0.00 0.00 0.00. 2021-01-23 11:11:31:driver-hash-chip.c:591:recalc_invalid_volt: chain 0 domain 14 column 03 single core_domain: no useful core domain volt: 0.00 0.00 0.00 0.00. 2021-01-23 11:11:31:driver-hash-chip.c:591:recalc_invalid_volt: chain 0 domain 14 column 04 single core_domain: no useful core domain volt: 0.00 0.00 0.00 0.00. 2021-01-23 11:11:31:driver-hash-chip.c:591:recalc_invalid_volt: chain 0 domain 14 column 05 single core_domain: no useful core domain volt: 0.00 0.00 0.00 0.00. 2021-01-23 11:11:31:driver-hash-chip.c:591:recalc_invalid_volt: chain 0 domain 14 column 06 single core_domain: no useful core domain volt: 0.00 0.00 0.00 0.00. 2021-01-23 11:11:31:driver-hash-chip.c:591:recalc_invalid_volt: chain 0 domain 14 column 07 single core_domain: no useful core domain volt: 0.00 0.00 0.00 0.00. 2021-01-23 11:11:31:driver-hash-chip.c:591:recalc_invalid_volt: chain 0 domain 14 column 08 single core_domain: no useful core domain volt: 0.00 0.00 0.00 0.00. 2021-01-23 11:11:31:driver-hash-chip.c:707:dump_adc_voltage_v2: chain 0 domain 11 core_domain 0: all asic timeout or overrange. 2021-01-23 11:11:31:driver-hash-chip.c:707:dump_adc_voltage_v2: chain 0 domain 11 core_domain 1: all asic timeout or overrange. 2021-01-23 11:11:31:driver-hash-chip.c:707:dump_adc_voltage_v2: chain 0 domain 11 core_domain 2: all asic timeout or overrange. 2021-01-23 11:11:31:driver-hash-chip.c:707:dump_adc_voltage_v2: chain 0 domain 11 core_domain 3: all asic timeout or overrange. 2021-01-23 11:11:31:driver-hash-chip.c:707:dump_adc_voltage_v2: chain 0 domain 12 core_domain 0: all asic timeout or overrange. 2021-01-23 11:11:31:driver-hash-chip.c:707:dump_adc_voltage_v2: chain 0 domain 12 core_domain 1: all asic timeout or overrange. 2021-01-23 11:11:31:driver-hash-chip.c:707:dump_adc_voltage_v2: chain 0 domain 12 core_domain 2: all asic timeout or overrange. 2021-01-23 11:11:31:driver-hash-chip.c:707:dump_adc_voltage_v2: chain 0 domain 12 core_domain 3: all asic timeout or overrange. 2021-01-23 11:11:31:driver-hash-chip.c:707:dump_adc_voltage_v2: chain 0 domain 13 core_domain 0: all asic timeout or overrange. 2021-01-23 11:11:31:driver-hash-chip.c:707:dump_adc_voltage_v2: chain 0 domain 13 core_domain 1: all asic timeout or overrange. 2021-01-23 11:11:31:driver-hash-chip.c:707:dump_adc_voltage_v2: chain 0 domain 13 core_domain 2: all asic timeout or overrange. 2021-01-23 11:11:31:driver-hash-chip.c:707:dump_adc_voltage_v2: chain 0 domain 13 core_domain 3: all asic timeout or overrange. 2021-01-23 11:11:31:driver-hash-chip.c:707:dump_adc_voltage_v2: chain 0 domain 14 core_domain 0: all asic timeout or overrange. 2021-01-23 11:11:31:driver-hash-chip.c:707:dump_adc_voltage_v2: chain 0 domain 14 core_domain 1: all asic timeout or overrange. 2021-01-23 11:11:31:driver-hash-chip.c:707:dump_adc_voltage_v2: chain 0 domain 14 core_domain 2: all asic timeout or overrange. 2021-01-23 11:11:31:driver-hash-chip.c:707:dump_adc_voltage_v2: chain 0 domain 14 core_domain 3: all asic timeout or overrange. 2021-01-23 11:11:31:driver-hash-chip.c:737:dump_adc_voltage_v2: get ADC_DATAOUT from chain 0 with 176 regs timeout.
Can it be power issue? Like it doesn't get sufficient power or something? Key words what I mean are invalid volt and FAIL domain volt check. Sounds bad I suppose. In addition, I have just bought that machine which is pre-owned but haven't run more than 24h before. I can't say have this chain#1 ever worked. Little bit better now with fans https://www.imgpaste.net/image/jZO6w.
Title: Re: Antminer S17e's strange problem
Post by: mikeywith on January 24, 2021, 06:12:10 AM
2021-01-23 11:11:32:driver-btm-api.c:2379:bitmain_board_init: FAULT: check_asic_number_until_volt_balance PASS but bitmain_board_config_init FAIL!!!
There are a few things I would check, the first one would be the PSU, power off-chain 2 and 3, this will confirm if the problem is a bad PSU (a very common issue) or your Chain 1 has other problems, once that test is done, if the PSU is fine and the board still shows 0 frequency and hashrate, your next move would be changing the tunning profile, what is your profile settings as of right now? On a side note, BinancePool sucks (https://bitcointalk.org/index.php?topic=5271427.0).
Title: Re: Antminer S17e's strange problem
Post by: jonaeljoni on January 24, 2021, 06:32:45 AM
I disassembled miner yesterday, I tried to look any signs of problems but no result. I read yesterday that someone is mining with 2 hashboards and due to that he have changed a faulty one in the middle expected obtain low temperature for those two which are working. I did that. So that is why now it is chain one which is showing zero. I just wanted to clear that before I post new pics about miner's stats. So now I unplugged those chains which were working. And started miner with that problematic chain. I am mining BSV, do you have tips for better pools. And what do you think about that BSV, will it be disaster or is it future's coin? I will add kernel log and stat pic after a little while, my miner is about to start now. ... your next move would be changing the tunning profile, what is your profile settings as of right now?
I don't know my settings and where or how change those. We can look that after this psu test is over. This is kernel log when miner started with that faulty chain: 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: 195680K/245760K available (6345K kernel code, 231K rwdata, 1896K rodata, 1024K init, 223K bss, 33696K 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: 20656K (cc6d4000 - cdb00000) 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 nand_read_bbt: bad block at 0x000000c00000 nand_read_bbt: bad block at 0x000006800000 nand_read_bbt: bad block at 0x00000da00000 nand_read_bbt: bad block at 0x00000dc00000 nand_read_bbt: bad block at 0x00000dcc0000 nand_read_bbt: bad block at 0x00000f840000 nand_read_bbt: bad block at 0x00000f900000 nand_read_bbt: bad block at 0x00000fac0000 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: 9/4, 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): recovery needed UBIFS (ubi0:0): recovery completed 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: 1014, bad PEBs: 10, corrupted PEBs: 0 ubi1: user volume: 1, internal volumes: 1, max. volumes count: 128 ubi1: max/mean erase counter: 648/147, WL threshold: 4096, image sequence number: 614900815 ubi1: available PEBs: 0, total reserved PEBs: 1014, PEBs reserved for bad PEB handling: 30 ubi1: background thread "ubi_bgt1d" started, PID 720 UBIFS (ubi1:0): background thread "ubifs_bgt1_0" started, PID 723 UBIFS (ubi1:0): recovery needed UBIFS (ubi1:0): recovery completed 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 random: nonblocking pool is initialized 2021-01-24 06:22:22:thread.c:1555:create_bitmain_soc_init_thread: create thread 2021-01-24 06:22:22:driver-btm-api.c:682:init_freq_mode: This is scan-user version 2021-01-24 06:22:22:driver-btm-api.c:2518:bitmain_soc_init: Miner compile time: Thu Oct 22 07:33:06 CST 2020 type: Antminer S17e 2021-01-24 06:22:22:driver-btm-api.c:2519:bitmain_soc_init: commit version: 037ddcd 2020-10-21 22:42:21, build by: jenkins 2020-10-22 07:37:50 2021-01-24 06:22:22:driver-btm-api.c:2520:bitmain_soc_init: opt_multi_version = 1 2021-01-24 06:22:22:driver-btm-api.c:2521:bitmain_soc_init: opt_bitmain_ab = 1 2021-01-24 06:22:22:driver-btm-api.c:2522:bitmain_soc_init: mid_auto_gen = 0 2021-01-24 06:22:22:driver-btm-api.c:2523:bitmain_soc_init: work_mode = 0 2021-01-24 06:22:22:driver-btm-api.c:2524:bitmain_soc_init: power_feedback_en = true 2021-01-24 06:22:22:driver-btm-api.c:2067:show_sn: no SN got, please write SN to /config/sn 2021-01-24 06:22:22:driver-btm-api.c:1384:miner_device_init: Detect 256MB control board of XILINX 2021-01-24 06:22:22:driver-btm-api.c:1325:init_fan_parameter: fan_eft : 0 fan_pwm : 0 2021-01-24 06:22:28:driver-btm-api.c:1309:init_miner_version: miner ID : 81742c4815408854 2021-01-24 06:22:28:driver-btm-api.c:1315:init_miner_version: FPGA Version = 0xB023 2021-01-24 06:22:30:auto_adapt.c:100:_get_board_info: chain[1] board bin: 1, chip bin: 1, chip ft: A4V2, chip version: AB 2021-01-24 06:22:30:driver-btm-api.c:2164:get_calibration_voltage: calibration voltage flag is error data. 2021-01-24 06:22:30 voltage[1] = 1850 2021-01-24 06:22:30:auto_adapt.c:273:is_sweep_failed_before: open sweep tag failed voltage_ref = 0 2100 2100 2100 2100 2100 2000 1980 1980 1950 1950 1980 1950 1950 1920 1920 1950 1950 1920 1900 1900 1950 1920 1900 1880 1880
2021-01-24 06:22:30:thread.c:1523:create_read_nonce_reg_thread: create thread 2021-01-24 06:22:30:driver-btm-api.c:698:dump_pcb_bom_version: Chain [1] PCB Version: 0x0128 2021-01-24 06:22:30:driver-btm-api.c:699:dump_pcb_bom_version: Chain [1] BOM Version: 0x0100 2021-01-24 06:22:37:driver-btm-api.c:2344:bitmain_board_init: Fan check passed. 2021-01-24 06:22:38:board.c:81:jump_and_app_check_restore_pic: chain[1] PIC jump to app 2021-01-24 06:22:40:board.c:94:jump_and_app_check_restore_pic: Check chain[1] PIC fw version=0xb9 2021-01-24 06:22:40:thread.c:1518:create_pic_heart_beat_thread: create thread 2021-01-24 06:22:41:power_api.c:241:power_init: power type version: 0x0042 2021-01-24 06:22:43:power_api.c:259:power_init: Power init: 2021-01-24 06:22:43:power_api.c:260:power_init: current_voltage_raw = 2136 2021-01-24 06:22:43:power_api.c:261:power_init: highest_voltage_raw = 2000 2021-01-24 06:22:43:power_api.c:262:power_init: working_voltage_raw = 1800 2021-01-24 06:22:43:power_api.c:263:power_init: higher_voltage_raw = 1850 2021-01-24 06:22:43:power_api.c:264:power_init: check_asic_voltage_raw = 1800 2021-01-24 06:22:43:driver-btm-api.c:2354:bitmain_board_init: Enter 60s sleep to make sure power release finish. 2021-01-24 06:23:45:driver-btm-api.c:1123:check_asic_number_until_volt_balance: THIS is No.1 time boost asic: 2021-01-24 06:23:45:power_api.c:334:modify_check_asic_voltage: check_asic_voltage_raw = 1800 2021-01-24 06:23:48:power_api.c:298:set_to_check_asic_voltage_by_steps: Set to voltage raw 1800, step by step. 2021-01-24 06:24:07:uart.c:69:set_baud: set UART baud to 115200 chain 1, IO_DRIVE_STRENGTH_CONFIGURATION reg = 0x 7777777 2021-01-24 06:24:11:driver-btm-api.c:1035:check_asic_number_with_power_on: Chain[1]: find 135 asic, times 0 2021-01-24 06:24:11:driver-btm-api.c:1163:check_asic_number_until_volt_balance: PASS: volt balance at No.1 time boost asic. 2021-01-24 06:24:11:power_api.c:364:set_to_highest_voltage_by_steps: Set to voltage raw 2000, step by step. 2021-01-24 06:24:34:driver-hash-chip.c:876:set_uart_relay: set uart relay to 0x390003 2021-01-24 06:24:34:driver-hash-chip.c:1264:set_ldo_ctrl: Set LDO to 0x2000203 2021-01-24 06:24:35:driver-hash-chip.c:613:recalc_invalid_volt: fix timeout adc_read_back[chain 1][domain 10][column 4][core_domain 0] to 0.35 2021-01-24 06:24:35:driver-hash-chip.c:613:recalc_invalid_volt: fix timeout adc_read_back[chain 1][domain 10][column 4][core_domain 1] to 0.69 2021-01-24 06:24:35:driver-hash-chip.c:613:recalc_invalid_volt: fix timeout adc_read_back[chain 1][domain 10][column 5][core_domain 0] to 0.35 2021-01-24 06:24:35:driver-hash-chip.c:613:recalc_invalid_volt: fix timeout adc_read_back[chain 1][domain 10][column 5][core_domain 1] to 0.69 2021-01-24 06:24:35:driver-hash-chip.c:613:recalc_invalid_volt: fix timeout adc_read_back[chain 1][domain 10][column 6][core_domain 0] to 0.35 2021-01-24 06:24:35:driver-hash-chip.c:613:recalc_invalid_volt: fix timeout adc_read_back[chain 1][domain 10][column 6][core_domain 1] to 0.69 2021-01-24 06:24:35:driver-hash-chip.c:613:recalc_invalid_volt: fix timeout adc_read_back[chain 1][domain 10][column 7][core_domain 0] to 0.35 2021-01-24 06:24:35:driver-hash-chip.c:613:recalc_invalid_volt: fix timeout adc_read_back[chain 1][domain 10][column 7][core_domain 1] to 0.69 2021-01-24 06:24:35:driver-hash-chip.c:613:recalc_invalid_volt: fix timeout adc_read_back[chain 1][domain 10][column 8][core_domain 0] to 0.35 2021-01-24 06:24:35:driver-hash-chip.c:613:recalc_invalid_volt: fix timeout adc_read_back[chain 1][domain 10][column 8][core_domain 1] to 0.70 2021-01-24 06:24:35:driver-hash-chip.c:613:recalc_invalid_volt: fix timeout adc_read_back[chain 1][domain 11][column 0][core_domain 0] to 0.34 2021-01-24 06:24:35:driver-hash-chip.c:613:recalc_invalid_volt: fix timeout adc_read_back[chain 1][domain 11][column 0][core_domain 1] to 0.68 2021-01-24 06:24:35:driver-hash-chip.c:591:recalc_invalid_volt: chain 1 domain 11 column 01 single core_domain: no useful core domain volt: 0.00 0.00 0.00 0.00. 2021-01-24 06:24:35:driver-hash-chip.c:591:recalc_invalid_volt: chain 1 domain 11 column 02 single core_domain: no useful core domain volt: 0.00 0.00 0.00 0.00. 2021-01-24 06:24:35:driver-hash-chip.c:591:recalc_invalid_volt: chain 1 domain 11 column 03 single core_domain: no useful core domain volt: 0.00 0.00 0.00 0.00. 2021-01-24 06:24:35:driver-hash-chip.c:591:recalc_invalid_volt: chain 1 domain 11 column 04 single core_domain: no useful core domain volt: 0.00 0.00 0.00 0.00. 2021-01-24 06:24:35:driver-hash-chip.c:591:recalc_invalid_volt: chain 1 domain 11 column 05 single core_domain: no useful core domain volt: 0.00 0.00 0.00 0.00. 2021-01-24 06:24:35:driver-hash-chip.c:591:recalc_invalid_volt: chain 1 domain 11 column 06 single core_domain: no useful core domain volt: 0.00 0.00 0.00 0.00. 2021-01-24 06:24:35:driver-hash-chip.c:591:recalc_invalid_volt: chain 1 domain 11 column 07 single core_domain: no useful core domain volt: 0.00 0.00 0.00 0.00. 2021-01-24 06:24:35:driver-hash-chip.c:591:recalc_invalid_volt: chain 1 domain 11 column 08 single core_domain: no useful core domain volt: 0.00 0.00 0.00 0.00. 2021-01-24 06:24:35:driver-hash-chip.c:591:recalc_invalid_volt: chain 1 domain 12 column 00 single core_domain: no useful core domain volt: 0.00 0.00 0.00 0.00. 2021-01-24 06:24:35:driver-hash-chip.c:591:recalc_invalid_volt: chain 1 domain 12 column 01 single core_domain: no useful core domain volt: 0.00 0.00 0.00 0.00. 2021-01-24 06:24:35:driver-hash-chip.c:591:recalc_invalid_volt: chain 1 domain 12 column 02 single core_domain: no useful core domain volt: 0.00 0.00 0.00 0.00. 2021-01-24 06:24:35:driver-hash-chip.c:591:recalc_invalid_volt: chain 1 domain 12 column 03 single core_domain: no useful core domain volt: 0.00 0.00 0.00 0.00. 2021-01-24 06:24:35:driver-hash-chip.c:591:recalc_invalid_volt: chain 1 domain 12 column 04 single core_domain: no useful core domain volt: 0.00 0.00 0.00 0.00. 2021-01-24 06:24:35:driver-hash-chip.c:591:recalc_invalid_volt: chain 1 domain 12 column 05 single core_domain: no useful core domain volt: 0.00 0.00 0.00 0.00. 2021-01-24 06:24:35:driver-hash-chip.c:591:recalc_invalid_volt: chain 1 domain 12 column 06 single core_domain: no useful core domain volt: 0.00 0.00 0.00 0.00. 2021-01-24 06:24:35:driver-hash-chip.c:591:recalc_invalid_volt: chain 1 domain 12 column 07 single core_domain: no useful core domain volt: 0.00 0.00 0.00 0.00. 2021-01-24 06:24:35:driver-hash-chip.c:591:recalc_invalid_volt: chain 1 domain 12 column 08 single core_domain: no useful core domain volt: 0.00 0.00 0.00 0.00. 2021-01-24 06:24:35:driver-hash-chip.c:591:recalc_invalid_volt: chain 1 domain 13 column 00 single core_domain: no useful core domain volt: 0.00 0.00 0.00 0.00. 2021-01-24 06:24:35:driver-hash-chip.c:591:recalc_invalid_volt: chain 1 domain 13 column 01 single core_domain: no useful core domain volt: 0.00 0.00 0.00 0.00. 2021-01-24 06:24:35:driver-hash-chip.c:591:recalc_invalid_volt: chain 1 domain 13 column 02 single core_domain: no useful core domain volt: 0.00 0.00 0.00 0.00. 2021-01-24 06:24:35:driver-hash-chip.c:591:recalc_invalid_volt: chain 1 domain 13 column 03 single core_domain: no useful core domain volt: 0.00 0.00 0.00 0.00. 2021-01-24 06:24:35:driver-hash-chip.c:591:recalc_invalid_volt: chain 1 domain 13 column 04 single core_domain: no useful core domain volt: 0.00 0.00 0.00 0.00. 2021-01-24 06:24:35:driver-hash-chip.c:591:recalc_invalid_volt: chain 1 domain 13 column 05 single core_domain: no useful core domain volt: 0.00 0.00 0.00 0.00. 2021-01-24 06:24:35:driver-hash-chip.c:591:recalc_invalid_volt: chain 1 domain 13 column 06 single core_domain: no useful core domain volt: 0.00 0.00 0.00 0.00. 2021-01-24 06:24:35:driver-hash-chip.c:591:recalc_invalid_volt: chain 1 domain 13 column 07 single core_domain: no useful core domain volt: 0.00 0.00 0.00 0.00. 2021-01-24 06:24:35:driver-hash-chip.c:591:recalc_invalid_volt: chain 1 domain 13 column 08 single core_domain: no useful core domain volt: 0.00 0.00 0.00 0.00. 2021-01-24 06:24:35:driver-hash-chip.c:591:recalc_invalid_volt: chain 1 domain 14 column 00 single core_domain: no useful core domain volt: 0.00 0.00 0.00 0.00. 2021-01-24 06:24:35:driver-hash-chip.c:591:recalc_invalid_volt: chain 1 domain 14 column 01 single core_domain: no useful core domain volt: 0.00 0.00 0.00 0.00. 2021-01-24 06:24:35:driver-hash-chip.c:591:recalc_invalid_volt: chain 1 domain 14 column 02 single core_domain: no useful core domain volt: 0.00 0.00 0.00 0.00. 2021-01-24 06:24:35:driver-hash-chip.c:591:recalc_invalid_volt: chain 1 domain 14 column 03 single core_domain: no useful core domain volt: 0.00 0.00 0.00 0.00. 2021-01-24 06:24:35:driver-hash-chip.c:591:recalc_invalid_volt: chain 1 domain 14 column 04 single core_domain: no useful core domain volt: 0.00 0.00 0.00 0.00. 2021-01-24 06:24:35:driver-hash-chip.c:591:recalc_invalid_volt: chain 1 domain 14 column 05 single core_domain: no useful core domain volt: 0.00 0.00 0.00 0.00. 2021-01-24 06:24:35:driver-hash-chip.c:591:recalc_invalid_volt: chain 1 domain 14 column 06 single core_domain: no useful core domain volt: 0.00 0.00 0.00 0.00. 2021-01-24 06:24:35:driver-hash-chip.c:591:recalc_invalid_volt: chain 1 domain 14 column 07 single core_domain: no useful core domain volt: 0.00 0.00 0.00 0.00. 2021-01-24 06:24:35:driver-hash-chip.c:591:recalc_invalid_volt: chain 1 domain 14 column 08 single core_domain: no useful core domain volt: 0.00 0.00 0.00 0.00. 2021-01-24 06:24:35:driver-hash-chip.c:707:dump_adc_voltage_v2: chain 1 domain 12 core_domain 0: all asic timeout or overrange. 2021-01-24 06:24:35:driver-hash-chip.c:707:dump_adc_voltage_v2: chain 1 domain 12 core_domain 1: all asic timeout or overrange. 2021-01-24 06:24:35:driver-hash-chip.c:707:dump_adc_voltage_v2: chain 1 domain 12 core_domain 2: all asic timeout or overrange. 2021-01-24 06:24:35:driver-hash-chip.c:707:dump_adc_voltage_v2: chain 1 domain 12 core_domain 3: all asic timeout or overrange. 2021-01-24 06:24:35:driver-hash-chip.c:707:dump_adc_voltage_v2: chain 1 domain 13 core_domain 0: all asic timeout or overrange. 2021-01-24 06:24:35:driver-hash-chip.c:707:dump_adc_voltage_v2: chain 1 domain 13 core_domain 1: all asic timeout or overrange. 2021-01-24 06:24:35:driver-hash-chip.c:707:dump_adc_voltage_v2: chain 1 domain 13 core_domain 2: all asic timeout or overrange. 2021-01-24 06:24:35:driver-hash-chip.c:707:dump_adc_voltage_v2: chain 1 domain 13 core_domain 3: all asic timeout or overrange. 2021-01-24 06:24:35:driver-hash-chip.c:707:dump_adc_voltage_v2: chain 1 domain 14 core_domain 0: all asic timeout or overrange. 2021-01-24 06:24:35:driver-hash-chip.c:707:dump_adc_voltage_v2: chain 1 domain 14 core_domain 1: all asic timeout or overrange. 2021-01-24 06:24:35:driver-hash-chip.c:707:dump_adc_voltage_v2: chain 1 domain 14 core_domain 2: all asic timeout or overrange. 2021-01-24 06:24:35:driver-hash-chip.c:707:dump_adc_voltage_v2: chain 1 domain 14 core_domain 3: all asic timeout or overrange. 2021-01-24 06:24:35:driver-hash-chip.c:737:dump_adc_voltage_v2: get ADC_DATAOUT from chain 1 with 140 regs timeout. chain 1 domain 0: d0 0.331, d1 0.331, d2 0.329, d3 0.335, sum = 1.326416 chain 1 domain 1: d0 0.325, d1 0.323, d2 0.327, d3 0.327, sum = 1.302572 chain 1 domain 2: d0 0.326, d1 0.326, d2 0.320, d3 0.305, sum = 1.277303 chain 1 domain 3: d0 0.334, d1 0.330, d2 0.331, d3 0.332, sum = 1.326497 chain 1 domain 4: d0 0.331, d1 0.330, d2 0.332, d3 0.336, sum = 1.328735 chain 1 domain 5: d0 0.327, d1 0.327, d2 0.331, d3 0.331, sum = 1.315267 chain 1 domain 6: d0 0.319, d1 0.317, d2 0.317, d3 0.318, sum = 1.270711 chain 1 domain 7: d0 0.321, d1 0.318, d2 0.320, d3 0.320, sum = 1.279012 chain 1 domain 8: d0 0.329, d1 0.328, d2 0.328, d3 0.335, sum = 1.320882 chain 1 domain 9: d0 0.326, d1 0.322, d2 0.328, d3 0.329, sum = 1.305868 chain 1 domain 10: d0 0.347, d1 0.347, d2 0.345, d3 0.348, sum = 1.387166 chain 1 domain 11: d0 0.338, d1 0.339, d2 0.337, d3 0.340, sum = 1.354614 chain 1 domain 12: x d0 0.000, x d1 0.000, x d2 0.000, x d3 0.000, x sum = 0.000000 chain 1 domain 13: x d0 0.000, x d1 0.000, x d2 0.000, x d3 0.000, x sum = 0.000000 chain 1 domain 14: x d0 0.000, x d1 0.000, x d2 0.000, x d3 0.000, x sum = 0.000000 2021-01-24 06:24:35:driver-hash-chip.c:486:check_adc_voltage: FAIL domain volt check: chain 1 domain 12 volt 0.000 less then request 0.800 (index 0) 2021-01-24 06:24:35:driver-hash-chip.c:486:check_adc_voltage: FAIL domain volt check: chain 1 domain 13 volt 0.000 less then request 0.800 (index 0) 2021-01-24 06:24:35:driver-hash-chip.c:486:check_adc_voltage: FAIL domain volt check: chain 1 domain 14 volt 0.000 less then request 0.800 (index 0) 2021-01-24 06:24:35:driver-btm-api.c:2379:bitmain_board_init: FAULT: check_asic_number_until_volt_balance PASS but bitmain_board_config_init FAIL!!! 2021-01-24 06:24:36:driver-btm-api.c:247:set_miner_status: ERROR_SOC_INIT 2021-01-24 06:24:36:driver-btm-api.c:176:stop_mining: stop mining: soc init failed! 2021-01-24 06:24:36:thread.c:1595:cancel_read_nonce_reg_thread: cancel thread 2021-01-24 06:24:36:driver-btm-api.c:147:killall_hashboard: ****power off hashboard****
What do you think? At the end there is again issues with volt check and the last line says power off dashboard. On a side note, BinancePool sucks (https://bitcointalk.org/index.php?topic=5271427.0).
I read that, good to know! I might consider other pools.
And I rebooted once again and I think it is looking same. 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: 195680K/245760K available (6345K kernel code, 231K rwdata, 1896K rodata, 1024K init, 223K bss, 33696K 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: 20656K (cc6d4000 - cdb00000) 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 nand_read_bbt: bad block at 0x000000c00000 nand_read_bbt: bad block at 0x000006800000 nand_read_bbt: bad block at 0x00000da00000 nand_read_bbt: bad block at 0x00000dc00000 nand_read_bbt: bad block at 0x00000dcc0000 nand_read_bbt: bad block at 0x00000f840000 nand_read_bbt: bad block at 0x00000f900000 nand_read_bbt: bad block at 0x00000fac0000 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: 9/4, 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: 1014, bad PEBs: 10, corrupted PEBs: 0 ubi1: user volume: 1, internal volumes: 1, max. volumes count: 128 ubi1: max/mean erase counter: 648/147, WL threshold: 4096, image sequence number: 614900815 ubi1: available PEBs: 0, total reserved PEBs: 1014, PEBs reserved for bad PEB handling: 30 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-01-24 07:07:00:thread.c:1555:create_bitmain_soc_init_thread: create thread 2021-01-24 07:07:00:driver-btm-api.c:682:init_freq_mode: This is scan-user version 2021-01-24 07:07:00:driver-btm-api.c:2518:bitmain_soc_init: Miner compile time: Thu Oct 22 07:33:06 CST 2020 type: Antminer S17e 2021-01-24 07:07:00:driver-btm-api.c:2519:bitmain_soc_init: commit version: 037ddcd 2020-10-21 22:42:21, build by: jenkins 2020-10-22 07:37:50 2021-01-24 07:07:00:driver-btm-api.c:2520:bitmain_soc_init: opt_multi_version = 1 2021-01-24 07:07:00:driver-btm-api.c:2521:bitmain_soc_init: opt_bitmain_ab = 1 2021-01-24 07:07:00:driver-btm-api.c:2522:bitmain_soc_init: mid_auto_gen = 0 2021-01-24 07:07:00:driver-btm-api.c:2523:bitmain_soc_init: work_mode = 0 2021-01-24 07:07:00:driver-btm-api.c:2524:bitmain_soc_init: power_feedback_en = true 2021-01-24 07:07:00:driver-btm-api.c:2067:show_sn: no SN got, please write SN to /config/sn 2021-01-24 07:07:00:driver-btm-api.c:1384:miner_device_init: Detect 256MB control board of XILINX 2021-01-24 07:07:00:driver-btm-api.c:1325:init_fan_parameter: fan_eft : 0 fan_pwm : 0 2021-01-24 07:07:06:driver-btm-api.c:1309:init_miner_version: miner ID : 81742c4815408854 2021-01-24 07:07:06:driver-btm-api.c:1315:init_miner_version: FPGA Version = 0xB023 2021-01-24 07:07:08:auto_adapt.c:100:_get_board_info: chain[1] board bin: 1, chip bin: 1, chip ft: A4V2, chip version: AB 2021-01-24 07:07:08:driver-btm-api.c:2164:get_calibration_voltage: calibration voltage flag is error data. 2021-01-24 07:07:08 voltage[1] = 1850 2021-01-24 07:07:08:auto_adapt.c:273:is_sweep_failed_before: open sweep tag failed voltage_ref = 0 2100 2100 2100 2100 2100 2000 1980 1980 1950 1950 1980 1950 1950 1920 1920 1950 1950 1920 1900 1900 1950 1920 1900 1880 1880
2021-01-24 07:07:08:thread.c:1523:create_read_nonce_reg_thread: create thread 2021-01-24 07:07:08:driver-btm-api.c:698:dump_pcb_bom_version: Chain [1] PCB Version: 0x0128 2021-01-24 07:07:08:driver-btm-api.c:699:dump_pcb_bom_version: Chain [1] BOM Version: 0x0100 2021-01-24 07:07:15:driver-btm-api.c:2344:bitmain_board_init: Fan check passed. 2021-01-24 07:07:16:board.c:81:jump_and_app_check_restore_pic: chain[1] PIC jump to app 2021-01-24 07:07:18:board.c:94:jump_and_app_check_restore_pic: Check chain[1] PIC fw version=0xb9 2021-01-24 07:07:18:thread.c:1518:create_pic_heart_beat_thread: create thread 2021-01-24 07:07:19:power_api.c:241:power_init: power type version: 0x0042 2021-01-24 07:07:21:power_api.c:259:power_init: Power init: 2021-01-24 07:07:21:power_api.c:260:power_init: current_voltage_raw = 2002 2021-01-24 07:07:21:power_api.c:261:power_init: highest_voltage_raw = 2000 2021-01-24 07:07:21:power_api.c:262:power_init: working_voltage_raw = 1800 2021-01-24 07:07:21:power_api.c:263:power_init: higher_voltage_raw = 1850 2021-01-24 07:07:21:power_api.c:264:power_init: check_asic_voltage_raw = 1800 2021-01-24 07:07:21:driver-btm-api.c:2354:bitmain_board_init: Enter 60s sleep to make sure power release finish. 2021-01-24 07:08:23:driver-btm-api.c:1123:check_asic_number_until_volt_balance: THIS is No.1 time boost asic: 2021-01-24 07:08:23:power_api.c:334:modify_check_asic_voltage: check_asic_voltage_raw = 1800 2021-01-24 07:08:26:power_api.c:298:set_to_check_asic_voltage_by_steps: Set to voltage raw 1800, step by step. 2021-01-24 07:08:40:uart.c:69:set_baud: set UART baud to 115200 chain 1, IO_DRIVE_STRENGTH_CONFIGURATION reg = 0x 7777777 2021-01-24 07:08:45:driver-btm-api.c:1035:check_asic_number_with_power_on: Chain[1]: find 135 asic, times 0 2021-01-24 07:08:45:driver-btm-api.c:1163:check_asic_number_until_volt_balance: PASS: volt balance at No.1 time boost asic. 2021-01-24 07:08:45:power_api.c:364:set_to_highest_voltage_by_steps: Set to voltage raw 2000, step by step. 2021-01-24 07:09:07:driver-hash-chip.c:876:set_uart_relay: set uart relay to 0x390003 2021-01-24 07:09:07:driver-hash-chip.c:1264:set_ldo_ctrl: Set LDO to 0x2000203 2021-01-24 07:09:07:driver-hash-chip.c:591:recalc_invalid_volt: chain 1 domain 10 column 01 single core_domain: no useful core domain volt: 0.00 0.00 0.00 0.00. 2021-01-24 07:09:07:driver-hash-chip.c:591:recalc_invalid_volt: chain 1 domain 10 column 02 single core_domain: no useful core domain volt: 0.00 0.00 0.00 0.00. 2021-01-24 07:09:07:driver-hash-chip.c:591:recalc_invalid_volt: chain 1 domain 10 column 03 single core_domain: no useful core domain volt: 0.00 0.00 0.00 0.00. 2021-01-24 07:09:07:driver-hash-chip.c:591:recalc_invalid_volt: chain 1 domain 10 column 04 single core_domain: no useful core domain volt: 0.00 0.00 0.00 0.00. 2021-01-24 07:09:07:driver-hash-chip.c:591:recalc_invalid_volt: chain 1 domain 10 column 05 single core_domain: no useful core domain volt: 0.00 0.00 0.00 0.00. 2021-01-24 07:09:07:driver-hash-chip.c:591:recalc_invalid_volt: chain 1 domain 10 column 06 single core_domain: no useful core domain volt: 0.00 0.00 0.00 0.00. 2021-01-24 07:09:07:driver-hash-chip.c:591:recalc_invalid_volt: chain 1 domain 10 column 07 single core_domain: no useful core domain volt: 0.00 0.00 0.00 0.00. 2021-01-24 07:09:07:driver-hash-chip.c:591:recalc_invalid_volt: chain 1 domain 10 column 08 single core_domain: no useful core domain volt: 0.00 0.00 0.00 0.00. 2021-01-24 07:09:07:driver-hash-chip.c:591:recalc_invalid_volt: chain 1 domain 11 column 00 single core_domain: no useful core domain volt: 0.00 0.00 0.00 0.00. 2021-01-24 07:09:07:driver-hash-chip.c:591:recalc_invalid_volt: chain 1 domain 11 column 01 single core_domain: no useful core domain volt: 0.00 0.00 0.00 0.00. 2021-01-24 07:09:07:driver-hash-chip.c:591:recalc_invalid_volt: chain 1 domain 11 column 02 single core_domain: no useful core domain volt: 0.00 0.00 0.00 0.00. 2021-01-24 07:09:07:driver-hash-chip.c:591:recalc_invalid_volt: chain 1 domain 11 column 03 single core_domain: no useful core domain volt: 0.00 0.00 0.00 0.00. 2021-01-24 07:09:07:driver-hash-chip.c:591:recalc_invalid_volt: chain 1 domain 11 column 04 single core_domain: no useful core domain volt: 0.00 0.00 0.00 0.00. 2021-01-24 07:09:07:driver-hash-chip.c:591:recalc_invalid_volt: chain 1 domain 11 column 05 single core_domain: no useful core domain volt: 0.00 0.00 0.00 0.00. 2021-01-24 07:09:07:driver-hash-chip.c:591:recalc_invalid_volt: chain 1 domain 11 column 06 single core_domain: no useful core domain volt: 0.00 0.00 0.00 0.00. 2021-01-24 07:09:07:driver-hash-chip.c:591:recalc_invalid_volt: chain 1 domain 11 column 07 single core_domain: no useful core domain volt: 0.00 0.00 0.00 0.00. 2021-01-24 07:09:07:driver-hash-chip.c:591:recalc_invalid_volt: chain 1 domain 11 column 08 single core_domain: no useful core domain volt: 0.00 0.00 0.00 0.00. 2021-01-24 07:09:07:driver-hash-chip.c:591:recalc_invalid_volt: chain 1 domain 12 column 00 single core_domain: no useful core domain volt: 0.00 0.00 0.00 0.00. 2021-01-24 07:09:07:driver-hash-chip.c:591:recalc_invalid_volt: chain 1 domain 12 column 01 single core_domain: no useful core domain volt: 0.00 0.00 0.00 0.00. 2021-01-24 07:09:07:driver-hash-chip.c:591:recalc_invalid_volt: chain 1 domain 12 column 02 single core_domain: no useful core domain volt: 0.00 0.00 0.00 0.00. 2021-01-24 07:09:07:driver-hash-chip.c:591:recalc_invalid_volt: chain 1 domain 12 column 03 single core_domain: no useful core domain volt: 0.00 0.00 0.00 0.00. 2021-01-24 07:09:07:driver-hash-chip.c:591:recalc_invalid_volt: chain 1 domain 12 column 04 single core_domain: no useful core domain volt: 0.00 0.00 0.00 0.00. 2021-01-24 07:09:07:driver-hash-chip.c:591:recalc_invalid_volt: chain 1 domain 12 column 05 single core_domain: no useful core domain volt: 0.00 0.00 0.00 0.00. 2021-01-24 07:09:07:driver-hash-chip.c:591:recalc_invalid_volt: chain 1 domain 12 column 06 single core_domain: no useful core domain volt: 0.00 0.00 0.00 0.00. 2021-01-24 07:09:07:driver-hash-chip.c:591:recalc_invalid_volt: chain 1 domain 12 column 07 single core_domain: no useful core domain volt: 0.00 0.00 0.00 0.00. 2021-01-24 07:09:07:driver-hash-chip.c:591:recalc_invalid_volt: chain 1 domain 12 column 08 single core_domain: no useful core domain volt: 0.00 0.00 0.00 0.00. 2021-01-24 07:09:07:driver-hash-chip.c:591:recalc_invalid_volt: chain 1 domain 13 column 00 single core_domain: no useful core domain volt: 0.00 0.00 0.00 0.00. 2021-01-24 07:09:07:driver-hash-chip.c:591:recalc_invalid_volt: chain 1 domain 13 column 01 single core_domain: no useful core domain volt: 0.00 0.00 0.00 0.00. 2021-01-24 07:09:07:driver-hash-chip.c:591:recalc_invalid_volt: chain 1 domain 13 column 02 single core_domain: no useful core domain volt: 0.00 0.00 0.00 0.00. 2021-01-24 07:09:07:driver-hash-chip.c:591:recalc_invalid_volt: chain 1 domain 13 column 03 single core_domain: no useful core domain volt: 0.00 0.00 0.00 0.00. 2021-01-24 07:09:07:driver-hash-chip.c:591:recalc_invalid_volt: chain 1 domain 13 column 04 single core_domain: no useful core domain volt: 0.00 0.00 0.00 0.00. 2021-01-24 07:09:07:driver-hash-chip.c:591:recalc_invalid_volt: chain 1 domain 13 column 05 single core_domain: no useful core domain volt: 0.00 0.00 0.00 0.00. 2021-01-24 07:09:07:driver-hash-chip.c:591:recalc_invalid_volt: chain 1 domain 13 column 06 single core_domain: no useful core domain volt: 0.00 0.00 0.00 0.00. 2021-01-24 07:09:07:driver-hash-chip.c:591:recalc_invalid_volt: chain 1 domain 13 column 07 single core_domain: no useful core domain volt: 0.00 0.00 0.00 0.00. 2021-01-24 07:09:07:driver-hash-chip.c:591:recalc_invalid_volt: chain 1 domain 13 column 08 single core_domain: no useful core domain volt: 0.00 0.00 0.00 0.00. 2021-01-24 07:09:07:driver-hash-chip.c:591:recalc_invalid_volt: chain 1 domain 14 column 00 single core_domain: no useful core domain volt: 0.00 0.00 0.00 0.00. 2021-01-24 07:09:07:driver-hash-chip.c:591:recalc_invalid_volt: chain 1 domain 14 column 01 single core_domain: no useful core domain volt: 0.00 0.00 0.00 0.00. 2021-01-24 07:09:07:driver-hash-chip.c:591:recalc_invalid_volt: chain 1 domain 14 column 02 single core_domain: no useful core domain volt: 0.00 0.00 0.00 0.00. 2021-01-24 07:09:07:driver-hash-chip.c:591:recalc_invalid_volt: chain 1 domain 14 column 03 single core_domain: no useful core domain volt: 0.00 0.00 0.00 0.00. 2021-01-24 07:09:07:driver-hash-chip.c:591:recalc_invalid_volt: chain 1 domain 14 column 04 single core_domain: no useful core domain volt: 0.00 0.00 0.00 0.00. 2021-01-24 07:09:07:driver-hash-chip.c:591:recalc_invalid_volt: chain 1 domain 14 column 05 single core_domain: no useful core domain volt: 0.00 0.00 0.00 0.00. 2021-01-24 07:09:07:driver-hash-chip.c:591:recalc_invalid_volt: chain 1 domain 14 column 06 single core_domain: no useful core domain volt: 0.00 0.00 0.00 0.00. 2021-01-24 07:09:07:driver-hash-chip.c:591:recalc_invalid_volt: chain 1 domain 14 column 07 single core_domain: no useful core domain volt: 0.00 0.00 0.00 0.00. 2021-01-24 07:09:07:driver-hash-chip.c:591:recalc_invalid_volt: chain 1 domain 14 column 08 single core_domain: no useful core domain volt: 0.00 0.00 0.00 0.00. 2021-01-24 07:09:07:driver-hash-chip.c:707:dump_adc_voltage_v2: chain 1 domain 11 core_domain 0: all asic timeout or overrange. 2021-01-24 07:09:07:driver-hash-chip.c:707:dump_adc_voltage_v2: chain 1 domain 11 core_domain 1: all asic timeout or overrange. 2021-01-24 07:09:07:driver-hash-chip.c:707:dump_adc_voltage_v2: chain 1 domain 11 core_domain 2: all asic timeout or overrange. 2021-01-24 07:09:07:driver-hash-chip.c:707:dump_adc_voltage_v2: chain 1 domain 11 core_domain 3: all asic timeout or overrange. 2021-01-24 07:09:07:driver-hash-chip.c:707:dump_adc_voltage_v2: chain 1 domain 12 core_domain 0: all asic timeout or overrange. 2021-01-24 07:09:07:driver-hash-chip.c:707:dump_adc_voltage_v2: chain 1 domain 12 core_domain 1: all asic timeout or overrange. 2021-01-24 07:09:07:driver-hash-chip.c:707:dump_adc_voltage_v2: chain 1 domain 12 core_domain 2: all asic timeout or overrange. 2021-01-24 07:09:07:driver-hash-chip.c:707:dump_adc_voltage_v2: chain 1 domain 12 core_domain 3: all asic timeout or overrange. 2021-01-24 07:09:07:driver-hash-chip.c:707:dump_adc_voltage_v2: chain 1 domain 13 core_domain 0: all asic timeout or overrange. 2021-01-24 07:09:07:driver-hash-chip.c:707:dump_adc_voltage_v2: chain 1 domain 13 core_domain 1: all asic timeout or overrange. 2021-01-24 07:09:07:driver-hash-chip.c:707:dump_adc_voltage_v2: chain 1 domain 13 core_domain 2: all asic timeout or overrange. 2021-01-24 07:09:07:driver-hash-chip.c:707:dump_adc_voltage_v2: chain 1 domain 13 core_domain 3: all asic timeout or overrange. 2021-01-24 07:09:07:driver-hash-chip.c:707:dump_adc_voltage_v2: chain 1 domain 14 core_domain 0: all asic timeout or overrange. 2021-01-24 07:09:07:driver-hash-chip.c:707:dump_adc_voltage_v2: chain 1 domain 14 core_domain 1: all asic timeout or overrange. 2021-01-24 07:09:07:driver-hash-chip.c:707:dump_adc_voltage_v2: chain 1 domain 14 core_domain 2: all asic timeout or overrange. 2021-01-24 07:09:07:driver-hash-chip.c:707:dump_adc_voltage_v2: chain 1 domain 14 core_domain 3: all asic timeout or overrange. 2021-01-24 07:09:07:driver-hash-chip.c:737:dump_adc_voltage_v2: get ADC_DATAOUT from chain 1 with 176 regs timeout. chain 1 domain 0: d0 0.336, d1 0.336, d2 0.334, d3 0.339, sum = 1.344604 chain 1 domain 1: d0 0.329, d1 0.327, d2 0.329, d3 0.330, sum = 1.314616 chain 1 domain 2: d0 0.328, d1 0.328, d2 0.325, d3 0.305, sum = 1.285807 chain 1 domain 3: d0 0.338, d1 0.334, d2 0.336, d3 0.337, sum = 1.345093 chain 1 domain 4: d0 0.337, d1 0.336, d2 0.338, d3 0.342, sum = 1.351847 chain 1 domain 5: d0 0.332, d1 0.332, d2 0.334, d3 0.335, sum = 1.332520 chain 1 domain 6: d0 0.320, d1 0.319, d2 0.319, d3 0.319, sum = 1.277832 chain 1 domain 7: d0 0.320, d1 0.317, d2 0.319, d3 0.319, sum = 1.274211 chain 1 domain 8: d0 0.327, d1 0.325, d2 0.327, d3 0.332, sum = 1.310140 chain 1 domain 9: d0 0.323, d1 0.319, d2 0.324, d3 0.325, sum = 1.291870 chain 1 domain 10: d0 0.342, d1 0.344, d2 0.341, d3 0.342, sum = 1.369263 chain 1 domain 11: x d0 0.000, x d1 0.000, x d2 0.000, x d3 0.000, x sum = 0.000000 chain 1 domain 12: x d0 0.000, x d1 0.000, x d2 0.000, x d3 0.000, x sum = 0.000000 chain 1 domain 13: x d0 0.000, x d1 0.000, x d2 0.000, x d3 0.000, x sum = 0.000000 chain 1 domain 14: x d0 0.000, x d1 0.000, x d2 0.000, x d3 0.000, x sum = 0.000000 2021-01-24 07:09:07:driver-hash-chip.c:486:check_adc_voltage: FAIL domain volt check: chain 1 domain 11 volt 0.000 less then request 0.800 (index 0) 2021-01-24 07:09:07:driver-hash-chip.c:486:check_adc_voltage: FAIL domain volt check: chain 1 domain 12 volt 0.000 less then request 0.800 (index 0) 2021-01-24 07:09:07:driver-hash-chip.c:486:check_adc_voltage: FAIL domain volt check: chain 1 domain 13 volt 0.000 less then request 0.800 (index 0) 2021-01-24 07:09:07:driver-hash-chip.c:486:check_adc_voltage: FAIL domain volt check: chain 1 domain 14 volt 0.000 less then request 0.800 (index 0) 2021-01-24 07:09:07:driver-btm-api.c:2379:bitmain_board_init: FAULT: check_asic_number_until_volt_balance PASS but bitmain_board_config_init FAIL!!! 2021-01-24 07:09:08:driver-btm-api.c:247:set_miner_status: ERROR_SOC_INIT 2021-01-24 07:09:08:driver-btm-api.c:176:stop_mining: stop mining: soc init failed! 2021-01-24 07:09:08:thread.c:1595:cancel_read_nonce_reg_thread: cancel thread 2021-01-24 07:09:08:driver-btm-api.c:147:killall_hashboard: ****power off hashboard****
Is it PSU? Now it says socket connect failed and no stats at all https://www.imgpaste.net/image/jvOQi.
Title: Re: Antminer S17e's strange problem
Post by: favebook on January 25, 2021, 02:03:26 AM
I would prefer this to be moved to Mining support (https://bitcointalk.org/index.php?board=40.0) but as you are mining BSV, this might be correct board.
There could be four things wrong with that unit. 1st - hashboard is defective (chips are being read which means that part of it is working fine; at least you know that loose heatsink is not your problem like in other X17 miners). 2nd - that hashboard is overheating and it is turning itself off to protect itself. 3rd - one of four tempsensors failed and it is turning itself off again to protect itself from overheating. 4th - PSU is acting up - try another one if you have. Or try running only one hashboard at a time to see if it will work (also try different connections on PSU as well as on control board so you can rule out things one by one).
Firstly, I'd advise you not to mine BSV but rather switch to BTC as mining profit is better and BTC has much brighter future imho. Secondly, try updating firmware (from official bitmain website) or try custom firmware like asic.to (WHEN and IF they release firmware for S17e) or Thierry's (https://bitcointalk.org/index.php?topic=5265677.0) which I personally reviewed and tested on my S17e.
Title: Re: Antminer S17e's strange problem
Post by: philipma1957 on January 25, 2021, 02:54:54 AM
It looks like the psu has 1 dead feed.
Since I have not looked at that particular miner my guess is you had a dead board and not a dead feeder.
So physically pull the two good boards out of the case and lay them on a static guard.
You should now have just the dead board. fire the gear up and see if the dead board works.
move the board over a slot test again.
move the board over test again.
Since I am 90% sure the board is dead it should not work in any of the three slots.
If so place the board to the side and take the two good boards hook them up
good----empty---good board---slot------board
and ask for a 33% refund offer to send the dead board back.
Good luck.
Title: Re: Antminer S17e's strange problem
Post by: jonaeljoni on January 25, 2021, 12:17:33 PM
I unplugged those two boards and tried that faulty one only. It doesn't work at all. Luckily the shop where this has bought from provides two years warranty. So they will send repair ticket for me. Now I am little bit nervous since I have opened that miner. Maybe I have to rely on that they won't notice it.
Title: Re: Antminer S17e's strange problem
Post by: favebook on January 25, 2021, 12:59:37 PM
I unplugged those two boards and tried that faulty one only. It doesn't work at all. Luckily the shop where this has bought from provides two years warranty. So they will send repair ticket for me. Now I am little bit nervous since I have opened that miner. Maybe I have to rely on that they won't notice it.
Have you tried moving that hashboard in place of one of those that you removed? It could still be that PSU connector is defective and not hashboard itself - even though I still suspect that hashboard is bad. No need to be nervous, just put everything back in order it was and there is no way they can know you were opening it. And even if they do notice it (by some sort of magic), there are no more "warranty void" stickers on Antminers, so you shouldn't worry about it. When I was contacting Bitmain support to troubleshoot a few of my miners, they even told me to open it and try different things there before RMA-ing it and they even wanted me to take pictures and videos of hashboards after removing them from the unit so they could visually inspect them.
Title: Re: Antminer S17e's strange problem
Post by: jonaeljoni on January 25, 2021, 01:24:41 PM
Ahh okay, I think they won't recognize I have opened metal covers. I changed places between hashboards but no results. The same issue occurs. Only chains number exchanges. And with only that faulty hashboard it doesn't work at all. It doesn't matter which slot it is connected, it doesn't work. I am now almost sure the hashboard is broken somehow. Your 90% guess is increasing to 99% as far as I'm concerned. There is on the top kernel log about that. From Bitmain they sent instructions like these: Dear Joni Björklund,
Thanks for your consultation!
please try to exclude the issues by the below instructions
1.check the wires for the hashboard--pull them and re-plug them again, and also you can try to change the new wires 2.upgrade to the latest firmware 3. change the PSU to try it and reset the miner to the factory settings 4.flash the SD card program to recover the control board Please download the SD card file in the below link https://service.bitmain.com/support/download?product=Flashing%20SD%20card%20with%20image
instructions: https://support.bitmain.com/hc/en-us/articles/360033757513-S17-S17Pro-S9-SE-S9k-Z11-control-board-program-recovery-SD-card-flashing-with-customized-PW-
Please let us know if you have additional questions or concerns
I don't have another PSU so I can't accomplish step 3 I ordered SD card (under 16GB), so step 4 might be one thing to do. The shop where this has been ordered from is located in Netherlands. I think it will take few weeks all together: shipping it to there, maintenance and repair time + shipping back to Finland. :-[
Title: Re: Antminer S17e's strange problem
Post by: favebook on January 25, 2021, 01:39:05 PM
Ahh okay, I think they won't recognize I have opened metal covers.
I changed places between hashboards but no results. The same issue occurs. Only chains number exchanges. And with only that faulty hashboard it doesn't work at all. It doesn't matter which slot it is connected, it doesn't work.
I am now almost sure the hashboard is broken somehow. Your 90% guess is increasing to 99% as far as I'm concerned.
Yeah, that hashboard is bonkers. You could try with different PSU if you have any friend or know someone who has antminers near you, but I doubt that will do anything. Trying custom firmware MIGHT fix your problem TEMPORARILY but best thing you can do is RMA it if they can provide you with another in short time frame, but be careful with additional tariffs here too. Otherwise I'd keep mining on those 2/3 hashboards and ask for partial refund if possible.
Title: Re: Antminer S17e's strange problem
Post by: jonaeljoni on January 25, 2021, 05:45:20 PM
Am I right this miner's power consumption is roughly 2/3 from original (2880w). So something around 2000w? Or is the PSU still taking the whole amount?
Or is this obvious?
Title: Re: Antminer S17e's strange problem
Post by: NotFuzzyWarm on January 25, 2021, 05:54:25 PM
It should be obvious: The miner only draws from the PSU what the hash boards, fans and controller need. If nothing is connected to a PSU it will only pull a very few watts from the wall. Dropping 1 hash board out of 3 means roughly 1/3 less power used.
Title: Re: Antminer S17e's strange problem
Post by: jonaeljoni on January 25, 2021, 05:56:45 PM
Okay, just had to be sure. Thanks for information
Title: Re: Antminer S17e's strange problem
Post by: mikeywith on January 25, 2021, 07:12:10 PM
It should be obvious: The miner only draws from the PSU what the hash boards, fans and controller need. If nothing is connected to a PSU it will only pull a very few watts from the wall. Dropping 1 hash board out of 3 means roughly 1/3 less power used.
True, it's worth mentioning that these PSUs are different from the old APW3/APW7, with the old models you could easily check the voltage at the 6 pin cables, the APW9 and APW9s need to have some sort of load to give you that 18-19v reading, so if it's not attached to a miner, you can't really test it, I also noticed that once you the power miner on it will read the normal voltage of 18-19v and then drops for a while, so taking the voltage readings isn't all that simple. From Bitmain they sent instructions like these:
Don't listen to bitmain, I can tell you with certainty that members in this form are more capable of troubleshooting these miners than Bitmain's support, I don't claim we are better than their tech guys, but without a doubt, we are a few years ahead of their support team, I mean look at all the silly things they asked you to try 2.upgrade to the latest firmware
If you do this, your miner will be locked forever, I doubt that guys in Vnish team have figured out a way to break that latest firmware signature, so by doing this you can't even roll-back to previous bitmain firmware, and if for whatever reason the miner doesn't like the latest firmware, you will have to buy a new control board, this indeed is very stupid advice coming from Bitmain. 3. change the PSU
Since you changed the bad hash board location and the problem follows that hashboard then it can't be a PSU issue anymore, if you disconnect 2 hash boards and the bad one works, then yes that is most likely a PSU issue, but for your case, it's a dead hash board, refer to this topic (https://bitcointalk.org/index.php?topic=5217949.0l)for tips and tricks, chances are slim but you lose nothing if you try.
Title: Re: Antminer S17e's strange problem
Post by: jonaeljoni on January 26, 2021, 02:02:02 PM
I received a repair ticket. BUT it is from Bitmain. I think it will be sent to Bitmain for repair. If it's going to China I think shipping period might be like 1-2 months back and forth ??? :o Plus repairing time there. Should I send it or what? In a long term, this might be the best solution? I found information about repairing. There two options. Apply for repair and apply for parts. I will try if Bitmain somehow accepts hashboard's shipping only. this type of repair ticket is on case-by-case basis, and is treated as valid only when instructed to create by us.
Please write in to us describing the problems with the defective parts, SN of the miner and order ID of the miner. We will need these details review and approve your request.
Always support your problems with screenshots or photos of the defects.
Title: Re: Antminer S17e's strange problem
Post by: favebook on January 27, 2021, 02:02:50 AM
They will not accept your "apply for parts". All newer models must be sent as a whole unit. Depending on where are you from, shipping might or might not take that long.
There are multiple repair sites around world, not exactly sure if any are open now tho. Netherlands one was closed during outbreak of COVID and I am not sure if they have reopened it.
Long term your best solution might be to mine with working two hashboards until one of those breaks or whole unit stops mining and then RMA it.
Repair should cost between 50 and 100 USD and it usually takes day or two for it as they do not actually repair your unit, they just ship you a different one.
Your biggest problem is shipping time and taxes (if there are any).
Title: Re: Antminer S17e's strange problem
Post by: jonaeljoni on January 27, 2021, 08:06:09 AM
Okay, I checked a tax concern from customs and they said if it will be a warranty repair with no costs, there won't be any additional taxes. If I have to pay for shipping, I have to pay VAT only contributing those shipping costs. A shipment will be sent from Finland. I am not aware of do I have to pay for shipping costs back and forth. Or is it included for warranty? I will of course ask this from the shop which are responsible for this warranty. I think this is very intricate if you have problems with antminers. EDIT: I asked details about shipping costs. The return costs from repair center to you is paid by BITMAIN. I think what I have to pay is for shipping to China. Is it that 50 to 100USD what you mentioned?
Title: Re: Antminer S17e's strange problem
Post by: favebook on January 27, 2021, 11:35:44 AM
Okay, I checked a tax concern from customs and they said if it will be a warranty repair with no costs, there won't be any additional taxes. If I have to pay for shipping, I have to pay VAT only contributing those shipping costs. A shipment will be sent from Finland. I am not aware of do I have to pay for shipping costs back and forth. Or is it included for warranty? I will of course ask this from the shop which are responsible for this warranty. I think this is very intricate if you have problems with antminers. EDIT: I asked details about shipping costs. The return costs from repair center to you is paid by BITMAIN. I think what I have to pay is for shipping to China. Is it that 50 to 100USD what you mentioned? Yes, Bitmain always pays the shipping to you, but you have to pay shipping to them. No, 50-100USD is for repair. I am not sure how much shipping would cost. But I wouldn't count on less than 200 USD for that weight.
Title: Re: Antminer S17e's strange problem
Post by: jonaeljoni on January 27, 2021, 11:47:20 AM
Okay, I checked that from DHL for example. It is something like 200 euros. Weird warranty policy since normally here in Finland we don't have to pay any costs if something is under warranty. It is not customers responsibility to pay.
So at least I suppose the repairing cost goes to that shop where this has been bought from.
This is surreal situation from Finnish citizen's respect. We don't have any policies like that. First you buy some product, you get some warranty, after that it goes broken and finally you pay more ???
If told this to anyone in Finland they would be so overwhelmed and confused. But this is some Bitmain's sick and twisted conspiracy. I have read their policies in general.
Title: Re: Antminer S17e's strange problem
Post by: jonaeljoni on January 27, 2021, 12:07:50 PM
I updated costs via finnish postal service. It's only 70 euros for normal shipping and shipping time 6 to 14 work days. Faster option is 80e and shipping time only 2 to 8 working days.
Okay update:
NOTE: The repaircenter in the Netherlands has been closed recently. This means from now on repairs need to be send to the repaircenter in Hong Kong directly by you. The adress will be given to you after you have created a ticket.
You will have to pay for the shipping fee to Hong Kong. The repaircenter will pay for the shipping costs back to you.
So it will be afterwards free for me.
Title: Re: Antminer S17e's strange problem
Post by: jonaeljoni on January 27, 2021, 01:58:57 PM
2021-01-23 11:11:32:driver-btm-api.c:2379:bitmain_board_init: FAULT: check_asic_number_until_volt_balance PASS but bitmain_board_config_init FAIL!!!
There are a few things I would check, the first one would be the PSU, power off-chain 2 and 3, this will confirm if the problem is a bad PSU (a very common issue) or your Chain 1 has other problems, once that test is done, if the PSU is fine and the board still shows 0 frequency and hashrate, your next move would be changing the tunning profile, what is your profile settings as of right now? On a side note, BinancePool sucks (https://bitcointalk.org/index.php?topic=5271427.0). How can I change those tuning settings? Or is it wise now? I can try to find information tuninging it up
Title: Re: Antminer S17e's strange problem
Post by: favebook on January 27, 2021, 11:56:39 PM
You would have to upgrade it to a custom firmware, like Thierry's one I linked previously.
But if you do that, please revert back to original one before sending it to Bitmain as it is not covered under warranty.
Title: Re: Antminer S17e's strange problem
Post by: jonaeljoni on February 22, 2021, 11:09:39 AM
I recovered control board with sd file. I got it from Bitmain's customer service. Now the whole miner isn't working. So frustrating. Before it showed that invalid volt etc. but worked with two hashboards. After driving sd file none of hashboards arent working. Kernel log says something about temp sensor's type. I think this is a crucial moment when I will send this to warranty repair. 2021-02-22 10:59:34 power_api.c:274:set_working_voltage_raw: working_voltage_raw = 1850 2021-02-22 10:59:35 temperature.c:297:calibrate_temp_sensor_one_chain: chain 0 temp sensor NCT218 2021-02-22 11:00:30 temperature.c:219:is_temp_sensor_type_correct: Wrong temp sensor type, chain = 1, sensor = 107, type = 0x0, retry. 2021-02-22 11:00:30 driver-btm-api.c:186:set_miner_status: ERROR_TEMP_LOST 2021-02-22 11:00:30 driver-btm-api.c:127:stop_mining: stop mining: Can't get temperature sensor type! 2021-02-22 11:00:30 thread.c:750:cancel_read_nonce_reg_thread: cancel thread 2021-02-22 11:00:30 driver-btm-api.c:112:killall_hashboard: ****power off hashboard**** EDIT: I upgraded firmware and now it is working again with two same hashboards as before. So sending to China for warranty repair is not compulsory right now. I will do it later. My warranty expires end of this year. Miners bought from antminerdistribution gets warranty of two years. So I have time left.
|