T17/S17 malfunction: cases, solutions, remedies, RMA history

[mikeywith]

Whoah, so running a big farm like that easily becomes your full time job if you can also do repairing yourself

I think the type of mining gears running at the farm will determine whether this becomes feasible or not, if the farm is full of 17 series gears, well, then probably a dozen technicians can do that full-time, if it's other robust gears, the amount of work needed could be extremely low.

If I charged enough to make it worth my time I'd be even more expensive than the overpriced services already listed...

Makes sense.

No, unfortunately not. I guess it could be the soldier or a burnt chip, although, could there be a log of "find 30 asic" even with a burnt chip? Seems kinda contradictory.

If the chips are burnt then they are burnt, the kernel log won't show 30 asics at times and 0 in the others, however, if it's just a bad solder connection then it's pretty normal for the hash board to show 30 asics and then maybe 24 and then 0, I personally managed to fix a few hash boards by freezing them in the freezer, the freezing did something to that solder joint and fixed it, so ya, it's pretty normal for that to happen.

[1714991688]

1714991688

[1714991688]

1714991688

[1714991688]

1714991688

[1714991688]

1714991688

[1714991688]

1714991688

[flashgear]

Sooo bringing in $50k worth of T17's 42Th/s is starting to look/sound like a bad idea....

Am I in for a world of pain? - No, I haven't bought them yet.

[wndsnb]

It's a gamble. I think the quality control just wasn't good enough for all these 17 series miners to get a reliably good product, but it seems like some batches were fine, others were horrible. I have 10 S17s that came directly from Bitmain in one batch and haven't had a single one go down. Been running for nearly 2 years. Got 7 s17 pros in another batch from Malaysia and had issues with 3 out of 7 in under a year.

So could go either way. With used miners, if they've been solidly running with no issues they may be good and the original owners were the ones that took the risk. Or it could be every single miner they are selling had issues and it's just a matter of time before they start failing.

I'd just go into it assuming 25% of the hashboards will die. Make sure the #s make sense with that assumption. Consolidate working hashboards into fully working miners and either sell the bad boards for parts or see if you can find a repair shop.

[robertpaulsen]

On another note, I plan to underclock my T17 so it uses less power and makes less noise so it will be more acceptable for home mining. When I underlocked it and set power consumption to around 1200W (half of the original), I noticed that the PSU (APW9) is barely getting any heat but the fans are still pretty loud. Is there any way to slow down these small fans? Also, is there any heat sensor in the APW9? I don't wanna mess with it if it will make it unsafe, like fire hazard.

[thierry4wd]

Yes, without any problem, just swap original fan by slower fan, i make 8000trs fan, and run good !!! (underclock to, on 35 th)

[usrzero01]

Hello guys, just had a small rig of gpus since 2018.  Have a opportunity to buy a couple of s17 for great price. But doing some research I seen they have a fire hazard, heatsink problems, weak psu, and faulty fans. my buddy said stay away.

If i decided to get them and wanted to overclock them what can I do to reduce risk? Get new power supply, new fan, new heatsink? I have background in computers from the 90s, i put together and taken apart many pc, cpus, heatsinks, fixed or upgraded everything at one time or another over the years.

Also for overclocking i was wondering what firmwares are legit? (ascii.to (the moon))?  I like to hear good and bad from actual users to make informed decision.
 
Thanks guys.

[mikeywith]

But doing some research I seen they have a fire hazard, heatsink problems, weak psu, and faulty fans. my buddy said stay away.

If i decided to get them and wanted to overclock them

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

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

Keep these gears as cool as possible, forget the overclocking thing all together, that's my advice.

[usrzero01]

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

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

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

If i had 2 s17 overclocked i would make back my investment in about 2 months, i have free power. So, that is very alluring, but 30% failure rate is very off putting. still undecided....

[mikeywith]

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

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

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

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

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

[wndsnb]

I agree with mikeywith about the overclocking. The hashboard layout, case, and fans were not built to handle the 3000W required to run these at 70TH or more. The temperature of only 4 out of the 48 ASICs on each hashboard is monitored. So you can very easily get into a situation where one of the non-monitored ASICs that is less efficient or has a poorly attached heatsink, gets hot enough to melt its solder connections, short out a bunch of high power connections, and cause unrepairable damage.

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

Also, not every S17 will overclock that much anyway.

[flashgear]

Are the S17 Pro's just as bad as the other 17 range?

[wndsnb]

Are the S17 Pro's just as bad as the other 17 range?

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

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

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

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

The S17e was a completely different beast, different chip (1396), and an insane number of them on a single board, 135 chips per board. I took a look at a dead one for my host once and after seeing it in person I just sent it back to him. Looked like a complete nightmare to work on. But that was the only one I saw, and I didn't even take a chip off, so I don't really have any thoughts on them other than I don't want to mess with them.

[niko83]

You can use something like https://www.amazon.com/Arctic-Silver-Premium-Adhesive-ASTA-7G/dp/B0087X7262, or use the black glue from the same website you got the tool, adding more solder to the existing isn't a good idea, you should clean the chip's surface and then start fresh, ensure that the amount of solder paste is equally even across the whole chip.

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

Do you know if that glue gets soft when attacked with a heat gun, like the black glue Bitmain uses does?

[BitMaxz]

Do you know if that glue gets soft when attacked with a heat gun, like the black glue Bitmain uses does?

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

So more than that it can soften the glue if you set it to higher than temp 150c.

[minefarmbuy]

Any reports on the thermal adhesive working? Have a unit with about 8 heatsinks fell off and wondering if results are good with the artic silver as my soldering skills are pretty rudimentary and don't want to risk more "transit damage" for more skilled soldering repair. 

[wndsnb]

I've seen several posts about people asking about using thermal adhesives on these but never saw a post from anyone that had done it and had success or not. The solder used is about 10X better at transferring heat compared to arctic silver, so there will be a larger temperature drop between the heatsink and chip when using the adhesive, which means the chip will run hotter.

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

About soldering the heastinks back on, many times it is not possible to re-attach. Most of the time I've seen heasinks fall off it is because the copper plating on the top of the chip has delaminated. The copper is what the solder adheres to, and without it, you can't make a good connection. So I've found most of the time the chip needs to be replaced. If you post some pictures of the chips with missing heatsinks, I may be able to determine if it is possible to re-solder them.

[DwarfNo3]

Hello all!

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

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

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

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

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

Regards,

[wndsnb]

Post a kernel log and we might be able to give some good advice.

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

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

No sure what you mean by metal brackets ... If you mean the busbars that connect the main power to the hashboards .... then yeah, not gonna work too well without those attached.

[DwarfNo3]

Thank you wndsnb for your reply,

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

Here is the kernel log with 3 hashboards connected:

Code:

Booting Linux on physical CPU 0x0
Linux version 4.6.0-xilinx-gff8137b-dirty (lzq@armdev2) (gcc version 4.8.3 20140320 (prerelease) (Sourcery CodeBench Lite 2014.05-23) ) #25 SMP PREEMPT Fri Nov 23 15:30:52 CST 2018
CPU: ARMv7 Processor [413fc090] revision 0 (ARMv7), cr=18c5387d
CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
Machine model: Xilinx Zynq
cma: Reserved 16 MiB at 0x0e000000
Memory policy: Data cache writealloc
On node 0 totalpages: 61440
free_area_init_node: node 0, pgdat c0b39280, node_mem_map cde10000
  Normal zone: 480 pages used for memmap
  Normal zone: 0 pages reserved
  Normal zone: 61440 pages, LIFO batch:15
percpu: Embedded 12 pages/cpu @cddf1000 s19776 r8192 d21184 u49152
pcpu-alloc: s19776 r8192 d21184 u49152 alloc=12*4096
pcpu-alloc: [0] 0 [0] 1 
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 60960
Kernel command line: mem=240M console=ttyPS0,115200 ramdisk_size=33554432 root=/dev/ram rw earlyprintk
PID hash table entries: 1024 (order: 0, 4096 bytes)
Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
Memory: 203752K/245760K available (6345K kernel code, 231K rwdata, 1896K rodata, 1024K init, 223K bss, 25624K reserved, 16384K cma-reserved, 0K highmem)
Virtual kernel memory layout:
    vector  : 0xffff0000 - 0xffff1000   (   4 kB)
    fixmap  : 0xffc00000 - 0xfff00000   (3072 kB)
    vmalloc : 0xcf800000 - 0xff800000   ( 768 MB)
    lowmem  : 0xc0000000 - 0xcf000000   ( 240 MB)
    pkmap   : 0xbfe00000 - 0xc0000000   (   2 MB)
    modules : 0xbf000000 - 0xbfe00000   (  14 MB)
      .text : 0xc0008000 - 0xc090c424   (9234 kB)
      .init : 0xc0a00000 - 0xc0b00000   (1024 kB)
      .data : 0xc0b00000 - 0xc0b39fe0   ( 232 kB)
       .bss : 0xc0b39fe0 - 0xc0b71c28   ( 224 kB)
Preemptible hierarchical RCU implementation.
	Build-time adjustment of leaf fanout to 32.
	RCU restricting CPUs from NR_CPUS=4 to nr_cpu_ids=2.
RCU: Adjusting geometry for rcu_fanout_leaf=32, nr_cpu_ids=2
NR_IRQS:16 nr_irqs:16 16
efuse mapped to cf800000
ps7-slcr mapped to cf802000
L2C: platform modifies aux control register: 0x72360000 -> 0x72760000
L2C: DT/platform modifies aux control register: 0x72360000 -> 0x72760000
L2C-310 erratum 769419 enabled
L2C-310 enabling early BRESP for Cortex-A9
L2C-310 full line of zeros enabled for Cortex-A9
L2C-310 ID prefetch enabled, offset 1 lines
L2C-310 dynamic clock gating enabled, standby mode enabled
L2C-310 cache controller enabled, 8 ways, 512 kB
L2C-310: CACHE_ID 0x410000c8, AUX_CTRL 0x76760001
zynq_clock_init: clkc starts at cf802100
Zynq clock init
sched_clock: 64 bits at 333MHz, resolution 3ns, wraps every 4398046511103ns
clocksource: arm_global_timer: mask: 0xffffffffffffffff max_cycles: 0x4ce07af025, max_idle_ns: 440795209040 ns
Switching to timer-based delay loop, resolution 3ns
clocksource: ttc_clocksource: mask: 0xffff max_cycles: 0xffff, max_idle_ns: 537538477 ns
ps7-ttc #0 at cf80a000, irq=18
Console: colour dummy device 80x30
Calibrating delay loop (skipped), value calculated using timer frequency.. 666.66 BogoMIPS (lpj=3333333)
pid_max: default: 32768 minimum: 301
Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
CPU: Testing write buffer coherency: ok
CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
Setting up static identity map for 0x100000 - 0x100058
CPU1: failed to boot: -1
Brought up 1 CPUs
SMP: Total of 1 processors activated (666.66 BogoMIPS).
CPU: All CPU(s) started in SVC mode.
devtmpfs: initialized
VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4
clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
pinctrl core: initialized pinctrl subsystem
NET: Registered protocol family 16
DMA: preallocated 256 KiB pool for atomic coherent allocations
cpuidle: using governor menu
hw-breakpoint: found 5 (+1 reserved) breakpoint and 1 watchpoint registers.
hw-breakpoint: maximum watchpoint size is 4 bytes.
zynq-ocm f800c000.ps7-ocmc: ZYNQ OCM pool: 256 KiB @ 0xcf880000
vgaarb: loaded
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
media: Linux media interface: v0.10
Linux video capture interface: v2.00
pps_core: LinuxPPS API ver. 1 registered
pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <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: 12584K (cceb7000 - cdb01000)
hw perfevents: enabled with armv7_cortex_a9 PMU driver, 7 counters available
futex hash table entries: 512 (order: 3, 32768 bytes)
workingset: timestamp_bits=28 max_order=16 bucket_order=0
jffs2: version 2.2. (NAND) (SUMMARY)  © 2001-2006 Red Hat, Inc.
io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered (default)
dma-pl330 f8003000.ps7-dma: Loaded driver for PL330 DMAC-241330
dma-pl330 f8003000.ps7-dma: 	DBUFF-128x8bytes Num_Chans-8 Num_Peri-4 Num_Events-16
e0000000.serial: ttyPS0 at MMIO 0xe0000000 (irq = 158, base_baud = 6249999) is a xuartps
console [ttyPS0] enabled
xdevcfg f8007000.ps7-dev-cfg: ioremap 0xf8007000 to cf86e000
[drm] Initialized drm 1.1.0 20060810
brd: module loaded
loop: module loaded
CAN device driver interface
gpiod_set_value: invalid GPIO
libphy: MACB_mii_bus: probed
macb e000b000.ethernet eth0: Cadence GEM rev 0x00020118 at 0xe000b000 irq 31 (00:0a:35:00:00:00)
Generic PHY e000b000.etherne:00: attached PHY driver [Generic PHY] (mii_bus:phy_addr=e000b000.etherne:00, irq=-1)
e1000e: Intel(R) PRO/1000 Network Driver - 3.2.6-k
e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
ehci-pci: EHCI PCI platform driver
usbcore: registered new interface driver usb-storage
mousedev: PS/2 mouse device common for all mice
i2c /dev entries driver
Xilinx Zynq CpuIdle Driver started
sdhci: Secure Digital Host Controller Interface driver
sdhci: Copyright(c) Pierre Ossman
sdhci-pltfm: SDHCI platform and OF driver helper
mmc0: SDHCI controller on e0100000.ps7-sdio [e0100000.ps7-sdio] using ADMA
ledtrig-cpu: registered to indicate activity on CPUs
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
nand: device found, Manufacturer ID: 0x2c, Chip ID: 0xda
nand: Micron MT29F2G08ABAEAWP
nand: 256 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 64
nand: WARNING: pl35x-nand: the ECC used on your system is too weak compared to the one required by the NAND chip
Bad block table found at page 131008, version 0x01
Bad block table found at page 130944, version 0x01
6 ofpart partitions found on MTD device pl35x-nand
Creating 6 MTD partitions on "pl35x-nand":
0x000000000000-0x000002800000 : "BOOT.bin-env-dts-kernel"
0x000002800000-0x000004800000 : "ramfs"
0x000004800000-0x000005000000 : "configs"
0x000005000000-0x000006000000 : "reserve"
0x000006000000-0x000008000000 : "ramfs-bak"
0x000008000000-0x000010000000 : "reserve1"
NET: Registered protocol family 10
sit: IPv6 over IPv4 tunneling driver
NET: Registered protocol family 17
can: controller area network core (rev 20120528 abi 9)
NET: Registered protocol family 29
can: raw protocol (rev 20120528)
can: broadcast manager protocol (rev 20120528 t)
can: netlink gateway (rev 20130117) max_hops=1
zynq_pm_ioremap: no compatible node found for 'xlnx,zynq-ddrc-a05'
zynq_pm_late_init: Unable to map DDRC IO memory.
Registering SWP/SWPB emulation handler
hctosys: unable to open rtc device (rtc0)
ALSA device list:
  No soundcards found.
