S9K temperature related network failure - logs

[sxo13]

Hi all,

If somebody could help to interpret the S9K logs, it would be much appreciated.
My s9k models stopped working and I suspect it has to done with the changing environment temperature but cant interpret properly the logs due to lack of experience with them.
They are in an environment temperature of ~15C(10-20C) on a shelf along with other S9(all working normally) meaning that the hardware is constantly at around 30C at cold start. Earlier it was 5-10C warmer environment temp. here.
I flashed with the latest january firmware but no difference. Weird is, they all stopped to work with a few hours difference. Network setup is all ok, the issue is not there to find I assume.

The kernel log sample:

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: 203784K/245760K available (6345K kernel code, 231K rwdata, 1896K rodata, 1024K init, 223K bss, 25592K reserved, 16384K cma-reserved, 0K highmem)
Virtual kernel memory layout:
    vector  : 0xffff0000 - 0xffff1000   (   4 kB)
    fixmap  : 0xffc00000 - 0xfff00000   (3072 kB)
    vmalloc : 0xcf800000 - 0xff800000   ( 768 MB)
    lowmem  : 0xc0000000 - 0xcf000000   ( 240 MB)
    pkmap   : 0xbfe00000 - 0xc0000000   (   2 MB)
    modules : 0xbf000000 - 0xbfe00000   (  14 MB)
      .text : 0xc0008000 - 0xc090c424   (9234 kB)
      .init : 0xc0a00000 - 0xc0b00000   (1024 kB)
      .data : 0xc0b00000 - 0xc0b39fe0   ( 232 kB)
       .bss : 0xc0b39fe0 - 0xc0b71c28   ( 224 kB)
Preemptible hierarchical RCU implementation.
	Build-time adjustment of leaf fanout to 32.
	RCU restricting CPUs from NR_CPUS=4 to nr_cpu_ids=2.
RCU: Adjusting geometry for rcu_fanout_leaf=32, nr_cpu_ids=2
NR_IRQS:16 nr_irqs:16 16
efuse mapped to cf800000
ps7-slcr mapped to cf802000
L2C: platform modifies aux control register: 0x72360000 -> 0x72760000
L2C: DT/platform modifies aux control register: 0x72360000 -> 0x72760000
L2C-310 erratum 769419 enabled
L2C-310 enabling early BRESP for Cortex-A9
L2C-310 full line of zeros enabled for Cortex-A9
L2C-310 ID prefetch enabled, offset 1 lines
L2C-310 dynamic clock gating enabled, standby mode enabled
L2C-310 cache controller enabled, 8 ways, 512 kB
L2C-310: CACHE_ID 0x410000c8, AUX_CTRL 0x76760001
zynq_clock_init: clkc starts at cf802100
Zynq clock init
sched_clock: 64 bits at 333MHz, resolution 3ns, wraps every 4398046511103ns
clocksource: arm_global_timer: mask: 0xffffffffffffffff max_cycles: 0x4ce07af025, max_idle_ns: 440795209040 ns
Switching to timer-based delay loop, resolution 3ns
clocksource: ttc_clocksource: mask: 0xffff max_cycles: 0xffff, max_idle_ns: 537538477 ns
ps7-ttc #0 at cf80a000, irq=18
Console: colour dummy device 80x30
Calibrating delay loop (skipped), value calculated using timer frequency.. 666.66 BogoMIPS (lpj=3333333)
pid_max: default: 32768 minimum: 301
Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
CPU: Testing write buffer coherency: ok
CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
Setting up static identity map for 0x100000 - 0x100058
CPU1: failed to boot: -1
Brought up 1 CPUs
SMP: Total of 1 processors activated (666.66 BogoMIPS).
CPU: All CPU(s) started in SVC mode.
devtmpfs: initialized
VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4
clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
pinctrl core: initialized pinctrl subsystem
NET: Registered protocol family 16
DMA: preallocated 256 KiB pool for atomic coherent allocations
cpuidle: using governor menu
hw-breakpoint: found 5 (+1 reserved) breakpoint and 1 watchpoint registers.
hw-breakpoint: maximum watchpoint size is 4 bytes.
zynq-ocm f800c000.ps7-ocmc: ZYNQ OCM pool: 256 KiB @ 0xcf880000
vgaarb: loaded
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
media: Linux media interface: v0.10
Linux video capture interface: v2.00
pps_core: LinuxPPS API ver. 1 registered
pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
PTP clock support registered
EDAC MC: Ver: 3.0.0
Advanced Linux Sound Architecture Driver Initialized.
clocksource: Switched to clocksource arm_global_timer
NET: Registered protocol family 2
TCP established hash table entries: 2048 (order: 1, 8192 bytes)
TCP bind hash table entries: 2048 (order: 2, 16384 bytes)
TCP: Hash tables configured (established 2048 bind 2048)
UDP hash table entries: 256 (order: 1, 8192 bytes)
UDP-Lite hash table entries: 256 (order: 1, 8192 bytes)
NET: Registered protocol family 1
RPC: Registered named UNIX socket transport module.
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
PCI: CLS 0 bytes, default 64
Trying to unpack rootfs image as initramfs...
rootfs image is not initramfs (no cpio magic); looks like an initrd
Freeing initrd memory: 12552K (ccebe000 - 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)
Broadcom BCM5241 e000b000.etherne:00: attached PHY driver [Broadcom BCM5241] (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: 19/9, WL threshold: 4096, image sequence number: 237714726
ubi0: available PEBs: 0, total reserved PEBs: 64, PEBs reserved for bad PEB handling: 40
ubi0: background thread "ubi_bgt0d" started, PID 708
UBIFS (ubi0:0): background thread "ubifs_bgt0_0" started, PID 711
UBIFS (ubi0:0): UBIFS: mounted UBI device 0, volume 0, name "configs"
UBIFS (ubi0:0): LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
UBIFS (ubi0:0): FS size: 1396736 bytes (1 MiB, 11 LEBs), journal size 888833 bytes (0 MiB, 5 LEBs)
UBIFS (ubi0:0): reserved for root: 65970 bytes (64 KiB)
UBIFS (ubi0:0): media format: w4/r0 (latest is w4/r0), UUID FF09433B-E002-4C29-97EC-6220DDC4BB36, small LPT model
ubi1: attaching mtd5
ubi1: scanning is finished
ubi1: attached mtd5 (name "reserve1", size 128 MiB)
ubi1: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
ubi1: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
ubi1: VID header offset: 2048 (aligned 2048), data offset: 4096
ubi1: good PEBs: 1020, bad PEBs: 4, corrupted PEBs: 0
ubi1: user volume: 1, internal volumes: 1, max. volumes count: 128
ubi1: max/mean erase counter: 26/12, WL threshold: 4096, image sequence number: 914180297
ubi1: available PEBs: 0, total reserved PEBs: 1020, PEBs reserved for bad PEB handling: 36
ubi1: background thread "ubi_bgt1d" started, PID 720
UBIFS (ubi1:0): background thread "ubifs_bgt1_0" started, PID 723
UBIFS (ubi1:0): UBIFS: mounted UBI device 1, volume 0, name "reserve1"
UBIFS (ubi1:0): LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
UBIFS (ubi1:0): FS size: 123039744 bytes (117 MiB, 969 LEBs), journal size 6221824 bytes (5 MiB, 49 LEBs)
UBIFS (ubi1:0): reserved for root: 4952683 bytes (4836 KiB)
UBIFS (ubi1:0): media format: w4/r0 (latest is w4/r0), UUID BCBDE5E0-4C0B-4978-9734-FC58D9F68227, small LPT model
IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
macb e000b000.ethernet eth0: unable to generate target frequency: 25000000 Hz
macb e000b000.ethernet eth0: link up (100/Full)
IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
In axi fpga driver!
request_mem_region OK!
AXI fpga dev virtual address is 0xcfb38000
*base_vir_addr = 0xab00d
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/Half)
 [2020-02-14 09:07:00.495] httpListenThread start ret=0
 [2020-02-14 09:07:30.515] start listen on 6060 ...
 [2020-02-14 09:13:26.552] setStartTimePoint total_tv_start_sys=402 total_tv_end_sys=403

2020-02-14 09:07:00 cgminer.c:11470:cnt_of_proc: pidof cgminer command result is:1143

2020-02-14 09:07:00 cgminer.c:11471:cnt_of_proc: strlen is: 5
2020-02-14 09:07:00 cgminer.c:11492:cnt_of_proc: Parsed proc id is: 1143
2020-02-14 09:07:00 cgminer.c:11504:cnt_of_proc:  1 instance of cgminer is  already Running on this machine
2020-02-14 09:07:00 driver-btm-soc.c:6311:bitmain_soc_init: This is Antminer S9k scan user version
2020-02-14 09:07:00 driver-btm-soc.c:6317:bitmain_soc_init: special mode: disabled
2020-02-14 09:07:00 driver-btm-soc.c:6324:bitmain_soc_init: This is high performance mode
2020-02-14 09:07:00 driver-btm-soc.c:6329:bitmain_soc_init: last commit version: 94e8f08 commit time: 2019-10-31 10:33:22 build: 2019-12-13 10:14:11
2020-02-14 09:07:00 driver-btm-soc.c:6350:bitmain_soc_init: Detect 256MB control board of XILINX
2020-02-14 09:07:00 driver-btm-soc.c:6353:bitmain_soc_init: Miner compile time: Fri Dec 13 10:01:09 CST 2019 type: Antminer S9k
2020-02-14 09:07:00 driver-btm-soc.c:849:check_chain: get_hash_on_plug is 0x7
2020-02-14 09:07:00 driver-btm-soc.c:861:check_chain: !! chain[0]is exist
2020-02-14 09:07:00 driver-btm-soc.c:861:check_chain: !! chain[1]is exist
2020-02-14 09:07:00 driver-btm-soc.c:861:check_chain: !! chain[2]is exist
         00 01 02 03 04 05 06 07   08 09 0A 0B 0C 0D 0E 0F
00000000 7e ff ff ff ff ff ff ff   ff ff ff ff ff ff ff ff
00000010 ff ff ff ff ff ff ff ff   ff ff ff ff ff ff ff ff
00000020 ff ff ff ff ff ff ff ff   ff ff ff ff ff ff ff ff
00000030 ff ff ff ff ff ff ff ff   ff ff ff ff ff ff ff ff
00000040 ff ff ff ff ff ff ff ff   ff ff ff ff ff ff ff ff
00000050 ff ff ff ff ff ff ff ff   ff ff ff ff ff ff ff ff
00000060 ff ff ff ff ff ff ff ff   ff ff ff ff ff ff ff ff
00000070 ff ff ff ff ff ff ff ff   ff 01 02 1f fb 28 fc ff
00000080 ff ff ff ff ff ff ff c3   4d 4d 4d 4d 4d 4d 4d 4d
00000090 4d 4d 4d 4d 4d 4d 4d 4d   4d 4d 4d 4d 4d 4d 4d 4d
000000a0 4d 4d 4d 4d 4d 4d 4d 4d   4d 4d 4d 4d 4d 4d 4d 4d
000000b0 4d 4d 4d 4d 4d 4d 4d 4d   4d 4d 4d 4d 4d 4d 4d 4d
000000c0 4d 4d 4d 4d 00 ff ff ff   ff ff ff ff ff ff ff ff
000000d0 ff ff ff ff ff ff ff ff   ff ff ff ff ff ff ff ff
000000e0 ff ff ff ff ff ff ff ff   ff ff ff ff ff ff ff ff
000000f0 ff ff ff ff e3 11 00 00   80 ff ff ff 39 10 a4 bd
         00 01 02 03 04 05 06 07   08 09 0A 0B 0C 0D 0E 0F
00000000 7e ff ff ff ff ff ff ff   ff ff ff ff ff ff ff ff
00000010 ff ff ff ff ff ff ff ff   ff ff ff ff ff ff ff ff
00000020 ff ff ff ff ff ff ff ff   ff ff ff ff ff ff ff ff
00000030 ff ff ff ff ff ff ff ff   ff ff ff ff ff ff ff ff
00000040 ff ff ff ff ff ff ff ff   ff ff ff ff ff ff ff ff
00000050 ff ff ff ff ff ff ff ff   ff ff ff ff ff ff ff ff
00000060 ff ff ff ff ff ff ff ff   ff ff ff ff ff ff ff ff
00000070 ff ff ff ff ff ff ff ff   ff 01 02 1f fc 28 fd ff
00000080 ff ff ff ff ff ff ff c3   4d 4d 4d 4d 4d 4d 4d 4d
00000090 4d 4d 4d 4d 4d 4d 4d 4d   4d 4d 4d 4d 4d 4d 4d 4d
000000a0 4d 4d 4d 4d 4d 4d 4d 4d   4d 4d 4d 4d 4d 4d 4d 4d
000000b0 4d 4d 4d 4d 4d 4d 4d 4d   4d 4d 4d 4d 4d 4d 4d 4d
000000c0 4d 4d 4d 4d 02 ff ff ff   ff ff ff ff ff ff ff ff
000000d0 ff ff ff ff ff ff ff ff   ff ff ff ff ff ff ff ff
000000e0 ff ff ff ff ff ff ff ff   ff ff ff ff ff ff ff ff
000000f0 ff ff ff ff 77 11 00 00   80 ff ff ff 39 10 e5 c6
         00 01 02 03 04 05 06 07   08 09 0A 0B 0C 0D 0E 0F
00000000 7e ff ff ff ff ff ff ff   ff ff ff ff ff ff ff ff
00000010 ff ff ff ff ff ff ff ff   ff ff ff ff ff ff ff ff
00000020 ff ff ff ff ff ff ff ff   ff ff ff ff ff ff ff ff
00000030 ff ff ff ff ff ff ff ff   ff ff ff ff ff ff ff ff
00000040 ff ff ff ff ff ff ff ff   ff ff ff ff ff ff ff ff
00000050 ff ff ff ff ff ff ff ff   ff ff ff ff ff ff ff ff
00000060 ff ff ff ff ff ff ff ff   ff ff ff ff ff ff ff ff
00000070 ff ff ff ff ff ff ff ff   ff 01 02 1f fb 28 fc ff
00000080 ff ff ff ff ff ff ff c3   4d 4d 4d 4d 4d 4d 4d 4d
00000090 4d 4d 4d 4d 4d 4d 4d 4d   4d 4d 4d 4d 4d 4d 4d 4d
000000a0 4d 4d 4d 4d 4d 4d 4d 4d   4d 4d 4d 4d 4d 4d 4d 4d
000000b0 4d 4d 4d 4d 4d 4d 4d 4d   4d 4d 4d 4d 4d 4d 4d 4d
000000c0 4d 4d 4d 4d 00 ff ff ff   ff ff ff ff ff ff ff ff
000000d0 ff ff ff ff ff ff ff ff   ff ff ff ff ff ff ff ff
000000e0 ff ff ff ff ff ff ff ff   ff ff ff ff ff ff ff ff
000000f0 ff ff ff ff df 11 00 00   80 ff ff ff 39 10 64 7d

read chain[0] hardware info:
major type: 0
minor type: 0
chip level: 2
bom version: 0x10
pcb version: 0x39
fixture 8pattern result: L0

read chain[1] hardware info:
major type: 0
minor type: 0
chip level: 2
bom version: 0x10
pcb version: 0x39
fixture 8pattern result: L2

read chain[2] hardware info:
major type: 0
minor type: 0
chip level: 2
bom version: 0x10
pcb version: 0x39
fixture 8pattern result: L0

sweep config for eco mode: 
sweep_start_voltage: 9.44
max_aging_voltage:   9.84
sweep_min_freq:      270M
sweep_max_freq:      310M

sweep config for hpf mode: 
sweep_start_voltage: 9.90
max_aging_voltage:   10.30
sweep_min_freq:      355M
sweep_max_freq:      385M
2020-02-14 09:07:12 driver-btm-soc.c:5770:get_freq_result_from_eeprom: orginal chip freq: 
chain 0 freq:
385 385 385 385 385 385 385 385 385 385 
385 385 385 385 385 385 385 385 385 385 
385 385 385 385 385 385 385 385 385 385 
385 385 385 385 385 385 385 385 385 385 
385 385 385 385 385 385 385 385 385 385 
385 385 385 385 385 385 385 385 385 385 

chain 1 freq:
385 385 385 385 385 385 385 385 385 385 
385 385 385 385 385 385 385 385 385 385 
385 385 385 385 385 385 385 385 385 385 
385 385 385 385 385 385 385 385 385 385 
385 385 385 385 385 385 385 385 385 385 
385 385 385 385 385 385 385 385 385 385 

chain 2 freq:
385 385 385 385 385 385 385 385 385 385 
385 385 385 385 385 385 385 385 385 385 
385 385 385 385 385 385 385 385 385 385 
385 385 385 385 385 385 385 385 385 385 
385 385 385 385 385 385 385 385 385 385 
385 385 385 385 385 385 385 385 385 385 

