Antminer S17e Fan anomalies / unusual error

MinerMEDIC

member

Activity: 166

Merit: 82

EET/NASA intern 2013 Bitmain/MicroBT/IPC cert

From a theoretical standpoint you should always have your pairs of fans matched. If one starts spinning faster than the other or one reaches full speed before the other they are not matched. This means their impedance is not matched, in this state a failure within a short period of time is not unexpected. The front and the back have separate power sources so not all four need to be matched.

BitMaxz

legendary

Activity: 3234

Merit: 2943

Block halving is coming.

Why don't check the fan that you buy physically if you have a multimeter check the wires?

here's the color of the wires
- Black = Ground
- Red = + 12V
- Yellow = RPM signal
- Blue = PWM

The blue if this has an abnormal connection or it is disconnected the fan will run at full speed and yellow will report or it will give you the RPM speed.
So start checking the blue wire it might have cold solder joint resoldering the blue wire or replacing the wire sometimes it can fix this issue.

mikeywith

legendary

Activity: 2170

Merit: 6279

be constructive or S.T.F.U

I had the same issue with some cheap fans I bought, they were reporting 30k RPMs and then suddenly fan lost, i could not get them to work on stock firmware, I remember someone mention about cutting one of the wires but i did not bother to try it, so you might want to look into that direction.

danieleither

full member

Activity: 201

Merit: 404

I should add...

I've tried updating to latest Bitmain firmware. I've also tried using custom firmware(s) that offer fixed fan speed function (e.g. 90% or 100%), and these work perfectly and fan RPM's are reported 'normally' or what I would consider, from my experience, as correct / appropriate. Obviously this is a workaround, but since I have no wish to run the miners under or over 'normal' clock speed, I'd prefer to use standard Bitmain firmware at zero additional cost.

danieleither

full member

Activity: 201

Merit: 404

I recently purchased a quantity of new fans and PSU's directly from Bitmain, in order to service some old S17e 60T I've had since new. I am getting a strange 'fan lost' error where the firmware seems to think the fans are spinning much slower than they really are. I have installed to a number of units and all return this same problem. I have also tried mixing and matching, (old fans and new) and every time these new fans return this strange low speed error in the kernel. In the example below, at first it appears that fan id 3 is the issue, however on next reboot it will be a different fan id that it thinks is missing (e.g. random each time).#

I've used some fans from this same batch on 19-series and they function normally and report normal RPM.

These are the fans: (Nidec W12E12BS11B5-57)