RAMDISK: gzip image found at block 0
EXT4-fs (ram0): couldn't mount as ext3 due to feature incompatibilities
EXT4-fs (ram0): mounted filesystem without journal. Opts: (null)
VFS: Mounted root (ext4 filesystem) on device 1:0.
devtmpfs: mounted
Freeing unused kernel memory: 1024K (c0a00000 - c0b00000)
EXT4-fs (ram0): re-mounted. Opts: block_validity,delalloc,barrier,user_xattr
random: dd urandom read with 0 bits of entropy available
ubi0: attaching mtd2
ubi0: scanning is finished
ubi0: attached mtd2 (name "configs", size 8 MiB)
ubi0: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
ubi0: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
ubi0: VID header offset: 2048 (aligned 2048), data offset: 4096
ubi0: good PEBs: 64, bad PEBs: 0, corrupted PEBs: 0
ubi0: user volume: 1, internal volumes: 1, max. volumes count: 128
ubi0: max/mean erase counter: 6/2, WL threshold: 4096, image sequence number: 638989880
ubi0: available PEBs: 0, total reserved PEBs: 64, PEBs reserved for bad PEB handling: 40
ubi0: background thread "ubi_bgt0d" started, PID 708
UBIFS (ubi0:0): background thread "ubifs_bgt0_0" started, PID 711
UBIFS (ubi0:0): recovery needed
UBIFS (ubi0:0): recovery completed
UBIFS (ubi0:0): UBIFS: mounted UBI device 0, volume 0, name "configs"
UBIFS (ubi0:0): LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
UBIFS (ubi0:0): FS size: 1396736 bytes (1 MiB, 11 LEBs), journal size 888833 bytes (0 MiB, 5 LEBs)
UBIFS (ubi0:0): reserved for root: 65970 bytes (64 KiB)
UBIFS (ubi0:0): media format: w4/r0 (latest is w4/r0), UUID 6593BA4D-00F7-467B-9E0A-A2198CBE84FF, small LPT model
ubi1: attaching mtd5
ubi1: scanning is finished
ubi1: attached mtd5 (name "reserve1", size 128 MiB)
ubi1: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
ubi1: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
ubi1: VID header offset: 2048 (aligned 2048), data offset: 4096
ubi1: good PEBs: 1020, bad PEBs: 4, corrupted PEBs: 0
ubi1: user volume: 1, internal volumes: 1, max. volumes count: 128
ubi1: max/mean erase counter: 11/7, WL threshold: 4096, image sequence number: 100324054
ubi1: available PEBs: 0, total reserved PEBs: 1020, PEBs reserved for bad PEB handling: 36
ubi1: background thread "ubi_bgt1d" started, PID 720
UBIFS (ubi1:0): background thread "ubifs_bgt1_0" started, PID 723
UBIFS (ubi1:0): recovery needed
UBIFS (ubi1:0): recovery completed
UBIFS (ubi1:0): UBIFS: mounted UBI device 1, volume 0, name "reserve1"
UBIFS (ubi1:0): LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
UBIFS (ubi1:0): FS size: 123039744 bytes (117 MiB, 969 LEBs), journal size 6221824 bytes (5 MiB, 49 LEBs)
UBIFS (ubi1:0): reserved for root: 4952683 bytes (4836 KiB)
UBIFS (ubi1:0): media format: w4/r0 (latest is w4/r0), UUID 058C0E40-6EAA-4676-9C52-F694F6D34F3B, small LPT model
IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
macb e000b000.ethernet eth0: unable to generate target frequency: 25000000 Hz
macb e000b000.ethernet eth0: link up (100/Full)
IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
In axi fpga driver!
request_mem_region OK!
AXI fpga dev virtual address is 0xcfb38000
*base_vir_addr = 0xfb013
In fpga mem driver!
request_mem_region OK!
fpga mem virtual address is 0xd2000000
random: nonblocking pool is initialized
Jan 16 07:52:23 (none) user.notice kernel: random: nonblocking pool is initialized
2022-01-16 07:47:52 driver-btm-api.c:663:init_freq_mode: This is scan-user version
2022-01-16 07:47:52 driver-btm-api.c:2028:bitmain_soc_init: opt_multi_version     = 1
2022-01-16 07:47:52 driver-btm-api.c:2029:bitmain_soc_init: opt_bitmain_ab        = 1
2022-01-16 07:47:52 driver-btm-api.c:2030:bitmain_soc_init: opt_bitmain_work_mode = 0
2022-01-16 07:47:52 driver-btm-api.c:2031:bitmain_soc_init: Miner compile time: Thu Apr 23 16:29:07 CST 2020 type: Antminer T17
2022-01-16 07:47:52 driver-btm-api.c:2032:bitmain_soc_init: commit version: 1c5be6f 2020-04-20 16:18:14, build by: lol 2020-04-23 16:35:04
2022-01-16 07:47:52 driver-btm-api.c:1844:show_sn: no SN got, please write SN to /nvdata/sn
2022-01-16 07:47:52 driver-btm-api.c:1167:miner_device_init: Detect 256MB control board of XILINX
2022-01-16 07:47:52 driver-btm-api.c:1115:init_fan_parameter: fan_eft : 0  fan_pwm : 0
2022-01-16 07:47:52 thread.c:885:create_read_nonce_reg_thread: create thread
2022-01-16 07:47:58 driver-btm-api.c:1099:init_miner_version: miner ID : 8072d5025c20885c
2022-01-16 07:47:58 driver-btm-api.c:1105:init_miner_version: FPGA Version = 0xB013
2022-01-16 07:48:00 eeprom.c:431:check_pattern_test_level: L1 board
2022-01-16 07:48:01 eeprom.c:431:check_pattern_test_level: L1 board
2022-01-16 07:48:03 eeprom.c:431:check_pattern_test_level: L1 board
2022-01-16 07:48:03 driver-btm-api.c:737:get_product_id: product_id[0] = 1
2022-01-16 07:48:03 driver-btm-api.c:737:get_product_id: product_id[1] = 1
2022-01-16 07:48:03 driver-btm-api.c:737:get_product_id: product_id[2] = 1
2022-01-16 07:48:03 driver-btm-api.c:1666:get_ccdly_opt: ccdly_opt[0] = 1
2022-01-16 07:48:03 driver-btm-api.c:1666:get_ccdly_opt: ccdly_opt[1] = 1
2022-01-16 07:48:03 driver-btm-api.c:1666:get_ccdly_opt: ccdly_opt[2] = 1
2022-01-16 07:48:03 driver-btm-api.c:1919:bitmain_board_init: g_ccdly_opt = 1
2022-01-16 07:48:03 driver-btm-api.c:676:_set_project_type: project:2
2022-01-16 07:48:03 driver-btm-api.c:706:_set_project_type: Project type: Antminer T17
2022-01-16 07:48:03 driver-btm-api.c:717:dump_pcb_bom_version: Chain [0] PCB Version: 0x0100
2022-01-16 07:48:03 driver-btm-api.c:718:dump_pcb_bom_version: Chain [0] BOM Version: 0x0100
2022-01-16 07:48:03 driver-btm-api.c:717:dump_pcb_bom_version: Chain [1] PCB Version: 0x0100
2022-01-16 07:48:03 driver-btm-api.c:718:dump_pcb_bom_version: Chain [1] BOM Version: 0x0100
2022-01-16 07:48:03 driver-btm-api.c:717:dump_pcb_bom_version: Chain [2] PCB Version: 0x0100
2022-01-16 07:48:03 driver-btm-api.c:718:dump_pcb_bom_version: Chain [2] BOM Version: 0x0100
2022-01-16 07:48:06 driver-btm-api.c:1939:bitmain_board_init: Fan check passed.
2022-01-16 07:48:08 board.c:36:jump_and_app_check_restore_pic: chain[0] PIC jump to app
2022-01-16 07:48:11 board.c:40:jump_and_app_check_restore_pic: Check chain[0] PIC fw version=0xb9
2022-01-16 07:48:13 board.c:36:jump_and_app_check_restore_pic: chain[1] PIC jump to app
2022-01-16 07:48:17 board.c:40:jump_and_app_check_restore_pic: Check chain[1] PIC fw version=0xb9
2022-01-16 07:48:18 board.c:36:jump_and_app_check_restore_pic: chain[2] PIC jump to app
2022-01-16 07:48:22 board.c:40:jump_and_app_check_restore_pic: Check chain[2] PIC fw version=0xb9
2022-01-16 07:48:22 thread.c:880:create_pic_heart_beat_thread: create thread
2022-01-16 07:48:22 power_api.c:55:power_init: power init ... 
2022-01-16 07:48:22 driver-btm-api.c:1949:bitmain_board_init: Enter 30s sleep to make sure power release finish.
2022-01-16 07:48:22 power_api.c:46:power_off: init gpio907
2022-01-16 07:48:54 power_api.c:232:set_iic_power_to_highest_voltage: setting to voltage: 17.00 ...
2022-01-16 07:49:00 power_api.c:124:check_voltage_multi: retry time: 0
2022-01-16 07:49:01 power_api.c:86:get_average_voltage: chain[0], voltage is: 0.061230 
2022-01-16 07:49:03 power_api.c:86:get_average_voltage: chain[1], voltage is: 22.398105 
2022-01-16 07:49:05 power_api.c:86:get_average_voltage: chain[2], voltage is: 16.966963 
2022-01-16 07:49:05 power_api.c:97:get_average_voltage: aveage voltage is: 13.142099 
2022-01-16 07:49:05 power_api.c:110:check_voltage: target_vol = 17.00, actural_vol = 13.14, more than 1.0v diff.
2022-01-16 07:49:06 power_api.c:124:check_voltage_multi: retry time: 1
2022-01-16 07:49:08 power_api.c:86:get_average_voltage: chain[0], voltage is: 17.064931 
2022-01-16 07:49:09 power_api.c:86:get_average_voltage: chain[1], voltage is: 22.391982 
2022-01-16 07:49:13 power_api.c:86:get_average_voltage: chain[2], voltage is: 16.991455 
2022-01-16 07:49:13 power_api.c:97:get_average_voltage: aveage voltage is: 18.816123 
2022-01-16 07:49:13 power_api.c:110:check_voltage: target_vol = 17.00, actural_vol = 18.82, more than 1.0v diff.
2022-01-16 07:49:14 power_api.c:124:check_voltage_multi: retry time: 2
2022-01-16 07:49:16 power_api.c:86:get_average_voltage: chain[0], voltage is: 17.064931 
2022-01-16 07:49:19 power_api.c:86:get_average_voltage: chain[1], voltage is: 22.391982 
2022-01-16 07:49:21 power_api.c:86:get_average_voltage: chain[2], voltage is: 16.966963 
2022-01-16 07:49:21 power_api.c:97:get_average_voltage: aveage voltage is: 18.807959 
2022-01-16 07:49:21 power_api.c:110:check_voltage: target_vol = 17.00, actural_vol = 18.81, more than 1.0v diff.
2022-01-16 07:49:22 power_api.c:124:check_voltage_multi: retry time: 3
2022-01-16 07:49:23 power_api.c:86:get_average_voltage: chain[0], voltage is: 17.083301 
2022-01-16 07:49:25 power_api.c:86:get_average_voltage: chain[1], voltage is: 22.379736 
2022-01-16 07:49:27 power_api.c:86:get_average_voltage: chain[2], voltage is: 16.973086 
2022-01-16 07:49:27 power_api.c:97:get_average_voltage: aveage voltage is: 18.812041 
2022-01-16 07:49:27 power_api.c:110:check_voltage: target_vol = 17.00, actural_vol = 18.81, more than 1.0v diff.
2022-01-16 07:49:28 power_api.c:124:check_voltage_multi: retry time: 4
2022-01-16 07:49:31 power_api.c:86:get_average_voltage: chain[0], voltage is: 17.083301 
2022-01-16 07:49:34 power_api.c:86:get_average_voltage: chain[1], voltage is: 22.379736 
2022-01-16 07:49:37 power_api.c:86:get_average_voltage: chain[2], voltage is: 16.966963 
2022-01-16 07:49:37 power_api.c:97:get_average_voltage: aveage voltage is: 18.810000 
2022-01-16 07:49:37 power_api.c:110:check_voltage: target_vol = 17.00, actural_vol = 18.81, more than 1.0v diff.
2022-01-16 07:49:38 power_api.c:124:check_voltage_multi: retry time: 5
2022-01-16 07:49:40 power_api.c:86:get_average_voltage: chain[0], voltage is: 17.071054 
2022-01-16 07:49:41 power_api.c:86:get_average_voltage: chain[1], voltage is: 22.385859 
2022-01-16 07:49:43 power_api.c:86:get_average_voltage: chain[2], voltage is: 16.991455 
2022-01-16 07:49:43 power_api.c:97:get_average_voltage: aveage voltage is: 18.816123 
2022-01-16 07:49:43 power_api.c:110:check_voltage: target_vol = 17.00, actural_vol = 18.82, more than 1.0v diff.
2022-01-16 07:49:44 power_api.c:124:check_voltage_multi: retry time: 6
2022-01-16 07:49:46 power_api.c:86:get_average_voltage: chain[0], voltage is: 17.071054 
2022-01-16 07:49:49 power_api.c:86:get_average_voltage: chain[1], voltage is: 22.367490 
2022-01-16 07:49:52 power_api.c:86:get_average_voltage: chain[2], voltage is: 16.979209 
2022-01-16 07:49:52 power_api.c:97:get_average_voltage: aveage voltage is: 18.805918 
2022-01-16 07:49:52 power_api.c:110:check_voltage: target_vol = 17.00, actural_vol = 18.81, more than 1.0v diff.
2022-01-16 07:49:53 power_api.c:124:check_voltage_multi: retry time: 7
2022-01-16 07:49:55 power_api.c:86:get_average_voltage: chain[0], voltage is: 17.064931 
2022-01-16 07:49:57 power_api.c:86:get_average_voltage: chain[1], voltage is: 22.379736 
2022-01-16 07:49:59 power_api.c:86:get_average_voltage: chain[2], voltage is: 16.979209 
2022-01-16 07:49:59 power_api.c:97:get_average_voltage: aveage voltage is: 18.807959 
2022-01-16 07:49:59 power_api.c:110:check_voltage: target_vol = 17.00, actural_vol = 18.81, more than 1.0v diff.
2022-01-16 07:50:00 power_api.c:124:check_voltage_multi: retry time: 8
2022-01-16 07:50:02 power_api.c:86:get_average_voltage: chain[0], voltage is: 17.083301 
2022-01-16 07:50:04 power_api.c:86:get_average_voltage: chain[1], voltage is: 22.373613 
2022-01-16 07:50:05 power_api.c:86:get_average_voltage: chain[2], voltage is: 16.997578 
2022-01-16 07:50:05 power_api.c:97:get_average_voltage: aveage voltage is: 18.818164 
2022-01-16 07:50:05 power_api.c:110:check_voltage: target_vol = 17.00, actural_vol = 18.82, more than 1.0v diff.
2022-01-16 07:50:06 power_api.c:124:check_voltage_multi: retry time: 9
2022-01-16 07:50:08 power_api.c:86:get_average_voltage: chain[0], voltage is: 17.071054 
2022-01-16 07:50:12 power_api.c:86:get_average_voltage: chain[1], voltage is: 22.379736 
2022-01-16 07:50:15 power_api.c:86:get_average_voltage: chain[2], voltage is: 16.991455 
2022-01-16 07:50:15 power_api.c:97:get_average_voltage: aveage voltage is: 18.814082 
2022-01-16 07:50:15 power_api.c:110:check_voltage: target_vol = 17.00, actural_vol = 18.81, more than 1.0v diff.
2022-01-16 07:50:16 power_api.c:124:check_voltage_multi: retry time: 10
2022-01-16 07:50:18 power_api.c:86:get_average_voltage: chain[0], voltage is: 17.071054 
2022-01-16 07:50:19 power_api.c:86:get_average_voltage: chain[1], voltage is: 22.379736 
2022-01-16 07:50:21 power_api.c:86:get_average_voltage: chain[2], voltage is: 16.979209 
2022-01-16 07:50:21 power_api.c:97:get_average_voltage: aveage voltage is: 18.810000 
2022-01-16 07:50:21 power_api.c:110:check_voltage: target_vol = 17.00, actural_vol = 18.81, more than 1.0v diff.
2022-01-16 07:50:22 power_api.c:124:check_voltage_multi: retry time: 11
2022-01-16 07:50:24 power_api.c:86:get_average_voltage: chain[0], voltage is: 17.071054 
2022-01-16 07:50:27 power_api.c:86:get_average_voltage: chain[1], voltage is: 22.373613 
2022-01-16 07:50:30 power_api.c:86:get_average_voltage: chain[2], voltage is: 16.985332 
2022-01-16 07:50:30 power_api.c:97:get_average_voltage: aveage voltage is: 18.810000 
2022-01-16 07:50:30 power_api.c:110:check_voltage: target_vol = 17.00, actural_vol = 18.81, more than 1.0v diff.
2022-01-16 07:50:31 power_api.c:124:check_voltage_multi: retry time: 12
2022-01-16 07:50:33 power_api.c:86:get_average_voltage: chain[0], voltage is: 17.077178 
2022-01-16 07:50:35 power_api.c:86:get_average_voltage: chain[1], voltage is: 22.398105 
2022-01-16 07:50:37 power_api.c:86:get_average_voltage: chain[2], voltage is: 16.979209 
2022-01-16 07:50:37 power_api.c:97:get_average_voltage: aveage voltage is: 18.818164 
2022-01-16 07:50:37 power_api.c:110:check_voltage: target_vol = 17.00, actural_vol = 18.82, more than 1.0v diff.
2022-01-16 07:50:38 power_api.c:124:check_voltage_multi: retry time: 13
2022-01-16 07:50:40 power_api.c:86:get_average_voltage: chain[0], voltage is: 17.101670 
2022-01-16 07:50:41 power_api.c:86:get_average_voltage: chain[1], voltage is: 22.398105 
2022-01-16 07:50:43 power_api.c:86:get_average_voltage: chain[2], voltage is: 16.979209 
2022-01-16 07:50:43 power_api.c:97:get_average_voltage: aveage voltage is: 18.826328 
2022-01-16 07:50:43 power_api.c:110:check_voltage: target_vol = 17.00, actural_vol = 18.83, more than 1.0v diff.
2022-01-16 07:50:44 power_api.c:124:check_voltage_multi: retry time: 14
2022-01-16 07:50:46 power_api.c:86:get_average_voltage: chain[0], voltage is: 17.089424 
2022-01-16 07:50:49 power_api.c:86:get_average_voltage: chain[1], voltage is: 22.391982 
2022-01-16 07:50:53 power_api.c:86:get_average_voltage: chain[2], voltage is: 16.979209 
2022-01-16 07:50:53 power_api.c:97:get_average_voltage: aveage voltage is: 18.820205 
2022-01-16 07:50:53 power_api.c:110:check_voltage: target_vol = 17.00, actural_vol = 18.82, more than 1.0v diff.
2022-01-16 07:50:54 power_api.c:124:check_voltage_multi: retry time: 15
2022-01-16 07:50:55 power_api.c:86:get_average_voltage: chain[0], voltage is: 17.089424 
2022-01-16 07:50:57 power_api.c:86:get_average_voltage: chain[1], voltage is: 22.391982 
2022-01-16 07:50:59 power_api.c:86:get_average_voltage: chain[2], voltage is: 16.997578 
2022-01-16 07:50:59 power_api.c:97:get_average_voltage: aveage voltage is: 18.826328 
2022-01-16 07:50:59 power_api.c:110:check_voltage: target_vol = 17.00, actural_vol = 18.83, more than 1.0v diff.
2022-01-16 07:51:00 power_api.c:124:check_voltage_multi: retry time: 16
2022-01-16 07:51:02 power_api.c:86:get_average_voltage: chain[0], voltage is: 17.052685 
2022-01-16 07:51:05 power_api.c:86:get_average_voltage: chain[1], voltage is: 22.398105 
2022-01-16 07:51:08 power_api.c:86:get_average_voltage: chain[2], voltage is: 16.966963 
2022-01-16 07:51:08 power_api.c:97:get_average_voltage: aveage voltage is: 18.805918 
2022-01-16 07:51:08 power_api.c:110:check_voltage: target_vol = 17.00, actural_vol = 18.81, more than 1.0v diff.
2022-01-16 07:51:09 power_api.c:124:check_voltage_multi: retry time: 17
2022-01-16 07:51:11 power_api.c:86:get_average_voltage: chain[0], voltage is: 17.071054 
2022-01-16 07:51:13 power_api.c:86:get_average_voltage: chain[1], voltage is: 22.379736 
2022-01-16 07:51:15 power_api.c:86:get_average_voltage: chain[2], voltage is: 16.973086 
2022-01-16 07:51:15 power_api.c:97:get_average_voltage: aveage voltage is: 18.807959 
2022-01-16 07:51:15 power_api.c:110:check_voltage: target_vol = 17.00, actural_vol = 18.81, more than 1.0v diff.
2022-01-16 07:51:16 power_api.c:124:check_voltage_multi: retry time: 18
2022-01-16 07:51:17 power_api.c:86:get_average_voltage: chain[0], voltage is: 17.083301 
2022-01-16 07:51:19 power_api.c:86:get_average_voltage: chain[1], voltage is: 22.391982 
2022-01-16 07:51:21 power_api.c:86:get_average_voltage: chain[2], voltage is: 16.973086 
2022-01-16 07:51:21 power_api.c:97:get_average_voltage: aveage voltage is: 18.816123 
2022-01-16 07:51:21 power_api.c:110:check_voltage: target_vol = 17.00, actural_vol = 18.82, more than 1.0v diff.
2022-01-16 07:51:22 power_api.c:124:check_voltage_multi: retry time: 19
2022-01-16 07:51:24 power_api.c:86:get_average_voltage: chain[0], voltage is: 17.077178 
2022-01-16 07:51:27 power_api.c:86:get_average_voltage: chain[1], voltage is: 22.385859 
2022-01-16 07:51:30 power_api.c:86:get_average_voltage: chain[2], voltage is: 16.966963 
2022-01-16 07:51:30 power_api.c:97:get_average_voltage: aveage voltage is: 18.810000 
2022-01-16 07:51:30 power_api.c:110:check_voltage: target_vol = 17.00, actural_vol = 18.81, more than 1.0v diff.
2022-01-16 07:51:31 power_api.c:124:check_voltage_multi: retry time: 20
2022-01-16 07:51:33 power_api.c:86:get_average_voltage: chain[0], voltage is: 17.064931 
2022-01-16 07:51:35 power_api.c:86:get_average_voltage: chain[1], voltage is: 22.373613 
2022-01-16 07:51:37 power_api.c:86:get_average_voltage: chain[2], voltage is: 16.991455 
2022-01-16 07:51:37 power_api.c:97:get_average_voltage: aveage voltage is: 18.810000 
2022-01-16 07:51:37 power_api.c:110:check_voltage: target_vol = 17.00, actural_vol = 18.81, more than 1.0v diff.
2022-01-16 07:51:38 power_api.c:124:check_voltage_multi: retry time: 21
2022-01-16 07:51:39 power_api.c:86:get_average_voltage: chain[0], voltage is: 17.064931 
2022-01-16 07:51:43 power_api.c:86:get_average_voltage: chain[1], voltage is: 22.373613 
2022-01-16 07:51:46 power_api.c:86:get_average_voltage: chain[2], voltage is: 16.985332 
2022-01-16 07:51:46 power_api.c:97:get_average_voltage: aveage voltage is: 18.807959 
2022-01-16 07:51:46 power_api.c:110:check_voltage: target_vol = 17.00, actural_vol = 18.81, more than 1.0v diff.
2022-01-16 07:51:47 power_api.c:124:check_voltage_multi: retry time: 22
2022-01-16 07:51:49 power_api.c:86:get_average_voltage: chain[0], voltage is: 17.089424 
2022-01-16 07:51:51 power_api.c:86:get_average_voltage: chain[1], voltage is: 22.379736 
2022-01-16 07:51:52 power_api.c:86:get_average_voltage: chain[2], voltage is: 16.973086 
2022-01-16 07:51:52 power_api.c:97:get_average_voltage: aveage voltage is: 18.814082 
2022-01-16 07:51:52 power_api.c:110:check_voltage: target_vol = 17.00, actural_vol = 18.81, more than 1.0v diff.
2022-01-16 07:51:53 power_api.c:124:check_voltage_multi: retry time: 23
2022-01-16 07:51:55 power_api.c:86:get_average_voltage: chain[0], voltage is: 17.077178 
2022-01-16 07:51:57 power_api.c:86:get_average_voltage: chain[1], voltage is: 22.379736 
2022-01-16 07:51:59 power_api.c:86:get_average_voltage: chain[2], voltage is: 16.966963 
2022-01-16 07:51:59 power_api.c:97:get_average_voltage: aveage voltage is: 18.807959 
2022-01-16 07:51:59 power_api.c:110:check_voltage: target_vol = 17.00, actural_vol = 18.81, more than 1.0v diff.
2022-01-16 07:52:00 power_api.c:124:check_voltage_multi: retry time: 24
2022-01-16 07:52:02 power_api.c:86:get_average_voltage: chain[0], voltage is: 17.089424 
2022-01-16 07:52:05 power_api.c:86:get_average_voltage: chain[1], voltage is: 22.391982 
2022-01-16 07:52:08 power_api.c:86:get_average_voltage: chain[2], voltage is: 16.985332 
2022-01-16 07:52:08 power_api.c:97:get_average_voltage: aveage voltage is: 18.822246 
2022-01-16 07:52:08 power_api.c:110:check_voltage: target_vol = 17.00, actural_vol = 18.82, more than 1.0v diff.
2022-01-16 07:52:09 power_api.c:124:check_voltage_multi: retry time: 25
2022-01-16 07:52:11 power_api.c:86:get_average_voltage: chain[0], voltage is: 17.083301 
2022-01-16 07:52:13 power_api.c:86:get_average_voltage: chain[1], voltage is: 22.385859 
2022-01-16 07:52:15 power_api.c:86:get_average_voltage: chain[2], voltage is: 16.985332 
2022-01-16 07:52:15 power_api.c:97:get_average_voltage: aveage voltage is: 18.818164 
2022-01-16 07:52:15 power_api.c:110:check_voltage: target_vol = 17.00, actural_vol = 18.82, more than 1.0v diff.
2022-01-16 07:52:16 power_api.c:124:check_voltage_multi: retry time: 26
2022-01-16 07:52:17 power_api.c:86:get_average_voltage: chain[0], voltage is: 17.064931 
2022-01-16 07:52:18 http_test.c:111:get_sys_running_seconds: system uptime 311.012022-01-16 07:52:18 http_test.c:371:upload_log_generate: write result.json done
2022-01-16 07:52:20 power_api.c:86:get_average_voltage: chain[1], voltage is: 22.379736 
2022-01-16 07:52:24 power_api.c:86:get_average_voltage: chain[2], voltage is: 16.973086 
2022-01-16 07:52:24 power_api.c:97:get_average_voltage: aveage voltage is: 18.805918 
2022-01-16 07:52:24 power_api.c:110:check_voltage: target_vol = 17.00, actural_vol = 18.81, more than 1.0v diff.
2022-01-16 07:52:25 power_api.c:124:check_voltage_multi: retry time: 27
2022-01-16 07:52:27 power_api.c:86:get_average_voltage: chain[0], voltage is: 17.064931 
2022-01-16 07:52:28 power_api.c:86:get_average_voltage: chain[1], voltage is: 22.391982 
2022-01-16 07:52:30 power_api.c:86:get_average_voltage: chain[2], voltage is: 16.960840 
2022-01-16 07:52:30 power_api.c:97:get_average_voltage: aveage voltage is: 18.805918 
2022-01-16 07:52:30 power_api.c:110:check_voltage: target_vol = 17.00, actural_vol = 18.81, more than 1.0v diff.
2022-01-16 07:52:31 power_api.c:124:check_voltage_multi: retry time: 28
2022-01-16 07:52:33 power_api.c:86:get_average_voltage: chain[0], voltage is: 17.089424 
2022-01-16 07:52:35 power_api.c:86:get_average_voltage: chain[1], voltage is: 22.391982 
2022-01-16 07:52:37 power_api.c:86:get_average_voltage: chain[2], voltage is: 16.966963 
2022-01-16 07:52:37 power_api.c:97:get_average_voltage: aveage voltage is: 18.816123 
2022-01-16 07:52:37 power_api.c:110:check_voltage: target_vol = 17.00, actural_vol = 18.82, more than 1.0v diff.
2022-01-16 07:52:38 power_api.c:124:check_voltage_multi: retry time: 29
2022-01-16 07:52:40 power_api.c:86:get_average_voltage: chain[0], voltage is: 17.089424 
2022-01-16 07:52:43 power_api.c:86:get_average_voltage: chain[1], voltage is: 22.385859 
2022-01-16 07:52:46 power_api.c:86:get_average_voltage: chain[2], voltage is: 16.997578 
2022-01-16 07:52:46 power_api.c:97:get_average_voltage: aveage voltage is: 18.824287 
2022-01-16 07:52:46 power_api.c:110:check_voltage: target_vol = 17.00, actural_vol = 18.82, more than 1.0v diff.
2022-01-16 07:52:47 power_api.c:182:set_iic_power_by_voltage: now set voltage to : 17.000000 
2022-01-16 07:52:47 driver-btm-api.c:205:set_miner_status: ERROR_POWER_LOST
2022-01-16 07:52:47 driver-btm-api.c:146:stop_mining: stop mining: power set failed!
2022-01-16 07:52:47 thread.c:930:cancel_read_nonce_reg_thread: cancel thread
2022-01-16 07:52:47 driver-btm-api.c:131:killall_hashboard: ****power off hashboard****

[DwarfNo3]

and when I swap the hasboard with 22 volts another hashboard goes to 0 volts. So it's probably both PSUs? (both are used)

Code:

Booting Linux on physical CPU 0x0
Linux version 4.6.0-xilinx-gff8137b-dirty (lzq@armdev2) (gcc version 4.8.3 20140320 (prerelease) (Sourcery CodeBench Lite 2014.05-23) ) #25 SMP PREEMPT Fri Nov 23 15:30:52 CST 2018
CPU: ARMv7 Processor [413fc090] revision 0 (ARMv7), cr=18c5387d
CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
Machine model: Xilinx Zynq
cma: Reserved 16 MiB at 0x0e000000
Memory policy: Data cache writealloc
On node 0 totalpages: 61440
free_area_init_node: node 0, pgdat c0b39280, node_mem_map cde10000
  Normal zone: 480 pages used for memmap
  Normal zone: 0 pages reserved
  Normal zone: 61440 pages, LIFO batch:15
percpu: Embedded 12 pages/cpu @cddf1000 s19776 r8192 d21184 u49152
pcpu-alloc: s19776 r8192 d21184 u49152 alloc=12*4096
pcpu-alloc: [0] 0 [0] 1 
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 60960
Kernel command line: mem=240M console=ttyPS0,115200 ramdisk_size=33554432 root=/dev/ram rw earlyprintk
PID hash table entries: 1024 (order: 0, 4096 bytes)
Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
Memory: 203752K/245760K available (6345K kernel code, 231K rwdata, 1896K rodata, 1024K init, 223K bss, 25624K reserved, 16384K cma-reserved, 0K highmem)
Virtual kernel memory layout:
    vector  : 0xffff0000 - 0xffff1000   (   4 kB)
    fixmap  : 0xffc00000 - 0xfff00000   (3072 kB)
    vmalloc : 0xcf800000 - 0xff800000   ( 768 MB)
    lowmem  : 0xc0000000 - 0xcf000000   ( 240 MB)
    pkmap   : 0xbfe00000 - 0xc0000000   (   2 MB)
    modules : 0xbf000000 - 0xbfe00000   (  14 MB)
      .text : 0xc0008000 - 0xc090c424   (9234 kB)
      .init : 0xc0a00000 - 0xc0b00000   (1024 kB)
      .data : 0xc0b00000 - 0xc0b39fe0   ( 232 kB)
       .bss : 0xc0b39fe0 - 0xc0b71c28   ( 224 kB)
Preemptible hierarchical RCU implementation.
	Build-time adjustment of leaf fanout to 32.
	RCU restricting CPUs from NR_CPUS=4 to nr_cpu_ids=2.
RCU: Adjusting geometry for rcu_fanout_leaf=32, nr_cpu_ids=2
NR_IRQS:16 nr_irqs:16 16
efuse mapped to cf800000
ps7-slcr mapped to cf802000
L2C: platform modifies aux control register: 0x72360000 -> 0x72760000
L2C: DT/platform modifies aux control register: 0x72360000 -> 0x72760000
L2C-310 erratum 769419 enabled
L2C-310 enabling early BRESP for Cortex-A9
L2C-310 full line of zeros enabled for Cortex-A9
L2C-310 ID prefetch enabled, offset 1 lines
L2C-310 dynamic clock gating enabled, standby mode enabled
L2C-310 cache controller enabled, 8 ways, 512 kB
L2C-310: CACHE_ID 0x410000c8, AUX_CTRL 0x76760001
zynq_clock_init: clkc starts at cf802100
Zynq clock init
sched_clock: 64 bits at 333MHz, resolution 3ns, wraps every 4398046511103ns
clocksource: arm_global_timer: mask: 0xffffffffffffffff max_cycles: 0x4ce07af025, max_idle_ns: 440795209040 ns
Switching to timer-based delay loop, resolution 3ns
clocksource: ttc_clocksource: mask: 0xffff max_cycles: 0xffff, max_idle_ns: 537538477 ns
ps7-ttc #0 at cf80a000, irq=18
Console: colour dummy device 80x30
Calibrating delay loop (skipped), value calculated using timer frequency.. 666.66 BogoMIPS (lpj=3333333)
pid_max: default: 32768 minimum: 301
Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
CPU: Testing write buffer coherency: ok
CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
Setting up static identity map for 0x100000 - 0x100058
CPU1: failed to boot: -1
Brought up 1 CPUs
SMP: Total of 1 processors activated (666.66 BogoMIPS).
CPU: All CPU(s) started in SVC mode.
devtmpfs: initialized
VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4
clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
pinctrl core: initialized pinctrl subsystem
NET: Registered protocol family 16
DMA: preallocated 256 KiB pool for atomic coherent allocations
cpuidle: using governor menu
hw-breakpoint: found 5 (+1 reserved) breakpoint and 1 watchpoint registers.
hw-breakpoint: maximum watchpoint size is 4 bytes.
zynq-ocm f800c000.ps7-ocmc: ZYNQ OCM pool: 256 KiB @ 0xcf880000
vgaarb: loaded
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
media: Linux media interface: v0.10
Linux video capture interface: v2.00
pps_core: LinuxPPS API ver. 1 registered
pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <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: 12584K (cceb7000 - cdb01000)
hw perfevents: enabled with armv7_cortex_a9 PMU driver, 7 counters available
futex hash table entries: 512 (order: 3, 32768 bytes)
workingset: timestamp_bits=28 max_order=16 bucket_order=0
jffs2: version 2.2. (NAND) (SUMMARY)  © 2001-2006 Red Hat, Inc.
io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered (default)
dma-pl330 f8003000.ps7-dma: Loaded driver for PL330 DMAC-241330
dma-pl330 f8003000.ps7-dma: 	DBUFF-128x8bytes Num_Chans-8 Num_Peri-4 Num_Events-16
e0000000.serial: ttyPS0 at MMIO 0xe0000000 (irq = 158, base_baud = 6249999) is a xuartps
console [ttyPS0] enabled
xdevcfg f8007000.ps7-dev-cfg: ioremap 0xf8007000 to cf86e000
[drm] Initialized drm 1.1.0 20060810
brd: module loaded
loop: module loaded
CAN device driver interface
gpiod_set_value: invalid GPIO
libphy: MACB_mii_bus: probed
macb e000b000.ethernet eth0: Cadence GEM rev 0x00020118 at 0xe000b000 irq 31 (00:0a:35:00:00:00)
Generic PHY e000b000.etherne:00: attached PHY driver [Generic PHY] (mii_bus:phy_addr=e000b000.etherne:00, irq=-1)
e1000e: Intel(R) PRO/1000 Network Driver - 3.2.6-k
e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
ehci-pci: EHCI PCI platform driver
usbcore: registered new interface driver usb-storage
mousedev: PS/2 mouse device common for all mice
i2c /dev entries driver
Xilinx Zynq CpuIdle Driver started
sdhci: Secure Digital Host Controller Interface driver
sdhci: Copyright(c) Pierre Ossman
sdhci-pltfm: SDHCI platform and OF driver helper
mmc0: SDHCI controller on e0100000.ps7-sdio [e0100000.ps7-sdio] using ADMA
ledtrig-cpu: registered to indicate activity on CPUs
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
nand: device found, Manufacturer ID: 0x2c, Chip ID: 0xda
nand: Micron MT29F2G08ABAEAWP
nand: 256 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 64
nand: WARNING: pl35x-nand: the ECC used on your system is too weak compared to the one required by the NAND chip
Bad block table found at page 131008, version 0x01
Bad block table found at page 130944, version 0x01
6 ofpart partitions found on MTD device pl35x-nand
Creating 6 MTD partitions on "pl35x-nand":
0x000000000000-0x000002800000 : "BOOT.bin-env-dts-kernel"
0x000002800000-0x000004800000 : "ramfs"
0x000004800000-0x000005000000 : "configs"
0x000005000000-0x000006000000 : "reserve"
0x000006000000-0x000008000000 : "ramfs-bak"
0x000008000000-0x000010000000 : "reserve1"
NET: Registered protocol family 10
sit: IPv6 over IPv4 tunneling driver
NET: Registered protocol family 17
can: controller area network core (rev 20120528 abi 9)
NET: Registered protocol family 29
can: raw protocol (rev 20120528)
can: broadcast manager protocol (rev 20120528 t)
can: netlink gateway (rev 20130117) max_hops=1
zynq_pm_ioremap: no compatible node found for 'xlnx,zynq-ddrc-a05'
zynq_pm_late_init: Unable to map DDRC IO memory.
Registering SWP/SWPB emulation handler
hctosys: unable to open rtc device (rtc0)
ALSA device list:
  No soundcards found.