2020-02-14 09:07:13 driver-btm-soc.c:6443:bitmain_soc_init: reset all...
2020-02-14 09:07:15 driver-btm-soc.c:6451:bitmain_soc_init: miner ID : 815cc4417b808854
2020-02-14 09:07:15 driver-btm-soc.c:6112:init_miner_version: FPGA Version = 0xB00D
2020-02-14 09:07:34 dspic33ep16gs202.c:486:get_pic_software_version_all_chain: chain[0] PIC software version: 177
2020-02-14 09:07:35 dspic33ep16gs202.c:486:get_pic_software_version_all_chain: chain[1] PIC software version: 177
2020-02-14 09:07:35 dspic33ep16gs202.c:486:get_pic_software_version_all_chain: chain[2] PIC software version: 177
2020-02-14 09:07:35 power.c:185:power_init: power init ... 
2020-02-14 09:07:35 driver-btm-soc.c:4877:get_working_voltage_from_eeprom: get working vol [ 9.90] from chain[0] eeprom
2020-02-14 09:07:35 power.c:232:set_working_voltage_by_chain: chain[0] working_voltage = 9.90
2020-02-14 09:07:35 driver-btm-soc.c:4877:get_working_voltage_from_eeprom: get working vol [ 9.90] from chain[1] eeprom
2020-02-14 09:07:35 power.c:232:set_working_voltage_by_chain: chain[1] working_voltage = 9.90
2020-02-14 09:07:35 driver-btm-soc.c:4877:get_working_voltage_from_eeprom: get working vol [ 9.90] from chain[2] eeprom
2020-02-14 09:07:35 power.c:232:set_working_voltage_by_chain: chain[2] working_voltage = 9.90
2020-02-14 09:07:35 driver-btm-soc.c:5560:update_highest_voltage: chain 0 hpf working voltage 9.90
2020-02-14 09:07:35 driver-btm-soc.c:5560:update_highest_voltage: chain 1 hpf working voltage 9.90
2020-02-14 09:07:35 driver-btm-soc.c:5560:update_highest_voltage: chain 2 hpf working voltage 9.90
2020-02-14 09:07:35 driver-btm-soc.c:5569:update_highest_voltage: open core at max voltage 10.20
2020-02-14 09:07:35 power.c:781:set_iic_power_to_highest_voltage_by_chain: chain[0] setting to highest voltage: 10.20 ...
2020-02-14 09:07:38 power.c:707:set_iic_power_by_voltage: now setting voltage to : 10.20 
2020-02-14 09:07:38 power.c:781:set_iic_power_to_highest_voltage_by_chain: chain[1] setting to highest voltage: 10.20 ...
2020-02-14 09:07:39 power.c:707:set_iic_power_by_voltage: now setting voltage to : 10.20 
2020-02-14 09:07:39 power.c:781:set_iic_power_to_highest_voltage_by_chain: chain[2] setting to highest voltage: 10.20 ...
2020-02-14 09:07:40 power.c:707:set_iic_power_by_voltage: now setting voltage to : 10.20 
2020-02-14 09:07:40 driver-btm-soc.c:1259:get_ideal_hash_rate: get ideal hash rate 13500
2020-02-14 09:07:40 eeprom.c:675:travel_eeprom_store: chain[0] data in eeprom is:
magic number: 0x7e
freq data per ASIC:
IC[000]:1275 IC[001]:1275 IC[002]:1275 IC[003]:1275 IC[004]:1275 IC[005]:1275 IC[006]:1275 IC[007]:1275 IC[008]:1275 IC[009]:1275 
IC[010]:1275 IC[011]:1275 IC[012]:1275 IC[013]:1275 IC[014]:1275 IC[015]:1275 IC[016]:1275 IC[017]:1275 IC[018]:1275 IC[019]:1275 
IC[020]:1275 IC[021]:1275 IC[022]:1275 IC[023]:1275 IC[024]:1275 IC[025]:1275 IC[026]:1275 IC[027]:1275 IC[028]:1275 IC[029]:1275 
IC[030]:1275 IC[031]:1275 IC[032]:1275 IC[033]:1275 IC[034]:1275 IC[035]:1275 IC[036]:1275 IC[037]:1275 IC[038]:1275 IC[039]:1275 
IC[040]:1275 IC[041]:1275 IC[042]:1275 IC[043]:1275 IC[044]:1275 IC[045]:1275 IC[046]:1275 IC[047]:1275 IC[048]:1275 IC[049]:1275 
IC[050]:1275 IC[051]:1275 IC[052]:1275 IC[053]:1275 IC[054]:1275 IC[055]:1275 IC[056]:1275 IC[057]:1275 IC[058]:1275 IC[059]:1275 
voltage: 11.10 V
hash rate: -0001 GH/s

freq data per ASIC in mode2:
IC[000]:385 IC[001]:385 IC[002]:385 IC[003]:385 IC[004]:385 IC[005]:385 IC[006]:385 IC[007]:385 IC[008]:385 IC[009]:385 
IC[010]:385 IC[011]:385 IC[012]:385 IC[013]:385 IC[014]:385 IC[015]:385 IC[016]:385 IC[017]:385 IC[018]:385 IC[019]:385 
IC[020]:385 IC[021]:385 IC[022]:385 IC[023]:385 IC[024]:385 IC[025]:385 IC[026]:385 IC[027]:385 IC[028]:385 IC[029]:385 
IC[030]:385 IC[031]:385 IC[032]:385 IC[033]:385 IC[034]:385 IC[035]:385 IC[036]:385 IC[037]:385 IC[038]:385 IC[039]:385 
IC[040]:385 IC[041]:385 IC[042]:385 IC[043]:385 IC[044]:385 IC[045]:385 IC[046]:385 IC[047]:385 IC[048]:385 IC[049]:385 
IC[050]:385 IC[051]:385 IC[052]:385 IC[053]:385 IC[054]:385 IC[055]:385 IC[056]:385 IC[057]:385 IC[058]:385 IC[059]:385 
voltage in mode2: 9.90 V
hash rate in mode2: 04579 GH/s

2020-02-14 09:07:40 eeprom.c:675:travel_eeprom_store: chain[1] data in eeprom is:
magic number: 0x7e
freq data per ASIC:
IC[000]:1275 IC[001]:1275 IC[002]:1275 IC[003]:1275 IC[004]:1275 IC[005]:1275 IC[006]:1275 IC[007]:1275 IC[008]:1275 IC[009]:1275 
IC[010]:1275 IC[011]:1275 IC[012]:1275 IC[013]:1275 IC[014]:1275 IC[015]:1275 IC[016]:1275 IC[017]:1275 IC[018]:1275 IC[019]:1275 
IC[020]:1275 IC[021]:1275 IC[022]:1275 IC[023]:1275 IC[024]:1275 IC[025]:1275 IC[026]:1275 IC[027]:1275 IC[028]:1275 IC[029]:1275 
IC[030]:1275 IC[031]:1275 IC[032]:1275 IC[033]:1275 IC[034]:1275 IC[035]:1275 IC[036]:1275 IC[037]:1275 IC[038]:1275 IC[039]:1275 
IC[040]:1275 IC[041]:1275 IC[042]:1275 IC[043]:1275 IC[044]:1275 IC[045]:1275 IC[046]:1275 IC[047]:1275 IC[048]:1275 IC[049]:1275 
IC[050]:1275 IC[051]:1275 IC[052]:1275 IC[053]:1275 IC[054]:1275 IC[055]:1275 IC[056]:1275 IC[057]:1275 IC[058]:1275 IC[059]:1275 
voltage: 11.10 V
hash rate: -0001 GH/s

freq data per ASIC in mode2:
IC[000]:385 IC[001]:385 IC[002]:385 IC[003]:385 IC[004]:385 IC[005]:385 IC[006]:385 IC[007]:385 IC[008]:385 IC[009]:385 
IC[010]:385 IC[011]:385 IC[012]:385 IC[013]:385 IC[014]:385 IC[015]:385 IC[016]:385 IC[017]:385 IC[018]:385 IC[019]:385 
IC[020]:385 IC[021]:385 IC[022]:385 IC[023]:385 IC[024]:385 IC[025]:385 IC[026]:385 IC[027]:385 IC[028]:385 IC[029]:385 
IC[030]:385 IC[031]:385 IC[032]:385 IC[033]:385 IC[034]:385 IC[035]:385 IC[036]:385 IC[037]:385 IC[038]:385 IC[039]:385 
IC[040]:385 IC[041]:385 IC[042]:385 IC[043]:385 IC[044]:385 IC[045]:385 IC[046]:385 IC[047]:385 IC[048]:385 IC[049]:385 
IC[050]:385 IC[051]:385 IC[052]:385 IC[053]:385 IC[054]:385 IC[055]:385 IC[056]:385 IC[057]:385 IC[058]:385 IC[059]:385 
voltage in mode2: 9.90 V
hash rate in mode2: 04471 GH/s

2020-02-14 09:07:40 eeprom.c:675:travel_eeprom_store: chain[2] data in eeprom is:
magic number: 0x7e
freq data per ASIC:
IC[000]:1275 IC[001]:1275 IC[002]:1275 IC[003]:1275 IC[004]:1275 IC[005]:1275 IC[006]:1275 IC[007]:1275 IC[008]:1275 IC[009]:1275 
IC[010]:1275 IC[011]:1275 IC[012]:1275 IC[013]:1275 IC[014]:1275 IC[015]:1275 IC[016]:1275 IC[017]:1275 IC[018]:1275 IC[019]:1275 
IC[020]:1275 IC[021]:1275 IC[022]:1275 IC[023]:1275 IC[024]:1275 IC[025]:1275 IC[026]:1275 IC[027]:1275 IC[028]:1275 IC[029]:1275 
IC[030]:1275 IC[031]:1275 IC[032]:1275 IC[033]:1275 IC[034]:1275 IC[035]:1275 IC[036]:1275 IC[037]:1275 IC[038]:1275 IC[039]:1275 
IC[040]:1275 IC[041]:1275 IC[042]:1275 IC[043]:1275 IC[044]:1275 IC[045]:1275 IC[046]:1275 IC[047]:1275 IC[048]:1275 IC[049]:1275 
IC[050]:1275 IC[051]:1275 IC[052]:1275 IC[053]:1275 IC[054]:1275 IC[055]:1275 IC[056]:1275 IC[057]:1275 IC[058]:1275 IC[059]:1275 
voltage: 11.10 V
hash rate: -0001 GH/s

freq data per ASIC in mode2:
IC[000]:385 IC[001]:385 IC[002]:385 IC[003]:385 IC[004]:385 IC[005]:385 IC[006]:385 IC[007]:385 IC[008]:385 IC[009]:385 
IC[010]:385 IC[011]:385 IC[012]:385 IC[013]:385 IC[014]:385 IC[015]:385 IC[016]:385 IC[017]:385 IC[018]:385 IC[019]:385 
IC[020]:385 IC[021]:385 IC[022]:385 IC[023]:385 IC[024]:385 IC[025]:385 IC[026]:385 IC[027]:385 IC[028]:385 IC[029]:385 
IC[030]:385 IC[031]:385 IC[032]:385 IC[033]:385 IC[034]:385 IC[035]:385 IC[036]:385 IC[037]:385 IC[038]:385 IC[039]:385 
IC[040]:385 IC[041]:385 IC[042]:385 IC[043]:385 IC[044]:385 IC[045]:385 IC[046]:385 IC[047]:385 IC[048]:385 IC[049]:385 
IC[050]:385 IC[051]:385 IC[052]:385 IC[053]:385 IC[054]:385 IC[055]:385 IC[056]:385 IC[057]:385 IC[058]:385 IC[059]:385 
voltage in mode2: 9.90 V
hash rate in mode2: 04575 GH/s

