Bitcoin Forum>Bitcoin>Mining>Mining support
Pages:
Author

Topic: T17/S17 malfunction: cases, solutions, remedies, RMA history - page 2. (Read 7029 times)

Heathen23
newbie
Activity: 26
Merit: 30
Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
January 17, 2022, 05:43:47 PM
#406
I rebooted one more time as only one hash-board was running.
Now it finds all asics on all boards but shuts down due to votage being different!.
Code:
2022-01-17 22:27:12 driver-btm-api.c:1134:check_asic_number_with_power_on: Chain[0]: find 65 asic, times 0
2022-01-17 22:27:23 driver-btm-api.c:1134:check_asic_number_with_power_on: Chain[1]: find 65 asic, times 0
2022-01-17 22:27:34 driver-btm-api.c:1134:check_asic_number_with_power_on: Chain[2]: find 65 asic, times 0
-----------------------------------
2022-01-17 22:27:44 voltage[0] = 1920
2022-01-17 22:27:44 voltage[1] = 1920
2022-01-17 22:27:44 voltage[2] = 1960
2022-01-17 22:27:44 Voltage are different. Will exit.
2022-01-17 22:27:44 driver-btm-api.c:222:set_miner_status: ERROR_SOC_INIT
2022-01-17 22:27:44 driver-btm-api.c:156:stop_mining: stop mining: soc init failed!
2022-01-17 22:27:44 thread.c:1403:cancel_read_nonce_reg_thread: cancel thread
2022-01-17 22:27:44 driver-btm-api.c:141:killall_hashboard: ****power off hashboard****

But voltages were 1920 on chain0 and chain1 even when it did not find all asics on chain2 and it started hashing with chain0 and chain1. Why this time despite finding all asics in chain2 it is shutting down Chain0 and chain1 just because chqin2 has a different voltage?  Is this the real problem? Any clues about what to do?

Chain2 is where I re-soldered the capacitor.
 