RAMDISK: gzip image found at block 0
EXT4-fs (ram0): couldn't mount as ext3 due to feature incompatibilities
EXT4-fs (ram0): mounted filesystem without journal. Opts: (null)
VFS: Mounted root (ext4 filesystem) on device 1:0.
devtmpfs: mounted
Freeing unused kernel memory: 1024K (c0a00000 - c0b00000)
EXT4-fs (ram0): re-mounted. Opts: block_validity,delalloc,barrier,user_xattr
random: dd urandom read with 0 bits of entropy available
ubi0: attaching mtd2
ubi0: scanning is finished
ubi0: attached mtd2 (name "configs", size 8 MiB)
ubi0: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
ubi0: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
ubi0: VID header offset: 2048 (aligned 2048), data offset: 4096
ubi0: good PEBs: 64, bad PEBs: 0, corrupted PEBs: 0
ubi0: user volume: 1, internal volumes: 1, max. volumes count: 128
ubi0: max/mean erase counter: 6/2, WL threshold: 4096, image sequence number: 638989880
ubi0: available PEBs: 0, total reserved PEBs: 64, PEBs reserved for bad PEB handling: 40
ubi0: background thread "ubi_bgt0d" started, PID 708
UBIFS (ubi0:0): background thread "ubifs_bgt0_0" started, PID 711
UBIFS (ubi0:0): recovery needed
UBIFS (ubi0:0): recovery completed
UBIFS (ubi0:0): UBIFS: mounted UBI device 0, volume 0, name "configs"
UBIFS (ubi0:0): LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
UBIFS (ubi0:0): FS size: 1396736 bytes (1 MiB, 11 LEBs), journal size 888833 bytes (0 MiB, 5 LEBs)
UBIFS (ubi0:0): reserved for root: 65970 bytes (64 KiB)
UBIFS (ubi0:0): media format: w4/r0 (latest is w4/r0), UUID 6593BA4D-00F7-467B-9E0A-A2198CBE84FF, small LPT model
ubi1: attaching mtd5
ubi1: scanning is finished
ubi1: attached mtd5 (name "reserve1", size 128 MiB)
ubi1: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
ubi1: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
ubi1: VID header offset: 2048 (aligned 2048), data offset: 4096
ubi1: good PEBs: 1020, bad PEBs: 4, corrupted PEBs: 0
ubi1: user volume: 1, internal volumes: 1, max. volumes count: 128
ubi1: max/mean erase counter: 12/7, WL threshold: 4096, image sequence number: 100324054
ubi1: available PEBs: 0, total reserved PEBs: 1020, PEBs reserved for bad PEB handling: 36
ubi1: background thread "ubi_bgt1d" started, PID 720
UBIFS (ubi1:0): background thread "ubifs_bgt1_0" started, PID 723
UBIFS (ubi1:0): recovery needed
UBIFS (ubi1:0): recovery completed
UBIFS (ubi1:0): UBIFS: mounted UBI device 1, volume 0, name "reserve1"
UBIFS (ubi1:0): LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
UBIFS (ubi1:0): FS size: 123039744 bytes (117 MiB, 969 LEBs), journal size 6221824 bytes (5 MiB, 49 LEBs)
UBIFS (ubi1:0): reserved for root: 4952683 bytes (4836 KiB)
UBIFS (ubi1:0): media format: w4/r0 (latest is w4/r0), UUID 058C0E40-6EAA-4676-9C52-F694F6D34F3B, small LPT model
IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
macb e000b000.ethernet eth0: unable to generate target frequency: 25000000 Hz
macb e000b000.ethernet eth0: link up (100/Full)
IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
In axi fpga driver!
request_mem_region OK!
AXI fpga dev virtual address is 0xcfb38000
*base_vir_addr = 0xfb013
In fpga mem driver!
request_mem_region OK!
fpga mem virtual address is 0xd2000000
2022-01-16 08:03:59 driver-btm-api.c:663:init_freq_mode: This is scan-user version
2022-01-16 08:03:59 driver-btm-api.c:2028:bitmain_soc_init: opt_multi_version     = 1
2022-01-16 08:03:59 driver-btm-api.c:2029:bitmain_soc_init: opt_bitmain_ab        = 1
2022-01-16 08:03:59 driver-btm-api.c:2030:bitmain_soc_init: opt_bitmain_work_mode = 0
2022-01-16 08:03:59 driver-btm-api.c:2031:bitmain_soc_init: Miner compile time: Thu Apr 23 16:29:07 CST 2020 type: Antminer T17
2022-01-16 08:03:59 driver-btm-api.c:2032:bitmain_soc_init: commit version: 1c5be6f 2020-04-20 16:18:14, build by: lol 2020-04-23 16:35:04
2022-01-16 08:03:59 driver-btm-api.c:1844:show_sn: no SN got, please write SN to /nvdata/sn
2022-01-16 08:03:59 driver-btm-api.c:1167:miner_device_init: Detect 256MB control board of XILINX
2022-01-16 08:03:59 driver-btm-api.c:1115:init_fan_parameter: fan_eft : 0  fan_pwm : 0
2022-01-16 08:03:59 thread.c:885:create_read_nonce_reg_thread: create thread
2022-01-16 08:04:05 driver-btm-api.c:1099:init_miner_version: miner ID : 8072d5025c20885c
2022-01-16 08:04:05 driver-btm-api.c:1105:init_miner_version: FPGA Version = 0xB013
2022-01-16 08:04:07 eeprom.c:431:check_pattern_test_level: L1 board
2022-01-16 08:04:09 eeprom.c:431:check_pattern_test_level: L1 board
2022-01-16 08:04:11 eeprom.c:431:check_pattern_test_level: L1 board
2022-01-16 08:04:11 driver-btm-api.c:737:get_product_id: product_id[0] = 1
2022-01-16 08:04:11 driver-btm-api.c:737:get_product_id: product_id[1] = 1
2022-01-16 08:04:11 driver-btm-api.c:737:get_product_id: product_id[2] = 1
2022-01-16 08:04:11 driver-btm-api.c:1666:get_ccdly_opt: ccdly_opt[0] = 1
2022-01-16 08:04:11 driver-btm-api.c:1666:get_ccdly_opt: ccdly_opt[1] = 1
2022-01-16 08:04:11 driver-btm-api.c:1666:get_ccdly_opt: ccdly_opt[2] = 1
2022-01-16 08:04:11 driver-btm-api.c:1919:bitmain_board_init: g_ccdly_opt = 1
2022-01-16 08:04:11 driver-btm-api.c:676:_set_project_type: project:2
2022-01-16 08:04:11 driver-btm-api.c:706:_set_project_type: Project type: Antminer T17
2022-01-16 08:04:11 driver-btm-api.c:717:dump_pcb_bom_version: Chain [0] PCB Version: 0x0100
2022-01-16 08:04:11 driver-btm-api.c:718:dump_pcb_bom_version: Chain [0] BOM Version: 0x0100
2022-01-16 08:04:11 driver-btm-api.c:717:dump_pcb_bom_version: Chain [1] PCB Version: 0x0100
2022-01-16 08:04:11 driver-btm-api.c:718:dump_pcb_bom_version: Chain [1] BOM Version: 0x0100
2022-01-16 08:04:11 driver-btm-api.c:717:dump_pcb_bom_version: Chain [2] PCB Version: 0x0100
2022-01-16 08:04:11 driver-btm-api.c:718:dump_pcb_bom_version: Chain [2] BOM Version: 0x0100
2022-01-16 08:04:13 driver-btm-api.c:1939:bitmain_board_init: Fan check passed.
2022-01-16 08:04:14 board.c:36:jump_and_app_check_restore_pic: chain[0] PIC jump to app
2022-01-16 08:04:18 board.c:40:jump_and_app_check_restore_pic: Check chain[0] PIC fw version=0xb9
2022-01-16 08:04:20 board.c:36:jump_and_app_check_restore_pic: chain[1] PIC jump to app
2022-01-16 08:04:23 board.c:40:jump_and_app_check_restore_pic: Check chain[1] PIC fw version=0xb9
2022-01-16 08:04:25 board.c:36:jump_and_app_check_restore_pic: chain[2] PIC jump to app
2022-01-16 08:04:28 board.c:40:jump_and_app_check_restore_pic: Check chain[2] PIC fw version=0xb9
2022-01-16 08:04:28 thread.c:880:create_pic_heart_beat_thread: create thread
2022-01-16 08:04:28 power_api.c:55:power_init: power init ... 
2022-01-16 08:04:28 driver-btm-api.c:1949:bitmain_board_init: Enter 30s sleep to make sure power release finish.
2022-01-16 08:04:28 power_api.c:46:power_off: init gpio907
2022-01-16 08:05:00 power_api.c:232:set_iic_power_to_highest_voltage: setting to voltage: 17.00 ...
2022-01-16 08:05:06 power_api.c:124:check_voltage_multi: retry time: 0
2022-01-16 08:05:08 power_api.c:86:get_average_voltage: chain[0], voltage is: 0.067354 
2022-01-16 08:05:10 power_api.c:86:get_average_voltage: chain[1], voltage is: 17.034316 
2022-01-16 08:05:11 power_api.c:86:get_average_voltage: chain[2], voltage is: 16.905732 
2022-01-16 08:05:11 power_api.c:97:get_average_voltage: aveage voltage is: 11.335801 
2022-01-16 08:05:11 power_api.c:110:check_voltage: target_vol = 17.00, actural_vol = 11.34, more than 1.0v diff.
2022-01-16 08:05:12 power_api.c:124:check_voltage_multi: retry time: 1
2022-01-16 08:05:14 power_api.c:86:get_average_voltage: chain[0], voltage is: 17.046562 
2022-01-16 08:05:16 power_api.c:86:get_average_voltage: chain[1], voltage is: 17.015947 
2022-01-16 08:05:19 power_api.c:86:get_average_voltage: chain[2], voltage is: 16.924101 
2022-01-16 08:05:19 power_api.c:97:get_average_voltage: aveage voltage is: 16.995537 
2022-01-16 08:05:19 power_api.c:182:set_iic_power_by_voltage: now set voltage to : 17.000000 
2022-01-16 08:05:19 uart.c:80:set_baud: set fpga_baud = 115200, fpga_divider = 26
2022-01-16 08:05:29 driver-btm-api.c:1042:check_asic_number_with_power_on: Chain[0]: find 30 asic, times 0
2022-01-16 08:05:39 driver-btm-api.c:1042:check_asic_number_with_power_on: Chain[1]: find 0 asic, times 0
2022-01-16 08:05:48 driver-btm-api.c:1042:check_asic_number_with_power_on: Chain[1]: find 0 asic, times 1
2022-01-16 08:05:59 driver-btm-api.c:1042:check_asic_number_with_power_on: Chain[1]: find 0 asic, times 2
2022-01-16 08:05:59 driver-btm-api.c:1069:check_asic_number: Chain 1 only find 0 asic, will power off hash board 1
2022-01-16 08:06:11 driver-btm-api.c:1042:check_asic_number_with_power_on: Chain[2]: find 30 asic, times 0
2022-01-16 08:06:13 driver-btm-api.c:352:set_order_clock: chain[0]: set order clock, stragegy 3 clock_en=0x1
2022-01-16 08:06:13 driver-btm-api.c:352:set_order_clock: chain[2]: set order clock, stragegy 3 clock_en=0x1
2022-01-16 08:06:13 driver-hash-chip.c:502:set_clock_delay_control: core_data = 0xb4
2022-01-16 08:06:13 uart.c:80:set_baud: set fpga_baud = 3000000, fpga_divider = 0
2022-01-16 08:06:13 driver-btm-api.c:1693:check_clock_counter: freq 50 clock_counter_limit 6
2022-01-16 08:06:14 register.c:1416:quick_dump_core_hash_clock_counter: bad clock counter. chain = 2, asic = 21, core = 105, found 1, clock counter 0x00340000
2022-01-16 08:06:14 uart.c:80:set_baud: set fpga_baud = 115200, fpga_divider = 26
2022-01-16 08:06:14 driver-btm-api.c:1981:bitmain_board_init: clock counter status was not good. Try reset.