2020-02-14 09:07:41 driver-btm-soc.c:6494:bitmain_soc_init: fan_eft : 0  fan_pwm : 0
2020-02-14 09:07:41 driver-btm-soc.c:6141:bring_up_chain: 

bring up chain 0
2020-02-14 09:07:41 zynq.c:212:set_reset_hashboard: set_reset_hashboard = 0x0000ffff
2020-02-14 09:08:14 zynq.c:212:set_reset_hashboard: set_reset_hashboard = 0x0000fffe
2020-02-14 09:08:16 driver-btm-soc.c:3807:check_asic_num: without pre_open_core chain 0, find asic num = 60
2020-02-14 09:08:19 driver-btm-soc.c:4630:set_freq_by_chain: chain[0] set freq:100.00
2020-02-14 09:08:19 driver-btm-soc.c:3853:open_core_BM1393_pre_open: pre open core = 13
2020-02-14 09:08:20 driver-btm-soc.c:3733:pre_open_core_one_chain: for chain 0
2020-02-14 09:08:20 temperature.c:591:is_eeprom_tempsensor_data_correct: check sensor info ...
2020-02-14 09:08:20 temperature.c:606:is_eeprom_tempsensor_data_correct: sensor type is TMP451
2020-02-14 09:08:20 temperature.c:618:is_eeprom_tempsensor_data_correct: 2
2020-02-14 09:08:20 temperature.c:632:is_eeprom_tempsensor_data_correct: sensor num is 2
2020-02-14 09:08:20 temperature.c:641:is_eeprom_tempsensor_data_correct: sensor pos = 31, 40, 0, 0
2020-02-14 09:08:20 temperature.c:659:is_eeprom_tempsensor_data_correct: chain[0] temp sensor info, correct!
2020-02-14 09:08:20 temperature.c:748:check_eeprom_calibration_data: chain[0] no need to calibrate !
2020-02-14 09:08:20 temperature.c:524:is_tempsensor_data_correct: Bad,temp_info.type = 0
2020-02-14 09:08:20 temperature.c:763:calibration_sensor_offset: chain[0] temp info,Bad. Reload from eeprom..
sensor type = 1,sensor num = 2
sensor pos: 31  40  0  0  0  0 
sensor offset: -5  -4  0  0  0  0 
2020-02-14 09:08:20 temperature.c:801:calibration_sensor_offset: get temp info from eeprom,just use it!
2020-02-14 09:08:20 asic.c:1429:set_misc_control: cmd_buf[0]=0x41097818, cmd_buf[1]=0x7a61, cmd_buf[2]=0x1a000000, misc=0x7a61
2020-02-14 09:08:20 temperature.c:818:calibration_sensor_offset: Chain[0] chip[31] use PIC middle temp offset=-5, typeID=55
2020-02-14 09:08:21 temperature.c:346:do_calibration_sensor_offset_by_eeprom: New offset - Chain[0] Chip[31] local:0 remote:0 offset:-5 
2020-02-14 09:08:21 temperature.c:870:calibration_sensor_offset: Chain[0] Chip[31] get middle temp offset=-5 typeID=55
2020-02-14 09:08:21 asic.c:1429:set_misc_control: cmd_buf[0]=0x41099c18, cmd_buf[1]=0x7a61, cmd_buf[2]=0x13000000, misc=0x7a61
2020-02-14 09:08:21 temperature.c:818:calibration_sensor_offset: Chain[0] chip[40] use PIC middle temp offset=-4, typeID=55
2020-02-14 09:08:21 temperature.c:346:do_calibration_sensor_offset_by_eeprom: New offset - Chain[0] Chip[40] local:0 remote:0 offset:-4 
2020-02-14 09:08:21 temperature.c:870:calibration_sensor_offset: Chain[0] Chip[40] get middle temp offset=-4 typeID=55
2020-02-14 09:08:21 driver-btm-soc.c:6141:bring_up_chain: 

bring up chain 1
2020-02-14 09:08:22 zynq.c:212:set_reset_hashboard: set_reset_hashboard = 0x0000fffe
2020-02-14 09:08:53 zynq.c:212:set_reset_hashboard: set_reset_hashboard = 0x0000fffc
2020-02-14 09:08:55 driver-btm-soc.c:3807:check_asic_num: without pre_open_core chain 1, find asic num = 60
2020-02-14 09:08:58 driver-btm-soc.c:4630:set_freq_by_chain: chain[1] set freq:100.00
2020-02-14 09:08:58 driver-btm-soc.c:3853:open_core_BM1393_pre_open: pre open core = 13
2020-02-14 09:08:59 driver-btm-soc.c:3733:pre_open_core_one_chain: for chain 1
2020-02-14 09:08:59 temperature.c:591:is_eeprom_tempsensor_data_correct: check sensor info ...
2020-02-14 09:08:59 temperature.c:606:is_eeprom_tempsensor_data_correct: sensor type is TMP451
2020-02-14 09:08:59 temperature.c:618:is_eeprom_tempsensor_data_correct: 2
2020-02-14 09:08:59 temperature.c:632:is_eeprom_tempsensor_data_correct: sensor num is 2
2020-02-14 09:08:59 temperature.c:641:is_eeprom_tempsensor_data_correct: sensor pos = 31, 40, 0, 0
2020-02-14 09:08:59 temperature.c:659:is_eeprom_tempsensor_data_correct: chain[1] temp sensor info, correct!
2020-02-14 09:08:59 temperature.c:748:check_eeprom_calibration_data: chain[1] no need to calibrate !
2020-02-14 09:08:59 temperature.c:524:is_tempsensor_data_correct: Bad,temp_info.type = 0
2020-02-14 09:08:59 temperature.c:763:calibration_sensor_offset: chain[1] temp info,Bad. Reload from eeprom..
sensor type = 1,sensor num = 2
sensor pos: 31  40  0  0  0  0 
sensor offset: -4  -3  0  0  0  0 
2020-02-14 09:08:59 temperature.c:801:calibration_sensor_offset: get temp info from eeprom,just use it!
2020-02-14 09:08:59 asic.c:1429:set_misc_control: cmd_buf[0]=0x41097818, cmd_buf[1]=0x7a61, cmd_buf[2]=0x1a000000, misc=0x7a61
2020-02-14 09:08:59 temperature.c:818:calibration_sensor_offset: Chain[1] chip[31] use PIC middle temp offset=-4, typeID=55
2020-02-14 09:09:00 temperature.c:346:do_calibration_sensor_offset_by_eeprom: New offset - Chain[1] Chip[31] local:0 remote:0 offset:-4 
2020-02-14 09:09:00 temperature.c:870:calibration_sensor_offset: Chain[1] Chip[31] get middle temp offset=-4 typeID=55
2020-02-14 09:09:00 asic.c:1429:set_misc_control: cmd_buf[0]=0x41099c18, cmd_buf[1]=0x7a61, cmd_buf[2]=0x13000000, misc=0x7a61
2020-02-14 09:09:00 temperature.c:818:calibration_sensor_offset: Chain[1] chip[40] use PIC middle temp offset=-3, typeID=55
2020-02-14 09:09:00 temperature.c:346:do_calibration_sensor_offset_by_eeprom: New offset - Chain[1] Chip[40] local:0 remote:0 offset:-3 
2020-02-14 09:09:00 temperature.c:870:calibration_sensor_offset: Chain[1] Chip[40] get middle temp offset=-3 typeID=55
2020-02-14 09:09:00 driver-btm-soc.c:6141:bring_up_chain: 

bring up chain 2
2020-02-14 09:09:01 zynq.c:212:set_reset_hashboard: set_reset_hashboard = 0x0000fffc
2020-02-14 09:09:32 zynq.c:212:set_reset_hashboard: set_reset_hashboard = 0x0000fff8
2020-02-14 09:09:34 driver-btm-soc.c:3807:check_asic_num: without pre_open_core chain 2, find asic num = 60
2020-02-14 09:09:37 driver-btm-soc.c:4630:set_freq_by_chain: chain[2] set freq:100.00
2020-02-14 09:09:37 driver-btm-soc.c:3853:open_core_BM1393_pre_open: pre open core = 13
2020-02-14 09:09:38 driver-btm-soc.c:3733:pre_open_core_one_chain: for chain 2
2020-02-14 09:09:38 temperature.c:591:is_eeprom_tempsensor_data_correct: check sensor info ...
2020-02-14 09:09:38 temperature.c:606:is_eeprom_tempsensor_data_correct: sensor type is TMP451
2020-02-14 09:09:38 temperature.c:618:is_eeprom_tempsensor_data_correct: 2
2020-02-14 09:09:38 temperature.c:632:is_eeprom_tempsensor_data_correct: sensor num is 2
2020-02-14 09:09:38 temperature.c:641:is_eeprom_tempsensor_data_correct: sensor pos = 31, 40, 0, 0
2020-02-14 09:09:38 temperature.c:659:is_eeprom_tempsensor_data_correct: chain[2] temp sensor info, correct!
2020-02-14 09:09:38 temperature.c:748:check_eeprom_calibration_data: chain[2] no need to calibrate !
2020-02-14 09:09:38 temperature.c:524:is_tempsensor_data_correct: Bad,temp_info.type = 0
2020-02-14 09:09:38 temperature.c:763:calibration_sensor_offset: chain[2] temp info,Bad. Reload from eeprom..
sensor type = 1,sensor num = 2
sensor pos: 31  40  0  0  0  0 
sensor offset: -5  -4  0  0  0  0 
2020-02-14 09:09:38 temperature.c:801:calibration_sensor_offset: get temp info from eeprom,just use it!
2020-02-14 09:09:38 asic.c:1429:set_misc_control: cmd_buf[0]=0x41097818, cmd_buf[1]=0x7a61, cmd_buf[2]=0x1a000000, misc=0x7a61
2020-02-14 09:09:38 temperature.c:818:calibration_sensor_offset: Chain[2] chip[31] use PIC middle temp offset=-5, typeID=55
2020-02-14 09:09:39 temperature.c:346:do_calibration_sensor_offset_by_eeprom: New offset - Chain[2] Chip[31] local:0 remote:0 offset:-5 
2020-02-14 09:09:39 temperature.c:870:calibration_sensor_offset: Chain[2] Chip[31] get middle temp offset=-5 typeID=55
2020-02-14 09:09:39 asic.c:1429:set_misc_control: cmd_buf[0]=0x41099c18, cmd_buf[1]=0x7a61, cmd_buf[2]=0x13000000, misc=0x7a61
2020-02-14 09:09:39 temperature.c:818:calibration_sensor_offset: Chain[2] chip[40] use PIC middle temp offset=-4, typeID=55
2020-02-14 09:09:39 temperature.c:346:do_calibration_sensor_offset_by_eeprom: New offset - Chain[2] Chip[40] local:0 remote:0 offset:-4 
2020-02-14 09:09:39 temperature.c:870:calibration_sensor_offset: Chain[2] Chip[40] get middle temp offset=-4 typeID=55
2020-02-14 09:09:39 asic.c:1153:set_baud: set baud=1
2020-02-14 09:09:39 asic.c:1126:set_baud_one_chain: cmd_buf[0]=0x51090018, cmd_buf[1]=0x2101, cmd_buf[2]=0x11000000, misc=0x2101
2020-02-14 09:09:39 asic.c:1126:set_baud_one_chain: cmd_buf[0]=0x51090018, cmd_buf[1]=0x2101, cmd_buf[2]=0x11000000, misc=0x2101
2020-02-14 09:09:39 asic.c:1126:set_baud_one_chain: cmd_buf[0]=0x51090018, cmd_buf[1]=0x2101, cmd_buf[2]=0x11000000, misc=0x2101
2020-02-14 09:09:39 asic.c:1164:set_baud: read bc write is 0x82001a
2020-02-14 09:09:39 asic.c:1429:set_misc_control: cmd_buf[0]=0x41097818, cmd_buf[1]=0x6161, cmd_buf[2]=0x13000000, misc=0x6161
2020-02-14 09:09:39 asic.c:1429:set_misc_control: cmd_buf[0]=0x41099c18, cmd_buf[1]=0x6161, cmd_buf[2]=0x1a000000, misc=0x6161
2020-02-14 09:09:39 asic.c:1429:set_misc_control: cmd_buf[0]=0x41097818, cmd_buf[1]=0x6161, cmd_buf[2]=0x13000000, misc=0x6161
2020-02-14 09:09:39 asic.c:1429:set_misc_control: cmd_buf[0]=0x41099c18, cmd_buf[1]=0x6161, cmd_buf[2]=0x1a000000, misc=0x6161
2020-02-14 09:09:39 asic.c:1429:set_misc_control: cmd_buf[0]=0x41097818, cmd_buf[1]=0x6161, cmd_buf[2]=0x13000000, misc=0x6161
2020-02-14 09:09:39 asic.c:1429:set_misc_control: cmd_buf[0]=0x41099c18, cmd_buf[1]=0x6161, cmd_buf[2]=0x1a000000, misc=0x6161
2020-02-14 09:09:39 driver-btm-soc.c:6509:bitmain_soc_init: set TICKET_MASK
2020-02-14 09:09:41 temperature.c:2081:detect_startup_environment_temperature: Environment temperature: [30]
2020-02-14 09:09:41 temperature.c:2098:detect_startup_environment_temperature: Enter 10 secs to cool down hash board, 1 times ...
2020-02-14 09:09:52 temperature.c:2081:detect_startup_environment_temperature: Environment temperature: [29]
2020-02-14 09:09:52 temperature.c:2098:detect_startup_environment_temperature: Enter 10 secs to cool down hash board, 2 times ...
2020-02-14 09:10:03 temperature.c:2081:detect_startup_environment_temperature: Environment temperature: [29]
2020-02-14 09:10:03 temperature.c:2098:detect_startup_environment_temperature: Enter 10 secs to cool down hash board, 3 times ...
2020-02-14 09:10:13 driver-btm-soc.c:3884:set_clock_delay_control: set mode 0
2020-02-14 09:10:13 driver-btm-soc.c:3903:set_clock_delay_control: core_data = 0x04
2020-02-14 09:10:13 driver-btm-soc.c:3974:open_core_bm1393: Start Open Core!!
2020-02-14 09:10:19 driver-btm-soc.c:4041:open_core_bm1393: End Open Core!!
2020-02-14 09:10:20 driver-btm-soc.c:5193:increase_freq_by_eeprom_slowly: chain[0] increase to 125
2020-02-14 09:10:22 driver-btm-soc.c:5193:increase_freq_by_eeprom_slowly: chain[0] increase to 150
2020-02-14 09:10:24 driver-btm-soc.c:5193:increase_freq_by_eeprom_slowly: chain[0] increase to 175
2020-02-14 09:10:27 driver-btm-soc.c:5193:increase_freq_by_eeprom_slowly: chain[0] increase to 200
2020-02-14 09:10:29 driver-btm-soc.c:5193:increase_freq_by_eeprom_slowly: chain[0] increase to 225
2020-02-14 09:10:31 driver-btm-soc.c:5193:increase_freq_by_eeprom_slowly: chain[0] increase to 250
2020-02-14 09:10:33 driver-btm-soc.c:5193:increase_freq_by_eeprom_slowly: chain[0] increase to 275
2020-02-14 09:10:35 driver-btm-soc.c:5193:increase_freq_by_eeprom_slowly: chain[0] increase to 300
2020-02-14 09:10:37 driver-btm-soc.c:5193:increase_freq_by_eeprom_slowly: chain[0] increase to 325
2020-02-14 09:10:39 driver-btm-soc.c:5193:increase_freq_by_eeprom_slowly: chain[0] increase to 350
2020-02-14 09:10:42 driver-btm-soc.c:5193:increase_freq_by_eeprom_slowly: chain[0] increase to 375
2020-02-14 09:10:44 driver-btm-soc.c:5193:increase_freq_by_eeprom_slowly: chain[0] increase to 385
2020-02-14 09:10:46 driver-btm-soc.c:5209:increase_freq_by_eeprom_slowly: max = 385 ,min = 385
2020-02-14 09:10:46 driver-btm-soc.c:5215:increase_freq_by_eeprom_slowly: chain[0] increaseing the diff freq ...
2020-02-14 09:10:46 driver-btm-soc.c:5243:increase_freq_by_eeprom_slowly: chain 0 final freq setting:
385 385 385 385 385 385 385 385 385 385 
385 385 385 385 385 385 385 385 385 385 
385 385 385 385 385 385 385 385 385 385 
385 385 385 385 385 385 385 385 385 385 
385 385 385 385 385 385 385 385 385 385 
385 385 385 385 385 385 385 385 385 385 
2020-02-14 09:10:46 driver-btm-soc.c:5255:increase_freq_by_eeprom_slowly: set chain 0 to working voltage
2020-02-14 09:10:46 power.c:1309:slowly_set_working_power_t11: set chain 0 to working voltage:
now setting chain[0]-volt[10.20]-data[026] 
now setting chain[0]-volt[10.17]-data[027] 
now setting chain[0]-volt[10.14]-data[028] 
now setting chain[0]-volt[10.11]-data[029] 
2020-02-14 09:11:01 dspic33ep16gs202.c:213:dsPIC33EP16GS202_pic_heart_beat: ERROR! failed on Chain[0] after 3 times try!
now setting chain[0]-volt[10.08]-data[030] 
now setting chain[0]-volt[10.02]-data[032] 
now setting chain[0]-volt[09.97]-data[034] 
now setting chain[0]-volt[09.95]-data[035] 
now setting chain[0]-volt[09.92]-data[036] 
2020-02-14 09:11:22 power.c:1331:slowly_set_working_power_t11: done!
2020-02-14 09:11:22 driver-btm-soc.c:5193:increase_freq_by_eeprom_slowly: chain[1] increase to 125
2020-02-14 09:11:24 driver-btm-soc.c:5193:increase_freq_by_eeprom_slowly: chain[1] increase to 150
2020-02-14 09:11:26 driver-btm-soc.c:5193:increase_freq_by_eeprom_slowly: chain[1] increase to 175
2020-02-14 09:11:28 driver-btm-soc.c:5193:increase_freq_by_eeprom_slowly: chain[1] increase to 200
2020-02-14 09:11:31 driver-btm-soc.c:5193:increase_freq_by_eeprom_slowly: chain[1] increase to 225
2020-02-14 09:11:33 driver-btm-soc.c:5193:increase_freq_by_eeprom_slowly: chain[1] increase to 250
2020-02-14 09:11:35 driver-btm-soc.c:5193:increase_freq_by_eeprom_slowly: chain[1] increase to 275
2020-02-14 09:11:37 driver-btm-soc.c:5193:increase_freq_by_eeprom_slowly: chain[1] increase to 300
2020-02-14 09:11:39 driver-btm-soc.c:5193:increase_freq_by_eeprom_slowly: chain[1] increase to 325
2020-02-14 09:11:41 driver-btm-soc.c:5193:increase_freq_by_eeprom_slowly: chain[1] increase to 350
2020-02-14 09:11:43 driver-btm-soc.c:5193:increase_freq_by_eeprom_slowly: chain[1] increase to 375
2020-02-14 09:11:46 driver-btm-soc.c:5193:increase_freq_by_eeprom_slowly: chain[1] increase to 385
2020-02-14 09:11:48 driver-btm-soc.c:5209:increase_freq_by_eeprom_slowly: max = 385 ,min = 385
2020-02-14 09:11:48 driver-btm-soc.c:5215:increase_freq_by_eeprom_slowly: chain[1] increaseing the diff freq ...
2020-02-14 09:11:48 driver-btm-soc.c:5243:increase_freq_by_eeprom_slowly: chain 1 final freq setting:
385 385 385 385 385 385 385 385 385 385 
385 385 385 385 385 385 385 385 385 385 
385 385 385 385 385 385 385 385 385 385 
385 385 385 385 385 385 385 385 385 385 
385 385 385 385 385 385 385 385 385 385 
385 385 385 385 385 385 385 385 385 385 
2020-02-14 09:11:48 driver-btm-soc.c:5255:increase_freq_by_eeprom_slowly: set chain 1 to working voltage
2020-02-14 09:11:48 power.c:1309:slowly_set_working_power_t11: set chain 1 to working voltage:
now setting chain[1]-volt[10.20]-data[026] 
now setting chain[1]-volt[10.17]-data[027] 
now setting chain[1]-volt[10.14]-data[028] 
now setting chain[1]-volt[10.11]-data[029] 
now setting chain[1]-volt[10.08]-data[030] 
now setting chain[1]-volt[10.02]-data[032] 
now setting chain[1]-volt[09.97]-data[034] 
now setting chain[1]-volt[09.95]-data[035] 
now setting chain[1]-volt[09.92]-data[036] 
2020-02-14 09:12:23 power.c:1331:slowly_set_working_power_t11: done!
2020-02-14 09:12:23 driver-btm-soc.c:5193:increase_freq_by_eeprom_slowly: chain[2] increase to 125
2020-02-14 09:12:25 driver-btm-soc.c:5193:increase_freq_by_eeprom_slowly: chain[2] increase to 150
2020-02-14 09:12:27 driver-btm-soc.c:5193:increase_freq_by_eeprom_slowly: chain[2] increase to 175
2020-02-14 09:12:30 driver-btm-soc.c:5193:increase_freq_by_eeprom_slowly: chain[2] increase to 200
2020-02-14 09:12:32 driver-btm-soc.c:5193:increase_freq_by_eeprom_slowly: chain[2] increase to 225
2020-02-14 09:12:34 driver-btm-soc.c:5193:increase_freq_by_eeprom_slowly: chain[2] increase to 250
2020-02-14 09:12:36 driver-btm-soc.c:5193:increase_freq_by_eeprom_slowly: chain[2] increase to 275
2020-02-14 09:12:38 driver-btm-soc.c:5193:increase_freq_by_eeprom_slowly: chain[2] increase to 300
2020-02-14 09:12:40 driver-btm-soc.c:5193:increase_freq_by_eeprom_slowly: chain[2] increase to 325
2020-02-14 09:12:42 driver-btm-soc.c:5193:increase_freq_by_eeprom_slowly: chain[2] increase to 350
2020-02-14 09:12:45 driver-btm-soc.c:5193:increase_freq_by_eeprom_slowly: chain[2] increase to 375
2020-02-14 09:12:47 driver-btm-soc.c:5193:increase_freq_by_eeprom_slowly: chain[2] increase to 385
2020-02-14 09:12:49 driver-btm-soc.c:5209:increase_freq_by_eeprom_slowly: max = 385 ,min = 385
2020-02-14 09:12:49 driver-btm-soc.c:5215:increase_freq_by_eeprom_slowly: chain[2] increaseing the diff freq ...
2020-02-14 09:12:49 driver-btm-soc.c:5243:increase_freq_by_eeprom_slowly: chain 2 final freq setting:
385 385 385 385 385 385 385 385 385 385 
385 385 385 385 385 385 385 385 385 385 
385 385 385 385 385 385 385 385 385 385 
385 385 385 385 385 385 385 385 385 385 
385 385 385 385 385 385 385 385 385 385 
385 385 385 385 385 385 385 385 385 385 
2020-02-14 09:12:49 driver-btm-soc.c:5255:increase_freq_by_eeprom_slowly: set chain 2 to working voltage
2020-02-14 09:12:49 power.c:1309:slowly_set_working_power_t11: set chain 2 to working voltage:
now setting chain[2]-volt[10.20]-data[026] 
now setting chain[2]-volt[10.17]-data[027] 
now setting chain[2]-volt[10.14]-data[028] 
now setting chain[2]-volt[10.11]-data[029] 
now setting 2020-02-14 09:13:07 dspic33ep16gs202.c:276:dsPIC33EP16GS202_set_pic_voltage: ERROR! failed on Chain[2] after 3 times try!
chain[2]-volt[10.08]-data[030] 
now setting chain[2]-volt[10.02]-data[032] 
now setting chain[2]-volt[09.97]-data[034] 
now setting 2020-02-14 09:13:19 dspic33ep16gs202.c:276:dsPIC33EP16GS202_set_pic_voltage: ERROR! failed on Chain[2] after 3 times try!
chain[2]-volt[09.95]-data[035] 
now setting chain[2]-volt[09.92]-data[036] 
2020-02-14 09:13:23 power.c:1331:slowly_set_working_power_t11: done!
2020-02-14 09:13:23 driver-btm-soc.c:6545:bitmain_soc_init: set to working voltage...
2020-02-14 09:13:23 power.c:1258:slowly_set_iic_power_voltage_t11: parallel set all chain to working voltage:
now setting chain[0]-volt[09.92]-data[036] chain[1]-volt[09.92]-data[036] chain[2]-volt[09.92]-data[036] 
2020-02-14 09:13:26 power.c:1278:slowly_set_iic_power_voltage_t11: parallel set all chain to working voltage end!
now setting chain[0]-volt[09.90]-data[036] chain[1]-volt[09.90]-data[036] chain[2]-volt[09.90]-data[036] 
2020-02-14 09:13:26 driver-btm-soc.c:4929:set_timeout: freq 385 final timeout=340
2020-02-14 09:13:26 driver-btm-soc.c:2925:low_temp_process_parm_init: chip miner_type = [0]
2020-02-14 09:13:26 driver-btm-soc.c:2925:low_temp_process_parm_init: chip miner_type = [0]
2020-02-14 09:13:26 driver-btm-soc.c:2925:low_temp_process_parm_init: chip miner_type = [0]
2020-02-14 09:13:26 driver-btm-soc.c:3539:check_system_work: check system thread start...
2020-02-14 09:13:26 driver-btm-soc.c:6614:bitmain_soc_init: Init done!
2020-02-14 09:13:26 driver-btm-soc.c:7257:bitmain_soc_prepare: bitmain soc init success.
2020-02-14 09:13:27 temperature.c:1542:read_temp_func: bring_up_pcb_temp = 35
2020-02-14 09:13:45 temperature.c:1887:get_target_chip_temp: if startup in low temp environment: NO
2020-02-14 09:13:45 temperature.c:1733:_get_target_chip_temp_t11: chip miner_type = [0]
2020-02-14 09:13:45 temperature.c:1733:_get_target_chip_temp_t11: chip miner_type = [0]
2020-02-14 09:13:45 temperature.c:1733:_get_target_chip_temp_t11: chip miner_type = [0]
2020-02-14 09:15:30 temperature.c:1363:process_status_value: Fatal Error: network connection lost!
2020-02-14 09:15:34 temperature.c:1363:process_status_value: Fatal Error: network connection lost!
2020-02-14 09:15:39 temperature.c:1363:process_status_value: Fatal Error: network connection lost!
2020-02-14 09:15:43 temperature.c:1363:process_status_value: Fatal Error: network connection lost!
2020-02-14 09:15:48 temperature.c:1363:process_status_value: Fatal Error: network connection lost!
2020-02-14 09:15:53 temperature.c:1363:process_status_value: Fatal Error: network connection lost!
2020-02-14 09:15:57 temperature.c:1363:process_status_value: Fatal Error: network connection lost!
2020-02-14 09:16:02 temperature.c:1363:process_status_value: Fatal Error: network connection lost!
2020-02-14 09:16:06 temperature.c:1363:process_status_value: Fatal Error: network connection lost!
2020-02-14 09:16:11 temperature.c:1363:process_status_value: Fatal Error: network connection lost!
2020-02-14 09:16:15 temperature.c:1363:process_status_value: Fatal Error: network connection lost!
2020-02-14 09:16:20 temperature.c:1363:process_status_value: Fatal Error: network connection lost!
2020-02-14 09:16:24 temperature.c:1363:process_status_value: Fatal Error: network connection lost!
2020-02-14 09:16:29 temperature.c:1363:process_status_value: Fatal Error: network connection lost!
2020-02-14 09:16:34 temperature.c:1363:process_status_value: Fatal Error: network connection lost!
2020-02-14 09:16:38 temperature.c:1363:process_status_value: Fatal Error: network connection lost!
2020-02-14 09:16:43 temperature.c:1363:process_status_value: Fatal Error: network connection lost!
2020-02-14 09:16:47 temperature.c:1363:process_status_value: Fatal Error: network connection lost!
2020-02-14 09:16:52 temperature.c:1363:process_status_value: Fatal Error: network connection lost!
2020-02-14 09:16:56 temperature.c:1363:process_status_value: Fatal Error: network connection lost!
2020-02-14 09:17:01 temperature.c:1363:process_status_value: Fatal Error: network connection lost!
2020-02-14 09:17:05 temperature.c:1363:process_status_value: Fatal Error: network connection lost!

[1714809993]

1714809993

[1714809993]

1714809993

[1714809993]

1714809993

[BitMaxz]

The log stuck on the temp.

Code:

2020-02-14 09:15:30 temperature.c:1363:process_status_value: Fatal Error: network connection lost!

It might be a temperature sensor.

The temp from PCB is fine it detects properly but after detecting the temp on the chip you got a fatal error then connection lost.

Can you check the miner's configuration and find the low power mode then enable it. then test it again. Let's see if it fixes your issue.

Just in case if still doesn't work check the kernel logs for changes and make a screenshot of your miner's status then post them here.

[sxo13]

Thank you very much!

First thing in the morning I do as instructed.

Not sure I have that option with the low power mode, at least I never noticed in the UI.

Weird thing is that all the s9k stopped at more or less the same time and have the same issue thats why I suspected it has to do with ambient temperature.....hoped the january firware would solve it as they referred in the notes to some temp. related issues but didn't.

Btw. any other reliable firmware suggestion for the s9k?   Just in case nothing else works out with the current one.....every other miner I run with BraiinsOS but s9k is not yet supported.

Can you check the miner's configuration and find the low power mode then enable it. then test it again. Let's see if it fixes your issue.

As I thought, unfortunately no such setting on the s9k firmware, it seems thats only available on the other s9x models.