Full log below:
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: 203316K/245760K available (6345K kernel code, 231K rwdata, 1896K rodata, 1024K init, 223K bss, 26060K 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
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: 13020K (cce49000 - 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 MT29F2G08ABAEAWP
nand: 256 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 64
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: 1/0, WL threshold: 4096, image sequence number: 11906131
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 5C61C316-5FAD-4CFA-B280-2AFAE13C9D72, 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: 2/0, WL threshold: 4096, image sequence number: 169213079
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 6FB1BE46-BF1C-4F4C-9CA2-2F82009B82B4, 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 0xcfb38000
*base_vir_addr = 0xb023
In fpga mem driver!
request_mem_region OK!
fpga mem virtual address is 0xd2000000
2022-01-17 22:25:26 driver-btm-api.c:779:init_freq_mode: This is scan-user version
2022-01-17 22:25:26 driver-btm-api.c:2451:bitmain_soc_init: opt_multi_version     = 1
2022-01-17 22:25:26 driver-btm-api.c:2452:bitmain_soc_init: opt_bitmain_ab        = 1
2022-01-17 22:25:26 driver-btm-api.c:2453:bitmain_soc_init: opt_bitmain_work_mode = 0
2022-01-17 22:25:26 driver-btm-api.c:2454:bitmain_soc_init: Miner compile time: Tue Jun  2 10:31:07 CST 2020 type: Antminer S17+
2022-01-17 22:25:26 driver-btm-api.c:2455:bitmain_soc_init: commit version: 1ca50a5 2020-06-01 18:51:22, build by: lol 2020-06-02 10:37:21
2022-01-17 22:25:26 driver-btm-api.c:2083:show_sn: len:16, 8034b4442b104814
2022-01-17 22:25:26 driver-btm-api.c:2461:bitmain_soc_init: show sn return 1
2022-01-17 22:25:26 driver-btm-api.c:2103:handle_sn_for_factory_mode: show sn return 1
2022-01-17 22:25:26 driver-btm-api.c:2141:handle_sn_for_factory_mode: read sn success, 8034b4442b104814
2022-01-17 22:25:26 fan.c:284:front_fan_power_on: Note: front fan is power on!
2022-01-17 22:25:26 fan.c:296:rear_fan_power_on: Note: rear fan is power on!
2022-01-17 22:25:26 driver-btm-api.c:1314:miner_device_init: Detect 256MB control board of XILINX
2022-01-17 22:25:26 driver-btm-api.c:1255:init_fan_parameter: fan_eft : 0  fan_pwm : 0
2022-01-17 22:25:32 driver-btm-api.c:1239:init_miner_version: miner ID : 8034b4442b104814
2022-01-17 22:25:32 driver-btm-api.c:1245:init_miner_version: FPGA Version = 0xB023
2022-01-17 22:25:37 driver-btm-api.c:837:get_product_id: product_id[0] = 0
2022-01-17 22:25:37 driver-btm-api.c:837:get_product_id: product_id[1] = 0
2022-01-17 22:25:37 driver-btm-api.c:837:get_product_id: product_id[2] = 0
2022-01-17 22:25:37 driver-btm-api.c:2234:update_conf_by_power_feedback: Power feedback is disabled
2022-01-17 22:25:37 driver-btm-api.c:2202:get_calibration_voltage: calibration voltage flag is error data.
2022-01-17 22:25:37 driver-btm-api.c:2268:update_conf_by_power_feedback: Note: no calibration voltage, default diff = 0
2022-01-17 22:25:37 frequency.c:1457:adjust_higer_max_vol_table: adjust_higer_max_vol_table, adjust_vol = 0
2022-01-17 22:25:37 thread.c:1363:create_read_nonce_reg_thread: create thread
2022-01-17 22:25:43 driver-btm-api.c:1239:init_miner_version: miner ID : 8034b4442b104814
2022-01-17 22:25:43 driver-btm-api.c:1245:init_miner_version: FPGA Version = 0xB023
2022-01-17 22:25:49 driver-btm-api.c:837:get_product_id: product_id[0] = 0
2022-01-17 22:25:49 driver-btm-api.c:837:get_product_id: product_id[1] = 0
2022-01-17 22:25:49 driver-btm-api.c:837:get_product_id: product_id[2] = 0
2022-01-17 22:25:49 driver-btm-api.c:792:_set_project_type: project:0
2022-01-17 22:25:49 driver-btm-api.c:813:_set_project_type: Project type: Antminer S17+
2022-01-17 22:25:49 driver-btm-api.c:824:dump_pcb_bom_version: Chain [0] PCB Version: 0x0100
2022-01-17 22:25:49 driver-btm-api.c:825:dump_pcb_bom_version: Chain [0] BOM Version: 0x0100
2022-01-17 22:25:49 driver-btm-api.c:824:dump_pcb_bom_version: Chain [1] PCB Version: 0x0100
2022-01-17 22:25:49 driver-btm-api.c:825:dump_pcb_bom_version: Chain [1] BOM Version: 0x0100
2022-01-17 22:25:49 driver-btm-api.c:824:dump_pcb_bom_version: Chain [2] PCB Version: 0x0100
2022-01-17 22:25:49 driver-btm-api.c:825:dump_pcb_bom_version: Chain [2] BOM Version: 0x0100
2022-01-17 22:25:51 driver-btm-api.c:2372:bitmain_board_init: Fan check passed.
2022-01-17 22:25:52 board.c:36:jump_and_app_check_restore_pic: chain[0] PIC jump to app
2022-01-17 22:25:54 board.c:40:jump_and_app_check_restore_pic: Check chain[0] PIC fw version=0x88
2022-01-17 22:25:55 board.c:36:jump_and_app_check_restore_pic: chain[1] PIC jump to app
2022-01-17 22:25:57 board.c:40:jump_and_app_check_restore_pic: Check chain[1] PIC fw version=0x88
2022-01-17 22:25:58 board.c:36:jump_and_app_check_restore_pic: chain[2] PIC jump to app
2022-01-17 22:26:00 board.c:40:jump_and_app_check_restore_pic: Check chain[2] PIC fw version=0x88
2022-01-17 22:26:00 thread.c:1358:create_pic_heart_beat_thread: create thread
2022-01-17 22:26:00 power_api.c:213:power_init: Power init:
2022-01-17 22:26:00 power_api.c:214:power_init: current_voltage_raw = 0
2022-01-17 22:26:00 power_api.c:215:power_init: highest_voltage_raw = 2100
2022-01-17 22:26:00 power_api.c:216:power_init: working_voltage_raw = 1950
2022-01-17 22:26:00 power_api.c:217:power_init: higher_voltage_raw  = 2040
2022-01-17 22:26:00 power_api.c:218:power_init: check_asic_voltage_raw  = 2100
2022-01-17 22:26:00 driver-btm-api.c:2382:bitmain_board_init: Enter 30s sleep to make sure power release finish.
2022-01-17 22:26:00 power_api.c:186:power_off: init gpio907
2022-01-17 22:26:32 power_api.c:324:set_to_highest_voltage_by_steps: Set to voltage raw 2100, step by step.
2022-01-17 22:26:58 power_api.c:85:check_voltage_multi: retry time: 0
2022-01-17 22:26:59 power_api.c:40:_get_avg_voltage: chain = 0, voltage = 21.094872
2022-01-17 22:27:00 power_api.c:40:_get_avg_voltage: chain = 1, voltage = 21.124679
2022-01-17 22:27:01 power_api.c:40:_get_avg_voltage: chain = 2, voltage = 21.295630
2022-01-17 22:27:01 power_api.c:53:_get_avg_voltage: average_voltage = 21.171727
2022-01-17 22:27:01 power_api.c:71:check_voltage: target_vol = 21.00, actural_vol = 21.17, check voltage passed.
2022-01-17 22:27:01 uart.c:72:set_baud: set fpga_baud to 115200
2022-01-17 22:27:12 driver-btm-api.c:1134:check_asic_number_with_power_on: Chain[0]: find 65 asic, times 0
2022-01-17 22:27:23 driver-btm-api.c:1134:check_asic_number_with_power_on: Chain[1]: find 65 asic, times 0
2022-01-17 22:27:34 driver-btm-api.c:1134:check_asic_number_with_power_on: Chain[2]: find 65 asic, times 0
2022-01-17 22:27:43 driver-hash-chip.c:266:set_uart_relay: set uart relay to 0x330003
2022-01-17 22:27:43 driver-btm-api.c:435:set_order_clock: chain[0]: set order clock, stragegy 3
2022-01-17 22:27:43 driver-btm-api.c:435:set_order_clock: chain[1]: set order clock, stragegy 3
2022-01-17 22:27:43 driver-btm-api.c:435:set_order_clock: chain[2]: set order clock, stragegy 3
2022-01-17 22:27:43 driver-hash-chip.c:502:set_clock_delay_control: core_data = 0x34
2022-01-17 22:27:43 driver-btm-api.c:1892:check_clock_counter: freq 50 clock_counter_limit 6
2022-01-17 22:27:44 voltage[0] = 1920
2022-01-17 22:27:44 voltage[1] = 1920
2022-01-17 22:27:44 voltage[2] = 1960
2022-01-17 22:27:44 Voltage are different. Will exit.
2022-01-17 22:27:44 driver-btm-api.c:222:set_miner_status: ERROR_SOC_INIT
2022-01-17 22:27:44 driver-btm-api.c:156:stop_mining: stop mining: soc init failed!
2022-01-17 22:27:44 thread.c:1403:cancel_read_nonce_reg_thread: cancel thread
2022-01-17 22:27:44 driver-btm-api.c:141:killall_hashboard: ****power off hashboard****
wndsnb
hero member
Activity: 544
Merit: 589
Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
January 17, 2022, 11:55:15 AM
#405
The chip count is only ever a clue and does often change with multiple attempts on a bad board. A lot of times the core problem is a resistive or flaky connection that can change with temperature. So you might get 0, or a number close to the actual problem area, or a random number.

Quote from: Heathen23 on January 16, 2022, 10:41:19 PM
domain if I am not wrong. I agree that just re-soldering is a shot in the dark but I lack expertise and probably equipment to do anything more.
Chain 0 is now saying
"chain 0 get hashrate_reg_counter 63, require 65, failed times 1: ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo xxooo"
compared to last time
chain 0 get hashrate_reg_counter 58, require 65, failed times 1: ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo oooxx xxxxx"

I don't know the exact meaning/format last part of these lines. The chips on the board are all connected in series in a chain, so to get a message from chip 65, it gets forwarded through every other chip on the board. If chip 63 has a problem, it normally won't forward messages from the chips further down the chain and you end up with a count of 62. So I don't know if that "xxooo" on the last domain is just ordered backwards so the two x chips are actually 65 and 64, or if the chips are both forwarding messages correctly but not responding with their own messages correctly.
Heathen23
newbie
Activity: 26
Merit: 30
Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
January 16, 2022, 10:41:19 PM
#404
Quote from: wndsnb on January 16, 2022, 08:03:31 PM
Quote from: Heathen23 on January 16, 2022, 06:36:13 PM
My question is do you think the problem with chain 2 is the capacitor that the 63rd chip? Would you do something different that re-soldering if you faced these errors?

I assume you're talking about one of the large electrolytic caps? I doubt it would cause the issue you are seeing. If it was one of the caps in the boost circuit that generates the 1.8V signal for the last voltage domain, maybe the regulator could go unstable, so that would mess up all the chips in the last voltage domain though.

Also, just re-soldering those chips is a bit of a shot in the dark. The problem could be those chips, or the chips after, or sometimes even just another chip in the same voltage domain.

Thanks wndsnb for responding. You are right. it is the large 330mf and 30v cap just besides, what I think is, the 63rd chip. Incidentally this board is finding only 62 chip. I encircled the cap and the 63rd chip in black oval in the picture that I borrowed from Zeus manual.

https://imgur.com/a/RaQXtuS

Another strange thing is after another reboot the error message changed a bit
"Chain 2 only find 0 asic, will power off hash board 2"
compared to last time
"Chain 2 only find 62 asic, will power off hash board 2"

So why did it find 62 Asic last time but 0 this time? Outside temperature is sub zero after a round of snow and I don't have insulation / heating in the place where the miner is so excess temperature is ruled out. This is the board where I reinstated the capacitor. i agree with you that the problem may be in chip # 62, 61, 63 or in the entire last column 61 through 65 which is the voltage domain if I am not wrong. I agree that just re-soldering is a shot in the dark but I lack expertise and probably equipment to do anything more.

Chain 0 is now saying
"chain 0 get hashrate_reg_counter 63, require 65, failed times 1: ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo xxooo"
compared to last time
chain 0 get hashrate_reg_counter 58, require 65, failed times 1: ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo oooxx xxxxx"

This board seem to have done slightly better. If I am reading it right last time chips #59 through 65 failed but this time only chip#61 and 62 failed. Am I reading it right?
wndsnb
hero member
Activity: 544
Merit: 589
Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
January 16, 2022, 08:03:31 PM
#403
Quote from: Heathen23 on January 16, 2022, 06:36:13 PM
My question is do you think the problem with chain 2 is the capacitor that the 63rd chip? Would you do something different that re-soldering if you faced these errors?

I assume you're talking about one of the large electrolytic caps? I doubt it would cause the issue you are seeing. If it was one of the caps in the boost circuit that generates the 1.8V signal for the last voltage domain, maybe the regulator could go unstable, so that would mess up all the chips in the last voltage domain though.

Also, just re-soldering those chips is a bit of a shot in the dark. The problem could be those chips, or the chips after, or sometimes even just another chip in the same voltage domain.
Heathen23
newbie
Activity: 26
Merit: 30
Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
January 16, 2022, 06:36:13 PM
#402
Hi Guys,
I am having trouble with an S17+. This one used to run well and suddenly stopped working. I opened up, cleaned the power supply and the hash-boards. While putting the hash-boards back a capacitor from 3rd hash-board(Chain2) got detached from the board. I soldered it back.

Now,
Chain 0: starts hashing but is shutoff with the following error
"ERROR: chain 0 get hashrate_reg_counter 58, require 65, failed times 1: ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo oooxx xxxxx
chain 0 can't get enough hashrate reg val for 30 times, power off."

Chain1: working fine.

Chain2: is powered off with error: "Chain 2 only find 62 asic, will power off hash board 2". This is the board that lost the capacitor that i have resoldered.

- I am thinking I have to re-solder chip 59 on chain 0 and resolder chip 63 on Chain 2.

Do you think the problem with chain 2 is the capacitor rather than the 63rd chip? Would you do something different if you faced these errors? I notice that with bosminer all 3 boards start and shut off.


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: 203316K/245760K available (6345K kernel code, 231K rwdata, 1896K rodata, 1024K init, 223K bss, 26060K 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
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: 13020K (cce49000 - 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 MT29F2G08ABAEAWP
nand: 256 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 64
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: 1/0, WL threshold: 4096, image sequence number: 11906131
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 5C61C316-5FAD-4CFA-B280-2AFAE13C9D72, 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: 1/0, WL threshold: 4096, image sequence number: 169213079
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): default file-system created
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 6FB1BE46-BF1C-4F4C-9CA2-2F82009B82B4, 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 0xcfb58000
*base_vir_addr = 0xb023
In fpga mem driver!
request_mem_region OK!
fpga mem virtual address is 0xd2000000
random: nonblocking pool is initialized
2022-01-16 22:43:51 driver-btm-api.c:779:init_freq_mode: This is scan-user version
2022-01-16 22:43:51 driver-btm-api.c:2451:bitmain_soc_init: opt_multi_version     = 1
2022-01-16 22:43:51 driver-btm-api.c:2452:bitmain_soc_init: opt_bitmain_ab        = 1
2022-01-16 22:43:51 driver-btm-api.c:2453:bitmain_soc_init: opt_bitmain_work_mode = 0
2022-01-16 22:43:51 driver-btm-api.c:2454:bitmain_soc_init: Miner compile time: Tue Jun  2 10:31:07 CST 2020 type: Antminer S17+
2022-01-16 22:43:51 driver-btm-api.c:2455:bitmain_soc_init: commit version: 1ca50a5 2020-06-01 18:51:22, build by: lol 2020-06-02 10:37:21
2022-01-16 22:43:51 driver-btm-api.c:2083:show_sn: len:16, 8034b4442b104814
2022-01-16 22:43:51 driver-btm-api.c:2461:bitmain_soc_init: show sn return 1
2022-01-16 22:43:51 driver-btm-api.c:2103:handle_sn_for_factory_mode: show sn return 1
2022-01-16 22:43:51 driver-btm-api.c:2141:handle_sn_for_factory_mode: read sn success, 8034b4442b104814
2022-01-16 22:43:51 fan.c:284:front_fan_power_on: Note: front fan is power on!
2022-01-16 22:43:51 fan.c:296:rear_fan_power_on: Note: rear fan is power on!
2022-01-16 22:43:51 driver-btm-api.c:1314:miner_device_init: Detect 256MB control board of XILINX
2022-01-16 22:43:51 driver-btm-api.c:1255:init_fan_parameter: fan_eft : 0  fan_pwm : 0
2022-01-16 22:43:57 driver-btm-api.c:1239:init_miner_version: miner ID : 8034b4442b104814
2022-01-16 22:43:57 driver-btm-api.c:1245:init_miner_version: FPGA Version = 0xB023
2022-01-16 22:44:02 driver-btm-api.c:837:get_product_id: product_id[0] = 0
2022-01-16 22:44:02 driver-btm-api.c:837:get_product_id: product_id[1] = 0
2022-01-16 22:44:02 driver-btm-api.c:837:get_product_id: product_id[2] = 0
2022-01-16 22:44:02 driver-btm-api.c:2234:update_conf_by_power_feedback: Power feedback is disabled
2022-01-16 22:44:02 driver-btm-api.c:2202:get_calibration_voltage: calibration voltage flag is error data.
2022-01-16 22:44:02 driver-btm-api.c:2268:update_conf_by_power_feedback: Note: no calibration voltage, default diff = 0
2022-01-16 22:44:02 frequency.c:1457:adjust_higer_max_vol_table: adjust_higer_max_vol_table, adjust_vol = 0
2022-01-16 22:44:02 thread.c:1363:create_read_nonce_reg_thread: create thread
2022-01-16 22:44:08 driver-btm-api.c:1239:init_miner_version: miner ID : 8034b4442b104814
2022-01-16 22:44:08 driver-btm-api.c:1245:init_miner_version: FPGA Version = 0xB023
2022-01-16 22:44:14 driver-btm-api.c:837:get_product_id: product_id[0] = 0
2022-01-16 22:44:14 driver-btm-api.c:837:get_product_id: product_id[1] = 0
2022-01-16 22:44:14 driver-btm-api.c:837:get_product_id: product_id[2] = 0
2022-01-16 22:44:14 driver-btm-api.c:792:_set_project_type: project:0
2022-01-16 22:44:14 driver-btm-api.c:813:_set_project_type: Project type: Antminer S17+
2022-01-16 22:44:14 driver-btm-api.c:824:dump_pcb_bom_version: Chain [0] PCB Version: 0x0100
2022-01-16 22:44:14 driver-btm-api.c:825:dump_pcb_bom_version: Chain [0] BOM Version: 0x0100
2022-01-16 22:44:14 driver-btm-api.c:824:dump_pcb_bom_version: Chain [1] PCB Version: 0x0100
2022-01-16 22:44:14 driver-btm-api.c:825:dump_pcb_bom_version: Chain [1] BOM Version: 0x0100
2022-01-16 22:44:14 driver-btm-api.c:824:dump_pcb_bom_version: Chain [2] PCB Version: 0x0100
2022-01-16 22:44:14 driver-btm-api.c:825:dump_pcb_bom_version: Chain [2] BOM Version: 0x0100
2022-01-16 22:44:14 driver-btm-api.c:2372:bitmain_board_init: Fan check passed.
2022-01-16 22:44:15 board.c:36:jump_and_app_check_restore_pic: chain[0] PIC jump to app
2022-01-16 22:44:17 board.c:40:jump_and_app_check_restore_pic: Check chain[0] PIC fw version=0x88
2022-01-16 22:44:18 board.c:36:jump_and_app_check_restore_pic: chain[1] PIC jump to app
2022-01-16 22:44:20 board.c:40:jump_and_app_check_restore_pic: Check chain[1] PIC fw version=0x88
2022-01-16 22:44:21 board.c:36:jump_and_app_check_restore_pic: chain[2] PIC jump to app
2022-01-16 22:44:23 board.c:40:jump_and_app_check_restore_pic: Check chain[2] PIC fw version=0x88
2022-01-16 22:44:23 thread.c:1358:create_pic_heart_beat_thread: create thread
2022-01-16 22:44:23 power_api.c:213:power_init: Power init:
2022-01-16 22:44:23 power_api.c:214:power_init: current_voltage_raw = 0
2022-01-16 22:44:23 power_api.c:215:power_init: highest_voltage_raw = 2100
2022-01-16 22:44:23 power_api.c:216:power_init: working_voltage_raw = 1950
2022-01-16 22:44:23 power_api.c:217:power_init: higher_voltage_raw  = 2040
2022-01-16 22:44:23 power_api.c:218:power_init: check_asic_voltage_raw  = 2100
2022-01-16 22:44:23 driver-btm-api.c:2382:bitmain_board_init: Enter 30s sleep to make sure power release finish.
2022-01-16 22:44:55 power_api.c:324:set_to_highest_voltage_by_steps: Set to voltage raw 2100, step by step.
2022-01-16 22:45:21 power_api.c:85:check_voltage_multi: retry time: 0
2022-01-16 22:45:22 power_api.c:40:_get_avg_voltage: chain = 0, voltage = 21.070513
2022-01-16 22:45:23 power_api.c:40:_get_avg_voltage: chain = 1, voltage = 21.100258
2022-01-16 22:45:24 power_api.c:40:_get_avg_voltage: chain = 2, voltage = 21.271209
2022-01-16 22:45:24 power_api.c:53:_get_avg_voltage: average_voltage = 21.147326
2022-01-16 22:45:24 power_api.c:71:check_voltage: target_vol = 21.00, actural_vol = 21.15, check voltage passed.
2022-01-16 22:45:24 uart.c:72:set_baud: set fpga_baud to 115200
2022-01-16 22:45:35 driver-btm-api.c:1134:check_asic_number_with_power_on: Chain[0]: find 65 asic, times 0
2022-01-16 22:45:46 driver-btm-api.c:1134:check_asic_number_with_power_on: Chain[1]: find 8 asic, times 0
2022-01-16 22:45:57 driver-btm-api.c:1134:check_asic_number_with_power_on: Chain[1]: find 8 asic, times 1
2022-01-16 22:46:08 driver-btm-api.c:1134:check_asic_number_with_power_on: Chain[1]: find 8 asic, times 2
2022-01-16 22:46:08 power_api.c:380:modify_check_asic_voltage: check_asic_voltage_raw  = 2100
chain 1, IO_DRIVE_STRENGTH_CONFIGURATION reg = 0x f1fffff
2022-01-16 22:46:17 driver-btm-api.c:1157:check_asic_number_with_power_on: Chain[1]: find 63 asic, times 3
2022-01-16 22:46:17 power_api.c:380:modify_check_asic_voltage: check_asic_voltage_raw  = 2050
2022-01-16 22:46:17 power_api.c:364:set_to_check_asic_voltage_by_steps: Set to voltage raw 2050, step by step.
2022-01-16 22:46:21 power_api.c:85:check_voltage_multi: retry time: 0
2022-01-16 22:46:23 power_api.c:40:_get_avg_voltage: chain = 0, voltage = 20.556977
2022-01-16 22:46:24 power_api.c:40:_get_avg_voltage: chain = 1, voltage = 20.560975
2022-01-16 22:46:25 power_api.c:40:_get_avg_voltage: chain = 2, voltage = 20.758355
2022-01-16 22:46:25 power_api.c:53:_get_avg_voltage: average_voltage = 20.625436
2022-01-16 22:46:25 power_api.c:71:check_voltage: target_vol = 20.50, actural_vol = 20.63, check voltage passed.
chain 1, IO_DRIVE_STRENGTH_CONFIGURATION reg = 0x f1fffff
2022-01-16 22:46:34 driver-btm-api.c:1157:check_asic_number_with_power_on: Chain[1]: find 65 asic, times 4
2022-01-16 22:46:34 power_api.c:324:set_to_highest_voltage_by_steps: Set to voltage raw 2100, step by step.
2022-01-16 22:46:37 power_api.c:85:check_voltage_multi: retry time: 0
2022-01-16 22:46:39 power_api.c:40:_get_avg_voltage: chain = 0, voltage = 21.019205
2022-01-16 22:46:40 power_api.c:40:_get_avg_voltage: chain = 1, voltage = 21.048780
2022-01-16 22:46:41 power_api.c:40:_get_avg_voltage: chain = 2, voltage = 21.246787
2022-01-16 22:46:41 power_api.c:53:_get_avg_voltage: average_voltage = 21.104924
2022-01-16 22:46:41 power_api.c:71:check_voltage: target_vol = 21.00, actural_vol = 21.10, check voltage passed.
2022-01-16 22:46:52 driver-btm-api.c:1134:check_asic_number_with_power_on: Chain[2]: find 62 asic, times 0
2022-01-16 22:47:03 driver-btm-api.c:1134:check_asic_number_with_power_on: Chain[2]: find 62 asic, times 1
2022-01-16 22:47:14 driver-btm-api.c:1134:check_asic_number_with_power_on: Chain[2]: find 62 asic, times 2
2022-01-16 22:47:14 power_api.c:380:modify_check_asic_voltage: check_asic_voltage_raw  = 2100
chain 2, IO_DRIVE_STRENGTH_CONFIGURATION reg = 0x f1fffff
2022-01-16 22:47:23 driver-btm-api.c:1157:check_asic_number_with_power_on: Chain[2]: find 62 asic, times 3
2022-01-16 22:47:23 power_api.c:380:modify_check_asic_voltage: check_asic_voltage_raw  = 2050
2022-01-16 22:47:23 power_api.c:364:set_to_check_asic_voltage_by_steps: Set to voltage raw 2050, step by step.
2022-01-16 22:47:27 power_api.c:85:check_voltage_multi: retry time: 0
2022-01-16 22:47:28 power_api.c:40:_get_avg_voltage: chain = 0, voltage = 20.556977
2022-01-16 22:47:29 power_api.c:40:_get_avg_voltage: chain = 1, voltage = 20.560975
2022-01-16 22:47:30 power_api.c:40:_get_avg_voltage: chain = 2, voltage = 20.731706
2022-01-16 22:47:30 power_api.c:53:_get_avg_voltage: average_voltage = 20.616553
2022-01-16 22:47:30 power_api.c:71:check_voltage: target_vol = 20.50, actural_vol = 20.62, check voltage passed.
chain 2, IO_DRIVE_STRENGTH_CONFIGURATION reg = 0x f1fffff
2022-01-16 22:47:39 driver-btm-api.c:1157:check_asic_number_with_power_on: Chain[2]: find 62 asic, times 4
2022-01-16 22:47:39 power_api.c:380:modify_check_asic_voltage: check_asic_voltage_raw  = 2000
2022-01-16 22:47:39 power_api.c:364:set_to_check_asic_voltage_by_steps: Set to voltage raw 2000, step by step.
2022-01-16 22:47:42 power_api.c:85:check_voltage_multi: retry time: 0
2022-01-16 22:47:43 power_api.c:40:_get_avg_voltage: chain = 0, voltage = 20.046094
2022-01-16 22:47:44 power_api.c:40:_get_avg_voltage: chain = 1, voltage = 20.048780
2022-01-16 22:47:45 power_api.c:40:_get_avg_voltage: chain = 2, voltage = 20.219511
2022-01-16 22:47:45 power_api.c:53:_get_avg_voltage: average_voltage = 20.104795
2022-01-16 22:47:45 power_api.c:71:check_voltage: target_vol = 20.00, actural_vol = 20.10, check voltage passed.
chain 2, IO_DRIVE_STRENGTH_CONFIGURATION reg = 0x f1fffff
2022-01-16 22:47:55 driver-btm-api.c:1157:check_asic_number_with_power_on: Chain[2]: find 62 asic, times 5
2022-01-16 22:47:55 power_api.c:380:modify_check_asic_voltage: check_asic_voltage_raw  = 2100
2022-01-16 22:47:55 power_api.c:364:set_to_check_asic_voltage_by_steps: Set to voltage raw 2100, step by step.
2022-01-16 22:48:00 power_api.c:85:check_voltage_multi: retry time: 0
2022-01-16 22:48:01 power_api.c:40:_get_avg_voltage: chain = 0, voltage = 21.043533
2022-01-16 22:48:02 power_api.c:40:_get_avg_voltage: chain = 1, voltage = 21.048780
2022-01-16 22:48:03 power_api.c:40:_get_avg_voltage: chain = 2, voltage = 21.219511
2022-01-16 22:48:03 power_api.c:53:_get_avg_voltage: average_voltage = 21.103941
2022-01-16 22:48:03 power_api.c:71:check_voltage: target_vol = 21.00, actural_vol = 21.10, check voltage passed.
2022-01-16 22:48:03 driver-btm-api.c:1193:check_asic_number: Chain 2 only find 62 asic, will power off hash board 2
2022-01-16 22:48:04 driver-btm-api.c:1195:check_asic_number: Chain 2 voltage: an0 = 2.787097, an2 2.806452, an6 2.512903.
2022-01-16 22:48:11 driver-hash-chip.c:266:set_uart_relay: set uart relay to 0x330003
2022-01-16 22:48:11 driver-btm-api.c:435:set_order_clock: chain[0]: set order clock, stragegy 3
2022-01-16 22:48:11 driver-btm-api.c:435:set_order_clock: chain[1]: set order clock, stragegy 3
2022-01-16 22:48:11 driver-hash-chip.c:502:set_clock_delay_control: core_data = 0x34
2022-01-16 22:48:11 driver-btm-api.c:1892:check_clock_counter: freq 50 clock_counter_limit 6
2022-01-16 22:48:12 voltage[0] = 1920
2022-01-16 22:48:12 voltage[1] = 1920
2022-01-16 22:48:12 power_api.c:226:set_working_voltage_raw: working_voltage_raw = 1920
2022-01-16 22:48:13 temperature.c:340:calibrate_temp_sensor_one_chain: chain 0 temp sensor NCT218
2022-01-16 22:48:14 temperature.c:340:calibrate_temp_sensor_one_chain: chain 1 temp sensor NCT218
2022-01-16 22:48:14 uart.c:72:set_baud: set fpga_baud to 12000000
2022-01-16 22:48:15 driver-btm-api.c:293:check_bringup_temp: Bring up temperature is 23
2022-01-16 22:48:15 thread.c:1378:create_check_miner_status_thread: create thread
2022-01-16 22:48:15 thread.c:1368:create_show_miner_status_thread: create thread
2022-01-16 22:48:15 thread.c:1348:create_temperature_monitor_thread: create thread
2022-01-16 22:48:15 frequency.c:514:check_bringup_temp_dec_freq: dec freq = 0 when bringup temp = 23 dec_freq_index=0
2022-01-16 22:48:15 freq_tuning.c:183:freq_tuning_get_max_freq: Max freq of tuning is 650
2022-01-16 22:48:15 driver-btm-api.c:1765:send_null_work: [DEBUG] Send null work.
2022-01-16 22:48:15 thread.c:1338:create_asic_status_monitor_thread: create thread
2022-01-16 22:48:15 frequency.c:1110:inc_freq_with_fixed_vco: chain = 255, freq = 560, is_higher_voltage = true
2022-01-16 22:49:47 power_api.c:352:set_to_voltage_by_steps: Set to voltage raw 2090, step by step.
2022-01-16 22:49:48 power_api.c:85:check_voltage_multi: retry time: 0
2022-01-16 22:49:49 power_api.c:40:_get_avg_voltage: chain = 0, voltage = 20.897566
2022-01-16 22:49:51 power_api.c:40:_get_avg_voltage: chain = 1, voltage = 20.926828
2022-01-16 22:49:51 power_api.c:53:_get_avg_voltage: average_voltage = 20.912197
2022-01-16 22:49:51 power_api.c:71:check_voltage: target_vol = 20.90, actural_vol = 20.91, check voltage passed.
2022-01-16 22:52:02 power_api.c:352:set_to_voltage_by_steps: Set to voltage raw 2080, step by step.
2022-01-16 22:52:03 power_api.c:85:check_voltage_multi: retry time: 0
2022-01-16 22:52:04 power_api.c:40:_get_avg_voltage: chain = 0, voltage = 20.775927
2022-01-16 22:52:05 power_api.c:40:_get_avg_voltage: chain = 1, voltage = 20.780487
2022-01-16 22:52:05 power_api.c:53:_get_avg_voltage: average_voltage = 20.778207
2022-01-16 22:52:05 power_api.c:71:check_voltage: target_vol = 20.80, actural_vol = 20.78, check voltage passed.
2022-01-16 22:54:29 frequency.c:1152:inc_freq_with_fixed_step: chain = 0, freq_start = 560, freq_end = 570, freq_step = 5, is_higher_voltage = true
2022-01-16 22:54:33 frequency.c:1181:inc_asic_diff_freq_by_steps: chain = 1, start = 560, freq_step = 5
2022-01-16 22:54:35 driver-btm-api.c:765:set_timeout: freq = 570, percent = 90, hcn = 44236, timeout = 77
2022-01-16 22:54:35 power_api.c:310:set_to_working_voltage_by_steps: Set to voltage raw 1920, step by step.
2022-01-16 22:54:42 power_api.c:85:check_voltage_multi: retry time: 0
2022-01-16 22:54:43 power_api.c:40:_get_avg_voltage: chain = 0, voltage = 19.218949
2022-01-16 22:54:44 power_api.c:40:_get_avg_voltage: chain = 1, voltage = 19.219511
2022-01-16 22:54:44 power_api.c:53:_get_avg_voltage: average_voltage = 19.219230
2022-01-16 22:54:44 power_api.c:71:check_voltage: target_vol = 19.20, actural_vol = 19.22, check voltage passed.
2022-01-16 22:54:44 thread.c:1373:create_check_system_status_thread: create thread
2022-01-16 22:54:44 driver-btm-api.c:2618:bitmain_soc_init: Init done!
2022-01-16 22:54:44 driver-btm-api.c:222:set_miner_status: STATUS_INIT
2022-01-16 22:54:49 driver-btm-api.c:222:set_miner_status: STATUS_OKAY
2022-01-16 22:54:50 frequency.c:205:get_ideal_hash_rate_GH: ideal_hash_rate = 48464
2022-01-16 22:54:50 frequency.c:223:get_sale_hash_rate_GH: sale_hash_rate = 46000
2022-01-16 22:54:54 driver-btm-api.c:1496:dhash_chip_send_job: Version num 4.
2022-01-16 22:54:54 driver-btm-api.c:1644:dhash_chip_send_job: stime.tv_sec 1642373694, block_ntime 1642373688
2022-01-16 23:05:51 thread.c:1273:asic_status_monitor_thread: ERROR: chain 0 get hashrate_reg_counter 58, require 65, failed times 1: ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo oooxx xxxxx
2022-01-16 23:05:53 thread.c:1293:asic_status_monitor_thread: chain 0 can't get enough hashrate reg val for 0 times.
2022-01-16 23:05:53 thread.c:1273:asic_status_monitor_thread: ERROR: chain 0 get hashrate_reg_counter 58, require 65, failed times 1: ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo oooxx xxxxx
2022-01-16 23:05:55 thread.c:1293:asic_status_monitor_thread: chain 0 can't get enough hashrate reg val for 1 times.
2022-01-16 23:05:55 thread.c:1273:asic_status_monitor_thread: ERROR: chain 0 get hashrate_reg_counter 58, require 65, failed times 1: ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo oooxx xxxxx
2022-01-16 23:05:57 thread.c:1293:asic_status_monitor_thread: chain 0 can't get enough hashrate reg val for 2 times.
2022-01-16 23:05:57 thread.c:1273:asic_status_monitor_thread: ERROR: chain 0 get hashrate_reg_counter 58, require 65, failed times 1: ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo oooxx xxxxx
2022-01-16 23:05:59 thread.c:1293:asic_status_monitor_thread: chain 0 can't get enough hashrate reg val for 3 times.
2022-01-16 23:05:59 thread.c:1273:asic_status_monitor_thread: ERROR: chain 0 get hashrate_reg_counter 58, require 65, failed times 1: ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo oooxx xxxxx
2022-01-16 23:06:01 thread.c:1293:asic_status_monitor_thread: chain 0 can't get enough hashrate reg val for 4 times.
2022-01-16 23:06:01 thread.c:1273:asic_status_monitor_thread: ERROR: chain 0 get hashrate_reg_counter 58, require 65, failed times 1: ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo oooxx xxxxx
2022-01-16 23:06:03 thread.c:1293:asic_status_monitor_thread: chain 0 can't get enough hashrate reg val for 5 times.
2022-01-16 23:06:03 thread.c:1273:asic_status_monitor_thread: ERROR: chain 0 get hashrate_reg_counter 58, require 65, failed times 1: ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo oooxx xxxxx
2022-01-16 23:06:05 thread.c:1293:asic_status_monitor_thread: chain 0 can't get enough hashrate reg val for 6 times.
2022-01-16 23:06:05 thread.c:1273:asic_status_monitor_thread: ERROR: chain 0 get hashrate_reg_counter 58, require 65, failed times 1: ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo oooxx xxxxx
2022-01-16 23:06:07 thread.c:1293:asic_status_monitor_thread: chain 0 can't get enough hashrate reg val for 7 times.
2022-01-16 23:06:07 thread.c:1273:asic_status_monitor_thread: ERROR: chain 0 get hashrate_reg_counter 58, require 65, failed times 1: ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo oooxx xxxxx
2022-01-16 23:06:09 thread.c:1293:asic_status_monitor_thread: chain 0 can't get enough hashrate reg val for 8 times.
2022-01-16 23:06:09 thread.c:1273:asic_status_monitor_thread: ERROR: chain 0 get hashrate_reg_counter 58, require 65, failed times 1: ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo oooxx xxxxx
2022-01-16 23:06:11 thread.c:1293:asic_status_monitor_thread: chain 0 can't get enough hashrate reg val for 9 times.
2022-01-16 23:06:11 thread.c:1273:asic_status_monitor_thread: ERROR: chain 0 get hashrate_reg_counter 58, require 65, failed times 1: ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo oooxx xxxxx
2022-01-16 23:06:13 thread.c:1293:asic_status_monitor_thread: chain 0 can't get enough hashrate reg val for 10 times.
2022-01-16 23:06:13 thread.c:1273:asic_status_monitor_thread: ERROR: chain 0 get hashrate_reg_counter 58, require 65, failed times 1: ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo oooxx xxxxx
2022-01-16 23:06:15 thread.c:1293:asic_status_monitor_thread: chain 0 can't get enough hashrate reg val for 11 times.
2022-01-16 23:06:15 thread.c:1273:asic_status_monitor_thread: ERROR: chain 0 get hashrate_reg_counter 58, require 65, failed times 1: ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo oooxx xxxxx
2022-01-16 23:06:17 thread.c:1293:asic_status_monitor_thread: chain 0 can't get enough hashrate reg val for 12 times.
2022-01-16 23:06:17 thread.c:1273:asic_status_monitor_thread: ERROR: chain 0 get hashrate_reg_counter 58, require 65, failed times 1: ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo oooxx xxxxx
2022-01-16 23:06:19 thread.c:1293:asic_status_monitor_thread: chain 0 can't get enough hashrate reg val for 13 times.
2022-01-16 23:06:19 thread.c:1273:asic_status_monitor_thread: ERROR: chain 0 get hashrate_reg_counter 58, require 65, failed times 1: ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo oooxx xxxxx
2022-01-16 23:06:21 thread.c:1293:asic_status_monitor_thread: chain 0 can't get enough hashrate reg val for 14 times.
2022-01-16 23:06:21 thread.c:1273:asic_status_monitor_thread: ERROR: chain 0 get hashrate_reg_counter 58, require 65, failed times 1: ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo oooxx xxxxx
2022-01-16 23:06:23 thread.c:1293:asic_status_monitor_thread: chain 0 can't get enough hashrate reg val for 15 times.
2022-01-16 23:06:23 thread.c:1273:asic_status_monitor_thread: ERROR: chain 0 get hashrate_reg_counter 58, require 65, failed times 1: ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo oooxx xxxxx
2022-01-16 23:06:25 thread.c:1293:asic_status_monitor_thread: chain 0 can't get enough hashrate reg val for 16 times.
2022-01-16 23:06:25 thread.c:1273:asic_status_monitor_thread: ERROR: chain 0 get hashrate_reg_counter 58, require 65, failed times 1: ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo oooxx xxxxx
2022-01-16 23:06:27 thread.c:1293:asic_status_monitor_thread: chain 0 can't get enough hashrate reg val for 17 times.
2022-01-16 23:06:27 thread.c:1273:asic_status_monitor_thread: ERROR: chain 0 get hashrate_reg_counter 58, require 65, failed times 1: ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo oooxx xxxxx
2022-01-16 23:06:29 thread.c:1293:asic_status_monitor_thread: chain 0 can't get enough hashrate reg val for 18 times.
2022-01-16 23:06:29 thread.c:1273:asic_status_monitor_thread: ERROR: chain 0 get hashrate_reg_counter 58, require 65, failed times 1: ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo oooxx xxxxx
2022-01-16 23:06:31 thread.c:1293:asic_status_monitor_thread: chain 0 can't get enough hashrate reg val for 19 times.
2022-01-16 23:06:31 thread.c:1273:asic_status_monitor_thread: ERROR: chain 0 get hashrate_reg_counter 58, require 65, failed times 1: ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo oooxx xxxxx
2022-01-16 23:06:33 thread.c:1293:asic_status_monitor_thread: chain 0 can't get enough hashrate reg val for 20 times.
2022-01-16 23:06:33 thread.c:1273:asic_status_monitor_thread: ERROR: chain 0 get hashrate_reg_counter 58, require 65, failed times 1: ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo oooxx xxxxx
2022-01-16 23:06:35 thread.c:1293:asic_status_monitor_thread: chain 0 can't get enough hashrate reg val for 21 times.
2022-01-16 23:06:35 thread.c:1273:asic_status_monitor_thread: ERROR: chain 0 get hashrate_reg_counter 58, require 65, failed times 1: ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo oooxx xxxxx
2022-01-16 23:06:37 thread.c:1293:asic_status_monitor_thread: chain 0 can't get enough hashrate reg val for 22 times.
2022-01-16 23:06:37 thread.c:1273:asic_status_monitor_thread: ERROR: chain 0 get hashrate_reg_counter 58, require 65, failed times 1: ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo oooxx xxxxx
2022-01-16 23:06:39 thread.c:1293:asic_status_monitor_thread: chain 0 can't get enough hashrate reg val for 23 times.
2022-01-16 23:06:39 thread.c:1273:asic_status_monitor_thread: ERROR: chain 0 get hashrate_reg_counter 58, require 65, failed times 1: ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo oooxx xxxxx
2022-01-16 23:06:41 thread.c:1293:asic_status_monitor_thread: chain 0 can't get enough hashrate reg val for 24 times.
2022-01-16 23:06:41 thread.c:1273:asic_status_monitor_thread: ERROR: chain 0 get hashrate_reg_counter 58, require 65, failed times 1: ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo oooxx xxxxx
2022-01-16 23:06:43 thread.c:1293:asic_status_monitor_thread: chain 0 can't get enough hashrate reg val for 25 times.
2022-01-16 23:06:43 thread.c:1273:asic_status_monitor_thread: ERROR: chain 0 get hashrate_reg_counter 58, require 65, failed times 1: ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo oooxx xxxxx
2022-01-16 23:06:45 thread.c:1293:asic_status_monitor_thread: chain 0 can't get enough hashrate reg val for 26 times.
2022-01-16 23:06:45 thread.c:1273:asic_status_monitor_thread: ERROR: chain 0 get hashrate_reg_counter 58, require 65, failed times 1: ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo oooxx xxxxx
2022-01-16 23:06:47 thread.c:1293:asic_status_monitor_thread: chain 0 can't get enough hashrate reg val for 27 times.
2022-01-16 23:06:47 thread.c:1273:asic_status_monitor_thread: ERROR: chain 0 get hashrate_reg_counter 58, require 65, failed times 1: ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo oooxx xxxxx
2022-01-16 23:06:49 thread.c:1293:asic_status_monitor_thread: chain 0 can't get enough hashrate reg val for 28 times.
2022-01-16 23:06:49 thread.c:1273:asic_status_monitor_thread: ERROR: chain 0 get hashrate_reg_counter 58, require 65, failed times 1: ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo oooxx xxxxx
2022-01-16 23:06:51 thread.c:1293:asic_status_monitor_thread: chain 0 can't get enough hashrate reg val for 29 times.
2022-01-16 23:06:51 thread.c:1297:asic_status_monitor_thread: chain 0 can't get enough hashrate reg val for 30 times, power off.
2022-01-16 23:06:52 frequency.c:205:get_ideal_hash_rate_GH: ideal_hash_rate = 24189
2022-01-16 23:06:52 frequency.c:223:get_sale_hash_rate_GH: sale_hash_rate = 22000
wndsnb
hero member
Activity: 544
Merit: 589
Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
January 16, 2022, 08:49:17 AM
#401
It looks like you have 2 bad hashboards that need repair.

The 0V reading is not the issue, there is just a delay between the hashboard reading the voltage, and the psu setting it.

The chain[1] board in the 1st log is reading incorrect voltage, the 22V reading is not correct. All 3 hashboards are actually reading the same exact voltage, the one delivered by the busbars. Could be an issue with the pic microcontroller.

Quote from: DwarfNo3 on January 16, 2022, 02:57:31 AM
Code:
2022-01-16 07:49:13 power_api.c:110:check_voltage: target_vol = 17.00, actural_vol = 18.82, more than 1.0v diff.
2022-01-16 07:49:14 power_api.c:124:check_voltage_multi: retry time: 2

...

2022-01-16 07:52:38 power_api.c:124:check_voltage_multi: retry time: 29
2022-01-16 07:52:40 power_api.c:86:get_average_voltage: chain[0], voltage is: 17.089424
2022-01-16 07:52:43 power_api.c:86:get_average_voltage: chain[1], voltage is: 22.385859
2022-01-16 07:52:46 power_api.c:86:get_average_voltage: chain[2], voltage is: 16.997578
2022-01-16 07:52:46 power_api.c:97:get_average_voltage: aveage voltage is: 18.824287
2022-01-16 07:52:46 power_api.c:110:check_voltage: target_vol = 17.00, actural_vol = 18.82, more than 1.0v diff.
2022-01-16 07:52:47 power_api.c:182:set_iic_power_by_voltage: now set voltage to : 17.000000
2022-01-16 07:52:47 driver-btm-api.c:205:set_miner_status: ERROR_POWER_LOST
2022-01-16 07:52:47 driver-btm-api.c:146:stop_mining: stop mining: power set failed!

The chain[1] board in the 2nd log is measuring the voltage correctly, but not finding any ASICs, so there is likely a bad solder connection somewhere on the board. The "find 0 asic" log entry is the issue.

Quote from: DwarfNo3 on January 16, 2022, 03:08:12 AM
Code:
2022-01-16 08:05:00 power_api.c:232:set_iic_power_to_highest_voltage: setting to voltage: 17.00 ...
2022-01-16 08:05:06 power_api.c:124:check_voltage_multi: retry time: 0
2022-01-16 08:05:08 power_api.c:86:get_average_voltage: chain[0], voltage is: 0.067354
2022-01-16 08:05:10 power_api.c:86:get_average_voltage: chain[1], voltage is: 17.034316
2022-01-16 08:05:11 power_api.c:86:get_average_voltage: chain[2], voltage is: 16.905732
2022-01-16 08:05:11 power_api.c:97:get_average_voltage: aveage voltage is: 11.335801
2022-01-16 08:05:11 power_api.c:110:check_voltage: target_vol = 17.00, actural_vol = 11.34, more than 1.0v diff.
2022-01-16 08:05:12 power_api.c:124:check_voltage_multi: retry time: 1
2022-01-16 08:05:14 power_api.c:86:get_average_voltage: chain[0], voltage is: 17.046562
2022-01-16 08:05:16 power_api.c:86:get_average_voltage: chain[1], voltage is: 17.015947
2022-01-16 08:05:19 power_api.c:86:get_average_voltage: chain[2], voltage is: 16.924101
2022-01-16 08:05:19 power_api.c:97:get_average_voltage: aveage voltage is: 16.995537
2022-01-16 08:05:19 power_api.c:182:set_iic_power_by_voltage: now set voltage to : 17.000000
2022-01-16 08:05:19 uart.c:80:set_baud: set fpga_baud = 115200, fpga_divider = 26
2022-01-16 08:05:29 driver-btm-api.c:1042:check_asic_number_with_power_on: Chain[0]: find 30 asic, times 0
2022-01-16 08:05:39 driver-btm-api.c:1042:check_asic_number_with_power_on: Chain[1]: find 0 asic, times 0
2022-01-16 08:05:48 driver-btm-api.c:1042:check_asic_number_with_power_on: Chain[1]: find 0 asic, times 1
2022-01-16 08:05:59 driver-btm-api.c:1042:check_asic_number_with_power_on: Chain[1]: find 0 asic, times 2
2022-01-16 08:05:59 driver-btm-api.c:1069:check_asic_number: Chain 1 only find 0 asic, will power off hash board 1
2022-01-16 08:06:11 driver-btm-api.c:1042:check_asic_number_with_power_on: Chain[2]: find 30 asic, times 0
DwarfNo3
newbie
Activity: 5
Merit: 0
Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
January 16, 2022, 03:08:12 AM
#400
and when I swap the hasboard with 22 volts another hashboard goes to 0 volts. So it's probably both PSUs? (both are used)

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: 203752K/245760K available (6345K kernel code, 231K rwdata, 1896K rodata, 1024K init, 223K bss, 25624K 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
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: 12584K (cceb7000 - 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 MT29F2G08ABAEAWP
nand: 256 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 64
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: 6/2, WL threshold: 4096, image sequence number: 638989880
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 6593BA4D-00F7-467B-9E0A-A2198CBE84FF, 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: 12/7, WL threshold: 4096, image sequence number: 100324054
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): 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 058C0E40-6EAA-4676-9C52-F694F6D34F3B, 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 0xcfb38000
*base_vir_addr = 0xfb013
In fpga mem driver!
request_mem_region OK!
fpga mem virtual address is 0xd2000000
2022-01-16 08:03:59 driver-btm-api.c:663:init_freq_mode: This is scan-user version
2022-01-16 08:03:59 driver-btm-api.c:2028:bitmain_soc_init: opt_multi_version     = 1
2022-01-16 08:03:59 driver-btm-api.c:2029:bitmain_soc_init: opt_bitmain_ab        = 1
2022-01-16 08:03:59 driver-btm-api.c:2030:bitmain_soc_init: opt_bitmain_work_mode = 0
2022-01-16 08:03:59 driver-btm-api.c:2031:bitmain_soc_init: Miner compile time: Thu Apr 23 16:29:07 CST 2020 type: Antminer T17
2022-01-16 08:03:59 driver-btm-api.c:2032:bitmain_soc_init: commit version: 1c5be6f 2020-04-20 16:18:14, build by: lol 2020-04-23 16:35:04
2022-01-16 08:03:59 driver-btm-api.c:1844:show_sn: no SN got, please write SN to /nvdata/sn
2022-01-16 08:03:59 driver-btm-api.c:1167:miner_device_init: Detect 256MB control board of XILINX
2022-01-16 08:03:59 driver-btm-api.c:1115:init_fan_parameter: fan_eft : 0  fan_pwm : 0
2022-01-16 08:03:59 thread.c:885:create_read_nonce_reg_thread: create thread
2022-01-16 08:04:05 driver-btm-api.c:1099:init_miner_version: miner ID : 8072d5025c20885c
2022-01-16 08:04:05 driver-btm-api.c:1105:init_miner_version: FPGA Version = 0xB013
2022-01-16 08:04:07 eeprom.c:431:check_pattern_test_level: L1 board
2022-01-16 08:04:09 eeprom.c:431:check_pattern_test_level: L1 board
2022-01-16 08:04:11 eeprom.c:431:check_pattern_test_level: L1 board
2022-01-16 08:04:11 driver-btm-api.c:737:get_product_id: product_id[0] = 1
2022-01-16 08:04:11 driver-btm-api.c:737:get_product_id: product_id[1] = 1
2022-01-16 08:04:11 driver-btm-api.c:737:get_product_id: product_id[2] = 1
2022-01-16 08:04:11 driver-btm-api.c:1666:get_ccdly_opt: ccdly_opt[0] = 1
2022-01-16 08:04:11 driver-btm-api.c:1666:get_ccdly_opt: ccdly_opt[1] = 1
2022-01-16 08:04:11 driver-btm-api.c:1666:get_ccdly_opt: ccdly_opt[2] = 1
2022-01-16 08:04:11 driver-btm-api.c:1919:bitmain_board_init: g_ccdly_opt = 1
2022-01-16 08:04:11 driver-btm-api.c:676:_set_project_type: project:2
2022-01-16 08:04:11 driver-btm-api.c:706:_set_project_type: Project type: Antminer T17
2022-01-16 08:04:11 driver-btm-api.c:717:dump_pcb_bom_version: Chain [0] PCB Version: 0x0100
2022-01-16 08:04:11 driver-btm-api.c:718:dump_pcb_bom_version: Chain [0] BOM Version: 0x0100
2022-01-16 08:04:11 driver-btm-api.c:717:dump_pcb_bom_version: Chain [1] PCB Version: 0x0100
2022-01-16 08:04:11 driver-btm-api.c:718:dump_pcb_bom_version: Chain [1] BOM Version: 0x0100
2022-01-16 08:04:11 driver-btm-api.c:717:dump_pcb_bom_version: Chain [2] PCB Version: 0x0100
2022-01-16 08:04:11 driver-btm-api.c:718:dump_pcb_bom_version: Chain [2] BOM Version: 0x0100
2022-01-16 08:04:13 driver-btm-api.c:1939:bitmain_board_init: Fan check passed.
2022-01-16 08:04:14 board.c:36:jump_and_app_check_restore_pic: chain[0] PIC jump to app
2022-01-16 08:04:18 board.c:40:jump_and_app_check_restore_pic: Check chain[0] PIC fw version=0xb9
2022-01-16 08:04:20 board.c:36:jump_and_app_check_restore_pic: chain[1] PIC jump to app
2022-01-16 08:04:23 board.c:40:jump_and_app_check_restore_pic: Check chain[1] PIC fw version=0xb9
2022-01-16 08:04:25 board.c:36:jump_and_app_check_restore_pic: chain[2] PIC jump to app
2022-01-16 08:04:28 board.c:40:jump_and_app_check_restore_pic: Check chain[2] PIC fw version=0xb9
2022-01-16 08:04:28 thread.c:880:create_pic_heart_beat_thread: create thread
2022-01-16 08:04:28 power_api.c:55:power_init: power init ...
2022-01-16 08:04:28 driver-btm-api.c:1949:bitmain_board_init: Enter 30s sleep to make sure power release finish.
2022-01-16 08:04:28 power_api.c:46:power_off: init gpio907
2022-01-16 08:05:00 power_api.c:232:set_iic_power_to_highest_voltage: setting to voltage: 17.00 ...
2022-01-16 08:05:06 power_api.c:124:check_voltage_multi: retry time: 0
2022-01-16 08:05:08 power_api.c:86:get_average_voltage: chain[0], voltage is: 0.067354
2022-01-16 08:05:10 power_api.c:86:get_average_voltage: chain[1], voltage is: 17.034316
2022-01-16 08:05:11 power_api.c:86:get_average_voltage: chain[2], voltage is: 16.905732
2022-01-16 08:05:11 power_api.c:97:get_average_voltage: aveage voltage is: 11.335801
2022-01-16 08:05:11 power_api.c:110:check_voltage: target_vol = 17.00, actural_vol = 11.34, more than 1.0v diff.
2022-01-16 08:05:12 power_api.c:124:check_voltage_multi: retry time: 1
2022-01-16 08:05:14 power_api.c:86:get_average_voltage: chain[0], voltage is: 17.046562
2022-01-16 08:05:16 power_api.c:86:get_average_voltage: chain[1], voltage is: 17.015947
2022-01-16 08:05:19 power_api.c:86:get_average_voltage: chain[2], voltage is: 16.924101
2022-01-16 08:05:19 power_api.c:97:get_average_voltage: aveage voltage is: 16.995537
2022-01-16 08:05:19 power_api.c:182:set_iic_power_by_voltage: now set voltage to : 17.000000
2022-01-16 08:05:19 uart.c:80:set_baud: set fpga_baud = 115200, fpga_divider = 26
2022-01-16 08:05:29 driver-btm-api.c:1042:check_asic_number_with_power_on: Chain[0]: find 30 asic, times 0
2022-01-16 08:05:39 driver-btm-api.c:1042:check_asic_number_with_power_on: Chain[1]: find 0 asic, times 0
2022-01-16 08:05:48 driver-btm-api.c:1042:check_asic_number_with_power_on: Chain[1]: find 0 asic, times 1
2022-01-16 08:05:59 driver-btm-api.c:1042:check_asic_number_with_power_on: Chain[1]: find 0 asic, times 2
2022-01-16 08:05:59 driver-btm-api.c:1069:check_asic_number: Chain 1 only find 0 asic, will power off hash board 1
2022-01-16 08:06:11 driver-btm-api.c:1042:check_asic_number_with_power_on: Chain[2]: find 30 asic, times 0
2022-01-16 08:06:13 driver-btm-api.c:352:set_order_clock: chain[0]: set order clock, stragegy 3 clock_en=0x1
2022-01-16 08:06:13 driver-btm-api.c:352:set_order_clock: chain[2]: set order clock, stragegy 3 clock_en=0x1
2022-01-16 08:06:13 driver-hash-chip.c:502:set_clock_delay_control: core_data = 0xb4
2022-01-16 08:06:13 uart.c:80:set_baud: set fpga_baud = 3000000, fpga_divider = 0
2022-01-16 08:06:13 driver-btm-api.c:1693:check_clock_counter: freq 50 clock_counter_limit 6
2022-01-16 08:06:14 register.c:1416:quick_dump_core_hash_clock_counter: bad clock counter. chain = 2, asic = 21, core = 105, found 1, clock counter 0x00340000
2022-01-16 08:06:14 uart.c:80:set_baud: set fpga_baud = 115200, fpga_divider = 26
2022-01-16 08:06:14 driver-btm-api.c:1981:bitmain_board_init: clock counter status was not good. Try reset.
DwarfNo3
newbie
Activity: 5
Merit: 0
Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
January 16, 2022, 02:57:31 AM
#399
Thank you wndsnb for your reply,

sorry I forgot to mention that I did swap the PSU and nothing changed. what I meant with the metal brackets are the ones that connect the psu with the hashboard I thought they only help keep them in place, but it seems there is something that affects the electric.

Here is the kernel log with 3 hashboards connected:

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: 203752K/245760K available (6345K kernel code, 231K rwdata, 1896K rodata, 1024K init, 223K bss, 25624K 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
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: 12584K (cceb7000 - 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 MT29F2G08ABAEAWP
nand: 256 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 64
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: 6/2, WL threshold: 4096, image sequence number: 638989880
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 6593BA4D-00F7-467B-9E0A-A2198CBE84FF, 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: 11/7, WL threshold: 4096, image sequence number: 100324054
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): 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 058C0E40-6EAA-4676-9C52-F694F6D34F3B, 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 0xcfb38000
*base_vir_addr = 0xfb013
In fpga mem driver!
request_mem_region OK!
fpga mem virtual address is 0xd2000000
random: nonblocking pool is initialized
Jan 16 07:52:23 (none) user.notice kernel: random: nonblocking pool is initialized
2022-01-16 07:47:52 driver-btm-api.c:663:init_freq_mode: This is scan-user version
2022-01-16 07:47:52 driver-btm-api.c:2028:bitmain_soc_init: opt_multi_version     = 1
2022-01-16 07:47:52 driver-btm-api.c:2029:bitmain_soc_init: opt_bitmain_ab        = 1
2022-01-16 07:47:52 driver-btm-api.c:2030:bitmain_soc_init: opt_bitmain_work_mode = 0
2022-01-16 07:47:52 driver-btm-api.c:2031:bitmain_soc_init: Miner compile time: Thu Apr 23 16:29:07 CST 2020 type: Antminer T17
2022-01-16 07:47:52 driver-btm-api.c:2032:bitmain_soc_init: commit version: 1c5be6f 2020-04-20 16:18:14, build by: lol 2020-04-23 16:35:04
2022-01-16 07:47:52 driver-btm-api.c:1844:show_sn: no SN got, please write SN to /nvdata/sn
2022-01-16 07:47:52 driver-btm-api.c:1167:miner_device_init: Detect 256MB control board of XILINX
2022-01-16 07:47:52 driver-btm-api.c:1115:init_fan_parameter: fan_eft : 0  fan_pwm : 0
2022-01-16 07:47:52 thread.c:885:create_read_nonce_reg_thread: create thread
2022-01-16 07:47:58 driver-btm-api.c:1099:init_miner_version: miner ID : 8072d5025c20885c
2022-01-16 07:47:58 driver-btm-api.c:1105:init_miner_version: FPGA Version = 0xB013
2022-01-16 07:48:00 eeprom.c:431:check_pattern_test_level: L1 board
2022-01-16 07:48:01 eeprom.c:431:check_pattern_test_level: L1 board
2022-01-16 07:48:03 eeprom.c:431:check_pattern_test_level: L1 board
2022-01-16 07:48:03 driver-btm-api.c:737:get_product_id: product_id[0] = 1
2022-01-16 07:48:03 driver-btm-api.c:737:get_product_id: product_id[1] = 1
2022-01-16 07:48:03 driver-btm-api.c:737:get_product_id: product_id[2] = 1
2022-01-16 07:48:03 driver-btm-api.c:1666:get_ccdly_opt: ccdly_opt[0] = 1
2022-01-16 07:48:03 driver-btm-api.c:1666:get_ccdly_opt: ccdly_opt[1] = 1
2022-01-16 07:48:03 driver-btm-api.c:1666:get_ccdly_opt: ccdly_opt[2] = 1
2022-01-16 07:48:03 driver-btm-api.c:1919:bitmain_board_init: g_ccdly_opt = 1
2022-01-16 07:48:03 driver-btm-api.c:676:_set_project_type: project:2
2022-01-16 07:48:03 driver-btm-api.c:706:_set_project_type: Project type: Antminer T17
2022-01-16 07:48:03 driver-btm-api.c:717:dump_pcb_bom_version: Chain [0] PCB Version: 0x0100
2022-01-16 07:48:03 driver-btm-api.c:718:dump_pcb_bom_version: Chain [0] BOM Version: 0x0100
2022-01-16 07:48:03 driver-btm-api.c:717:dump_pcb_bom_version: Chain [1] PCB Version: 0x0100
2022-01-16 07:48:03 driver-btm-api.c:718:dump_pcb_bom_version: Chain [1] BOM Version: 0x0100
2022-01-16 07:48:03 driver-btm-api.c:717:dump_pcb_bom_version: Chain [2] PCB Version: 0x0100
2022-01-16 07:48:03 driver-btm-api.c:718:dump_pcb_bom_version: Chain [2] BOM Version: 0x0100
2022-01-16 07:48:06 driver-btm-api.c:1939:bitmain_board_init: Fan check passed.
2022-01-16 07:48:08 board.c:36:jump_and_app_check_restore_pic: chain[0] PIC jump to app
2022-01-16 07:48:11 board.c:40:jump_and_app_check_restore_pic: Check chain[0] PIC fw version=0xb9
2022-01-16 07:48:13 board.c:36:jump_and_app_check_restore_pic: chain[1] PIC jump to app
2022-01-16 07:48:17 board.c:40:jump_and_app_check_restore_pic: Check chain[1] PIC fw version=0xb9
2022-01-16 07:48:18 board.c:36:jump_and_app_check_restore_pic: chain[2] PIC jump to app
2022-01-16 07:48:22 board.c:40:jump_and_app_check_restore_pic: Check chain[2] PIC fw version=0xb9
2022-01-16 07:48:22 thread.c:880:create_pic_heart_beat_thread: create thread
2022-01-16 07:48:22 power_api.c:55:power_init: power init ...
2022-01-16 07:48:22 driver-btm-api.c:1949:bitmain_board_init: Enter 30s sleep to make sure power release finish.
2022-01-16 07:48:22 power_api.c:46:power_off: init gpio907
2022-01-16 07:48:54 power_api.c:232:set_iic_power_to_highest_voltage: setting to voltage: 17.00 ...
2022-01-16 07:49:00 power_api.c:124:check_voltage_multi: retry time: 0
2022-01-16 07:49:01 power_api.c:86:get_average_voltage: chain[0], voltage is: 0.061230
2022-01-16 07:49:03 power_api.c:86:get_average_voltage: chain[1], voltage is: 22.398105
2022-01-16 07:49:05 power_api.c:86:get_average_voltage: chain[2], voltage is: 16.966963
2022-01-16 07:49:05 power_api.c:97:get_average_voltage: aveage voltage is: 13.142099
2022-01-16 07:49:05 power_api.c:110:check_voltage: target_vol = 17.00, actural_vol = 13.14, more than 1.0v diff.
2022-01-16 07:49:06 power_api.c:124:check_voltage_multi: retry time: 1
2022-01-16 07:49:08 power_api.c:86:get_average_voltage: chain[0], voltage is: 17.064931
2022-01-16 07:49:09 power_api.c:86:get_average_voltage: chain[1], voltage is: 22.391982
2022-01-16 07:49:13 power_api.c:86:get_average_voltage: chain[2], voltage is: 16.991455
2022-01-16 07:49:13 power_api.c:97:get_average_voltage: aveage voltage is: 18.816123
2022-01-16 07:49:13 power_api.c:110:check_voltage: target_vol = 17.00, actural_vol = 18.82, more than 1.0v diff.
2022-01-16 07:49:14 power_api.c:124:check_voltage_multi: retry time: 2
2022-01-16 07:49:16 power_api.c:86:get_average_voltage: chain[0], voltage is: 17.064931
2022-01-16 07:49:19 power_api.c:86:get_average_voltage: chain[1], voltage is: 22.391982
2022-01-16 07:49:21 power_api.c:86:get_average_voltage: chain[2], voltage is: 16.966963
2022-01-16 07:49:21 power_api.c:97:get_average_voltage: aveage voltage is: 18.807959
2022-01-16 07:49:21 power_api.c:110:check_voltage: target_vol = 17.00, actural_vol = 18.81, more than 1.0v diff.
2022-01-16 07:49:22 power_api.c:124:check_voltage_multi: retry time: 3
2022-01-16 07:49:23 power_api.c:86:get_average_voltage: chain[0], voltage is: 17.083301
2022-01-16 07:49:25 power_api.c:86:get_average_voltage: chain[1], voltage is: 22.379736
2022-01-16 07:49:27 power_api.c:86:get_average_voltage: chain[2], voltage is: 16.973086
2022-01-16 07:49:27 power_api.c:97:get_average_voltage: aveage voltage is: 18.812041
2022-01-16 07:49:27 power_api.c:110:check_voltage: target_vol = 17.00, actural_vol = 18.81, more than 1.0v diff.
2022-01-16 07:49:28 power_api.c:124:check_voltage_multi: retry time: 4
2022-01-16 07:49:31 power_api.c:86:get_average_voltage: chain[0], voltage is: 17.083301
2022-01-16 07:49:34 power_api.c:86:get_average_voltage: chain[1], voltage is: 22.379736
2022-01-16 07:49:37 power_api.c:86:get_average_voltage: chain[2], voltage is: 16.966963
2022-01-16 07:49:37 power_api.c:97:get_average_voltage: aveage voltage is: 18.810000
2022-01-16 07:49:37 power_api.c:110:check_voltage: target_vol = 17.00, actural_vol = 18.81, more than 1.0v diff.
2022-01-16 07:49:38 power_api.c:124:check_voltage_multi: retry time: 5
2022-01-16 07:49:40 power_api.c:86:get_average_voltage: chain[0], voltage is: 17.071054
2022-01-16 07:49:41 power_api.c:86:get_average_voltage: chain[1], voltage is: 22.385859
2022-01-16 07:49:43 power_api.c:86:get_average_voltage: chain[2], voltage is: 16.991455
2022-01-16 07:49:43 power_api.c:97:get_average_voltage: aveage voltage is: 18.816123
2022-01-16 07:49:43 power_api.c:110:check_voltage: target_vol = 17.00, actural_vol = 18.82, more than 1.0v diff.
2022-01-16 07:49:44 power_api.c:124:check_voltage_multi: retry time: 6
2022-01-16 07:49:46 power_api.c:86:get_average_voltage: chain[0], voltage is: 17.071054
2022-01-16 07:49:49 power_api.c:86:get_average_voltage: chain[1], voltage is: 22.367490
2022-01-16 07:49:52 power_api.c:86:get_average_voltage: chain[2], voltage is: 16.979209
2022-01-16 07:49:52 power_api.c:97:get_average_voltage: aveage voltage is: 18.805918
2022-01-16 07:49:52 power_api.c:110:check_voltage: target_vol = 17.00, actural_vol = 18.81, more than 1.0v diff.
2022-01-16 07:49:53 power_api.c:124:check_voltage_multi: retry time: 7
2022-01-16 07:49:55 power_api.c:86:get_average_voltage: chain[0], voltage is: 17.064931
2022-01-16 07:49:57 power_api.c:86:get_average_voltage: chain[1], voltage is: 22.379736
2022-01-16 07:49:59 power_api.c:86:get_average_voltage: chain[2], voltage is: 16.979209
2022-01-16 07:49:59 power_api.c:97:get_average_voltage: aveage voltage is: 18.807959
2022-01-16 07:49:59 power_api.c:110:check_voltage: target_vol = 17.00, actural_vol = 18.81, more than 1.0v diff.
2022-01-16 07:50:00 power_api.c:124:check_voltage_multi: retry time: 8
2022-01-16 07:50:02 power_api.c:86:get_average_voltage: chain[0], voltage is: 17.083301
2022-01-16 07:50:04 power_api.c:86:get_average_voltage: chain[1], voltage is: 22.373613
2022-01-16 07:50:05 power_api.c:86:get_average_voltage: chain[2], voltage is: 16.997578
2022-01-16 07:50:05 power_api.c:97:get_average_voltage: aveage voltage is: 18.818164
2022-01-16 07:50:05 power_api.c:110:check_voltage: target_vol = 17.00, actural_vol = 18.82, more than 1.0v diff.
2022-01-16 07:50:06 power_api.c:124:check_voltage_multi: retry time: 9
2022-01-16 07:50:08 power_api.c:86:get_average_voltage: chain[0], voltage is: 17.071054
2022-01-16 07:50:12 power_api.c:86:get_average_voltage: chain[1], voltage is: 22.379736
2022-01-16 07:50:15 power_api.c:86:get_average_voltage: chain[2], voltage is: 16.991455
2022-01-16 07:50:15 power_api.c:97:get_average_voltage: aveage voltage is: 18.814082
2022-01-16 07:50:15 power_api.c:110:check_voltage: target_vol = 17.00, actural_vol = 18.81, more than 1.0v diff.
2022-01-16 07:50:16 power_api.c:124:check_voltage_multi: retry time: 10
2022-01-16 07:50:18 power_api.c:86:get_average_voltage: chain[0], voltage is: 17.071054
2022-01-16 07:50:19 power_api.c:86:get_average_voltage: chain[1], voltage is: 22.379736
2022-01-16 07:50:21 power_api.c:86:get_average_voltage: chain[2], voltage is: 16.979209
2022-01-16 07:50:21 power_api.c:97:get_average_voltage: aveage voltage is: 18.810000
2022-01-16 07:50:21 power_api.c:110:check_voltage: target_vol = 17.00, actural_vol = 18.81, more than 1.0v diff.
2022-01-16 07:50:22 power_api.c:124:check_voltage_multi: retry time: 11
2022-01-16 07:50:24 power_api.c:86:get_average_voltage: chain[0], voltage is: 17.071054
2022-01-16 07:50:27 power_api.c:86:get_average_voltage: chain[1], voltage is: 22.373613
2022-01-16 07:50:30 power_api.c:86:get_average_voltage: chain[2], voltage is: 16.985332
2022-01-16 07:50:30 power_api.c:97:get_average_voltage: aveage voltage is: 18.810000
2022-01-16 07:50:30 power_api.c:110:check_voltage: target_vol = 17.00, actural_vol = 18.81, more than 1.0v diff.
2022-01-16 07:50:31 power_api.c:124:check_voltage_multi: retry time: 12
2022-01-16 07:50:33 power_api.c:86:get_average_voltage: chain[0], voltage is: 17.077178
2022-01-16 07:50:35 power_api.c:86:get_average_voltage: chain[1], voltage is: 22.398105
2022-01-16 07:50:37 power_api.c:86:get_average_voltage: chain[2], voltage is: 16.979209
2022-01-16 07:50:37 power_api.c:97:get_average_voltage: aveage voltage is: 18.818164
2022-01-16 07:50:37 power_api.c:110:check_voltage: target_vol = 17.00, actural_vol = 18.82, more than 1.0v diff.
2022-01-16 07:50:38 power_api.c:124:check_voltage_multi: retry time: 13
2022-01-16 07:50:40 power_api.c:86:get_average_voltage: chain[0], voltage is: 17.101670
2022-01-16 07:50:41 power_api.c:86:get_average_voltage: chain[1], voltage is: 22.398105
2022-01-16 07:50:43 power_api.c:86:get_average_voltage: chain[2], voltage is: 16.979209
2022-01-16 07:50:43 power_api.c:97:get_average_voltage: aveage voltage is: 18.826328
2022-01-16 07:50:43 power_api.c:110:check_voltage: target_vol = 17.00, actural_vol = 18.83, more than 1.0v diff.
2022-01-16 07:50:44 power_api.c:124:check_voltage_multi: retry time: 14
2022-01-16 07:50:46 power_api.c:86:get_average_voltage: chain[0], voltage is: 17.089424
2022-01-16 07:50:49 power_api.c:86:get_average_voltage: chain[1], voltage is: 22.391982
2022-01-16 07:50:53 power_api.c:86:get_average_voltage: chain[2], voltage is: 16.979209
2022-01-16 07:50:53 power_api.c:97:get_average_voltage: aveage voltage is: 18.820205
2022-01-16 07:50:53 power_api.c:110:check_voltage: target_vol = 17.00, actural_vol = 18.82, more than 1.0v diff.
2022-01-16 07:50:54 power_api.c:124:check_voltage_multi: retry time: 15
2022-01-16 07:50:55 power_api.c:86:get_average_voltage: chain[0], voltage is: 17.089424
2022-01-16 07:50:57 power_api.c:86:get_average_voltage: chain[1], voltage is: 22.391982
2022-01-16 07:50:59 power_api.c:86:get_average_voltage: chain[2], voltage is: 16.997578
2022-01-16 07:50:59 power_api.c:97:get_average_voltage: aveage voltage is: 18.826328
2022-01-16 07:50:59 power_api.c:110:check_voltage: target_vol = 17.00, actural_vol = 18.83, more than 1.0v diff.
2022-01-16 07:51:00 power_api.c:124:check_voltage_multi: retry time: 16
2022-01-16 07:51:02 power_api.c:86:get_average_voltage: chain[0], voltage is: 17.052685
2022-01-16 07:51:05 power_api.c:86:get_average_voltage: chain[1], voltage is: 22.398105
2022-01-16 07:51:08 power_api.c:86:get_average_voltage: chain[2], voltage is: 16.966963
2022-01-16 07:51:08 power_api.c:97:get_average_voltage: aveage voltage is: 18.805918
2022-01-16 07:51:08 power_api.c:110:check_voltage: target_vol = 17.00, actural_vol = 18.81, more than 1.0v diff.
2022-01-16 07:51:09 power_api.c:124:check_voltage_multi: retry time: 17
2022-01-16 07:51:11 power_api.c:86:get_average_voltage: chain[0], voltage is: 17.071054
2022-01-16 07:51:13 power_api.c:86:get_average_voltage: chain[1], voltage is: 22.379736
2022-01-16 07:51:15 power_api.c:86:get_average_voltage: chain[2], voltage is: 16.973086
2022-01-16 07:51:15 power_api.c:97:get_average_voltage: aveage voltage is: 18.807959
2022-01-16 07:51:15 power_api.c:110:check_voltage: target_vol = 17.00, actural_vol = 18.81, more than 1.0v diff.
2022-01-16 07:51:16 power_api.c:124:check_voltage_multi: retry time: 18
2022-01-16 07:51:17 power_api.c:86:get_average_voltage: chain[0], voltage is: 17.083301
2022-01-16 07:51:19 power_api.c:86:get_average_voltage: chain[1], voltage is: 22.391982
2022-01-16 07:51:21 power_api.c:86:get_average_voltage: chain[2], voltage is: 16.973086
2022-01-16 07:51:21 power_api.c:97:get_average_voltage: aveage voltage is: 18.816123
2022-01-16 07:51:21 power_api.c:110:check_voltage: target_vol = 17.00, actural_vol = 18.82, more than 1.0v diff.
2022-01-16 07:51:22 power_api.c:124:check_voltage_multi: retry time: 19
2022-01-16 07:51:24 power_api.c:86:get_average_voltage: chain[0], voltage is: 17.077178
2022-01-16 07:51:27 power_api.c:86:get_average_voltage: chain[1], voltage is: 22.385859
2022-01-16 07:51:30 power_api.c:86:get_average_voltage: chain[2], voltage is: 16.966963
2022-01-16 07:51:30 power_api.c:97:get_average_voltage: aveage voltage is: 18.810000
2022-01-16 07:51:30 power_api.c:110:check_voltage: target_vol = 17.00, actural_vol = 18.81, more than 1.0v diff.
2022-01-16 07:51:31 power_api.c:124:check_voltage_multi: retry time: 20
2022-01-16 07:51:33 power_api.c:86:get_average_voltage: chain[0], voltage is: 17.064931
2022-01-16 07:51:35 power_api.c:86:get_average_voltage: chain[1], voltage is: 22.373613
2022-01-16 07:51:37 power_api.c:86:get_average_voltage: chain[2], voltage is: 16.991455
2022-01-16 07:51:37 power_api.c:97:get_average_voltage: aveage voltage is: 18.810000
2022-01-16 07:51:37 power_api.c:110:check_voltage: target_vol = 17.00, actural_vol = 18.81, more than 1.0v diff.
2022-01-16 07:51:38 power_api.c:124:check_voltage_multi: retry time: 21
2022-01-16 07:51:39 power_api.c:86:get_average_voltage: chain[0], voltage is: 17.064931
2022-01-16 07:51:43 power_api.c:86:get_average_voltage: chain[1], voltage is: 22.373613
2022-01-16 07:51:46 power_api.c:86:get_average_voltage: chain[2], voltage is: 16.985332
2022-01-16 07:51:46 power_api.c:97:get_average_voltage: aveage voltage is: 18.807959
2022-01-16 07:51:46 power_api.c:110:check_voltage: target_vol = 17.00, actural_vol = 18.81, more than 1.0v diff.
2022-01-16 07:51:47 power_api.c:124:check_voltage_multi: retry time: 22
2022-01-16 07:51:49 power_api.c:86:get_average_voltage: chain[0], voltage is: 17.089424
2022-01-16 07:51:51 power_api.c:86:get_average_voltage: chain[1], voltage is: 22.379736
2022-01-16 07:51:52 power_api.c:86:get_average_voltage: chain[2], voltage is: 16.973086
2022-01-16 07:51:52 power_api.c:97:get_average_voltage: aveage voltage is: 18.814082
2022-01-16 07:51:52 power_api.c:110:check_voltage: target_vol = 17.00, actural_vol = 18.81, more than 1.0v diff.
2022-01-16 07:51:53 power_api.c:124:check_voltage_multi: retry time: 23
2022-01-16 07:51:55 power_api.c:86:get_average_voltage: chain[0], voltage is: 17.077178
2022-01-16 07:51:57 power_api.c:86:get_average_voltage: chain[1], voltage is: 22.379736
2022-01-16 07:51:59 power_api.c:86:get_average_voltage: chain[2], voltage is: 16.966963
2022-01-16 07:51:59 power_api.c:97:get_average_voltage: aveage voltage is: 18.807959
2022-01-16 07:51:59 power_api.c:110:check_voltage: target_vol = 17.00, actural_vol = 18.81, more than 1.0v diff.
2022-01-16 07:52:00 power_api.c:124:check_voltage_multi: retry time: 24
2022-01-16 07:52:02 power_api.c:86:get_average_voltage: chain[0], voltage is: 17.089424
2022-01-16 07:52:05 power_api.c:86:get_average_voltage: chain[1], voltage is: 22.391982
2022-01-16 07:52:08 power_api.c:86:get_average_voltage: chain[2], voltage is: 16.985332
2022-01-16 07:52:08 power_api.c:97:get_average_voltage: aveage voltage is: 18.822246
2022-01-16 07:52:08 power_api.c:110:check_voltage: target_vol = 17.00, actural_vol = 18.82, more than 1.0v diff.
2022-01-16 07:52:09 power_api.c:124:check_voltage_multi: retry time: 25
2022-01-16 07:52:11 power_api.c:86:get_average_voltage: chain[0], voltage is: 17.083301
2022-01-16 07:52:13 power_api.c:86:get_average_voltage: chain[1], voltage is: 22.385859
2022-01-16 07:52:15 power_api.c:86:get_average_voltage: chain[2], voltage is: 16.985332
2022-01-16 07:52:15 power_api.c:97:get_average_voltage: aveage voltage is: 18.818164
2022-01-16 07:52:15 power_api.c:110:check_voltage: target_vol = 17.00, actural_vol = 18.82, more than 1.0v diff.
2022-01-16 07:52:16 power_api.c:124:check_voltage_multi: retry time: 26
2022-01-16 07:52:17 power_api.c:86:get_average_voltage: chain[0], voltage is: 17.064931
2022-01-16 07:52:18 http_test.c:111:get_sys_running_seconds: system uptime 311.012022-01-16 07:52:18 http_test.c:371:upload_log_generate: write result.json done
2022-01-16 07:52:20 power_api.c:86:get_average_voltage: chain[1], voltage is: 22.379736
2022-01-16 07:52:24 power_api.c:86:get_average_voltage: chain[2], voltage is: 16.973086
2022-01-16 07:52:24 power_api.c:97:get_average_voltage: aveage voltage is: 18.805918
2022-01-16 07:52:24 power_api.c:110:check_voltage: target_vol = 17.00, actural_vol = 18.81, more than 1.0v diff.
2022-01-16 07:52:25 power_api.c:124:check_voltage_multi: retry time: 27
2022-01-16 07:52:27 power_api.c:86:get_average_voltage: chain[0], voltage is: 17.064931
2022-01-16 07:52:28 power_api.c:86:get_average_voltage: chain[1], voltage is: 22.391982
2022-01-16 07:52:30 power_api.c:86:get_average_voltage: chain[2], voltage is: 16.960840
2022-01-16 07:52:30 power_api.c:97:get_average_voltage: aveage voltage is: 18.805918
2022-01-16 07:52:30 power_api.c:110:check_voltage: target_vol = 17.00, actural_vol = 18.81, more than 1.0v diff.
2022-01-16 07:52:31 power_api.c:124:check_voltage_multi: retry time: 28
2022-01-16 07:52:33 power_api.c:86:get_average_voltage: chain[0], voltage is: 17.089424
2022-01-16 07:52:35 power_api.c:86:get_average_voltage: chain[1], voltage is: 22.391982
2022-01-16 07:52:37 power_api.c:86:get_average_voltage: chain[2], voltage is: 16.966963
2022-01-16 07:52:37 power_api.c:97:get_average_voltage: aveage voltage is: 18.816123
2022-01-16 07:52:37 power_api.c:110:check_voltage: target_vol = 17.00, actural_vol = 18.82, more than 1.0v diff.
2022-01-16 07:52:38 power_api.c:124:check_voltage_multi: retry time: 29
2022-01-16 07:52:40 power_api.c:86:get_average_voltage: chain[0], voltage is: 17.089424
2022-01-16 07:52:43 power_api.c:86:get_average_voltage: chain[1], voltage is: 22.385859
2022-01-16 07:52:46 power_api.c:86:get_average_voltage: chain[2], voltage is: 16.997578
2022-01-16 07:52:46 power_api.c:97:get_average_voltage: aveage voltage is: 18.824287
2022-01-16 07:52:46 power_api.c:110:check_voltage: target_vol = 17.00, actural_vol = 18.82, more than 1.0v diff.
2022-01-16 07:52:47 power_api.c:182:set_iic_power_by_voltage: now set voltage to : 17.000000
2022-01-16 07:52:47 driver-btm-api.c:205:set_miner_status: ERROR_POWER_LOST
2022-01-16 07:52:47 driver-btm-api.c:146:stop_mining: stop mining: power set failed!
2022-01-16 07:52:47 thread.c:930:cancel_read_nonce_reg_thread: cancel thread
2022-01-16 07:52:47 driver-btm-api.c:131:killall_hashboard: ****power off hashboard****
wndsnb
hero member
Activity: 544
Merit: 589
Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
January 14, 2022, 09:34:36 PM
#398
Post a kernel log and we might be able to give some good advice.

From the info you've given, I'd guess it is the PSU. It is the only thing that you haven't swapped, and when the voltages are measured by the hashboards they are measured one at a time and there is some time delay between them. So It could be that the 1st one to measure is getting 22V, the second is getting 17, and by the time the 3rd measures the PSU shut down and is now giving you 0V.

Quote from: DwarfNo3 on January 13, 2022, 07:12:37 AM
Btw, I noticed that if I don't attach the metal brackets even when it's just two boards, the voltage gets messed up but with them it's fine. Could this be related?

No sure what you mean by metal brackets ... If you mean the busbars that connect the main power to the hashboards .... then yeah, not gonna work too well without those attached.
DwarfNo3
newbie
Activity: 5
Merit: 0
Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
January 13, 2022, 07:12:37 AM
#397
Hello all!

First thing, thank you all for all your posts. I've gone through hundreds and read full threads and it helped me a lot with those darned machines. I have a few T17 that I bought used from China because they had the best ROI, and it turns out there was a reason for that  Cheesy

Anyway, I have solved most issues but couldn't find one for this issue. Basically when I connect all 3 boards, one would be 0 volts, the other 17 and the last one 22. if I disconnect one the other two would work fine. I have tried the following:

- Made sure the outlet is grounded and working fine (227 v)
- Tried different:
 - Hashboards
 - Control board
 - Cables (signal, and the small voltage one and the 6 pin power one)

and I keep getting the same issue. The only things that I have not tried replacing are the fans and the case, but I can't imagine them being the issue. Anyone has any idea what could it?

Btw, I noticed that if I don't attach the metal brackets even when it's just two boards, the voltage gets messed up but with them it's fine. Could this be related?

Regards,
wndsnb
hero member
Activity: 544
Merit: 589
Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
November 16, 2021, 06:41:42 AM
#396
I've seen several posts about people asking about using thermal adhesives on these but never saw a post from anyone that had done it and had success or not. The solder used is about 10X better at transferring heat compared to arctic silver, so there will be a larger temperature drop between the heatsink and chip when using the adhesive, which means the chip will run hotter.

Since the miner only monitors the temperature of 4 chips, having some chips with better cooling than others could cause problems especially if one of the 4 monitored chips isn't one that has the thermal adhesive.

About soldering the heastinks back on, many times it is not possible to re-attach. Most of the time I've seen heasinks fall off it is because the copper plating on the top of the chip has delaminated. The copper is what the solder adheres to, and without it, you can't make a good connection. So I've found most of the time the chip needs to be replaced. If you post some pictures of the chips with missing heatsinks, I may be able to determine if it is possible to re-solder them.
minefarmbuy
full member
Activity: 1022
Merit: 221
We are not retail.
Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
November 15, 2021, 05:20:52 PM
#395
Any reports on the thermal adhesive working? Have a unit with about 8 heatsinks fell off and wondering if results are good with the artic silver as my soldering skills are pretty rudimentary and don't want to risk more "transit damage" for more skilled soldering repair. 
BitMaxz
legendary
Activity: 3374
Merit: 3095
BTC price road to $80k
Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
October 24, 2021, 05:26:50 PM
#394
Quote from: niko83 on October 24, 2021, 02:45:03 PM
Do you know if that glue gets soft when attacked with a heat gun, like the black glue Bitmain uses does?

It depends on the temp you set in your heat gun according to the temp range of this glue adhesive it can handle - 40C to >150C.

So more than that it can soften the glue if you set it to higher than temp 150c.
niko83
sr. member
Activity: 340
Merit: 278
Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
October 24, 2021, 02:45:03 PM
#393
Quote from: mikeywith on November 23, 2020, 04:39:57 PM
You can use something like https://www.amazon.com/Arctic-Silver-Premium-Adhesive-ASTA-7G/dp/B0087X7262, or use the black glue from the same website you got the tool, adding more solder to the existing isn't a good idea, you should clean the chip's surface and then start fresh, ensure that the amount of solder paste is equally even across the whole chip.

Watch this video https://youtu.be/5WH7g61d90w, it's helpful.

Do you know if that glue gets soft when attacked with a heat gun, like the black glue Bitmain uses does?
wndsnb
hero member
Activity: 544
Merit: 589
Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
October 24, 2021, 08:51:39 AM
#392
Quote from: flashgear on October 23, 2021, 11:29:39 PM
Are the S17 Pro's just as bad as the other 17 range?

The S17 and S17 Pro are identical, no hardware differences at all. They just select the hashboards that have the best efficiency for the Pro version, and the rest go to the non-pro.

The T17 used the identical chip, but put fewer of them in the same area (30 vs 48) with larger heatsinks so they could be run at higher frequencies at the expense of lower efficiency. Many T17s will run the same efficiency as an S17 when you drop the frequency and voltage. So with a bit of luck, your T17 might do 30TH or so at <40W/TH.

The S17+ was a redesign of the hashboard that used the newer version of the same chip, 1397AG vs the 1397AD for the S17/T17, and packed a bunch more chips on each hashboard. 65 chips for the S17+ hashboard vs 48 chips for the S17. I couldn't find any information on what the differences might be between AD and AG, but they seem to be interchangeable. I've replaced AD chips on S17s with AG chips and it worked fine. What I did see on the S17+ way more than the S17 was delamination of the copper plating on the top of the chip. The copper plating is what the heatsinks are soldered to, and when it delaminates the heatsink can come off with the copper with little force. If you ship a S17+ that has chips with copper delamination, it will likely show up at its destination with a bunch of heatsinks detached from their chips and jingling around loose. Which is how every one of the S17+s I've looked at arrived. Not sure if the delamination issue was more from the new chip version, or just from the higher possibility of excess heat caused by packing more chips into the same area. Could also be that the temperature got too high for too long during board assembly.

The T17+ was the same idea as the T17. I haven't looked at one in person but I'd guess they have the same delamination issues as the S17+.

The S17e was a completely different beast, different chip (1396), and an insane number of them on a single board, 135 chips per board. I took a look at a dead one for my host once and after seeing it in person I just sent it back to him. Looked like a complete nightmare to work on. But that was the only one I saw, and I didn't even take a chip off, so I don't really have any thoughts on them other than I don't want to mess with them.
flashgear
newbie
Activity: 14
Merit: 0
Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
October 23, 2021, 11:29:39 PM
#391
Are the S17 Pro's just as bad as the other 17 range?
wndsnb
hero member
Activity: 544
Merit: 589
Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
October 20, 2021, 05:52:13 AM
#390
I agree with mikeywith about the overclocking. The hashboard layout, case, and fans were not built to handle the 3000W required to run these at 70TH or more. The temperature of only 4 out of the 48 ASICs on each hashboard is monitored. So you can very easily get into a situation where one of the non-monitored ASICs that is less efficient or has a poorly attached heatsink, gets hot enough to melt its solder connections, short out a bunch of high power connections, and cause unrepairable damage.

If you're going to ROI in 2 months with overclocking, you'd only need to wait another couple of weeks to ROI without taking the overclocking risk.

Also, not every S17 will overclock that much anyway.
mikeywith
legendary
Activity: 2394
Merit: 6581
be constructive or S.T.F.U
Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
October 20, 2021, 03:31:15 AM
#389
Quote from: usrzero01 on October 19, 2021, 08:59:28 PM
there is nothing i cant do in my mind. Been working on computers and taking apart anything and everything and putting back together since the 80's as a kid, coding, building, repairing and replacing chips on pcb, etc.... and i already make enough money not to work, so if the information is out there, have all the time to figure it out...

If you know that you have what it takes and have all the time in the world, you could provide repair service and charge a premium, you will probably make a lot more money than actually mining, even if that doesn't make sense, it really makes no sense to buy a mining gear with such a high failure rate just because you can fix them, even if you think your time is free, wouldn't you rather watch some movies than having to fix a poorly built ASIC miner? besides, the time you are going to spend fixing them is time wasted not only for you but for the miner itself which would otherwise be generating revenue.


Quote
If i had 2 s17 overclocked i would make back my investment in about 2 months.

Assuming they will survive the overclocking for 2 months, which isn't something anyone would guarantee.

I can't think of any reason as to why would anyone (regardless of the circumstances in the world)buy any of those 17 series gears, if someone gives it to me for free, hell ya I'll take it, but will I pay half the price that gets me a Whatsminer or Avalon gear instead? hell, no.

usrzero01
newbie
Activity: 20
Merit: 0
Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
October 19, 2021, 08:59:28 PM
#388
Quote from: mikeywith on October 19, 2021, 07:50:05 PM

LOL, so you took all the online advice and your buddy's and just dumped it all in the trash?? why would you do that?

I didn't buy them, yet, his advice made me do more research. He doesn't have any 1st hand experience so that why im posting. I've read some people getting 5 out of 10 machines bad and other saying they been running their machines for couple years and fine.... SO, yeah it is a risk.
That is why im asking is there things to do to reduce the risk? PSU, FAN, HEATSINK, turn it on its side, idk just what i read......

As for working on them, there is nothing i cant do in my mind. Been working on computers and taking apart anything and everything and putting back together since the 80's as a kid, coding, building, repairing and replacing chips on pcb, etc.... and i already make enough money not to work, so if the information is out there, have all the time to figure it out...

If i had 2 s17 overclocked i would make back my investment in about 2 months, i have free power. So, that is very alluring, but 30% failure rate is very off putting. still undecided....
mikeywith
legendary
Activity: 2394
Merit: 6581
be constructive or S.T.F.U
Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
October 19, 2021, 07:50:05 PM
#387
Quote from: usrzero01 on October 19, 2021, 07:37:54 PM
But doing some research I seen they have a fire hazard, heatsink problems, weak psu, and faulty fans. my buddy said stay away.

If i decided to get them and wanted to overclock them

LOL, so you took all the online advice and your buddy's and just dumped it all in the trash?? why would you do that? I have to sadly inform you that you are likely going to regret doing that, heck, I feel bad for getting those gears LONG before the reviews started coming out, I sure as hell would feel worse if I knew in advance that I was getting some shit-gear.

Don't even think about overclocking them, your experience with computers will not serve you once those gears go bad, it isn't a matter of gluing a heatsink, the chips themselves will go bad or become loose, identifying the chip/chips that need fixing require some special tools, acquiring the replacement chip from China is some serious pain on its own, fixing these mining gears isn't something the average joe with some computer background can fix, so chances are you will have to send them for repair, which is costly and takes forever to be done, assuming they will be in a fixable state in the first place.

Keep these gears as cool as possible, forget the overclocking thing all together, that's my advice.
Pages:
Bitcoin Forum>Bitcoin>Mining>Mining support
Jump to: