Bitcoin Forum>Bitcoin>Mining>Mining support
Author

Topic: S17 Pro Kernel log information (Read 165 times)

mikeywith
legendary
Activity: 2394
Merit: 6581
be constructive or S.T.F.U
S17 Pro Kernel log information
February 23, 2021, 07:43:53 PM
#9
I spoke to one of Vnish devs (Marc) and he also believes what you think is true, in other words, the voltage settings are stored on the e-prom, he also said that Vnish ignores the e-prom completely in that regards, which means (in theory) you can mix hash boards with different e-prom stored values, but since that isn't the case, I am still trying to investigate the matter.
danieleither
full member
Activity: 219
Merit: 426
Re: S17 Pro Kernel log information
February 16, 2021, 12:58:40 PM
#8
On older Bitmain firmware, a voltage difference here will cause the miner to shutdown at this point. On newer Bitmain firmware, the voltage difference does not shut down the miner.
wndsnb
hero member
Activity: 544
Merit: 589
Re: S17 Pro Kernel log information
February 16, 2021, 07:08:54 AM
#7
I'm not positive, but I think frequency and voltage settings are saved in eeprom on each hashboard. These are set at the factory, and boards are matched up based on what voltage they will run at and hashrate to reach the required #. 3rd party firmware just ignores these settings, so the easiest/cheapest way to fix it is to move to vnish or similar.

I've seen logs that show similar voltage setting differences, and then a warning message saying they are different so it will set the voltage to the highest setting read. Maybe that was a newer firmware from Bitmain, so updating to the latest firmware might help as well.

You might try using this trick to set the voltage and frequency manually with the factory firmware:

https://bitcointalksearch.org/topic/m.54397808
mikeywith
legendary
Activity: 2394
Merit: 6581
be constructive or S.T.F.U
Re: S17 Pro Kernel log information
February 15, 2021, 08:48:42 PM
#6
I mixed and matched a lot of S17 pro hash boards, never had a problem, also the hash boards seem to be identical in the kernel log,

Code:
2021-02-15 20:56:55 driver-btm-api.c:616:get_product_id: product_id[0] = 0
2021-02-15 20:56:55 driver-btm-api.c:616:get_product_id: product_id[1] = 0
2021-02-15 20:56:55 driver-btm-api.c:616:get_product_id: product_id[2] = 0
2021-02-15 20:56:55 driver-btm-api.c:560:_set_project_type: project:0
2021-02-15 20:56:55 driver-btm-api.c:585:_set_project_type: Project type: Antminer S17 Pro
2021-02-15 20:56:55 driver-btm-api.c:596:dump_pcb_bom_version: Chain [0] PCB Version: 0x0101
2021-02-15 20:56:55 driver-btm-api.c:597:dump_pcb_bom_version: Chain [0] BOM Version: 0x0103
2021-02-15 20:56:55 driver-btm-api.c:596:dump_pcb_bom_version: Chain [1] PCB Version: 0x0101
2021-02-15 20:56:55 driver-btm-api.c:597:dump_pcb_bom_version: Chain [1] BOM Version: 0x0103
2021-02-15 20:56:55 driver-btm-api.c:596:dump_pcb_bom_version: Chain [2] PCB Version: 0x0101
2021-02-15 20:56:55 driver-btm-api.c:597:dump_pcb_bom_version: Chain [2] BOM Version: 0x0103
2021-02-15 20:56:57 driver-btm-api.c:1802:bitmain_board_init: Fan check passed.
2021-02-15 20:56:58 board.c:36:jump_and_app_check_restore_pic: chain[0] PIC jump to app
2021-02-15 20:57:00 board.c:40:jump_and_app_check_restore_pic: Check chain[0] PIC fw version=0xb9
2021-02-15 20:57:01 board.c:36:jump_and_app_check_restore_pic: chain[1] PIC jump to app
2021-02-15 20:57:03 board.c:40:jump_and_app_check_restore_pic: Check chain[1] PIC fw version=0xb9
2021-02-15 20:57:04 board.c:36:jump_and_app_check_restore_pic: chain[2] PIC jump to app
2021-02-15 20:57:06 board.c:40:jump_and_app_check_restore_pic: Check chain[2] PIC fw version=0xb9

The same ID, the same PCB, BOM and PIC FW version.

I highly doubt that there are any voltage settings stored in the hash board itself, makes no sense to me.

Quote from: BitMaxz on February 15, 2021, 07:53:25 PM
I don't know if this hashboard is supported on Pickit 3 but from the old miner's like t9+ and s9 they can dump and flash the pic firmware using pickit 3.

Yes, it can, another member here confirmed it.
BitMaxz
legendary
Activity: 3374
Merit: 3095
Playbet.io - Crypto Casino and Sportsbook
Re: S17 Pro Kernel log information
February 15, 2021, 07:53:25 PM
#5
Well, all hashboard from Bitmain it has it's own program but the only problem how you can replace the pic firmware for newer miner like s17 pro.
I don't know if this hashboard is supported on Pickit 3 but from the old miner's like t9+ and s9 they can dump and flash the pic firmware using pickit 3.

If you can able to backup/dump the pic firmware of the two working hashboard from your miner maybe you can solve this issue by using the backup firmware to flash the middle hashboard.

Take a look at this old thread here "repair a T9 + after a bad firmware (lost chain)"
danieleither
full member
Activity: 219
Merit: 426
Re: S17 Pro Kernel log information
February 15, 2021, 07:18:35 PM
#4
Quote from: BitMaxz on February 15, 2021, 05:46:20 PM
What I think is it is a voltage that stored in the pic on each Hashboard. It's just based on the discussion from Bitmain forum it might be also a voltage reading and according to your full logs, it seems that this issue is related to the hashboard temperature sensor.

I also think it is a pic setting - because I moved that middle hashboard from another miner. Interestingly, the temp sensor issue dose not occur when that middle hashboard is placed in a different machine (where that voltage reading reads the same as other hashboards.

Further to above, Bitmain and ZeusBTC suggest that temp sensor issues are often due to a faulty PSU or undervoltage. SO... I was wondering if the mismatched pic voltage setting is causing the temp sensor issues?

I've tried reflashing SD image with Bitmain firmware and Vnish, doing a hard reset (with the button on control board) but nothing seems to update that voltage readout / setting. I also note that those voltage settings are always the same across all 3 boards in my other miners, however the number itself does vary from machine to machine.
mikeywith
legendary
Activity: 2394
Merit: 6581
be constructive or S.T.F.U
Re: S17 Pro Kernel log information
February 15, 2021, 06:04:39 PM
#3
It is significant, the design of a single busbar connecting all 3 hash boards results in an almost exactly equal voltage across all 3 hash boards, here is how one of my miners reads.

Code:
2021-02-15 22:37:56 voltage[0] = 1800
2021-02-15 22:37:56 voltage[1] = 1800
2021-02-15 22:37:56 voltage[2] = 1800

And then once the hash boards are initiated mine shows

Code:
2021-02-15 22:38:21 power_api.c:37:_get_avg_voltage: chain = 0, voltage = 20.255039
2021-02-15 22:38:23 power_api.c:37:_get_avg_voltage: chain = 1, voltage = 20.083593
2021-02-15 22:38:24 power_api.c:37:_get_avg_voltage: chain = 2, voltage = 20.065224

Here is another miner:

Code:
2021-02-15 22:37:13 power_api.c:37:_get_avg_voltage: chain = 0, voltage = 21.381679
2021-02-15 22:37:14 power_api.c:37:_get_avg_voltage: chain = 1, voltage = 21.259218
2021-02-15 22:37:15 power_api.c:37:_get_avg_voltage: chain = 2, voltage = 21.234726

Yours shows:

Code:
2021-02-15 20:57:41 power_api.c:37:_get_avg_voltage: chain = 0, voltage = 21.185742
2021-02-15 20:57:43 power_api.c:37:_get_avg_voltage: chain = 1, voltage = 21.259218
2021-02-15 20:57:44 power_api.c:37:_get_avg_voltage: chain = 2, voltage = 21.216357

Notice how in mine chain 0 has the highest voltage reading and chain 2 has the lowest, I checked a few and they all are the same, this is logical because chain 0 is the closest to the PSU feed and the voltage will always drop slightly the further it gets from the source, yours is a bit strange, the middle one has a higher voltage than the rest and your chain 0 has the lowest voltage reading.

I think you need to tighten the screws that attach the busbar to the hash boards, it could be the reason why your temp sensors have a problem.
BitMaxz
legendary
Activity: 3374
Merit: 3095
Playbet.io - Crypto Casino and Sportsbook
Re: S17 Pro Kernel log information
February 15, 2021, 05:46:20 PM
#2
What I think is it is a voltage that stored in the pic on each Hashboard. It's just based on the discussion from Bitmain forum it might be also a voltage reading and according to your full logs, it seems that this issue is related to the hashboard temperature sensor.

Read the whole post from here https://support.bitmain.com/hc/en-us/community/posts/900000965826-S17-Pro-hashboard-temperature-sensor-problem?page=1#comments

One other solution to solve this issue is by using modded firmware that could bypass the sensors but it depends on you if you want to use other firmware than Bitmain.
danieleither
full member
Activity: 219
Merit: 426
Re: S17 Pro Kernel log information
February 15, 2021, 05:09:18 PM
#1
What is the significance of the following information in kernel log:

Code:
2021-02-15 20:58:25 voltage[0] = 1780
2021-02-15 20:58:25 voltage[1] = 1800
2021-02-15 20:58:25 voltage[2] = 1780
2021-02-15 20:58:25 Voltage are different. Will exit.

Are these voltage settings that have been stored in the pics, or are they voltage readings?

Full log here if required:

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: 203608K/245760K available (6345K kernel code, 231K rwdata, 1896K rodata, 1024K init, 223K bss, 25768K 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: 12728K (cce93000 - cdb01000)
hw perfevents: enabled with armv7_cortex_a9 PMU driver, 7 counters available
futex hash table entries: 512 (order: 3, 32768 bytes)
workingset: timestamp_bits=28 max_order=16 bucket_order=0
jffs2: version 2.2. (NAND) (SUMMARY)  © 2001-2006 Red Hat, Inc.
io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered (default)
dma-pl330 f8003000.ps7-dma: Loaded driver for PL330 DMAC-241330
dma-pl330 f8003000.ps7-dma: 	DBUFF-128x8bytes Num_Chans-8 Num_Peri-4 Num_Events-16
e0000000.serial: ttyPS0 at MMIO 0xe0000000 (irq = 158, base_baud = 6249999) is a xuartps
console [ttyPS0] enabled
xdevcfg f8007000.ps7-dev-cfg: ioremap 0xf8007000 to cf86e000
[drm] Initialized drm 1.1.0 20060810
brd: module loaded
loop: module loaded
CAN device driver interface
gpiod_set_value: invalid GPIO
libphy: MACB_mii_bus: probed
macb e000b000.ethernet eth0: Cadence GEM rev 0x00020118 at 0xe000b000 irq 31 (00:0a:35:00:00:00)
Generic PHY e000b000.etherne:00: attached PHY driver [Generic PHY] (mii_bus:phy_addr=e000b000.etherne:00, irq=-1)
e1000e: Intel(R) PRO/1000 Network Driver - 3.2.6-k
e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
ehci-pci: EHCI PCI platform driver
usbcore: registered new interface driver usb-storage
mousedev: PS/2 mouse device common for all mice
i2c /dev entries driver
Xilinx Zynq CpuIdle Driver started
sdhci: Secure Digital Host Controller Interface driver
sdhci: Copyright(c) Pierre Ossman
sdhci-pltfm: SDHCI platform and OF driver helper
mmc0: SDHCI controller on e0100000.ps7-sdio [e0100000.ps7-sdio] using ADMA
ledtrig-cpu: registered to indicate activity on CPUs
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
nand: device found, Manufacturer ID: 0x2c, Chip ID: 0xda
nand: Micron MT29F2G08ABAGAWP
nand: 256 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 128
nand: WARNING: pl35x-nand: the ECC used on your system is too weak compared to the one required by the NAND chip
Bad block table found at page 131008, version 0x01
Bad block table found at page 130944, version 0x01
6 ofpart partitions found on MTD device pl35x-nand
Creating 6 MTD partitions on "pl35x-nand":
0x000000000000-0x000002800000 : "BOOT.bin-env-dts-kernel"
0x000002800000-0x000004800000 : "ramfs"
0x000004800000-0x000005000000 : "configs"
0x000005000000-0x000006000000 : "reserve"
0x000006000000-0x000008000000 : "ramfs-bak"
0x000008000000-0x000010000000 : "reserve1"
NET: Registered protocol family 10
sit: IPv6 over IPv4 tunneling driver
NET: Registered protocol family 17
can: controller area network core (rev 20120528 abi 9)
NET: Registered protocol family 29
can: raw protocol (rev 20120528)
can: broadcast manager protocol (rev 20120528 t)
can: netlink gateway (rev 20130117) max_hops=1
zynq_pm_ioremap: no compatible node found for 'xlnx,zynq-ddrc-a05'
zynq_pm_late_init: Unable to map DDRC IO memory.
Registering SWP/SWPB emulation handler
hctosys: unable to open rtc device (rtc0)
ALSA device list:
  No soundcards found.
RAMDISK: gzip image found at block 0
EXT4-fs (ram0): couldn't mount as ext3 due to feature incompatibilities
EXT4-fs (ram0): mounted filesystem without journal. Opts: (null)
VFS: Mounted root (ext4 filesystem) on device 1:0.
devtmpfs: mounted
Freeing unused kernel memory: 1024K (c0a00000 - c0b00000)
EXT4-fs (ram0): re-mounted. Opts: block_validity,delalloc,barrier,user_xattr
random: dd urandom read with 0 bits of entropy available
ubi0: attaching mtd2
ubi0: scanning is finished
ubi0: attached mtd2 (name "configs", size 8 MiB)
ubi0: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
ubi0: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
ubi0: VID header offset: 2048 (aligned 2048), data offset: 4096
ubi0: good PEBs: 64, bad PEBs: 0, corrupted PEBs: 0
ubi0: user volume: 1, internal volumes: 1, max. volumes count: 128
ubi0: max/mean erase counter: 2/1, WL threshold: 4096, image sequence number: 1066548518
ubi0: available PEBs: 0, total reserved PEBs: 64, PEBs reserved for bad PEB handling: 40
ubi0: background thread "ubi_bgt0d" started, PID 708
UBIFS (ubi0:0): background thread "ubifs_bgt0_0" started, PID 711
UBIFS (ubi0:0): UBIFS: mounted UBI device 0, volume 0, name "configs"
UBIFS (ubi0:0): LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
UBIFS (ubi0:0): FS size: 1396736 bytes (1 MiB, 11 LEBs), journal size 888833 bytes (0 MiB, 5 LEBs)
UBIFS (ubi0:0): reserved for root: 65970 bytes (64 KiB)
UBIFS (ubi0:0): media format: w4/r0 (latest is w4/r0), UUID 3B9BE536-7E90-4DCF-AEE1-1A87FFC44969, 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: 680/161, WL threshold: 4096, image sequence number: 914180297
ubi1: available PEBs: 0, total reserved PEBs: 1020, PEBs reserved for bad PEB handling: 36
ubi1: background thread "ubi_bgt1d" started, PID 720
UBIFS (ubi1:0): background thread "ubifs_bgt1_0" started, PID 723
UBIFS (ubi1:0): UBIFS: mounted UBI device 1, volume 0, name "reserve1"
UBIFS (ubi1:0): LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
UBIFS (ubi1:0): FS size: 123039744 bytes (117 MiB, 969 LEBs), journal size 6221824 bytes (5 MiB, 49 LEBs)
UBIFS (ubi1:0): reserved for root: 4952683 bytes (4836 KiB)
UBIFS (ubi1:0): media format: w4/r0 (latest is w4/r0), UUID BCBDE5E0-4C0B-4978-9734-FC58D9F68227, small LPT model
alloc_contig_range: [e043, e044) PFNs busy
IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
alloc_contig_range: [e043, e044) PFNs busy
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 = 0xab013
In fpga mem driver!
request_mem_region OK!
fpga mem virtual address is 0xd2000000
random: nonblocking pool is initialized
Feb 15 20:59:44 (none) user.notice kernel: random: nonblocking pool is initialized
Feb 15 21:00:47 (none) local0.notice bmminer: set_start_time_point total_tv_start_sys=288 total_tv_end_sys=289
Feb 15 21:00:49 (none) local0.notice cgminer: cgminer_socket_init reg bitmain_api_detect return: 0
Feb 15 21:00:50 (none) local0.notice cgminer: cgminer_socket_init reg bitmain_update_job return: 0
Feb 15 21:00:51 (none) local0.notice cgminer: cgminer_socket_init reg bitmain_shutdown return: 0
Feb 15 21:00:51 (none) local0.err cgminer: Miner compile time: Mon Apr 27 13:25:08 CST 2020 type: Antminer S17 Pro
Feb 15 21:00:51 (none) local0.notice cgminer[999]: about to send detect
Feb 15 21:00:51 (none) local0.notice cgminer[999]: set_start_time_point total_tv_start_sys=292 total_tv_end_sys=293
Feb 15 21:00:51 (none) local0.notice cgminer[999]: Probing for an alive pool
Feb 15 21:00:51 (none) local0.notice cgminer[999]: LOW POWER MODE!
Feb 15 21:00:51 (none) local0.notice cgminer[999]: Switching to pool 1 stratum+tcp://btc-eu.f2pool.com:1314 - first alive pool
Feb 15 21:00:51 (none) local0.notice cgminer[999]: in stratum_sthread 
Feb 15 21:00:51 (none) local0.notice cgminer[999]: Pool 1 difficulty changed to 65536
Feb 15 21:00:51 (none) local0.notice cgminer[999]: Network diff set to 21.4T
Feb 15 21:00:51 (none) local0.notice cgminer[999]: POOL 1 support ab mode!
Feb 15 21:00:51 (none) local0.notice cgminer[999]: LOW POWER MODE!
Feb 15 21:00:51 (none) local0.notice cgminer[999]: in stratum_sthread 
Feb 15 21:00:51 (none) local0.notice cgminer[999]: Pool 2 difficulty changed to 4096
Feb 15 21:00:51 (none) local0.notice cgminer[999]: LOW POWER MODE!
Feb 15 21:00:51 (none) local0.warn cgminer[999]: Pool 0 stratum+tcp://btc.ss.poolin.com:443 alive, testing stability
Feb 15 21:00:51 (none) local0.notice cgminer[999]: in stratum_sthread 
Feb 15 21:00:51 (none) local0.notice cgminer[999]: Pool 0 difficulty changed to 65536
Feb 15 21:00:52 (none) local0.notice cgminer[999]: POOL 0 support ab mode!
Feb 15 21:00:52 (none) local0.notice cgminer[999]: update job
Feb 15 21:00:52 (none) local0.notice cgminer[999]: job buf total len:2610, offset:2610
Feb 15 21:00:52 (none) local0.notice cgminer[999]: about to send job, size is 2610
Feb 15 21:00:52 (none) local0.notice bmminer: bitmain_update_job_cb, rec job data 0xb4000480 size: 2610
Feb 15 21:00:52 (none) local0.notice bmminer: parse job buf len:2610
Feb 15 21:00:52 (none) local0.warn cgminer[999]: Pool 0 stratum+tcp://btc.ss.poolin.com:443 stable for >120 seconds
Feb 15 21:00:52 (none) local0.warn cgminer[999]: Switching to pool 0 stratum+tcp://btc.ss.poolin.com:443
Feb 15 21:00:56 (none) local0.notice cgminer[999]: update job
Feb 15 21:00:56 (none) local0.notice cgminer[999]: job buf total len:2631, offset:2631
Feb 15 21:00:56 (none) local0.notice cgminer[999]: about to send job, size is 2631
Feb 15 21:00:56 (none) local0.notice bmminer: bitmain_update_job_cb, rec job data 0xb4000480 size: 2631
Feb 15 21:00:56 (none) local0.notice bmminer: parse job buf len:2631
Feb 15 21:00:57 (none) local0.warn cgminer[999]: API running in IP access mode on port 4028 (15)
Feb 15 21:01:02 (none) local0.notice bmminer: need data size:514, actual size:514
Feb 15 21:01:02 (none) local0.notice cgminer[999]: got nonce sz 514
Feb 15 21:01:02 (none) local0.notice cgminer[999]: Pool 0 stale share detected, submitting as user requested
Feb 15 21:01:02 (none) local0.notice cgminer[999]: cb_bitmain_submit_nonce nonce submited
Feb 15 21:01:02 (none) local0.notice cgminer[999]: Accepted 1de4cf0b Diff 561K/65536 BTM_SOC 0 pool 0 
Feb 15 21:01:04 (none) local0.notice cgminer[999]: update job
Feb 15 21:01:04 (none) local0.notice cgminer[999]: job buf total len:2631, offset:2631
Feb 15 21:01:04 (none) local0.notice cgminer[999]: about to send job, size is 2631
Feb 15 21:01:04 (none) local0.notice bmminer: bitmain_update_job_cb, rec job data 0xb4000480 size: 2631
Feb 15 21:01:04 (none) local0.notice bmminer: parse job buf len:2631
Feb 15 21:01:24 (none) local0.notice bmminer: need data size:514, actual size:514
Feb 15 21:01:24 (none) local0.notice cgminer[999]: got nonce sz 514
Feb 15 21:01:24 (none) local0.notice cgminer[999]: Pool 0 stale share detected, submitting as user requested
Feb 15 21:01:24 (none) local0.notice cgminer[999]: cb_bitmain_submit_nonce nonce submited
Feb 15 21:01:24 (none) local0.notice cgminer[999]: Accepted 371d0bbd Diff 304K/65536 BTM_SOC 0 pool 0 
Feb 15 21:01:28 (none) local0.notice bmminer: need data size:514, actual size:514
Feb 15 21:01:28 (none) local0.notice cgminer[999]: got nonce sz 514
Feb 15 21:01:28 (none) local0.notice cgminer[999]: Pool 0 stale share detected, submitting as user requested
Feb 15 21:01:28 (none) local0.notice cgminer[999]: cb_bitmain_submit_nonce nonce submited
Feb 15 21:01:28 (none) local0.notice cgminer[999]: Accepted 56609a64 Diff 194K/65536 BTM_SOC 0 pool 0 
Feb 15 21:01:29 (none) local0.info bmminer: (null) 0: invalid nonce - HW error
Feb 15 21:01:29 (none) local0.info bmminer: (null) 0: invalid nonce - HW error
Feb 15 21:01:29 (none) local0.info bmminer: (null) 0: invalid nonce - HW error
Feb 15 21:01:30 (none) local0.info bmminer: (null) 0: invalid nonce - HW error
Feb 15 21:01:30 (none) local0.info bmminer: (null) 0: invalid nonce - HW error
Feb 15 21:01:30 (none) local0.info bmminer: (null) 0: invalid nonce - HW error
Feb 15 21:01:30 (none) local0.info bmminer: (null) 0: invalid nonce - HW error
Feb 15 21:01:30 (none) local0.info bmminer: (null) 0: invalid nonce - HW error
Feb 15 21:01:30 (none) local0.info bmminer: (null) 0: invalid nonce - HW error
Feb 15 21:01:30 (none) local0.info bmminer: (null) 0: invalid nonce - HW error
Feb 15 21:01:30 (none) local0.info bmminer: (null) 0: invalid nonce - HW error
Feb 15 21:01:30 (none) local0.info bmminer: (null) 0: invalid nonce - HW error
Feb 15 21:01:30 (none) local0.info bmminer: (null) 0: invalid nonce - HW error
Feb 15 21:01:30 (none) local0.info bmminer: (null) 0: invalid nonce - HW error
Feb 15 21:01:30 (none) local0.info bmminer: (null) 0: invalid nonce - HW error
Feb 15 21:01:30 (none) local0.info bmminer: (null) 0: invalid nonce - HW error
Feb 15 21:01:30 (none) local0.info bmminer: (null) 0: invalid nonce - HW error
Feb 15 21:01:30 (none) local0.info bmminer: (null) 0: invalid nonce - HW error
Feb 15 21:01:30 (none) local0.info bmminer: (null) 0: invalid nonce - HW error
Feb 15 21:01:30 (none) local0.info bmminer: (null) 0: invalid nonce - HW error
Feb 15 21:01:30 (none) local0.info bmminer: (null) 0: invalid nonce - HW error
Feb 15 21:01:30 (none) local0.info bmminer: (null) 0: invalid nonce - HW error
Feb 15 21:01:30 (none) local0.info bmminer: (null) 0: invalid nonce - HW error
Feb 15 21:01:30 (none) local0.info bmminer: (null) 0: invalid nonce - HW error
Feb 15 21:01:30 (none) local0.info bmminer: (null) 0: invalid nonce - HW error
Feb 15 21:01:30 (none) local0.info bmminer: (null) 0: invalid nonce - HW error
Feb 15 21:01:30 (none) local0.info bmminer: (null) 0: invalid nonce - HW error
Feb 15 21:01:30 (none) local0.info bmminer: (null) 0: invalid nonce - HW error
Feb 15 21:01:30 (none) local0.info bmminer: (null) 0: invalid nonce - HW error
Feb 15 21:01:30 (none) local0.info bmminer: (null) 0: invalid nonce - HW error
Feb 15 21:01:30 (none) local0.info bmminer: (null) 0: invalid nonce - HW error
Feb 15 21:01:30 (none) local0.info bmminer: (null) 0: invalid nonce - HW error
Feb 15 21:01:30 (none) local0.info bmminer: (null) 0: invalid nonce - HW error
Feb 15 21:01:31 (none) local0.notice bmminer: need data size:514, actual size:514
Feb 15 21:01:31 (none) local0.notice cgminer[999]: got nonce sz 514
Feb 15 21:01:31 (none) local0.notice cgminer[999]: Pool 0 stale share detected, submitting as user requested
Feb 15 21:01:31 (none) local0.notice cgminer[999]: cb_bitmain_submit_nonce nonce submited
Feb 15 21:01:31 (none) local0.notice cgminer[999]: Accepted 7a0bf0ca Diff 137K/65536 BTM_SOC 0 pool 0 
Feb 15 21:01:34 (none) local0.notice cgminer[999]: update job
Feb 15 21:01:34 (none) local0.notice cgminer[999]: job buf total len:2631, offset:2631
Feb 15 21:01:34 (none) local0.notice cgminer[999]: about to send job, size is 2631
Feb 15 21:01:34 (none) local0.notice bmminer: bitmain_update_job_cb, rec job data 0xb4000480 size: 2631
Feb 15 21:01:34 (none) local0.notice bmminer: parse job buf len:2631
Feb 15 21:01:37 (none) local0.notice bmminer: need data size:514, actual size:514
Feb 15 21:01:37 (none) local0.notice cgminer[999]: got nonce sz 514
Feb 15 21:01:37 (none) local0.notice cgminer[999]: Pool 0 stale share detected, submitting as user requested
Feb 15 21:01:37 (none) local0.notice cgminer[999]: cb_bitmain_submit_nonce nonce submited
Feb 15 21:01:37 (none) local0.notice bmminer: need data size:514, actual size:514
Feb 15 21:01:37 (none) local0.notice cgminer[999]: got nonce sz 514
Feb 15 21:01:37 (none) local0.notice cgminer[999]: Pool 0 stale share detected, submitting as user requested
Feb 15 21:01:37 (none) local0.notice cgminer[999]: cb_bitmain_submit_nonce nonce submited
Feb 15 21:01:37 (none) local0.notice cgminer[999]: Accepted 68fdcbf6 Diff 160K/65536 BTM_SOC 0 pool 0 
Feb 15 21:01:37 (none) local0.notice cgminer[999]: Accepted ac569406 Diff 97.3K/65536 BTM_SOC 0 pool 0 
Feb 15 21:02:01 (none) local0.notice bmminer: need data size:514, actual size:514
Feb 15 21:02:01 (none) local0.notice cgminer[999]: got nonce sz 514
Feb 15 21:02:01 (none) local0.notice cgminer[999]: Pool 0 stale share detected, submitting as user requested
Feb 15 21:02:01 (none) local0.notice cgminer[999]: cb_bitmain_submit_nonce nonce submited
Feb 15 21:02:01 (none) local0.notice cgminer[999]: Accepted 56f7828d Diff 193K/65536 BTM_SOC 0 pool 0 
Feb 15 21:02:04 (none) local0.notice cgminer[999]: update job
Feb 15 21:02:04 (none) local0.notice cgminer[999]: job buf total len:2631, offset:2631
Feb 15 21:02:04 (none) local0.notice cgminer[999]: about to send job, size is 2631
Feb 15 21:02:04 (none) local0.notice bmminer: bitmain_update_job_cb, rec job data 0xb4000480 size: 2631
Feb 15 21:02:04 (none) local0.notice bmminer: parse job buf len:2631
Feb 15 21:02:13 (none) local0.notice bmminer: need data size:514, actual size:514
Feb 15 21:02:13 (none) local0.notice cgminer[999]: got nonce sz 514
Feb 15 21:02:13 (none) local0.notice cgminer[999]: Pool 0 stale share detected, submitting as user requested
Feb 15 21:02:13 (none) local0.notice cgminer[999]: cb_bitmain_submit_nonce nonce submited
Feb 15 21:02:13 (none) local0.notice cgminer[999]: Accepted 55a0d2b0 Diff 196K/65536 BTM_SOC 0 pool 0 
2021-02-15 20:56:43 driver-btm-api.c:542:init_freq_mode: This is scan-user version
2021-02-15 20:56:43 driver-btm-api.c:1877:bitmain_soc_init: opt_multi_version     = 1
2021-02-15 20:56:43 driver-btm-api.c:1878:bitmain_soc_init: opt_bitmain_ab        = 1
2021-02-15 20:56:43 driver-btm-api.c:1879:bitmain_soc_init: opt_bitmain_work_mode = 1
2021-02-15 20:56:43 driver-btm-api.c:1880:bitmain_soc_init: Miner compile time: Mon Apr 27 13:25:08 CST 2020 type: Antminer S17
2021-02-15 20:56:43 driver-btm-api.c:1881:bitmain_soc_init: commit version: d22f356 2020-04-24 18:30:49, build by: lol 2020-04-27 13:31:45
2021-02-15 20:56:43 driver-btm-api.c:1691:show_sn: no SN got, please write SN to /nvdata/sn
2021-02-15 20:56:44 driver-btm-api.c:1040:miner_device_init: Detect 256MB control board of XILINX
2021-02-15 20:56:44 driver-btm-api.c:988:init_fan_parameter: fan_eft : 0  fan_pwm : 0
2021-02-15 20:56:44 thread.c:783:create_read_nonce_reg_thread: create thread
2021-02-15 20:56:50 driver-btm-api.c:972:init_miner_version: miner ID : 80026d864e104814
2021-02-15 20:56:50 driver-btm-api.c:978:init_miner_version: FPGA Version = 0xB013
2021-02-15 20:56:55 driver-btm-api.c:616:get_product_id: product_id[0] = 0
2021-02-15 20:56:55 driver-btm-api.c:616:get_product_id: product_id[1] = 0
2021-02-15 20:56:55 driver-btm-api.c:616:get_product_id: product_id[2] = 0
2021-02-15 20:56:55 driver-btm-api.c:560:_set_project_type: project:0
2021-02-15 20:56:55 driver-btm-api.c:585:_set_project_type: Project type: Antminer S17 Pro
2021-02-15 20:56:55 driver-btm-api.c:596:dump_pcb_bom_version: Chain [0] PCB Version: 0x0101
2021-02-15 20:56:55 driver-btm-api.c:597:dump_pcb_bom_version: Chain [0] BOM Version: 0x0103
2021-02-15 20:56:55 driver-btm-api.c:596:dump_pcb_bom_version: Chain [1] PCB Version: 0x0101
2021-02-15 20:56:55 driver-btm-api.c:597:dump_pcb_bom_version: Chain [1] BOM Version: 0x0103
2021-02-15 20:56:55 driver-btm-api.c:596:dump_pcb_bom_version: Chain [2] PCB Version: 0x0101
2021-02-15 20:56:55 driver-btm-api.c:597:dump_pcb_bom_version: Chain [2] BOM Version: 0x0103
2021-02-15 20:56:57 driver-btm-api.c:1802:bitmain_board_init: Fan check passed.
2021-02-15 20:56:58 board.c:36:jump_and_app_check_restore_pic: chain[0] PIC jump to app
2021-02-15 20:57:00 board.c:40:jump_and_app_check_restore_pic: Check chain[0] PIC fw version=0xb9
2021-02-15 20:57:01 board.c:36:jump_and_app_check_restore_pic: chain[1] PIC jump to app
2021-02-15 20:57:03 board.c:40:jump_and_app_check_restore_pic: Check chain[1] PIC fw version=0xb9
2021-02-15 20:57:04 board.c:36:jump_and_app_check_restore_pic: chain[2] PIC jump to app
2021-02-15 20:57:06 board.c:40:jump_and_app_check_restore_pic: Check chain[2] PIC fw version=0xb9
2021-02-15 20:57:06 thread.c:778:create_pic_heart_beat_thread: create thread
2021-02-15 20:57:06 power_api.c:207:power_init: Power init:
2021-02-15 20:57:06 power_api.c:208:power_init: current_voltage_raw = 0
2021-02-15 20:57:06 power_api.c:209:power_init: highest_voltage_raw = 2100
2021-02-15 20:57:06 power_api.c:210:power_init: working_voltage_raw = 1830
2021-02-15 20:57:06 power_api.c:211:power_init: higher_voltage_raw  = 1950
2021-02-15 20:57:06 driver-btm-api.c:1812:bitmain_board_init: Enter 30s sleep to make sure power release finish.
2021-02-15 20:57:06 power_api.c:181:power_off: init gpio907
2021-02-15 20:57:38 power_api.c:251:set_to_highest_voltage: Set to voltage raw 2100, one step.
2021-02-15 20:57:40 power_api.c:87:check_voltage_multi: retry time: 0
2021-02-15 20:57:41 power_api.c:37:_get_avg_voltage: chain = 0, voltage = 21.185742
2021-02-15 20:57:43 power_api.c:37:_get_avg_voltage: chain = 1, voltage = 21.259218
2021-02-15 20:57:44 power_api.c:37:_get_avg_voltage: chain = 2, voltage = 21.216357
2021-02-15 20:57:44 power_api.c:50:_get_avg_voltage: average_voltage = 21.220439
2021-02-15 20:57:44 power_api.c:68:check_voltage: target_vol = 21.00, actural_vol = 21.22, check voltage passed.
2021-02-15 20:57:44 uart.c:71:set_baud: set fpga_baud to 115200
2021-02-15 20:57:55 driver-btm-api.c:915:check_asic_number_with_power_on: Chain[0]: find 48 asic, times 0
2021-02-15 20:58:06 driver-btm-api.c:915:check_asic_number_with_power_on: Chain[1]: find 48 asic, times 0
2021-02-15 20:58:17 driver-btm-api.c:915:check_asic_number_with_power_on: Chain[2]: find 48 asic, times 0
2021-02-15 20:58:22 driver-btm-api.c:345:set_order_clock: chain[0]: set order clock, stragegy 3
2021-02-15 20:58:22 driver-btm-api.c:345:set_order_clock: chain[1]: set order clock, stragegy 3
2021-02-15 20:58:22 driver-btm-api.c:345:set_order_clock: chain[2]: set order clock, stragegy 3
2021-02-15 20:58:22 driver-hash-chip.c:502:set_clock_delay_control: core_data = 0x34
2021-02-15 20:58:22 uart.c:71:set_baud: set fpga_baud to 3000000
2021-02-15 20:58:22 driver-btm-api.c:1574:check_clock_counter: freq 50 clock_counter_limit 6
2021-02-15 20:58:24 uart.c:71:set_baud: set fpga_baud to 115200
2021-02-15 20:58:25 voltage[0] = 1780
2021-02-15 20:58:25 voltage[1] = 1800
2021-02-15 20:58:25 voltage[2] = 1780
2021-02-15 20:58:25 Voltage are different. Will exit.
2021-02-15 20:58:26 temperature.c:281:calibrate_temp_sensor_one_chain: Temperature sensor calibration: chain 0 success.
2021-02-15 20:58:27 temperature.c:281:calibrate_temp_sensor_one_chain: Temperature sensor calibration: chain 1 success.
2021-02-15 20:58:29 temperature.c:281:calibrate_temp_sensor_one_chain: Temperature sensor calibration: chain 2 success.
2021-02-15 20:58:29 uart.c:71:set_baud: set fpga_baud to 6000000
2021-02-15 20:58:30 driver-btm-api.c:245:check_bringup_temp: Bring up temperature is 18
2021-02-15 20:58:30 thread.c:798:create_check_miner_status_thread: create thread
2021-02-15 20:58:30 thread.c:788:create_set_miner_status_thread: create thread
2021-02-15 20:58:30 thread.c:773:create_temperature_monitor_thread: create thread
2021-02-15 20:58:30 frequency.c:749:inc_freq_with_fixed_vco: chain = 255, freq = 565, is_higher_voltage = true
2021-02-15 20:58:30 power_api.c:287:set_to_voltage_by_steps: Set to voltage raw 2020, step by step.
2021-02-15 20:58:49 power_api.c:87:check_voltage_multi: retry time: 0
2021-02-15 20:58:50 power_api.c:37:_get_avg_voltage: chain = 0, voltage = 20.334638
2021-02-15 20:58:51 power_api.c:37:_get_avg_voltage: chain = 1, voltage = 20.414238
2021-02-15 20:58:52 power_api.c:37:_get_avg_voltage: chain = 2, voltage = 20.365254
2021-02-15 20:58:52 power_api.c:50:_get_avg_voltage: average_voltage = 20.371377
2021-02-15 20:58:52 power_api.c:68:check_voltage: target_vol = 20.20, actural_vol = 20.37, check voltage passed.
2021-02-15 20:59:09 temperature.c:695:get_temp_info: read temp sensor failed: chain = 1, sensor = 0, chip = 55, reg = 0
2021-02-15 20:59:11 temperature.c:695:get_temp_info: read temp sensor failed: chain = 1, sensor = 0, chip = 55, reg = 1
2021-02-15 20:59:11 temperature.c:695:get_temp_info: read temp sensor failed: chain = 1, sensor = 1, chip = 40, reg = 0
2021-02-15 20:59:13 temperature.c:695:get_temp_info: read temp sensor failed: chain = 1, sensor = 1, chip = 40, reg = 1
2021-02-15 20:59:13 temperature.c:695:get_temp_info: read temp sensor failed: chain = 1, sensor = 2, chip = 180, reg = 0
2021-02-15 20:59:15 temperature.c:695:get_temp_info: read temp sensor failed: chain = 1, sensor = 2, chip = 180, reg = 1
2021-02-15 20:59:15 temperature.c:695:get_temp_info: read temp sensor failed: chain = 1, sensor = 3, chip = 195, reg = 0
2021-02-15 20:59:17 temperature.c:695:get_temp_info: read temp sensor failed: chain = 1, sensor = 3, chip = 195, reg = 1
2021-02-15 20:59:20 temperature.c:695:get_temp_info: read temp sensor failed: chain = 1, sensor = 0, chip = 55, reg = 0
2021-02-15 20:59:21 temperature.c:695:get_temp_info: read temp sensor failed: chain = 1, sensor = 0, chip = 55, reg = 1
2021-02-15 20:59:22 temperature.c:695:get_temp_info: read temp sensor failed: chain = 1, sensor = 1, chip = 40, reg = 0
2021-02-15 20:59:22 power_api.c:287:set_to_voltage_by_steps: Set to voltage raw 1900, step by step.
2021-02-15 20:59:23 temperature.c:695:get_temp_info: read temp sensor failed: chain = 1, sensor = 1, chip = 40, reg = 1
2021-02-15 20:59:23 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 1, chip = 180, reg = 28, got chain = 1, chip = 40, reg = 28
2021-02-15 20:59:42 power_api.c:87:check_voltage_multi: retry time: 0
2021-02-15 20:59:43 power_api.c:37:_get_avg_voltage: chain = 0, voltage = 19.097783
2021-02-15 20:59:44 power_api.c:37:_get_avg_voltage: chain = 1, voltage = 19.195752
2021-02-15 20:59:45 power_api.c:37:_get_avg_voltage: chain = 2, voltage = 19.116152
2021-02-15 20:59:45 power_api.c:50:_get_avg_voltage: average_voltage = 19.136562
2021-02-15 20:59:45 power_api.c:68:check_voltage: target_vol = 19.00, actural_vol = 19.14, check voltage passed.
2021-02-15 20:59:51 frequency.c:801:inc_freq_with_fixed_step: chain = 0, freq_start = 565, freq_end = 590, freq_step = 5, is_higher_voltage = true
2021-02-15 20:59:51 power_api.c:287:set_to_voltage_by_steps: Set to voltage raw 1880, step by step.
2021-02-15 21:00:10 power_api.c:87:check_voltage_multi: retry time: 0
2021-02-15 21:00:11 power_api.c:37:_get_avg_voltage: chain = 0, voltage = 18.889599
2021-02-15 21:00:12 power_api.c:37:_get_avg_voltage: chain = 1, voltage = 18.969199
2021-02-15 21:00:13 power_api.c:37:_get_avg_voltage: chain = 2, voltage = 18.883476
2021-02-15 21:00:13 power_api.c:50:_get_avg_voltage: average_voltage = 18.914092
2021-02-15 21:00:13 power_api.c:68:check_voltage: target_vol = 18.80, actural_vol = 18.91, check voltage passed.
2021-02-15 21:00:15 frequency.c:801:inc_freq_with_fixed_step: chain = 2, freq_start = 565, freq_end = 590, freq_step = 5, is_higher_voltage = true
2021-02-15 21:00:18 frequency.c:801:inc_freq_with_fixed_step: chain = 0, freq_start = 590, freq_end = 590, freq_step = 5, is_higher_voltage = true
2021-02-15 21:00:18 frequency.c:801:inc_freq_with_fixed_step: chain = 2, freq_start = 590, freq_end = 590, freq_step = 5, is_higher_voltage = true
2021-02-15 21:00:18 frequency.c:618:inc_asic_diff_freq_by_steps: chain = 1, start = 565, freq_step = 5
2021-02-15 21:00:21 driver-btm-api.c:528:set_timeout: freq = 595, percent = 90, hcn = 73728, timeout = 123
2021-02-15 21:00:21 power_api.c:225:set_higher_voltage_raw: higher_voltage_raw = 1900
2021-02-15 21:00:21 power_api.c:281:set_to_higher_voltage_by_steps: Set to voltage raw 1900, step by step.
2021-02-15 21:00:39 power_api.c:87:check_voltage_multi: retry time: 0
2021-02-15 21:00:40 power_api.c:37:_get_avg_voltage: chain = 0, voltage = 19.073291
2021-02-15 21:00:42 power_api.c:37:_get_avg_voltage: chain = 1, voltage = 19.116152
2021-02-15 21:00:43 power_api.c:37:_get_avg_voltage: chain = 2, voltage = 19.067168
2021-02-15 21:00:43 power_api.c:50:_get_avg_voltage: average_voltage = 19.085537
2021-02-15 21:00:43 power_api.c:68:check_voltage: target_vol = 19.00, actural_vol = 19.09, check voltage passed.
2021-02-15 21:00:43 thread.c:793:create_check_system_status_thread: create thread
2021-02-15 21:00:43 driver-btm-api.c:1988:bitmain_soc_init: Init done!
2021-02-15 21:00:43 driver-btm-api.c:198:set_miner_status: STATUS_INIT
2021-02-15 21:00:47 driver-btm-api.c:198:set_miner_status: STATUS_OKAY
2021-02-15 21:00:48 frequency.c:216:get_ideal_hash_rate_GH: ideal_hash_rate = 55871
2021-02-15 21:00:48 frequency.c:236:get_sale_hash_rate_GH: sale_hash_rate = 53000
2021-02-15 21:00:52 driver-btm-api.c:1199:dhash_chip_send_job: Version num 4
2021-02-15 21:01:02 temperature.c:695:get_temp_info: read temp sensor failed: chain = 1, sensor = 2, chip = 180, reg = 0
2021-02-15 21:01:04 temperature.c:695:get_temp_info: read temp sensor failed: chain = 1, sensor = 2, chip = 180, reg = 1
2021-02-15 21:01:05 temperature.c:695:get_temp_info: read temp sensor failed: chain = 1, sensor = 3, chip = 195, reg = 0
2021-02-15 21:01:06 temperature.c:695:get_temp_info: read temp sensor failed: chain = 1, sensor = 3, chip = 195, reg = 1
2021-02-15 21:01:09 temperature.c:695:get_temp_info: read temp sensor failed: chain = 1, sensor = 0, chip = 55, reg = 0
2021-02-15 21:01:10 temperature.c:695:get_temp_info: read temp sensor failed: chain = 1, sensor = 0, chip = 55, reg = 1
2021-02-15 21:01:11 temperature.c:695:get_temp_info: read temp sensor failed: chain = 1, sensor = 1, chip = 40, reg = 0
2021-02-15 21:01:12 temperature.c:695:get_temp_info: read temp sensor failed: chain = 1, sensor = 1, chip = 40, reg = 1
2021-02-15 21:01:13 temperature.c:695:get_temp_info: read temp sensor failed: chain = 1, sensor = 2, chip = 180, reg = 0
2021-02-15 21:01:14 temperature.c:695:get_temp_info: read temp sensor failed: chain = 1, sensor = 2, chip = 180, reg = 1
2021-02-15 21:01:15 temperature.c:695:get_temp_info: read temp sensor failed: chain = 1, sensor = 3, chip = 195, reg = 0
2021-02-15 21:01:17 temperature.c:695:get_temp_info: read temp sensor failed: chain = 1, sensor = 3, chip = 195, reg = 1
2021-02-15 21:01:19 temperature.c:695:get_temp_info: read temp sensor failed: chain = 1, sensor = 0, chip = 55, reg = 0
2021-02-15 21:01:21 temperature.c:695:get_temp_info: read temp sensor failed: chain = 1, sensor = 0, chip = 55, reg = 1
2021-02-15 21:01:21 temperature.c:695:get_temp_info: read temp sensor failed: chain = 1, sensor = 1, chip = 40, reg = 0
2021-02-15 21:01:23 temperature.c:695:get_temp_info: read temp sensor failed: chain = 1, sensor = 1, chip = 40, reg = 1
2021-02-15 21:01:23 temperature.c:695:get_temp_info: read temp sensor failed: chain = 1, sensor = 2, chip = 180, reg = 0
2021-02-15 21:01:25 temperature.c:695:get_temp_info: read temp sensor failed: chain = 1, sensor = 2, chip = 180, reg = 1
2021-02-15 21:01:26 temperature.c:695:get_temp_info: read temp sensor failed: chain = 1, sensor = 3, chip = 195, reg = 0
2021-02-15 21:01:27 temperature.c:695:get_temp_info: read temp sensor failed: chain = 1, sensor = 3, chip = 195, reg = 1
2021-02-15 21:01:29 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 1, chip = 55, reg = 28, got chain = 1, chip = 40, reg = 28
2021-02-15 21:01:29 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 1, chip = 55, reg = 28, got chain = 1, chip = 195, reg = 28
2021-02-15 21:01:30 temperature.c:695:get_temp_info: read temp sensor failed: chain = 1, sensor = 2, chip = 180, reg = 0
2021-02-15 21:01:36 temperature.c:695:get_temp_info: read temp sensor failed: chain = 1, sensor = 0, chip = 55, reg = 0
2021-02-15 21:01:37 temperature.c:695:get_temp_info: read temp sensor failed: chain = 1, sensor = 0, chip = 55, reg = 1
2021-02-15 21:01:38 temperature.c:695:get_temp_info: read temp sensor failed: chain = 1, sensor = 1, chip = 40, reg = 0
2021-02-15 21:01:39 temperature.c:695:get_temp_info: read temp sensor failed: chain = 1, sensor = 1, chip = 40, reg = 1
2021-02-15 21:01:40 temperature.c:695:get_temp_info: read temp sensor failed: chain = 1, sensor = 2, chip = 180, reg = 0
2021-02-15 21:01:41 temperature.c:695:get_temp_info: read temp sensor failed: chain = 1, sensor = 2, chip = 180, reg = 1
2021-02-15 21:01:42 temperature.c:695:get_temp_info: read temp sensor failed: chain = 1, sensor = 3, chip = 195, reg = 0
2021-02-15 21:01:43 temperature.c:695:get_temp_info: read temp sensor failed: chain = 1, sensor = 3, chip = 195, reg = 1
2021-02-15 21:01:46 temperature.c:695:get_temp_info: read temp sensor failed: chain = 1, sensor = 0, chip = 55, reg = 0
2021-02-15 21:01:48 temperature.c:695:get_temp_info: read temp sensor failed: chain = 1, sensor = 0, chip = 55, reg = 1
2021-02-15 21:01:48 temperature.c:695:get_temp_info: read temp sensor failed: chain = 1, sensor = 1, chip = 40, reg = 0
2021-02-15 21:01:50 temperature.c:695:get_temp_info: read temp sensor failed: chain = 1, sensor = 1, chip = 40, reg = 1
2021-02-15 21:01:51 temperature.c:695:get_temp_info: read temp sensor failed: chain = 1, sensor = 2, chip = 180, reg = 0
2021-02-15 21:01:52 temperature.c:695:get_temp_info: read temp sensor failed: chain = 1, sensor = 2, chip = 180, reg = 1
2021-02-15 21:01:53 temperature.c:695:get_temp_info: read temp sensor failed: chain = 1, sensor = 3, chip = 195, reg = 0
2021-02-15 21:01:54 temperature.c:695:get_temp_info: read temp sensor failed: chain = 1, sensor = 3, chip = 195, reg = 1
2021-02-15 21:01:57 temperature.c:695:get_temp_info: read temp sensor failed: chain = 1, sensor = 0, chip = 55, reg = 0
2021-02-15 21:01:58 temperature.c:695:get_temp_info: read temp sensor failed: chain = 1, sensor = 0, chip = 55, reg = 1
2021-02-15 21:01:59 temperature.c:695:get_temp_info: read temp sensor failed: chain = 1, sensor = 1, chip = 40, reg = 0
2021-02-15 21:02:00 temperature.c:695:get_temp_info: read temp sensor failed: chain = 1, sensor = 1, chip = 40, reg = 1
2021-02-15 21:02:01 temperature.c:695:get_temp_info: read temp sensor failed: chain = 1, sensor = 2, chip = 180, reg = 0
2021-02-15 21:02:02 temperature.c:695:get_temp_info: read temp sensor failed: chain = 1, sensor = 2, chip = 180, reg = 1
2021-02-15 21:02:03 temperature.c:695:get_temp_info: read temp sensor failed: chain = 1, sensor = 3, chip = 195, reg = 0
2021-02-15 21:02:04 temperature.c:695:get_temp_info: read temp sensor failed: chain = 1, sensor = 3, chip = 195, reg = 1
2021-02-15 21:02:07 temperature.c:695:get_temp_info: read temp sensor failed: chain = 1, sensor = 0, chip = 55, reg = 0
2021-02-15 21:02:09 temperature.c:695:get_temp_info: read temp sensor failed: chain = 1, sensor = 0, chip = 55, reg = 1
2021-02-15 21:02:09 temperature.c:695:get_temp_info: read temp sensor failed: chain = 1, sensor = 1, chip = 40, reg = 0
2021-02-15 21:02:11 temperature.c:695:get_temp_info: read temp sensor failed: chain = 1, sensor = 1, chip = 40, reg = 1
2021-02-15 21:02:12 temperature.c:695:get_temp_info: read temp sensor failed: chain = 1, sensor = 2, chip = 180, reg = 0
2021-02-15 21:02:13 temperature.c:695:get_temp_info: read temp sensor failed: chain = 1, sensor = 2, chip = 180, reg = 1
2021-02-15 21:02:14 temperature.c:695:get_temp_info: read temp sensor failed: chain = 1, sensor = 3, chip = 195, reg = 0

Bitcoin Forum>Bitcoin>Mining>Mining support
Jump to: