Antminer S11 Suddenly not working

[Greekscreamer]

Hallo everyone,
relatively new to bitcoin mining, i purchased recently 4 miners S11 from bitmain.
For 3 Months now everything ok, hashing like a pro...

But suddenly two days ago i woke up, found one of those not hashing at all, there was blank indication in Hardware version and in BMminer version.
Miner Status page is everything 0
Green light flashing as though all were ok, but then Red light comes in and rebooting. And the same cycle continuous...

Kernel as follows

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: 199152K/245760K available (6345K kernel code, 231K rwdata, 1896K rodata, 1024K init, 223K bss, 30224K 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: 17184K (cca38000 - cdb00000)
hw perfevents: enabled with armv7_cortex_a9 PMU driver, 7 counters available
futex hash table entries: 512 (order: 3, 32768 bytes)
workingset: timestamp_bits=28 max_order=16 bucket_order=0
jffs2: version 2.2. (NAND) (SUMMARY)  © 2001-2006 Red Hat, Inc.
io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered (default)
dma-pl330 f8003000.ps7-dma: Loaded driver for PL330 DMAC-241330
dma-pl330 f8003000.ps7-dma: 	DBUFF-128x8bytes Num_Chans-8 Num_Peri-4 Num_Events-16
e0000000.serial: ttyPS0 at MMIO 0xe0000000 (irq = 158, base_baud = 6249999) is a xuartps
console [ttyPS0] enabled
xdevcfg f8007000.ps7-dev-cfg: ioremap 0xf8007000 to cf86e000
[drm] Initialized drm 1.1.0 20060810
brd: module loaded
loop: module loaded
CAN device driver interface
gpiod_set_value: invalid GPIO
libphy: MACB_mii_bus: probed
macb e000b000.ethernet eth0: Cadence GEM rev 0x00020118 at 0xe000b000 irq 31 (00:0a:35:00:00:00)
Generic PHY e000b000.etherne:00: attached PHY driver [Generic PHY] (mii_bus:phy_addr=e000b000.etherne:00, irq=-1)
e1000e: Intel(R) PRO/1000 Network Driver - 3.2.6-k
e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
ehci-pci: EHCI PCI platform driver
usbcore: registered new interface driver usb-storage
mousedev: PS/2 mouse device common for all mice
i2c /dev entries driver
Xilinx Zynq CpuIdle Driver started
sdhci: Secure Digital Host Controller Interface driver
sdhci: Copyright(c) Pierre Ossman
sdhci-pltfm: SDHCI platform and OF driver helper
mmc0: SDHCI controller on e0100000.ps7-sdio [e0100000.ps7-sdio] using ADMA
ledtrig-cpu: registered to indicate activity on CPUs
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
nand: device found, Manufacturer ID: 0x2c, Chip ID: 0xda
nand: Micron MT29F2G08ABAEAWP
nand: 256 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 64
nand: WARNING: pl35x-nand: the ECC used on your system is too weak compared to the one required by the NAND chip
Bad block table found at page 131008, version 0x01
Bad block table found at page 130944, version 0x01
6 ofpart partitions found on MTD device pl35x-nand
Creating 6 MTD partitions on "pl35x-nand":
0x000000000000-0x000002800000 : "BOOT.bin-env-dts-kernel"
0x000002800000-0x000004800000 : "ramfs"
0x000004800000-0x000005000000 : "configs"
0x000005000000-0x000006000000 : "reserve"
0x000006000000-0x000008000000 : "ramfs-bak"
0x000008000000-0x000010000000 : "reserve1"
NET: Registered protocol family 10
sit: IPv6 over IPv4 tunneling driver
NET: Registered protocol family 17
can: controller area network core (rev 20120528 abi 9)
NET: Registered protocol family 29
can: raw protocol (rev 20120528)
can: broadcast manager protocol (rev 20120528 t)
can: netlink gateway (rev 20130117) max_hops=1
zynq_pm_ioremap: no compatible node found for 'xlnx,zynq-ddrc-a05'
zynq_pm_late_init: Unable to map DDRC IO memory.
Registering SWP/SWPB emulation handler
hctosys: unable to open rtc device (rtc0)
ALSA device list:
  No soundcards found.
RAMDISK: gzip image found at block 0
EXT4-fs (ram0): couldn't mount as ext3 due to feature incompatibilities
EXT4-fs (ram0): mounted filesystem without journal. Opts: (null)
VFS: Mounted root (ext4 filesystem) on device 1:0.
devtmpfs: mounted
Freeing unused kernel memory: 1024K (c0a00000 - c0b00000)
EXT4-fs (ram0): re-mounted. Opts: block_validity,delalloc,barrier,user_xattr
random: dd urandom read with 0 bits of entropy available
ubi0: attaching mtd2
ubi0: scanning is finished
ubi0: attached mtd2 (name "configs", size 8 MiB)
ubi0: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
ubi0: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
ubi0: VID header offset: 2048 (aligned 2048), data offset: 4096
ubi0: good PEBs: 64, bad PEBs: 0, corrupted PEBs: 0
ubi0: user volume: 1, internal volumes: 1, max. volumes count: 128
ubi0: max/mean erase counter: 436/305, WL threshold: 4096, image sequence number: 2142463726
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 AC5E70A5-96DE-4ED8-BAA0-FE7F035A1963, 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: 3/1, WL threshold: 4096, image sequence number: 436397348
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 7FDDA6AD-21FF-44A6-B266-0927BA62D766, 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
main.c:13937: log_level = 4
main.c:13964: This is XILINX board. Totalram:       239353856
main.c:13982: Detect 256MB control board of XILINX
driver-bitmain.c:1777: mmap axi_fpga_addr = 0xb6f4c000
driver-bitmain.c:1782: axi_fpga_addr data = 0xb00d
driver-bitmain.c:1798: mmap fpga_mem_addr = 0xb5d50000
driver-bitmain.c:995: forceFreq=-1 forceFlag=0
driver-bitmain.c:1697: min work minertest[0]:912


main.c:8515: DETECT HW version=000ab00d
main.c:14009: miner ID : 8058842679104814
main.c:14038: Miner Type = S9+
main.c:14046: AsicType = 1387
main.c:14049: real AsicNum = 84
main.c:14142: use critical mode to search freq...
driver-bitmain.c:1877: get PLUG ON=0x00000007
driver-bitmain.c:1947: Find hashboard on Chain[0]
driver-bitmain.c:1947: Find hashboard on Chain[1]
driver-bitmain.c:1947: Find hashboard on Chain[2]
dsPIC33EP16GS202.c:164: dsPIC33EP16GS202_reset_pic failed on Chain[0]!
dsPIC33EP16GS202.c:164: dsPIC33EP16GS202_reset_pic failed on Chain[0]!
dsPIC33EP16GS202.c:164: dsPIC33EP16GS202_reset_pic failed on Chain[0]!
main.c:2173: chain[0] PIC jump to app
dsPIC33EP16GS202.c:117: dsPIC33EP16GS202_jump_to_app_from_loader failed on Chain[0]!
dsPIC33EP16GS202.c:117: dsPIC33EP16GS202_jump_to_app_from_loader failed on Chain[0]!
dsPIC33EP16GS202.c:117: dsPIC33EP16GS202_jump_to_app_from_loader failed on Chain[0]!
dsPIC33EP16GS202.c:61: dsPIC33EP16GS202_get_pic_sw_version failed on Chain[0]!
dsPIC33EP16GS202.c:61: dsPIC33EP16GS202_get_pic_sw_version failed on Chain[0]!
dsPIC33EP16GS202.c:61: dsPIC33EP16GS202_get_pic_sw_version failed on Chain[0]!
main.c:2178: Check chain[0] PIC fw version=0xff
main.c:2173: chain[1] PIC jump to app
main.c:2178: Check chain[1] PIC fw version=0xa4
main.c:2173: chain[2] PIC jump to app
main.c:2178: Check chain[2] PIC fw version=0xa4
main.c:8830: Chain[0] read_freq_badcores : 0xc0 0xc0 0xc0 0xc0 0xc0 0xc0 0xc0 0xc0 0xc0 0xc0 0xc0 0xc0 0xc0 0xc0 0xc0 0xc0 0xc0 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 
main.c:8842: chain[0]: [86:86] [86:86] [86:86] [86:86] [86:86] [86:86] [86:86] [86:86]
main.c:8861: chain[0]: [86:86] [86:86] [86:86] [86:86] [86:86] [86:86] [86:86] [86:86]
main.c:9093: chain[0] has no freq in PIC! Will use default freq=0 and jump over...
main.c:8830: Chain[1] read_freq_badcores : 0x7d 0xd7 0x52 0x56 0x56 0x52 0x56 0x56 0x56 0x56 0x52 0x56 0x56 0x52 0x56 0x52 0x56 0x56 0x52 0x56 0x56 0x56 0x52 0x56 0x52 0x56 0x56 0x56 0x52 0x52 0x56 0x56 0x56 0x52 0x56 0x56 0x52 0x56 0x52 0x56 0x56 0x56 0x52 0x56 0x56 0x56 0x52 0x56 0x56 0x52 0x56 0x56 0x52 0x56 0x52 0x56 0x56 0x56 0x52 0x56 0x56 0x52 0x56 0x56 0x52 0x56 0x52 0x56 0x56 0x56 0x52 0x52 0x56 0x56 0x56 0x56 0x52 0x56 0x52 0x56 0x56 0x52 0x56 0x56 0x56 0x52 0xcf 0x19 0x00 0x00 0xc8 0xdf 0xdd 0xdf 0xdf 0x77 0xf7 0xfd 0xfd 0x7d 0xf7 0x77 0xdf 0x7d 0x7f 0xdf 0x7d 0x7f 0xdf 0xf7 0xd7 0xf7 0xee 0x14 0x00 0x00 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 
main.c:8842: chain[1]: [255:255] [255:255] [255:255] [255:255] [255:255] [255:255] [255:255] [255:255]
main.c:8861: chain[1]: [255:255] [255:255] [255:255] [255:255] [255:255] [255:255] [255:255] [255:255]
main.c:8948: has freq in PIC, will disable freq setting.
main.c:9022: chain[1] has freq in PIC and will jump over...
main.c:9024: Chain[1] has core num in PIC
main.c:8830: Chain[2] read_freq_badcores : 0x7d 0xd7 0x5a 0x4e 0x56 0x4e 0x56 0x5a 0x5a 0x4e 0x56 0x5a 0x56 0x4e 0x5a 0x56 0x4e 0x56 0x4e 0x5a 0x5a 0x56 0x4e 0x56 0x4e 0x5a 0x5a 0x4e 0x56 0x5a 0x56 0x4e 0x56 0x4e 0x5a 0x56 0x5a 0x4e 0x5a 0x4e 0x56 0x56 0x4e 0x5a 0x4e 0x5a 0x56 0x56 0x5a 0x4e 0x4e 0x5a 0x56 0x5a 0x4e 0x56 0x4e 0x5a 0x56 0x4e 0x56 0x5a 0x5a 0x56 0x4e 0x5a 0x56 0x4e 0x4e 0x56 0x5a 0x56 0x5a 0x4e 0x4e 0x5a 0x56 0x5a 0x4e 0x56 0x5a 0x56 0x4e 0x56 0x4e 0x5a 0x5a 0x1a 0x00 0x00 0xc8 0xf8 0xc2 0xe2 0xb8 0x83 0x3b 0xac 0xec 0xc8 0xac 0x33 0xca 0x23 0x3b 0x2e 0x38 0xbe 0xc8 0x23 0x8b 0x3b 0xc8 0x14 0x00 0x00 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 
main.c:8842: chain[2]: [255:255] [255:255] [255:255] [255:255] [255:255] [255:255] [255:255] [255:255]
main.c:8861: chain[2]: [255:255] [255:255] [255:255] [255:255] [255:255] [255:255] [255:255] [255:255]
main.c:8948: has freq in PIC, will disable freq setting.
main.c:9022: chain[2] has freq in PIC and will jump over...
main.c:9024: Chain[2] has core num in PIC
main.c:9128: get PIC voltage=255 on chain[0], value=710
main.c:9128: get PIC voltage=0 on chain[1], value=930
main.c:9128: get PIC voltage=85 on chain[2], value=750
main.c:3512: chain[0] heart beat fail 1 times.
main.c:9294: chain[0] temp offset record: 29,29,29,29,29,29,29,29
main.c:9311: chain[0] temp chip I2C addr=0x98
main.c:9294: chain[1] temp offset record: -1,-1,-1,-1,-1,-1,-1,-1
main.c:9311: chain[1] temp chip I2C addr=0x98
main.c:9294: chain[2] temp offset record: -1,-1,-1,-1,-1,-1,-1,-1
main.c:9311: chain[2] temp chip I2C addr=0x98
main.c:13901: total_exist_chain_num = 3
main.c:14583: restart Miner chance num=0
main.c:14623: waiting for receive_func to exit!
main.c:14637: waiting for pic heart to exit!
main.c:13872: bmminer not found= 1037 root      2156 S    grep bmminer

main.c:14681: bmminer not found, restart bmminer ...
driver-btm-c5.c:12205:bitmain_c5_init: This is the first time running after searching freq!
driver-btm-c5.c:12265:bitmain_c5_init: Detect 256MB control board of XILINX
driver-btm-c5.c:12284:bitmain_c5_init: Miner Type = S9+
driver-btm-c5.c:12291:bitmain_c5_init: Miner compile time: Wed Jan 23 22:51:52 CST 2019 type: Antminer S11
driver-btm-c5.c:12371:bitmain_c5_init: miner ID : 8058842679104814
driver-btm-c5.c:3031:check_fan_beforeInit: get fan[0] speed=3240
dsPIC33EP16GS202.c:166:dsPIC33EP16GS202_reset_pic: dsPIC33EP16GS202_reset_pic failed on Chain[0]!
dsPIC33EP16GS202.c:166:dsPIC33EP16GS202_reset_pic: dsPIC33EP16GS202_reset_pic failed on Chain[0]!
dsPIC33EP16GS202.c:166:dsPIC33EP16GS202_reset_pic: dsPIC33EP16GS202_reset_pic failed on Chain[0]!
driver-btm-c5.c:12528:bitmain_c5_init: Checking fans...
driver-btm-c5.c:3031:check_fan_beforeInit: get fan[0] speed=4560
driver-btm-c5.c:3031:check_fan_beforeInit: get fan[1] speed=4560
driver-btm-c5.c:3031:check_fan_beforeInit: get fan[0] speed=4560
driver-btm-c5.c:3031:check_fan_beforeInit: get fan[1] speed=4560
driver-btm-c5.c:3031:check_fan_beforeInit: get fan[0] speed=4560
driver-btm-c5.c:3031:check_fan_beforeInit: get fan[1] speed=4560
dsPIC33EP16GS202.c:166:dsPIC33EP16GS202_reset_pic: dsPIC33EP16GS202_reset_pic failed on Chain[0]!
dsPIC33EP16GS202.c:166:dsPIC33EP16GS202_reset_pic: dsPIC33EP16GS202_reset_pic failed on Chain[0]!
dsPIC33EP16GS202.c:166:dsPIC33EP16GS202_reset_pic: dsPIC33EP16GS202_reset_pic failed on Chain[0]!
driver-btm-c5.c:1767:jump_to_app_CheckAndRestorePIC_T9_18: chain[0] PIC jump to app
driver-btm-c5.c:1768:jump_to_app_CheckAndRestorePIC_T9_18: chain[0] PIC jump to app
dsPIC33EP16GS202.c:118:dsPIC33EP16GS202_jump_to_app_from_loader: dsPIC33EP16GS202_jump_to_app_from_loader failed on Chain[0]!
dsPIC33EP16GS202.c:118:dsPIC33EP16GS202_jump_to_app_from_loader: dsPIC33EP16GS202_jump_to_app_from_loader failed on Chain[0]!
dsPIC33EP16GS202.c:118:dsPIC33EP16GS202_jump_to_app_from_loader: dsPIC33EP16GS202_jump_to_app_from_loader failed on Chain[0]!
dsPIC33EP16GS202.c:61:dsPIC33EP16GS202_get_pic_sw_version: dsPIC33EP16GS202_get_pic_sw_version failed on Chain[0]!
dsPIC33EP16GS202.c:61:dsPIC33EP16GS202_get_pic_sw_version: dsPIC33EP16GS202_get_pic_sw_version failed on Chain[0]!
dsPIC33EP16GS202.c:61:dsPIC33EP16GS202_get_pic_sw_version: dsPIC33EP16GS202_get_pic_sw_version failed on Chain[0]!
driver-btm-c5.c:1773:jump_to_app_CheckAndRestorePIC_T9_18: Check chain[0] PIC fw version=0xff
driver-btm-c5.c:12981:bitmain_c5_init: Chain[0] read_freq_badcores : 0x7d 0xd7 0x56 0x52 0x56 0x56 0x56 0x52 0x56 0x56 0x52 0x56 0x52 0x52 0x52 0x52 0x52 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 0x56 
driver-btm-c5.c:13020:bitmain_c5_init: Chain[J1] has backup chain_voltage=1075
power.c:238:set_fixed_voltage: s9_84_fixed_voltage = 10.750000
driver-btm-c5.c:13027:bitmain_c5_init: S9+: use voltage limit rules on single board!
driver-btm-c5.c:13031:bitmain_c5_init: S9+ fix Chain[J1] test patten OK temp=60
driver-btm-c5.c:1767:jump_to_app_CheckAndRestorePIC_T9_18: chain[1] PIC jump to app
driver-btm-c5.c:1768:jump_to_app_CheckAndRestorePIC_T9_18: chain[1] PIC jump to app
driver-btm-c5.c:1773:jump_to_app_CheckAndRestorePIC_T9_18: Check chain[1] PIC fw version=0xa4
driver-btm-c5.c:12981:bitmain_c5_init: Chain[1] read_freq_badcores : 0x7d 0xd7 0x52 0x56 0x56 0x52 0x56 0x56 0x56 0x56 0x52 0x56 0x56 0x52 0x56 0x52 0x56 0x56 0x52 0x56 0x56 0x56 0x52 0x56 0x52 0x56 0x56 0x56 0x52 0x52 0x56 0x56 0x56 0x52 0x56 0x56 0x52 0x56 0x52 0x56 0x56 0x56 0x52 0x56 0x56 0x56 0x52 0x56 0x56 0x52 0x56 0x56 0x52 0x56 0x52 0x56 0x56 0x56 0x52 0x56 0x56 0x52 0x56 0x56 0x52 0x56 0x52 0x56 0x56 0x56 0x52 0x52 0x56 0x56 0x56 0x56 0x52 0x56 0x52 0x56 0x56 0x52 0x56 0x56 0x56 0x52 0xcf 0x19 0x00 0x00 0xc8 0xdf 0xdd 0xdf 0xdf 0x77 0xf7 0xfd 0xfd 0x7d 0xf7 0x77 0xdf 0x7d 0x7f 0xdf 0x7d 0x7f 0xdf 0xf7 0xd7 0xf7 0xee 0x14 0x00 0x00 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 
driver-btm-c5.c:13020:bitmain_c5_init: Chain[J2] has backup chain_voltage=1075
power.c:238:set_fixed_voltage: s9_84_fixed_voltage = 10.750000
driver-btm-c5.c:13027:bitmain_c5_init: S9+: use voltage limit rules on single board!
driver-btm-c5.c:13031:bitmain_c5_init: S9+ fix Chain[J2] test patten OK temp=60
driver-btm-c5.c:1767:jump_to_app_CheckAndRestorePIC_T9_18: chain[2] PIC jump to app
driver-btm-c5.c:1768:jump_to_app_CheckAndRestorePIC_T9_18: chain[2] PIC jump to app
driver-btm-c5.c:1773:jump_to_app_CheckAndRestorePIC_T9_18: Check chain[2] PIC fw version=0xa4
driver-btm-c5.c:12981:bitmain_c5_init: Chain[2] read_freq_badcores : 0x7d 0xd7 0x5a 0x4e 0x56 0x4e 0x56 0x5a 0x5a 0x4e 0x56 0x5a 0x56 0x4e 0x5a 0x56 0x4e 0x56 0x4e 0x5a 0x5a 0x56 0x4e 0x56 0x4e 0x5a 0x5a 0x4e 0x56 0x5a 0x56 0x4e 0x56 0x4e 0x5a 0x56 0x5a 0x4e 0x5a 0x4e 0x56 0x56 0x4e 0x5a 0x4e 0x5a 0x56 0x56 0x5a 0x4e 0x4e 0x5a 0x56 0x5a 0x4e 0x56 0x4e 0x5a 0x56 0x4e 0x56 0x5a 0x5a 0x56 0x4e 0x5a 0x56 0x4e 0x4e 0x56 0x5a 0x56 0x5a 0x4e 0x4e 0x5a 0x56 0x5a 0x4e 0x56 0x5a 0x56 0x4e 0x56 0x4e 0x5a 0x5a 0x1a 0x00 0x00 0xc8 0xf8 0xc2 0xe2 0xb8 0x83 0x3b 0xac 0xec 0xc8 0xac 0x33 0xca 0x23 0x3b 0x2e 0x38 0xbe 0xc8 0x23 0x8b 0x3b 0xc8 0x14 0x00 0x00 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 
driver-btm-c5.c:13020:bitmain_c5_init: Chain[J3] has backup chain_voltage=1075
power.c:238:set_fixed_voltage: s9_84_fixed_voltage = 10.750000
driver-btm-c5.c:13027:bitmain_c5_init: S9+: use voltage limit rules on single board!
driver-btm-c5.c:13031:bitmain_c5_init: S9+ fix Chain[J3] test patten OK temp=60
driver-btm-c5.c:12164:init_exist_chain_table: total_exist_chain_num = 3
power.c:148:power_check_protocal_type: power protocal f5, using package cmd
power.c:173:power_type_detect: start detect power type
power.c:181:power_type_detect: init gpio907
power.c:211:power_type_detect: power type is APW8 new type
driver-btm-c5.c:9753:pic_heart_beat_func: chain[0] heart beat fail 1 times.
power.c:349:get_power_iic_value_from_voltage: iic_index for voltage[52] = 10
power.c:583:set_iic_power_voltage: voltage_tunning, set to 10.900000, N=52
power.c:349:get_power_iic_value_from_voltage: iic_index for voltage[26] = 11
power.c:583:set_iic_power_voltage: voltage_tunning, set to 11.050000, N=26
dsPIC33EP16GS202.c:214:dsPIC33EP16GS202_enable_pic_dc_dc: dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[0]!
dsPIC33EP16GS202.c:214:dsPIC33EP16GS202_enable_pic_dc_dc: dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[0]!
dsPIC33EP16GS202.c:214:dsPIC33EP16GS202_enable_pic_dc_dc: dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[0]!
driver-btm-c5.c:13258:bitmain_c5_init: Chain[J1] orignal chain_voltage_pic=138 value=730
driver-btm-c5.c:13275:bitmain_c5_init: Chain[J1] will use backup chain_voltage_pic=1075 [0]
driver-btm-c5.c:13285:bitmain_c5_init: Chain[J1] get working chain_voltage_pic=0
driver-btm-c5.c:13258:bitmain_c5_init: Chain[J2] orignal chain_voltage_pic=0 value=930
driver-btm-c5.c:13275:bitmain_c5_init: Chain[J2] will use backup chain_voltage_pic=1075 [0]
driver-btm-c5.c:13285:bitmain_c5_init: Chain[J2] get working chain_voltage_pic=0
driver-btm-c5.c:13258:bitmain_c5_init: Chain[J3] orignal chain_voltage_pic=85 value=750
driver-btm-c5.c:13275:bitmain_c5_init: Chain[J3] will use backup chain_voltage_pic=1075 [0]
driver-btm-c5.c:13285:bitmain_c5_init: Chain[J3] get working chain_voltage_pic=0
driver-btm-c5.c:9753:pic_heart_beat_func: chain[0] heart beat fail 2 times.
driver-btm-c5.c:13376:bitmain_c5_init: Chain[J1] has 0 asic
dsPIC33EP16GS202.c:214:dsPIC33EP16GS202_enable_pic_dc_dc: dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[0]!
dsPIC33EP16GS202.c:214:dsPIC33EP16GS202_enable_pic_dc_dc: dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[0]!
dsPIC33EP16GS202.c:214:dsPIC33EP16GS202_enable_pic_dc_dc: dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[0]!
dsPIC33EP16GS202.c:214:dsPIC33EP16GS202_enable_pic_dc_dc: dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[0]!
dsPIC33EP16GS202.c:214:dsPIC33EP16GS202_enable_pic_dc_dc: dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[0]!
dsPIC33EP16GS202.c:214:dsPIC33EP16GS202_enable_pic_dc_dc: dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[0]!
driver-btm-c5.c:9753:pic_heart_beat_func: chain[0] heart beat fail 3 times.
driver-btm-c5.c:13404:bitmain_c5_init: retry Chain[J1] has 0 asic
dsPIC33EP16GS202.c:214:dsPIC33EP16GS202_enable_pic_dc_dc: dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[0]!
dsPIC33EP16GS202.c:214:dsPIC33EP16GS202_enable_pic_dc_dc: dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[0]!
dsPIC33EP16GS202.c:214:dsPIC33EP16GS202_enable_pic_dc_dc: dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[0]!
dsPIC33EP16GS202.c:214:dsPIC33EP16GS202_enable_pic_dc_dc: dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[0]!
dsPIC33EP16GS202.c:214:dsPIC33EP16GS202_enable_pic_dc_dc: dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[0]!
dsPIC33EP16GS202.c:214:dsPIC33EP16GS202_enable_pic_dc_dc: dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[0]!
driver-btm-c5.c:9753:pic_heart_beat_func: chain[0] heart beat fail 4 times.
driver-btm-c5.c:13404:bitmain_c5_init: retry Chain[J1] has 0 asic
dsPIC33EP16GS202.c:214:dsPIC33EP16GS202_enable_pic_dc_dc: dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[0]!
dsPIC33EP16GS202.c:214:dsPIC33EP16GS202_enable_pic_dc_dc: dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[0]!
dsPIC33EP16GS202.c:214:dsPIC33EP16GS202_enable_pic_dc_dc: dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[0]!
dsPIC33EP16GS202.c:214:dsPIC33EP16GS202_enable_pic_dc_dc: dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[0]!

Tried already several reboots, unplug re-plug, no results.
Tried downloading all available official Firmwares for the model from BITMAIN and re-flashing them, not working either, i receive same kernel.
Checked the pool for spelling errors, changed pools.
Tried also switching to Low Power - not working
LAN cable in another LAN port etc.
Change the power plug not helps.

Every Help appreciated, do you thing is hardware or software? I still have warranty from Bitmain.
Thanks in advance.

[Hockeybum]

Have you tried swapping the PSU from another miner?

[tim-bc]

It looks like there is an issue with the PIC on chain[0] (the board that is plugged into connector J1 on the control board). I would try testing the miner with that board disconnected, if possible, to see if that is what's causing the miner to keep rebooting itself.

[BitMaxz]

It looks like this one has a program issue.

Code:

main.c:2178: Check chain[0] PIC fw version=0xff

Compared to this two chain

Code:

main.c:2173: chain[1] PIC jump to app
main.c:2178: Check chain[1] PIC fw version=0xa4
main.c:2173: chain[2] PIC jump to app
main.c:2178: Check chain[2] PIC fw version=0xa4

One of the hashboard might have a problem related to the program or hardware. Can you try to swap the cable(18 pin cable) from another hashboard and check if there's changes on the kernel logs.


Or you need to test and follow what tim-bc suggested.

If its a program issue you will need to do is to reflash the hashboard with working hex file but since your miner still under warranty much better to don't touch anything from your miner then contact the bitmain support and send it back for warranty repair.

[Greekscreamer]

Thanks a lot for your replies,
the advises you sent will be very useful i think, first of all because the miner has warranty i will contact Bitmain support for instructions, and as soon as i have news i will update.
If the problem is resolved with common troubleshooting i will write here exactly what was faulty. Thank you.

[mikeywith]

Waiting for bitmain to solve your problem is a waste of time, all they will tell you is " reboot,reset" and when they get tired of your emails they will ask you to ship the gear back to them, so while you do all that try everything that doesn't void the warranty on your miner.

This could very likely be power related, if trying a different psu from abother miner won't void your miner ( probably won't, but dyor) then that would be the first thing i would do, also check the data cable on chain 0.

