Title: S17 Pro no longer hashing. Bad ASICs ?
Post by: agilmore on August 03, 2020, 12:07:32 AM
My S17 has stopped hashing. Neither the Red Fault light or the Green Normal, light are on.It just keeps cycling through the messages below. Is this repairable? Any suggestions? Here's the Kernel Log: 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: 190356K/245760K available (6345K kernel code, 231K rwdata, 1896K rodata, 1024K init, 223K bss, 39020K reserved, 16384K cma-reserved, 0K highmem)
Virtual kernel memory layout:
vector : 0xffff0000 - 0xffff1000 ( 4 kB)
fixmap : 0xffc00000 - 0xfff00000 (3072 kB)
vmalloc : 0xcf800000 - 0xff800000 ( 768 MB)
lowmem : 0xc0000000 - 0xcf000000 ( 240 MB)
pkmap : 0xbfe00000 - 0xc0000000 ( 2 MB)
modules : 0xbf000000 - 0xbfe00000 ( 14 MB)
.text : 0xc0008000 - 0xc090c424 (9234 kB)
.init : 0xc0a00000 - 0xc0b00000 (1024 kB)
.data : 0xc0b00000 - 0xc0b39fe0 ( 232 kB)
.bss : 0xc0b39fe0 - 0xc0b71c28 ( 224 kB)
Preemptible hierarchical RCU implementation.
Build-time adjustment of leaf fanout to 32.
RCU restricting CPUs from NR_CPUS=4 to nr_cpu_ids=2.
RCU: Adjusting geometry for rcu_fanout_leaf=32, nr_cpu_ids=2
NR_IRQS:16 nr_irqs:16 16
efuse mapped to cf800000
ps7-slcr mapped to cf802000
L2C: platform modifies aux control register: 0x72360000 -> 0x72760000
L2C: DT/platform modifies aux control register: 0x72360000 -> 0x72760000
L2C-310 erratum 769419 enabled
L2C-310 enabling early BRESP for Cortex-A9
L2C-310 full line of zeros enabled for Cortex-A9
L2C-310 ID prefetch enabled, offset 1 lines
L2C-310 dynamic clock gating enabled, standby mode enabled
L2C-310 cache controller enabled, 8 ways, 512 kB
L2C-310: CACHE_ID 0x410000c8, AUX_CTRL 0x76760001
zynq_clock_init: clkc starts at cf802100
Zynq clock init
sched_clock: 64 bits at 333MHz, resolution 3ns, wraps every 4398046511103ns
clocksource: arm_global_timer: mask: 0xffffffffffffffff max_cycles: 0x4ce07af025, max_idle_ns: 440795209040 ns
Switching to timer-based delay loop, resolution 3ns
clocksource: ttc_clocksource: mask: 0xffff max_cycles: 0xffff, max_idle_ns: 537538477 ns
ps7-ttc #0 at cf80a000, irq=18
Console: colour dummy device 80x30
Calibrating delay loop (skipped), value calculated using timer frequency.. 666.66 BogoMIPS (lpj=3333333)
pid_max: default: 32768 minimum: 301
Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
CPU: Testing write buffer coherency: ok
CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
Setting up static identity map for 0x100000 - 0x100058
CPU1: failed to boot: -1
Brought up 1 CPUs
SMP: Total of 1 processors activated (666.66 BogoMIPS).
CPU: All CPU(s) started in SVC mode.
devtmpfs: initialized
VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4
clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
pinctrl core: initialized pinctrl subsystem
NET: Registered protocol family 16
DMA: preallocated 256 KiB pool for atomic coherent allocations
cpuidle: using governor menu
hw-breakpoint: found 5 (+1 reserved) breakpoint and 1 watchpoint registers.
hw-breakpoint: maximum watchpoint size is 4 bytes.
zynq-ocm f800c000.ps7-ocmc: ZYNQ OCM pool: 256 KiB @ 0xcf880000
vgaarb: loaded
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
media: Linux media interface: v0.10
Linux video capture interface: v2.00
pps_core: LinuxPPS API ver. 1 registered
pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
PTP clock support registered
EDAC MC: Ver: 3.0.0
Advanced Linux Sound Architecture Driver Initialized.
clocksource: Switched to clocksource arm_global_timer
NET: Registered protocol family 2
TCP established hash table entries: 2048 (order: 1, 8192 bytes)
TCP bind hash table entries: 2048 (order: 2, 16384 bytes)
TCP: Hash tables configured (established 2048 bind 2048)
UDP hash table entries: 256 (order: 1, 8192 bytes)
UDP-Lite hash table entries: 256 (order: 1, 8192 bytes)
NET: Registered protocol family 1
RPC: Registered named UNIX socket transport module.
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
PCI: CLS 0 bytes, default 64
Trying to unpack rootfs image as initramfs...
rootfs image is not initramfs (no cpio magic); looks like an initrd
Freeing initrd memory: 25980K (cc1a2000 - cdb01000)
hw perfevents: enabled with armv7_cortex_a9 PMU driver, 7 counters available
futex hash table entries: 512 (order: 3, 32768 bytes)
workingset: timestamp_bits=28 max_order=16 bucket_order=0
jffs2: version 2.2. (NAND) (SUMMARY) © 2001-2006 Red Hat, Inc.
io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered (default)
dma-pl330 f8003000.ps7-dma: Loaded driver for PL330 DMAC-241330
dma-pl330 f8003000.ps7-dma: DBUFF-128x8bytes Num_Chans-8 Num_Peri-4 Num_Events-16
e0000000.serial: ttyPS0 at MMIO 0xe0000000 (irq = 158, base_baud = 6249999) is a xuartps
console [ttyPS0] enabled
xdevcfg f8007000.ps7-dev-cfg: ioremap 0xf8007000 to cf86e000
[drm] Initialized drm 1.1.0 20060810
brd: module loaded
loop: module loaded
CAN device driver interface
gpiod_set_value: invalid GPIO
libphy: MACB_mii_bus: probed
macb e000b000.ethernet eth0: Cadence GEM rev 0x00020118 at 0xe000b000 irq 31 (00:0a:35:00:00:00)
Generic PHY e000b000.etherne:00: attached PHY driver [Generic PHY] (mii_bus:phy_addr=e000b000.etherne:00, irq=-1)
e1000e: Intel(R) PRO/1000 Network Driver - 3.2.6-k
e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
ehci-pci: EHCI PCI platform driver
usbcore: registered new interface driver usb-storage
mousedev: PS/2 mouse device common for all mice
i2c /dev entries driver
Xilinx Zynq CpuIdle Driver started
sdhci: Secure Digital Host Controller Interface driver
sdhci: Copyright(c) Pierre Ossman
sdhci-pltfm: SDHCI platform and OF driver helper
mmc0: SDHCI controller on e0100000.ps7-sdio [e0100000.ps7-sdio] using ADMA
ledtrig-cpu: registered to indicate activity on CPUs
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
nand: device found, Manufacturer ID: 0x2c, Chip ID: 0xda
nand: Micron MT29F2G08ABAGAWP
nand: 256 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 128
nand: WARNING: pl35x-nand: the ECC used on your system is too weak compared to the one required by the NAND chip
Bad block table found at page 131008, version 0x01
Bad block table found at page 130944, version 0x01
6 ofpart partitions found on MTD device pl35x-nand
Creating 6 MTD partitions on "pl35x-nand":
0x000000000000-0x000002800000 : "BOOT.bin-env-dts-kernel"
0x000002800000-0x000004800000 : "ramfs"
0x000004800000-0x000005000000 : "configs"
0x000005000000-0x000006000000 : "reserve"
0x000006000000-0x000008000000 : "ramfs-bak"
0x000008000000-0x000010000000 : "reserve1"
NET: Registered protocol family 10
sit: IPv6 over IPv4 tunneling driver
NET: Registered protocol family 17
can: controller area network core (rev 20120528 abi 9)
NET: Registered protocol family 29
can: raw protocol (rev 20120528)
can: broadcast manager protocol (rev 20120528 t)
can: netlink gateway (rev 20130117) max_hops=1
zynq_pm_ioremap: no compatible node found for 'xlnx,zynq-ddrc-a05'
zynq_pm_late_init: Unable to map DDRC IO memory.
Registering SWP/SWPB emulation handler
hctosys: unable to open rtc device (rtc0)
ALSA device list:
No soundcards found.
RAMDISK: gzip image found at block 0
EXT4-fs (ram0): couldn't mount as ext3 due to feature incompatibilities
EXT4-fs (ram0): mounted filesystem without journal. Opts: (null)
VFS: Mounted root (ext4 filesystem) on device 1:0.
devtmpfs: mounted
Freeing unused kernel memory: 1024K (c0a00000 - c0b00000)
EXT4-fs (ram0): re-mounted. Opts: block_validity,delalloc,barrier,user_xattr
random: dd urandom read with 0 bits of entropy available
ubi0: attaching mtd2
ubi0: scanning is finished
ubi0: attached mtd2 (name "configs", size 8 MiB)
ubi0: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
ubi0: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
ubi0: VID header offset: 2048 (aligned 2048), data offset: 4096
ubi0: good PEBs: 64, bad PEBs: 0, corrupted PEBs: 0
ubi0: user volume: 1, internal volumes: 1, max. volumes count: 128
ubi0: max/mean erase counter: 5/2, WL threshold: 4096, image sequence number: 237714726
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 FF09433B-E002-4C29-97EC-6220DDC4BB36, 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: 4353/1931, WL threshold: 4096, image sequence number: 914180297
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 BCBDE5E0-4C0B-4978-9734-FC58D9F68227, 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 = 0xab011
In fpga mem driver!
request_mem_region OK!
fpga mem virtual address is 0xd2000000
random: nonblocking pool is initialized
Alignment trap: cg@0/RStratum (2225) PC=0x00020c54 Instr=0xedd20b1a Address=0x00000089 FSR 0x001
Alignment trap: not handling instruction edd20b1a at [<00020c54>]
Unhandled fault: alignment exception (0x001) at 0x00000089
pgd = c983c000
[00000089] *pgd=05c8c831, *pte=00000000, *ppte=00000000
[2020-08-03 00:01:40.304] httpListenThread start ret=0
[2020-08-03 00:02:10.308] start listen on 6060 ...
2020-08-03 00:01:40 driver-btm-soc.c:3160:init_freq_mode: This is scan-user version
2020-08-03 00:01:40 driver-btm-soc.c:3896:bitmain_soc_init: opt_multi_version=1
2020-08-03 00:01:40 driver-btm-soc.c:3897:bitmain_soc_init: opt_bitmain_ab=1
2020-08-03 00:01:40 driver-btm-soc.c:3898:bitmain_soc_init: opt_bitmain_work_mode=2
2020-08-03 00:01:40 driver-btm-soc.c:3521:_show_sn: no SN got, please write SN to /nvdata/sn
2020-08-03 00:01:40 driver-btm-soc.c:3191:init_phy_mem_nonce2_jobid_address: Detect 256MB control board of XILINX
2020-08-03 00:01:40 driver-btm-soc.c:3904:bitmain_soc_init: Miner compile time: Tue Apr 16 19:05:06 CST 2019
2020-08-03 00:01:40 driver-btm-soc.c:3906:bitmain_soc_init: last commit version: 8b856e7 commit time: 2019-04-16 16:36:14 build: 2019-04-16 19:09:46
2020-08-03 00:01:40 driver-btm-soc.c:3223:check_fan_multi: check fan for 20 times...
2020-08-03 00:01:42 driver-btm-soc.c:3299:init_miner_version: miner ID : 813275ce57408854
2020-08-03 00:01:42 driver-btm-soc.c:3305:init_miner_version: FPGA Version = 0xB011
2020-08-03 00:01:42 driver-btm-soc.c:404:check_chain: !! chain[0]is exist
2020-08-03 00:01:42 driver-btm-soc.c:404:check_chain: !! chain[1]is exist
2020-08-03 00:01:42 driver-btm-soc.c:404:check_chain: !! chain[2]is exist
2020-08-03 00:01:46 driver-btm-soc.c:3722:get_product_id: product_id[0] = 0
2020-08-03 00:01:46 driver-btm-soc.c:3722:get_product_id: product_id[1] = 0
2020-08-03 00:01:46 driver-btm-soc.c:3722:get_product_id: product_id[2] = 0
2020-08-03 00:01:46 driver-btm-soc.c:3823:bitmain_board_init: g_product_id = 0
2020-08-03 00:01:46 driver-btm-soc.c:3574:_set_project_type: Project type: Antminer S17 Pro
2020-08-03 00:01:46 driver-btm-soc.c:3321:dump_pcb_bom_version: Chain [0] PCB Version: 0x0101
2020-08-03 00:01:46 driver-btm-soc.c:3322:dump_pcb_bom_version: Chain [0] BOM Version: 0x0103
2020-08-03 00:01:46 driver-btm-soc.c:3321:dump_pcb_bom_version: Chain [1] PCB Version: 0x0101
2020-08-03 00:01:46 driver-btm-soc.c:3322:dump_pcb_bom_version: Chain [1] BOM Version: 0x0103
2020-08-03 00:01:46 driver-btm-soc.c:3321:dump_pcb_bom_version: Chain [2] PCB Version: 0x0101
2020-08-03 00:01:46 driver-btm-soc.c:3322:dump_pcb_bom_version: Chain [2] BOM Version: 0x0103
2020-08-03 00:01:46 pic.c:619:pic_reset: chain[0] ok
2020-08-03 00:01:51 pic.c:898:jump_to_app_from_loader: chain[0] ok
2020-08-03 00:01:51 pic.c:619:pic_reset: chain[1] ok
2020-08-03 00:01:56 pic.c:898:jump_to_app_from_loader: chain[1] ok
2020-08-03 00:01:57 pic.c:619:pic_reset: chain[2] ok
2020-08-03 00:02:01 pic.c:898:jump_to_app_from_loader: chain[2] ok
2020-08-03 00:02:01 driver-btm-soc.c:3840:bitmain_board_init: Enter 30s sleep to make sure power release finish.
2020-08-03 00:02:01 driver-btm-soc.c:1156:heart_beat_func_one_chain: for chain 2
2020-08-03 00:02:01 driver-btm-soc.c:1156:heart_beat_func_one_chain: for chain 1
2020-08-03 00:02:01 driver-btm-soc.c:1156:heart_beat_func_one_chain: for chain 0
2020-08-03 00:02:31 power.c:216:power_init: power init ...
2020-08-03 00:02:33 power.c:348:power_get_firmware_version: power firmware version is 00 07
2020-08-03 00:02:34 power.c:338:power_get_device_no: power device no is 00 41
2020-08-03 00:02:34 power.c:203:power_check_protocol_type: power protocol f5, using package cmd
2020-08-03 00:02:34 power.c:204:power_check_protocol_type: power type APW9 3600W
2020-08-03 00:02:35 power.c:624:set_iic_power_to_highest_voltage: setting to voltage: 21.00 ...
2020-08-03 00:02:38 power.c:573:set_iic_power_by_voltage: now setting voltage to : 21.000000
2020-08-03 00:02:38 zynq.c:192:set_reset_hashboard: set_reset_hashboard = 0x0000fff9
2020-08-03 00:02:42 pic.c:234:hashboard_power_cntl: [1] ok, i2c=0!
2020-08-03 00:02:44 zynq.c:192:set_reset_hashboard: set_reset_hashboard = 0x0000fff8
2020-08-03 00:02:48 driver-btm-soc.c:3657:check_asic_number_with_power_on: Chain[0]: find 0 asic, times 0
2020-08-03 00:02:48 zynq.c:192:set_reset_hashboard: set_reset_hashboard = 0x0000fff9
2020-08-03 00:02:51 pic.c:234:hashboard_power_cntl: [1] ok, i2c=0!
2020-08-03 00:02:53 zynq.c:192:set_reset_hashboard: set_reset_hashboard = 0x0000fff8
2020-08-03 00:02:57 driver-btm-soc.c:3657:check_asic_number_with_power_on: Chain[0]: find 0 asic, times 1
2020-08-03 00:02:57 zynq.c:192:set_reset_hashboard: set_reset_hashboard = 0x0000fff9
2020-08-03 00:03:01 pic.c:234:hashboard_power_cntl: [1] ok, i2c=0!
2020-08-03 00:03:03 zynq.c:192:set_reset_hashboard: set_reset_hashboard = 0x0000fff8
2020-08-03 00:03:07 driver-btm-soc.c:3657:check_asic_number_with_power_on: Chain[0]: find 0 asic, times 2
2020-08-03 00:03:07 driver-btm-soc.c:3682:check_asic_number: Chain 0 only find 0 asic, will power off hash board 0
2020-08-03 00:03:08 pic.c:234:hashboard_power_cntl: [0] ok, i2c=0!
2020-08-03 00:03:08 zynq.c:192:set_reset_hashboard: set_reset_hashboard = 0x0000fffa
2020-08-03 00:03:12 pic.c:234:hashboard_power_cntl: [1] ok, i2c=1!
2020-08-03 00:03:14 zynq.c:192:set_reset_hashboard: set_reset_hashboard = 0x0000fff8
2020-08-03 00:03:18 driver-btm-soc.c:3657:check_asic_number_with_power_on: Chain[1]: find 0 asic, times 0
2020-08-03 00:03:18 zynq.c:192:set_reset_hashboard: set_reset_hashboard = 0x0000fffa
2020-08-03 00:03:21 pic.c:234:hashboard_power_cntl: [1] ok, i2c=1!
2020-08-03 00:03:23 zynq.c:192:set_reset_hashboard: set_reset_hashboard = 0x0000fff8
2020-08-03 00:03:28 driver-btm-soc.c:3657:check_asic_number_with_power_on: Chain[1]: find 0 asic, times 1
2020-08-03 00:03:28 zynq.c:192:set_reset_hashboard: set_reset_hashboard = 0x0000fffa
2020-08-03 00:03:31 pic.c:234:hashboard_power_cntl: [1] ok, i2c=1!
2020-08-03 00:03:33 zynq.c:192:set_reset_hashboard: set_reset_hashboard = 0x0000fff8
2020-08-03 00:03:37 driver-btm-soc.c:3657:check_asic_number_with_power_on: Chain[1]: find 0 asic, times 2
2020-08-03 00:03:37 driver-btm-soc.c:3682:check_asic_number: Chain 1 only find 0 asic, will power off hash board 1
2020-08-03 00:03:38 pic.c:234:hashboard_power_cntl: [0] ok, i2c=1!
2020-08-03 00:03:38 zynq.c:192:set_reset_hashboard: set_reset_hashboard = 0x0000fffc
2020-08-03 00:03:42 pic.c:234:hashboard_power_cntl: [1] ok, i2c=2!
2020-08-03 00:03:44 zynq.c:192:set_reset_hashboard: set_reset_hashboard = 0x0000fff8
2020-08-03 00:03:48 driver-btm-soc.c:3657:check_asic_number_with_power_on: Chain[2]: find 0 asic, times 0
2020-08-03 00:03:48 zynq.c:192:set_reset_hashboard: set_reset_hashboard = 0x0000fffc
2020-08-03 00:03:51 pic.c:234:hashboard_power_cntl: [1] ok, i2c=2!
2020-08-03 00:03:53 zynq.c:192:set_reset_hashboard: set_reset_hashboard = 0x0000fff8
2020-08-03 00:03:57 driver-btm-soc.c:3657:check_asic_number_with_power_on: Chain[2]: find 0 asic, times 1
2020-08-03 00:03:57 zynq.c:192:set_reset_hashboard: set_reset_hashboard = 0x0000fffc
2020-08-03 00:04:01 pic.c:234:hashboard_power_cntl: [1] ok, i2c=2!
2020-08-03 00:04:03 zynq.c:192:set_reset_hashboard: set_reset_hashboard = 0x0000fff8
Title: Re: S17 Pro no longer hashing. Bad ASICs ?
Post by: philipma1957 on August 03, 2020, 12:35:01 AM
i am looking at it.
unplug it let it sit.
lets play 20 questions.
did you ever use any firmware other then bitmain.
what setting is it on low normal turbo.
is it the s17pro 50th 53th 56th
do not use a different firmware but if you have always had bitmain firmware
which one are you using?
do not upgrade the bitmain firmware just tell which one you have.
Title: Re: S17 Pro no longer hashing. Bad ASICs ?
Post by: agilmore on August 03, 2020, 01:18:07 AM
did you ever use any firmware other then bitmain.
No. what setting is it on low normal turbo.
Turbo. is it the s17pro 50th 53th 56th
I dont recall. How can I find out? which one are you using?
Kernel Version: Linux 4.6.0-xilinx-gff8137b-dirty #25 SMP PREEMPT Fri Nov 23 15:30:52 CST 2018Hardware Version: 17.10.1.3
Title: Re: S17 Pro no longer hashing. Bad ASICs ?
Post by: mikeywith on August 03, 2020, 03:32:40 AM
This > 2020-08-03 00:03:07 driver-btm-soc.c:3657:check_asic_number_with_power_on: Chain[0]: find 0 asic, times 2 2020-08-03 00:03:37 driver-btm-soc.c:3657:check_asic_number_with_power_on: Chain[1]: find 0 asic, times 2 2020-08-03 00:03:48 driver-btm-soc.c:3657:check_asic_number_with_power_on: Chain[2]: find 0 asic, times 0 In plain English implies that the contorl board isn't sensing/seeing any asics on all 3 hash boards, now if it was only on a single chain I would say it's a taosted chain, but what are the chances of 3 hash boards going down at the same time? I would say slim to nothing which leads me to think that this has to be a POWER related issue. - Your feeding the PSU with a higher/lower AC voltage that it can handle, so you need to tell us what is the voltage or - Your PSU has gone bad and needs replacement, but before you do that, give it a good dusting and set the miner on "low" settings, the results that come out of this troubleshooting will probably lead us to know what the problem actually is.
Title: Re: S17 Pro no longer hashing. Bad ASICs ?
Post by: philipma1957 on August 03, 2020, 03:42:16 AM
yeah i think he killed psu.
if he killed the psu it will be hard to get one.
as bitmain stopped selling them. or any other gear.
Op are you usa based?
i may have a source for psu.
first listen to mikey
set to low
check all power plugs to psu
make sure you have 210-240 power.
Title: Re: S17 Pro no longer hashing. Bad ASICs ?
Post by: agilmore on August 04, 2020, 02:16:15 AM
Thanks All for the suggestions. I'll give these a shot tomorrow and report back. FYI, I am in the USA.
Heres the log after switching to Low Power mode. Also, maybe it was there before, but I didnt notice it, but this time the Miner Status was temporarily displayed. See the screenshots at the bottom. Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
CPU: Testing write buffer coherency: ok
CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
Setting up static identity map for 0x100000 - 0x100058
CPU1: failed to boot: -1
Brought up 1 CPUs
SMP: Total of 1 processors activated (666.66 BogoMIPS).
CPU: All CPU(s) started in SVC mode.
devtmpfs: initialized
VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4
clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
pinctrl core: initialized pinctrl subsystem
NET: Registered protocol family 16
DMA: preallocated 256 KiB pool for atomic coherent allocations
cpuidle: using governor menu
hw-breakpoint: found 5 (+1 reserved) breakpoint and 1 watchpoint registers.
hw-breakpoint: maximum watchpoint size is 4 bytes.
zynq-ocm f800c000.ps7-ocmc: ZYNQ OCM pool: 256 KiB @ 0xcf880000
vgaarb: loaded
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
media: Linux media interface: v0.10
Linux video capture interface: v2.00
pps_core: LinuxPPS API ver. 1 registered
pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
PTP clock support registered
EDAC MC: Ver: 3.0.0
Advanced Linux Sound Architecture Driver Initialized.
clocksource: Switched to clocksource arm_global_timer
NET: Registered protocol family 2
TCP established hash table entries: 2048 (order: 1, 8192 bytes)
TCP bind hash table entries: 2048 (order: 2, 16384 bytes)
TCP: Hash tables configured (established 2048 bind 2048)
UDP hash table entries: 256 (order: 1, 8192 bytes)
UDP-Lite hash table entries: 256 (order: 1, 8192 bytes)
NET: Registered protocol family 1
RPC: Registered named UNIX socket transport module.
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
PCI: CLS 0 bytes, default 64
Trying to unpack rootfs image as initramfs...
rootfs image is not initramfs (no cpio magic); looks like an initrd
Freeing initrd memory: 25980K (cc1a2000 - cdb01000)
hw perfevents: enabled with armv7_cortex_a9 PMU driver, 7 counters available
futex hash table entries: 512 (order: 3, 32768 bytes)
workingset: timestamp_bits=28 max_order=16 bucket_order=0
jffs2: version 2.2. (NAND) (SUMMARY) © 2001-2006 Red Hat, Inc.
io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered (default)
dma-pl330 f8003000.ps7-dma: Loaded driver for PL330 DMAC-241330
dma-pl330 f8003000.ps7-dma: DBUFF-128x8bytes Num_Chans-8 Num_Peri-4 Num_Events-16
e0000000.serial: ttyPS0 at MMIO 0xe0000000 (irq = 158, base_baud = 6249999) is a xuartps
console [ttyPS0] enabled
xdevcfg f8007000.ps7-dev-cfg: ioremap 0xf8007000 to cf86e000
[drm] Initialized drm 1.1.0 20060810
brd: module loaded
loop: module loaded
CAN device driver interface
gpiod_set_value: invalid GPIO
libphy: MACB_mii_bus: probed
macb e000b000.ethernet eth0: Cadence GEM rev 0x00020118 at 0xe000b000 irq 31 (00:0a:35:00:00:00)
Generic PHY e000b000.etherne:00: attached PHY driver [Generic PHY] (mii_bus:phy_addr=e000b000.etherne:00, irq=-1)
e1000e: Intel(R) PRO/1000 Network Driver - 3.2.6-k
e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
ehci-pci: EHCI PCI platform driver
usbcore: registered new interface driver usb-storage
mousedev: PS/2 mouse device common for all mice
i2c /dev entries driver
Xilinx Zynq CpuIdle Driver started
sdhci: Secure Digital Host Controller Interface driver
sdhci: Copyright(c) Pierre Ossman
sdhci-pltfm: SDHCI platform and OF driver helper
mmc0: SDHCI controller on e0100000.ps7-sdio [e0100000.ps7-sdio] using ADMA
ledtrig-cpu: registered to indicate activity on CPUs
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
nand: device found, Manufacturer ID: 0x2c, Chip ID: 0xda
nand: Micron MT29F2G08ABAGAWP
nand: 256 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 128
nand: WARNING: pl35x-nand: the ECC used on your system is too weak compared to the one required by the NAND chip
Bad block table found at page 131008, version 0x01
Bad block table found at page 130944, version 0x01
6 ofpart partitions found on MTD device pl35x-nand
Creating 6 MTD partitions on "pl35x-nand":
0x000000000000-0x000002800000 : "BOOT.bin-env-dts-kernel"
0x000002800000-0x000004800000 : "ramfs"
0x000004800000-0x000005000000 : "configs"
0x000005000000-0x000006000000 : "reserve"
0x000006000000-0x000008000000 : "ramfs-bak"
0x000008000000-0x000010000000 : "reserve1"
NET: Registered protocol family 10
sit: IPv6 over IPv4 tunneling driver
NET: Registered protocol family 17
can: controller area network core (rev 20120528 abi 9)
NET: Registered protocol family 29
can: raw protocol (rev 20120528)
can: broadcast manager protocol (rev 20120528 t)
can: netlink gateway (rev 20130117) max_hops=1
zynq_pm_ioremap: no compatible node found for 'xlnx,zynq-ddrc-a05'
zynq_pm_late_init: Unable to map DDRC IO memory.
Registering SWP/SWPB emulation handler
hctosys: unable to open rtc device (rtc0)
ALSA device list:
No soundcards found.
RAMDISK: gzip image found at block 0
EXT4-fs (ram0): couldn't mount as ext3 due to feature incompatibilities
EXT4-fs (ram0): mounted filesystem without journal. Opts: (null)
VFS: Mounted root (ext4 filesystem) on device 1:0.
devtmpfs: mounted
Freeing unused kernel memory: 1024K (c0a00000 - c0b00000)
EXT4-fs (ram0): re-mounted. Opts: block_validity,delalloc,barrier,user_xattr
random: dd urandom read with 0 bits of entropy available
ubi0: attaching mtd2
ubi0: scanning is finished
ubi0: attached mtd2 (name "configs", size 8 MiB)
ubi0: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
ubi0: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
ubi0: VID header offset: 2048 (aligned 2048), data offset: 4096
ubi0: good PEBs: 64, bad PEBs: 0, corrupted PEBs: 0
ubi0: user volume: 1, internal volumes: 1, max. volumes count: 128
ubi0: max/mean erase counter: 5/2, WL threshold: 4096, image sequence number: 237714726
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 FF09433B-E002-4C29-97EC-6220DDC4BB36, 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: 4353/1931, WL threshold: 4096, image sequence number: 914180297
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 BCBDE5E0-4C0B-4978-9734-FC58D9F68227, 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 = 0xab011
In fpga mem driver!
request_mem_region OK!
fpga mem virtual address is 0xd2000000
random: nonblocking pool is initialized
Alignment trap: cg@0/RStratum (1324) PC=0x00020c54 Instr=0xedd20b1a Address=0x00000089 FSR 0x001
Alignment trap: not handling instruction edd20b1a at [<00020c54>]
Unhandled fault: alignment exception (0x001) at 0x00000089
pgd = c4150000
[00000089] *pgd=0983a831, *pte=00000000, *ppte=00000000
Alignment trap: cg@0/RStratum (1663) PC=0x00020c54 Instr=0xedd20b1a Address=0x00000089 FSR 0x001
Alignment trap: not handling instruction edd20b1a at [<00020c54>]
Unhandled fault: alignment exception (0x001) at 0x00000089
pgd = cbf58000
[00000089] *pgd=09e42831, *pte=00000000, *ppte=00000000
Alignment trap: cg@0/RStratum (2003) PC=0x00020c54 Instr=0xedd20b1a Address=0x00000089 FSR 0x001
Alignment trap: not handling instruction edd20b1a at [<00020c54>]
Unhandled fault: alignment exception (0x001) at 0x00000089
pgd = cbf54000
[00000089] *pgd=08256831, *pte=00000000, *ppte=00000000
Alignment trap: cg@0/RStratum (3090) PC=0x00020c54 Instr=0xedd20b1a Address=0x00000089 FSR 0x001
Alignment trap: not handling instruction edd20b1a at [<00020c54>]
Unhandled fault: alignment exception (0x001) at 0x00000089
pgd = c3bbc000
[00000089] *pgd=0d591831, *pte=00000000, *ppte=00000000
Alignment trap: cg@0/RStratum (3793) PC=0x00020c54 Instr=0xedd20b1a Address=0x00000089 FSR 0x001
Alignment trap: not handling instruction edd20b1a at [<00020c54>]
Unhandled fault: alignment exception (0x001) at 0x00000089
pgd = c9c0c000
[00000089] *pgd=0bccd831, *pte=00000000, *ppte=00000000
Alignment trap: cg@0/RStratum (4855) PC=0x00020c54 Instr=0xedd20b1a Address=0x00000089 FSR 0x001
Alignment trap: not handling instruction edd20b1a at [<00020c54>]
Unhandled fault: alignment exception (0x001) at 0x00000089
pgd = c6ef4000
[00000089] *pgd=09e42831, *pte=00000000, *ppte=00000000
Alignment trap: cg@0/RStratum (5194) PC=0x00020c54 Instr=0xedd20b1a Address=0x00000089 FSR 0x001
Alignment trap: not handling instruction edd20b1a at [<00020c54>]
Unhandled fault: alignment exception (0x001) at 0x00000089
pgd = c3d6c000
[00000089] *pgd=0bf51831, *pte=00000000, *ppte=00000000
Alignment trap: cg@0/RStratum (5533) PC=0x00020c54 Instr=0xedd20b1a Address=0x00000089 FSR 0x001
Alignment trap: not handling instruction edd20b1a at [<00020c54>]
Unhandled fault: alignment exception (0x001) at 0x00000089
pgd = c9c0c000
[00000089] *pgd=09e42831, *pte=00000000, *ppte=00000000
Alignment trap: cg@0/RStratum (5872) PC=0x00020c54 Instr=0xedd20b1a Address=0x00000089 FSR 0x001
Alignment trap: not handling instruction edd20b1a at [<00020c54>]
Unhandled fault: alignment exception (0x001) at 0x00000089
pgd = c9c14000
[00000089] *pgd=0bf5f831, *pte=00000000, *ppte=00000000
Alignment trap: cg@0/RStratum (6211) PC=0x00020c54 Instr=0xedd20b1a Address=0x00000089 FSR 0x001
Alignment trap: not handling instruction edd20b1a at [<00020c54>]
Unhandled fault: alignment exception (0x001) at 0x00000089
pgd = c433c000
[00000089] *pgd=08253831, *pte=00000000, *ppte=00000000
Alignment trap: cg@0/RStratum (6578) PC=0x00020c54 Instr=0xedd20b1a Address=0x00000089 FSR 0x001
Alignment trap: not handling instruction edd20b1a at [<00020c54>]
Unhandled fault: alignment exception (0x001) at 0x00000089
pgd = c9c14000
[00000089] *pgd=0bf5c831, *pte=00000000, *ppte=00000000
Alignment trap: cg@0/RStratum (7212) PC=0x00020c54 Instr=0xedd20b1a Address=0x00000089 FSR 0x001
Alignment trap: not handling instruction edd20b1a at [<00020c54>]
Unhandled fault: alignment exception (0x001) at 0x00000089
pgd = c8d94000
[00000089] *pgd=06ef6831, *pte=00000000, *ppte=00000000
[2020-08-04 02:09:32.242] httpListenThread start ret=0
2020-08-04 02:09:32 driver-btm-soc.c:3160:init_freq_mode: This is scan-user version
2020-08-04 02:09:32 driver-btm-soc.c:3896:bitmain_soc_init: opt_multi_version=1
2020-08-04 02:09:32 driver-btm-soc.c:3897:bitmain_soc_init: opt_bitmain_ab=1
2020-08-04 02:09:32 driver-btm-soc.c:3898:bitmain_soc_init: opt_bitmain_work_mode=0
2020-08-04 02:09:32 driver-btm-soc.c:3521:_show_sn: no SN got, please write SN to /nvdata/sn
2020-08-04 02:09:32 driver-btm-soc.c:3191:init_phy_mem_nonce2_jobid_address: Detect 256MB control board of XILINX
2020-08-04 02:09:32 driver-btm-soc.c:3904:bitmain_soc_init: Miner compile time: Tue Apr 16 19:05:06 CST 2019
2020-08-04 02:09:32 driver-btm-soc.c:3906:bitmain_soc_init: last commit version: 8b856e7 commit time: 2019-04-16 16:36:14 build: 2019-04-16 19:09:46
2020-08-04 02:09:32 driver-btm-soc.c:3223:check_fan_multi: check fan for 20 times...
2020-08-04 02:09:34 driver-btm-soc.c:3299:init_miner_version: miner ID : 813275ce57408854
2020-08-04 02:09:34 driver-btm-soc.c:3305:init_miner_version: FPGA Version = 0xB011
2020-08-04 02:09:34 driver-btm-soc.c:404:check_chain: !! chain[0]is exist
2020-08-04 02:09:34 driver-btm-soc.c:404:check_chain: !! chain[1]is exist
2020-08-04 02:09:34 driver-btm-soc.c:404:check_chain: !! chain[2]is exist
2020-08-04 02:09:38 driver-btm-soc.c:3722:get_product_id: product_id[0] = 0
2020-08-04 02:09:38 driver-btm-soc.c:3722:get_product_id: product_id[1] = 0
2020-08-04 02:09:38 driver-btm-soc.c:3722:get_product_id: product_id[2] = 0
2020-08-04 02:09:38 driver-btm-soc.c:3823:bitmain_board_init: g_product_id = 0
2020-08-04 02:09:38 driver-btm-soc.c:3574:_set_project_type: Project type: Antminer S17 Pro
2020-08-04 02:09:38 driver-btm-soc.c:3321:dump_pcb_bom_version: Chain [0] PCB Version: 0x0101
2020-08-04 02:09:38 driver-btm-soc.c:3322:dump_pcb_bom_version: Chain [0] BOM Version: 0x0103
2020-08-04 02:09:38 driver-btm-soc.c:3321:dump_pcb_bom_version: Chain [1] PCB Version: 0x0101
2020-08-04 02:09:38 driver-btm-soc.c:3322:dump_pcb_bom_version: Chain [1] BOM Version: 0x0103
2020-08-04 02:09:38 driver-btm-soc.c:3321:dump_pcb_bom_version: Chain [2] PCB Version: 0x0101
2020-08-04 02:09:38 driver-btm-soc.c:3322:dump_pcb_bom_version: Chain [2] BOM Version: 0x0103
2020-08-04 02:09:38 pic.c:619:pic_reset: chain[0] ok
2020-08-04 02:09:43 pic.c:898:jump_to_app_from_loader: chain[0] ok
2020-08-04 02:09:43 pic.c:619:pic_reset: chain[1] ok
2020-08-04 02:09:48 pic.c:898:jump_to_app_from_loader: chain[1] ok
2020-08-04 02:09:48 pic.c:619:pic_reset: chain[2] ok
2020-08-04 02:09:53 pic.c:898:jump_to_app_from_loader: chain[2] ok
2020-08-04 02:09:53 driver-btm-soc.c:3840:bitmain_board_init: Enter 30s sleep to make sure power release finish.
2020-08-04 02:09:53 driver-btm-soc.c:1156:heart_beat_func_one_chain: for chain 2
2020-08-04 02:09:53 driver-btm-soc.c:1156:heart_beat_func_one_chain: for chain 1
2020-08-04 02:09:53 driver-btm-soc.c:1156:heart_beat_func_one_chain: for chain 0
https://photos.google.com/album/AF1QipPE5gJFdH8kH6BxaXAJxQkTA3bski1-pR7Qk0Df/photo/AF1QipPIgDdruwhtQCOXEe724dG4PuUMf3A16duMEUP2 https://photos.google.com/album/AF1QipPE5gJFdH8kH6BxaXAJxQkTA3bski1-pR7Qk0Df/photo/AF1QipNlom_28Ix6hduzLlLS1jraraU15WaWFMOsrzPD
Title: Re: S17 Pro no longer hashing. Bad ASICs ?
Post by: mikeywith on August 05, 2020, 03:37:32 AM
You should have waited 30 seconds before copying the Kernel log, it' missing all the important details, after the last line it should show power.c:216:power_init: power init ... and then a whole bunch of other details, so please post again, also none of the links you posted contain any images, please use imgur.com or imgbb.com to upload the pictures.
Title: Re: S17 Pro no longer hashing. Bad ASICs ?
Post by: PopoJeff on August 05, 2020, 03:30:40 PM
@philipma1957
Was it you that said somewhere you have a repair contact in NC somewhere? I got and S17+ for almost free with my Bitmain credit just prior to the virus. One board isnt reading (temp sensor error). I created a DOA repair ticket with Bitmain, and they wanted me to ship it to Asia for repair because CA faculty was closed due to virus. The agreed to honor my request to wait for CA to re-open..... but..... I'm still waiting.
It's running fine on two boards, but was wonder what kind of costs i might incur to ship to NC dude for repair. Might even be able to hand deliver... I have several friends from here in PA who work down there, and they go back n forth often.
Title: Re: S17 Pro no longer hashing. Bad ASICs ?
Post by: Philipma1957cellphone on August 05, 2020, 03:38:41 PM
@philipma1957
Was it you that said somewhere you have a repair contact in NC somewhere? I got and S17+ for almost free with my Bitmain credit just prior to the virus. One board isnt reading (temp sensor error). I created a DOA repair ticket with Bitmain, and they wanted me to ship it to Asia for repair because CA faculty was closed due to virus. The agreed to honor my request to wait for CA to re-open..... but..... I'm still waiting.
It's running fine on two boards, but was wonder what kind of costs i might incur to ship to NC dude for repair. Might even be able to hand deliver... I have several friends from here in PA who work down there, and they go back n forth often.
I do. I need to look at my threads here. Major storm knocked out power. Internet. Cable. Slowed cell phones. Let me see if I posted the link in another thread. Go to page 2 of this section. Steamtyme has a repair thread on his m20s. I gave a phone and a link copying links on a cell phone is hard for me. But the number is 919 283
Title: Re: S17 Pro no longer hashing. Bad ASICs ?
Post by: PopoJeff on August 05, 2020, 04:42:47 PM
Found it... thanks.
Title: Re: S17 Pro no longer hashing. Bad ASICs ?
Post by: Philipma1957cellphone on August 05, 2020, 04:51:38 PM
Good as I dropped the last 4 digits of phone. Let him know that you found him from bitcointalk. He fixed two of my m20s and he fixed steamtyme m20s.
Title: Re: S17 Pro no longer hashing. Bad ASICs ?
Post by: favebook on August 07, 2020, 11:26:32 AM
as bitmain stopped selling them. or any other gear.
https://shop.bitmain.com/product/detail?pid=00020200403105249382Ow2fHTq80690 Was on sale for brief moment but seems to be sold out now. There are other PSUs on sale however. To OP: Try using custom firmware if you are up for doing testing yourself. If not, try putting your miner on one side horizontally instead of vertically (low chance of success but worth trying). I had exactly the same problem with my S17 Pro 50T before as I wrote in many threads before, I couldn't get it to work properly but custom firmware helped to run it at least with 1 or 2 hashboards at the time. Didn't really narrow the problem down to either hashboards or PSU but I assume PSU was bad. Couldn't wait for new one to be in shop so I RMA-ed it (this was before corona). Not really sure what you should do here, but try checking the link I gave above every day to see if PSU comes back to shop.
Title: Re: S17 Pro no longer hashing. Bad ASICs ?
Post by: mikeywith on August 08, 2020, 11:28:01 PM
I couldn't get it to work properly but custom firmware helped to run it at least with 1 or 2 hashboards at the time. Didn't really narrow the problem down to either hashboards or PSU but I assume PSU was bad. Couldn't wait for new one to be in shop so I RMA-ed it (this was before corona).
It was more than likely a PSU issue, I have had the same issue on one of friend's S17 pro as well, and running the miner on low-power-mode fixed the issue. https://i.ibb.co/449P11q/sleep.png (https://i.ibb.co/449P11q/sleep.png) So what happened was that the PSU wasn't exactly dead but it couldn't deliver enough power to run the hash boards on turbo or normal mode, what the custom firmware did to your miner was probably nothing different, it has probably tuned the hashboards to work on a lower frequency and voltage so then the PSU was good enough to run 1-2 hashboards. It's worth saying that after running this bad PSU for about 2 weeks, it finally got to the point whereby it couldn't handle the low-power-mode either and it had to be replaced, this, of course, depends on the how damaged the PSU is, but as long as it can't run the miner with the stock firmware on the default settings then it's always a good idea to get a replacement as soon as possible.
Title: Re: S17 Pro no longer hashing. Bad ASICs ?
Post by: favebook on August 09, 2020, 01:41:25 AM
Exactly the same thing happened to me. Ran on Normal/Turbo for months and then one day it just dropped one hashboard, I immediately went LP mode and it worked for a few days w/o problems, and then from that point every day was worse and worse. It wouldn't run Turbo and Normal at all, or sometime it would run all 3 hashboards on Turbo but none on LP. Other times, it would see couple of chips on couple of boards but not run them. A lot of restarting kinda got me to use it for a month before I RMA-ed it.
But yeah, when I went with Vnish firmware, I literally started fiddling with all the different combos of voltage and frequency, it kept working on one hashboard or maximum two. And the one week it decided it was over. It just said: "NO! You've abused me enough, I will not mine for you anymore". And that's where I decided to RMA it's ass.
Title: Re: S17 Pro no longer hashing. Bad ASICs ?
Post by: agilmore on August 09, 2020, 10:58:18 PM
I've cleaned it and let it run in Low Power Mode. Neither the Fault or Normal lights are on. Any suggestions? Do I need to replace the PSU? It's a S17 Pro 50T and out of warranty. Kernel Log: 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: 190356K/245760K available (6345K kernel code, 231K rwdata, 1896K rodata, 1024K init, 223K bss, 39020K reserved, 16384K cma-reserved, 0K highmem)
Virtual kernel memory layout:
vector : 0xffff0000 - 0xffff1000 ( 4 kB)
fixmap : 0xffc00000 - 0xfff00000 (3072 kB)
vmalloc : 0xcf800000 - 0xff800000 ( 768 MB)
lowmem : 0xc0000000 - 0xcf000000 ( 240 MB)
pkmap : 0xbfe00000 - 0xc0000000 ( 2 MB)
modules : 0xbf000000 - 0xbfe00000 ( 14 MB)
.text : 0xc0008000 - 0xc090c424 (9234 kB)
.init : 0xc0a00000 - 0xc0b00000 (1024 kB)
.data : 0xc0b00000 - 0xc0b39fe0 ( 232 kB)
.bss : 0xc0b39fe0 - 0xc0b71c28 ( 224 kB)
Preemptible hierarchical RCU implementation.
Build-time adjustment of leaf fanout to 32.
RCU restricting CPUs from NR_CPUS=4 to nr_cpu_ids=2.
RCU: Adjusting geometry for rcu_fanout_leaf=32, nr_cpu_ids=2
NR_IRQS:16 nr_irqs:16 16
efuse mapped to cf800000
ps7-slcr mapped to cf802000
L2C: platform modifies aux control register: 0x72360000 -> 0x72760000
L2C: DT/platform modifies aux control register: 0x72360000 -> 0x72760000
L2C-310 erratum 769419 enabled
L2C-310 enabling early BRESP for Cortex-A9
L2C-310 full line of zeros enabled for Cortex-A9
L2C-310 ID prefetch enabled, offset 1 lines
L2C-310 dynamic clock gating enabled, standby mode enabled
L2C-310 cache controller enabled, 8 ways, 512 kB
L2C-310: CACHE_ID 0x410000c8, AUX_CTRL 0x76760001
zynq_clock_init: clkc starts at cf802100
Zynq clock init
sched_clock: 64 bits at 333MHz, resolution 3ns, wraps every 4398046511103ns
clocksource: arm_global_timer: mask: 0xffffffffffffffff max_cycles: 0x4ce07af025, max_idle_ns: 440795209040 ns
Switching to timer-based delay loop, resolution 3ns
clocksource: ttc_clocksource: mask: 0xffff max_cycles: 0xffff, max_idle_ns: 537538477 ns
ps7-ttc #0 at cf80a000, irq=18
Console: colour dummy device 80x30
Calibrating delay loop (skipped), value calculated using timer frequency.. 666.66 BogoMIPS (lpj=3333333)
pid_max: default: 32768 minimum: 301
Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
CPU: Testing write buffer coherency: ok
CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
Setting up static identity map for 0x100000 - 0x100058
CPU1: failed to boot: -1
Brought up 1 CPUs
SMP: Total of 1 processors activated (666.66 BogoMIPS).
CPU: All CPU(s) started in SVC mode.
devtmpfs: initialized
VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4
clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
pinctrl core: initialized pinctrl subsystem
NET: Registered protocol family 16
DMA: preallocated 256 KiB pool for atomic coherent allocations
cpuidle: using governor menu
hw-breakpoint: found 5 (+1 reserved) breakpoint and 1 watchpoint registers.
hw-breakpoint: maximum watchpoint size is 4 bytes.
zynq-ocm f800c000.ps7-ocmc: ZYNQ OCM pool: 256 KiB @ 0xcf880000
vgaarb: loaded
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
media: Linux media interface: v0.10
Linux video capture interface: v2.00
pps_core: LinuxPPS API ver. 1 registered
pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
PTP clock support registered
EDAC MC: Ver: 3.0.0
Advanced Linux Sound Architecture Driver Initialized.
clocksource: Switched to clocksource arm_global_timer
NET: Registered protocol family 2
TCP established hash table entries: 2048 (order: 1, 8192 bytes)
TCP bind hash table entries: 2048 (order: 2, 16384 bytes)
TCP: Hash tables configured (established 2048 bind 2048)
UDP hash table entries: 256 (order: 1, 8192 bytes)
UDP-Lite hash table entries: 256 (order: 1, 8192 bytes)
NET: Registered protocol family 1
RPC: Registered named UNIX socket transport module.
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
PCI: CLS 0 bytes, default 64
Trying to unpack rootfs image as initramfs...
rootfs image is not initramfs (no cpio magic); looks like an initrd
Freeing initrd memory: 25980K (cc1a2000 - cdb01000)
hw perfevents: enabled with armv7_cortex_a9 PMU driver, 7 counters available
futex hash table entries: 512 (order: 3, 32768 bytes)
workingset: timestamp_bits=28 max_order=16 bucket_order=0
jffs2: version 2.2. (NAND) (SUMMARY) © 2001-2006 Red Hat, Inc.
io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered (default)
dma-pl330 f8003000.ps7-dma: Loaded driver for PL330 DMAC-241330
dma-pl330 f8003000.ps7-dma: DBUFF-128x8bytes Num_Chans-8 Num_Peri-4 Num_Events-16
e0000000.serial: ttyPS0 at MMIO 0xe0000000 (irq = 158, base_baud = 6249999) is a xuartps
console [ttyPS0] enabled
xdevcfg f8007000.ps7-dev-cfg: ioremap 0xf8007000 to cf86e000
[drm] Initialized drm 1.1.0 20060810
brd: module loaded
loop: module loaded
CAN device driver interface
gpiod_set_value: invalid GPIO
libphy: MACB_mii_bus: probed
macb e000b000.ethernet eth0: Cadence GEM rev 0x00020118 at 0xe000b000 irq 31 (00:0a:35:00:00:00)
Generic PHY e000b000.etherne:00: attached PHY driver [Generic PHY] (mii_bus:phy_addr=e000b000.etherne:00, irq=-1)
e1000e: Intel(R) PRO/1000 Network Driver - 3.2.6-k
e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
ehci-pci: EHCI PCI platform driver
usbcore: registered new interface driver usb-storage
mousedev: PS/2 mouse device common for all mice
i2c /dev entries driver
Xilinx Zynq CpuIdle Driver started
sdhci: Secure Digital Host Controller Interface driver
sdhci: Copyright(c) Pierre Ossman
sdhci-pltfm: SDHCI platform and OF driver helper
mmc0: SDHCI controller on e0100000.ps7-sdio [e0100000.ps7-sdio] using ADMA
ledtrig-cpu: registered to indicate activity on CPUs
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
nand: device found, Manufacturer ID: 0x2c, Chip ID: 0xda
nand: Micron MT29F2G08ABAGAWP
nand: 256 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 128
nand: WARNING: pl35x-nand: the ECC used on your system is too weak compared to the one required by the NAND chip
Bad block table found at page 131008, version 0x01
Bad block table found at page 130944, version 0x01
6 ofpart partitions found on MTD device pl35x-nand
Creating 6 MTD partitions on "pl35x-nand":
0x000000000000-0x000002800000 : "BOOT.bin-env-dts-kernel"
0x000002800000-0x000004800000 : "ramfs"
0x000004800000-0x000005000000 : "configs"
0x000005000000-0x000006000000 : "reserve"
0x000006000000-0x000008000000 : "ramfs-bak"
0x000008000000-0x000010000000 : "reserve1"
NET: Registered protocol family 10
sit: IPv6 over IPv4 tunneling driver
NET: Registered protocol family 17
can: controller area network core (rev 20120528 abi 9)
NET: Registered protocol family 29
can: raw protocol (rev 20120528)
can: broadcast manager protocol (rev 20120528 t)
can: netlink gateway (rev 20130117) max_hops=1
zynq_pm_ioremap: no compatible node found for 'xlnx,zynq-ddrc-a05'
zynq_pm_late_init: Unable to map DDRC IO memory.
Registering SWP/SWPB emulation handler
hctosys: unable to open rtc device (rtc0)
ALSA device list:
No soundcards found.
RAMDISK: gzip image found at block 0
EXT4-fs (ram0): couldn't mount as ext3 due to feature incompatibilities
EXT4-fs (ram0): mounted filesystem without journal. Opts: (null)
VFS: Mounted root (ext4 filesystem) on device 1:0.
devtmpfs: mounted
Freeing unused kernel memory: 1024K (c0a00000 - c0b00000)
EXT4-fs (ram0): re-mounted. Opts: block_validity,delalloc,barrier,user_xattr
random: dd urandom read with 0 bits of entropy available
ubi0: attaching mtd2
ubi0: scanning is finished
ubi0: attached mtd2 (name "configs", size 8 MiB)
ubi0: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
ubi0: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
ubi0: VID header offset: 2048 (aligned 2048), data offset: 4096
ubi0: good PEBs: 64, bad PEBs: 0, corrupted PEBs: 0
ubi0: user volume: 1, internal volumes: 1, max. volumes count: 128
ubi0: max/mean erase counter: 5/2, WL threshold: 4096, image sequence number: 237714726
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 FF09433B-E002-4C29-97EC-6220DDC4BB36, 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: 4353/1931, WL threshold: 4096, image sequence number: 914180297
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 BCBDE5E0-4C0B-4978-9734-FC58D9F68227, 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 = 0xab011
In fpga mem driver!
request_mem_region OK!
fpga mem virtual address is 0xd2000000
random: nonblocking pool is initialized
[2020-08-09 22:41:50.942] httpListenThread start ret=0
[2020-08-09 22:42:20.951] start listen on 6060 ...
2020-08-09 22:41:51 driver-btm-soc.c:3160:init_freq_mode: This is scan-user version
2020-08-09 22:41:51 driver-btm-soc.c:3896:bitmain_soc_init: opt_multi_version=1
2020-08-09 22:41:51 driver-btm-soc.c:3897:bitmain_soc_init: opt_bitmain_ab=1
2020-08-09 22:41:51 driver-btm-soc.c:3898:bitmain_soc_init: opt_bitmain_work_mode=0
2020-08-09 22:41:51 driver-btm-soc.c:3521:_show_sn: no SN got, please write SN to /nvdata/sn
2020-08-09 22:41:51 driver-btm-soc.c:3191:init_phy_mem_nonce2_jobid_address: Detect 256MB control board of XILINX
2020-08-09 22:41:51 driver-btm-soc.c:3904:bitmain_soc_init: Miner compile time: Tue Apr 16 19:05:06 CST 2019
2020-08-09 22:41:51 driver-btm-soc.c:3906:bitmain_soc_init: last commit version: 8b856e7 commit time: 2019-04-16 16:36:14 build: 2019-04-16 19:09:46
2020-08-09 22:41:51 driver-btm-soc.c:3223:check_fan_multi: check fan for 20 times...
2020-08-09 22:41:53 driver-btm-soc.c:3299:init_miner_version: miner ID : 813275ce57408854
2020-08-09 22:41:53 driver-btm-soc.c:3305:init_miner_version: FPGA Version = 0xB011
2020-08-09 22:41:53 driver-btm-soc.c:404:check_chain: !! chain[0]is exist
2020-08-09 22:41:53 driver-btm-soc.c:404:check_chain: !! chain[1]is exist
2020-08-09 22:41:53 driver-btm-soc.c:404:check_chain: !! chain[2]is exist
2020-08-09 22:41:57 driver-btm-soc.c:3722:get_product_id: product_id[0] = 0
2020-08-09 22:41:57 driver-btm-soc.c:3722:get_product_id: product_id[1] = 0
2020-08-09 22:41:57 driver-btm-soc.c:3722:get_product_id: product_id[2] = 0
2020-08-09 22:41:57 driver-btm-soc.c:3823:bitmain_board_init: g_product_id = 0
2020-08-09 22:41:57 driver-btm-soc.c:3574:_set_project_type: Project type: Antminer S17 Pro
2020-08-09 22:41:57 driver-btm-soc.c:3321:dump_pcb_bom_version: Chain [0] PCB Version: 0x0101
2020-08-09 22:41:57 driver-btm-soc.c:3322:dump_pcb_bom_version: Chain [0] BOM Version: 0x0103
2020-08-09 22:41:57 driver-btm-soc.c:3321:dump_pcb_bom_version: Chain [1] PCB Version: 0x0101
2020-08-09 22:41:57 driver-btm-soc.c:3322:dump_pcb_bom_version: Chain [1] BOM Version: 0x0103
2020-08-09 22:41:57 driver-btm-soc.c:3321:dump_pcb_bom_version: Chain [2] PCB Version: 0x0101
2020-08-09 22:41:57 driver-btm-soc.c:3322:dump_pcb_bom_version: Chain [2] BOM Version: 0x0103
2020-08-09 22:41:57 pic.c:619:pic_reset: chain[0] ok
2020-08-09 22:42:02 pic.c:898:jump_to_app_from_loader: chain[0] ok
2020-08-09 22:42:02 pic.c:619:pic_reset: chain[1] ok
2020-08-09 22:42:07 pic.c:898:jump_to_app_from_loader: chain[1] ok
2020-08-09 22:42:07 pic.c:619:pic_reset: chain[2] ok
2020-08-09 22:42:12 pic.c:898:jump_to_app_from_loader: chain[2] ok
2020-08-09 22:42:12 driver-btm-soc.c:3840:bitmain_board_init: Enter 30s sleep to make sure power release finish.
2020-08-09 22:42:12 driver-btm-soc.c:1156:heart_beat_func_one_chain: for chain 2
2020-08-09 22:42:12 driver-btm-soc.c:1156:heart_beat_func_one_chain: for chain 1
2020-08-09 22:42:12 driver-btm-soc.c:1156:heart_beat_func_one_chain: for chain 0
2020-08-09 22:42:42 power.c:216:power_init: power init ...
2020-08-09 22:42:43 power.c:348:power_get_firmware_version: power firmware version is 00 07
2020-08-09 22:42:45 power.c:338:power_get_device_no: power device no is 00 41
2020-08-09 22:42:45 power.c:203:power_check_protocol_type: power protocol f5, using package cmd
2020-08-09 22:42:45 power.c:204:power_check_protocol_type: power type APW9 3600W
2020-08-09 22:42:45 power.c:155:power_on: init gpio907
2020-08-09 22:42:46 power.c:624:set_iic_power_to_highest_voltage: setting to voltage: 21.00 ...
2020-08-09 22:42:48 power.c:573:set_iic_power_by_voltage: now setting voltage to : 21.000000
2020-08-09 22:42:49 zynq.c:192:set_reset_hashboard: set_reset_hashboard = 0x0000ffff
2020-08-09 22:42:52 pic.c:234:hashboard_power_cntl: [1] ok, i2c=0!
2020-08-09 22:42:54 zynq.c:192:set_reset_hashboard: set_reset_hashboard = 0x0000fffe
2020-08-09 22:42:58 driver-btm-soc.c:3657:check_asic_number_with_power_on: Chain[0]: find 0 asic, times 0
2020-08-09 22:42:58 zynq.c:192:set_reset_hashboard: set_reset_hashboard = 0x0000ffff
2020-08-09 22:43:02 pic.c:234:hashboard_power_cntl: [1] ok, i2c=0!
2020-08-09 22:43:04 zynq.c:192:set_reset_hashboard: set_reset_hashboard = 0x0000fffe
2020-08-09 22:43:08 driver-btm-soc.c:3657:check_asic_number_with_power_on: Chain[0]: find 0 asic, times 1
2020-08-09 22:43:08 zynq.c:192:set_reset_hashboard: set_reset_hashboard = 0x0000ffff
2020-08-09 22:43:12 pic.c:234:hashboard_power_cntl: [1] ok, i2c=0!
2020-08-09 22:43:14 zynq.c:192:set_reset_hashboard: set_reset_hashboard = 0x0000fffe
2020-08-09 22:43:18 driver-btm-soc.c:3657:check_asic_number_with_power_on: Chain[0]: find 0 asic, times 2
2020-08-09 22:43:18 driver-btm-soc.c:3682:check_asic_number: Chain 0 only find 0 asic, will power off hash board 0
2020-08-09 22:43:19 pic.c:234:hashboard_power_cntl: [0] ok, i2c=0!
2020-08-09 22:43:19 zynq.c:192:set_reset_hashboard: set_reset_hashboard = 0x0000fffe
2020-08-09 22:43:22 pic.c:234:hashboard_power_cntl: [1] ok, i2c=1!
2020-08-09 22:43:24 zynq.c:192:set_reset_hashboard: set_reset_hashboard = 0x0000fffc
2020-08-09 22:43:29 driver-btm-soc.c:3657:check_asic_number_with_power_on: Chain[1]: find 0 asic, times 0
2020-08-09 22:43:29 zynq.c:192:set_reset_hashboard: set_reset_hashboard = 0x0000fffe
2020-08-09 22:43:32 pic.c:234:hashboard_power_cntl: [1] ok, i2c=1!
2020-08-09 22:43:34 zynq.c:192:set_reset_hashboard: set_reset_hashboard = 0x0000fffc
2020-08-09 22:43:38 driver-btm-soc.c:3657:check_asic_number_with_power_on: Chain[1]: find 0 asic, times 1
2020-08-09 22:43:38 zynq.c:192:set_reset_hashboard: set_reset_hashboard = 0x0000fffe
2020-08-09 22:43:42 pic.c:234:hashboard_power_cntl: [1] ok, i2c=1!
2020-08-09 22:43:44 zynq.c:192:set_reset_hashboard: set_reset_hashboard = 0x0000fffc
2020-08-09 22:43:48 driver-btm-soc.c:3657:check_asic_number_with_power_on: Chain[1]: find 0 asic, times 2
2020-08-09 22:43:48 driver-btm-soc.c:3682:check_asic_number: Chain 1 only find 0 asic, will power off hash board 1
2020-08-09 22:43:49 pic.c:234:hashboard_power_cntl: [0] ok, i2c=1!
2020-08-09 22:43:49 zynq.c:192:set_reset_hashboard: set_reset_hashboard = 0x0000fffc
2020-08-09 22:43:52 pic.c:234:hashboard_power_cntl: [1] ok, i2c=2!
2020-08-09 22:43:54 zynq.c:192:set_reset_hashboard: set_reset_hashboard = 0x0000fff8
2020-08-09 22:43:58 driver-btm-soc.c:3657:check_asic_number_with_power_on: Chain[2]: find 0 asic, times 0
2020-08-09 22:43:58 zynq.c:192:set_reset_hashboard: set_reset_hashboard = 0x0000fffc
2020-08-09 22:44:02 pic.c:234:hashboard_power_cntl: [1] ok, i2c=2!
2020-08-09 22:44:04 zynq.c:192:set_reset_hashboard: set_reset_hashboard = 0x0000fff8
2020-08-09 22:44:08 driver-btm-soc.c:3657:check_asic_number_with_power_on: Chain[2]: find 0 asic, times 1
2020-08-09 22:44:08 zynq.c:192:set_reset_hashboard: set_reset_hashboard = 0x0000fffc
2020-08-09 22:44:12 pic.c:234:hashboard_power_cntl: [1] ok, i2c=2!
2020-08-09 22:44:14 zynq.c:192:set_reset_hashboard: set_reset_hashboard = 0x0000fff8
2020-08-09 22:44:18 driver-btm-soc.c:3657:check_asic_number_with_power_on: Chain[2]: find 0 asic, times 2
2020-08-09 22:44:18 driver-btm-soc.c:3682:check_asic_number: Chain 2 only find 0 asic, will power off hash board 2
2020-08-09 22:44:19 pic.c:234:hashboard_power_cntl: [0] ok, i2c=2!
2020-08-09 22:44:19 util.c:2178:process_version_mask: Pool 1 Verion num is 4
2020-08-09 22:44:19 util.c:2178:process_version_mask: Pool 0 Verion num is 4
2020-08-09 22:44:19 util.c:2178:process_version_mask: Pool 0 Verion num is 4
total rate = 0
total rate = 0
total rate = 0
total rate = 0
total rate = 0
total rate = 0
total rate = 0
Title: Re: S17 Pro no longer hashing. Bad ASICs ?
Post by: mikeywith on August 10, 2020, 02:44:36 PM
Nothing has changed sadly. driver-btm-soc.c:3657:check_asic_number_with_power_on: Chain[0]: find 0 asic, times 0 driver-btm-soc.c:3657:check_asic_number_with_power_on: Chain[1]: find 0 asic, times 1 driver-btm-soc.c:3657:check_asic_number_with_power_on: Chain[2]: find 0 asic, times 0 I am now 99% sure you need to replace the PSU, do you have another S17 pro? or even S17 / T17 since these 3 use the same PSU, one last thing I would try before getting a new PSU is to Sdcard flash the control board and flash a custom firmware for testing, if that doesn't solve the problem then nothing left to do but to get a PSU for about $100.
Title: Re: S17 Pro no longer hashing. Bad ASICs ?
Post by: agilmore on August 23, 2020, 10:48:48 PM
I've replaced the PSU and still don't see any improvement. Here's the kernel log: 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: 190356K/245760K available (6345K kernel code, 231K rwdata, 1896K rodata, 1024K init, 223K bss, 39020K reserved, 16384K cma-reserved, 0K highmem)
Virtual kernel memory layout:
vector : 0xffff0000 - 0xffff1000 ( 4 kB)
fixmap : 0xffc00000 - 0xfff00000 (3072 kB)
vmalloc : 0xcf800000 - 0xff800000 ( 768 MB)
lowmem : 0xc0000000 - 0xcf000000 ( 240 MB)
pkmap : 0xbfe00000 - 0xc0000000 ( 2 MB)
modules : 0xbf000000 - 0xbfe00000 ( 14 MB)
.text : 0xc0008000 - 0xc090c424 (9234 kB)
.init : 0xc0a00000 - 0xc0b00000 (1024 kB)
.data : 0xc0b00000 - 0xc0b39fe0 ( 232 kB)
.bss : 0xc0b39fe0 - 0xc0b71c28 ( 224 kB)
Preemptible hierarchical RCU implementation.
Build-time adjustment of leaf fanout to 32.
RCU restricting CPUs from NR_CPUS=4 to nr_cpu_ids=2.
RCU: Adjusting geometry for rcu_fanout_leaf=32, nr_cpu_ids=2
NR_IRQS:16 nr_irqs:16 16
efuse mapped to cf800000
ps7-slcr mapped to cf802000
L2C: platform modifies aux control register: 0x72360000 -> 0x72760000
L2C: DT/platform modifies aux control register: 0x72360000 -> 0x72760000
L2C-310 erratum 769419 enabled
L2C-310 enabling early BRESP for Cortex-A9
L2C-310 full line of zeros enabled for Cortex-A9
L2C-310 ID prefetch enabled, offset 1 lines
L2C-310 dynamic clock gating enabled, standby mode enabled
L2C-310 cache controller enabled, 8 ways, 512 kB
L2C-310: CACHE_ID 0x410000c8, AUX_CTRL 0x76760001
zynq_clock_init: clkc starts at cf802100
Zynq clock init
sched_clock: 64 bits at 333MHz, resolution 3ns, wraps every 4398046511103ns
clocksource: arm_global_timer: mask: 0xffffffffffffffff max_cycles: 0x4ce07af025, max_idle_ns: 440795209040 ns
Switching to timer-based delay loop, resolution 3ns
clocksource: ttc_clocksource: mask: 0xffff max_cycles: 0xffff, max_idle_ns: 537538477 ns
ps7-ttc #0 at cf80a000, irq=18
Console: colour dummy device 80x30
Calibrating delay loop (skipped), value calculated using timer frequency.. 666.66 BogoMIPS (lpj=3333333)
pid_max: default: 32768 minimum: 301
Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
CPU: Testing write buffer coherency: ok
CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
Setting up static identity map for 0x100000 - 0x100058
CPU1: failed to boot: -1
Brought up 1 CPUs
SMP: Total of 1 processors activated (666.66 BogoMIPS).
CPU: All CPU(s) started in SVC mode.
devtmpfs: initialized
VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4
clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
pinctrl core: initialized pinctrl subsystem
NET: Registered protocol family 16
DMA: preallocated 256 KiB pool for atomic coherent allocations
cpuidle: using governor menu
hw-breakpoint: found 5 (+1 reserved) breakpoint and 1 watchpoint registers.
hw-breakpoint: maximum watchpoint size is 4 bytes.
zynq-ocm f800c000.ps7-ocmc: ZYNQ OCM pool: 256 KiB @ 0xcf880000
vgaarb: loaded
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
media: Linux media interface: v0.10
Linux video capture interface: v2.00
pps_core: LinuxPPS API ver. 1 registered
pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
PTP clock support registered
EDAC MC: Ver: 3.0.0
Advanced Linux Sound Architecture Driver Initialized.
clocksource: Switched to clocksource arm_global_timer
NET: Registered protocol family 2
TCP established hash table entries: 2048 (order: 1, 8192 bytes)
TCP bind hash table entries: 2048 (order: 2, 16384 bytes)
TCP: Hash tables configured (established 2048 bind 2048)
UDP hash table entries: 256 (order: 1, 8192 bytes)
UDP-Lite hash table entries: 256 (order: 1, 8192 bytes)
NET: Registered protocol family 1
RPC: Registered named UNIX socket transport module.
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
PCI: CLS 0 bytes, default 64
Trying to unpack rootfs image as initramfs...
rootfs image is not initramfs (no cpio magic); looks like an initrd
Freeing initrd memory: 25980K (cc1a2000 - cdb01000)
hw perfevents: enabled with armv7_cortex_a9 PMU driver, 7 counters available
futex hash table entries: 512 (order: 3, 32768 bytes)
workingset: timestamp_bits=28 max_order=16 bucket_order=0
jffs2: version 2.2. (NAND) (SUMMARY) © 2001-2006 Red Hat, Inc.
io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered (default)
dma-pl330 f8003000.ps7-dma: Loaded driver for PL330 DMAC-241330
dma-pl330 f8003000.ps7-dma: DBUFF-128x8bytes Num_Chans-8 Num_Peri-4 Num_Events-16
e0000000.serial: ttyPS0 at MMIO 0xe0000000 (irq = 158, base_baud = 6249999) is a xuartps
console [ttyPS0] enabled
xdevcfg f8007000.ps7-dev-cfg: ioremap 0xf8007000 to cf86e000
[drm] Initialized drm 1.1.0 20060810
brd: module loaded
loop: module loaded
CAN device driver interface
gpiod_set_value: invalid GPIO
libphy: MACB_mii_bus: probed
macb e000b000.ethernet eth0: Cadence GEM rev 0x00020118 at 0xe000b000 irq 31 (00:0a:35:00:00:00)
Generic PHY e000b000.etherne:00: attached PHY driver [Generic PHY] (mii_bus:phy_addr=e000b000.etherne:00, irq=-1)
e1000e: Intel(R) PRO/1000 Network Driver - 3.2.6-k
e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
ehci-pci: EHCI PCI platform driver
usbcore: registered new interface driver usb-storage
mousedev: PS/2 mouse device common for all mice
i2c /dev entries driver
Xilinx Zynq CpuIdle Driver started
sdhci: Secure Digital Host Controller Interface driver
sdhci: Copyright(c) Pierre Ossman
sdhci-pltfm: SDHCI platform and OF driver helper
mmc0: SDHCI controller on e0100000.ps7-sdio [e0100000.ps7-sdio] using ADMA
ledtrig-cpu: registered to indicate activity on CPUs
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
nand: device found, Manufacturer ID: 0x2c, Chip ID: 0xda
nand: Micron MT29F2G08ABAGAWP
nand: 256 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 128
nand: WARNING: pl35x-nand: the ECC used on your system is too weak compared to the one required by the NAND chip
Bad block table found at page 131008, version 0x01
Bad block table found at page 130944, version 0x01
6 ofpart partitions found on MTD device pl35x-nand
Creating 6 MTD partitions on "pl35x-nand":
0x000000000000-0x000002800000 : "BOOT.bin-env-dts-kernel"
0x000002800000-0x000004800000 : "ramfs"
0x000004800000-0x000005000000 : "configs"
0x000005000000-0x000006000000 : "reserve"
0x000006000000-0x000008000000 : "ramfs-bak"
0x000008000000-0x000010000000 : "reserve1"
NET: Registered protocol family 10
sit: IPv6 over IPv4 tunneling driver
NET: Registered protocol family 17
can: controller area network core (rev 20120528 abi 9)
NET: Registered protocol family 29
can: raw protocol (rev 20120528)
can: broadcast manager protocol (rev 20120528 t)
can: netlink gateway (rev 20130117) max_hops=1
zynq_pm_ioremap: no compatible node found for 'xlnx,zynq-ddrc-a05'
zynq_pm_late_init: Unable to map DDRC IO memory.
Registering SWP/SWPB emulation handler
hctosys: unable to open rtc device (rtc0)
ALSA device list:
No soundcards found.
RAMDISK: gzip image found at block 0
EXT4-fs (ram0): couldn't mount as ext3 due to feature incompatibilities
EXT4-fs (ram0): mounted filesystem without journal. Opts: (null)
VFS: Mounted root (ext4 filesystem) on device 1:0.
devtmpfs: mounted
Freeing unused kernel memory: 1024K (c0a00000 - c0b00000)
EXT4-fs (ram0): re-mounted. Opts: block_validity,delalloc,barrier,user_xattr
random: dd urandom read with 0 bits of entropy available
ubi0: attaching mtd2
ubi0: scanning is finished
ubi0: attached mtd2 (name "configs", size 8 MiB)
ubi0: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
ubi0: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
ubi0: VID header offset: 2048 (aligned 2048), data offset: 4096
ubi0: good PEBs: 64, bad PEBs: 0, corrupted PEBs: 0
ubi0: user volume: 1, internal volumes: 1, max. volumes count: 128
ubi0: max/mean erase counter: 5/2, WL threshold: 4096, image sequence number: 237714726
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 FF09433B-E002-4C29-97EC-6220DDC4BB36, 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: 4353/1931, WL threshold: 4096, image sequence number: 914180297
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 BCBDE5E0-4C0B-4978-9734-FC58D9F68227, 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 = 0xab011
In fpga mem driver!
request_mem_region OK!
fpga mem virtual address is 0xd2000000
random: nonblocking pool is initialized
Alignment trap: cg@0/RStratum (1958) PC=0x00020c54 Instr=0xedd20b1a Address=0x00000089 FSR 0x001
Alignment trap: not handling instruction edd20b1a at [<00020c54>]
Unhandled fault: alignment exception (0x001) at 0x00000089
pgd = cbf58000
[00000089] *pgd=058f6831, *pte=00000000, *ppte=00000000
Alignment trap: cg@0/RStratum (2424) PC=0x00020c54 Instr=0xedd20b1a Address=0x00000089 FSR 0x001
Alignment trap: not handling instruction edd20b1a at [<00020c54>]
Unhandled fault: alignment exception (0x001) at 0x00000089
pgd = c8d8c000
[00000089] *pgd=03d4a831, *pte=00000000, *ppte=00000000
[2020-08-23 22:41:08.424] httpListenThread start ret=0
[2020-08-23 22:41:38.428] start listen on 6060 ...
2020-08-23 22:41:08 driver-btm-soc.c:3160:init_freq_mode: This is scan-user version
2020-08-23 22:41:08 driver-btm-soc.c:3896:bitmain_soc_init: opt_multi_version=1
2020-08-23 22:41:08 driver-btm-soc.c:3897:bitmain_soc_init: opt_bitmain_ab=1
2020-08-23 22:41:08 driver-btm-soc.c:3898:bitmain_soc_init: opt_bitmain_work_mode=1
2020-08-23 22:41:08 driver-btm-soc.c:3521:_show_sn: no SN got, please write SN to /nvdata/sn
2020-08-23 22:41:08 driver-btm-soc.c:3191:init_phy_mem_nonce2_jobid_address: Detect 256MB control board of XILINX
2020-08-23 22:41:08 driver-btm-soc.c:3904:bitmain_soc_init: Miner compile time: Tue Apr 16 19:05:06 CST 2019
2020-08-23 22:41:08 driver-btm-soc.c:3906:bitmain_soc_init: last commit version: 8b856e7 commit time: 2019-04-16 16:36:14 build: 2019-04-16 19:09:46
2020-08-23 22:41:08 driver-btm-soc.c:3223:check_fan_multi: check fan for 20 times...
2020-08-23 22:41:10 driver-btm-soc.c:3299:init_miner_version: miner ID : 813275ce57408854
2020-08-23 22:41:10 driver-btm-soc.c:3305:init_miner_version: FPGA Version = 0xB011
2020-08-23 22:41:10 driver-btm-soc.c:404:check_chain: !! chain[0]is exist
2020-08-23 22:41:10 driver-btm-soc.c:404:check_chain: !! chain[1]is exist
2020-08-23 22:41:10 driver-btm-soc.c:404:check_chain: !! chain[2]is exist
2020-08-23 22:41:14 driver-btm-soc.c:3722:get_product_id: product_id[0] = 0
2020-08-23 22:41:14 driver-btm-soc.c:3722:get_product_id: product_id[1] = 0
2020-08-23 22:41:14 driver-btm-soc.c:3722:get_product_id: product_id[2] = 0
2020-08-23 22:41:14 driver-btm-soc.c:3823:bitmain_board_init: g_product_id = 0
2020-08-23 22:41:14 driver-btm-soc.c:3574:_set_project_type: Project type: Antminer S17 Pro
2020-08-23 22:41:14 driver-btm-soc.c:3321:dump_pcb_bom_version: Chain [0] PCB Version: 0x0101
2020-08-23 22:41:14 driver-btm-soc.c:3322:dump_pcb_bom_version: Chain [0] BOM Version: 0x0103
2020-08-23 22:41:14 driver-btm-soc.c:3321:dump_pcb_bom_version: Chain [1] PCB Version: 0x0101
2020-08-23 22:41:14 driver-btm-soc.c:3322:dump_pcb_bom_version: Chain [1] BOM Version: 0x0103
2020-08-23 22:41:14 driver-btm-soc.c:3321:dump_pcb_bom_version: Chain [2] PCB Version: 0x0101
2020-08-23 22:41:14 driver-btm-soc.c:3322:dump_pcb_bom_version: Chain [2] BOM Version: 0x0103
2020-08-23 22:41:15 pic.c:619:pic_reset: chain[0] ok
2020-08-23 22:41:19 pic.c:898:jump_to_app_from_loader: chain[0] ok
2020-08-23 22:41:20 pic.c:619:pic_reset: chain[1] ok
2020-08-23 22:41:24 pic.c:898:jump_to_app_from_loader: chain[1] ok
2020-08-23 22:41:25 pic.c:619:pic_reset: chain[2] ok
2020-08-23 22:41:29 pic.c:898:jump_to_app_from_loader: chain[2] ok
2020-08-23 22:41:29 driver-btm-soc.c:3840:bitmain_board_init: Enter 30s sleep to make sure power release finish.
2020-08-23 22:41:29 driver-btm-soc.c:1156:heart_beat_func_one_chain: for chain 2
2020-08-23 22:41:29 driver-btm-soc.c:1156:heart_beat_func_one_chain: for chain 1
2020-08-23 22:41:29 driver-btm-soc.c:1156:heart_beat_func_one_chain: for chain 0
2020-08-23 22:41:59 power.c:216:power_init: power init ...
2020-08-23 22:42:01 power.c:348:power_get_firmware_version: power firmware version is 00 07
2020-08-23 22:42:02 power.c:338:power_get_device_no: power device no is 00 41
2020-08-23 22:42:02 power.c:203:power_check_protocol_type: power protocol f5, using package cmd
2020-08-23 22:42:02 power.c:204:power_check_protocol_type: power type APW9 3600W
2020-08-23 22:42:03 power.c:624:set_iic_power_to_highest_voltage: setting to voltage: 21.00 ...
2020-08-23 22:42:06 power.c:573:set_iic_power_by_voltage: now setting voltage to : 21.000000
2020-08-23 22:42:06 zynq.c:192:set_reset_hashboard: set_reset_hashboard = 0x0000fff9
2020-08-23 22:42:10 pic.c:234:hashboard_power_cntl: [1] ok, i2c=0!
2020-08-23 22:42:12 zynq.c:192:set_reset_hashboard: set_reset_hashboard = 0x0000fff8
2020-08-23 22:42:16 driver-btm-soc.c:3657:check_asic_number_with_power_on: Chain[0]: find 0 asic, times 0
2020-08-23 22:42:16 zynq.c:192:set_reset_hashboard: set_reset_hashboard = 0x0000fff9
2020-08-23 22:42:19 pic.c:234:hashboard_power_cntl: [1] ok, i2c=0!
2020-08-23 22:42:21 zynq.c:192:set_reset_hashboard: set_reset_hashboard = 0x0000fff8
2020-08-23 22:42:26 driver-btm-soc.c:3657:check_asic_number_with_power_on: Chain[0]: find 0 asic, times 1
2020-08-23 22:42:26 zynq.c:192:set_reset_hashboard: set_reset_hashboard = 0x0000fff9
2020-08-23 22:42:29 pic.c:234:hashboard_power_cntl: [1] ok, i2c=0!
2020-08-23 22:42:31 zynq.c:192:set_reset_hashboard: set_reset_hashboard = 0x0000fff8
2020-08-23 22:42:35 driver-btm-soc.c:3657:check_asic_number_with_power_on: Chain[0]: find 0 asic, times 2
2020-08-23 22:42:35 driver-btm-soc.c:3682:check_asic_number: Chain 0 only find 0 asic, will power off hash board 0
2020-08-23 22:42:36 pic.c:234:hashboard_power_cntl: [0] ok, i2c=0!
2020-08-23 22:42:36 zynq.c:192:set_reset_hashboard: set_reset_hashboard = 0x0000fffa
2020-08-23 22:42:40 pic.c:234:hashboard_power_cntl: [1] ok, i2c=1!
2020-08-23 22:42:42 zynq.c:192:set_reset_hashboard: set_reset_hashboard = 0x0000fff8
2020-08-23 22:42:46 driver-btm-soc.c:3657:check_asic_number_with_power_on: Chain[1]: find 0 asic, times 0
2020-08-23 22:42:46 zynq.c:192:set_reset_hashboard: set_reset_hashboard = 0x0000fffa
2020-08-23 22:42:50 pic.c:234:hashboard_power_cntl: [1] ok, i2c=1!
2020-08-23 22:42:52 zynq.c:192:set_reset_hashboard: set_reset_hashboard = 0x0000fff8
2020-08-23 22:42:56 driver-btm-soc.c:3657:check_asic_number_with_power_on: Chain[1]: find 0 asic, times 1
2020-08-23 22:42:56 zynq.c:192:set_reset_hashboard: set_reset_hashboard = 0x0000fffa
2020-08-23 22:42:59 pic.c:234:hashboard_power_cntl: [1] ok, i2c=1!
2020-08-23 22:43:01 zynq.c:192:set_reset_hashboard: set_reset_hashboard = 0x0000fff8
2020-08-23 22:43:06 driver-btm-soc.c:3657:check_asic_number_with_power_on: Chain[1]: find 0 asic, times 2
2020-08-23 22:43:06 driver-btm-soc.c:3682:check_asic_number: Chain 1 only find 0 asic, will power off hash board 1
2020-08-23 22:43:06 pic.c:234:hashboard_power_cntl: [0] ok, i2c=1!
2020-08-23 22:43:06 zynq.c:192:set_reset_hashboard: set_reset_hashboard = 0x0000fffc
2020-08-23 22:43:10 pic.c:234:hashboard_power_cntl: [1] ok, i2c=2!
2020-08-23 22:43:12 zynq.c:192:set_reset_hashboard: set_reset_hashboard = 0x0000fff8
2020-08-23 22:43:16 driver-btm-soc.c:3657:check_asic_number_with_power_on: Chain[2]: find 0 asic, times 0
2020-08-23 22:43:16 zynq.c:192:set_reset_hashboard: set_reset_hashboard = 0x0000fffc
2020-08-23 22:43:19 pic.c:234:hashboard_power_cntl: [1] ok, i2c=2!
2020-08-23 22:43:21 zynq.c:192:set_reset_hashboard: set_reset_hashboard = 0x0000fff8
2020-08-23 22:43:26 driver-btm-soc.c:3657:check_asic_number_with_power_on: Chain[2]: find 0 asic, times 1
2020-08-23 22:43:26 zynq.c:192:set_reset_hashboard: set_reset_hashboard = 0x0000fffc
2020-08-23 22:43:29 pic.c:234:hashboard_power_cntl: [1] ok, i2c=2!
2020-08-23 22:43:31 zynq.c:192:set_reset_hashboard: set_reset_hashboard = 0x0000fff8
2020-08-23 22:43:36 driver-btm-soc.c:3657:check_asic_number_with_power_on: Chain[2]: find 0 asic, times 2
2020-08-23 22:43:36 driver-btm-soc.c:3682:check_asic_number: Chain 2 only find 0 asic, will power off hash board 2
2020-08-23 22:43:36 pic.c:234:hashboard_power_cntl: [0] ok, i2c=2!
2020-08-23 22:43:36 util.c:2178:process_version_mask: Pool 0 Verion num is 4
2020-08-23 22:43:36 util.c:2178:process_version_mask: Pool 0 Verion num is 4
2020-08-23 22:43:39 driver-btm-soc.c:4183:send_job: Version num 4
total rate = 0
total rate = 0
total rate = 0
total rate = 0
Screenshots: https://imgur.com/a/XoC9bhT
Title: Re: S17 Pro no longer hashing. Bad ASICs ?
Post by: mikeywith on August 23, 2020, 11:01:13 PM
That is very strange, the kernel log is almost identical to the first one, have you flashed the miner using an Sdcard prior to or after the replacement of the PSU? also, are you sure you have installed the PSU correctly? also, have you tried custom firmware?
The kernel log now suggest that all 3 boards are dead, it's possible but it's really a very small probability, obviously, you could be that unlucky and all 3 dashboards went down at the same time, but I still find it hard to believe so, so let's troubleshoot this even further.
Start with Sdcard flash, do not upgrade to the latest firmware, flash Vnish firmware from AwesomeMiner or Asic.to.
Title: Re: S17 Pro no longer hashing. Bad ASICs ?
Post by: agilmore on August 23, 2020, 11:09:52 PM
I'm guessing that I replaced it correctly. Power is on, the little fans are on. There are only 2 cables that plug into the PSU. I haven't attempted to flash the miner. Can you point me to the instructions ?
Title: Re: S17 Pro no longer hashing. Bad ASICs ?
Post by: BitMaxz on August 23, 2020, 11:24:13 PM
I'm guessing that I replaced it correctly. Power is on, the little fans are on. There are only 2 cables that plug into the PSU. I haven't attempted to flash the miner. Can you point me to the instructions ?
You can follow the instruction from Bitmain here "S17/S17Pro/S9 SE/S9k/Z11 control board program recovery (SD card flashing with customized PW) (https://support.bitmain.com/hc/en-us/articles/360033757513-S17-S17Pro-S9-SE-S9k-Z11-control-board-program-recovery-SD-card-flashing-with-customized-PW-)" The only problem you will need to contact Bitmain to get the SD card image. I just can't remember the thread that someone shares the mp test firmware image for s17 here on the forum. I'm going to find it and I'll update this post soon.
Title: Re: S17 Pro no longer hashing. Bad ASICs ?
Post by: mikeywith on August 24, 2020, 11:19:31 AM
The only problem you will need to contact Bitmain to get the SD card image.
There is no need for that, you can use the link from asic.to which is here > https://mega.nz/folder/Wo0wHS4J#9WvygRhcT5Qo5aM-jPSrrg You will not find S17 pro firmware, but it's the same as the S17/T17 so chose whatever you want, make sure you extract the files to the main directory of your sdcard and not into a sub folder, keep us updated.
Title: Re: S17 Pro no longer hashing. Bad ASICs ?
Post by: agilmore on August 28, 2020, 09:25:39 PM
I think this jacked up my miner. I see this message " WARNING! OLD VERSION CONFIG FILE DETECTED!" and the UI doesnt look anything like the factory model. It looks worse off than before.....lol. I used the S17 and S17+ FM...the same result for both. 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: 202804K/245760K available (6345K kernel code, 231K rwdata, 1896K rodata, 1024K init, 223K bss, 26572K reserved, 16384K cma-reserved, 0K highmem)
Virtual kernel memory layout:
vector : 0xffff0000 - 0xffff1000 ( 4 kB)
fixmap : 0xffc00000 - 0xfff00000 (3072 kB)
vmalloc : 0xcf800000 - 0xff800000 ( 768 MB)
lowmem : 0xc0000000 - 0xcf000000 ( 240 MB)
pkmap : 0xbfe00000 - 0xc0000000 ( 2 MB)
modules : 0xbf000000 - 0xbfe00000 ( 14 MB)
.text : 0xc0008000 - 0xc090c424 (9234 kB)
.init : 0xc0a00000 - 0xc0b00000 (1024 kB)
.data : 0xc0b00000 - 0xc0b39fe0 ( 232 kB)
.bss : 0xc0b39fe0 - 0xc0b71c28 ( 224 kB)
Preemptible hierarchical RCU implementation.
Build-time adjustment of leaf fanout to 32.
RCU restricting CPUs from NR_CPUS=4 to nr_cpu_ids=2.
RCU: Adjusting geometry for rcu_fanout_leaf=32, nr_cpu_ids=2
NR_IRQS:16 nr_irqs:16 16
efuse mapped to cf800000
ps7-slcr mapped to cf802000
L2C: platform modifies aux control register: 0x72360000 -> 0x72760000
L2C: DT/platform modifies aux control register: 0x72360000 -> 0x72760000
L2C-310 erratum 769419 enabled
L2C-310 enabling early BRESP for Cortex-A9
L2C-310 full line of zeros enabled for Cortex-A9
L2C-310 ID prefetch enabled, offset 1 lines
L2C-310 dynamic clock gating enabled, standby mode enabled
L2C-310 cache controller enabled, 8 ways, 512 kB
L2C-310: CACHE_ID 0x410000c8, AUX_CTRL 0x76760001
zynq_clock_init: clkc starts at cf802100
Zynq clock init
sched_clock: 64 bits at 333MHz, resolution 3ns, wraps every 4398046511103ns
clocksource: arm_global_timer: mask: 0xffffffffffffffff max_cycles: 0x4ce07af025, max_idle_ns: 440795209040 ns
Switching to timer-based delay loop, resolution 3ns
clocksource: ttc_clocksource: mask: 0xffff max_cycles: 0xffff, max_idle_ns: 537538477 ns
ps7-ttc #0 at cf80a000, irq=18
Console: colour dummy device 80x30
Calibrating delay loop (skipped), value calculated using timer frequency.. 666.66 BogoMIPS (lpj=3333333)
pid_max: default: 32768 minimum: 301
Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
CPU: Testing write buffer coherency: ok
CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
Setting up static identity map for 0x100000 - 0x100058
CPU1: failed to boot: -1
Brought up 1 CPUs
SMP: Total of 1 processors activated (666.66 BogoMIPS).
CPU: All CPU(s) started in SVC mode.
devtmpfs: initialized
VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4
clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
pinctrl core: initialized pinctrl subsystem
NET: Registered protocol family 16
DMA: preallocated 256 KiB pool for atomic coherent allocations
cpuidle: using governor menu
hw-breakpoint: found 5 (+1 reserved) breakpoint and 1 watchpoint registers.
hw-breakpoint: maximum watchpoint size is 4 bytes.
zynq-ocm f800c000.ps7-ocmc: ZYNQ OCM pool: 256 KiB @ 0xcf880000
vgaarb: loaded
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
media: Linux media interface: v0.10
Linux video capture interface: v2.00
pps_core: LinuxPPS API ver. 1 registered
pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
PTP clock support registered
EDAC MC: Ver: 3.0.0
Advanced Linux Sound Architecture Driver Initialized.
clocksource: Switched to clocksource arm_global_timer
NET: Registered protocol family 2
TCP established hash table entries: 2048 (order: 1, 8192 bytes)
TCP bind hash table entries: 2048 (order: 2, 16384 bytes)
TCP: Hash tables configured (established 2048 bind 2048)
UDP hash table entries: 256 (order: 1, 8192 bytes)
UDP-Lite hash table entries: 256 (order: 1, 8192 bytes)
NET: Registered protocol family 1
RPC: Registered named UNIX socket transport module.
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
PCI: CLS 0 bytes, default 64
Trying to unpack rootfs image as initramfs...
rootfs image is not initramfs (no cpio magic); looks like an initrd
Freeing initrd memory: 13532K (ccdca000 - cdb01000)
hw perfevents: enabled with armv7_cortex_a9 PMU driver, 7 counters available
futex hash table entries: 512 (order: 3, 32768 bytes)
workingset: timestamp_bits=28 max_order=16 bucket_order=0
jffs2: version 2.2. (NAND) (SUMMARY) © 2001-2006 Red Hat, Inc.
io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered (default)
dma-pl330 f8003000.ps7-dma: Loaded driver for PL330 DMAC-241330
dma-pl330 f8003000.ps7-dma: DBUFF-128x8bytes Num_Chans-8 Num_Peri-4 Num_Events-16
e0000000.serial: ttyPS0 at MMIO 0xe0000000 (irq = 158, base_baud = 6249999) is a xuartps
console [ttyPS0] enabled
xdevcfg f8007000.ps7-dev-cfg: ioremap 0xf8007000 to cf86e000
[drm] Initialized drm 1.1.0 20060810
brd: module loaded
loop: module loaded
CAN device driver interface
gpiod_set_value: invalid GPIO
libphy: MACB_mii_bus: probed
macb e000b000.ethernet eth0: Cadence GEM rev 0x00020118 at 0xe000b000 irq 31 (00:0a:35:00:00:00)
Generic PHY e000b000.etherne:00: attached PHY driver [Generic PHY] (mii_bus:phy_addr=e000b000.etherne:00, irq=-1)
e1000e: Intel(R) PRO/1000 Network Driver - 3.2.6-k
e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
ehci-pci: EHCI PCI platform driver
usbcore: registered new interface driver usb-storage
mousedev: PS/2 mouse device common for all mice
i2c /dev entries driver
Xilinx Zynq CpuIdle Driver started
sdhci: Secure Digital Host Controller Interface driver
sdhci: Copyright(c) Pierre Ossman
sdhci-pltfm: SDHCI platform and OF driver helper
mmc0: SDHCI controller on e0100000.ps7-sdio [e0100000.ps7-sdio] using ADMA
ledtrig-cpu: registered to indicate activity on CPUs
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
nand: device found, Manufacturer ID: 0x2c, Chip ID: 0xda
nand: Micron MT29F2G08ABAGAWP
nand: 256 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 128
nand: WARNING: pl35x-nand: the ECC used on your system is too weak compared to the one required by the NAND chip
Bad block table found at page 131008, version 0x01
Bad block table found at page 130944, version 0x01
6 ofpart partitions found on MTD device pl35x-nand
Creating 6 MTD partitions on "pl35x-nand":
0x000000000000-0x000002800000 : "BOOT.bin-env-dts-kernel"
0x000002800000-0x000004800000 : "ramfs"
0x000004800000-0x000005000000 : "configs"
0x000005000000-0x000006000000 : "reserve"
0x000006000000-0x000008000000 : "ramfs-bak"
0x000008000000-0x000010000000 : "reserve1"
NET: Registered protocol family 10
sit: IPv6 over IPv4 tunneling driver
NET: Registered protocol family 17
can: controller area network core (rev 20120528 abi 9)
NET: Registered protocol family 29
can: raw protocol (rev 20120528)
can: broadcast manager protocol (rev 20120528 t)
can: netlink gateway (rev 20130117) max_hops=1
zynq_pm_ioremap: no compatible node found for 'xlnx,zynq-ddrc-a05'
zynq_pm_late_init: Unable to map DDRC IO memory.
Registering SWP/SWPB emulation handler
hctosys: unable to open rtc device (rtc0)
ALSA device list:
No soundcards found.
RAMDISK: gzip image found at block 0
EXT4-fs (ram0): couldn't mount as ext3 due to feature incompatibilities
EXT4-fs (ram0): mounted filesystem without journal. Opts: (null)
VFS: Mounted root (ext4 filesystem) on device 1:0.
devtmpfs: mounted
Freeing unused kernel memory: 1024K (c0a00000 - c0b00000)
EXT4-fs (ram0): re-mounted. Opts: block_validity,delalloc,barrier,user_xattr
random: dd urandom read with 0 bits of entropy available
ubi0: attaching mtd2
ubi0: scanning is finished
ubi0: attached mtd2 (name "configs", size 8 MiB)
ubi0: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
ubi0: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
ubi0: VID header offset: 2048 (aligned 2048), data offset: 4096
ubi0: good PEBs: 64, bad PEBs: 0, corrupted PEBs: 0
ubi0: user volume: 1, internal volumes: 1, max. volumes count: 128
ubi0: max/mean erase counter: 2/1, WL threshold: 4096, image sequence number: 2723388427
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 12DF1A1C-0ABD-4738-A41B-3E1C6DCD44BA, 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: 4353/1931, WL threshold: 4096, image sequence number: 914180297
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 BCBDE5E0-4C0B-4978-9734-FC58D9F68227, 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
random: nonblocking pool is initialized
Please help. My miner is a S17 Pro. I've found these, but they dont seem to be installable at the moment. I'm now using the FW above but don't have a copy of the original FM. https://service.bitmain.com/support/download?product=Antminer%20S17%20Pro
More logs 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: 202888K/245760K available (6345K kernel code, 231K rwdata, 1896K rodata, 1024K init, 223K bss, 26488K reserved, 16384K cma-reserved, 0K highmem)
Virtual kernel memory layout:
vector : 0xffff0000 - 0xffff1000 ( 4 kB)
fixmap : 0xffc00000 - 0xfff00000 (3072 kB)
vmalloc : 0xcf800000 - 0xff800000 ( 768 MB)
lowmem : 0xc0000000 - 0xcf000000 ( 240 MB)
pkmap : 0xbfe00000 - 0xc0000000 ( 2 MB)
modules : 0xbf000000 - 0xbfe00000 ( 14 MB)
.text : 0xc0008000 - 0xc090c424 (9234 kB)
.init : 0xc0a00000 - 0xc0b00000 (1024 kB)
.data : 0xc0b00000 - 0xc0b39fe0 ( 232 kB)
.bss : 0xc0b39fe0 - 0xc0b71c28 ( 224 kB)
Preemptible hierarchical RCU implementation.
Build-time adjustment of leaf fanout to 32.
RCU restricting CPUs from NR_CPUS=4 to nr_cpu_ids=2.
RCU: Adjusting geometry for rcu_fanout_leaf=32, nr_cpu_ids=2
NR_IRQS:16 nr_irqs:16 16
efuse mapped to cf800000
ps7-slcr mapped to cf802000
L2C: platform modifies aux control register: 0x72360000 -> 0x72760000
L2C: DT/platform modifies aux control register: 0x72360000 -> 0x72760000
L2C-310 erratum 769419 enabled
L2C-310 enabling early BRESP for Cortex-A9
L2C-310 full line of zeros enabled for Cortex-A9
L2C-310 ID prefetch enabled, offset 1 lines
L2C-310 dynamic clock gating enabled, standby mode enabled
L2C-310 cache controller enabled, 8 ways, 512 kB
L2C-310: CACHE_ID 0x410000c8, AUX_CTRL 0x76760001
zynq_clock_init: clkc starts at cf802100
Zynq clock init
sched_clock: 64 bits at 333MHz, resolution 3ns, wraps every 4398046511103ns
clocksource: arm_global_timer: mask: 0xffffffffffffffff max_cycles: 0x4ce07af025, max_idle_ns: 440795209040 ns
Switching to timer-based delay loop, resolution 3ns
clocksource: ttc_clocksource: mask: 0xffff max_cycles: 0xffff, max_idle_ns: 537538477 ns
ps7-ttc #0 at cf80a000, irq=18
Console: colour dummy device 80x30
Calibrating delay loop (skipped), value calculated using timer frequency.. 666.66 BogoMIPS (lpj=3333333)
pid_max: default: 32768 minimum: 301
Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
CPU: Testing write buffer coherency: ok
CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
Setting up static identity map for 0x100000 - 0x100058
CPU1: failed to boot: -1
Brought up 1 CPUs
SMP: Total of 1 processors activated (666.66 BogoMIPS).
CPU: All CPU(s) started in SVC mode.
devtmpfs: initialized
VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4
clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
pinctrl core: initialized pinctrl subsystem
NET: Registered protocol family 16
DMA: preallocated 256 KiB pool for atomic coherent allocations
cpuidle: using governor menu
hw-breakpoint: found 5 (+1 reserved) breakpoint and 1 watchpoint registers.
hw-breakpoint: maximum watchpoint size is 4 bytes.
zynq-ocm f800c000.ps7-ocmc: ZYNQ OCM pool: 256 KiB @ 0xcf880000
vgaarb: loaded
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
media: Linux media interface: v0.10
Linux video capture interface: v2.00
pps_core: LinuxPPS API ver. 1 registered
pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
PTP clock support registered
EDAC MC: Ver: 3.0.0
Advanced Linux Sound Architecture Driver Initialized.
clocksource: Switched to clocksource arm_global_timer
NET: Registered protocol family 2
TCP established hash table entries: 2048 (order: 1, 8192 bytes)
TCP bind hash table entries: 2048 (order: 2, 16384 bytes)
TCP: Hash tables configured (established 2048 bind 2048)
UDP hash table entries: 256 (order: 1, 8192 bytes)
UDP-Lite hash table entries: 256 (order: 1, 8192 bytes)
NET: Registered protocol family 1
RPC: Registered named UNIX socket transport module.
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
PCI: CLS 0 bytes, default 64
Trying to unpack rootfs image as initramfs...
rootfs image is not initramfs (no cpio magic); looks like an initrd
Freeing initrd memory: 13448K (ccddf000 - cdb01000)
hw perfevents: enabled with armv7_cortex_a9 PMU driver, 7 counters available
futex hash table entries: 512 (order: 3, 32768 bytes)
workingset: timestamp_bits=28 max_order=16 bucket_order=0
jffs2: version 2.2. (NAND) (SUMMARY) © 2001-2006 Red Hat, Inc.
io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered (default)
dma-pl330 f8003000.ps7-dma: Loaded driver for PL330 DMAC-241330
dma-pl330 f8003000.ps7-dma: DBUFF-128x8bytes Num_Chans-8 Num_Peri-4 Num_Events-16
e0000000.serial: ttyPS0 at MMIO 0xe0000000 (irq = 158, base_baud = 6249999) is a xuartps
console [ttyPS0] enabled
xdevcfg f8007000.ps7-dev-cfg: ioremap 0xf8007000 to cf86e000
[drm] Initialized drm 1.1.0 20060810
brd: module loaded
loop: module loaded
CAN device driver interface
gpiod_set_value: invalid GPIO
libphy: MACB_mii_bus: probed
macb e000b000.ethernet eth0: Cadence GEM rev 0x00020118 at 0xe000b000 irq 31 (00:0a:35:00:00:00)
Generic PHY e000b000.etherne:00: attached PHY driver [Generic PHY] (mii_bus:phy_addr=e000b000.etherne:00, irq=-1)
e1000e: Intel(R) PRO/1000 Network Driver - 3.2.6-k
e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
ehci-pci: EHCI PCI platform driver
usbcore: registered new interface driver usb-storage
mousedev: PS/2 mouse device common for all mice
i2c /dev entries driver
Xilinx Zynq CpuIdle Driver started
sdhci: Secure Digital Host Controller Interface driver
sdhci: Copyright(c) Pierre Ossman
sdhci-pltfm: SDHCI platform and OF driver helper
mmc0: SDHCI controller on e0100000.ps7-sdio [e0100000.ps7-sdio] using ADMA
ledtrig-cpu: registered to indicate activity on CPUs
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
nand: device found, Manufacturer ID: 0x2c, Chip ID: 0xda
nand: Micron MT29F2G08ABAGAWP
nand: 256 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 128
nand: WARNING: pl35x-nand: the ECC used on your system is too weak compared to the one required by the NAND chip
Bad block table found at page 131008, version 0x01
Bad block table found at page 130944, version 0x01
6 ofpart partitions found on MTD device pl35x-nand
Creating 6 MTD partitions on "pl35x-nand":
0x000000000000-0x000002800000 : "BOOT.bin-env-dts-kernel"
0x000002800000-0x000004800000 : "ramfs"
0x000004800000-0x000005000000 : "configs"
0x000005000000-0x000006000000 : "reserve"
0x000006000000-0x000008000000 : "ramfs-bak"
0x000008000000-0x000010000000 : "reserve1"
NET: Registered protocol family 10
sit: IPv6 over IPv4 tunneling driver
NET: Registered protocol family 17
can: controller area network core (rev 20120528 abi 9)
NET: Registered protocol family 29
can: raw protocol (rev 20120528)
can: broadcast manager protocol (rev 20120528 t)
can: netlink gateway (rev 20130117) max_hops=1
zynq_pm_ioremap: no compatible node found for 'xlnx,zynq-ddrc-a05'
zynq_pm_late_init: Unable to map DDRC IO memory.
Registering SWP/SWPB emulation handler
hctosys: unable to open rtc device (rtc0)
ALSA device list:
No soundcards found.
RAMDISK: gzip image found at block 0
EXT4-fs (ram0): couldn't mount as ext3 due to feature incompatibilities
EXT4-fs (ram0): mounted filesystem without journal. Opts: (null)
VFS: Mounted root (ext4 filesystem) on device 1:0.
devtmpfs: mounted
Freeing unused kernel memory: 1024K (c0a00000 - c0b00000)
EXT4-fs (ram0): re-mounted. Opts: block_validity,delalloc,barrier,user_xattr
random: dd urandom read with 0 bits of entropy available
ubi0: attaching mtd2
ubi0: scanning is finished
ubi0: attached mtd2 (name "configs", size 8 MiB)
ubi0: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
ubi0: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
ubi0: VID header offset: 2048 (aligned 2048), data offset: 4096
ubi0: good PEBs: 64, bad PEBs: 0, corrupted PEBs: 0
ubi0: user volume: 1, internal volumes: 1, max. volumes count: 128
ubi0: max/mean erase counter: 2/1, WL threshold: 4096, image sequence number: 4008956885
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 CB6D5B73-C1E8-448B-B1D9-BEFE5F46466B, 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: 4353/1931, WL threshold: 4096, image sequence number: 914180297
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 BCBDE5E0-4C0B-4978-9734-FC58D9F68227, 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
random: nonblocking pool is initialized
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
[2020/08/28 21:30:48] INFO: Detected 256 Mb of RAM
[2020/08/28 21:30:48] INFO: Switching to manual fan control (30 %)
[2020/08/28 21:30:48] INFO: Checking fans
[2020/08/28 21:30:49] INFO: fan[0] - OK
[2020/08/28 21:30:49] INFO: fan[1] - OK
[2020/08/28 21:30:49] INFO: fan[2] - OK
[2020/08/28 21:30:49] INFO: fan[3] - OK
[2020/08/28 21:30:55] INFO: Power ON
[2020/08/28 21:30:57] INFO: Starting FPGA queue
[2020/08/28 21:30:57] INFO: Initializing hash boards
[2020/08/28 21:30:57] INFO: chain[2] - Initializing
[2020/08/28 21:30:57] INFO: chain[1] - Initializing
[2020/08/28 21:30:57] INFO: chain[0] - Initializing
[2020/08/28 21:31:01] WARN: chain[2] - Failed to measure current voltage (attempt=1) with resp: 0x%02 0xfe
[2020/08/28 21:31:02] WARN: chain[1] - Failed to measure current voltage (attempt=1) with resp: 0x%02 0xfe
[2020/08/28 21:31:02] WARN: chain[2] - Failed to measure current voltage (attempt=2) with resp: 0x%02 0xfe
[2020/08/28 21:31:04] WARN: chain[0] - Failed to measure current voltage (attempt=1) with resp: 0x%02 0xfe
[2020/08/28 21:31:04] WARN: chain[2] - Failed to measure current voltage (attempt=3) with resp: 0x%02 0xfe
[2020/08/28 21:31:05] WARN: chain[1] - Failed to measure current voltage (attempt=2) with resp: 0x%02 0xfe
[2020/08/28 21:31:05] WARN: chain[0] - Failed to measure current voltage (attempt=2) with resp: 0x%02 0xfe
[2020/08/28 21:31:06] WARN: chain[1] - Failed to measure current voltage (attempt=3) with resp: 0x%02 0xfe
[2020/08/28 21:31:07] WARN: chain[2] - Failed to measure current voltage (attempt=1) with resp: 0x%02 0xfe
[2020/08/28 21:31:07] WARN: chain[0] - Failed to measure current voltage (attempt=3) with resp: 0x%02 0xfe
[2020/08/28 21:31:08] WARN: chain[2] - Failed to measure current voltage (attempt=2) with resp: 0x%02 0xfe
[2020/08/28 21:31:08] WARN: chain[1] - Failed to measure current voltage (attempt=1) with resp: 0x%02 0xfe
[2020/08/28 21:31:09] WARN: chain[2] - Failed to measure current voltage (attempt=3) with resp: 0x%02 0xfe
[2020/08/28 21:31:09] WARN: chain[0] - Failed to measure current voltage (attempt=1) with resp: 0x%02 0xfe
[2020/08/28 21:31:10] WARN: chain[1] - Failed to measure current voltage (attempt=2) with resp: 0x%02 0xfe
[2020/08/28 21:31:11] WARN: chain[0] - Failed to measure current voltage (attempt=2) with resp: 0x%02 0xfe
[2020/08/28 21:31:11] WARN: chain[2] - Failed to measure current voltage (attempt=1) with resp: 0x%02 0xfe
[2020/08/28 21:31:12] WARN: chain[1] - Failed to measure current voltage (attempt=3) with resp: 0x%02 0xfe
[2020/08/28 21:31:12] WARN: chain[0] - Failed to measure current voltage (attempt=3) with resp: 0x%02 0xfe
[2020/08/28 21:31:13] WARN: chain[2] - Failed to measure current voltage (attempt=2) with resp: 0x%02 0xfe
[2020/08/28 21:31:14] WARN: chain[1] - Failed to measure current voltage (attempt=1) with resp: 0x%02 0xfe
[2020/08/28 21:31:14] WARN: chain[2] - Failed to measure current voltage (attempt=3) with resp: 0x%02 0xfe
[2020/08/28 21:31:15] WARN: chain[0] - Failed to measure current voltage (attempt=1) with resp: 0x%02 0xfe
[2020/08/28 21:31:15] WARN: chain[1] - Failed to measure current voltage (attempt=2) with resp: 0x%02 0xfe
[2020/08/28 21:31:16] WARN: chain[0] - Failed to measure current voltage (attempt=2) with resp: 0x%02 0xfe
[2020/08/28 21:31:17] WARN: chain[2] - Failed to measure current voltage (attempt=1) with resp: 0x%02 0xfe
[2020/08/28 21:31:17] WARN: chain[1] - Failed to measure current voltage (attempt=3) with resp: 0x%02 0xfe
[2020/08/28 21:31:18] WARN: chain[0] - Failed to measure current voltage (attempt=3) with resp: 0x%02 0xfe
[2020/08/28 21:31:18] WARN: chain[2] - Failed to measure current voltage (attempt=2) with resp: 0x%02 0xfe
[2020/08/28 21:31:19] WARN: chain[1] - Failed to measure current voltage (attempt=1) with resp: 0x%02 0xfe
[2020/08/28 21:31:19] WARN: chain[2] - Failed to measure current voltage (attempt=3) with resp: 0x%02 0xfe
[2020/08/28 21:31:20] WARN: chain[0] - Failed to measure current voltage (attempt=1) with resp: 0x%02 0xfe
[2020/08/28 21:31:21] WARN: chain[1] - Failed to measure current voltage (attempt=2) with resp: 0x%02 0xfe
[2020/08/28 21:31:21] WARN: chain[0] - Failed to measure current voltage (attempt=2) with resp: 0x%02 0xfe
[2020/08/28 21:31:22] WARN: chain[2] - Failed to measure current voltage (attempt=1) with resp: 0x%02 0xfe
[2020/08/28 21:31:22] WARN: chain[1] - Failed to measure current voltage (attempt=3) with resp: 0x%02 0xfe
[2020/08/28 21:31:23] WARN: chain[0] - Failed to measure current voltage (attempt=3) with resp: 0x%02 0xfe
[2020/08/28 21:31:24] WARN: chain[2] - Failed to measure current voltage (attempt=2) with resp: 0x%02 0xfe
[2020/08/28 21:31:24] WARN: chain[1] - Failed to measure current voltage (attempt=1) with resp: 0x%02 0xfe
[2020/08/28 21:31:25] WARN: chain[2] - Failed to measure current voltage (attempt=3) with resp: 0x%02 0xfe
[2020/08/28 21:31:25] WARN: chain[0] - Failed to measure current voltage (attempt=1) with resp: 0x%02 0xfe
[2020/08/28 21:31:26] ERROR: driver-btm-chain.c:687 chain[2] - Voltage is different, cur=0 mV tgt=21000 mV
[2020/08/28 21:31:26] ERROR: driver-btm-chain.c:471 chain[2] - Failed to set start up voltage
[2020/08/28 21:31:26] INFO: chain[2] - Shutting down the chain
[2020/08/28 21:31:26] ERROR: driver-btm-base.c:361 chain[2] - Initialization failed
[2020/08/28 21:31:26] WARN: chain[1] - Failed to measure current voltage (attempt=2) with resp: 0x%02 0xfe
[2020/08/28 21:31:26] WARN: chain[0] - Failed to measure current voltage (attempt=2) with resp: 0x%02 0xfe
[2020/08/28 21:31:27] WARN: chain[1] - Failed to measure current voltage (attempt=3) with resp: 0x%02 0xfe
[2020/08/28 21:31:28] WARN: chain[0] - Failed to measure current voltage (attempt=3) with resp: 0x%02 0xfe
[2020/08/28 21:31:28] ERROR: driver-btm-chain.c:687 chain[1] - Voltage is different, cur=0 mV tgt=21000 mV
[2020/08/28 21:31:28] ERROR: driver-btm-chain.c:471 chain[1] - Failed to set start up voltage
[2020/08/28 21:31:28] INFO: chain[1] - Shutting down the chain
[2020/08/28 21:31:28] ERROR: driver-btm-base.c:361 chain[1] - Initialization failed
[2020/08/28 21:31:29] ERROR: driver-btm-chain.c:687 chain[0] - Voltage is different, cur=0 mV tgt=21000 mV
[2020/08/28 21:31:29] ERROR: driver-btm-chain.c:471 chain[0] - Failed to set start up voltage
[2020/08/28 21:31:29] INFO: chain[0] - Shutting down the chain
[2020/08/28 21:31:29] ERROR: driver-btm-base.c:361 chain[0] - Initialization failed
[2020/08/28 21:31:29] WARN: All chains are disabled or disconnected
[2020/08/28 21:31:29] ERROR: driver-btm-base.c:2156 Failed to initialize hash boards
[2020/08/28 21:31:29] INFO: Shutting down the miner
[2020/08/28 21:31:29] INFO: Stopping FPGA queue
[2020/08/28 21:31:29] INFO: chain[0] - Shutting down the chain
[2020/08/28 21:31:29] INFO: chain[1] - Shutting down the chain
[2020/08/28 21:31:29] INFO: chain[2] - Shutting down the chain
[2020/08/28 21:31:29] INFO: Power OFF
[2020/08/28 21:31:29] ERROR: driver-btm-base.c:2360 Miner initialization failed
[2020/08/28 21:31:52] INFO: Detected 256 Mb of RAM
[2020/08/28 21:31:52] INFO: Switching to manual fan control (30 %)
[2020/08/28 21:31:52] INFO: Checking fans
[2020/08/28 21:31:53] INFO: fan[0] - OK
[2020/08/28 21:31:53] INFO: fan[1] - OK
[2020/08/28 21:31:53] INFO: fan[2] - OK
[2020/08/28 21:31:53] INFO: fan[3] - OK
[2020/08/28 21:31:59] INFO: Shutting down the miner
[2020/08/28 21:31:59] INFO: Power OFF
[2020/08/28 21:34:02] INFO: Detected 256 Mb of RAM
[2020/08/28 21:34:02] INFO: Switching to manual fan control (30 %)
[2020/08/28 21:34:02] INFO: Checking fans
[2020/08/28 21:34:03] INFO: fan[0] - OK
[2020/08/28 21:34:03] INFO: fan[1] - OK
[2020/08/28 21:34:03] INFO: fan[2] - OK
[2020/08/28 21:34:03] INFO: fan[3] - OK
[2020/08/28 21:34:09] INFO: Power ON
[2020/08/28 21:34:11] INFO: Starting FPGA queue
[2020/08/28 21:34:11] INFO: Initializing hash boards
[2020/08/28 21:34:11] INFO: chain[2] - Initializing
[2020/08/28 21:34:11] INFO: chain[1] - Initializing
[2020/08/28 21:34:11] INFO: chain[0] - Initializing
[2020/08/28 21:34:15] WARN: chain[2] - Failed to measure current voltage (attempt=1) with resp: 0x%02 0xfe
[2020/08/28 21:34:16] WARN: chain[1] - Failed to measure current voltage (attempt=1) with resp: 0x%02 0xfe
[2020/08/28 21:34:17] INFO: Shutting down the miner
[2020/08/28 21:34:17] WARN: chain[2] - Failed to measure current voltage (attempt=2) with resp: 0x%02 0xfe
[2020/08/28 21:34:17] INFO: Stopping FPGA queue
[2020/08/28 21:34:17] INFO: chain[0] - Shutting down the chain
[2020/08/28 21:34:17] INFO: chain[1] - Shutting down the chain
[2020/08/28 21:34:17] INFO: chain[2] - Shutting down the chain
[2020/08/28 21:34:17] INFO: Power OFF
[2020/08/28 21:34:28] INFO: Detected 256 Mb of RAM
[2020/08/28 21:34:28] INFO: Switching to manual fan control (30 %)
[2020/08/28 21:34:28] INFO: Checking fans
[2020/08/28 21:34:29] INFO: fan[0] - OK
[2020/08/28 21:34:29] INFO: fan[1] - OK
[2020/08/28 21:34:29] INFO: fan[2] - OK
[2020/08/28 21:34:29] INFO: fan[3] - OK
[2020/08/28 21:34:35] INFO: Power ON
[2020/08/28 21:34:37] INFO: Starting FPGA queue
[2020/08/28 21:34:37] INFO: Initializing hash boards
[2020/08/28 21:34:37] INFO: chain[2] - Initializing
[2020/08/28 21:34:37] INFO: chain[1] - Initializing
[2020/08/28 21:34:37] INFO: chain[0] - Initializing
[2020/08/28 21:34:41] WARN: chain[2] - Failed to measure current voltage (attempt=1) with resp: 0x%02 0xfe
[2020/08/28 21:34:42] WARN: chain[1] - Failed to measure current voltage (attempt=1) with resp: 0x%02 0xfe
[2020/08/28 21:34:43] WARN: chain[2] - Failed to measure current voltage (attempt=2) with resp: 0x%02 0xfe
[2020/08/28 21:34:44] WARN: chain[0] - Failed to measure current voltage (attempt=1) with resp: 0x%02 0xfe
[2020/08/28 21:34:45] WARN: chain[2] - Failed to measure current voltage (attempt=3) with resp: 0x%02 0xfe
[2020/08/28 21:34:45] WARN: chain[1] - Failed to measure current voltage (attempt=2) with resp: 0x%02 0xfe
[2020/08/28 21:34:46] WARN: chain[0] - Failed to measure current voltage (attempt=2) with resp: 0x%02 0xfe
[2020/08/28 21:34:46] WARN: chain[1] - Failed to measure current voltage (attempt=3) with resp: 0x%02 0xfe
[2020/08/28 21:34:47] WARN: chain[2] - Failed to measure current voltage (attempt=1) with resp: 0x%02 0xfe
[2020/08/28 21:34:48] WARN: chain[0] - Failed to measure current voltage (attempt=3) with resp: 0x%02 0xfe
[2020/08/28 21:34:48] WARN: chain[2] - Failed to measure current voltage (attempt=2) with resp: 0x%02 0xfe
[2020/08/28 21:34:49] WARN: chain[1] - Failed to measure current voltage (attempt=1) with resp: 0x%02 0xfe
[2020/08/28 21:34:49] WARN: chain[2] - Failed to measure current voltage (attempt=3) with resp: 0x%02 0xfe
[2020/08/28 21:34:50] WARN: chain[0] - Failed to measure current voltage (attempt=1) with resp: 0x%02 0xfe
[2020/08/28 21:34:51] WARN: chain[1] - Failed to measure current voltage (attempt=2) with resp: 0x%02 0xfe
[2020/08/28 21:34:51] WARN: chain[0] - Failed to measure current voltage (attempt=2) with resp: 0x%02 0xfe
[2020/08/28 21:34:52] WARN: chain[2] - Failed to measure current voltage (attempt=1) with resp: 0x%02 0xfe
[2020/08/28 21:34:52] WARN: chain[1] - Failed to measure current voltage (attempt=3) with resp: 0x%02 0xfe
[2020/08/28 21:34:53] WARN: chain[0] - Failed to measure current voltage (attempt=3) with resp: 0x%02 0xfe
[2020/08/28 21:34:54] WARN: chain[2] - Failed to measure current voltage (attempt=2) with resp: 0x%02 0xfe
[2020/08/28 21:34:54] WARN: chain[1] - Failed to measure current voltage (attempt=1) with resp: 0x%02 0xfe
[2020/08/28 21:34:55] WARN: chain[2] - Failed to measure current voltage (attempt=3) with resp: 0x%02 0xfe
[2020/08/28 21:34:55] WARN: chain[0] - Failed to measure current voltage (attempt=1) with resp: 0x%02 0xfe
[2020/08/28 21:34:56] WARN: chain[1] - Failed to measure current voltage (attempt=2) with resp: 0x%02 0xfe
[2020/08/28 21:34:56] WARN: chain[0] - Failed to measure current voltage (attempt=2) with resp: 0x%02 0xfe
[2020/08/28 21:34:57] WARN: chain[2] - Failed to measure current voltage (attempt=1) with resp: 0x%02 0xfe
[2020/08/28 21:34:58] WARN: chain[1] - Failed to measure current voltage (attempt=3) with resp: 0x%02 0xfe
[2020/08/28 21:34:58] WARN: chain[0] - Failed to measure current voltage (attempt=3) with resp: 0x%02 0xfe
[2020/08/28 21:34:59] WARN: chain[2] - Failed to measure current voltage (attempt=2) with resp: 0x%02 0xfe
[2020/08/28 21:34:59] WARN: chain[1] - Failed to measure current voltage (attempt=1) with resp: 0x%02 0xfe
[2020/08/28 21:35:00] WARN: chain[2] - Failed to measure current voltage (attempt=3) with resp: 0x%02 0xfe
[2020/08/28 21:35:01] WARN: chain[0] - Failed to measure current voltage (attempt=1) with resp: 0x%02 0xfe
[2020/08/28 21:35:01] WARN: chain[1] - Failed to measure current voltage (attempt=2) with resp: 0x%02 0xfe
[2020/08/28 21:35:02] WARN: chain[0] - Failed to measure current voltage (attempt=2) with resp: 0x%02 0xfe
[2020/08/28 21:35:02] WARN: chain[2] - Failed to measure current voltage (attempt=1) with resp: 0x%02 0xfe
[2020/08/28 21:35:03] WARN: chain[1] - Failed to measure current voltage (attempt=3) with resp: 0x%02 0xfe
[2020/08/28 21:35:03] WARN: chain[0] - Failed to measure current voltage (attempt=3) with resp: 0x%02 0xfe
[2020/08/28 21:35:04] WARN: chain[2] - Failed to measure current voltage (attempt=2) with resp: 0x%02 0xfe
[2020/08/28 21:35:05] WARN: chain[1] - Failed to measure current voltage (attempt=1) with resp: 0x%02 0xfe
[2020/08/28 21:35:05] WARN: chain[2] - Failed to measure current voltage (attempt=3) with resp: 0x%02 0xfe
[2020/08/28 21:35:06] WARN: chain[0] - Failed to measure current voltage (attempt=1) with resp: 0x%02 0xfe
[2020/08/28 21:35:06] ERROR: driver-btm-chain.c:687 chain[2] - Voltage is different, cur=0 mV tgt=21000 mV
[2020/08/28 21:35:06] ERROR: driver-btm-chain.c:471 chain[2] - Failed to set start up voltage
[2020/08/28 21:35:06] INFO: chain[2] - Shutting down the chain
[2020/08/28 21:35:06] ERROR: driver-btm-base.c:361 chain[2] - Initialization failed
[2020/08/28 21:35:06] WARN: chain[1] - Failed to measure current voltage (attempt=2) with resp: 0x%02 0xfe
[2020/08/28 21:35:07] WARN: chain[0] - Failed to measure current voltage (attempt=2) with resp: 0x%02 0xfe
[2020/08/28 21:35:08] WARN: chain[1] - Failed to measure current voltage (attempt=3) with resp: 0x%02 0xfe
[2020/08/28 21:35:08] WARN: chain[0] - Failed to measure current voltage (attempt=3) with resp: 0x%02 0xfe
[2020/08/28 21:35:09] ERROR: driver-btm-chain.c:687 chain[1] - Voltage is different, cur=0 mV tgt=21000 mV
[2020/08/28 21:35:09] ERROR: driver-btm-chain.c:471 chain[1] - Failed to set start up voltage
[2020/08/28 21:35:09] INFO: chain[1] - Shutting down the chain
[2020/08/28 21:35:09] ERROR: driver-btm-base.c:361 chain[1] - Initialization failed
Here are some screens that I aee with the new FW. They didnt exist in the original FW. Also, I dont see a way to change between the different modes (low, normal, turbo). So, I'm concerned that this isn't the correct FW for my miner. https://imgur.com/a/noqSYn7
Title: Re: S17 Pro no longer hashing. Bad ASICs ?
Post by: mikeywith on August 28, 2020, 11:09:09 PM
I got your pm but all you have to do is mention my username here and LoyceV's bot will notify me.
This isn't the stock firmware, it is Vnish firmware, it looks different and acts different, go the configuration page and check "profile", it will be disabled by default, set it to a low profile, there is no turbo, normal and low, you need to chose a terahash based profile, pick something below 40th and let it tune for an hour or so.
I can't access my PC now, but tomorrow i might be able to access your miner via teamviewer to help you troubleshoot it.
Let us know how tuning for a low profile goes, and be patient it might take 2-3 hours, watch the logs on the same page.
Title: Re: S17 Pro no longer hashing. Bad ASICs ?
Post by: agilmore on August 29, 2020, 10:14:58 PM
I let it run for 3 hours, still no luck. Here are some screenshots and logs. https://imgur.com/a/zVNJLgO (https://imgur.com/a/zVNJLgO) [2020/08/29 19:18:56] INFO: =[ Tuner ]==============================
[2020/08/29 19:18:56] INFO: Starting auto-tuning
[2020/08/29 19:18:56] INFO: Preset: Profile 38Th @ 400MHz
[2020/08/29 19:18:56] INFO: Detecting mininum voltage
[2020/08/29 19:19:51] ERROR: driver-btm-tuner.c:905 Failed to initialize the miner
[2020/08/29 19:20:04] INFO: =[ Tuner ]==============================
[2020/08/29 19:20:04] INFO: Starting auto-tuning
[2020/08/29 19:20:04] INFO: Preset: Profile 38Th @ 400MHz
[2020/08/29 19:20:04] INFO: Detecting mininum voltage
[2020/08/29 19:20:59] ERROR: driver-btm-tuner.c:905 Failed to initialize the miner
[2020/08/29 19:21:15] INFO: =[ Tuner ]==============================
[2020/08/29 19:21:15] INFO: Starting auto-tuning
[2020/08/29 19:21:15] INFO: Preset: Profile 38Th @ 400MHz
[2020/08/29 19:21:15] INFO: Detecting mininum voltage
[2020/08/29 19:22:09] ERROR: driver-btm-tuner.c:905 Failed to initialize the miner
[2020/08/29 19:22:25] INFO: =[ Tuner ]==============================
[2020/08/29 19:22:25] INFO: Starting auto-tuning
[2020/08/29 19:22:25] INFO: Preset: Profile 38Th @ 400MHz
[2020/08/29 19:22:25] INFO: Detecting mininum voltage
[2020/08/29 19:23:20] ERROR: driver-btm-tuner.c:905 Failed to initialize the miner
[2020/08/29 19:23:35] INFO: =[ Tuner ]==============================
[2020/08/29 19:23:35] INFO: Starting auto-tuning
[2020/08/29 19:23:35] INFO: Preset: Profile 38Th @ 400MHz
[2020/08/29 19:23:35] INFO: Detecting mininum voltage
[2020/08/29 19:24:30] ERROR: driver-btm-tuner.c:905 Failed to initialize the miner
[2020/08/29 19:24:45] INFO: =[ Tuner ]==============================
[2020/08/29 19:24:45] INFO: Starting auto-tuning
[2020/08/29 19:24:45] INFO: Preset: Profile 38Th @ 400MHz
[2020/08/29 19:24:45] INFO: Detecting mininum voltage
[2020/08/29 19:25:40] ERROR: driver-btm-tuner.c:905 Failed to initialize the miner
[2020/08/29 19:25:56] INFO: =[ Tuner ]==============================
[2020/08/29 19:25:56] INFO: Starting auto-tuning
[2020/08/29 19:25:56] INFO: Preset: Profile 38Th @ 400MHz
[2020/08/29 19:25:56] INFO: Detecting mininum voltage
[2020/08/29 19:26:04] INFO: =[ Tuner ]==============================
[2020/08/29 19:26:04] INFO: Starting auto-tuning
[2020/08/29 19:26:04] INFO: Preset: Profile 38Th @ 400MHz
[2020/08/29 19:26:04] INFO: Detecting mininum voltage
[2020/08/29 19:26:59] ERROR: driver-btm-tuner.c:905 Failed to initialize the miner
[2020/08/29 19:27:26] INFO: =[ Tuner ]==============================
[2020/08/29 19:27:26] INFO: Starting auto-tuning
[2020/08/29 19:27:26] INFO: Preset: Profile 38Th @ 400MHz
[2020/08/29 19:27:26] INFO: Detecting mininum voltage
[2020/08/29 19:28:21] ERROR: driver-btm-tuner.c:905 Failed to initialize the miner
[2020/08/29 19:28:36] INFO: =[ Tuner ]==============================
[2020/08/29 19:28:36] INFO: Starting auto-tuning
[2020/08/29 19:28:36] INFO: Preset: Profile 38Th @ 400MHz
[2020/08/29 19:28:36] INFO: Detecting mininum voltage
[2020/08/29 19:29:31] ERROR: driver-btm-tuner.c:905 Failed to initialize the miner
[2020/08/29 19:29:46] INFO: =[ Tuner ]==============================
[2020/08/29 19:29:46] INFO: Starting auto-tuning
[2020/08/29 19:29:46] INFO: Preset: Profile 38Th @ 400MHz
[2020/08/29 19:29:46] INFO: Detecting mininum voltage
[2020/08/29 19:30:41] ERROR: driver-btm-tuner.c:905 Failed to initialize the miner
[2020/08/29 19:30:56] INFO: =[ Tuner ]==============================
[2020/08/29 19:30:56] INFO: Starting auto-tuning
[2020/08/29 19:30:57] INFO: Preset: Profile 38Th @ 400MHz
[2020/08/29 19:30:57] INFO: Detecting mininum voltage
[2020/08/29 19:31:51] ERROR: driver-btm-tuner.c:905 Failed to initialize the miner
[2020/08/29 19:32:07] INFO: =[ Tuner ]==============================
[2020/08/29 19:32:07] INFO: Starting auto-tuning
[2020/08/29 19:32:07] INFO: Preset: Profile 38Th @ 400MHz
[2020/08/29 19:32:07] INFO: Detecting mininum voltage
[2020/08/29 19:33:01] ERROR: driver-btm-tuner.c:905 Failed to initialize the miner
[2020/08/29 19:33:17] INFO: =[ Tuner ]==============================
[2020/08/29 19:33:17] INFO: Starting auto-tuning
[2020/08/29 19:33:17] INFO: Preset: Profile 38Th @ 400MHz
[2020/08/29 19:33:17] INFO: Detecting mininum voltage
[2020/08/29 19:34:12] ERROR: driver-btm-tuner.c:905 Failed to initialize the miner
[2020/08/29 19:34:27] INFO: =[ Tuner ]==============================
[2020/08/29 19:34:27] INFO: Starting auto-tuning
[2020/08/29 19:34:27] INFO: Preset: Profile 38Th @ 400MHz
[2020/08/29 19:34:27] INFO: Detecting mininum voltage
[2020/08/29 19:35:22] ERROR: driver-btm-tuner.c:905 Failed to initialize the miner
[2020/08/29 19:35:37] INFO: =[ Tuner ]==============================
[2020/08/29 19:35:37] INFO: Starting auto-tuning
[2020/08/29 19:35:37] INFO: Preset: Profile 38Th @ 400MHz
[2020/08/29 19:35:37] INFO: Detecting mininum voltage
[2020/08/29 19:36:32] ERROR: driver-btm-tuner.c:905 Failed to initialize the miner
[2020/08/29 19:36:48] INFO: =[ Tuner ]==============================
[2020/08/29 19:36:48] INFO: Starting auto-tuning
[2020/08/29 19:36:48] INFO: Preset: Profile 38Th @ 400MHz
[2020/08/29 19:36:48] INFO: Detecting mininum voltage
[2020/08/29 19:37:42] ERROR: driver-btm-tuner.c:905 Failed to initialize the miner
[2020/08/29 19:37:58] INFO: =[ Tuner ]==============================
[2020/08/29 19:37:58] INFO: Starting auto-tuning
[2020/08/29 19:37:58] INFO: Preset: Profile 38Th @ 400MHz
[2020/08/29 19:37:58] INFO: Detecting mininum voltage
[2020/08/29 19:38:53] ERROR: driver-btm-tuner.c:905 Failed to initialize the miner
[2020/08/29 19:39:08] INFO: =[ Tuner ]==============================
[2020/08/29 19:39:08] INFO: Starting auto-tuning
[2020/08/29 19:39:08] INFO: Preset: Profile 38Th @ 400MHz
[2020/08/29 19:39:08] INFO: Detecting mininum voltage
[2020/08/29 19:40:03] ERROR: driver-btm-tuner.c:905 Failed to initialize the miner
[2020/08/29 19:40:18] INFO: =[ Tuner ]==============================
[2020/08/29 19:40:18] INFO: Starting auto-tuning
[2020/08/29 19:40:18] INFO: Preset: Profile 38Th @ 400MHz
[2020/08/29 19:40:18] INFO: Detecting mininum voltage
[2020/08/29 19:41:13] ERROR: driver-btm-tuner.c:905 Failed to initialize the miner
[2020/08/29 19:41:28] INFO: =[ Tuner ]==============================
[2020/08/29 19:41:28] INFO: Starting auto-tuning
[2020/08/29 19:41:28] INFO: Preset: Profile 38Th @ 400MHz
[2020/08/29 19:41:28] INFO: Detecting mininum voltage
[2020/08/29 19:42:23] ERROR: driver-btm-tuner.c:905 Failed to initialize the miner
[2020/08/29 19:42:39] INFO: =[ Tuner ]==============================
[2020/08/29 19:42:39] INFO: Starting auto-tuning
[2020/08/29 19:42:39] INFO: Preset: Profile 38Th @ 400MHz
[2020/08/29 19:42:39] INFO: Detecting mininum voltage
[2020/08/29 19:43:33] ERROR: driver-btm-tuner.c:905 Failed to initialize the miner
[2020/08/29 19:43:49] INFO: =[ Tuner ]==============================
[2020/08/29 19:43:49] INFO: Starting auto-tuning
[2020/08/29 19:43:49] INFO: Preset: Profile 38Th @ 400MHz
[2020/08/29 19:43:49] INFO: Detecting mininum voltage
[2020/08/29 19:44:44] ERROR: driver-btm-tuner.c:905 Failed to initialize the miner
[2020/08/29 19:44:59] INFO: =[ Tuner ]==============================
[2020/08/29 19:44:59] INFO: Starting auto-tuning
[2020/08/29 19:44:59] INFO: Preset: Profile 38Th @ 400MHz
[2020/08/29 19:44:59] INFO: Detecting mininum voltage
[2020/08/29 19:45:54] ERROR: driver-btm-tuner.c:905 Failed to initialize the miner
[2020/08/29 19:46:09] INFO: =[ Tuner ]==============================
[2020/08/29 19:46:09] INFO: Starting auto-tuning
[2020/08/29 19:46:09] INFO: Preset: Profile 38Th @ 400MHz
[2020/08/29 19:46:09] INFO: Detecting mininum voltage
[2020/08/29 19:47:04] ERROR: driver-btm-tuner.c:905 Failed to initialize the miner
[2020/08/29 19:47:20] INFO: =[ Tuner ]==============================
[2020/08/29 19:47:20] INFO: Starting auto-tuning
[2020/08/29 19:47:20] INFO: Preset: Profile 38Th @ 400MHz
[2020/08/29 19:47:20] INFO: Detecting mininum voltage
[2020/08/29 19:48:17] ERROR: driver-btm-tuner.c:905 Failed to initialize the miner
[2020/08/29 19:48:30] INFO: =[ Tuner ]==============================
[2020/08/29 19:48:30] INFO: Starting auto-tuning
[2020/08/29 19:48:30] INFO: Preset: Profile 38Th @ 400MHz
[2020/08/29 19:48:30] INFO: Detecting mininum voltage
[2020/08/29 19:49:24] ERROR: driver-btm-tuner.c:905 Failed to initialize the miner
[2020/08/29 19:49:40] INFO: =[ Tuner ]==============================
[2020/08/29 19:49:40] INFO: Starting auto-tuning
[2020/08/29 19:49:40] INFO: Preset: Profile 38Th @ 400MHz
[2020/08/29 19:49:40] INFO: Detecting mininum voltage
[2020/08/29 19:50:35] ERROR: driver-btm-tuner.c:905 Failed to initialize the miner
[2020/08/29 19:50:50] INFO: =[ Tuner ]==============================
[2020/08/29 19:50:50] INFO: Starting auto-tuning
[2020/08/29 19:50:50] INFO: Preset: Profile 38Th @ 400MHz
[2020/08/29 19:50:50] INFO: Detecting mininum voltage
[2020/08/29 19:51:45] ERROR: driver-btm-tuner.c:905 Failed to initialize the miner
[2020/08/29 19:52:00] INFO: =[ Tuner ]==============================
[2020/08/29 19:52:00] INFO: Starting auto-tuning
[2020/08/29 19:52:00] INFO: Preset: Profile 38Th @ 400MHz
[2020/08/29 19:52:00] INFO: Detecting mininum voltage
[2020/08/29 19:52:55] ERROR: driver-btm-tuner.c:905 Failed to initialize the miner
[2020/08/29 19:53:11] INFO: =[ Tuner ]==============================
[2020/08/29 19:53:11] INFO: Starting auto-tuning
[2020/08/29 19:53:11] INFO: Preset: Profile 38Th @ 400MHz
[2020/08/29 19:53:11] INFO: Detecting mininum voltage
[2020/08/29 19:54:05] ERROR: driver-btm-tuner.c:905 Failed to initialize the miner
[2020/08/29 19:54:21] INFO: =[ Tuner ]==============================
[2020/08/29 19:54:21] INFO: Starting auto-tuning
[2020/08/29 19:54:21] INFO: Preset: Profile 38Th @ 400MHz
[2020/08/29 19:54:21] INFO: Detecting mininum voltage
[2020/08/29 19:55:16] ERROR: driver-btm-tuner.c:905 Failed to initialize the miner
[2020/08/29 19:55:31] INFO: =[ Tuner ]==============================
[2020/08/29 19:55:31] INFO: Starting auto-tuning
[2020/08/29 19:55:31] INFO: Preset: Profile 38Th @ 400MHz
[2020/08/29 19:55:31] INFO: Detecting mininum voltage
[2020/08/29 19:56:26] ERROR: driver-btm-tuner.c:905 Failed to initialize the miner
[2020/08/29 19:56:41] INFO: =[ Tuner ]==============================
[2020/08/29 19:56:41] INFO: Starting auto-tuning
[2020/08/29 19:56:41] INFO: Preset: Profile 38Th @ 400MHz
[2020/08/29 19:56:41] INFO: Detecting mininum voltage
[2020/08/29 19:57:36] ERROR: driver-btm-tuner.c:905 Failed to initialize the miner
[2020/08/29 19:57:51] INFO: =[ Tuner ]==============================
[2020/08/29 19:57:51] INFO: Starting auto-tuning
[2020/08/29 19:57:51] INFO: Preset: Profile 38Th @ 400MHz
[2020/08/29 19:57:51] INFO: Detecting mininum voltage
[2020/08/29 19:58:49] ERROR: driver-btm-tuner.c:905 Failed to initialize the miner
[2020/08/29 19:59:02] INFO: =[ Tuner ]==============================
[2020/08/29 19:59:02] INFO: Starting auto-tuning
[2020/08/29 19:59:02] INFO: Preset: Profile 38Th @ 400MHz
[2020/08/29 19:59:02] INFO: Detecting mininum voltage
[2020/08/29 19:59:56] ERROR: driver-btm-tuner.c:905 Failed to initialize the miner
[2020/08/29 20:00:12] INFO: =[ Tuner ]==============================
[2020/08/29 20:00:12] INFO: Starting auto-tuning
[2020/08/29 20:00:12] INFO: Preset: Profile 38Th @ 400MHz
[2020/08/29 20:00:12] INFO: Detecting mininum voltage
[2020/08/29 20:01:07] ERROR: driver-btm-tuner.c:905 Failed to initialize the miner
[2020/08/29 20:01:22] INFO: =[ Tuner ]==============================
[2020/08/29 20:01:22] INFO: Starting auto-tuning
[2020/08/29 20:01:22] INFO: Preset: Profile 38Th @ 400MHz
[2020/08/29 20:01:22] INFO: Detecting mininum voltage
[2020/08/29 20:02:23] ERROR: driver-btm-tuner.c:905 Failed to initialize the miner
[2020/08/29 20:02:52] INFO: =[ Tuner ]==============================
[2020/08/29 20:02:52] INFO: Starting auto-tuning
[2020/08/29 20:02:52] INFO: Preset: Profile 38Th @ 400MHz
[2020/08/29 20:02:52] INFO: Detecting mininum voltage
[2020/08/29 20:03:47] ERROR: driver-btm-tuner.c:905 Failed to initialize the miner
[2020/08/29 20:04:03] INFO: =[ Tuner ]==============================
[2020/08/29 20:04:03] INFO: Starting auto-tuning
[2020/08/29 20:04:03] INFO: Preset: Profile 38Th @ 400MHz
[2020/08/29 20:04:03] INFO: Detecting mininum voltage
[2020/08/29 20:04:57] ERROR: driver-btm-tuner.c:905 Failed to initialize the miner
[2020/08/29 20:05:13] INFO: =[ Tuner ]==============================
[2020/08/29 20:05:13] INFO: Starting auto-tuning
[2020/08/29 20:05:13] INFO: Preset: Profile 38Th @ 400MHz
[2020/08/29 20:05:13] INFO: Detecting mininum voltage
[2020/08/29 20:06:08] ERROR: driver-btm-tuner.c:905 Failed to initialize the miner
[2020/08/29 20:06:23] INFO: =[ Tuner ]==============================
[2020/08/29 20:06:23] INFO: Starting auto-tuning
[2020/08/29 20:06:23] INFO: Preset: Profile 38Th @ 400MHz
[2020/08/29 20:06:23] INFO: Detecting mininum voltage
[2020/08/29 20:07:18] ERROR: driver-btm-tuner.c:905 Failed to initialize the miner
[2020/08/29 20:07:33] INFO: =[ Tuner ]==============================
[2020/08/29 20:07:33] INFO: Starting auto-tuning
[2020/08/29 20:07:33] INFO: Preset: Profile 38Th @ 400MHz
[2020/08/29 20:07:33] INFO: Detecting mininum voltage
[2020/08/29 20:08:28] ERROR: driver-btm-tuner.c:905 Failed to initialize the miner
[2020/08/29 20:08:43] INFO: =[ Tuner ]==============================
[2020/08/29 20:08:43] INFO: Starting auto-tuning
[2020/08/29 20:08:43] INFO: Preset: Profile 38Th @ 400MHz
[2020/08/29 20:08:43] INFO: Detecting mininum voltage
[2020/08/29 20:09:38] ERROR: driver-btm-tuner.c:905 Failed to initialize the miner
[2020/08/29 20:09:54] INFO: =[ Tuner ]==============================
[2020/08/29 20:09:54] INFO: Starting auto-tuning
[2020/08/29 20:09:54] INFO: Preset: Profile 38Th @ 400MHz
[2020/08/29 20:09:54] INFO: Detecting mininum voltage
[2020/08/29 20:10:48] ERROR: driver-btm-tuner.c:905 Failed to initialize the miner
[2020/08/29 20:11:04] INFO: =[ Tuner ]==============================
[2020/08/29 20:11:04] INFO: Starting auto-tuning
[2020/08/29 20:11:04] INFO: Preset: Profile 38Th @ 400MHz
[2020/08/29 20:11:04] INFO: Detecting mininum voltage
[2020/08/29 20:11:59] ERROR: driver-btm-tuner.c:905 Failed to initialize the miner
[2020/08/29 20:12:14] INFO: =[ Tuner ]==============================
[2020/08/29 20:12:14] INFO: Starting auto-tuning
[2020/08/29 20:12:14] INFO: Preset: Profile 38Th @ 400MHz
[2020/08/29 20:12:14] INFO: Detecting mininum voltage
[2020/08/29 20:13:09] ERROR: driver-btm-tuner.c:905 Failed to initialize the miner
[2020/08/29 20:13:24] INFO: =[ Tuner ]==============================
[2020/08/29 20:13:24] INFO: Starting auto-tuning
[2020/08/29 20:13:24] INFO: Preset: Profile 38Th @ 400MHz
[2020/08/29 20:13:24] INFO: Detecting mininum voltage
[2020/08/29 20:14:19] ERROR: driver-btm-tuner.c:905 Failed to initialize the miner
[2020/08/29 20:14:34] INFO: =[ Tuner ]==============================
[2020/08/29 20:14:34] INFO: Starting auto-tuning
[2020/08/29 20:14:34] INFO: Preset: Profile 38Th @ 400MHz
[2020/08/29 20:14:34] INFO: Detecting mininum voltage
[2020/08/29 20:15:30] ERROR: driver-btm-tuner.c:905 Failed to initialize the miner
[2020/08/29 20:15:45] INFO: =[ Tuner ]==============================
[2020/08/29 20:15:45] INFO: Starting auto-tuning
[2020/08/29 20:15:45] INFO: Preset: Profile 38Th @ 400MHz
[2020/08/29 20:15:45] INFO: Detecting mininum voltage
[2020/08/29 20:16:39] ERROR: driver-btm-tuner.c:905 Failed to initialize the miner
[2020/08/29 20:16:55] INFO: =[ Tuner ]==============================
[2020/08/29 20:16:55] INFO: Starting auto-tuning
[2020/08/29 20:16:55] INFO: Preset: Profile 38Th @ 400MHz
[2020/08/29 20:16:55] INFO: Detecting mininum voltage
[2020/08/29 20:17:50] ERROR: driver-btm-tuner.c:905 Failed to initialize the miner
[2020/08/29 20:18:05] INFO: =[ Tuner ]==============================
[2020/08/29 20:18:05] INFO: Starting auto-tuning
[2020/08/29 20:18:05] INFO: Preset: Profile 38Th @ 400MHz
[2020/08/29 20:18:05] INFO: Detecting mininum voltage
[2020/08/29 20:19:00] ERROR: driver-btm-tuner.c:905 Failed to initialize the miner
[2020/08/29 20:19:15] INFO: =[ Tuner ]==============================
[2020/08/29 20:19:15] INFO: Starting auto-tuning
[2020/08/29 20:19:15] INFO: Preset: Profile 38Th @ 400MHz
[2020/08/29 20:19:15] INFO: Detecting mininum voltage
[2020/08/29 20:20:10] ERROR: driver-btm-tuner.c:905 Failed to initialize the miner
[2020/08/29 20:20:25] INFO: =[ Tuner ]==============================
[2020/08/29 20:20:25] INFO: Starting auto-tuning
[2020/08/29 20:20:25] INFO: Preset: Profile 38Th @ 400MHz
[2020/08/29 20:20:25] INFO: Detecting mininum voltage
[2020/08/29 20:21:20] ERROR: driver-btm-tuner.c:905 Failed to initialize the miner
[2020/08/29 20:21:36] INFO: =[ Tuner ]==============================
[2020/08/29 20:21:36] INFO: Starting auto-tuning
[2020/08/29 20:21:36] INFO: Preset: Profile 38Th @ 400MHz
[2020/08/29 20:21:36] INFO: Detecting mininum voltage
[2020/08/29 20:22:30] ERROR: driver-btm-tuner.c:905 Failed to initialize the miner
[2020/08/29 20:22:46] INFO: =[ Tuner ]==============================
[2020/08/29 20:22:46] INFO: Starting auto-tuning
[2020/08/29 20:22:46] INFO: Preset: Profile 38Th @ 400MHz
[2020/08/29 20:22:46] INFO: Detecting mininum voltage
[2020/08/29 20:23:41] ERROR: driver-btm-tuner.c:905 Failed to initialize the miner
[2020/08/29 20:23:56] INFO: =[ Tuner ]==============================
[2020/08/29 20:23:56] INFO: Starting auto-tuning
[2020/08/29 20:23:56] INFO: Preset: Profile 38Th @ 400MHz
[2020/08/29 20:23:56] INFO: Detecting mininum voltage
[2020/08/29 20:24:51] ERROR: driver-btm-tuner.c:905 Failed to initialize the miner
[2020/08/29 20:25:06] INFO: =[ Tuner ]==============================
[2020/08/29 20:25:06] INFO: Starting auto-tuning
[2020/08/29 20:25:06] INFO: Preset: Profile 38Th @ 400MHz
[2020/08/29 20:25:06] INFO: Detecting mininum voltage
[2020/08/29 20:26:01] ERROR: driver-btm-tuner.c:905 Failed to initialize the miner
[2020/08/29 20:26:17] INFO: =[ Tuner ]==============================
[2020/08/29 20:26:17] INFO: Starting auto-tuning
[2020/08/29 20:26:17] INFO: Preset: Profile 38Th @ 400MHz
[2020/08/29 20:26:17] INFO: Detecting mininum voltage
[2020/08/29 20:27:11] ERROR: driver-btm-tuner.c:905 Failed to initialize the miner
[2020/08/29 20:27:27] INFO: =[ Tuner ]==============================
[2020/08/29 20:27:27] INFO: Starting auto-tuning
[2020/08/29 20:27:27] INFO: Preset: Profile 38Th @ 400MHz
[2020/08/29 20:27:27] INFO: Detecting mininum voltage
[2020/08/29 20:28:22] ERROR: driver-btm-tuner.c:905 Failed to initialize the miner
[2020/08/29 20:28:37] INFO: =[ Tuner ]==============================
[2020/08/29 20:28:37] INFO: Starting auto-tuning
[2020/08/29 20:28:37] INFO: Preset: Profile 38Th @ 400MHz
[2020/08/29 20:28:37] INFO: Detecting mininum voltage
[2020/08/29 20:29:35] ERROR: driver-btm-tuner.c:905 Failed to initialize the miner
[2020/08/29 20:29:47] INFO: =[ Tuner ]==============================
[2020/08/29 20:29:47] INFO: Starting auto-tuning
[2020/08/29 20:29:47] INFO: Preset: Profile 38Th @ 400MHz
[2020/08/29 20:29:47] INFO: Detecting mininum voltage
[2020/08/29 20:30:42] ERROR: driver-btm-tuner.c:905 Failed to initialize the miner
[2020/08/29 20:30:57] INFO: =[ Tuner ]==============================
[2020/08/29 20:30:57] INFO: Starting auto-tuning
[2020/08/29 20:30:57] INFO: Preset: Profile 38Th @ 400MHz
[2020/08/29 20:30:57] INFO: Detecting mininum voltage
[2020/08/29 20:31:52] ERROR: driver-btm-tuner.c:905 Failed to initialize the miner
[2020/08/29 20:32:08] INFO: =[ Tuner ]==============================
[2020/08/29 20:32:08] INFO: Starting auto-tuning
[2020/08/29 20:32:08] INFO: Preset: Profile 38Th @ 400MHz
[2020/08/29 20:32:08] INFO: Detecting mininum voltage
[2020/08/29 20:33:08] ERROR: driver-btm-tuner.c:905 Failed to initialize the miner
[2020/08/29 20:33:38] INFO: =[ Tuner ]==============================
[2020/08/29 20:33:38] INFO: Starting auto-tuning
[2020/08/29 20:33:38] INFO: Preset: Profile 38Th @ 400MHz
[2020/08/29 20:33:38] INFO: Detecting mininum voltage
[2020/08/29 20:34:33] ERROR: driver-btm-tuner.c:905 Failed to initialize the miner
[2020/08/29 20:34:48] INFO: =[ Tuner ]==============================
[2020/08/29 20:34:48] INFO: Starting auto-tuning
[2020/08/29 20:34:48] INFO: Preset: Profile 38Th @ 400MHz
[2020/08/29 20:34:48] INFO: Detecting mininum voltage
[2020/08/29 20:35:43] ERROR: driver-btm-tuner.c:905 Failed to initialize the miner
[2020/08/29 20:35:58] INFO: =[ Tuner ]==============================
[2020/08/29 20:35:58] INFO: Starting auto-tuning
[2020/08/29 20:35:58] INFO: Preset: Profile 38Th @ 400MHz
[2020/08/29 20:35:58] INFO: Detecting mininum voltage
[2020/08/29 20:36:53] ERROR: driver-btm-tuner.c:905 Failed to initialize the miner
[2020/08/29 20:37:08] INFO: =[ Tuner ]==============================
[2020/08/29 20:37:08] INFO: Starting auto-tuning
[2020/08/29 20:37:08] INFO: Preset: Profile 38Th @ 400MHz
[2020/08/29 20:37:08] INFO: Detecting mininum voltage
[2020/08/29 20:38:03] ERROR: driver-btm-tuner.c:905 Failed to initialize the miner
[2020/08/29 20:38:19] INFO: =[ Tuner ]==============================
[2020/08/29 20:38:19] INFO: Starting auto-tuning
[2020/08/29 20:38:19] INFO: Preset: Profile 38Th @ 400MHz
[2020/08/29 20:38:19] INFO: Detecting mininum voltage
[2020/08/29 20:39:13] ERROR: driver-btm-tuner.c:905 Failed to initialize the miner
[2020/08/29 20:39:29] INFO: =[ Tuner ]==============================
[2020/08/29 20:39:29] INFO: Starting auto-tuning
[2020/08/29 20:39:29] INFO: Preset: Profile 38Th @ 400MHz
[2020/08/29 20:39:29] INFO: Detecting mininum voltage
[2020/08/29 20:40:24] ERROR: driver-btm-tuner.c:905 Failed to initialize the miner
[2020/08/29 20:40:39] INFO: =[ Tuner ]==============================
[2020/08/29 20:40:39] INFO: Starting auto-tuning
[2020/08/29 20:40:39] INFO: Preset: Profile 38Th @ 400MHz
[2020/08/29 20:40:39] INFO: Detecting mininum voltage
[2020/08/29 20:41:34] ERROR: driver-btm-tuner.c:905 Failed to initialize the miner
[2020/08/29 20:41:49] INFO: =[ Tuner ]==============================
[2020/08/29 20:41:49] INFO: Starting auto-tuning
[2020/08/29 20:41:49] INFO: Preset: Profile 38Th @ 400MHz
[2020/08/29 20:41:49] INFO: Detecting mininum voltage
[2020/08/29 20:42:44] ERROR: driver-btm-tuner.c:905 Failed to initialize the miner
[2020/08/29 20:42:59] INFO: =[ Tuner ]==============================
[2020/08/29 20:42:59] INFO: Starting auto-tuning
[2020/08/29 20:42:59] INFO: Preset: Profile 38Th @ 400MHz
[2020/08/29 20:42:59] INFO: Detecting mininum voltage
[2020/08/29 20:43:54] ERROR: driver-btm-tuner.c:905 Failed to initialize the miner
[2020/08/29 20:44:10] INFO: =[ Tuner ]==============================
[2020/08/29 20:44:10] INFO: Starting auto-tuning
[2020/08/29 20:44:10] INFO: Preset: Profile 38Th @ 400MHz
[2020/08/29 20:44:10] INFO: Detecting mininum voltage
[2020/08/29 20:45:04] ERROR: driver-btm-tuner.c:905 Failed to initialize the miner
[2020/08/29 20:45:20] INFO: =[ Tuner ]==============================
[2020/08/29 20:45:20] INFO: Starting auto-tuning
[2020/08/29 20:45:20] INFO: Preset: Profile 38Th @ 400MHz
[2020/08/29 20:45:20] INFO: Detecting mininum voltage
[2020/08/29 20:46:15] ERROR: driver-btm-tuner.c:905 Failed to initialize the miner
[2020/08/29 20:46:30] INFO: =[ Tuner ]==============================
[2020/08/29 20:46:30] INFO: Starting auto-tuning
[2020/08/29 20:46:30] INFO: Preset: Profile 38Th @ 400MHz
[2020/08/29 20:46:30] INFO: Detecting mininum voltage
[2020/08/29 20:47:31] ERROR: driver-btm-tuner.c:905 Failed to initialize the miner
[2020/08/29 20:48:00] INFO: =[ Tuner ]==============================
[2020/08/29 20:48:00] INFO: Starting auto-tuning
[2020/08/29 20:48:00] INFO: Preset: Profile 38Th @ 400MHz
[2020/08/29 20:48:00] INFO: Detecting mininum voltage
[2020/08/29 20:48:56] ERROR: driver-btm-tuner.c:905 Failed to initialize the miner
[2020/08/29 20:49:11] INFO: =[ Tuner ]==============================
[2020/08/29 20:49:11] INFO: Starting auto-tuning
[2020/08/29 20:49:11] INFO: Preset: Profile 38Th @ 400MHz
[2020/08/29 20:49:11] INFO: Detecting mininum voltage
[2020/08/29 20:50:05] ERROR: driver-btm-tuner.c:905 Failed to initialize the miner
[2020/08/29 20:50:21] INFO: =[ Tuner ]==============================
[2020/08/29 20:50:21] INFO: Starting auto-tuning
[2020/08/29 20:50:21] INFO: Preset: Profile 38Th @ 400MHz
[2020/08/29 20:50:21] INFO: Detecting mininum voltage
[2020/08/29 20:51:18] ERROR: driver-btm-tuner.c:905 Failed to initialize the miner
[2020/08/29 20:51:31] INFO: =[ Tuner ]==============================
[2020/08/29 20:51:31] INFO: Starting auto-tuning
[2020/08/29 20:51:31] INFO: Preset: Profile 38Th @ 400MHz
[2020/08/29 20:51:31] INFO: Detecting mininum voltage
[2020/08/29 20:52:26] ERROR: driver-btm-tuner.c:905 Failed to initialize the miner
[2020/08/29 20:52:41] INFO: =[ Tuner ]==============================
[2020/08/29 20:52:41] INFO: Starting auto-tuning
[2020/08/29 20:52:41] INFO: Preset: Profile 38Th @ 400MHz
[2020/08/29 20:52:41] INFO: Detecting mininum voltage
[2020/08/29 20:53:36] ERROR: driver-btm-tuner.c:905 Failed to initialize the miner
[2020/08/29 20:53:51] INFO: =[ Tuner ]==============================
[2020/08/29 20:53:51] INFO: Starting auto-tuning
[2020/08/29 20:53:51] INFO: Preset: Profile 38Th @ 400MHz
[2020/08/29 20:53:51] INFO: Detecting mininum voltage
[2020/08/29 20:54:47] ERROR: driver-btm-tuner.c:905 Failed to initialize the miner
[2020/08/29 20:55:02] INFO: =[ Tuner ]==============================
[2020/08/29 20:55:02] INFO: Starting auto-tuning
[2020/08/29 20:55:02] INFO: Preset: Profile 38Th @ 400MHz
[2020/08/29 20:55:02] INFO: Detecting mininum voltage
[2020/08/29 20:56:04] ERROR: driver-btm-tuner.c:905 Failed to initialize the miner
[2020/08/29 20:56:32] INFO: =[ Tuner ]==============================
[2020/08/29 20:56:32] INFO: Starting auto-tuning
[2020/08/29 20:56:32] INFO: Preset: Profile 38Th @ 400MHz
[2020/08/29 20:56:32] INFO: Detecting mininum voltage
[2020/08/29 20:57:27] ERROR: driver-btm-tuner.c:905 Failed to initialize the miner
[2020/08/29 20:57:42] INFO: =[ Tuner ]==============================
[2020/08/29 20:57:42] INFO: Starting auto-tuning
[2020/08/29 20:57:42] INFO: Preset: Profile 38Th @ 400MHz
[2020/08/29 20:57:42] INFO: Detecting mininum voltage
[2020/08/29 20:58:37] ERROR: driver-btm-tuner.c:905 Failed to initialize the miner
[2020/08/29 20:58:52] INFO: =[ Tuner ]==============================
[2020/08/29 20:58:52] INFO: Starting auto-tuning
[2020/08/29 20:58:52] INFO: Preset: Profile 38Th @ 400MHz
[2020/08/29 20:58:52] INFO: Detecting mininum voltage
[2020/08/29 20:59:47] ERROR: driver-btm-tuner.c:905 Failed to initialize the miner
[2020/08/29 21:00:03] INFO: =[ Tuner ]==============================
[2020/08/29 21:00:03] INFO: Starting auto-tuning
[2020/08/29 21:00:03] INFO: Preset: Profile 38Th @ 400MHz
[2020/08/29 21:00:03] INFO: Detecting mininum voltage
[2020/08/29 21:00:58] ERROR: driver-btm-tuner.c:905 Failed to initialize the miner
[2020/08/29 21:01:13] INFO: =[ Tuner ]==============================
[2020/08/29 21:01:13] INFO: Starting auto-tuning
[2020/08/29 21:01:13] INFO: Preset: Profile 38Th @ 400MHz
[2020/08/29 21:01:13] INFO: Detecting mininum voltage
[2020/08/29 21:02:08] ERROR: driver-btm-tuner.c:905 Failed to initialize the miner
[2020/08/29 21:02:23] INFO: =[ Tuner ]==============================
[2020/08/29 21:02:23] INFO: Starting auto-tuning
[2020/08/29 21:02:23] INFO: Preset: Profile 38Th @ 400MHz
[2020/08/29 21:02:23] INFO: Detecting mininum voltage
[2020/08/29 21:03:18] ERROR: driver-btm-tuner.c:905 Failed to initialize the miner
[2020/08/29 21:03:33] INFO: =[ Tuner ]==============================
[2020/08/29 21:03:33] INFO: Starting auto-tuning
[2020/08/29 21:03:33] INFO: Preset: Profile 38Th @ 400MHz
[2020/08/29 21:03:33] INFO: Detecting mininum voltage
[2020/08/29 21:04:28] ERROR: driver-btm-tuner.c:905 Failed to initialize the miner
[2020/08/29 21:04:43] INFO: =[ Tuner ]==============================
[2020/08/29 21:04:43] INFO: Starting auto-tuning
[2020/08/29 21:04:43] INFO: Preset: Profile 38Th @ 400MHz
[2020/08/29 21:04:43] INFO: Detecting mininum voltage
[2020/08/29 21:05:38] ERROR: driver-btm-tuner.c:905 Failed to initialize the miner
[2020/08/29 21:05:54] INFO: =[ Tuner ]==============================
[2020/08/29 21:05:54] INFO: Starting auto-tuning
[2020/08/29 21:05:54] INFO: Preset: Profile 38Th @ 400MHz
[2020/08/29 21:05:54] INFO: Detecting mininum voltage
[2020/08/29 21:06:48] ERROR: driver-btm-tuner.c:905 Failed to initialize the miner
[2020/08/29 21:07:04] INFO: =[ Tuner ]==============================
[2020/08/29 21:07:04] INFO: Starting auto-tuning
[2020/08/29 21:07:04] INFO: Preset: Profile 38Th @ 400MHz
[2020/08/29 21:07:04] INFO: Detecting mininum voltage
[2020/08/29 21:07:59] ERROR: driver-btm-tuner.c:905 Failed to initialize the miner
[2020/08/29 21:08:14] INFO: =[ Tuner ]==============================
[2020/08/29 21:08:14] INFO: Starting auto-tuning
[2020/08/29 21:08:14] INFO: Preset: Profile 38Th @ 400MHz
[2020/08/29 21:08:14] INFO: Detecting mininum voltage
[2020/08/29 21:09:09] ERROR: driver-btm-tuner.c:905 Failed to initialize the miner
[2020/08/29 21:09:24] INFO: =[ Tuner ]==============================
[2020/08/29 21:09:24] INFO: Starting auto-tuning
[2020/08/29 21:09:24] INFO: Preset: Profile 38Th @ 400MHz
[2020/08/29 21:09:24] INFO: Detecting mininum voltage
[2020/08/29 21:10:19] ERROR: driver-btm-tuner.c:905 Failed to initialize the miner
[2020/08/29 21:10:35] INFO: =[ Tuner ]==============================
[2020/08/29 21:10:35] INFO: Starting auto-tuning
[2020/08/29 21:10:35] INFO: Preset: Profile 38Th @ 400MHz
[2020/08/29 21:10:35] INFO: Detecting mininum voltage
[2020/08/29 21:11:29] ERROR: driver-btm-tuner.c:905 Failed to initialize the miner
[2020/08/29 21:11:45] INFO: =[ Tuner ]==============================
[2020/08/29 21:11:45] INFO: Starting auto-tuning
[2020/08/29 21:11:45] INFO: Preset: Profile 38Th @ 400MHz
[2020/08/29 21:11:45] INFO: Detecting mininum voltage
[2020/08/29 21:12:39] ERROR: driver-btm-tuner.c:905 Failed to initialize the miner
[2020/08/29 21:12:55] INFO: =[ Tuner ]==============================
[2020/08/29 21:12:55] INFO: Starting auto-tuning
[2020/08/29 21:12:55] INFO: Preset: Profile 38Th @ 400MHz
[2020/08/29 21:12:55] INFO: Detecting mininum voltage
[2020/08/29 21:13:50] ERROR: driver-btm-tuner.c:905 Failed to initialize the miner
[2020/08/29 21:14:05] INFO: =[ Tuner ]==============================
[2020/08/29 21:14:05] INFO: Starting auto-tuning
[2020/08/29 21:14:05] INFO: Preset: Profile 38Th @ 400MHz
[2020/08/29 21:14:05] INFO: Detecting mininum voltage
[2020/08/29 21:15:00] ERROR: driver-btm-tuner.c:905 Failed to initialize the miner
[2020/08/29 21:15:15] INFO: =[ Tuner ]==============================
[2020/08/29 21:15:15] INFO: Starting auto-tuning
[2020/08/29 21:15:15] INFO: Preset: Profile 38Th @ 400MHz
[2020/08/29 21:15:15] INFO: Detecting mininum voltage
[2020/08/29 21:16:10] ERROR: driver-btm-tuner.c:905 Failed to initialize the miner
[2020/08/29 21:16:26] INFO: =[ Tuner ]==============================
[2020/08/29 21:16:26] INFO: Starting auto-tuning
[2020/08/29 21:16:26] INFO: Preset: Profile 38Th @ 400MHz
[2020/08/29 21:16:26] INFO: Detecting mininum voltage
[2020/08/29 21:17:20] ERROR: driver-btm-tuner.c:905 Failed to initialize the miner
[2020/08/29 21:17:36] INFO: =[ Tuner ]==============================
[2020/08/29 21:17:36] INFO: Starting auto-tuning
[2020/08/29 21:17:36] INFO: Preset: Profile 38Th @ 400MHz
[2020/08/29 21:17:36] INFO: Detecting mininum voltage
[2020/08/29 21:18:31] ERROR: driver-btm-tuner.c:905 Failed to initialize the miner
[2020/08/29 21:18:46] INFO: =[ Tuner ]==============================
[2020/08/29 21:18:46] INFO: Starting auto-tuning
[2020/08/29 21:18:46] INFO: Preset: Profile 38Th @ 400MHz
[2020/08/29 21:18:46] INFO: Detecting mininum voltage
[2020/08/29 21:19:41] ERROR: driver-btm-tuner.c:905 Failed to initialize the miner
[2020/08/29 21:19:56] INFO: =[ Tuner ]==============================
[2020/08/29 21:19:56] INFO: Starting auto-tuning
[2020/08/29 21:19:56] INFO: Preset: Profile 38Th @ 400MHz
[2020/08/29 21:19:56] INFO: Detecting mininum voltage
[2020/08/29 21:20:51] ERROR: driver-btm-tuner.c:905 Failed to initialize the miner
[2020/08/29 21:21:06] INFO: =[ Tuner ]==============================
[2020/08/29 21:21:06] INFO: Starting auto-tuning
[2020/08/29 21:21:06] INFO: Preset: Profile 38Th @ 400MHz
[2020/08/29 21:21:06] INFO: Detecting mininum voltage
[2020/08/29 21:22:01] ERROR: driver-btm-tuner.c:905 Failed to initialize the miner
[2020/08/29 21:22:17] INFO: =[ Tuner ]==============================
[2020/08/29 21:22:17] INFO: Starting auto-tuning
[2020/08/29 21:22:17] INFO: Preset: Profile 38Th @ 400MHz
[2020/08/29 21:22:17] INFO: Detecting mininum voltage
[2020/08/29 21:23:11] ERROR: driver-btm-tuner.c:905 Failed to initialize the miner
[2020/08/29 21:23:27] INFO: =[ Tuner ]==============================
[2020/08/29 21:23:27] INFO: Starting auto-tuning
[2020/08/29 21:23:27] INFO: Preset: Profile 38Th @ 400MHz
[2020/08/29 21:23:27] INFO: Detecting mininum voltage
[2020/08/29 21:24:22] ERROR: driver-btm-tuner.c:905 Failed to initialize the miner
[2020/08/29 21:24:37] INFO: =[ Tuner ]==============================
[2020/08/29 21:24:37] INFO: Starting auto-tuning
[2020/08/29 21:24:37] INFO: Preset: Profile 38Th @ 400MHz
[2020/08/29 21:24:37] INFO: Detecting mininum voltage
[2020/08/29 21:25:32] ERROR: driver-btm-tuner.c:905 Failed to initialize the miner
[2020/08/29 21:25:47] INFO: =[ Tuner ]==============================
Title: Re: S17 Pro no longer hashing. Bad ASICs ?
Post by: agilmore on August 29, 2020, 10:18:11 PM
This log just keeps repeating: 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: 202888K/245760K available (6345K kernel code, 231K rwdata, 1896K rodata, 1024K init, 223K bss, 26488K reserved, 16384K cma-reserved, 0K highmem)
Virtual kernel memory layout:
vector : 0xffff0000 - 0xffff1000 ( 4 kB)
fixmap : 0xffc00000 - 0xfff00000 (3072 kB)
vmalloc : 0xcf800000 - 0xff800000 ( 768 MB)
lowmem : 0xc0000000 - 0xcf000000 ( 240 MB)
pkmap : 0xbfe00000 - 0xc0000000 ( 2 MB)
modules : 0xbf000000 - 0xbfe00000 ( 14 MB)
.text : 0xc0008000 - 0xc090c424 (9234 kB)
.init : 0xc0a00000 - 0xc0b00000 (1024 kB)
.data : 0xc0b00000 - 0xc0b39fe0 ( 232 kB)
.bss : 0xc0b39fe0 - 0xc0b71c28 ( 224 kB)
Preemptible hierarchical RCU implementation.
Build-time adjustment of leaf fanout to 32.
RCU restricting CPUs from NR_CPUS=4 to nr_cpu_ids=2.
RCU: Adjusting geometry for rcu_fanout_leaf=32, nr_cpu_ids=2
NR_IRQS:16 nr_irqs:16 16
efuse mapped to cf800000
ps7-slcr mapped to cf802000
L2C: platform modifies aux control register: 0x72360000 -> 0x72760000
L2C: DT/platform modifies aux control register: 0x72360000 -> 0x72760000
L2C-310 erratum 769419 enabled
L2C-310 enabling early BRESP for Cortex-A9
L2C-310 full line of zeros enabled for Cortex-A9
L2C-310 ID prefetch enabled, offset 1 lines
L2C-310 dynamic clock gating enabled, standby mode enabled
L2C-310 cache controller enabled, 8 ways, 512 kB
L2C-310: CACHE_ID 0x410000c8, AUX_CTRL 0x76760001
zynq_clock_init: clkc starts at cf802100
Zynq clock init
sched_clock: 64 bits at 333MHz, resolution 3ns, wraps every 4398046511103ns
clocksource: arm_global_timer: mask: 0xffffffffffffffff max_cycles: 0x4ce07af025, max_idle_ns: 440795209040 ns
Switching to timer-based delay loop, resolution 3ns
clocksource: ttc_clocksource: mask: 0xffff max_cycles: 0xffff, max_idle_ns: 537538477 ns
ps7-ttc #0 at cf80a000, irq=18
Console: colour dummy device 80x30
Calibrating delay loop (skipped), value calculated using timer frequency.. 666.66 BogoMIPS (lpj=3333333)
pid_max: default: 32768 minimum: 301
Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
CPU: Testing write buffer coherency: ok
CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
Setting up static identity map for 0x100000 - 0x100058
CPU1: failed to boot: -1
Brought up 1 CPUs
SMP: Total of 1 processors activated (666.66 BogoMIPS).
CPU: All CPU(s) started in SVC mode.
devtmpfs: initialized
VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4
clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
pinctrl core: initialized pinctrl subsystem
NET: Registered protocol family 16
DMA: preallocated 256 KiB pool for atomic coherent allocations
cpuidle: using governor menu
hw-breakpoint: found 5 (+1 reserved) breakpoint and 1 watchpoint registers.
hw-breakpoint: maximum watchpoint size is 4 bytes.
zynq-ocm f800c000.ps7-ocmc: ZYNQ OCM pool: 256 KiB @ 0xcf880000
vgaarb: loaded
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
media: Linux media interface: v0.10
Linux video capture interface: v2.00
pps_core: LinuxPPS API ver. 1 registered
pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
PTP clock support registered
EDAC MC: Ver: 3.0.0
Advanced Linux Sound Architecture Driver Initialized.
clocksource: Switched to clocksource arm_global_timer
NET: Registered protocol family 2
TCP established hash table entries: 2048 (order: 1, 8192 bytes)
TCP bind hash table entries: 2048 (order: 2, 16384 bytes)
TCP: Hash tables configured (established 2048 bind 2048)
UDP hash table entries: 256 (order: 1, 8192 bytes)
UDP-Lite hash table entries: 256 (order: 1, 8192 bytes)
NET: Registered protocol family 1
RPC: Registered named UNIX socket transport module.
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
PCI: CLS 0 bytes, default 64
Trying to unpack rootfs image as initramfs...
rootfs image is not initramfs (no cpio magic); looks like an initrd
Freeing initrd memory: 13448K (ccddf000 - cdb01000)
hw perfevents: enabled with armv7_cortex_a9 PMU driver, 7 counters available
futex hash table entries: 512 (order: 3, 32768 bytes)
workingset: timestamp_bits=28 max_order=16 bucket_order=0
jffs2: version 2.2. (NAND) (SUMMARY) © 2001-2006 Red Hat, Inc.
io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered (default)
dma-pl330 f8003000.ps7-dma: Loaded driver for PL330 DMAC-241330
dma-pl330 f8003000.ps7-dma: DBUFF-128x8bytes Num_Chans-8 Num_Peri-4 Num_Events-16
e0000000.serial: ttyPS0 at MMIO 0xe0000000 (irq = 158, base_baud = 6249999) is a xuartps
console [ttyPS0] enabled
xdevcfg f8007000.ps7-dev-cfg: ioremap 0xf8007000 to cf86e000
[drm] Initialized drm 1.1.0 20060810
brd: module loaded
loop: module loaded
CAN device driver interface
gpiod_set_value: invalid GPIO
libphy: MACB_mii_bus: probed
macb e000b000.ethernet eth0: Cadence GEM rev 0x00020118 at 0xe000b000 irq 31 (00:0a:35:00:00:00)
Generic PHY e000b000.etherne:00: attached PHY driver [Generic PHY] (mii_bus:phy_addr=e000b000.etherne:00, irq=-1)
e1000e: Intel(R) PRO/1000 Network Driver - 3.2.6-k
e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
ehci-pci: EHCI PCI platform driver
usbcore: registered new interface driver usb-storage
mousedev: PS/2 mouse device common for all mice
i2c /dev entries driver
Xilinx Zynq CpuIdle Driver started
sdhci: Secure Digital Host Controller Interface driver
sdhci: Copyright(c) Pierre Ossman
sdhci-pltfm: SDHCI platform and OF driver helper
mmc0: SDHCI controller on e0100000.ps7-sdio [e0100000.ps7-sdio] using ADMA
ledtrig-cpu: registered to indicate activity on CPUs
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
nand: device found, Manufacturer ID: 0x2c, Chip ID: 0xda
nand: Micron MT29F2G08ABAGAWP
nand: 256 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 128
nand: WARNING: pl35x-nand: the ECC used on your system is too weak compared to the one required by the NAND chip
Bad block table found at page 131008, version 0x01
Bad block table found at page 130944, version 0x01
6 ofpart partitions found on MTD device pl35x-nand
Creating 6 MTD partitions on "pl35x-nand":
0x000000000000-0x000002800000 : "BOOT.bin-env-dts-kernel"
0x000002800000-0x000004800000 : "ramfs"
0x000004800000-0x000005000000 : "configs"
0x000005000000-0x000006000000 : "reserve"
0x000006000000-0x000008000000 : "ramfs-bak"
0x000008000000-0x000010000000 : "reserve1"
NET: Registered protocol family 10
sit: IPv6 over IPv4 tunneling driver
NET: Registered protocol family 17
can: controller area network core (rev 20120528 abi 9)
NET: Registered protocol family 29
can: raw protocol (rev 20120528)
can: broadcast manager protocol (rev 20120528 t)
can: netlink gateway (rev 20130117) max_hops=1
zynq_pm_ioremap: no compatible node found for 'xlnx,zynq-ddrc-a05'
zynq_pm_late_init: Unable to map DDRC IO memory.
Registering SWP/SWPB emulation handler
hctosys: unable to open rtc device (rtc0)
ALSA device list:
No soundcards found.
RAMDISK: gzip image found at block 0
EXT4-fs (ram0): couldn't mount as ext3 due to feature incompatibilities
EXT4-fs (ram0): mounted filesystem without journal. Opts: (null)
VFS: Mounted root (ext4 filesystem) on device 1:0.
devtmpfs: mounted
Freeing unused kernel memory: 1024K (c0a00000 - c0b00000)
EXT4-fs (ram0): re-mounted. Opts: block_validity,delalloc,barrier,user_xattr
random: dd urandom read with 0 bits of entropy available
ubi0: attaching mtd2
ubi0: scanning is finished
ubi0: attached mtd2 (name "configs", size 8 MiB)
ubi0: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
ubi0: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
ubi0: VID header offset: 2048 (aligned 2048), data offset: 4096
ubi0: good PEBs: 64, bad PEBs: 0, corrupted PEBs: 0
ubi0: user volume: 1, internal volumes: 1, max. volumes count: 128
ubi0: max/mean erase counter: 2/1, WL threshold: 4096, image sequence number: 4008956885
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 CB6D5B73-C1E8-448B-B1D9-BEFE5F46466B, 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: 4353/1931, WL threshold: 4096, image sequence number: 914180297
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 BCBDE5E0-4C0B-4978-9734-FC58D9F68227, 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
random: nonblocking pool is initialized
[2020/08/28 21:30:48] INFO: Detected 256 Mb of RAM
[2020/08/28 21:30:48] INFO: Switching to manual fan control (30 %)
[2020/08/28 21:30:48] INFO: Checking fans
[2020/08/28 21:30:49] INFO: fan[0] - OK
[2020/08/28 21:30:49] INFO: fan[1] - OK
[2020/08/28 21:30:49] INFO: fan[2] - OK
[2020/08/28 21:30:49] INFO: fan[3] - OK
[2020/08/28 21:30:55] INFO: Power ON
[2020/08/28 21:30:57] INFO: Starting FPGA queue
[2020/08/28 21:30:57] INFO: Initializing hash boards
[2020/08/28 21:30:57] INFO: chain[2] - Initializing
[2020/08/28 21:30:57] INFO: chain[1] - Initializing
[2020/08/28 21:30:57] INFO: chain[0] - Initializing
[2020/08/28 21:31:01] WARN: chain[2] - Failed to measure current voltage (attempt=1) with resp: 0x%02 0xfe
[2020/08/28 21:31:02] WARN: chain[1] - Failed to measure current voltage (attempt=1) with resp: 0x%02 0xfe
[2020/08/28 21:31:02] WARN: chain[2] - Failed to measure current voltage (attempt=2) with resp: 0x%02 0xfe
[2020/08/28 21:31:04] WARN: chain[0] - Failed to measure current voltage (attempt=1) with resp: 0x%02 0xfe
[2020/08/28 21:31:04] WARN: chain[2] - Failed to measure current voltage (attempt=3) with resp: 0x%02 0xfe
[2020/08/28 21:31:05] WARN: chain[1] - Failed to measure current voltage (attempt=2) with resp: 0x%02 0xfe
[2020/08/28 21:31:05] WARN: chain[0] - Failed to measure current voltage (attempt=2) with resp: 0x%02 0xfe
[2020/08/28 21:31:06] WARN: chain[1] - Failed to measure current voltage (attempt=3) with resp: 0x%02 0xfe
[2020/08/28 21:31:07] WARN: chain[2] - Failed to measure current voltage (attempt=1) with resp: 0x%02 0xfe
[2020/08/28 21:31:07] WARN: chain[0] - Failed to measure current voltage (attempt=3) with resp: 0x%02 0xfe
[2020/08/28 21:31:08] WARN: chain[2] - Failed to measure current voltage (attempt=2) with resp: 0x%02 0xfe
[2020/08/28 21:31:08] WARN: chain[1] - Failed to measure current voltage (attempt=1) with resp: 0x%02 0xfe
[2020/08/28 21:31:09] WARN: chain[2] - Failed to measure current voltage (attempt=3) with resp: 0x%02 0xfe
[2020/08/28 21:31:09] WARN: chain[0] - Failed to measure current voltage (attempt=1) with resp: 0x%02 0xfe
[2020/08/28 21:31:10] WARN: chain[1] - Failed to measure current voltage (attempt=2) with resp: 0x%02 0xfe
[2020/08/28 21:31:11] WARN: chain[0] - Failed to measure current voltage (attempt=2) with resp: 0x%02 0xfe
[2020/08/28 21:31:11] WARN: chain[2] - Failed to measure current voltage (attempt=1) with resp: 0x%02 0xfe
[2020/08/28 21:31:12] WARN: chain[1] - Failed to measure current voltage (attempt=3) with resp: 0x%02 0xfe
[2020/08/28 21:31:12] WARN: chain[0] - Failed to measure current voltage (attempt=3) with resp: 0x%02 0xfe
[2020/08/28 21:31:13] WARN: chain[2] - Failed to measure current voltage (attempt=2) with resp: 0x%02 0xfe
[2020/08/28 21:31:14] WARN: chain[1] - Failed to measure current voltage (attempt=1) with resp: 0x%02 0xfe
[2020/08/28 21:31:14] WARN: chain[2] - Failed to measure current voltage (attempt=3) with resp: 0x%02 0xfe
[2020/08/28 21:31:15] WARN: chain[0] - Failed to measure current voltage (attempt=1) with resp: 0x%02 0xfe
[2020/08/28 21:31:15] WARN: chain[1] - Failed to measure current voltage (attempt=2) with resp: 0x%02 0xfe
[2020/08/28 21:31:16] WARN: chain[0] - Failed to measure current voltage (attempt=2) with resp: 0x%02 0xfe
[2020/08/28 21:31:17] WARN: chain[2] - Failed to measure current voltage (attempt=1) with resp: 0x%02 0xfe
[2020/08/28 21:31:17] WARN: chain[1] - Failed to measure current voltage (attempt=3) with resp: 0x%02 0xfe
[2020/08/28 21:31:18] WARN: chain[0] - Failed to measure current voltage (attempt=3) with resp: 0x%02 0xfe
[2020/08/28 21:31:18] WARN: chain[2] - Failed to measure current voltage (attempt=2) with resp: 0x%02 0xfe
[2020/08/28 21:31:19] WARN: chain[1] - Failed to measure current voltage (attempt=1) with resp: 0x%02 0xfe
[2020/08/28 21:31:19] WARN: chain[2] - Failed to measure current voltage (attempt=3) with resp: 0x%02 0xfe
[2020/08/28 21:31:20] WARN: chain[0] - Failed to measure current voltage (attempt=1) with resp: 0x%02 0xfe
[2020/08/28 21:31:21] WARN: chain[1] - Failed to measure current voltage (attempt=2) with resp: 0x%02 0xfe
[2020/08/28 21:31:21] WARN: chain[0] - Failed to measure current voltage (attempt=2) with resp: 0x%02 0xfe
[2020/08/28 21:31:22] WARN: chain[2] - Failed to measure current voltage (attempt=1) with resp: 0x%02 0xfe
[2020/08/28 21:31:22] WARN: chain[1] - Failed to measure current voltage (attempt=3) with resp: 0x%02 0xfe
[2020/08/28 21:31:23] WARN: chain[0] - Failed to measure current voltage (attempt=3) with resp: 0x%02 0xfe
[2020/08/28 21:31:24] WARN: chain[2] - Failed to measure current voltage (attempt=2) with resp: 0x%02 0xfe
[2020/08/28 21:31:24] WARN: chain[1] - Failed to measure current voltage (attempt=1) with resp: 0x%02 0xfe
[2020/08/28 21:31:25] WARN: chain[2] - Failed to measure current voltage (attempt=3) with resp: 0x%02 0xfe
[2020/08/28 21:31:25] WARN: chain[0] - Failed to measure current voltage (attempt=1) with resp: 0x%02 0xfe
[2020/08/28 21:31:26] ERROR: driver-btm-chain.c:687 chain[2] - Voltage is different, cur=0 mV tgt=21000 mV
[2020/08/28 21:31:26] ERROR: driver-btm-chain.c:471 chain[2] - Failed to set start up voltage
[2020/08/28 21:31:26] INFO: chain[2] - Shutting down the chain
[2020/08/28 21:31:26] ERROR: driver-btm-base.c:361 chain[2] - Initialization failed
[2020/08/28 21:31:26] WARN: chain[1] - Failed to measure current voltage (attempt=2) with resp: 0x%02 0xfe
[2020/08/28 21:31:26] WARN: chain[0] - Failed to measure current voltage (attempt=2) with resp: 0x%02 0xfe
[2020/08/28 21:31:27] WARN: chain[1] - Failed to measure current voltage (attempt=3) with resp: 0x%02 0xfe
[2020/08/28 21:31:28] WARN: chain[0] - Failed to measure current voltage (attempt=3) with resp: 0x%02 0xfe
[2020/08/28 21:31:28] ERROR: driver-btm-chain.c:687 chain[1] - Voltage is different, cur=0 mV tgt=21000 mV
[2020/08/28 21:31:28] ERROR: driver-btm-chain.c:471 chain[1] - Failed to set start up voltage
[2020/08/28 21:31:28] INFO: chain[1] - Shutting down the chain
[2020/08/28 21:31:28] ERROR: driver-btm-base.c:361 chain[1] - Initialization failed
[2020/08/28 21:31:29] ERROR: driver-btm-chain.c:687 chain[0] - Voltage is different, cur=0 mV tgt=21000 mV
[2020/08/28 21:31:29] ERROR: driver-btm-chain.c:471 chain[0] - Failed to set start up voltage
[2020/08/28 21:31:29] INFO: chain[0] - Shutting down the chain
[2020/08/28 21:31:29] ERROR: driver-btm-base.c:361 chain[0] - Initialization failed
[2020/08/28 21:31:29] WARN: All chains are disabled or disconnected
[2020/08/28 21:31:29] ERROR: driver-btm-base.c:2156 Failed to initialize hash boards
[2020/08/28 21:31:29] INFO: Shutting down the miner
[2020/08/28 21:31:29] INFO: Stopping FPGA queue
[2020/08/28 21:31:29] INFO: chain[0] - Shutting down the chain
[2020/08/28 21:31:29] INFO: chain[1] - Shutting down the chain
[2020/08/28 21:31:29] INFO: chain[2] - Shutting down the chain
[2020/08/28 21:31:29] INFO: Power OFF
[2020/08/28 21:31:29] ERROR: driver-btm-base.c:2360 Miner initialization failed
[2020/08/28 21:31:52] INFO: Detected 256 Mb of RAM
[2020/08/28 21:31:52] INFO: Switching to manual fan control (30 %)
[2020/08/28 21:31:52] INFO: Checking fans
[2020/08/28 21:31:53] INFO: fan[0] - OK
[2020/08/28 21:31:53] INFO: fan[1] - OK
[2020/08/28 21:31:53] INFO: fan[2] - OK
[2020/08/28 21:31:53] INFO: fan[3] - OK
[2020/08/28 21:31:59] INFO: Shutting down the miner
[2020/08/28 21:31:59] INFO: Power OFF
[2020/08/28 21:34:02] INFO: Detected 256 Mb of RAM
[2020/08/28 21:34:02] INFO: Switching to manual fan control (30 %)
[2020/08/28 21:34:02] INFO: Checking fans
[2020/08/28 21:34:03] INFO: fan[0] - OK
[2020/08/28 21:34:03] INFO: fan[1] - OK
[2020/08/28 21:34:03] INFO: fan[2] - OK
[2020/08/28 21:34:03] INFO: fan[3] - OK
[2020/08/28 21:34:09] INFO: Power ON
[2020/08/28 21:34:11] INFO: Starting FPGA queue
[2020/08/28 21:34:11] INFO: Initializing hash boards
[2020/08/28 21:34:11] INFO: chain[2] - Initializing
[2020/08/28 21:34:11] INFO: chain[1] - Initializing
[2020/08/28 21:34:11] INFO: chain[0] - Initializing
[2020/08/28 21:34:15] WARN: chain[2] - Failed to measure current voltage (attempt=1) with resp: 0x%02 0xfe
[2020/08/28 21:34:16] WARN: chain[1] - Failed to measure current voltage (attempt=1) with resp: 0x%02 0xfe
[2020/08/28 21:34:17] INFO: Shutting down the miner
[2020/08/28 21:34:17] WARN: chain[2] - Failed to measure current voltage (attempt=2) with resp: 0x%02 0xfe
[2020/08/28 21:34:17] INFO: Stopping FPGA queue
[2020/08/28 21:34:17] INFO: chain[0] - Shutting down the chain
[2020/08/28 21:34:17] INFO: chain[1] - Shutting down the chain
[2020/08/28 21:34:17] INFO: chain[2] - Shutting down the chain
[2020/08/28 21:34:17] INFO: Power OFF
[2020/08/28 21:34:28] INFO: Detected 256 Mb of RAM
[2020/08/28 21:34:28] INFO: Switching to manual fan control (30 %)
[2020/08/28 21:34:28] INFO: Checking fans
[2020/08/28 21:34:29] INFO: fan[0] - OK
[2020/08/28 21:34:29] INFO: fan[1] - OK
[2020/08/28 21:34:29] INFO: fan[2] - OK
[2020/08/28 21:34:29] INFO: fan[3] - OK
[2020/08/28 21:34:35] INFO: Power ON
[2020/08/28 21:34:37] INFO: Starting FPGA queue
[2020/08/28 21:34:37] INFO: Initializing hash boards
[2020/08/28 21:34:37] INFO: chain[2] - Initializing
[2020/08/28 21:34:37] INFO: chain[1] - Initializing
[2020/08/28 21:34:37] INFO: chain[0] - Initializing
[2020/08/28 21:34:41] WARN: chain[2] - Failed to measure current voltage (attempt=1) with resp: 0x%02 0xfe
[2020/08/28 21:34:42] WARN: chain[1] - Failed to measure current voltage (attempt=1) with resp: 0x%02 0xfe
[2020/08/28 21:34:43] WARN: chain[2] - Failed to measure current voltage (attempt=2) with resp: 0x%02 0xfe
[2020/08/28 21:34:44] WARN: chain[0] - Failed to measure current voltage (attempt=1) with resp: 0x%02 0xfe
[2020/08/28 21:34:45] WARN: chain[2] - Failed to measure current voltage (attempt=3) with resp: 0x%02 0xfe
[2020/08/28 21:34:45] WARN: chain[1] - Failed to measure current voltage (attempt=2) with resp: 0x%02 0xfe
[2020/08/28 21:34:46] WARN: chain[0] - Failed to measure current voltage (attempt=2) with resp: 0x%02 0xfe
[2020/08/28 21:34:46] WARN: chain[1] - Failed to measure current voltage (attempt=3) with resp: 0x%02 0xfe
[2020/08/28 21:34:47] WARN: chain[2] - Failed to measure current voltage (attempt=1) with resp: 0x%02 0xfe
[2020/08/28 21:34:48] WARN: chain[0] - Failed to measure current voltage (attempt=3) with resp: 0x%02 0xfe
[2020/08/28 21:34:48] WARN: chain[2] - Failed to measure current voltage (attempt=2) with resp: 0x%02 0xfe
[2020/08/28 21:34:49] WARN: chain[1] - Failed to measure current voltage (attempt=1) with resp: 0x%02 0xfe
[2020/08/28 21:34:49] WARN: chain[2] - Failed to measure current voltage (attempt=3) with resp: 0x%02 0xfe
[2020/08/28 21:34:50] WARN: chain[0] - Failed to measure current voltage (attempt=1) with resp: 0x%02 0xfe
[2020/08/28 21:34:51] WARN: chain[1] - Failed to measure current voltage (attempt=2) with resp: 0x%02 0xfe
[2020/08/28 21:34:51] WARN: chain[0] - Failed to measure current voltage (attempt=2) with resp: 0x%02 0xfe
[2020/08/28 21:34:52] WARN: chain[2] - Failed to measure current voltage (attempt=1) with resp: 0x%02 0xfe
[2020/08/28 21:34:52] WARN: chain[1] - Failed to measure current voltage (attempt=3) with resp: 0x%02 0xfe
[2020/08/28 21:34:53] WARN: chain[0] - Failed to measure current voltage (attempt=3) with resp: 0x%02 0xfe
[2020/08/28 21:34:54] WARN: chain[2] - Failed to measure current voltage (attempt=2) with resp: 0x%02 0xfe
[2020/08/28 21:34:54] WARN: chain[1] - Failed to measure current voltage (attempt=1) with resp: 0x%02 0xfe
[2020/08/28 21:34:55] WARN: chain[2] - Failed to measure current voltage (attempt=3) with resp: 0x%02 0xfe
[2020/08/28 21:34:55] WARN: chain[0] - Failed to measure current voltage (attempt=1) with resp: 0x%02 0xfe
[2020/08/28 21:34:56] WARN: chain[1] - Failed to measure current voltage (attempt=2) with resp: 0x%02 0xfe
[2020/08/28 21:34:56] WARN: chain[0] - Failed to measure current voltage (attempt=2) with resp: 0x%02 0xfe
[2020/08/28 21:34:57] WARN: chain[2] - Failed to measure current voltage (attempt=1) with resp: 0x%02 0xfe
[2020/08/28 21:34:58] WARN: chain[1] - Failed to measure current voltage (attempt=3) with resp: 0x%02 0xfe
[2020/08/28 21:34:58] WARN: chain[0] - Failed to measure current voltage (attempt=3) with resp: 0x%02 0xfe
[2020/08/28 21:34:59] WARN: chain[2] - Failed to measure current voltage (attempt=2) with resp: 0x%02 0xfe
[2020/08/28 21:34:59] WARN: chain[1] - Failed to measure current voltage (attempt=1) with resp: 0x%02 0xfe
[2020/08/28 21:35:00] WARN: chain[2] - Failed to measure current voltage (attempt=3) with resp: 0x%02 0xfe
[2020/08/28 21:35:01] WARN: chain[0] - Failed to measure current voltage (attempt=1) with resp: 0x%02 0xfe
[2020/08/28 21:35:01] WARN: chain[1] - Failed to measure current voltage (attempt=2) with resp: 0x%02 0xfe
[2020/08/28 21:35:02] WARN: chain[0] - Failed to measure current voltage (attempt=2) with resp: 0x%02 0xfe
[2020/08/28 21:35:02] WARN: chain[2] - Failed to measure current voltage (attempt=1) with resp: 0x%02 0xfe
[2020/08/28 21:35:03] WARN: chain[1] - Failed to measure current voltage (attempt=3) with resp: 0x%02 0xfe
[2020/08/28 21:35:03] WARN: chain[0] - Failed to measure current voltage (attempt=3) with resp: 0x%02 0xfe
[2020/08/28 21:35:04] WARN: chain[2] - Failed to measure current voltage (attempt=2) with resp: 0x%02 0xfe
[2020/08/28 21:35:05] WARN: chain[1] - Failed to measure current voltage (attempt=1) with resp: 0x%02 0xfe
[2020/08/28 21:35:05] WARN: chain[2] - Failed to measure current voltage (attempt=3) with resp: 0x%02 0xfe
[2020/08/28 21:35:06] WARN: chain[0] - Failed to measure current voltage (attempt=1) with resp: 0x%02 0xfe
[2020/08/28 21:35:06] ERROR: driver-btm-chain.c:687 chain[2] - Voltage is different, cur=0 mV tgt=21000 mV
[2020/08/28 21:35:06] ERROR: driver-btm-chain.c:471 chain[2] - Failed to set start up voltage
[2020/08/28 21:35:06] INFO: chain[2] - Shutting down the chain
[2020/08/28 21:35:06] ERROR: driver-btm-base.c:361 chain[2] - Initialization failed
[2020/08/28 21:35:06] WARN: chain[1] - Failed to measure current voltage (attempt=2) with resp: 0x%02 0xfe
[2020/08/28 21:35:07] WARN: chain[0] - Failed to measure current voltage (attempt=2) with resp: 0x%02 0xfe
[2020/08/28 21:35:08] WARN: chain[1] - Failed to measure current voltage (attempt=3) with resp: 0x%02 0xfe
[2020/08/28 21:35:08] WARN: chain[0] - Failed to measure current voltage (attempt=3) with resp: 0x%02 0xfe
[2020/08/28 21:35:09] ERROR: driver-btm-chain.c:687 chain[1] - Voltage is different, cur=0 mV tgt=21000 mV
[2020/08/28 21:35:09] ERROR: driver-btm-chain.c:471 chain[1] - Failed to set start up voltage
[2020/08/28 21:35:09] INFO: chain[1] - Shutting down the chain
[2020/08/28 21:35:09] ERROR: driver-btm-base.c:361 chain[1] - Initialization failed
[2020/08/28 21:35:09] ERROR: driver-btm-chain.c:687 chain[0] - Voltage is different, cur=0 mV tgt=21000 mV
[2020/08/28 21:35:09] ERROR: driver-btm-chain.c:471 chain[0] - Failed to set start up voltage
[2020/08/28 21:35:09] INFO: chain[0] - Shutting down the chain
[2020/08/28 21:35:09] ERROR: driver-btm-base.c:361 chain[0] - Initialization failed
[2020/08/28 21:35:09] WARN: All chains are disabled or disconnected
[2020/08/28 21:35:09] ERROR: driver-btm-base.c:2156 Failed to initialize hash boards
[2020/08/28 21:35:09] INFO: Shutting down the miner
[2020/08/28 21:35:09] INFO: Stopping FPGA queue
[2020/08/28 21:35:09] INFO: chain[0] - Shutting down the chain
[2020/08/28 21:35:09] INFO: chain[1] - Shutting down the chain
[2020/08/28 21:35:09] INFO: chain[2] - Shutting down the chain
[2020/08/28 21:35:09] INFO: Power OFF
[2020/08/28 21:35:09] ERROR: driver-btm-base.c:2360 Miner initialization failed
[2020/08/28 21:35:32] INFO: Detected 256 Mb of RAM
[2020/08/28 21:35:32] INFO: Switching to manual fan control (30 %)
[2020/08/28 21:35:32] INFO: Checking fans
[2020/08/28 21:35:33] INFO: fan[0] - OK
[2020/08/28 21:35:33] INFO: fan[1] - OK
[2020/08/28 21:35:33] INFO: fan[2] - OK
[2020/08/28 21:35:33] INFO: fan[3] - OK
[2020/08/28 21:35:39] INFO: Power ON
[2020/08/28 21:35:41] INFO: Starting FPGA queue
[2020/08/28 21:35:41] INFO: Initializing hash boards
[2020/08/28 21:35:41] INFO: chain[1] - Initializing
[2020/08/28 21:35:41] INFO: chain[2] - Initializing
[2020/08/28 21:35:41] INFO: chain[0] - Initializing
[2020/08/28 21:35:45] WARN: chain[1] - Failed to measure current voltage (attempt=1) with resp: 0x%02 0xfe
[2020/08/28 21:35:47] WARN: chain[2] - Failed to measure current voltage (attempt=1) with resp: 0x%02 0xfe
[2020/08/28 21:35:47] WARN: chain[1] - Failed to measure current voltage (attempt=2) with resp: 0x%02 0xfe
[2020/08/28 21:35:48] WARN: chain[0] - Failed to measure current voltage (attempt=1) with resp: 0x%02 0xfe
[2020/08/28 21:35:49] WARN: chain[1] - Failed to measure current voltage (attempt=3) with resp: 0x%02 0xfe
[2020/08/28 21:35:49] WARN: chain[2] - Failed to measure current voltage (attempt=2) with resp: 0x%02 0xfe
[2020/08/28 21:35:50] WARN: chain[0] - Failed to measure current voltage (attempt=2) with resp: 0x%02 0xfe
[2020/08/28 21:35:51] WARN: chain[2] - Failed to measure current voltage (attempt=3) with resp: 0x%02 0xfe
[2020/08/28 21:35:51] WARN: chain[1] - Failed to measure current voltage (attempt=1) with resp: 0x%02 0xfe
[2020/08/28 21:35:52] WARN: chain[0] - Failed to measure current voltage (attempt=3) with resp: 0x%02 0xfe
[2020/08/28 21:35:52] WARN: chain[1] - Failed to measure current voltage (attempt=2) with resp: 0x%02 0xfe
[2020/08/28 21:35:53] WARN: chain[2] - Failed to measure current voltage (attempt=1) with resp: 0x%02 0xfe
[2020/08/28 21:35:54] WARN: chain[1] - Failed to measure current voltage (attempt=3) with resp: 0x%02 0xfe
[2020/08/28 21:35:54] WARN: chain[0] - Failed to measure current voltage (attempt=1) with resp: 0x%02 0xfe
[2020/08/28 21:35:55] WARN: chain[2] - Failed to measure current voltage (attempt=2) with resp: 0x%02 0xfe
[2020/08/28 21:35:55] WARN: chain[0] - Failed to measure current voltage (attempt=2) with resp: 0x%02 0xfe
[2020/08/28 21:35:56] WARN: chain[1] - Failed to measure current voltage (attempt=1) with resp: 0x%02 0xfe
[2020/08/28 21:35:56] WARN: chain[2] - Failed to measure current voltage (attempt=3) with resp: 0x%02 0xfe
[2020/08/28 21:35:57] WARN: chain[0] - Failed to measure current voltage (attempt=3) with resp: 0x%02 0xfe
[2020/08/28 21:35:58] WARN: chain[1] - Failed to measure current voltage (attempt=2) with resp: 0x%02 0xfe
[2020/08/28 21:35:58] WARN: chain[2] - Failed to measure current voltage (attempt=1) with resp: 0x%02 0xfe
[2020/08/28 21:35:59] WARN: chain[1] - Failed to measure current voltage (attempt=3) with resp: 0x%02 0xfe
[2020/08/28 21:35:59] WARN: chain[0] - Failed to measure current voltage (attempt=1) with resp: 0x%02 0xfe
[2020/08/28 21:36:00] WARN: chain[2] - Failed to measure current voltage (attempt=2) with resp: 0x%02 0xfe
[2020/08/28 21:36:01] WARN: chain[0] - Failed to measure current voltage (attempt=2) with resp: 0x%02 0xfe
[2020/08/28 21:36:01] WARN: chain[1] - Failed to measure current voltage (attempt=1) with resp: 0x%02 0xfe
[2020/08/28 21:36:02] WARN: chain[2] - Failed to measure current voltage (attempt=3) with resp: 0x%02 0xfe
[2020/08/28 21:36:02] WARN: chain[0] - Failed to measure current voltage (attempt=3) with resp: 0x%02 0xfe
[2020/08/28 21:36:03] WARN: chain[1] - Failed to measure current voltage (attempt=2) with resp: 0x%02 0xfe
[2020/08/28 21:36:04] WARN: chain[2] - Failed to measure current voltage (attempt=1) with resp: 0x%02 0xfe
[2020/08/28 21:36:04] WARN: chain[1] - Failed to measure current voltage (attempt=3) with resp: 0x%02 0xfe
[2020/08/28 21:36:05] WARN: chain[0] - Failed to measure current voltage (attempt=1) with resp: 0x%02 0xfe
[2020/08/28 21:36:05] WARN: chain[2] - Failed to measure current voltage (attempt=2) with resp: 0x%02 0xfe
[2020/08/28 21:36:06] WARN: chain[0] - Failed to measure current voltage (attempt=2) with resp: 0x%02 0xfe
[2020/08/28 21:36:06] WARN: chain[1] - Failed to measure current voltage (attempt=1) with resp: 0x%02 0xfe
[2020/08/28 21:36:07] WARN: chain[2] - Failed to measure current voltage (attempt=3) with resp: 0x%02 0xfe
[2020/08/28 21:36:08] WARN: chain[0] - Failed to measure current voltage (attempt=3) with resp: 0x%02 0xfe
[2020/08/28 21:36:08] WARN: chain[1] - Failed to measure current voltage (attempt=2) with resp: 0x%02 0xfe
[2020/08/28 21:36:09] WARN: chain[2] - Failed to measure current voltage (attempt=1) with resp: 0x%02 0xfe
[2020/08/28 21:36:09] WARN: chain[1] - Failed to measure current voltage (attempt=3) with resp: 0x%02 0xfe
[2020/08/28 21:36:10] WARN: chain[0] - Failed to measure current voltage (attempt=1) with resp: 0x%02 0xfe
[2020/08/28 21:36:10] ERROR: driver-btm-chain.c:687 chain[1] - Voltage is different, cur=0 mV tgt=21000 mV
[2020/08/28 21:36:10] ERROR: driver-btm-chain.c:471 chain[1] - Failed to set start up voltage
[2020/08/28 21:36:10] INFO: chain[1] - Shutting down the chain
[2020/08/28 21:36:10] ERROR: driver-btm-base.c:361 chain[1] - Initialization failed
[2020/08/28 21:36:11] WARN: chain[2] - Failed to measure current voltage (attempt=2) with resp: 0x%02 0xfe
[2020/08/28 21:36:11] WARN: chain[0] - Failed to measure current voltage (attempt=2) with resp: 0x%02 0xfe
[2020/08/28 21:36:12] WARN: chain[2] - Failed to measure current voltage (attempt=3) with resp: 0x%02 0xfe
[2020/08/28 21:36:12] WARN: chain[0] - Failed to measure current voltage (attempt=3) with resp: 0x%02 0xfe
[2020/08/28 21:36:13] ERROR: driver-btm-chain.c:687 chain[2] - Voltage is different, cur=0 mV tgt=21000 mV
[2020/08/28 21:36:13] ERROR: driver-btm-chain.c:471 chain[2] - Failed to set start up voltage
[2020/08/28 21:36:13] INFO: chain[2] - Shutting down the chain
[2020/08/28 21:36:13] ERROR: driver-btm-base.c:361 chain[2] - Initialization failed
[2020/08/28 21:36:13] ERROR: driver-btm-chain.c:687 chain[0] - Voltage is different, cur=0 mV tgt=21000 mV
[2020/08/28 21:36:13] ERROR: driver-btm-chain.c:471 chain[0] - Failed to set start up voltage
[2020/08/28 21:36:13] INFO: chain[0] - Shutting down the chain
[2020/08/28 21:36:13] ERROR: driver-btm-base.c:361 chain[0] - Initialization failed
[2020/08/28 21:36:13] WARN: All chains are disabled or disconnected
[2020/08/28 21:36:13] ERROR: driver-btm-base.c:2156 Failed to initialize hash boards
[2020/08/28 21:36:13] INFO: Shutting down the miner
[2020/08/28 21:36:14] INFO: Stopping FPGA queue
[2020/08/28 21:36:14] INFO: chain[0] - Shutting down the chain
[2020/08/28 21:36:14] INFO: chain[1] - Shutting down the chain
[2020/08/28 21:36:14] INFO: chain[2] - Shutting down the chain
[2020/08/28 21:36:14] INFO: Power OFF
[2020/08/28 21:36:14] ERROR: driver-btm-base.c:2360 Miner initialization failed
[2020/08/28 21:36:43] INFO: Detected 256 Mb of RAM
[2020/08/28 21:36:43] INFO: Switching to manual fan control (30 %)
[2020/08/28 21:36:43] INFO: Checking fans
[2020/08/28 21:36:44] INFO: fan[0] - OK
[2020/08/28 21:36:44] INFO: fan[1] - OK
[2020/08/28 21:36:44] INFO: fan[2] - OK
[2020/08/28 21:36:44] INFO: fan[3] - OK
[2020/08/28 21:36:50] INFO: Power ON
[2020/08/28 21:36:52] INFO: Starting FPGA queue
[2020/08/28 21:36:52] INFO: Initializing hash boards
[2020/08/28 21:36:52] INFO: chain[2] - Initializing
[2020/08/28 21:36:52] INFO: chain[1] - Initializing
[2020/08/28 21:36:52] INFO: chain[0] - Initializing
[2020/08/28 21:36:56] WARN: chain[2] - Failed to measure current voltage (attempt=1) with resp: 0x%02 0xfe
[2020/08/28 21:36:57] WARN: chain[1] - Failed to measure current voltage (attempt=1) with resp: 0x%02 0xfe
[2020/08/28 21:36:57] WARN: chain[2] - Failed to measure current voltage (attempt=2) with resp: 0x%02 0xfe
[2020/08/28 21:36:58] WARN: chain[0] - Failed to measure current voltage (attempt=1) with resp: 0x%02 0xfe
[2020/08/28 21:36:59] WARN: chain[2] - Failed to measure current voltage (attempt=3) with resp: 0x%02 0xfe
[2020/08/28 21:37:00] WARN: chain[1] - Failed to measure current voltage (attempt=2) with resp: 0x%02 0xfe
[2020/08/28 21:37:00] WARN: chain[0] - Failed to measure current voltage (attempt=2) with resp: 0x%02 0xfe
[2020/08/28 21:37:01] WARN: chain[1] - Failed to measure current voltage (attempt=3) with resp: 0x%02 0xfe
[2020/08/28 21:37:01] WARN: chain[2] - Failed to measure current voltage (attempt=1) with resp: 0x%02 0xfe
[2020/08/28 21:37:02] WARN: chain[0] - Failed to measure current voltage (attempt=3) with resp: 0x%02 0xfe
[2020/08/28 21:37:03] WARN: chain[2] - Failed to measure current voltage (attempt=2) with resp: 0x%02 0xfe
[2020/08/28 21:37:03] WARN: chain[1] - Failed to measure current voltage (attempt=1) with resp: 0x%02 0xfe
[2020/08/28 21:37:04] WARN: chain[2] - Failed to measure current voltage (attempt=3) with resp: 0x%02 0xfe
[2020/08/28 21:37:04] WARN: chain[0] - Failed to measure current voltage (attempt=1) with resp: 0x%02 0xfe
[2020/08/28 21:37:05] WARN: chain[1] - Failed to measure current voltage (attempt=2) with resp: 0x%02 0xfe
[2020/08/28 21:37:06] WARN: chain[0] - Failed to measure current voltage (attempt=2) with resp: 0x%02 0xfe
[2020/08/28 21:37:06] WARN: chain[2] - Failed to measure current voltage (attempt=1) with resp: 0x%02 0xfe
[2020/08/28 21:37:07] WARN: chain[1] - Failed to measure current voltage (attempt=3) with resp: 0x%02 0xfe
[2020/08/28 21:37:07] WARN: chain[0] - Failed to measure current voltage (attempt=3) with resp: 0x%02 0xfe
[2020/08/28 21:37:08] WARN: chain[2] - Failed to measure current voltage (attempt=2) with resp: 0x%02 0xfe
[2020/08/28 21:37:08] WARN: chain[1] - Failed to measure current voltage (attempt=1) with resp: 0x%02 0xfe
[2020/08/28 21:37:09] WARN: chain[2] - Failed to measure current voltage (attempt=3) with resp: 0x%02 0xfe
[2020/08/28 21:37:10] WARN: chain[0] - Failed to measure current voltage (attempt=1) with resp: 0x%02 0xfe
[2020/08/28 21:37:10] WARN: chain[1] - Failed to measure current voltage (attempt=2) with resp: 0x%02 0xfe
[2020/08/28 21:37:11] WARN: chain[0] - Failed to measure current voltage (attempt=2) with resp: 0x%02 0xfe
[2020/08/28 21:37:11] WARN: chain[2] - Failed to measure current voltage (attempt=1) with resp: 0x%02 0xfe
[2020/08/28 21:37:12] WARN: chain[1] - Failed to measure current voltage (attempt=3) with resp: 0x%02 0xfe
[2020/08/28 21:37:13] WARN: chain[0] - Failed to measure current voltage (attempt=3) with resp: 0x%02 0xfe
[2020/08/28 21:37:13] WARN: chain[2] - Failed to measure current voltage (attempt=2) with resp: 0x%02 0xfe
[2020/08/28 21:37:14] WARN: chain[1] - Failed to measure current voltage (attempt=1) with resp: 0x%02 0xfe
[2020/08/28 21:37:14] WARN: chain[2] - Failed to measure current voltage (attempt=3) with resp: 0x%02 0xfe
[2020/08/28 21:37:15] WARN: chain[0] - Failed to measure current voltage (attempt=1) with resp: 0x%02 0xfe
[2020/08/28 21:37:15] WARN: chain[1] - Failed to measure current voltage (attempt=2) with resp: 0x%02 0xfe
[2020/08/28 21:37:16] WARN: chain[0] - Failed to measure current voltage (attempt=2) with resp: 0x%02 0xfe
[2020/08/28 21:37:17] WARN: chain[2] - Failed to measure current voltage (attempt=1) with resp: 0x%02 0xfe
[2020/08/28 21:37:17] WARN: chain[1] - Failed to measure current voltage (attempt=3) with resp: 0x%02 0xfe
[2020/08/28 21:37:18] WARN: chain[0] - Failed to measure current voltage (attempt=3) with resp: 0x%02 0xfe
[2020/08/28 21:37:18] WARN: chain[2] - Failed to measure current voltage (attempt=2) with resp: 0x%02 0xfe
[2020/08/28 21:37:19] WARN: chain[1] - Failed to measure current voltage (attempt=1) with resp: 0x%02 0xfe
[2020/08/28 21:37:20] WARN: chain[2] - Failed to measure current voltage (attempt=3) with resp: 0x%02 0xfe
[2020/08/28 21:37:20] WARN: chain[0] - Failed to measure current voltage (attempt=1) with resp: 0x%02 0xfe
[2020/08/28 21:37:21] ERROR: driver-btm-chain.c:687 chain[2] - Voltage is different, cur=0 mV tgt=21000 mV
[2020/08/28 21:37:21] ERROR: driver-btm-chain.c:471 chain[2] - Failed to set start up voltage
[2020/08/28 21:37:21] INFO: chain[2] - Shutting down the chain
[2020/08/28 21:37:21] ERROR: driver-btm-base.c:361 chain[2] - Initialization failed
[2020/08/28 21:37:21] WARN: chain[1] - Failed to measure current voltage (attempt=2) with resp: 0x%02 0xfe
[2020/08/28 21:37:21] WARN: chain[0] - Failed to measure current voltage (attempt=2) with resp: 0x%02 0xfe
[2020/08/28 21:37:22] WARN: chain[1] - Failed to measure current voltage (attempt=3) with resp: 0x%02 0xfe
[2020/08/28 21:37:23] WARN: chain[0] - Failed to measure current voltage (attempt=3) with resp: 0x%02 0xfe
[2020/08/28 21:37:23] ERROR: driver-btm-chain.c:687 chain[1] - Voltage is different, cur=0 mV tgt=21000 mV
[2020/08/28 21:37:23] ERROR: driver-btm-chain.c:471 chain[1] - Failed to set start up voltage
[2020/08/28 21:37:23] INFO: chain[1] - Shutting down the chain
[2020/08/28 21:37:23] ERROR: driver-btm-base.c:361 chain[1] - Initialization failed
[2020/08/28 21:37:24] ERROR: driver-btm-chain.c:687 chain[0] - Voltage is different, cur=0 mV tgt=21000 mV
[2020/08/28 21:37:24] ERROR: driver-btm-chain.c:471 chain[0] - Failed to set start up voltage
[2020/08/28 21:37:24] INFO: chain[0] - Shutting down the chain
[2020/08/28 21:37:24] ERROR: driver-btm-base.c:361 chain[0] - Initialization failed
[2020/08/28 21:37:24] WARN: All chains are disabled or disconnected
[2020/08/28 21:37:24] ERROR: driver-btm-base.c:2156 Failed to initialize hash boards
[2020/08/28 21:37:24] INFO: Shutting down the miner
[2020/08/28 21:37:24] INFO: Stopping FPGA queue
[2020/08/28 21:37:24] INFO: chain[0] - Shutting down the chain
[2020/08/28 21:37:24] INFO: chain[1] - Shutting down the chain
[2020/08/28 21:37:24] INFO: chain[2] - Shutting down the chain
[2020/08/28 21:37:24] INFO: Power OFF
Title: Re: S17 Pro no longer hashing. Bad ASICs ?
Post by: mikeywith on August 29, 2020, 11:45:05 PM
The custom firmware made no difference, it also shows that all three hash boards are dead and showing 0 Asics, with that being a possibility I would most likely still bet against it assuming all three boards "failed" simultaneously, the odds of that happening are pretty slim.
At this point I think a little history about this miner will be handy, most importantly, was this miner hashing fine with all 3 boards with default hashrate of 50-54terahash/s?
If the answer is yes, then I still find it hard to believe that all 3 hash boards went down, if it was hashing at third the hashrate / with one hash board, then chances that that board was toasted as well.
Just so we don't go back and forth on the same thing, since I don't know the answer, if your answer is "yes" to the above question, then here are the possibilities.
1- You got another faulty PSU.
2- You installed the PSU incorrectly, not tightening the screws well enough for forgetting to firmly insert the data/ribbon cables from the control board to the hash boards.
3- Your voltage is out of the 200-240v range.
If your answer is "No", then well, that's just a bad luck, losing a board on these S17 series is nothing out of the ordinary.
Title: Re: S17 Pro no longer hashing. Bad ASICs ?
Post by: philipma1957 on August 29, 2020, 11:54:54 PM
I think you should fully disconnect two boards.
try 1 board in all three spots.
see if it fails in all three spots.
after you try the one board in all three spots.
get back to us.
your other two board should be completely outside the machine.
Title: Re: S17 Pro no longer hashing. Bad ASICs ?
Post by: agilmore on November 30, 2020, 05:20:46 AM
[...]
I ran this test and still no asics were reported. I ran the test on a second board just in case that was a bad board. Same results. How do I know that the control board isn't bad ?
Title: Re: S17 Pro no longer hashing. Bad ASICs ?
Post by: philipma1957 on November 30, 2020, 01:30:08 PM
fail order likelihood
1) hash boards
2) psu
3) controller
If you did what I said it points to a dead psu a little more than a dead hash board.
How to test if it is not the psu?
pull a working psu from another unit that must be working.
Take the psu from the dead unit and put it to the good unit.
if the good unit works than the suspect psu is good.
I am pretty sure if you do this the good unit will not work.
that brings use back to is it a dead controller?
take the dead or suspect unit pull the controller swap it to the working unit.
if the working unit still works.
it means your psu's and your controllers are all good.
what is left? the hash boards.
Title: Re: S17 Pro no longer hashing. Bad ASICs ?
Post by: agilmore on November 30, 2020, 03:17:19 PM
Thanks for the response. Here are answers to your suggestions:
1) I only have 1 system
2) I replaced the PSU a few months ago. Granted, I bought one off of ebay. I guess it could be faulty, but I'm giving the seller the benefit of the doubt given his feedback rating.
Is there something that I can find in a log that can point to the controller or hash board ?
Title: Re: S17 Pro no longer hashing. Bad ASICs ?
Post by: philipma1957 on November 30, 2020, 03:29:24 PM
Okay where are you ?
Tell me you are in NJ, USA I can help.
As I am in that state.
If you are not close by
I may have a controller in my spare parts.
I do have a psu.
I read your log I think the problem is your psu.
Title: Re: S17 Pro no longer hashing. Bad ASICs ?
Post by: agilmore on November 30, 2020, 07:55:07 PM
I'm in NC. Can I send you my PSUs to test? Or can you send me a working one and I'll pay for shipping?
Title: Re: S17 Pro no longer hashing. Bad ASICs ?
Post by: mikeywith on December 01, 2020, 09:04:23 PM
Is there something that I can find in a log that can point to the controller or hash board ?
The hashboard is easy to spot, most of the time it will show 0 Asics or anything below the correct chip number, but it's almost impossible to troubleshoot a bad control board using only the kernel log, the only way would be the obvious things fro ethernet LEDs, miner's LEDs or its ability to load/unload a certain firmware, those will be your positive, but lack of all those things aren't a confirmation of the control board's health, so it's a bit tricky here. Usually, for those who have 2 miners, it would be a matter of a simple swap to confirm, but since you don't have that, then you would do the rational thing and assume that the PSU is bad, I don't have exact failure figures but it's at least 9 out of 10 times whereby the PSU is bad and not the control board, it might be the control board after all, but what are the odds?
Title: Re: S17 Pro no longer hashing. Bad ASICs ?
Post by: philipma1957 on December 01, 2020, 09:08:42 PM
I'm in NC. Can I send you my PSUs to test? Or can you send me a working one and I'll pay for shipping?
We have a repair guy we use that is located in NC. Give me 5 minutes to find the link. He has been a godsend with psu replacement. I used https://hmtech.co/ (919) 283-2715 they do repair m20s they sold me a m20s psu a p21 they also have bitmain parts and repairs. Tell them philipma1957 of bitcointalk linked you. I get zero money for this. But I like that they know I send them people. He has to be close to you as it is the same state. He has helped 4 or 5 of us with psu replacements. yeah they seem to have really dropped in their service . I won't be using them to get a m30s. I used https://hmtech.co/ (919) 283-2715 they do repair m20s they sold me a m20s psu a p21 ASIC Repair : Basic / Advanced
Bitmain
$300 / $400
S17 & T17
Whatsminer
$300 / $400
M20s & M21S
Innosilicon
$300 / $400
T3 series
ASIC PSU's
Innosilicon T3 series PSU
$200
New
Whatspower P21 PSU
$200
New
Innosilicon T2 double fan series & T3 PSU
$200
New
good luck.
Title: Re: S17 Pro no longer hashing. Bad ASICs ?
Post by: agilmore on December 02, 2020, 06:20:11 AM
Thanks. They're only about 30min away from me.
Title: Re: S17 Pro no longer hashing. Bad ASICs ?
Post by: philipma1957 on December 03, 2020, 04:28:42 PM
Thanks. They're only about 30min away from me.
Please follow up and let us know how they did. So far they have helped more than 3 or 4 here on Bitcointalk. Lets hope you can add a good review. Now that coin is higher good repair guys are important.
Title: Re: S17 Pro no longer hashing. Bad ASICs ?
Post by: agilmore on February 03, 2021, 05:48:56 AM
Will do. I dropped it off yesterday. They'll get back to me in a couple of days.
So they've finally finished with the system. 1 board was repairable and the other 2 weren't . They took it apart and after several weeks, finally gave up. Any ideas on where i can find a couple of used hashboards so that the system isn't virtually useless?
Title: Re: S17 Pro no longer hashing. Bad ASICs ?
Post by: wndsnb on February 03, 2021, 01:53:44 PM
Sorry to hear that, did they say what was wrong with the 2 bad boards?
Don't think you are going to have much luck finding used hashboards, if someone was selling them they'd probably want more for 2 hashboards than what you could buy a full 2nd hand miner for.
Also, if using factory firmware they are not really swappable. They match up the hashboards at the factory and then write settings into the eeprom, if the settings don't match up between the hashboards factory firmware just refuses to start. Aftermarket firmware just ignores all the settings from the hashboard, so it will work in more situations.
Title: Re: S17 Pro no longer hashing. Bad ASICs ?
Post by: NoKeyboard-BTW on February 06, 2021, 11:49:43 PM
I had the same problems on a Pro recently as well with results below that might be useful to others in the future. Boost circuit took me by surprise. That said, I'm also looking for 2 boards now. I'm under the impression 50TH is not interchangeable with 53TH. All I could tell is the difference in power draw.
Hashboard 1-
YDFTYHUAIJDAH0K81
Temp sensors 2 & 4 replaced.
Reflowed Chips
Boost circuit failed board is unrepairable.
Hashboard 2-
YDFTYHUAIJDAH0K82
Temp sensors 2 & 4 replaced.
Reflowed Chips
Hashboard 3-
YDFTYHUAIJDAH0K83
Reflowed chip
5 or more ASICs failed board is unrepairable.
Title: Re: S17 Pro no longer hashing. Bad ASICs ?
Post by: wndsnb on February 07, 2021, 12:55:55 AM
5 or more ASICs I can understand, but not sure why a boost circuit failure would make a board "unrepairable".
Even though they are unrepairable I'd still be interested in your dead hashboards. Even if I can't repair them, I can still use them for spare parts.
If one of you is willing to sell the other your working hashboard, I'd also be interested in the PSU, case, and control board left over.
Title: Re: S17 Pro no longer hashing. Bad ASICs ?
Post by: NoKeyboard-BTW on February 07, 2021, 01:44:53 AM
wndsnd, I haven't received the miner back yet to see the damage on the screen myself but will keep you posted. Good idea though. They said the boost circuit is in-between "not worth their time" and "beyond their capabilities". They are certified Bitmain techs. so who knows.
agilemore, I'd be interested in your working board if you are willing to sell it.
Title: Re: S17 Pro no longer hashing. Bad ASICs ?
Post by: wndsnb on February 07, 2021, 03:46:24 AM
I guess it isn't very surprising given the rates they are charging. On average they probably can't spend more than 2 or 3 hours on a hashboard to break even.
I think the Bitmain training is probably pretty specific, focusing on the most likely issues. If the problem doesn't fall into the scope of their training, there isn't really any information out there on it. I've been going off the Bitmain repair manuals and then filling in the missing information by reverse-engineering the boards. Pretty time consuming ...
Title: Re: S17 Pro no longer hashing. Bad ASICs ?
Post by: mikeywith on February 07, 2021, 07:01:29 PM
I'm under the impression 50TH is not interchangeable with 53TH. All I could tell is the difference in power draw.
I have reasons to believe that this isn't the case, just to stay on topic I rather not mention them here, but I can tell you one thing, it's probably the product ID difference, The 17 pro version has like 3 different product id's, not sure what the reference but it seems like it does reference a certain format in the hex stored on some microchip on each of those hash boards. So if you mix two boards with different product id's the control board will refuse to turn on both of them, you could check the kernel log and you will find the product ID represented in something like so 2021-02-05 14:12:04 driver-btm-api.c:589:get_product_id: product_id[0] = 0
2021-02-05 14:12:04 driver-btm-api.c:589:get_product_id: product_id[1] = 0
2021-02-05 14:12:04 driver-btm-api.c:589:get_product_id: product_id[2] = 0 Or/And hexadecimal values on the PIC fw version: 2021-02-05 14:12:08 board.c:40:jump_and_app_check_restore_pic: Check chain[0] PIC fw version=0xb9
2021-02-05 14:12:11 board.c:40:jump_and_app_check_restore_pic: Check chain[1] PIC fw version=0xb9
2021-02-05 14:12:15 board.c:40:jump_and_app_check_restore_pic: Check chain[2] PIC fw version=0xb9 If the hash boards have any different values, then they need some work done before they can mine using the same control board.
Title: Re: S17 Pro no longer hashing. Bad ASICs ?
Post by: NoKeyboard-BTW on February 08, 2021, 08:45:13 PM
wdsnb, I agree, they probably have a massive backlog as well. With 6 actual technicians servicing the US I shouldn't be surprised it's taken since mid December to get this diagnosis and repair. Totally time-consuming I can just imagine the gaps you have to fill in but you know they work and your not under the corporate-type time crunch. Would you entertain repairs and perhaps complete overhauls that improve the factory build quality to boards? I tried to contact agilmore but he's not accepting messages from newbs. Perhaps you would have better luck. :-\
This is great information and clears up a lot of confusion mikeywith. I think this would be helpful seeing as replacement parts for the 17 series are becoming rarer and working hash boards are few and far between now. It's what I was afraid of and far beyond my skill set. Maybe a tutorial soon? :)
NKBTW
Title: Re: S17 Pro no longer hashing. Bad ASICs ?
Post by: mikeywith on February 09, 2021, 08:21:46 AM
It's what I was afraid of and far beyond my skill set. Maybe a tutorial soon? :)
A tutorial on what exactly? if we are talking about mix and match of hash boards I believe what I posted earlier on is enough of a "tutorial", if you are talking about something else, please explain. By the way, do you really not have a keyboard? ::)
Title: Re: S17 Pro no longer hashing. Bad ASICs ?
Post by: NoKeyboard-BTW on February 09, 2021, 08:38:16 PM
You mentioned that if you plan to mix and match boards they will need some work and seems like one would have to undergo some editing so that the control board recognizes the correct product id's. I'm interested to know if this work can be performed without specialty equipment.
Sometimes it's no brain and sometimes it's no keyboard, depends on the day :D
Title: Re: S17 Pro no longer hashing. Bad ASICs ?
Post by: mikeywith on February 09, 2021, 11:38:49 PM
You mentioned that if you plan to mix and match boards they will need some work and seems like one would have to undergo some editing so that the control board recognizes the correct product id's. I'm interested to know if this work can be performed without specialty equipment.
Well you are going to need some special device for that, you are going to write on a microchip somewhere on those hash boards, the easiest way would be using zuesbtc tool > https://www.zeusbtc.com/ASIC-Miner-Repair/Parts-Tools-Details.asp?ID=236, it's plug and play and easy to use, however, it's kind of expensive. The other alternative which I believe will achieve the same results would be using pickit 3, thierry4wd explained the use of that tool in great detail, and despite the fact that his topic (https://bitcointalk.org/index.php?topic=5032987.0) talks only about fixing T9+ in an unrelated subject to the code/id difference, I believe by extracting the hex from one board and writing it on the other one will make the latter have the same product id and thus will be able to function on the same control board. Keep in mind while the second option is A LOT cheaper but it has yet to be tested, the first option has been tested and works perfectly, but it's a matter of 250$++ difference.
Title: Re: S17 Pro no longer hashing. Bad ASICs ?
Post by: wndsnb on February 10, 2021, 12:05:00 AM
Extracting the pic firmware from a hashboard with the pickit it pretty easy. I've done it and can verify it works. No need to pay extra for the zeus tool if you have the time to spend 20 minutes to do an internet search and play with the pickit software.
The repair manuals on the zeus website describes how to program the pic with the pickit, all you need to do is find the option to read the firmware in the pickit software.
Title: Re: S17 Pro no longer hashing. Bad ASICs ?
Post by: NoKeyboard-BTW on February 10, 2021, 09:00:14 PM
The Pickit seems like the smartest choice here for a small scale operation and rare use situations. Also, thierry4wd's post provides a good reference to get things off the ground along with information in this thread. Would you recommend the newer Pickit4?
Title: Re: S17 Pro no longer hashing. Bad ASICs ?
Post by: mikeywith on February 11, 2021, 01:31:56 PM
The Pickit seems like the smartest choice here for a small scale operation and rare use situations. Also, thierry4wd's post provides a good reference to get things off the ground along with information in this thread. Would you recommend the newer Pickit4?
It's more than likely going to do the job just fine, but the price is more than double, the Pickit 4 has more features than the 3 version which you probably will never use, I'd say stick to Pickit3.
Title: Re: S17 Pro no longer hashing. Bad ASICs ?
Post by: agilmore on February 21, 2021, 10:04:20 PM
They basically told me that these were the worse units that bitmain produced and has had a ton of issues. The solder or whatever compound thats used to attach the chips to the board basically melted away.
Title: Re: S17 Pro no longer hashing. Bad ASICs ?
Post by: NoKeyboard-BTW on February 22, 2021, 12:11:30 AM
Agilmore, x17 could be considered the worst in terms of quality and depend on a lot of luck. Would you entertain selling your working hashboard? Wndsnb mentioned he'd also be interested in the dead hashboards, PSU, case, and control board left over. Appreciate the consideration.
Title: Re: S17 Pro no longer hashing. Bad ASICs ?
Post by: mikeywith on February 22, 2021, 12:22:21 AM
They basically told me that these were the worse units that bitmain produced and has had a ton of issues.
I have been saying this for months or perhaps years on this forum, I kept mentioning how bad the 17 series mining gears are on every occasion I saw possible, I did that to the extreme that someone accused me of "fud", I can't blame them, it did sound like I own a Bitmain competitor company. :'( Phill is probably the only one I know who didn't have a high failure rate, the vast majority of people I know had well over 30% failure rate, some are above 50% in less than a year, this is so unfortunate given that most of us bought those gears when BTC price was at or below 10k. It's a lesson learned, I hope more people become aware of that, if you don't have the tools and skills needed to fix these gears DO NOT buy them.
Title: Re: S17 Pro no longer hashing. Bad ASICs ?
Post by: wndsnb on February 22, 2021, 01:19:33 AM
Phill is probably the only one I know who didn't have a high failure rate, the vast majority of people I know had well over 30% failure rate, some are above 50% in less than a year, this is so unfortunate given that most of us bought those gears when BTC price was at or below 10k.
I think it was certain batches, or maybe miners made at certain facilities. I have 7 S17 pros from Malaysia, and 2 out of 7 failed in less than a year. But I also have 10 S17s and 3 S17 pros from China, and I haven't had a single one go down. Even if you do have the tools and skills to repair them, many times there are just too many issues to make it worth the effort. Many of these miners have flaky connections everywhere.. so you fix one issue and it runs for a few days until another issue springs up. Not worth the repair when it becomes a full time job to keep a single miner going...
Title: Re: S17 Pro no longer hashing. Bad ASICs ?
Post by: danieleither on February 22, 2021, 02:11:23 AM
Same here, running 24 x S17e and 12 x T17+ purchased around May / June 2020 and not had one single problem with them. I do have some older 2019 T17+ (that I bought used) and those are now dying though... I also recently purchased 20 x S17 Pro from a Chinese supplier who insists they were working 100% however 4 had bad hashboards on arrival, and now I think there are 12 dead hashboards in total :\
Also running 35 x S19 95t for around 7 months now and no problems at all.
Title: Re: S17 Pro no longer hashing. Bad ASICs ?
Post by: mikeywith on February 22, 2021, 06:48:02 PM
True, the recent batches are of better quality; also the ones that ship from Malaysia are worse according to what most people reported, however, the overall quality of all batches is combined is terrible, I bought those gears throughout the time of their release, as early as the second batch of the S17 (most of them for my clients), and nobody is really happy with any of them except for the s17 pro version which seems to be an expectation, not all great but a lot better than the rest. On the other hand, we have some Whatsminers from the same bitmain 17 series era that my clients reported 0 failure rate on, some are over 2 years old, imagine for 2 years, sounds like S9 all over again. With that being said, if you have a low failure rate, you should be thankful really as this is the unusual of how they are, you guys have decent luck I envy you. :'( Even if you do have the tools and skills to repair them, many times there are just too many issues to make it worth the effort. Many of these miners have flaky connections everywhere.. so you fix one issue and it runs for a few days until another issue springs up. Not worth the repair when it becomes a full time job to keep a single miner going...
Couldn't agree more, especially when you see Avalon and Whatsminer's owners be like "What does repair mean" ???, I know everyone has a different view on the subject, given what I think is a large enough sample size I find it very risky to buy any of the 17 series especially when other options are around, so far people are reporting good results with their S19s and T19s, some minor issues with their PSUs but nothing all that serious, my plan is to migrate to Whatsminer, selling my Bitmain gears for premium during this bull cycle and rebuying cheap M20s and M30s when things cool off little sounds like a great plan for the following years. I wish I could keep all the S9s I have because nothing comes close to their stability, but these gears are getting too old, I just realized some of them are as old as 4 years.
Title: Re: S17 Pro no longer hashing. Bad ASICs ?
Post by: agilmore on February 26, 2021, 11:51:36 PM
I've been seeing multiple sellers that advertise using a mixed collection boards for their s17s. I was under the impression that this isn't possible. I guess it is. Any idea where i can find some boards to try and bring my system completely back? Its currently running with 1 board at 17TH-20TH.
Title: Re: S17 Pro no longer hashing. Bad ASICs ?
Post by: NoKeyboard-BTW on February 27, 2021, 01:12:12 PM
Along with what mikeywith has described in this thread I spoke to a knowledgeable person in mining on TG they say if you run Vnish, interchangeability between boards (50/53/56) shouldn't be an issue. I have my doubts, so I'd recommend buying a PicKit just in case you do find a pro board.
Title: Re: S17 Pro no longer hashing. Bad ASICs ?
Post by: wndsnb on February 27, 2021, 01:30:20 PM
I have mixed boards a few times with S17s running vnish and have not had any issues.
To run stock firmware, I believe both the Pic program for all the boards need to be identical and the tuning data stored in the eeprom on the hashboard needs to be compatible. The pickit does not program the eeprom, that is a chip separate from the pic. I believe the tool from Zeus writes the eeprom, not the pic. It lets you read the eeprom settings from one board, and write them to another.
My understanding is that the different pic program revisions require different communications api, and at least in the stock firmware, it only supports one api at a time. That same limitation might also apply to vnish.
Title: Re: S17 Pro no longer hashing. Bad ASICs ?
Post by: NoKeyboard-BTW on February 27, 2021, 02:24:17 PM
Promising to hear there is some real success mixing boards under Vnish. I think the Asic Repair Center test jig also has the ability to work with the EEPROM...or just EEPROM flashing.
Title: Re: S17 Pro no longer hashing. Bad ASICs ?
Post by: wndsnb on February 27, 2021, 02:29:28 PM
Yes, the Asic Repair tester can burn the eeprom if you buy that option, but I don't think you can tell it what settings to write. So it just writes some default settings. If the hashboard doesn't work well at those settings then the stock firmware will work, but not very well. I haven't asked if there is a way to change the frequency and voltage setting that it writes, haven't needed it since the miners I've been repairing are pretty much all using vnish already.
|