Just in case if still doesn't work check the kernel logs for changes and make a screenshot of your miner's status then post them here.

Miner status pic:

https://i.imgur.com/GS5W7xc.png

[philipma1957]

try a different pool

try

http://solo.ckpool.org/


solo.ckpool.org:3333
your btc address
x


solo.ckpool.org:443
your btc address
x


de.ckpool.org:3333
your btc address
x

make sure you control the btc address.

I noticed that your dropped eth freq   below 25000000 two or three times  you may have a bad cable or some packet loss connections .

try ck pool see if you connect

try a new eth cable

or it is the heat sensor issue which means you need to wait for an aftermarket firmware that works with the s9k

btw I get this issue on 1 of my 4 s9k's on some pools but not others.  not the heat sensor but the ETH cable freq

also fill all three pool choices.

[sxo13]

Thanks much for the tip but unfortunately it didn't resolved the issue, tried with ckpool and f2 as well...

Will check the connection issue you pointed to, no idea whats causing that.

All in all, hard to swallow that I have to wait for new firmware to fix the issue but at least I dont have hundreds of these s9k just 7...

[BitMaxz]

How about resetting the miner to factory default by holding IP/reset button for 15 seconds release then reconfigure and test it again.

Well, if all recommendation doesn't work I think the issue still under their firmware which is a common issue on s9k miner.

Read this "WANRNING! Do Not Buy Antminer S9k"

If it still under warranty better contact the bitmain support and try to ask for SD card recovery(old version) and maybe using an old version of s9k can fix your "temp reading issue".

[mikeywith]

Well, if all recommendation doesn't work I think the issue still under their firmware which is a common issue on s9k miner.

Read this "WANRNING! Do Not Buy Antminer S9k"

Well, if only he read the topic before purchasing  

The stock firmware has a lot of issues in regards to reading the temperature of the chips, it has "supposedly" fixed in the later version/s, however, these S9ks suck by default, my S9ks keep losing a board every now and then, sometimes they reboot a few times a day for really no obvious reason, I have actually got to the point where I don't bother with them anymore, I have talked to Taserz and Patrick (Awesome Miner) about a firmware for the S9k, hoping that their firmware will fix these issues, but the of them did not promise me anything yet.

if you are certain the problem you have is temperature related, you can simply do one of the following or both.

1-Set all fans to 90%.
2-Turn the other S9s off to reduce the room temperature.

if the problem goes away, then you need to improve your ventilation system, if it does not, then try to return them to Bitmain while you still can.

[sxo13]

[...]

Tried the reset earlier, didnt worked....

I read it but my batch is from around september/october  

Contacted support in the meanwhile, lets see if they have a solution, for now they asked only for additional screenshots...will post here the outcome.

[...]

1 - no control over the fans, at least not from the UI
2 - ventilation is more then good, tried it also at different ambient temperatures but makes no sense to turn off the other machines, its not just 1-2 of them

[mikeywith]

1 - no control over the fans, at least not from the UI

Bitmain are doing a great job limiting the things you can do with your miner, but anyway I have figured out an easy way to temper with fan speed in S9k from the GUI, you can read about here

2 - ventilation is more then good, tried it also at different ambient temperatures but makes no sense to turn off the other machines, its not just 1-2 of them

Depending on the room size, 1-2 miners can make the place very hot, but since you know the ventilation is "more than good" then there is no need to go the route.

did you inspect the gears for physical damage such as lose heatsinks?

[thierry4wd]

Hum ... your kernel log is very strange for me... i thinks used by custom firmware... is true ?

Reason : your 3 hashboard is not same eprom

Code:

read chain[0] hardware info:
major type: 0
minor type: 0
chip level: 2
bom version: 0x10
pcb version: 0x39
fixture 8pattern result: L0

read chain[1] hardware info:
major type: 0
minor type: 0
chip level: 2
bom version: 0x10
pcb version: 0x39
fixture 8pattern result: L2

read chain[2] hardware info:
major type: 0
minor type: 0
chip level: 2
bom version: 0x10
pcb version: 0x39
fixture 8pattern result: L0

And, this is not conventional :

Code:

2020-02-14 09:07:35 driver-btm-soc.c:4877:get_working_voltage_from_eeprom: get working vol [ 9.90] from chain[0] eeprom
2020-02-14 09:07:35 power.c:232:set_working_voltage_by_chain: chain[0] working_voltage = 9.90
2020-02-14 09:07:35 driver-btm-soc.c:4877:get_working_voltage_from_eeprom: get working vol [ 9.90] from chain[1] eeprom
2020-02-14 09:07:35 power.c:232:set_working_voltage_by_chain: chain[1] working_voltage = 9.90
2020-02-14 09:07:35 driver-btm-soc.c:4877:get_working_voltage_from_eeprom: get working vol [ 9.90] from chain[2] eeprom
2020-02-14 09:07:35 power.c:232:set_working_voltage_by_chain: chain[2] working_voltage = 9.90
2020-02-14 09:07:35 driver-btm-soc.c:5560:update_highest_voltage: chain 0 hpf working voltage 9.90
2020-02-14 09:07:35 driver-btm-soc.c:5560:update_highest_voltage: chain 1 hpf working voltage 9.90
2020-02-14 09:07:35 driver-btm-soc.c:5560:update_highest_voltage: chain 2 hpf working voltage 9.90

[sxo13]

[...]

Thanks for the tip, will look into the code to set free the fan setting in the UI.

Yes, ventilation is fine, I have a cold/hot aisle setup, strong fans etc., all other miners behave nicely, even the 6KW bitfury machines work like a charm.

I looked into a few if there is any mechanical damage but no...and they would not have stopped all at more or less the same time. They worked less then 2 months.

[...]

All stock firmware(january build), weird that with the eprom but I assume its just one of the usual chinese manufacturing wonders or do you think it can cause any problems?

[mikeywith]

Hum ... your kernel log is very strange for me... i thinks used by custom firmware... is true ?

As far as I know, there is no custom firmware for S9k yet,I believe vnish should have theirs ready in a few weeks.

Reason : your 3 hashboard is not same eprom

Code:

read chain[0] hardware info:
major type: 0
minor type: 0
chip level: 2
bom version: 0x10
pcb version: 0x39
fixture 8pattern result: L0

read chain[1] hardware info:
major type: 0
minor type: 0
chip level: 2
bom version: 0x10
pcb version: 0x39
fixture 8pattern result: L2

read chain[2] hardware info:
major type: 0
minor type: 0
chip level: 2
bom version: 0x10
pcb version: 0x39
fixture 8pattern result: L0

Here is the kernel log of a proper working S9k

Code:

read chain[0] hardware info:
major type: 0
minor type: 2
chip level: 1
bom version: 0x10
pcb version: 0x39
fixture 8pattern result: L0

read chain[1] hardware info:
major type: 0
minor type: 2
chip level: 1
bom version: 0x10
pcb version: 0x39
fixture 8pattern result: L0

read chain[2] hardware info:
major type: 0
minor type: 2
chip level: 1
bom version: 0x10
pcb version: 0x39
fixture 8pattern result: L2

And, this is not conventional :

Code:

2020-02-14 09:07:35 driver-btm-soc.c:4877:get_working_voltage_from_eeprom: get working vol [ 9.90] from chain[0] eeprom
2020-02-14 09:07:35 power.c:232:set_working_voltage_by_chain: chain[0] working_voltage = 9.90
2020-02-14 09:07:35 driver-btm-soc.c:4877:get_working_voltage_from_eeprom: get working vol [ 9.90] from chain[1] eeprom
2020-02-14 09:07:35 power.c:232:set_working_voltage_by_chain: chain[1] working_voltage = 9.90
2020-02-14 09:07:35 driver-btm-soc.c:4877:get_working_voltage_from_eeprom: get working vol [ 9.90] from chain[2] eeprom
2020-02-14 09:07:35 power.c:232:set_working_voltage_by_chain: chain[2] working_voltage = 9.90
2020-02-14 09:07:35 driver-btm-soc.c:5560:update_highest_voltage: chain 0 hpf working voltage 9.90
2020-02-14 09:07:35 driver-btm-soc.c:5560:update_highest_voltage: chain 1 hpf working voltage 9.90
2020-02-14 09:07:35 driver-btm-soc.c:5560:update_highest_voltage: chain 2 hpf working voltage 9.90

and here is the same piece of code

Code:

1970-01-01 00:01:27 driver-btm-soc.c:4882:get_working_voltage_from_eeprom: get working vol [ 9.90] from chain[0] eeprom
1970-01-01 00:01:27 power.c:230:set_working_voltage_by_chain: chain[0] working_voltage = 9.900000
1970-01-01 00:01:27 driver-btm-soc.c:4882:get_working_voltage_from_eeprom: get working vol [ 9.90] from chain[1] eeprom
1970-01-01 00:01:27 power.c:230:set_working_voltage_by_chain: chain[1] working_voltage = 9.900000
1970-01-01 00:01:27 driver-btm-soc.c:4882:get_working_voltage_from_eeprom: get working vol [ 9.90] from chain[2] eeprom
1970-01-01 00:01:27 power.c:230:set_working_voltage_by_chain: chain[2] working_voltage = 9.900000
1970-01-01 00:01:27 driver-btm-soc.c:5554:update_highest_voltage: chain 0 hpf working voltage 9.90
1970-01-01 00:01:27 driver-btm-soc.c:5554:update_highest_voltage: chain 1 hpf working voltage 9.90
1970-01-01 00:01:27 driver-btm-soc.c:5554:update_highest_voltage: chain 2 hpf working voltage 9.90
1970-01-01 00:01:27 driver-btm-soc.c:5563:update_highest_voltage: open core at max voltage 10.20
1970-01-01 00:01:27 power.c:779:set_iic_power_to_highest_voltage_by_chain: chain[0] setting to hightest voltage: 10.20 ...
1970-01-01 00:01:28 power.c:705:set_iic_power_by_voltage: now setting voltage to : 10.200000 
1970-01-01 00:01:28 power.c:779:set_iic_power_to_highest_voltage_by_chain: chain[1] setting to hightest voltage: 10.20 ...
1970-01-01 00:01:30 power.c:705:set_iic_power_by_voltage: now setting voltage to : 10.200000 
1970-01-01 00:01:31 power.c:779:set_iic_power_to_highest_voltage_by_chain: chain[2] setting to hightest voltage: 10.20 ...
1970-01-01 00:01:31 power.c:705:set_iic_power_by_voltage: now setting voltage to : 10.200000 
1970-01-01 00:01:32 driver-btm-soc.c:1219:get_ideal_hash_rate: get ideal hash rate 14000
1970-01-01 00:01:32 eeprom.c:665:travel_eeprom_store: chain[0] data in eeprom is:
magic number: 0x7e

The code above is taken from an S9k that uses Thu Jul 11 10:29:07 CST 2019 firmware.

All stock firmware(january build),

Have you tried the latest one? it was released in December 2019> https://service.bitmain.com/support/download?product=Antminer%20S9k

[thierry4wd]

Two custom firmware already exist, i have buy only one, and run good ! S9K up to 20TH but very high temp (or need very low temp local) ... I don't know if he wants me to reveal his name ... So i assure this custom firmware is good

[mikeywith]

Two custom firmware already exist, i have buy only one, and run good ! S9K up to 20TH but very high temp (or need very low temp local) ... I don't know if he wants me to reveal his name ... So i assure this custom firmware is good

I don't understand why would a firmware developer want to keep their firmware a secret, I guess it's the exact opposite they would want. Anyway, it would be great if you could review the firmware, I am personally looking for a custom firmware for these piece of trash, I am just hoping that all or at least most of the issues I have with my Antminer S9ks are firmware related and that they would potentially go away with a better/another firmware.

I however have trust issues when it comes to custom firmware, there are only a few sources that I would trust, but a review from someone who has been around long enough like yourself will without a doubt make me a lot less worried.

[sxo13]

Hum ... your kernel log is very strange for me... i thinks used by custom firmware... is true ?

As far as I know, there is no custom firmware for S9k yet,I believe vnish should have theirs ready in a few weeks...

Cool, will keep an eye on it!

Have you tried the latest one? it was released in December 2019> https://service.bitmain.com/support/download?product=Antminer%20S9k

The original was the july one I think, I had also the december release and now the one from january....problems started with the july version and continued through the 2 recent as well.

Two custom firmware already exist, i have buy only one, and run good ! S9K up to 20TH but very high temp (or need very low temp local) ... I don't know if he wants me to reveal his name ... So i assure this custom firmware is good

Lets hear man, nothing to lose anyway   thanks.

[thierry4wd]

Just try this

https://drive.google.com/file/d/1EievYtO1mpnX8IHd8LyPYS9PLmtvygRm/view?usp=sharing


Is this a firmware bootable by SDCARD, is only ORIGINAL firmware + SSH unlocked

Just, past all file on SDCARD, power off miner, put sdcard, power on ! AND OLD SDCARD on miner for running on this firmware !

This SDCARD is utile for downgrade or install custom firmware

[sxo13]

Thanks much, the only problem is that my s9k do not have SD card slots....

[thierry4wd]

HO ! you are sur ! ? please verify ! on my know, all S9K are SDCARD slot !

https://support.bitmain.com/hc/en-us/articles/360033757513-S17-S17Pro-S9-SE-S9k-Z11-control-board-program-recovery-SD-card-flashing-with-customized-PW-


if not ... i'm curious! send picture

[mikeywith]

Just, past all file on SDCARD, power off miner, put sdcard, power on ! AND OLD SDCARD on miner for running on this firmware !

I don't understand the last part in bold, what do you mean by an old sdcard?

Thanks much, the only problem is that my s9k do not have SD card slots....

Where are you exactly trying to located the SDcard slot? I highly think you are mistaken, there MUST be an Sdcard slot on the right side of the ethernet port, just between the port and the IP report button.

[thierry4wd]

Sorry, my english is not very good ! lol

old = not take off / not remove

So, put the SDCARD (1go - 8go), power on miner, and, not remove this ! the miner booting by this sdcard

[mikeywith]

So, put the SDCARD (1go - 8go), power on miner, and, not remove this ! the miner booting by this sdcard

Ok, I think I understood, the firmware is loaded from the Sdcard and does not flash itself on the NAND memory, something similar to Braiins OS when it was first released, so what does he do if he wants to upgrade to a different firmware? I don't see this firmware running on an SD fixes any issue, what if he wants to use another custom firmware for an example, please explain more.

[sxo13]

Where are you exactly trying to located the SDcard slot? I highly think you are mistaken, there MUST be an Sdcard slot on the right side of the ethernet port, just between the port and the IP report button.

Im now not nearby the miners but Im pretty sure there is only the hole on the metal and no sd card slot behind it, or only the jumpers are missing to switch on the booting like from older s9 models ...I may be mistaken but something is off, anyway, will get checked shortly and report here the outcome based on the tips I got.

[thierry4wd]

Ok, I think I understood, the firmware is loaded from the Sdcard and does not flash itself on the NAND memory, something similar to Braiins OS when it was first released, so what does he do if he wants to upgrade to a different firmware? I don't see this firmware running on an SD fixes any issue, what if he wants to use another custom firmware for an example, please explain more.

Yes, runing mode only, no write on NAND ... but, is unlocked, you allowed for upgrade (by web gui after boot) any firmware you want !

Im now not nearby the miners but Im pretty sure there is only the hole on the metal and no sd card slot behind it, or only the jumpers are missing to switch on the booting like from older s9 models ...I may be mistaken but something is off, anyway, will get checked shortly and report here the outcome based on the tips I got.

I'm sur, you have SDCARD slot ! the port is behind

[mikeywith]

Well as long as you can flash a different firmware while booted from the Sdcard then that makes sense, i however, got the original Sdcard recovery program sent to me directly by bitmain after requesting it, i am not sure why do they "hide" that and not simply upload it to their website, that is plain stupid but nothing out of the usual for bitmain to do.

[DonnovanSA]

The log stuck on the temp.

Code:

2020-02-14 09:15:30 temperature.c:1363:process_status_value: Fatal Error: network connection lost!

It might be a temperature sensor.

The temp from PCB is fine it detects properly but after detecting the temp on the chip you got a fatal error then connection lost.

Can you check the miner's configuration and find the low power mode then enable it. then test it again. Let's see if it fixes your issue.

Just in case if still doesn't work check the kernel logs for changes and make a screenshot of your miner's status then post them here.

Had the same problem with my S9K farm found out that it was my uplink causing that, my Main Elect from the DB was running next to the network cable and caused interference I moved my cable away and ran it from a different side of the farm now I don't get any more of those errors

Hi also noted that my psu was on-top of the miner that also interfered with connection mine has been running now with no network lost

[DonnovanSA]

The log stuck on the temp.

Code:

2020-02-14 09:15:30 temperature.c:1363:process_status_value: Fatal Error: network connection lost!

It might be a temperature sensor.

The temp from PCB is fine it detects properly but after detecting the temp on the chip you got a fatal error then connection lost.

Can you check the miner's configuration and find the low power mode then enable it. then test it again. Let's see if it fixes your issue.

Just in case if still doesn't work check the kernel logs for changes and make a screenshot of your miner's status then post them here.

Hi I had the same problem (Is your PSU on top of the Miner where the control board is or your network cable running for more than a meter next to power cables. i removed mine and my psu standing next to the miner again and that error went away.) hopefully that helps for you as well.