[Greekscreamer]

Hi Everyone,
Regarding the Problem i did the following:
I left the miner switced off for 5 Days, then when i did had time, i powered on the miner in low power mode and everything worked!

I then tried putting it back to normal power mode, but miner restarted every 5-10 minutes, and i discoverd in Kernel Log the following:

Code:

power.c:587:get_min_voltage: board[0] voltage: 0.000000
power.c:593:get_min_voltage: min voltage: 0.000000
power.c:349:get_power_iic_value_from_voltage: iic_index for voltage[78] = 10
power.c:626:set_iic_power_voltage: voltage_tunning, set to 10.750000, N=78
power.c:538:dsPIC33EP16GS202_pic_get_an_voltage2: Couldn't hear AN voltage response from IIC[1]
read_back_data::
  0000  ff ff ff ff ff ff ff ff ff                       .........
power.c:538:dsPIC33EP16GS202_pic_get_an_voltage2: Couldn't hear AN voltage response from IIC[1]
read_back_data::
  0000  ff ff ff ff ff ff ff ff ff                       .........
power.c:587:get_min_voltage: board[1] voltage: 0.000000
power.c:538:dsPIC33EP16GS202_pic_get_an_voltage2: Couldn't hear AN voltage response from IIC[2]
read_back_data::
  0000  ff ff ff ff ff ff ff ff ff                       .........
power.c:538:dsPIC33EP16GS202_pic_get_an_voltage2: Couldn't hear AN voltage response from IIC[2]
read_back_data::
  0000  ff ff ff ff ff ff ff ff ff                       .........
power.c:587:get_min_voltage: board[2] voltage: 0.000000
power.c:538:dsPIC33EP16GS202_pic_get_an_voltage2: Couldn't hear AN voltage response from IIC[0]
read_back_data::
  0000  ff ff ff ff ff ff ff ff ff                       .........
power.c:538:dsPIC33EP16GS202_pic_get_an_voltage2: Couldn't hear AN voltage response from IIC[0]
read_back_data::
  0000  ff ff ff ff ff ff ff ff ff                       .........
power.c:587:get_min_voltage: board[0] voltage: 0.000000
power.c:593:get_min_voltage: min voltage: 0.000000
power.c:349:get_power_iic_value_from_voltage: iic_index for voltage[78] = 10
power.c:626:set_iic_power_voltage: voltage_tunning, set to 10.750000, N=78
power.c:538:dsPIC33EP16GS202_pic_get_an_voltage2: Couldn't hear AN voltage response from IIC[1]
read_back_data::
  0000  ff ff ff ff ff ff ff ff ff                       .........
power.c:538:dsPIC33EP16GS202_pic_get_an_voltage2: Couldn't hear AN voltage response from IIC[1]
read_back_data::
  0000  ff ff ff ff ff ff ff ff ff                       .........
