Bitcoin Forum>Bitcoin>Mining>Mining support
Author

Topic: t17+ 55 th/s problem (Read 256 times)

mikeywith
legendary
Activity: 2394
Merit: 6581
be constructive or S.T.F.U
t17+ 55 th/s problem
August 01, 2020, 05:37:52 PM
#18
Quote from: Pendrak on August 01, 2020, 01:16:02 AM
Yes, thats it, PSU was on the top, i see lot of images in the net that way, the best way is leaving PSU bottom, sad no know this before.

Most people on the internet are clueless, some random person on youtube position their miner in that way and people think it's the best way to do it, you should always refer back to this forum for more information.

Quote from: Pendrak on August 01, 2020, 01:16:02 AM
Weird part is that i remove a heatsink and i dont see any glue like the S9 serie, i see is soldering, why? i think glue is better and have more resistance.

Are you sure? why would they solder an aluminum on a plastic-like surface? will that even work? maybe they used a tiny amount of black glue which was all stuck on the chip itself and thus it's hard to see, did you confirm that the chip's surface is soft and has no trace of any glue at all?
Pendrak
member
Activity: 208
Merit: 46
Re: t17+ 55 th/s problem
August 01, 2020, 01:16:02 AM
#17
Yes, thats it, PSU was on the top, i see lot of images in the net that way, the best way is leaving PSU bottom, sad no know this before.

Weird part is that i remove a heatsink and i dont see any glue like the S9 serie, i see is soldering, why? i think glue is better and have more resistance.
mikeywith
legendary
Activity: 2394
Merit: 6581
be constructive or S.T.F.U
Re: t17+ 55 th/s problem
July 31, 2020, 07:31:18 PM
#16
You can literally turn the miner upside down so that the chips are on top, there is nothing that could restrict you from doing so, simply place the PSU at the bottom like so:



Sorry about the quality of the image, but I guess you should clearly see that in this position all the chips are facing up and without you flipping the miner to another position the large heatsinks can never touch the smaller once.

What you did was placing the miner with the PSU facing up, so either the 3rd or middle board (most likely middle) had a headsink which fell on the 1st board' small heatsinks.
Pendrak
member
Activity: 208
Merit: 46
Re: t17+ 55 th/s problem
July 31, 2020, 05:53:03 PM
#15
Short circuit.

Is sad that bitmain don't put the chips on the top part.

Horizontal position, the chips are in the bottom from the board so heat+gravity is easy to fall, i guess that "Vertical position" is the solution for prevent this.
mikeywith
legendary
Activity: 2394
Merit: 6581
be constructive or S.T.F.U
Re: t17+ 55 th/s problem
July 31, 2020, 05:27:14 PM
#14
Sorry for your loss, fortunately it didn't catch fire or something, did one of the heatsinks from the top board fall on the lower board and caused short circuit? I don't seem to understand what happened exactly looking at the images alone, my initial guess is that the vertical positioning of the miner wouldn't prevent such issues, assuming a heatsink from board A caused board B/C to short, in fact, that "horizontal position" is safer in such cases because even if the heatsink is losen, it will stay where it is assuming the chips are facing upward because the smaller heatsinks on the other side of the hashbaord don't tend to fall.

Anyway I would love to know what happened exactly.
Pendrak
member
Activity: 208
Merit: 46
Re: t17+ 55 th/s problem
July 30, 2020, 11:23:27 PM
#13
I use the "horizontal position" with my only T17.

This is what happen:



I guess if i use the "vertical position" next time this will not happen.
mikeywith
legendary
Activity: 2394
Merit: 6581
be constructive or S.T.F.U
Re: t17+ 55 th/s problem
July 30, 2020, 05:54:02 PM
#12
Quote from: amirheavy666 on July 30, 2020, 03:55:12 PM
Thanks mikeywith, I changed fan speed to 90% with your method. but problem is stable yet.

Changing the fan speed fixes the high temps on the other boards, it isn't going to fix the bad board, does your miner report lower temps on the two working chains? it MUST, and that should "prevent" the other two working boards from falling apart.

Quote from: amirheavy666 on July 30, 2020, 03:55:12 PM
I heard form some technician that we must set it With a 90 degree deviation horizontally instead of the normal position of miner in surface for problem heatsink in T17 and S17 !! whats your idea?

The_binary_Observer mentioned about this before, and my reply to him was:

Quote
... without totally negating the effect of positioning the miner in a horizontal position, it's safe to assume that unless you can do it easily [1] it's really not worth the effort, there isn't much you can do about these heatsinks until they fall, sadly.

[1]- if you use spilt-room design as I do and you have already made a whole to fit the miner vertically, going horizontal is a lot of effort, which IMO not worth it given the little advantages you get from this, but if it's a matter of simply repositioning the miner in 30-60 seconds, go ahead, you lose nothing...

If you want to go ahead with the "horizontal position" make sure the large heatsinks are facing the top, you must understand that the PCB is covered by 2 layers of heatsinks, one sits right on the top of the chip (they are lager in size and they are the once that tend to fall 99.99% of the time), if you would mistakenly position them in the wrong directing (facing down) you could expose them to more gravity and they might fall even faster.

In general you want to these gears to run as cool as possible so that the lousy solder paste doesn't get heated, so having your fans at 90-100% is without a doubt more effective than re-positioning the miner.
amirheavy666
full member
Activity: 228
Merit: 101
NEM (XEM) Top Coin
Re: t17+ 55 th/s problem
July 30, 2020, 03:55:12 PM
#11
Thanks mikeywith, I changed fan speed to 90% with your method. but problem is stable yet. what do you think. I heard form some technician that we must set it With a 90 degree deviation horizontally instead of the normal position of miner in surface for problem heatsink in T17 and S17 !! whats your idea?
mikeywith
legendary
Activity: 2394
Merit: 6581
be constructive or S.T.F.U
Re: t17+ 55 th/s problem
July 25, 2020, 01:48:57 PM
#10
Quote from: amirheavy666 on July 25, 2020, 02:25:23 AM
when miner show this temps, what i must do now for solving this problem ?

Code:
Chain# ASIC# Frequency GH/S(RT) HW Temp(PCB) Temp(Chip) ASIC status
1               44              647        18581.75   707  37-58-34-54     59-80-56-74       oooooooo oooooooo oooooooo oooooooo oooooooo oooo
2               44              636        19065.53   186  36-57-33-52     60-76-56-68       oooooooo oooooooo oooooooo oooooooo oooooooo oooo

Your temps are a bit high but they are not what causing the 0 asic issue, read this thread, there are a few ways you can follow to fix it, the simple once that require no skills and no special tools depend heavily on luck so you just have to try them out.

As for the temp, you could set a static speed of 80-100% and that will fix the temp issues assuming you have proper cooling.
Pendrak
member
Activity: 208
Merit: 46
Re: t17+ 55 th/s problem
July 25, 2020, 01:10:38 PM
#9
Quote from: BitMaxz on July 25, 2020, 12:31:55 PM
Heatsinks on hashboard are glued with thermal glue, maybe you just think that heatsink is soldered because the chips are under the heatsink. Only chips are soldered and heatsinks are glued.