Kernel 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: 195688K/245760K available (6345K kernel code, 231K rwdata, 1896K rodata, 1024K init, 223K bss, 33688K 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: 20648K (cc6d7000 - cdb01000)
hw perfevents: enabled with armv7_cortex_a9 PMU driver, 7 counters available
futex hash table entries: 512 (order: 3, 32768 bytes)
workingset: timestamp_bits=28 max_order=16 bucket_order=0
jffs2: version 2.2. (NAND) (SUMMARY)  © 2001-2006 Red Hat, Inc.
io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered (default)
dma-pl330 f8003000.ps7-dma: Loaded driver for PL330 DMAC-241330
dma-pl330 f8003000.ps7-dma: 	DBUFF-128x8bytes Num_Chans-8 Num_Peri-4 Num_Events-16
e0000000.serial: ttyPS0 at MMIO 0xe0000000 (irq = 158, base_baud = 6249999) is a xuartps
console [ttyPS0] enabled
xdevcfg f8007000.ps7-dev-cfg: ioremap 0xf8007000 to cf86e000
[drm] Initialized drm 1.1.0 20060810
brd: module loaded
loop: module loaded
CAN device driver interface
gpiod_set_value: invalid GPIO
libphy: MACB_mii_bus: probed
macb e000b000.ethernet eth0: Cadence GEM rev 0x00020118 at 0xe000b000 irq 31 (00:0a:35:00:00:00)
Generic PHY e000b000.etherne:00: attached PHY driver [Generic PHY] (mii_bus:phy_addr=e000b000.etherne:00, irq=-1)
e1000e: Intel(R) PRO/1000 Network Driver - 3.2.6-k
e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
ehci-pci: EHCI PCI platform driver
usbcore: registered new interface driver usb-storage
mousedev: PS/2 mouse device common for all mice
i2c /dev entries driver
Xilinx Zynq CpuIdle Driver started
sdhci: Secure Digital Host Controller Interface driver
sdhci: Copyright(c) Pierre Ossman
sdhci-pltfm: SDHCI platform and OF driver helper
mmc0: SDHCI controller on e0100000.ps7-sdio [e0100000.ps7-sdio] using ADMA
ledtrig-cpu: registered to indicate activity on CPUs
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
nand: device found, Manufacturer ID: 0x2c, Chip ID: 0xda
nand: Micron MT29F2G08ABAEAWP
nand: 256 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 64
nand: WARNING: pl35x-nand: the ECC used on your system is too weak compared to the one required by the NAND chip
Bad block table found at page 131008, version 0x01
Bad block table found at page 130944, version 0x01
6 ofpart partitions found on MTD device pl35x-nand
Creating 6 MTD partitions on "pl35x-nand":
0x000000000000-0x000002800000 : "BOOT.bin-env-dts-kernel"
0x000002800000-0x000004800000 : "ramfs"
0x000004800000-0x000005000000 : "configs"
0x000005000000-0x000006000000 : "reserve"
0x000006000000-0x000008000000 : "ramfs-bak"
0x000008000000-0x000010000000 : "reserve1"
NET: Registered protocol family 10
sit: IPv6 over IPv4 tunneling driver
NET: Registered protocol family 17
can: controller area network core (rev 20120528 abi 9)
NET: Registered protocol family 29
can: raw protocol (rev 20120528)
can: broadcast manager protocol (rev 20120528 t)
can: netlink gateway (rev 20130117) max_hops=1
zynq_pm_ioremap: no compatible node found for 'xlnx,zynq-ddrc-a05'
zynq_pm_late_init: Unable to map DDRC IO memory.
Registering SWP/SWPB emulation handler
hctosys: unable to open rtc device (rtc0)
ALSA device list:
  No soundcards found.
RAMDISK: gzip image found at block 0
EXT4-fs (ram0): couldn't mount as ext3 due to feature incompatibilities
EXT4-fs (ram0): mounted filesystem without journal. Opts: (null)
VFS: Mounted root (ext4 filesystem) on device 1:0.
devtmpfs: mounted
Freeing unused kernel memory: 1024K (c0a00000 - c0b00000)
EXT4-fs (ram0): re-mounted. Opts: block_validity,delalloc,barrier,user_xattr
random: dd urandom read with 0 bits of entropy available
ubi0: attaching mtd2
ubi0: scanning is finished
ubi0: attached mtd2 (name "configs", size 8 MiB)
ubi0: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
ubi0: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
ubi0: VID header offset: 2048 (aligned 2048), data offset: 4096
ubi0: good PEBs: 64, bad PEBs: 0, corrupted PEBs: 0
ubi0: user volume: 1, internal volumes: 1, max. volumes count: 128
ubi0: max/mean erase counter: 7/3, WL threshold: 4096, image sequence number: 2561576031
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 EF5A3011-AA5B-4A54-BCBC-0D453CFD6984, 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: 30010/27943, WL threshold: 4096, image sequence number: 106770571
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 BE99ABA8-7185-4600-9ACA-3B24BD557263, 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 0xcfb54000
*base_vir_addr = 0xb023
In fpga mem driver!
request_mem_region OK!
fpga mem virtual address is 0xd2000000
random: nonblocking pool is initialized
2022-08-20 15:30:02:thread.c:1555:create_bitmain_soc_init_thread: create thread
2022-08-20 15:30:02:driver-btm-api.c:682:init_freq_mode: This is scan-user version
2022-08-20 15:30:02:driver-btm-api.c:2518:bitmain_soc_init: Miner compile time: Fri Jan  8 22:31:06 CST 2021 type: Antminer S17e
2022-08-20 15:30:02:driver-btm-api.c:2519:bitmain_soc_init: commit version: 37668c9 2021-01-08 18:20:11, build by: jenkins 2021-01-08 22:35:52
2022-08-20 15:30:02:driver-btm-api.c:2520:bitmain_soc_init: opt_multi_version     = 1
2022-08-20 15:30:02:driver-btm-api.c:2521:bitmain_soc_init: opt_bitmain_ab        = 1
2022-08-20 15:30:02:driver-btm-api.c:2522:bitmain_soc_init: mid_auto_gen          = 0
2022-08-20 15:30:02:driver-btm-api.c:2523:bitmain_soc_init: work_mode             = 0
2022-08-20 15:30:02:driver-btm-api.c:2524:bitmain_soc_init: power_feedback_en     = true
2022-08-20 15:30:02:driver-btm-api.c:2067:show_sn: no SN got, please write SN to /config/sn
2022-08-20 15:30:02:driver-btm-api.c:1384:miner_device_init: Detect 256MB control board of XILINX
2022-08-20 15:30:02:driver-btm-api.c:1325:init_fan_parameter: fan_eft : 0  fan_pwm : 0
2022-08-20 15:30:08:driver-btm-api.c:1309:init_miner_version: miner ID : 803444c67510481c
2022-08-20 15:30:08:driver-btm-api.c:1315:init_miner_version: FPGA Version = 0xB023
2022-08-20 15:30:14:auto_adapt.c:100:_get_board_info: chain[0] board bin: 10, chip bin: 3, chip ft: A193V1, chip version: AB
2022-08-20 15:30:14:auto_adapt.c:100:_get_board_info: chain[1] board bin: 10, chip bin: 3, chip ft: A193V1, chip version: AB
2022-08-20 15:30:14:auto_adapt.c:100:_get_board_info: chain[2] board bin: 10, chip bin: 3, chip ft: A193V1, chip version: AB
2022-08-20 15:30:14:auto_adapt.c:273:is_sweep_failed_before: open sweep tag failed
voltage_ref = 1850
2100  2100  2100  2100  2100  2100  
2100  2100  2100  2100  2100  2100  
2100  2100  2100  2100  2090  2050  
2100  2090  2080  2060  2030  1960  
2080  2060  2030  2010  1960  1910  

2022-08-20 15:30:14:thread.c:1523:create_read_nonce_reg_thread: create thread
2022-08-20 15:30:14:driver-btm-api.c:698:dump_pcb_bom_version: Chain [0] PCB Version: 0x0128
2022-08-20 15:30:14:driver-btm-api.c:699:dump_pcb_bom_version: Chain [0] BOM Version: 0x0100
2022-08-20 15:30:14:driver-btm-api.c:698:dump_pcb_bom_version: Chain [1] PCB Version: 0x0128
2022-08-20 15:30:14:driver-btm-api.c:699:dump_pcb_bom_version: Chain [1] BOM Version: 0x0100
2022-08-20 15:30:14:driver-btm-api.c:698:dump_pcb_bom_version: Chain [2] PCB Version: 0x0128
2022-08-20 15:30:14:driver-btm-api.c:699:dump_pcb_bom_version: Chain [2] BOM Version: 0x0100
2022-08-20 15:30:20:driver-btm-api.c:2344:bitmain_board_init: Fan check passed.
2022-08-20 15:30:21:board.c:81:jump_and_app_check_restore_pic: chain[0] PIC jump to app
2022-08-20 15:30:23:board.c:94:jump_and_app_check_restore_pic: Check chain[0] PIC fw version=0xb9
2022-08-20 15:30:24:board.c:81:jump_and_app_check_restore_pic: chain[1] PIC jump to app
2022-08-20 15:30:27:board.c:94:jump_and_app_check_restore_pic: Check chain[1] PIC fw version=0xb9
2022-08-20 15:30:28:board.c:81:jump_and_app_check_restore_pic: chain[2] PIC jump to app
2022-08-20 15:30:30:board.c:94:jump_and_app_check_restore_pic: Check chain[2] PIC fw version=0xb9
2022-08-20 15:30:30:thread.c:1518:create_pic_heart_beat_thread: create thread
2022-08-20 15:30:31:power_api.c:241:power_init: power type version: 0x0042
2022-08-20 15:30:33:power_api.c:259:power_init: Power init:
2022-08-20 15:30:33:power_api.c:260:power_init: current_voltage_raw     = 2136
2022-08-20 15:30:33:power_api.c:261:power_init: highest_voltage_raw     = 2000
2022-08-20 15:30:33:power_api.c:262:power_init: working_voltage_raw     = 1800
2022-08-20 15:30:33:power_api.c:263:power_init: higher_voltage_raw      = 1850
2022-08-20 15:30:33:power_api.c:264:power_init: check_asic_voltage_raw  = 1800
2022-08-20 15:30:33:driver-btm-api.c:2354:bitmain_board_init: Enter 60s sleep to make sure power release finish.
2022-08-20 15:31:35:driver-btm-api.c:1123:check_asic_number_until_volt_balance: THIS is No.1 time boost asic:
2022-08-20 15:31:35:power_api.c:334:modify_check_asic_voltage: check_asic_voltage_raw  = 1800
2022-08-20 15:31:38:power_api.c:298:set_to_check_asic_voltage_by_steps: Set to voltage raw 1800, step by step.
2022-08-20 15:32:06:uart.c:69:set_baud: set UART baud to 115200
chain 0, IO_DRIVE_STRENGTH_CONFIGURATION reg = 0x 7777777
2022-08-20 15:32:11:driver-btm-api.c:1035:check_asic_number_with_power_on: Chain[0]: find 135 asic, times 0
chain 1, IO_DRIVE_STRENGTH_CONFIGURATION reg = 0x 7777777
2022-08-20 15:32:15:driver-btm-api.c:1035:check_asic_number_with_power_on: Chain[1]: find 135 asic, times 0
chain 2, IO_DRIVE_STRENGTH_CONFIGURATION reg = 0x 7777777
2022-08-20 15:32:19:driver-btm-api.c:1035:check_asic_number_with_power_on: Chain[2]: find 61 asic, times 0
2022-08-20 15:32:21:board.c:81:jump_and_app_check_restore_pic: chain[2] PIC jump to app
2022-08-20 15:32:23:board.c:94:jump_and_app_check_restore_pic: Check chain[2] PIC fw version=0xb9
chain 2, IO_DRIVE_STRENGTH_CONFIGURATION reg = 0x 7777777
2022-08-20 15:32:27:driver-btm-api.c:1035:check_asic_number_with_power_on: Chain[2]: find 63 asic, times 1
2022-08-20 15:32:28:board.c:81:jump_and_app_check_restore_pic: chain[2] PIC jump to app
2022-08-20 15:32:30:board.c:94:jump_and_app_check_restore_pic: Check chain[2] PIC fw version=0xb9
chain 2, IO_DRIVE_STRENGTH_CONFIGURATION reg = 0x 7777777
2022-08-20 15:32:35:driver-btm-api.c:1035:check_asic_number_with_power_on: Chain[2]: find 62 asic, times 2
2022-08-20 15:32:36:board.c:81:jump_and_app_check_restore_pic: chain[2] PIC jump to app
2022-08-20 15:32:38:board.c:94:jump_and_app_check_restore_pic: Check chain[2] PIC fw version=0xb9
chain 2, IO_DRIVE_STRENGTH_CONFIGURATION reg = 0x 7777777
2022-08-20 15:32:42:driver-btm-api.c:1035:check_asic_number_with_power_on: Chain[2]: find 62 asic, times 3
2022-08-20 15:32:43:board.c:81:jump_and_app_check_restore_pic: chain[2] PIC jump to app
2022-08-20 15:32:45:board.c:94:jump_and_app_check_restore_pic: Check chain[2] PIC fw version=0xb9
2022-08-20 15:32:45:driver-btm-api.c:1217:check_asic_number: Chain 2 only find 62 asic, will power off hash board 2
2022-08-20 15:32:46:driver-btm-api.c:1163:check_asic_number_until_volt_balance: PASS: volt balance at No.1 time boost asic.
2022-08-20 15:32:46:power_api.c:364:set_to_highest_voltage_by_steps: Set to voltage raw 2000, step by step.
2022-08-20 15:33:22:driver-hash-chip.c:876:set_uart_relay: set uart relay to 0x390003
2022-08-20 15:33:22:driver-hash-chip.c:1264:set_ldo_ctrl: Set LDO to 0x2000203
2022-08-20 15:33:22:driver-hash-chip.c:737:dump_adc_voltage_v2: get ADC_DATAOUT from chain 0 with 0 regs timeout.
chain 0 domain  0:   d0 0.339,   d1 0.342,   d2 0.338,   d3 0.340,   sum = 1.359172
chain 0 domain  1:   d0 0.340,   d1 0.341,   d2 0.341,   d3 0.342,   sum = 1.364624
chain 0 domain  2:   d0 0.341,   d1 0.344,   d2 0.338,   d3 0.340,   sum = 1.363729
chain 0 domain  3:   d0 0.332,   d1 0.331,   d2 0.327,   d3 0.330,   sum = 1.320516
chain 0 domain  4:   d0 0.329,   d1 0.333,   d2 0.329,   d3 0.331,   sum = 1.321655
chain 0 domain  5:   d0 0.332,   d1 0.332,   d2 0.326,   d3 0.328,   sum = 1.318563
chain 0 domain  6:   d0 0.316,   d1 0.318,   d2 0.316,   d3 0.319,   sum = 1.269084
chain 0 domain  7:   d0 0.343,   d1 0.343,   d2 0.340,   d3 0.341,   sum = 1.366455
chain 0 domain  8:   d0 0.331,   d1 0.333,   d2 0.329,   d3 0.331,   sum = 1.324137
chain 0 domain  9:   d0 0.326,   d1 0.324,   d2 0.320,   d3 0.320,   sum = 1.289307
chain 0 domain 10:   d0 0.334,   d1 0.338,   d2 0.334,   d3 0.336,   sum = 1.343180
chain 0 domain 11:   d0 0.334,   d1 0.335,   d2 0.330,   d3 0.331,   sum = 1.330688
chain 0 domain 12:   d0 0.331,   d1 0.335,   d2 0.330,   d3 0.332,   sum = 1.327637
chain 0 domain 13:   d0 0.324,   d1 0.324,   d2 0.322,   d3 0.323,   sum = 1.292806
chain 0 domain 14:   d0 0.333,   d1 0.335,   d2 0.331,   d3 0.334,   sum = 1.332845
2022-08-20 15:33:23:driver-hash-chip.c:737:dump_adc_voltage_v2: get ADC_DATAOUT from chain 1 with 0 regs timeout.
chain 1 domain  0:   d0 0.339,   d1 0.346,   d2 0.339,   d3 0.333,   sum = 1.357137
chain 1 domain  1:   d0 0.340,   d1 0.344,   d2 0.341,   d3 0.333,   sum = 1.359497
chain 1 domain  2:   d0 0.319,   d1 0.327,   d2 0.324,   d3 0.319,   sum = 1.289022
chain 1 domain  3:   d0 0.322,   d1 0.326,   d2 0.319,   d3 0.310,   sum = 1.276896
chain 1 domain  4:   d0 0.331,   d1 0.339,   d2 0.334,   d3 0.336,   sum = 1.339600
chain 1 domain  5:   d0 0.331,   d1 0.335,   d2 0.329,   d3 0.322,   sum = 1.317627
chain 1 domain  6:   d0 0.330,   d1 0.337,   d2 0.331,   d3 0.329,   sum = 1.327759
chain 1 domain  7:   d0 0.337,   d1 0.341,   d2 0.333,   d3 0.331,   sum = 1.340983
chain 1 domain  8:   d0 0.326,   d1 0.333,   d2 0.327,   d3 0.321,   sum = 1.306600
chain 1 domain  9:   d0 0.333,   d1 0.336,   d2 0.329,   d3 0.324,   sum = 1.322062
chain 1 domain 10:   d0 0.334,   d1 0.341,   d2 0.332,   d3 0.331,   sum = 1.337565
chain 1 domain 11:   d0 0.334,   d1 0.339,   d2 0.336,   d3 0.333,   sum = 1.341187
chain 1 domain 12:   d0 0.326,   d1 0.332,   d2 0.330,   d3 0.329,   sum = 1.316325
chain 1 domain 13:   d0 0.336,   d1 0.338,   d2 0.333,   d3 0.330,   sum = 1.336304
chain 1 domain 14:   d0 0.334,   d1 0.336,   d2 0.330,   d3 0.327,   sum = 1.326009
2022-08-20 15:33:23:driver-hash-chip.c:493:check_adc_voltage: PASS domainn volt check: request 0.800 (index 0, open_core)
2022-08-20 15:33:24:temperature.c:272:calibrate_temp_sensor_one_chain: chain 0 temp sensor NCT218
2022-08-20 15:33:26:temperature.c:272:calibrate_temp_sensor_one_chain: chain 1 temp sensor NCT218
2022-08-20 15:33:31:driver-btm-api.c:311:check_bringup_temp: Bring up temperature is 29
2022-08-20 15:33:31:uart.c:69:set_baud: set UART baud to 6000000
2022-08-20 15:33:31 voltage[0] = 1850
2022-08-20 15:33:31 voltage[1] = 1850
2022-08-20 15:33:31:power_api.c:272:set_working_voltage_raw: working_voltage_raw = 1850
2022-08-20 15:33:31:thread.c:1538:create_check_miner_status_thread: create thread
2022-08-20 15:33:31:thread.c:1528:create_show_miner_status_thread: create thread
2022-08-20 15:33:31:thread.c:1503:create_temperature_monitor_thread: create thread
2022-08-20 15:33:31:thread.c:1580:create_fan_monitor_thread: create thread
2022-08-20 15:33:31:frequency.c:578:inc_freq_with_fixed_vco: chain = 255, freq = 360, is_higher_voltage = true
2022-08-20 15:33:37:frequency.c:623:inc_freq_with_fixed_vco: get pcb 29 ~ 31, chip_temp 32 ~ 37, now 6.0s, target 37.0
2022-08-20 15:33:38:frequency.c:623:inc_freq_with_fixed_vco: get pcb 29 ~ 32, chip_temp 32 ~ 38, now 7.0s, target 37.2
2022-08-20 15:33:38:frequency.c:644:inc_freq_with_fixed_vco: heat speed too fast! current_temp 38 > 37.2 target_temp.
2022-08-20 15:33:44:frequency.c:623:inc_freq_with_fixed_vco: get pcb 30 ~ 32, chip_temp 33 ~ 39, now 13.0s, target 38.2
2022-08-20 15:33:44:frequency.c:644:inc_freq_with_fixed_vco: heat speed too fast! current_temp 39 > 38.2 target_temp.
2022-08-20 15:33:50:frequency.c:623:inc_freq_with_fixed_vco: get pcb 30 ~ 33, chip_temp 33 ~ 42, now 19.0s, target 39.2
2022-08-20 15:33:50:frequency.c:644:inc_freq_with_fixed_vco: heat speed too fast! current_temp 42 > 39.2 target_temp.
2022-08-20 15:33:56:frequency.c:623:inc_freq_with_fixed_vco: get pcb 31 ~ 35, chip_temp 34 ~ 44, now 25.0s, target 40.2
2022-08-20 15:33:56:frequency.c:644:inc_freq_with_fixed_vco: heat speed too fast! current_temp 44 > 40.2 target_temp.
2022-08-20 15:34:02:frequency.c:623:inc_freq_with_fixed_vco: get pcb 32 ~ 36, chip_temp 35 ~ 45, now 31.0s, target 41.2
2022-08-20 15:34:02:frequency.c:644:inc_freq_with_fixed_vco: heat speed too fast! current_temp 45 > 41.2 target_temp.
2022-08-20 15:34:08:frequency.c:623:inc_freq_with_fixed_vco: get pcb 32 ~ 37, chip_temp 35 ~ 48, now 37.0s, target 42.2
2022-08-20 15:34:08:frequency.c:644:inc_freq_with_fixed_vco: heat speed too fast! current_temp 48 > 42.2 target_temp.
2022-08-20 15:34:14:fan.c:149:check_fan_status: Error, fan lost, only find 3 (< 4)
2022-08-20 15:34:14:fan.c:152:check_fan_status: fan_id = 0, fan_speed = 480
2022-08-20 15:34:14:fan.c:152:check_fan_status: fan_id = 1, fan_speed = 480
2022-08-20 15:34:14:fan.c:152:check_fan_status: fan_id = 2, fan_speed = 480
2022-08-20 15:34:14:fan.c:152:check_fan_status: fan_id = 3, fan_speed = 360
2022-08-20 15:34:14:fan.c:152:check_fan_status: fan_id = 4, fan_speed = 0
2022-08-20 15:34:14:fan.c:152:check_fan_status: fan_id = 5, fan_speed = 0
2022-08-20 15:34:14:fan.c:152:check_fan_status: fan_id = 6, fan_speed = 0
2022-08-20 15:34:14:fan.c:152:check_fan_status: fan_id = 7, fan_speed = 0
2022-08-20 15:34:14:sweep_err.c:59:sweep_error_code_save2file: file /config/sweep_error_code already exists, do not overwrite it
2022-08-20 15:34:14:sweep_err.c:185:sweep_set_error_code: Sweep error string = F:1.
2022-08-20 15:34:14:driver-btm-api.c:247:set_miner_status: ERROR_FAN_LOST
2022-08-20 15:34:14:driver-btm-api.c:176:stop_mining: stop mining: fan lost
2022-08-20 15:34:14:thread.c:1611:cancel_check_miner_status_thread: cancel thread
2022-08-20 15:34:14:thread.c:1575:cancel_temperature_monitor_thread: cancel thread
2022-08-20 15:34:14:thread.c:1595:cancel_read_nonce_reg_thread: cancel thread
2022-08-20 15:34:14:thread.c:1631:cancel_bitmain_soc_init_thread: cancel thread
2022-08-20 15:34:14:driver-btm-api.c:147:killall_hashboard: ****power off hashboard****
2022-08-20 15:44:47:frequency.c:107:get_ideal_hash_rate_GH: ideal_hash_rate = 41103

Topic: Antminer S17e Fan anomalies / unusual error (Read 131 times)