power.c:587:get_min_voltage: board[1] voltage: 0.000000
power.c:538:dsPIC33EP16GS202_pic_get_an_voltage2: Couldn't hear AN voltage response from IIC[2]
read_back_data::
  0000  ff ff ff ff ff ff ff ff ff                       .........
power.c:538:dsPIC33EP16GS202_pic_get_an_voltage2: Couldn't hear AN voltage response from IIC[2]
read_back_data::
  0000  ff ff ff ff ff ff ff ff ff                       .........
power.c:587:get_min_voltage: board[2] voltage: 0.000000
power.c:538:dsPIC33EP16GS202_pic_get_an_voltage2: Couldn't hear AN voltage response from IIC[0]
read_back_data::
  0000  ff ff ff ff ff ff ff ff ff                       .........
power.c:538:dsPIC33EP16GS202_pic_get_an_voltage2: Couldn't hear AN voltage response from IIC[0]
read_back_data::
  0000  ff ff ff ff ff ff ff ff ff                       .........
power.c:587:get_min_voltage: board[0] voltage: 0.000000
power.c:593:get_min_voltage: min voltage: 0.000000
power.c:349:get_power_iic_value_from_voltage: iic_index for voltage[78] = 10
power.c:626:set_iic_power_voltage: voltage_tunning, set to 10.750000, N=78
power.c:538:dsPIC33EP16GS202_pic_get_an_voltage2: Couldn't hear AN voltage response from IIC[1]
read_back_data::
  0000  ff ff ff ff ff ff ff ff ff                       .........
power.c:538:dsPIC33EP16GS202_pic_get_an_voltage2: Couldn't hear AN voltage response from IIC[1]
read_back_data::
  0000  ff ff ff ff ff ff ff ff ff                       .........
power.c:587:get_min_voltage: board[1] voltage: 0.000000
power.c:538:dsPIC33EP16GS202_pic_get_an_voltage2: Couldn't hear AN voltage response from IIC[2]
read_back_data::
  0000  ff ff ff ff ff ff ff ff ff                       .........
power.c:538:dsPIC33EP16GS202_pic_get_an_voltage2: Couldn't hear AN voltage response from IIC[2]
read_back_data::
  0000  ff ff ff ff ff ff ff ff ff                       .........
power.c:587:get_min_voltage: board[2] voltage: 0.000000
power.c:538:dsPIC33EP16GS202_pic_get_an_voltage2: Couldn't hear AN voltage response from IIC[0]
read_back_data::
  0000  ff ff ff ff ff ff ff ff ff                       .........
power.c:538:dsPIC33EP16GS202_pic_get_an_voltage2: Couldn't hear AN voltage response from IIC[0]
read_back_data::
  0000  ff ff ff ff ff ff ff ff ff                       .........
power.c:587:get_min_voltage: board[0] voltage: 0.000000
power.c:593:get_min_voltage: min voltage: 0.000000
power.c:349:get_power_iic_value_from_voltage: iic_index for voltage[78] = 10
power.c:626:set_iic_power_voltage: voltage_tunning, set to 10.750000, N=78
power.c:538:dsPIC33EP16GS202_pic_get_an_voltage2: Couldn't hear AN voltage response from IIC[1]
read_back_data::
  0000  ff ff ff ff ff ff ff ff ff                       .........
power.c:538:dsPIC33EP16GS202_pic_get_an_voltage2: Couldn't hear AN voltage response from IIC[1]
read_back_data::
  0000  ff ff ff ff ff ff ff ff ff                       .........
power.c:587:get_min_voltage: board[1] voltage: 0.000000
power.c:538:dsPIC33EP16GS202_pic_get_an_voltage2: Couldn't hear AN voltage response from IIC[2]
read_back_data::
  0000  ff ff ff ff ff ff ff ff ff                       .........
power.c:538:dsPIC33EP16GS202_pic_get_an_voltage2: Couldn't hear AN voltage response from IIC[2]
read_back_data::
  0000  ff ff ff ff ff ff ff ff ff                       .........
power.c:587:get_min_voltage: board[2] voltage: 0.000000
power.c:538:dsPIC33EP16GS202_pic_get_an_voltage2: Couldn't hear AN voltage response from IIC[0]
read_back_data::
  0000  ff ff ff ff ff ff ff ff ff                       .........
power.c:538:dsPIC33EP16GS202_pic_get_an_voltage2: Couldn't hear AN voltage response from IIC[0]
read_back_data::
  0000  ff ff ff ff ff ff ff ff ff                       .........
power.c:587:get_min_voltage: board[0] voltage: 0.000000
power.c:593:get_min_voltage: min voltage: 0.000000
power.c:349:get_power_iic_value_from_voltage: iic_index for voltage[78] = 10
power.c:626:set_iic_power_voltage: voltage_tunning, set to 10.750000, N=78
power.c:538:dsPIC33EP16GS202_pic_get_an_voltage2: Couldn't hear AN voltage response from IIC[1]
read_back_data::
  0000  ff ff ff ff ff ff ff ff ff                       .........
power.c:538:dsPIC33EP16GS202_pic_get_an_voltage2: Couldn't hear AN voltage response from IIC[1]
read_back_data::
  0000  ff ff ff ff ff ff ff ff ff                       .........
power.c:587:get_min_voltage: board[1] voltage: 0.000000
power.c:538:dsPIC33EP16GS202_pic_get_an_voltage2: Couldn't hear AN voltage response from IIC[2]
read_back_data::
  0000  ff ff ff ff ff ff ff ff ff                       .........
power.c:538:dsPIC33EP16GS202_pic_get_an_voltage2: Couldn't hear AN voltage response from IIC[2]
read_back_data::
  0000  ff ff ff ff ff ff ff ff ff                       .........
power.c:587:get_min_voltage: board[2] voltage: 0.000000
power.c:538:dsPIC33EP16GS202_pic_get_an_voltage2: Couldn't hear AN voltage response from IIC[0]
read_back_data::
  0000  ff ff ff ff ff ff ff ff ff                       .........
power.c:538:dsPIC33EP16GS202_pic_get_an_voltage2: Couldn't hear AN voltage response from IIC[0]
read_back_data::
  0000  ff ff ff ff ff ff ff ff ff                       .........
power.c:587:get_min_voltage: board[0] voltage: 0.000000
power.c:593:get_min_voltage: min voltage: 0.000000
power.c:349:get_power_iic_value_from_voltage: iic_index for voltage[78] = 10
power.c:626:set_iic_power_voltage: voltage_tunning, set to 10.750000, N=78
power.c:538:dsPIC33EP16GS202_pic_get_an_voltage2: Couldn't hear AN voltage response from IIC[1]
read_back_data::
  0000  ff ff ff ff ff ff ff ff ff                       .........
power.c:538:dsPIC33EP16GS202_pic_get_an_voltage2: Couldn't hear AN voltage response from IIC[1]
read_back_data::
  0000  ff ff ff ff ff ff ff ff ff                       .........
power.c:587:get_min_voltage: board[1] voltage: 0.000000
power.c:538:dsPIC33EP16GS202_pic_get_an_voltage2: Couldn't hear AN voltage response from IIC[2]
read_back_data::
  0000  ff ff ff ff ff ff ff ff ff                       .........
power.c:538:dsPIC33EP16GS202_pic_get_an_voltage2: Couldn't hear AN voltage response from IIC[2]
read_back_data::
  0000  ff ff ff ff ff ff ff ff ff                       .........
power.c:587:get_min_voltage: board[2] voltage: 0.000000
power.c:538:dsPIC33EP16GS202_pic_get_an_voltage2: Couldn't hear AN voltage response from IIC[0]
read_back_data::
  0000  ff ff ff ff ff ff ff ff ff                       .........
power.c:538:dsPIC33EP16GS202_pic_get_an_voltage2: Couldn't hear AN voltage response from IIC[0]
read_back_data::
  0000  ff ff ff ff ff ff ff ff ff                       .........
power.c:587:get_min_voltage: board[0] voltage: 0.000000
power.c:593:get_min_voltage: min voltage: 0.000000
power.c:349:get_power_iic_value_from_voltage: iic_index for voltage[78] = 10
power.c:626:set_iic_power_voltage: voltage_tunning, set to 10.750000, N=78
power.c:629:set_iic_power_voltage: power voltage abnormal
driver-btm-c5.c:12205:stop_mining: power abnormal
do read_temp_func once...
Done check_asic_reg
Max pcb temp : -100
FAN PWM: 0
read_temp_func Done!
CRC error counter=13034

Looks like a PSU issue, not able to handle the full power mode.
Since then when i put it in Low power everything working stable.
I decided to keep it as it is, because 3.5 TH/s difference doesnt worth shipping costs...

[BitMaxz]

I thought that you already tried it on the low power mode as you said before and didn't work?

Anyway, it looks like the Max PCB temp of your miner reach 100c according to your logs.
According to Bitmain the Max PCB temp of s11 is 95 degrees so it means the hashboard exceeds the maximum PCB temp that is why the miner keeps restarting due to high-temperature protection mode.
The other reason is that the FAN PWM shows zero "0" possible that the fan is not detected that is why the miner turn to idle mode.

How about your room temperature? It might be because of high room temperature that is why all of your miners suddenly not working.

[mikeywith]

Anyway, it looks like the Max PCB temp of your miner reach 100c according to your logs.

Not really!

Code:

Max pcb temp : -100

Max temp does not mean actual temp, it literally means maximum pcb temp, the temp reading however can be found in another line of the kernel log

Code:

driver-btm-c5.c:13027:bitmain_c5_init: S9+: use voltage limit rules on single board!
driver-btm-c5.c:13031:bitmain_c5_init: S9+ fix Chain[J1] test patten OK temp=60

so as far as heat concern, there is no heat issue here.

Now coming to the fan , it does show 0, and it probably does not spin at all, but this is not because there is anything wrong with it, the fans are tested way before that stage , here is the line

Code:

driver-btm-c5.c:3031:check_fan_beforeInit: get fan[0] speed=4560
driver-btm-c5.c:3031:check_fan_beforeInit: get fan[1] speed=4560

but if you read 4 line further above you can clearly see

Code:

power.c:629:set_iic_power_voltage: power voltage abnormal
driver-btm-c5.c:12205:stop_mining: power abnormal

so at this line, the miner did really stop mining, therefore it shuts the fan off.

Now back to the real issue, since the miner runs fine on low power mode but not in normal, I have 2 simple theories to lay down.

1-The psu can't handle the current needed by the miner running in normal mode, but this theory is unlikely

you can troubleshoot this by trying another PSU.

2- The S11 requires 220v , and consumes 1671w on normal mode, but only 1301w in Low power mode , the only possible cause is that your voltage is below 220v, therefore on the low setting, the psu draws less amps and the voltage does not drop low enough to trigger that voltage-protection mode, while on normal mode the miner needs 1671 and the psu simply can't provide that with the given voltage it has.

You can troubleshoot this by turning one of the other miners you have, and use it's power cord on the faulty miner.

[Greekscreamer]

Hallo everyone,

there have been a while since my last post the reason is that my farm is in another town. First of all i want to thank everyone who kindly answered my questions.
All of you are really very helpfull
I wanted to share with you the story of what happened with this S11, and if someone else has a similar problem might receive help as well.

When i finally managed to go to the mining farm which is located in another town, i did a couple of testings.
fist of all i measured the Voltage while the machine was working and it was 220V to the PSU so that's ok. i Switched with another PSU didn't work either. then i realised that ONLY when the machine was working at normal mode and not low, a hash board were showing a weird number in the field "GH/S (Ideal)". Instead of approximately 7000GH, it was showing 50000+ GH, but in low power there was no problem at all. This issue caused an instabillity in the whole system and as a result it was restarting endlessly.

I took a board from another miner and problem fixed. I tried this faulty board in another miner, problem was there too. At the end, i collected this board with some other malfunctioning boards from some T15 i have and sending to BITMAIN for repair.

@bitmaxz, the first days i were testing with low power but didn;t work either, only after some days low power worked! Regarding Temps and ventilation i think i did good job, i haven't had any issues with 38 degrees environmental temperature (summer is hot here)
@mikeywith, the solutions were logical, maybe there was a problem in power supply that damaged the board. have you heard of something similar?

[mikeywith]

@mikeywith, the solutions were logical, maybe there was a problem in power supply that damaged the board. have you heard of something similar?

It's very unlikely that a PSU would cause damage to one board and not all three boards, after your last update, things became clear to me, you simply had a board with a bad chip (or a few bad chips which don't matter), when a board has a faulty chip sometimes running at lower frequency or even higher voltage brings it to life, so when you switch to lower-power-mode, the PSU feeds the hash board with lower voltage and the control board commands the board to work at a lower frequency, the board is happy and it mines on, however, when such symptoms appear, it means the board is bad and could fail completely at any given second, you might be lucky and get the board to work on LPM for quite some time but your chances are low plus it affects the hash rate of the other chains.

i collected this board with some other malfunctioning boards from some T15 i have and sending to BITMAIN for repair.

Bitmain no longer supports their S11, so they won't fix it, you will only lose money paying for shipping, plus it's not worth it anyway, what I would do is get a trusted custom firmware that would give you control over voltage and frequency of each chain, set that bad board at very low frequency and let it mine until it dies, it's really not worth fixing the 7th board at these prices, at worst case scenario get rid of that board and call it bad luck, plus you should get used to that, I have yet to hear from someone who uses Bitmain gears and doesn't have a few hashboards sitting in the garage doing nothing.

[BitMaxz]

Any reason why you need the hex file for s11?

You can get the hex file from other hashboard instead in your s11 miner since it has 3 hashboard one or two should be still has working hex file. Why not backup it first then flash it to other not working hashbord?

Try to contact the man from this guide https://bitcointalk.org/index.php?topic=5032987. He might have a backup copy of working hex for s11.