Yes i know the S9 serie use glue, but my T17 got destroyed, a heatsink just fall and make a short on the next hasboard, the heatsink that fall have solder, i guess is time to remove some heatsinks from the damage board to see.
BitMaxz
legendary
Activity: 3374
Merit: 3095
Playbet.io - Crypto Casino and Sportsbook
Re: t17+ 55 th/s problem
July 25, 2020, 12:31:55 PM
#8
Quote from: amirheavy666 on July 25, 2020, 02:25:23 AM
[...]

If that is your mining status it means that your one hashbaord is broken. mickeywith is right and maybe that hashboard has loose heatsinks. Try to disassemble the unit and check the one hashboard(The broken one) for loose heatsinks.

Quote from: Pendrak on July 25, 2020, 10:24:30 AM
Anyone can confirm me this: i found that the 17 serie don't use heatsink paste/glue, the heatsink are soldered, this is true or my eyes are bad.

Heatsinks on hashboard are glued with thermal glue, maybe you just think that heatsink is soldered because the chips are under the heatsink. Only chips are soldered and heatsinks are glued.
Pendrak
member
Activity: 208
Merit: 46
Re: t17+ 55 th/s problem
July 25, 2020, 10:24:30 AM
#7
-Disconect the white cable from the hashboard and reconect it.

-Install Asic.to firmware (vinish), not sure why but in the past i got a board from a T17 that was not detected like yours with bitmain original firmware, asic.to firmware detect it without problems.

Anyone can confirm me this: i found that the 17 serie don't use heatsink paste/glue, the heatsink are soldered, this is true or my eyes are bad.
amirheavy666
full member
Activity: 228
Merit: 101
NEM (XEM) Top Coin
Re: t17+ 55 th/s problem
July 25, 2020, 02:25:23 AM
#6
Dear mikeywith, when miner show this temps, what i must do now for solving this problem ?

Code:
Chain# ASIC# Frequency GH/S(RT) HW Temp(PCB) Temp(Chip) ASIC status
1               44              647        18581.75   707  37-58-34-54     59-80-56-74       oooooooo oooooooo oooooooo oooooooo oooooooo oooo
2               44              636        19065.53   186  36-57-33-52     60-76-56-68       oooooooo oooooooo oooooooo oooooooo oooooooo oooo
mikeywith
legendary
Activity: 2394
Merit: 6581
be constructive or S.T.F.U
Re: t17+ 55 th/s problem
July 24, 2020, 07:38:58 PM
#5
Guys where you coming up wit the temp-issue from?? Huh

Kernel log says:

Code:
2020-07-24 07:39:14 driver-btm-api.c:1162:check_asic_number_with_power_on: Chain[0]: find 44 asic, times 0
2020-07-24 07:39:23 driver-btm-api.c:1162:check_asic_number_with_power_on: Chain[1]: find 44 asic, times 0
2020-07-24 07:39:31 driver-btm-api.c:1162:check_asic_number_with_power_on: Chain[2]: find 0 asic, times 0
2020-07-24 07:39:40 driver-btm-api.c:1163:check_asic_number_with_power_on: Chain[2]: find 0 asic, times 1
2020-07-24 07:39:51 driver-btm-api.c:1164:check_asic_number_with_power_on: Chain[2]: find 0 asic, times 2

The second hashboard sees 0 Asics, this is 99% caused by a loose heatsink, the conductivity between one or more of the heatsinks and the chips is bad, bitmain uses a bad thermal adhesive / solder on these gears so everyone who owns a 17 series mining gear should expect these kind of issues.
amirheavy666
full member
Activity: 228
Merit: 101
NEM (XEM) Top Coin
Re: t17+ 55 th/s problem
July 24, 2020, 12:37:08 PM
#4
I don't think , it is for hot issue. because before this shut down of farm , the temp was very good and now this miner has this temp :

Code:
Chain# ASIC# Frequency GH/S(RT) HW Temp(PCB) Temp(Chip) ASIC status
1               44              647        18581.75   707  37-58-34-54     59-80-56-74       oooooooo oooooooo oooooooo oooooooo oooooooo oooo
2               44              636        19065.53   186  36-57-33-52     60-76-56-68       oooooooo oooooooo oooooooo oooooooo oooooooo oooo
philipma1957
legendary
Activity: 4256
Merit: 8551
'The right to privacy matters'
Re: t17+ 55 th/s problem
July 24, 2020, 11:17:46 AM
#3
Very likely a heat issue.

How hot is the room?
How hot is the town it is mining in?

I have 4 units that shut down when the outside temp gets above 95f or 35c

My farm is using around 85kwatts at this time.
BitMaxz
legendary
Activity: 3374
Merit: 3095
Playbet.io - Crypto Casino and Sportsbook
Re: t17+ 55 th/s problem
July 24, 2020, 10:08:36 AM
#2
One of your hashboard might be failing due to high temp. Do you have any screenshot of your miner's staus on the WebGUI? It might be because of the high temperature that's why one of your hashboard stops while the two are running.

Look at this logs below it shows zero asic

Code:
2020-07-24 07:39:14 driver-btm-api.c:1162:check_asic_number_with_power_on: Chain[0]: find 44 asic, times 0
2020-07-24 07:39:23 driver-btm-api.c:1162:check_asic_number_with_power_on: Chain[1]: find 44 asic, times 0
2020-07-24 07:39:31 driver-btm-api.c:1162:check_asic_number_with_power_on: Chain[2]: find 0 asic, times 0
2020-07-24 07:39:40 driver-btm-api.c:1163:check_asic_number_with_power_on: Chain[2]: find 0 asic, times 1
2020-07-24 07:39:51 driver-btm-api.c:1164:check_asic_number_with_power_on: Chain[2]: find 0 asic, times 2

And then it keeps trying

Code:
2020-07-24 07:40:14 power_api.c:106:check_voltage: target_vol = 20.00, actural_vol = 20.13, check voltage passed.
2020-07-24 07:40:23 driver-btm-api.c:1167:check_asic_number_with_power_on: Chain[2]: find 0 asic, times 3
2020-07-24 07:40:34 driver-btm-api.c:1168:check_asic_number_with_power_on: Chain[2]: find 0 asic, times 4
chain 2, IO_DRIVE_STRENGTH_CONFIGURATION reg = 0x f1fffff
2020-07-24 07:40:43 driver-btm-api.c:1169:check_asic_number_with_power_on: Chain[2]: find 0 asic, times 5
chain 2, IO_DRIVE_STRENGTH_CONFIGURATION reg = 0x f1fffff
2020-07-24 07:40:51 driver-btm-api.c:1170:check_asic_number_with_power_on: Chain[2]: find 0 asic, times 6
2020-07-24 07:40:51 driver-btm-api.c:1235:check_asic_number: Chain 2 only find 0 asic, will power off hash board 2

6 times until the hashboard chain[2] shut off.

Can you try to use extra power supply if you have an extra miner? The power supply might be failing.

If not try to flash it first with SD card image to refresh your gear then update it with t17+ firmware that you can download from Bitmain. You can download the SD card image from here https://bitcointalksearch.org/topic/m.54314634.

Then update here if it works.
amirheavy666
full member
Activity: 228
Merit: 101
NEM (XEM) Top Coin
Re: t17+ 55 th/s problem
July 24, 2020, 06:00:29 AM
#1
Dear bitcointalk members
I have a problem with my new antminer t17+ 55 th/s  Kiss:

My T17+ worked without any problems until one day the power of the farm was cut off and reconnected and after that the device works with only two hashboards with the log on below when i turn on my antminer every time. But when I reset factory my miner with pressing the “reset” button on the miner, the miner works correctly with 3 hashboards but after 4-5 hours without any problem,  again miner works with 2 hashboard. what do you thinks of problem? I updated framework to newest version but the problem is exist yet... Huh Huh
please check the code on below and advice about this problem...

This log  :
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: 203416K/245760K available (6345K kernel code, 231K rwdata, 1896K rodata, 1024K init, 223K bss, 25960K reserved, 16384K cma-reserved, 0K highmem)
Virtual kernel memory layout:
    vector  : 0xffff0000 - 0xffff1000   (   4 kB)
    fixmap  : 0xffc00000 - 0xfff00000   (3072 kB)
    vmalloc : 0xcf800000 - 0xff800000   ( 768 MB)
    lowmem  : 0xc0000000 - 0xcf000000   ( 240 MB)
    pkmap   : 0xbfe00000 - 0xc0000000   (   2 MB)
    modules : 0xbf000000 - 0xbfe00000   (  14 MB)
      .text : 0xc0008000 - 0xc090c424   (9234 kB)
      .init : 0xc0a00000 - 0xc0b00000   (1024 kB)
      .data : 0xc0b00000 - 0xc0b39fe0   ( 232 kB)
       .bss : 0xc0b39fe0 - 0xc0b71c28   ( 224 kB)
Preemptible hierarchical RCU implementation.
Build-time adjustment of leaf fanout to 32.
RCU restricting CPUs from NR_CPUS=4 to nr_cpu_ids=2.
RCU: Adjusting geometry for rcu_fanout_leaf=32, nr_cpu_ids=2
NR_IRQS:16 nr_irqs:16 16
efuse mapped to cf800000
ps7-slcr mapped to cf802000
L2C: platform modifies aux control register: 0x72360000 -> 0x72760000
L2C: DT/platform modifies aux control register: 0x72360000 -> 0x72760000
L2C-310 erratum 769419 enabled
L2C-310 enabling early BRESP for Cortex-A9
L2C-310 full line of zeros enabled for Cortex-A9
L2C-310 ID prefetch enabled, offset 1 lines
L2C-310 dynamic clock gating enabled, standby mode enabled
L2C-310 cache controller enabled, 8 ways, 512 kB
L2C-310: CACHE_ID 0x410000c8, AUX_CTRL 0x76760001
zynq_clock_init: clkc starts at cf802100
Zynq clock init
sched_clock: 64 bits at 333MHz, resolution 3ns, wraps every 4398046511103ns
clocksource: arm_global_timer: mask: 0xffffffffffffffff max_cycles: 0x4ce07af025, max_idle_ns: 440795209040 ns
Switching to timer-based delay loop, resolution 3ns
clocksource: ttc_clocksource: mask: 0xffff max_cycles: 0xffff, max_idle_ns: 537538477 ns
ps7-ttc #0 at cf80a000, irq=18
Console: colour dummy device 80x30
Calibrating delay loop (skipped), value calculated using timer frequency.. 666.66 BogoMIPS (lpj=3333333)
pid_max: default: 32768 minimum: 301
Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
CPU: Testing write buffer coherency: ok
CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
Setting up static identity map for 0x100000 - 0x100058
CPU1: failed to boot: -1
Brought up 1 CPUs
SMP: Total of 1 processors activated (666.66 BogoMIPS).
CPU: All CPU(s) started in SVC mode.
devtmpfs: initialized
VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4
clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
pinctrl core: initialized pinctrl subsystem
NET: Registered protocol family 16
DMA: preallocated 256 KiB pool for atomic coherent allocations
cpuidle: using governor menu
hw-breakpoint: found 5 (+1 reserved) breakpoint and 1 watchpoint registers.
hw-breakpoint: maximum watchpoint size is 4 bytes.
zynq-ocm f800c000.ps7-ocmc: ZYNQ OCM pool: 256 KiB @ 0xcf880000
vgaarb: loaded
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
media: Linux media interface: v0.10
Linux video capture interface: v2.00
pps_core: LinuxPPS API ver. 1 registered
pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti
PTP clock support registered
EDAC MC: Ver: 3.0.0
Advanced Linux Sound Architecture Driver Initialized.
clocksource: Switched to clocksource arm_global_timer
NET: Registered protocol family 2
TCP established hash table entries: 2048 (order: 1, 8192 bytes)
TCP bind hash table entries: 2048 (order: 2, 16384 bytes)
TCP: Hash tables configured (established 2048 bind 2048)
UDP hash table entries: 256 (order: 1, 8192 bytes)
UDP-Lite hash table entries: 256 (order: 1, 8192 bytes)
NET: Registered protocol family 1
RPC: Registered named UNIX socket transport module.
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
PCI: CLS 0 bytes, default 64
Trying to unpack rootfs image as initramfs...
rootfs image is not initramfs (no cpio magic); looks like an initrd
Freeing initrd memory: 12920K (cce62000 - cdb00000)
hw perfevents: enabled with armv7_cortex_a9 PMU driver, 7 counters available
futex hash table entries: 512 (order: 3, 32768 bytes)
workingset: timestamp_bits=28 max_order=16 bucket_order=0
jffs2: version 2.2. (NAND) (SUMMARY)  © 2001-2006 Red Hat, Inc.
io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered (default)
dma-pl330 f8003000.ps7-dma: Loaded driver for PL330 DMAC-241330
dma-pl330 f8003000.ps7-dma: DBUFF-128x8bytes Num_Chans-8 Num_Peri-4 Num_Events-16
e0000000.serial: ttyPS0 at MMIO 0xe0000000 (irq = 158, base_baud = 6249999) is a xuartps
console [ttyPS0] enabled
xdevcfg f8007000.ps7-dev-cfg: ioremap 0xf8007000 to cf86e000
[drm] Initialized drm 1.1.0 20060810
brd: module loaded
loop: module loaded
CAN device driver interface
gpiod_set_value: invalid GPIO
libphy: MACB_mii_bus: probed
macb e000b000.ethernet eth0: Cadence GEM rev 0x00020118 at 0xe000b000 irq 31 (00:0a:35:00:00:00)
Generic PHY e000b000.etherne:00: attached PHY driver [Generic PHY] (mii_bus:phy_addr=e000b000.etherne:00, irq=-1)
e1000e: Intel(R) PRO/1000 Network Driver - 3.2.6-k
e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
ehci-pci: EHCI PCI platform driver
usbcore: registered new interface driver usb-storage
mousedev: PS/2 mouse device common for all mice
i2c /dev entries driver
Xilinx Zynq CpuIdle Driver started
sdhci: Secure Digital Host Controller Interface driver
sdhci: Copyright(c) Pierre Ossman
sdhci-pltfm: SDHCI platform and OF driver helper
mmc0: SDHCI controller on e0100000.ps7-sdio [e0100000.ps7-sdio] using ADMA
ledtrig-cpu: registered to indicate activity on CPUs
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
nand: device found, Manufacturer ID: 0x2c, Chip ID: 0xda
nand: Micron MT29F2G08ABAEAWP
nand: 256 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 64
nand: WARNING: pl35x-nand: the ECC used on your system is too weak compared to the one required by the NAND chip
Bad block table found at page 131008, version 0x01
Bad block table found at page 130944, version 0x01
6 ofpart partitions found on MTD device pl35x-nand
Creating 6 MTD partitions on "pl35x-nand":
0x000000000000-0x000002800000 : "BOOT.bin-env-dts-kernel"
0x000002800000-0x000004800000 : "ramfs"
0x000004800000-0x000005000000 : "configs"
0x000005000000-0x000006000000 : "reserve"
0x000006000000-0x000008000000 : "ramfs-bak"
0x000008000000-0x000010000000 : "reserve1"
NET: Registered protocol family 10
sit: IPv6 over IPv4 tunneling driver
NET: Registered protocol family 17
can: controller area network core (rev 20120528 abi 9)
NET: Registered protocol family 29
can: raw protocol (rev 20120528)
can: broadcast manager protocol (rev 20120528 t)
can: netlink gateway (rev 20130117) max_hops=1
zynq_pm_ioremap: no compatible node found for 'xlnx,zynq-ddrc-a05'
zynq_pm_late_init: Unable to map DDRC IO memory.
Registering SWP/SWPB emulation handler
hctosys: unable to open rtc device (rtc0)
ALSA device list:
  No soundcards found.
RAMDISK: gzip image found at block 0
EXT4-fs (ram0): couldn't mount as ext3 due to feature incompatibilities
EXT4-fs (ram0): mounted filesystem without journal. Opts: (null)
VFS: Mounted root (ext4 filesystem) on device 1:0.
devtmpfs: mounted
Freeing unused kernel memory: 1024K (c0a00000 - c0b00000)
EXT4-fs (ram0): re-mounted. Opts: block_validity,delalloc,barrier,user_xattr
random: dd urandom read with 0 bits of entropy available
ubi0: attaching mtd2
ubi0: scanning is finished
ubi0: attached mtd2 (name "configs", size 8 MiB)
ubi0: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
ubi0: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
ubi0: VID header offset: 2048 (aligned 2048), data offset: 4096
ubi0: good PEBs: 64, bad PEBs: 0, corrupted PEBs: 0
ubi0: user volume: 1, internal volumes: 1, max. volumes count: 128
ubi0: max/mean erase counter: 34/12, WL threshold: 4096, image sequence number: 262741923
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 A9E8BDA4-70DE-45D9-83BE-2DD9F129C0C6, 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: 125/26, WL threshold: 4096, image sequence number: 3563076859
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 A21581E4-693A-4BBF-A66A-FCE5ACD2EF7F, small LPT model
IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
macb e000b000.ethernet eth0: unable to generate target frequency: 25000000 Hz
macb e000b000.ethernet eth0: link up (100/Full)
IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
In axi fpga driver!
request_mem_region OK!
AXI fpga dev virtual address is 0xcfb38000
*base_vir_addr = 0xb023
In fpga mem driver!
request_mem_region OK!
fpga mem virtual address is 0xd2000000
random: nonblocking pool is initialized
macb e000b000.ethernet eth0: link down
macb e000b000.ethernet eth0: unable to generate target frequency: 25000000 Hz
macb e000b000.ethernet eth0: link up (100/Full)
2020-07-24 07:37:33 driver-btm-api.c:762:init_freq_mode: This is scan-user version
2020-07-24 07:37:33 driver-btm-api.c:2553:bitmain_soc_init: opt_multi_version     = 1
2020-07-24 07:37:33 driver-btm-api.c:2554:bitmain_soc_init: opt_bitmain_ab        = 1
2020-07-24 07:37:33 driver-btm-api.c:2555:bitmain_soc_init: opt_bitmain_work_mode = 0
2020-07-24 07:37:33 driver-btm-api.c:2556:bitmain_soc_init: Miner compile time: Tue Jun  2 10:11:10 CST 2020 type: Antminer T17+
2020-07-24 07:37:33 driver-btm-api.c:2557:bitmain_soc_init: commit version: 9e9a5bf 2020-06-01 18:48:14, build by: lol 2020-06-02 10:21:50
2020-07-24 07:37:33 driver-btm-api.c:2180:show_sn: 807c250c2b10481c� 7
2020-07-24 07:37:33 driver-btm-api.c:2237:handle_sn_for_factory_mode: read sn success, 807c250c2b10481c� 7
2020-07-24 07:37:33 fan.c:263:front_fan_power_on: Note: front fan is power on!
2020-07-24 07:37:33 fan.c:273:rear_fan_power_on: Note: rear fan is power on!
2020-07-24 07:37:33 driver-btm-api.c:1357:miner_device_init: Detect 256MB control board of XILINX
2020-07-24 07:37:33 driver-btm-api.c:1298:init_fan_parameter: fan_eft : 0  fan_pwm : 0
2020-07-24 07:37:39 driver-btm-api.c:1281:init_miner_version: miner ID : 807c250c2b10481c
2020-07-24 07:37:39 driver-btm-api.c:1287:init_miner_version: FPGA Version = 0xB023
2020-07-24 07:37:45 driver-btm-api.c:814:get_product_id: product_id[0] = 0
2020-07-24 07:37:45 driver-btm-api.c:814:get_product_id: product_id[1] = 0
2020-07-24 07:37:45 driver-btm-api.c:814:get_product_id: product_id[2] = 0
2020-07-24 07:37:45 driver-btm-api.c:845:get_chip_version: chip_version[0] = 1
2020-07-24 07:37:45 driver-btm-api.c:845:get_chip_version: chip_version[1] = 1
2020-07-24 07:37:45 driver-btm-api.c:845:get_chip_version: chip_version[2] = 1
2020-07-24 07:37:45 driver-btm-api.c:2293:update_conf_by_power_feedback: Power feedback is disabled
2020-07-24 07:37:45 driver-btm-api.c:2297:update_conf_by_power_feedback: get_calibration_voltage, vol:1850.
2020-07-24 07:37:45 frequency.c:1389:adjust_higer_max_vol_table: adjust_higer_max_vol_table, ideal_hashrate = 56943, index = 2, adjust_vol = 40
2020-07-24 07:37:45 thread.c:1462:create_read_nonce_reg_thread: create thread
2020-07-24 07:37:51 driver-btm-api.c:1281:init_miner_version: miner ID : 807c250c2b10481c
2020-07-24 07:37:51 driver-btm-api.c:1287:init_miner_version: FPGA Version = 0xB023
2020-07-24 07:37:56 driver-btm-api.c:814:get_product_id: product_id[0] = 0
2020-07-24 07:37:56 driver-btm-api.c:814:get_product_id: product_id[1] = 0
2020-07-24 07:37:56 driver-btm-api.c:814:get_product_id: product_id[2] = 0
2020-07-24 07:37:56 driver-btm-api.c:845:get_chip_version: chip_version[0] = 1
2020-07-24 07:37:56 driver-btm-api.c:845:get_chip_version: chip_version[1] = 1
2020-07-24 07:37:56 driver-btm-api.c:845:get_chip_version: chip_version[2] = 1
2020-07-24 07:37:56 driver-btm-api.c:1944:get_ccdly_opt: ccdly_opt[0] = 0
2020-07-24 07:37:56 driver-btm-api.c:1944:get_ccdly_opt: ccdly_opt[1] = 0
2020-07-24 07:37:56 driver-btm-api.c:1944:get_ccdly_opt: ccdly_opt[2] = 0
2020-07-24 07:37:56 driver-btm-api.c:2439:bitmain_board_init: g_ccdly_opt = 0
2020-07-24 07:37:56 driver-btm-api.c:775:_set_project_type: project:0, set to T17Plus always
2020-07-24 07:37:56 driver-btm-api.c:790:_set_project_type: Project type: Antminer T17+
2020-07-24 07:37:56 driver-btm-api.c:801:dump_pcb_bom_version: Chain [0] PCB Version: 0x0100
2020-07-24 07:37:56 driver-btm-api.c:802:dump_pcb_bom_version: Chain [0] BOM Version: 0x0100
2020-07-24 07:37:56 driver-btm-api.c:801:dump_pcb_bom_version: Chain [1] PCB Version: 0x0100
2020-07-24 07:37:56 driver-btm-api.c:802:dump_pcb_bom_version: Chain [1] BOM Version: 0x0100
2020-07-24 07:37:56 driver-btm-api.c:801:dump_pcb_bom_version: Chain [2] PCB Version: 0x0100
2020-07-24 07:37:56 driver-btm-api.c:802:dump_pcb_bom_version: Chain [2] BOM Version: 0x0100
2020-07-24 07:37:56 driver-btm-api.c:2461:bitmain_board_init: Fan check passed.
2020-07-24 07:37:57 board.c:36:jump_and_app_check_restore_pic: chain[0] PIC jump to app
2020-07-24 07:37:59 board.c:40:jump_and_app_check_restore_pic: Check chain[0] PIC fw version=0x88
2020-07-24 07:38:00 board.c:36:jump_and_app_check_restore_pic: chain[1] PIC jump to app
2020-07-24 07:38:02 board.c:40:jump_and_app_check_restore_pic: Check chain[1] PIC fw version=0x88
2020-07-24 07:38:03 board.c:36:jump_and_app_check_restore_pic: chain[2] PIC jump to app
2020-07-24 07:38:05 board.c:40:jump_and_app_check_restore_pic: Check chain[2] PIC fw version=0x88
2020-07-24 07:38:05 thread.c:1457:create_pic_heart_beat_thread: create thread
2020-07-24 07:38:07 power_api.c:231:power_init: power type version: 0x0042
2020-07-24 07:38:07 power_api.c:249:power_init: Power init:
2020-07-24 07:38:07 power_api.c:250:power_init: current_voltage_raw = 0
2020-07-24 07:38:07 power_api.c:251:power_init: highest_voltage_raw = 1950
2020-07-24 07:38:07 power_api.c:252:power_init: working_voltage_raw = 1900
2020-07-24 07:38:07 power_api.c:253:power_init: higher_voltage_raw  = 1930
2020-07-24 07:38:07 power_api.c:254:power_init: check_asic_voltage_raw  = 2000
2020-07-24 07:38:07 driver-btm-api.c:2471:bitmain_board_init: Enter 30s sleep to make sure power release finish.
2020-07-24 07:38:07 power_api.c:221:power_off: set gpio907 to 1
2020-07-24 07:38:38 power_api.c:206:power_on: set gpio907 to 0
2020-07-24 07:38:39 power_api.c:388:set_to_voltage_by_steps: Set to voltage raw 1850, step by step.
2020-07-24 07:38:57 power_api.c:120:check_voltage_multi: retry time: 0
2020-07-24 07:38:58 power_api.c:56:_get_avg_voltage: an6 raw = 2.522581, factor = 1.009032
2020-07-24 07:38:58 power_api.c:60:_get_avg_voltage: chain 0, an0 = 0.631714, an2 18.708440, an6 2.500000.
2020-07-24 07:38:59 power_api.c:56:_get_avg_voltage: an6 raw = 2.525806, factor = 1.010323
2020-07-24 07:38:59 power_api.c:60:_get_avg_voltage: chain 1, an0 = 0.679438, an2 18.660282, an6 2.500000.
2020-07-24 07:39:00 power_api.c:56:_get_avg_voltage: an6 raw = 2.522581, factor = 1.009032
2020-07-24 07:39:00 power_api.c:60:_get_avg_voltage: chain 2, an0 = 0.558824, an2 18.732737, an6 2.500000.
2020-07-24 07:39:00 power_api.c:85:_get_avg_voltage: average_voltage = 18.700486
2020-07-24 07:39:00 power_api.c:106:check_voltage: target_vol = 18.50, actural_vol = 18.70, check voltage passed.
2020-07-24 07:39:03 power_api.c:56:_get_avg_voltage: an6 raw = 2.522581, factor = 1.009032
2020-07-24 07:39:03 power_api.c:60:_get_avg_voltage: chain 0, an0 = 0.631714, an2 18.684143, an6 2.500000.
2020-07-24 07:39:04 power_api.c:56:_get_avg_voltage: an6 raw = 2.525806, factor = 1.010323
2020-07-24 07:39:04 power_api.c:60:_get_avg_voltage: chain 1, an0 = 0.655172, an2 18.660282, an6 2.500000.
2020-07-24 07:39:05 power_api.c:56:_get_avg_voltage: an6 raw = 2.522581, factor = 1.009032
2020-07-24 07:39:05 power_api.c:60:_get_avg_voltage: chain 2, an0 = 0.558824, an2 18.708440, an6 2.500000.
2020-07-24 07:39:05 power_api.c:85:_get_avg_voltage: average_voltage = 18.684288
2020-07-24 07:39:05 power_api.c:106:check_voltage: target_vol = 18.50, actural_vol = 18.68, check voltage passed.
2020-07-24 07:39:05 uart.c:81:set_baud: set fpga_baud = 115200, fpga_divider = 26
2020-07-24 07:39:14 driver-btm-api.c:1162:check_asic_number_with_power_on: Chain[0]: find 44 asic, times 0
2020-07-24 07:39:23 driver-btm-api.c:1162:check_asic_number_with_power_on: Chain[1]: find 44 asic, times 0
2020-07-24 07:39:31 driver-btm-api.c:1162:check_asic_number_with_power_on: Chain[2]: find 0 asic, times 0
2020-07-24 07:39:40 driver-btm-api.c:1163:check_asic_number_with_power_on: Chain[2]: find 0 asic, times 1
2020-07-24 07:39:51 driver-btm-api.c:1164:check_asic_number_with_power_on: Chain[2]: find 0 asic, times 2
2020-07-24 07:39:51 power_api.c:400:set_to_check_asic_voltage_by_steps: Set to voltage raw 2000, step by step.
2020-07-24 07:40:07 power_api.c:120:check_voltage_multi: retry time: 0
2020-07-24 07:40:08 power_api.c:56:_get_avg_voltage: an6 raw = 2.525806, factor = 1.010323
2020-07-24 07:40:08 power_api.c:60:_get_avg_voltage: chain 0, an0 = 20.164752, an2 20.140487, an6 2.500000.
2020-07-24 07:40:09 power_api.c:56:_get_avg_voltage: an6 raw = 2.529032, factor = 1.011613
2020-07-24 07:40:09 power_api.c:60:_get_avg_voltage: chain 1, an0 = 20.090561, an2 20.090561, an6 2.500000.
2020-07-24 07:40:10 power_api.c:56:_get_avg_voltage: an6 raw = 2.522581, factor = 1.009032
2020-07-24 07:40:10 power_api.c:60:_get_avg_voltage: chain 2, an0 = 0.558824, an2 20.166241, an6 2.500000.
2020-07-24 07:40:10 power_api.c:85:_get_avg_voltage: average_voltage = 20.132429
2020-07-24 07:40:10 power_api.c:106:check_voltage: target_vol = 20.00, actural_vol = 20.13, check voltage passed.
2020-07-24 07:40:12 power_api.c:56:_get_avg_voltage: an6 raw = 2.525806, factor = 1.010323
2020-07-24 07:40:12 power_api.c:60:_get_avg_voltage: chain 0, an0 = 20.164752, an2 20.140487, an6 2.500000.
2020-07-24 07:40:13 power_api.c:56:_get_avg_voltage: an6 raw = 2.529032, factor = 1.011613
2020-07-24 07:40:13 power_api.c:60:_get_avg_voltage: chain 1, an0 = 20.090561, an2 20.090561, an6 2.500000.
2020-07-24 07:40:14 power_api.c:56:_get_avg_voltage: an6 raw = 2.522581, factor = 1.009032
2020-07-24 07:40:14 power_api.c:60:_get_avg_voltage: chain 2, an0 = 0.558824, an2 20.166241, an6 2.500000.
2020-07-24 07:40:14 power_api.c:85:_get_avg_voltage: average_voltage = 20.132429
2020-07-24 07:40:14 power_api.c:106:check_voltage: target_vol = 20.00, actural_vol = 20.13, check voltage passed.
2020-07-24 07:40:23 driver-btm-api.c:1167:check_asic_number_with_power_on: Chain[2]: find 0 asic, times 3
2020-07-24 07:40:34 driver-btm-api.c:1168:check_asic_number_with_power_on: Chain[2]: find 0 asic, times 4
chain 2, IO_DRIVE_STRENGTH_CONFIGURATION reg = 0x f1fffff
2020-07-24 07:40:43 driver-btm-api.c:1169:check_asic_number_with_power_on: Chain[2]: find 0 asic, times 5
chain 2, IO_DRIVE_STRENGTH_CONFIGURATION reg = 0x f1fffff
2020-07-24 07:40:51 driver-btm-api.c:1170:check_asic_number_with_power_on: Chain[2]: find 0 asic, times 6
2020-07-24 07:40:51 driver-btm-api.c:1235:check_asic_number: Chain 2 only find 0 asic, will power off hash board 2
2020-07-24 07:40:52 driver-btm-api.c:1238:check_asic_number: Chain 2 voltage: an0 = 20.274838, an2 20.348387, an6 2.525806.
2020-07-24 07:40:57 driver-btm-api.c:425:set_order_clock: chain[0]: set order clock, stragegy 3 clock_en=0x1
2020-07-24 07:40:57 driver-btm-api.c:425:set_order_clock: chain[1]: set order clock, stragegy 3 clock_en=0x1
2020-07-24 07:40:57 driver-btm-api.c:1931:get_core_clock_delay_setting: PWTH_SEL 3, CCDLY_SEL 0
2020-07-24 07:40:57 driver-hash-chip.c:502:set_clock_delay_control: core_data = 0x34
2020-07-24 07:40:57 driver-btm-api.c:1972:check_clock_counter: freq 50 clock_counter_limit 6
2020-07-24 07:41:12 voltage[0] = 1790
2020-07-24 07:41:12 voltage[1] = 1790
2020-07-24 07:41:12 power_api.c:262:set_working_voltage_raw: working_voltage_raw = 1790
2020-07-24 07:41:14 temperature.c:313:calibrate_temp_sensor_one_chain: Temperature sensor calibration: chain 0 success. NCT218
2020-07-24 07:41:15 temperature.c:313:calibrate_temp_sensor_one_chain: Temperature sensor calibration: chain 1 success. NCT218
2020-07-24 07:41:15 uart.c:81:set_baud: set fpga_baud = 6000000, fpga_divider = 3
2020-07-24 07:41:16 driver-btm-api.c:294:check_bringup_temp: Bring up temperature is 24
2020-07-24 07:41:16 thread.c:1477:create_check_miner_status_thread: create thread
2020-07-24 07:41:16 thread.c:1467:create_set_miner_status_thread: create thread
2020-07-24 07:41:16 driver-btm-api.c:712:calculate_timeout: dev->timeout = 245
2020-07-24 07:41:16 thread.c:1447:create_temperature_monitor_thread: create thread
2020-07-24 07:41:16 frequency.c:527:check_bringup_temp_dec_freq: dec freq = 0 when bringup temp = 24 dec_freq_index=0
2020-07-24 07:41:16 freq_tuning.c:184:freq_tuning_get_max_freq: Max freq of tuning is 790
2020-07-24 07:41:16 driver-btm-api.c:1802:send_null_work: [DEBUG] Send null work.
2020-07-24 07:41:16 thread.c:1437:create_asic_status_monitor_thread: create thread
2020-07-24 07:41:16 frequency.c:1194:inc_freq_with_fixed_vco: chain = 255, freq = 625, is_higher_voltage = true
2020-07-24 07:41:16 frequency.c:1210:inc_freq_with_fixed_vco: [0] _POSTDIV1 = 7, _POSTDIV2 = 7, USER_DIV = 1, freq = 51
2020-07-24 07:41:16 power_api.c:388:set_to_voltage_by_steps: Set to voltage raw 1880, step by step.
2020-07-24 07:41:33 power_api.c:120:check_voltage_multi: retry time: 0
2020-07-24 07:41:35 power_api.c:56:_get_avg_voltage: an6 raw = 2.525806, factor = 1.010323
2020-07-24 07:41:35 power_api.c:60:_get_avg_voltage: chain 0, an0 = 19.000001, an2 18.951470, an6 2.500000.
2020-07-24 07:41:36 power_api.c:56:_get_avg_voltage: an6 raw = 2.529032, factor = 1.011613
2020-07-24 07:41:36 power_api.c:60:_get_avg_voltage: chain 1, an0 = 18.903061, an2 18.927296, an6 2.500000.
2020-07-24 07:41:36 power_api.c:85:_get_avg_voltage: average_voltage = 18.939383
2020-07-24 07:41:36 power_api.c:106:check_voltage: target_vol = 18.80, actural_vol = 18.94, check voltage passed.
2020-07-24 07:41:38 power_api.c:56:_get_avg_voltage: an6 raw = 2.525806, factor = 1.010323
2020-07-24 07:41:38 power_api.c:60:_get_avg_voltage: chain 0, an0 = 18.975736, an2 18.951470, an6 2.500000.
2020-07-24 07:41:39 power_api.c:56:_get_avg_voltage: an6 raw = 2.529032, factor = 1.011613
2020-07-24 07:41:39 power_api.c:60:_get_avg_voltage: chain 1, an0 = 18.927296, an2 18.927296, an6 2.500000.
2020-07-24 07:41:39 power_api.c:85:_get_avg_voltage: average_voltage = 18.939383
2020-07-24 07:41:39 power_api.c:106:check_voltage: target_vol = 18.80, actural_vol = 18.94, check voltage passed.
2020-07-24 07:41:41 frequency.c:1210:inc_freq_with_fixed_vco: [1] _POSTDIV1 = 7, _POSTDIV2 = 6, USER_DIV = 1, freq = 59
2020-07-24 07:41:43 frequency.c:1210:inc_freq_with_fixed_vco: [2] _POSTDIV1 = 6, _POSTDIV2 = 6, USER_DIV = 1, freq = 69
2020-07-24 07:41:45 frequency.c:1210:inc_freq_with_fixed_vco: [3] _POSTDIV1 = 7, _POSTDIV2 = 5, USER_DIV = 1, freq = 71
2020-07-24 07:41:47 frequency.c:1210:inc_freq_with_fixed_vco: [4] _POSTDIV1 = 6, _POSTDIV2 = 5, USER_DIV = 1, freq = 83
2020-07-24 07:41:49 frequency.c:1210:inc_freq_with_fixed_vco: [5] _POSTDIV1 = 7, _POSTDIV2 = 4, USER_DIV = 1, freq = 89
2020-07-24 07:41:51 frequency.c:1210:inc_freq_with_fixed_vco: [6] _POSTDIV1 = 5, _POSTDIV2 = 5, USER_DIV = 1, freq = 100
2020-07-24 07:41:56 frequency.c:1210:inc_freq_with_fixed_vco: [7] _POSTDIV1 = 6, _POSTDIV2 = 4, USER_DIV = 1, freq = 104
2020-07-24 07:42:00 frequency.c:1210:inc_freq_with_fixed_vco: [8] _POSTDIV1 = 7, _POSTDIV2 = 3, USER_DIV = 1, freq = 119
2020-07-24 07:42:05 frequency.c:1210:inc_freq_with_fixed_vco: [9] _POSTDIV1 = 5, _POSTDIV2 = 4, USER_DIV = 1, freq = 125
2020-07-24 07:42:09 frequency.c:1210:inc_freq_with_fixed_vco: [10] _POSTDIV1 = 6, _POSTDIV2 = 3, USER_DIV = 1, freq = 138
2020-07-24 07:42:14 frequency.c:1210:inc_freq_with_fixed_vco: [11] _POSTDIV1 = 4, _POSTDIV2 = 4, USER_DIV = 1, freq = 156
2020-07-24 07:42:22 frequency.c:1210:inc_freq_with_fixed_vco: [12] _POSTDIV1 = 5, _POSTDIV2 = 3, USER_DIV = 1, freq = 166
2020-07-24 07:42:30 frequency.c:1210:inc_freq_with_fixed_vco: [13] _POSTDIV1 = 7, _POSTDIV2 = 2, USER_DIV = 1, freq = 178
2020-07-24 07:42:38 frequency.c:1210:inc_freq_with_fixed_vco: [14] _POSTDIV1 = 4, _POSTDIV2 = 3, USER_DIV = 1, freq = 208
2020-07-24 07:42:50 frequency.c:1210:inc_freq_with_fixed_vco: [15] _POSTDIV1 = 6, _POSTDIV2 = 2, USER_DIV = 1, freq = 208
2020-07-24 07:43:03 frequency.c:1210:inc_freq_with_fixed_vco: [16] _POSTDIV1 = 5, _POSTDIV2 = 2, USER_DIV = 1, freq = 250
2020-07-24 07:43:21 frequency.c:1210:inc_freq_with_fixed_vco: [17] _POSTDIV1 = 4, _POSTDIV2 = 2, USER_DIV = 1, freq = 312
2020-07-24 07:43:45 frequency.c:1210:inc_freq_with_fixed_vco: [18] _POSTDIV1 = 7, _POSTDIV2 = 1, USER_DIV = 1, freq = 357
2020-07-24 07:44:17 frequency.c:1210:inc_freq_with_fixed_vco: [19] _POSTDIV1 = 6, _POSTDIV2 = 1, USER_DIV = 1, freq = 416
2020-07-24 07:44:58 frequency.c:1210:inc_freq_with_fixed_vco: [20] _POSTDIV1 = 5, _POSTDIV2 = 1, USER_DIV = 1, freq = 500
2020-07-24 07:44:58 power_api.c:388:set_to_voltage_by_steps: Set to voltage raw 1860, step by step.
2020-07-24 07:45:15 power_api.c:120:check_voltage_multi: retry time: 0
2020-07-24 07:45:16 power_api.c:56:_get_avg_voltage: an6 raw = 2.525806, factor = 1.010323
2020-07-24 07:45:16 power_api.c:60:_get_avg_voltage: chain 0, an0 = 18.757345, an2 18.733079, an6 2.500000.
2020-07-24 07:45:18 power_api.c:56:_get_avg_voltage: an6 raw = 2.532258, factor = 1.012903
2020-07-24 07:45:18 power_api.c:60:_get_avg_voltage: chain 1, an0 = 18.685351, an2 18.685351, an6 2.500000.
2020-07-24 07:45:18 power_api.c:85:_get_avg_voltage: average_voltage = 18.709215
2020-07-24 07:45:18 power_api.c:106:check_voltage: target_vol = 18.60, actural_vol = 18.71, check voltage passed.
2020-07-24 07:45:20 power_api.c:56:_get_avg_voltage: an6 raw = 2.525806, factor = 1.010323
2020-07-24 07:45:20 power_api.c:60:_get_avg_voltage: chain 0, an0 = 18.757345, an2 18.733079, an6 2.500000.
2020-07-24 07:45:21 power_api.c:56:_get_avg_voltage: an6 raw = 2.532258, factor = 1.012903
2020-07-24 07:45:21 power_api.c:60:_get_avg_voltage: chain 1, an0 = 18.685351, an2 18.709555, an6 2.500000.
2020-07-24 07:45:21 power_api.c:85:_get_avg_voltage: average_voltage = 18.721317
2020-07-24 07:45:21 power_api.c:106:check_voltage: target_vol = 18.60, actural_vol = 18.72, check voltage passed.
2020-07-24 07:47:22 frequency.c:1210:inc_freq_with_fixed_vco: [21] _POSTDIV1 = 4, _POSTDIV2 = 1, USER_DIV = 1, freq = 625
2020-07-24 07:47:22 power_api.c:388:set_to_voltage_by_steps: Set to voltage raw 1840, step by step.
2020-07-24 07:47:39 power_api.c:120:check_voltage_multi: retry time: 0
2020-07-24 07:47:40 power_api.c:56:_get_avg_voltage: an6 raw = 2.529032, factor = 1.011613
2020-07-24 07:47:40 power_api.c:60:_get_avg_voltage: chain 0, an0 = 18.515306, an2 18.515306, an6 2.500000.
2020-07-24 07:47:41 power_api.c:56:_get_avg_voltage: an6 raw = 2.532258, factor = 1.012903
2020-07-24 07:47:41 power_api.c:60:_get_avg_voltage: chain 1, an0 = 18.443313, an2 18.467517, an6 2.500000.
2020-07-24 07:47:41 power_api.c:85:_get_avg_voltage: average_voltage = 18.491411
2020-07-24 07:47:41 power_api.c:106:check_voltage: target_vol = 18.40, actural_vol = 18.49, check voltage passed.
2020-07-24 07:47:43 power_api.c:56:_get_avg_voltage: an6 raw = 2.529032, factor = 1.011613
2020-07-24 07:47:43 power_api.c:60:_get_avg_voltage: chain 0, an0 = 18.515306, an2 18.491071, an6 2.500000.
2020-07-24 07:47:44 power_api.c:56:_get_avg_voltage: an6 raw = 2.532258, factor = 1.012903
2020-07-24 07:47:44 power_api.c:60:_get_avg_voltage: chain 1, an0 = 18.443313, an2 18.467517, an6 2.500000.
2020-07-24 07:47:44 power_api.c:85:_get_avg_voltage: average_voltage = 18.479294
2020-07-24 07:47:44 power_api.c:106:check_voltage: target_vol = 18.40, actural_vol = 18.48, check voltage passed.
2020-07-24 07:50:33 frequency.c:1231:inc_freq_with_fixed_step: chain = 0, freq_start = 625, freq_end = 640, freq_step = 5, is_higher_voltage = true
2020-07-24 07:50:33 driver-btm-api.c:2020:check_clock_counter_domain_last_core: freq 630 clock_counter_limit 20
2020-07-24 07:50:35 driver-btm-api.c:2020:check_clock_counter_domain_last_core: freq 635 clock_counter_limit 20
2020-07-24 07:50:37 driver-btm-api.c:2020:check_clock_counter_domain_last_core: freq 640 clock_counter_limit 20
2020-07-24 07:50:38 power_api.c:388:set_to_voltage_by_steps: Set to voltage raw 1830, step by step.
2020-07-24 07:50:55 power_api.c:120:check_voltage_multi: retry time: 0
2020-07-24 07:50:56 power_api.c:56:_get_avg_voltage: an6 raw = 2.525806, factor = 1.010323
2020-07-24 07:50:56 power_api.c:60:_get_avg_voltage: chain 0, an0 = 18.441891, an2 18.441891, an6 2.500000.
2020-07-24 07:50:58 power_api.c:56:_get_avg_voltage: an6 raw = 2.535484, factor = 1.014194
2020-07-24 07:50:58 power_api.c:60:_get_avg_voltage: chain 1, an0 = 18.347328, an2 18.347328, an6 2.500000.
2020-07-24 07:50:58 power_api.c:85:_get_avg_voltage: average_voltage = 18.394609
2020-07-24 07:50:58 power_api.c:106:check_voltage: target_vol = 18.30, actural_vol = 18.39, check voltage passed.
2020-07-24 07:51:00 power_api.c:56:_get_avg_voltage: an6 raw = 2.529032, factor = 1.011613
2020-07-24 07:51:00 power_api.c:60:_get_avg_voltage: chain 0, an0 = 18.418367, an2 18.418367, an6 2.500000.
2020-07-24 07:51:01 power_api.c:56:_get_avg_voltage: an6 raw = 2.532258, factor = 1.012903
2020-07-24 07:51:01 power_api.c:60:_get_avg_voltage: chain 1, an0 = 18.370702, an2 18.370702, an6 2.500000.
2020-07-24 07:51:01 power_api.c:85:_get_avg_voltage: average_voltage = 18.394534
2020-07-24 07:51:01 power_api.c:106:check_voltage: target_vol = 18.30, actural_vol = 18.39, check voltage passed.
2020-07-24 07:51:01 frequency.c:1058:inc_asic_diff_freq_by_steps: chain = 0, start = 640, freq_step = 5
2020-07-24 07:51:03 frequency.c:1058:inc_asic_diff_freq_by_steps: chain = 1, start = 625, freq_step = 5
2020-07-24 07:51:05 driver-btm-api.c:743:set_timeout: freq 660 final timeout=111
2020-07-24 07:51:05 power_api.c:346:set_to_working_voltage_by_steps: Set to voltage raw 1790, step by step.
2020-07-24 07:51:22 power_api.c:120:check_voltage_multi: retry time: 0
2020-07-24 07:51:23 power_api.c:56:_get_avg_voltage: an6 raw = 2.529032, factor = 1.011613
2020-07-24 07:51:23 power_api.c:60:_get_avg_voltage: chain 0, an0 = 18.054847, an2 18.030612, an6 2.500000.
2020-07-24 07:51:24 power_api.c:56:_get_avg_voltage: an6 raw = 2.532258, factor = 1.012903
2020-07-24 07:51:24 power_api.c:60:_get_avg_voltage: chain 1, an0 = 17.983440, an2 18.007644, an6 2.500000.
2020-07-24 07:51:24 power_api.c:85:_get_avg_voltage: average_voltage = 18.019128
2020-07-24 07:51:24 power_api.c:106:check_voltage: target_vol = 17.90, actural_vol = 18.02, check voltage passed.
2020-07-24 07:51:26 power_api.c:56:_get_avg_voltage: an6 raw = 2.529032, factor = 1.011613
2020-07-24 07:51:26 power_api.c:60:_get_avg_voltage: chain 0, an0 = 18.030612, an2 18.030612, an6 2.500000.
2020-07-24 07:51:27 power_api.c:56:_get_avg_voltage: an6 raw = 2.532258, factor = 1.012903
2020-07-24 07:51:27 power_api.c:60:_get_avg_voltage: chain 1, an0 = 17.983440, an2 18.007644, an6 2.500000.
2020-07-24 07:51:27 power_api.c:85:_get_avg_voltage: average_voltage = 18.019128
2020-07-24 07:51:27 power_api.c:106:check_voltage: target_vol = 17.90, actural_vol = 18.02, check voltage passed.
2020-07-24 07:51:27 thread.c:1472:create_check_system_status_thread: create thread
2020-07-24 07:51:27 driver-btm-api.c:2758:bitmain_soc_init: Init done!
2020-07-24 07:51:27 driver-btm-api.c:222:set_miner_status: STATUS_INIT
2020-07-24 07:51:32 driver-btm-api.c:222:set_miner_status: STATUS_OKAY
2020-07-24 07:51:33 frequency.c:316:get_sale_hash_rate_GH: g_sale_hash_rate = 34704
2020-07-24 07:51:37 driver-btm-api.c:1539:dhash_chip_send_job: Version num 4.
2020-07-24 07:51:37 driver-btm-api.c:1686:dhash_chip_send_job: stime.tv_sec 1595577097, block_ntime 1595577095
2020-07-24 07:51:37 driver-btm-api.c:1539:dhash_chip_send_job: Version num 1.
2020-07-24 07:52:01 driver-btm-api.c:1539:dhash_chip_send_job: Version num 4.
Bitcoin Forum>Bitcoin>Mining>Mining support
Jump to: