S17 Pro no longer hashing. Bad ASICs ? - page 3.

mikeywith

legendary

Activity: 2394

Merit: 6581

be constructive or S.T.F.U

Quote from: BitMaxz on August 23, 2020, 06:24:13 PM

The only problem you will need to contact Bitmain to get the SD card image.

There is no need for that, you can use the link from asic.to which is here > https://mega.nz/folder/Wo0wHS4J#9WvygRhcT5Qo5aM-jPSrrg

You will not find S17 pro firmware, but it's the same as the S17/T17 so chose whatever you want, make sure you extract the files to the main directory of your sdcard and not into a sub folder, keep us updated.

BitMaxz

legendary

Activity: 3374

Merit: 3095

Playbet.io - Crypto Casino and Sportsbook

Quote from: agilmore on August 23, 2020, 06:09:52 PM

I'm guessing that I replaced it correctly. Power is on, the little fans are on. There are only 2 cables that plug into the PSU. I haven't attempted to flash the miner. Can you point me to the instructions ?

You can follow the instruction from Bitmain here "S17/S17Pro/S9 SE/S9k/Z11 control board program recovery (SD card flashing with customized PW)"

The only problem you will need to contact Bitmain to get the SD card image.

I just can't remember the thread that someone shares the mp test firmware image for s17 here on the forum. I'm going to find it and I'll update this post soon.

agilmore

jr. member

Activity: 40

Merit: 13

I'm guessing that I replaced it correctly. Power is on, the little fans are on. There are only 2 cables that plug into the PSU. I haven't attempted to flash the miner. Can you point me to the instructions ?

mikeywith

legendary

Activity: 2394

Merit: 6581

be constructive or S.T.F.U

That is very strange, the kernel log is almost identical to the first one, have you flashed the miner using an Sdcard prior to or after the replacement of the PSU? also, are you sure you have installed the PSU correctly? also, have you tried custom firmware?

The kernel log now suggest that all 3 boards are dead, it's possible but it's really a very small probability, obviously, you could be that unlucky and all 3 dashboards went down at the same time, but I still find it hard to believe so, so let's troubleshoot this even further.

Start with Sdcard flash, do not upgrade to the latest firmware, flash Vnish firmware from AwesomeMiner or Asic.to.

agilmore

jr. member

Activity: 40

Merit: 13

I've replaced the PSU and still don't see any improvement. Here's the kernel log:

Code:

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: 190356K/245760K available (6345K kernel code, 231K rwdata, 1896K rodata, 1024K init, 223K bss, 39020K reserved, 16384K cma-reserved, 0K highmem)
Virtual kernel memory layout:
    vector  : 0xffff0000 - 0xffff1000   (   4 kB)
    fixmap  : 0xffc00000 - 0xfff00000   (3072 kB)
    vmalloc : 0xcf800000 - 0xff800000   ( 768 MB)
    lowmem  : 0xc0000000 - 0xcf000000   ( 240 MB)
    pkmap   : 0xbfe00000 - 0xc0000000   (   2 MB)
    modules : 0xbf000000 - 0xbfe00000   (  14 MB)
      .text : 0xc0008000 - 0xc090c424   (9234 kB)
      .init : 0xc0a00000 - 0xc0b00000   (1024 kB)
      .data : 0xc0b00000 - 0xc0b39fe0   ( 232 kB)
       .bss : 0xc0b39fe0 - 0xc0b71c28   ( 224 kB)
Preemptible hierarchical RCU implementation.
	Build-time adjustment of leaf fanout to 32.
	RCU restricting CPUs from NR_CPUS=4 to nr_cpu_ids=2.
RCU: Adjusting geometry for rcu_fanout_leaf=32, nr_cpu_ids=2
NR_IRQS:16 nr_irqs:16 16
efuse mapped to cf800000
ps7-slcr mapped to cf802000
L2C: platform modifies aux control register: 0x72360000 -> 0x72760000
L2C: DT/platform modifies aux control register: 0x72360000 -> 0x72760000
L2C-310 erratum 769419 enabled
L2C-310 enabling early BRESP for Cortex-A9
L2C-310 full line of zeros enabled for Cortex-A9
L2C-310 ID prefetch enabled, offset 1 lines
L2C-310 dynamic clock gating enabled, standby mode enabled
L2C-310 cache controller enabled, 8 ways, 512 kB
L2C-310: CACHE_ID 0x410000c8, AUX_CTRL 0x76760001
zynq_clock_init: clkc starts at cf802100
Zynq clock init
sched_clock: 64 bits at 333MHz, resolution 3ns, wraps every 4398046511103ns
clocksource: arm_global_timer: mask: 0xffffffffffffffff max_cycles: 0x4ce07af025, max_idle_ns: 440795209040 ns
Switching to timer-based delay loop, resolution 3ns
clocksource: ttc_clocksource: mask: 0xffff max_cycles: 0xffff, max_idle_ns: 537538477 ns
ps7-ttc #0 at cf80a000, irq=18
Console: colour dummy device 80x30
Calibrating delay loop (skipped), value calculated using timer frequency.. 666.66 BogoMIPS (lpj=3333333)
pid_max: default: 32768 minimum: 301
Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
CPU: Testing write buffer coherency: ok
CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
Setting up static identity map for 0x100000 - 0x100058
CPU1: failed to boot: -1
Brought up 1 CPUs
SMP: Total of 1 processors activated (666.66 BogoMIPS).
CPU: All CPU(s) started in SVC mode.
devtmpfs: initialized
VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4
clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
pinctrl core: initialized pinctrl subsystem
NET: Registered protocol family 16
DMA: preallocated 256 KiB pool for atomic coherent allocations
cpuidle: using governor menu
hw-breakpoint: found 5 (+1 reserved) breakpoint and 1 watchpoint registers.
hw-breakpoint: maximum watchpoint size is 4 bytes.
zynq-ocm f800c000.ps7-ocmc: ZYNQ OCM pool: 256 KiB @ 0xcf880000
vgaarb: loaded
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
media: Linux media interface: v0.10
Linux video capture interface: v2.00
pps_core: LinuxPPS API ver. 1 registered
pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti 
PTP clock support registered
EDAC MC: Ver: 3.0.0
Advanced Linux Sound Architecture Driver Initialized.
clocksource: Switched to clocksource arm_global_timer
NET: Registered protocol family 2
TCP established hash table entries: 2048 (order: 1, 8192 bytes)
TCP bind hash table entries: 2048 (order: 2, 16384 bytes)
TCP: Hash tables configured (established 2048 bind 2048)
UDP hash table entries: 256 (order: 1, 8192 bytes)
UDP-Lite hash table entries: 256 (order: 1, 8192 bytes)
NET: Registered protocol family 1
RPC: Registered named UNIX socket transport module.
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
PCI: CLS 0 bytes, default 64
Trying to unpack rootfs image as initramfs...
rootfs image is not initramfs (no cpio magic); looks like an initrd
Freeing initrd memory: 25980K (cc1a2000 - cdb01000)
hw perfevents: enabled with armv7_cortex_a9 PMU driver, 7 counters available
futex hash table entries: 512 (order: 3, 32768 bytes)
workingset: timestamp_bits=28 max_order=16 bucket_order=0
jffs2: version 2.2. (NAND) (SUMMARY)  © 2001-2006 Red Hat, Inc.
io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered (default)
dma-pl330 f8003000.ps7-dma: Loaded driver for PL330 DMAC-241330
dma-pl330 f8003000.ps7-dma: 	DBUFF-128x8bytes Num_Chans-8 Num_Peri-4 Num_Events-16
e0000000.serial: ttyPS0 at MMIO 0xe0000000 (irq = 158, base_baud = 6249999) is a xuartps
console [ttyPS0] enabled
xdevcfg f8007000.ps7-dev-cfg: ioremap 0xf8007000 to cf86e000
[drm] Initialized drm 1.1.0 20060810
brd: module loaded
loop: module loaded
CAN device driver interface
gpiod_set_value: invalid GPIO
libphy: MACB_mii_bus: probed
macb e000b000.ethernet eth0: Cadence GEM rev 0x00020118 at 0xe000b000 irq 31 (00:0a:35:00:00:00)
Generic PHY e000b000.etherne:00: attached PHY driver [Generic PHY] (mii_bus:phy_addr=e000b000.etherne:00, irq=-1)
e1000e: Intel(R) PRO/1000 Network Driver - 3.2.6-k
e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
ehci-pci: EHCI PCI platform driver
usbcore: registered new interface driver usb-storage
mousedev: PS/2 mouse device common for all mice
i2c /dev entries driver
Xilinx Zynq CpuIdle Driver started
sdhci: Secure Digital Host Controller Interface driver
sdhci: Copyright(c) Pierre Ossman
sdhci-pltfm: SDHCI platform and OF driver helper
mmc0: SDHCI controller on e0100000.ps7-sdio [e0100000.ps7-sdio] using ADMA
ledtrig-cpu: registered to indicate activity on CPUs
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
nand: device found, Manufacturer ID: 0x2c, Chip ID: 0xda
nand: Micron MT29F2G08ABAGAWP
nand: 256 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 128
nand: WARNING: pl35x-nand: the ECC used on your system is too weak compared to the one required by the NAND chip
Bad block table found at page 131008, version 0x01
Bad block table found at page 130944, version 0x01
6 ofpart partitions found on MTD device pl35x-nand
Creating 6 MTD partitions on "pl35x-nand":
0x000000000000-0x000002800000 : "BOOT.bin-env-dts-kernel"
0x000002800000-0x000004800000 : "ramfs"
0x000004800000-0x000005000000 : "configs"
0x000005000000-0x000006000000 : "reserve"
0x000006000000-0x000008000000 : "ramfs-bak"
0x000008000000-0x000010000000 : "reserve1"
NET: Registered protocol family 10
sit: IPv6 over IPv4 tunneling driver
NET: Registered protocol family 17
can: controller area network core (rev 20120528 abi 9)
NET: Registered protocol family 29
can: raw protocol (rev 20120528)
can: broadcast manager protocol (rev 20120528 t)
can: netlink gateway (rev 20130117) max_hops=1
zynq_pm_ioremap: no compatible node found for 'xlnx,zynq-ddrc-a05'
zynq_pm_late_init: Unable to map DDRC IO memory.
Registering SWP/SWPB emulation handler
hctosys: unable to open rtc device (rtc0)
ALSA device list:
  No soundcards found.
RAMDISK: gzip image found at block 0
EXT4-fs (ram0): couldn't mount as ext3 due to feature incompatibilities
EXT4-fs (ram0): mounted filesystem without journal. Opts: (null)
VFS: Mounted root (ext4 filesystem) on device 1:0.
devtmpfs: mounted
Freeing unused kernel memory: 1024K (c0a00000 - c0b00000)
EXT4-fs (ram0): re-mounted. Opts: block_validity,delalloc,barrier,user_xattr
random: dd urandom read with 0 bits of entropy available
ubi0: attaching mtd2
ubi0: scanning is finished
ubi0: attached mtd2 (name "configs", size 8 MiB)
ubi0: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
ubi0: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
ubi0: VID header offset: 2048 (aligned 2048), data offset: 4096
ubi0: good PEBs: 64, bad PEBs: 0, corrupted PEBs: 0
ubi0: user volume: 1, internal volumes: 1, max. volumes count: 128
ubi0: max/mean erase counter: 5/2, 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): recovery needed
UBIFS (ubi0:0): recovery completed
UBIFS (ubi0:0): UBIFS: mounted UBI device 0, volume 0, name "configs"
UBIFS (ubi0:0): LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
UBIFS (ubi0:0): FS size: 1396736 bytes (1 MiB, 11 LEBs), journal size 888833 bytes (0 MiB, 5 LEBs)
UBIFS (ubi0:0): reserved for root: 65970 bytes (64 KiB)
UBIFS (ubi0:0): media format: w4/r0 (latest is w4/r0), UUID 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: 4353/1931, 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): recovery needed
UBIFS (ubi1:0): recovery completed
UBIFS (ubi1:0): UBIFS: mounted UBI device 1, volume 0, name "reserve1"
UBIFS (ubi1:0): LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
UBIFS (ubi1:0): FS size: 123039744 bytes (117 MiB, 969 LEBs), journal size 6221824 bytes (5 MiB, 49 LEBs)
UBIFS (ubi1:0): reserved for root: 4952683 bytes (4836 KiB)
UBIFS (ubi1:0): media format: w4/r0 (latest is w4/r0), UUID 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 = 0xab011
In fpga mem driver!
request_mem_region OK!
fpga mem virtual address is 0xd2000000
random: nonblocking pool is initialized
Alignment trap: cg@0/RStratum (1958) PC=0x00020c54 Instr=0xedd20b1a Address=0x00000089 FSR 0x001
Alignment trap: not handling instruction edd20b1a at [<00020c54>]
Unhandled fault: alignment exception (0x001) at 0x00000089
pgd = cbf58000
[00000089] *pgd=058f6831, *pte=00000000, *ppte=00000000
Alignment trap: cg@0/RStratum (2424) PC=0x00020c54 Instr=0xedd20b1a Address=0x00000089 FSR 0x001
Alignment trap: not handling instruction edd20b1a at [<00020c54>]
Unhandled fault: alignment exception (0x001) at 0x00000089
pgd = c8d8c000
[00000089] *pgd=03d4a831, *pte=00000000, *ppte=00000000
 [2020-08-23 22:41:08.424] httpListenThread start ret=0
 [2020-08-23 22:41:38.428] start listen on 6060 ...
2020-08-23 22:41:08 driver-btm-soc.c:3160:init_freq_mode: This is scan-user version
2020-08-23 22:41:08 driver-btm-soc.c:3896:bitmain_soc_init: opt_multi_version=1
2020-08-23 22:41:08 driver-btm-soc.c:3897:bitmain_soc_init: opt_bitmain_ab=1
2020-08-23 22:41:08 driver-btm-soc.c:3898:bitmain_soc_init: opt_bitmain_work_mode=1
2020-08-23 22:41:08 driver-btm-soc.c:3521:_show_sn: no SN got, please write SN to /nvdata/sn
2020-08-23 22:41:08 driver-btm-soc.c:3191:init_phy_mem_nonce2_jobid_address: Detect 256MB control board of XILINX
2020-08-23 22:41:08 driver-btm-soc.c:3904:bitmain_soc_init: Miner compile time: Tue Apr 16 19:05:06 CST 2019
2020-08-23 22:41:08 driver-btm-soc.c:3906:bitmain_soc_init: last commit version: 8b856e7 commit time: 2019-04-16 16:36:14 build: 2019-04-16 19:09:46
2020-08-23 22:41:08 driver-btm-soc.c:3223:check_fan_multi: check fan for 20 times...
2020-08-23 22:41:10 driver-btm-soc.c:3299:init_miner_version: miner ID : 813275ce57408854
2020-08-23 22:41:10 driver-btm-soc.c:3305:init_miner_version: FPGA Version = 0xB011
2020-08-23 22:41:10 driver-btm-soc.c:404:check_chain: !! chain[0]is exist
2020-08-23 22:41:10 driver-btm-soc.c:404:check_chain: !! chain[1]is exist
2020-08-23 22:41:10 driver-btm-soc.c:404:check_chain: !! chain[2]is exist
2020-08-23 22:41:14 driver-btm-soc.c:3722:get_product_id: product_id[0] = 0
2020-08-23 22:41:14 driver-btm-soc.c:3722:get_product_id: product_id[1] = 0
2020-08-23 22:41:14 driver-btm-soc.c:3722:get_product_id: product_id[2] = 0
2020-08-23 22:41:14 driver-btm-soc.c:3823:bitmain_board_init: g_product_id = 0
2020-08-23 22:41:14 driver-btm-soc.c:3574:_set_project_type: Project type: Antminer S17 Pro
2020-08-23 22:41:14 driver-btm-soc.c:3321:dump_pcb_bom_version: Chain [0] PCB Version: 0x0101
2020-08-23 22:41:14 driver-btm-soc.c:3322:dump_pcb_bom_version: Chain [0] BOM Version: 0x0103
2020-08-23 22:41:14 driver-btm-soc.c:3321:dump_pcb_bom_version: Chain [1] PCB Version: 0x0101
2020-08-23 22:41:14 driver-btm-soc.c:3322:dump_pcb_bom_version: Chain [1] BOM Version: 0x0103
2020-08-23 22:41:14 driver-btm-soc.c:3321:dump_pcb_bom_version: Chain [2] PCB Version: 0x0101
2020-08-23 22:41:14 driver-btm-soc.c:3322:dump_pcb_bom_version: Chain [2] BOM Version: 0x0103
2020-08-23 22:41:15 pic.c:619:pic_reset: chain[0] ok
2020-08-23 22:41:19 pic.c:898:jump_to_app_from_loader: chain[0] ok
2020-08-23 22:41:20 pic.c:619:pic_reset: chain[1] ok
2020-08-23 22:41:24 pic.c:898:jump_to_app_from_loader: chain[1] ok
2020-08-23 22:41:25 pic.c:619:pic_reset: chain[2] ok
2020-08-23 22:41:29 pic.c:898:jump_to_app_from_loader: chain[2] ok
2020-08-23 22:41:29 driver-btm-soc.c:3840:bitmain_board_init: Enter 30s sleep to make sure power release finish.
2020-08-23 22:41:29 driver-btm-soc.c:1156:heart_beat_func_one_chain: for chain 2
2020-08-23 22:41:29 driver-btm-soc.c:1156:heart_beat_func_one_chain: for chain 1
2020-08-23 22:41:29 driver-btm-soc.c:1156:heart_beat_func_one_chain: for chain 0
2020-08-23 22:41:59 power.c:216:power_init: power init ... 
2020-08-23 22:42:01 power.c:348:power_get_firmware_version: power firmware version is 00 07
2020-08-23 22:42:02 power.c:338:power_get_device_no: power device no is 00 41
2020-08-23 22:42:02 power.c:203:power_check_protocol_type: power protocol f5, using package cmd
2020-08-23 22:42:02 power.c:204:power_check_protocol_type: power type APW9 3600W
2020-08-23 22:42:03 power.c:624:set_iic_power_to_highest_voltage: setting to voltage: 21.00 ...
2020-08-23 22:42:06 power.c:573:set_iic_power_by_voltage: now setting voltage to : 21.000000 
2020-08-23 22:42:06 zynq.c:192:set_reset_hashboard: set_reset_hashboard = 0x0000fff9
2020-08-23 22:42:10 pic.c:234:hashboard_power_cntl: [1] ok, i2c=0!
2020-08-23 22:42:12 zynq.c:192:set_reset_hashboard: set_reset_hashboard = 0x0000fff8
2020-08-23 22:42:16 driver-btm-soc.c:3657:check_asic_number_with_power_on: Chain[0]: find 0 asic, times 0
2020-08-23 22:42:16 zynq.c:192:set_reset_hashboard: set_reset_hashboard = 0x0000fff9
2020-08-23 22:42:19 pic.c:234:hashboard_power_cntl: [1] ok, i2c=0!
2020-08-23 22:42:21 zynq.c:192:set_reset_hashboard: set_reset_hashboard = 0x0000fff8
2020-08-23 22:42:26 driver-btm-soc.c:3657:check_asic_number_with_power_on: Chain[0]: find 0 asic, times 1
2020-08-23 22:42:26 zynq.c:192:set_reset_hashboard: set_reset_hashboard = 0x0000fff9
2020-08-23 22:42:29 pic.c:234:hashboard_power_cntl: [1] ok, i2c=0!
2020-08-23 22:42:31 zynq.c:192:set_reset_hashboard: set_reset_hashboard = 0x0000fff8
2020-08-23 22:42:35 driver-btm-soc.c:3657:check_asic_number_with_power_on: Chain[0]: find 0 asic, times 2
2020-08-23 22:42:35 driver-btm-soc.c:3682:check_asic_number: Chain 0 only find 0 asic, will power off hash board 0
2020-08-23 22:42:36 pic.c:234:hashboard_power_cntl: [0] ok, i2c=0!
2020-08-23 22:42:36 zynq.c:192:set_reset_hashboard: set_reset_hashboard = 0x0000fffa
2020-08-23 22:42:40 pic.c:234:hashboard_power_cntl: [1] ok, i2c=1!
2020-08-23 22:42:42 zynq.c:192:set_reset_hashboard: set_reset_hashboard = 0x0000fff8
2020-08-23 22:42:46 driver-btm-soc.c:3657:check_asic_number_with_power_on: Chain[1]: find 0 asic, times 0
2020-08-23 22:42:46 zynq.c:192:set_reset_hashboard: set_reset_hashboard = 0x0000fffa
2020-08-23 22:42:50 pic.c:234:hashboard_power_cntl: [1] ok, i2c=1!
2020-08-23 22:42:52 zynq.c:192:set_reset_hashboard: set_reset_hashboard = 0x0000fff8
2020-08-23 22:42:56 driver-btm-soc.c:3657:check_asic_number_with_power_on: Chain[1]: find 0 asic, times 1
2020-08-23 22:42:56 zynq.c:192:set_reset_hashboard: set_reset_hashboard = 0x0000fffa
2020-08-23 22:42:59 pic.c:234:hashboard_power_cntl: [1] ok, i2c=1!
2020-08-23 22:43:01 zynq.c:192:set_reset_hashboard: set_reset_hashboard = 0x0000fff8
2020-08-23 22:43:06 driver-btm-soc.c:3657:check_asic_number_with_power_on: Chain[1]: find 0 asic, times 2
2020-08-23 22:43:06 driver-btm-soc.c:3682:check_asic_number: Chain 1 only find 0 asic, will power off hash board 1
2020-08-23 22:43:06 pic.c:234:hashboard_power_cntl: [0] ok, i2c=1!
2020-08-23 22:43:06 zynq.c:192:set_reset_hashboard: set_reset_hashboard = 0x0000fffc
2020-08-23 22:43:10 pic.c:234:hashboard_power_cntl: [1] ok, i2c=2!
2020-08-23 22:43:12 zynq.c:192:set_reset_hashboard: set_reset_hashboard = 0x0000fff8
2020-08-23 22:43:16 driver-btm-soc.c:3657:check_asic_number_with_power_on: Chain[2]: find 0 asic, times 0
2020-08-23 22:43:16 zynq.c:192:set_reset_hashboard: set_reset_hashboard = 0x0000fffc
2020-08-23 22:43:19 pic.c:234:hashboard_power_cntl: [1] ok, i2c=2!
2020-08-23 22:43:21 zynq.c:192:set_reset_hashboard: set_reset_hashboard = 0x0000fff8
2020-08-23 22:43:26 driver-btm-soc.c:3657:check_asic_number_with_power_on: Chain[2]: find 0 asic, times 1
2020-08-23 22:43:26 zynq.c:192:set_reset_hashboard: set_reset_hashboard = 0x0000fffc
2020-08-23 22:43:29 pic.c:234:hashboard_power_cntl: [1] ok, i2c=2!
2020-08-23 22:43:31 zynq.c:192:set_reset_hashboard: set_reset_hashboard = 0x0000fff8
2020-08-23 22:43:36 driver-btm-soc.c:3657:check_asic_number_with_power_on: Chain[2]: find 0 asic, times 2
2020-08-23 22:43:36 driver-btm-soc.c:3682:check_asic_number: Chain 2 only find 0 asic, will power off hash board 2
2020-08-23 22:43:36 pic.c:234:hashboard_power_cntl: [0] ok, i2c=2!
2020-08-23 22:43:36 util.c:2178:process_version_mask: Pool 0 Verion num is 4
2020-08-23 22:43:36 util.c:2178:process_version_mask: Pool 0 Verion num is 4
2020-08-23 22:43:39 driver-btm-soc.c:4183:send_job: Version num 4
total rate = 0
total rate = 0
total rate = 0
total rate = 0

Screenshots: https://imgur.com/a/XoC9bhT

mikeywith

legendary

Activity: 2394

Merit: 6581

be constructive or S.T.F.U

Nothing has changed sadly.

Code:

driver-btm-soc.c:3657:check_asic_number_with_power_on: Chain[0]: find 0 asic, times 0

Code:

driver-btm-soc.c:3657:check_asic_number_with_power_on: Chain[1]: find 0 asic, times 1

Code:

driver-btm-soc.c:3657:check_asic_number_with_power_on: Chain[2]: find 0 asic, times 0

Code:

total rate = 0

I am now 99% sure you need to replace the PSU, do you have another S17 pro? or even S17 / T17 since these 3 use the same PSU, one last thing I would try before getting a new PSU is to Sdcard flash the control board and flash a custom firmware for testing, if that doesn't solve the problem then nothing left to do but to get a PSU for about $100.

agilmore

jr. member

Activity: 40

Merit: 13

I've cleaned it and let it run in Low Power Mode. Neither the Fault or Normal lights are on. Any suggestions? Do I need to replace the PSU? It's a S17 Pro 50T and out of warranty.

Kernel Log:

Code:

Booting Linux on physical CPU 0x0
Linux version 4.6.0-xilinx-gff8137b-dirty (lzq@armdev2) (gcc version 4.8.3 20140320 (prerelease) (Sourcery CodeBench Lite 2014.05-23) ) #25 SMP PREEMPT Fri Nov 23 15:30:52 CST 2018
CPU: ARMv7 Processor [413fc090] revision 0 (ARMv7), cr=18c5387d
CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
Machine model: Xilinx Zynq
cma: Reserved 16 MiB at 0x0e000000
Memory policy: Data cache writealloc
On node 0 totalpages: 61440
free_area_init_node: node 0, pgdat c0b39280, node_mem_map cde10000
  Normal zone: 480 pages used for memmap
  Normal zone: 0 pages reserved
  Normal zone: 61440 pages, LIFO batch:15
percpu: Embedded 12 pages/cpu @cddf1000 s19776 r8192 d21184 u49152
pcpu-alloc: s19776 r8192 d21184 u49152 alloc=12*4096
pcpu-alloc: [0] 0 [0] 1 
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 60960
Kernel command line: mem=240M console=ttyPS0,115200 ramdisk_size=33554432 root=/dev/ram rw earlyprintk
PID hash table entries: 1024 (order: 0, 4096 bytes)
Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
Memory: 190356K/245760K available (6345K kernel code, 231K rwdata, 1896K rodata, 1024K init, 223K bss, 39020K reserved, 16384K cma-reserved, 0K highmem)
Virtual kernel memory layout:
    vector  : 0xffff0000 - 0xffff1000   (   4 kB)
    fixmap  : 0xffc00000 - 0xfff00000   (3072 kB)
    vmalloc : 0xcf800000 - 0xff800000   ( 768 MB)
    lowmem  : 0xc0000000 - 0xcf000000   ( 240 MB)
    pkmap   : 0xbfe00000 - 0xc0000000   (   2 MB)
    modules : 0xbf000000 - 0xbfe00000   (  14 MB)
      .text : 0xc0008000 - 0xc090c424   (9234 kB)
      .init : 0xc0a00000 - 0xc0b00000   (1024 kB)
      .data : 0xc0b00000 - 0xc0b39fe0   ( 232 kB)
       .bss : 0xc0b39fe0 - 0xc0b71c28   ( 224 kB)
Preemptible hierarchical RCU implementation.
	Build-time adjustment of leaf fanout to 32.
	RCU restricting CPUs from NR_CPUS=4 to nr_cpu_ids=2.
RCU: Adjusting geometry for rcu_fanout_leaf=32, nr_cpu_ids=2
NR_IRQS:16 nr_irqs:16 16
efuse mapped to cf800000
ps7-slcr mapped to cf802000
L2C: platform modifies aux control register: 0x72360000 -> 0x72760000
L2C: DT/platform modifies aux control register: 0x72360000 -> 0x72760000
L2C-310 erratum 769419 enabled
L2C-310 enabling early BRESP for Cortex-A9
L2C-310 full line of zeros enabled for Cortex-A9
L2C-310 ID prefetch enabled, offset 1 lines
L2C-310 dynamic clock gating enabled, standby mode enabled
L2C-310 cache controller enabled, 8 ways, 512 kB
L2C-310: CACHE_ID 0x410000c8, AUX_CTRL 0x76760001
zynq_clock_init: clkc starts at cf802100
Zynq clock init
sched_clock: 64 bits at 333MHz, resolution 3ns, wraps every 4398046511103ns
clocksource: arm_global_timer: mask: 0xffffffffffffffff max_cycles: 0x4ce07af025, max_idle_ns: 440795209040 ns
Switching to timer-based delay loop, resolution 3ns
clocksource: ttc_clocksource: mask: 0xffff max_cycles: 0xffff, max_idle_ns: 537538477 ns
ps7-ttc #0 at cf80a000, irq=18
Console: colour dummy device 80x30
Calibrating delay loop (skipped), value calculated using timer frequency.. 666.66 BogoMIPS (lpj=3333333)
pid_max: default: 32768 minimum: 301
Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
CPU: Testing write buffer coherency: ok
CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
Setting up static identity map for 0x100000 - 0x100058
CPU1: failed to boot: -1
Brought up 1 CPUs
SMP: Total of 1 processors activated (666.66 BogoMIPS).
CPU: All CPU(s) started in SVC mode.
devtmpfs: initialized
VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4
clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
pinctrl core: initialized pinctrl subsystem
NET: Registered protocol family 16
DMA: preallocated 256 KiB pool for atomic coherent allocations
cpuidle: using governor menu
hw-breakpoint: found 5 (+1 reserved) breakpoint and 1 watchpoint registers.
hw-breakpoint: maximum watchpoint size is 4 bytes.
zynq-ocm f800c000.ps7-ocmc: ZYNQ OCM pool: 256 KiB @ 0xcf880000
vgaarb: loaded
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
media: Linux media interface: v0.10
Linux video capture interface: v2.00
pps_core: LinuxPPS API ver. 1 registered
pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti 
PTP clock support registered
EDAC MC: Ver: 3.0.0
Advanced Linux Sound Architecture Driver Initialized.
clocksource: Switched to clocksource arm_global_timer
NET: Registered protocol family 2
TCP established hash table entries: 2048 (order: 1, 8192 bytes)
TCP bind hash table entries: 2048 (order: 2, 16384 bytes)
TCP: Hash tables configured (established 2048 bind 2048)
UDP hash table entries: 256 (order: 1, 8192 bytes)
UDP-Lite hash table entries: 256 (order: 1, 8192 bytes)
NET: Registered protocol family 1
RPC: Registered named UNIX socket transport module.
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
PCI: CLS 0 bytes, default 64
Trying to unpack rootfs image as initramfs...
rootfs image is not initramfs (no cpio magic); looks like an initrd
Freeing initrd memory: 25980K (cc1a2000 - cdb01000)
hw perfevents: enabled with armv7_cortex_a9 PMU driver, 7 counters available
futex hash table entries: 512 (order: 3, 32768 bytes)
workingset: timestamp_bits=28 max_order=16 bucket_order=0
jffs2: version 2.2. (NAND) (SUMMARY)  © 2001-2006 Red Hat, Inc.
io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered (default)
dma-pl330 f8003000.ps7-dma: Loaded driver for PL330 DMAC-241330
dma-pl330 f8003000.ps7-dma: 	DBUFF-128x8bytes Num_Chans-8 Num_Peri-4 Num_Events-16
e0000000.serial: ttyPS0 at MMIO 0xe0000000 (irq = 158, base_baud = 6249999) is a xuartps
console [ttyPS0] enabled
xdevcfg f8007000.ps7-dev-cfg: ioremap 0xf8007000 to cf86e000
[drm] Initialized drm 1.1.0 20060810
brd: module loaded
loop: module loaded
CAN device driver interface
gpiod_set_value: invalid GPIO
libphy: MACB_mii_bus: probed
macb e000b000.ethernet eth0: Cadence GEM rev 0x00020118 at 0xe000b000 irq 31 (00:0a:35:00:00:00)
Generic PHY e000b000.etherne:00: attached PHY driver [Generic PHY] (mii_bus:phy_addr=e000b000.etherne:00, irq=-1)
e1000e: Intel(R) PRO/1000 Network Driver - 3.2.6-k
e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
ehci-pci: EHCI PCI platform driver
usbcore: registered new interface driver usb-storage
mousedev: PS/2 mouse device common for all mice
i2c /dev entries driver
Xilinx Zynq CpuIdle Driver started
sdhci: Secure Digital Host Controller Interface driver
sdhci: Copyright(c) Pierre Ossman
sdhci-pltfm: SDHCI platform and OF driver helper
mmc0: SDHCI controller on e0100000.ps7-sdio [e0100000.ps7-sdio] using ADMA
ledtrig-cpu: registered to indicate activity on CPUs
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
nand: device found, Manufacturer ID: 0x2c, Chip ID: 0xda
nand: Micron MT29F2G08ABAGAWP
nand: 256 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 128
nand: WARNING: pl35x-nand: the ECC used on your system is too weak compared to the one required by the NAND chip
Bad block table found at page 131008, version 0x01
Bad block table found at page 130944, version 0x01
6 ofpart partitions found on MTD device pl35x-nand
Creating 6 MTD partitions on "pl35x-nand":
0x000000000000-0x000002800000 : "BOOT.bin-env-dts-kernel"
0x000002800000-0x000004800000 : "ramfs"
0x000004800000-0x000005000000 : "configs"
0x000005000000-0x000006000000 : "reserve"
0x000006000000-0x000008000000 : "ramfs-bak"
0x000008000000-0x000010000000 : "reserve1"
NET: Registered protocol family 10
sit: IPv6 over IPv4 tunneling driver
NET: Registered protocol family 17
can: controller area network core (rev 20120528 abi 9)
NET: Registered protocol family 29
can: raw protocol (rev 20120528)
can: broadcast manager protocol (rev 20120528 t)
can: netlink gateway (rev 20130117) max_hops=1
zynq_pm_ioremap: no compatible node found for 'xlnx,zynq-ddrc-a05'
zynq_pm_late_init: Unable to map DDRC IO memory.
Registering SWP/SWPB emulation handler
hctosys: unable to open rtc device (rtc0)
ALSA device list:
  No soundcards found.
RAMDISK: gzip image found at block 0
EXT4-fs (ram0): couldn't mount as ext3 due to feature incompatibilities
EXT4-fs (ram0): mounted filesystem without journal. Opts: (null)
VFS: Mounted root (ext4 filesystem) on device 1:0.
devtmpfs: mounted
Freeing unused kernel memory: 1024K (c0a00000 - c0b00000)
EXT4-fs (ram0): re-mounted. Opts: block_validity,delalloc,barrier,user_xattr
random: dd urandom read with 0 bits of entropy available
ubi0: attaching mtd2
ubi0: scanning is finished
ubi0: attached mtd2 (name "configs", size 8 MiB)
ubi0: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
ubi0: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
ubi0: VID header offset: 2048 (aligned 2048), data offset: 4096
ubi0: good PEBs: 64, bad PEBs: 0, corrupted PEBs: 0
ubi0: user volume: 1, internal volumes: 1, max. volumes count: 128
ubi0: max/mean erase counter: 5/2, 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): recovery needed
UBIFS (ubi0:0): recovery completed
UBIFS (ubi0:0): UBIFS: mounted UBI device 0, volume 0, name "configs"
UBIFS (ubi0:0): LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
UBIFS (ubi0:0): FS size: 1396736 bytes (1 MiB, 11 LEBs), journal size 888833 bytes (0 MiB, 5 LEBs)
UBIFS (ubi0:0): reserved for root: 65970 bytes (64 KiB)
UBIFS (ubi0:0): media format: w4/r0 (latest is w4/r0), UUID 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: 4353/1931, 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): recovery needed
UBIFS (ubi1:0): recovery completed
UBIFS (ubi1:0): UBIFS: mounted UBI device 1, volume 0, name "reserve1"
UBIFS (ubi1:0): LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
UBIFS (ubi1:0): FS size: 123039744 bytes (117 MiB, 969 LEBs), journal size 6221824 bytes (5 MiB, 49 LEBs)
UBIFS (ubi1:0): reserved for root: 4952683 bytes (4836 KiB)
UBIFS (ubi1:0): media format: w4/r0 (latest is w4/r0), UUID 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 = 0xab011
In fpga mem driver!
request_mem_region OK!
fpga mem virtual address is 0xd2000000
random: nonblocking pool is initialized
 [2020-08-09 22:41:50.942] httpListenThread start ret=0
 [2020-08-09 22:42:20.951] start listen on 6060 ...
2020-08-09 22:41:51 driver-btm-soc.c:3160:init_freq_mode: This is scan-user version
2020-08-09 22:41:51 driver-btm-soc.c:3896:bitmain_soc_init: opt_multi_version=1
2020-08-09 22:41:51 driver-btm-soc.c:3897:bitmain_soc_init: opt_bitmain_ab=1
2020-08-09 22:41:51 driver-btm-soc.c:3898:bitmain_soc_init: opt_bitmain_work_mode=0
2020-08-09 22:41:51 driver-btm-soc.c:3521:_show_sn: no SN got, please write SN to /nvdata/sn
2020-08-09 22:41:51 driver-btm-soc.c:3191:init_phy_mem_nonce2_jobid_address: Detect 256MB control board of XILINX
2020-08-09 22:41:51 driver-btm-soc.c:3904:bitmain_soc_init: Miner compile time: Tue Apr 16 19:05:06 CST 2019
2020-08-09 22:41:51 driver-btm-soc.c:3906:bitmain_soc_init: last commit version: 8b856e7 commit time: 2019-04-16 16:36:14 build: 2019-04-16 19:09:46
2020-08-09 22:41:51 driver-btm-soc.c:3223:check_fan_multi: check fan for 20 times...
2020-08-09 22:41:53 driver-btm-soc.c:3299:init_miner_version: miner ID : 813275ce57408854
2020-08-09 22:41:53 driver-btm-soc.c:3305:init_miner_version: FPGA Version = 0xB011
2020-08-09 22:41:53 driver-btm-soc.c:404:check_chain: !! chain[0]is exist
2020-08-09 22:41:53 driver-btm-soc.c:404:check_chain: !! chain[1]is exist
2020-08-09 22:41:53 driver-btm-soc.c:404:check_chain: !! chain[2]is exist
2020-08-09 22:41:57 driver-btm-soc.c:3722:get_product_id: product_id[0] = 0
2020-08-09 22:41:57 driver-btm-soc.c:3722:get_product_id: product_id[1] = 0
2020-08-09 22:41:57 driver-btm-soc.c:3722:get_product_id: product_id[2] = 0
2020-08-09 22:41:57 driver-btm-soc.c:3823:bitmain_board_init: g_product_id = 0
2020-08-09 22:41:57 driver-btm-soc.c:3574:_set_project_type: Project type: Antminer S17 Pro
2020-08-09 22:41:57 driver-btm-soc.c:3321:dump_pcb_bom_version: Chain [0] PCB Version: 0x0101
2020-08-09 22:41:57 driver-btm-soc.c:3322:dump_pcb_bom_version: Chain [0] BOM Version: 0x0103
2020-08-09 22:41:57 driver-btm-soc.c:3321:dump_pcb_bom_version: Chain [1] PCB Version: 0x0101
2020-08-09 22:41:57 driver-btm-soc.c:3322:dump_pcb_bom_version: Chain [1] BOM Version: 0x0103
2020-08-09 22:41:57 driver-btm-soc.c:3321:dump_pcb_bom_version: Chain [2] PCB Version: 0x0101
2020-08-09 22:41:57 driver-btm-soc.c:3322:dump_pcb_bom_version: Chain [2] BOM Version: 0x0103
2020-08-09 22:41:57 pic.c:619:pic_reset: chain[0] ok
2020-08-09 22:42:02 pic.c:898:jump_to_app_from_loader: chain[0] ok
2020-08-09 22:42:02 pic.c:619:pic_reset: chain[1] ok
2020-08-09 22:42:07 pic.c:898:jump_to_app_from_loader: chain[1] ok
2020-08-09 22:42:07 pic.c:619:pic_reset: chain[2] ok
2020-08-09 22:42:12 pic.c:898:jump_to_app_from_loader: chain[2] ok
2020-08-09 22:42:12 driver-btm-soc.c:3840:bitmain_board_init: Enter 30s sleep to make sure power release finish.
2020-08-09 22:42:12 driver-btm-soc.c:1156:heart_beat_func_one_chain: for chain 2
2020-08-09 22:42:12 driver-btm-soc.c:1156:heart_beat_func_one_chain: for chain 1
2020-08-09 22:42:12 driver-btm-soc.c:1156:heart_beat_func_one_chain: for chain 0
2020-08-09 22:42:42 power.c:216:power_init: power init ... 
2020-08-09 22:42:43 power.c:348:power_get_firmware_version: power firmware version is 00 07
2020-08-09 22:42:45 power.c:338:power_get_device_no: power device no is 00 41
2020-08-09 22:42:45 power.c:203:power_check_protocol_type: power protocol f5, using package cmd
2020-08-09 22:42:45 power.c:204:power_check_protocol_type: power type APW9 3600W
2020-08-09 22:42:45 power.c:155:power_on: init gpio907
2020-08-09 22:42:46 power.c:624:set_iic_power_to_highest_voltage: setting to voltage: 21.00 ...
2020-08-09 22:42:48 power.c:573:set_iic_power_by_voltage: now setting voltage to : 21.000000 
2020-08-09 22:42:49 zynq.c:192:set_reset_hashboard: set_reset_hashboard = 0x0000ffff
2020-08-09 22:42:52 pic.c:234:hashboard_power_cntl: [1] ok, i2c=0!
2020-08-09 22:42:54 zynq.c:192:set_reset_hashboard: set_reset_hashboard = 0x0000fffe
2020-08-09 22:42:58 driver-btm-soc.c:3657:check_asic_number_with_power_on: Chain[0]: find 0 asic, times 0
2020-08-09 22:42:58 zynq.c:192:set_reset_hashboard: set_reset_hashboard = 0x0000ffff
2020-08-09 22:43:02 pic.c:234:hashboard_power_cntl: [1] ok, i2c=0!
2020-08-09 22:43:04 zynq.c:192:set_reset_hashboard: set_reset_hashboard = 0x0000fffe
2020-08-09 22:43:08 driver-btm-soc.c:3657:check_asic_number_with_power_on: Chain[0]: find 0 asic, times 1
2020-08-09 22:43:08 zynq.c:192:set_reset_hashboard: set_reset_hashboard = 0x0000ffff
2020-08-09 22:43:12 pic.c:234:hashboard_power_cntl: [1] ok, i2c=0!
2020-08-09 22:43:14 zynq.c:192:set_reset_hashboard: set_reset_hashboard = 0x0000fffe
2020-08-09 22:43:18 driver-btm-soc.c:3657:check_asic_number_with_power_on: Chain[0]: find 0 asic, times 2
2020-08-09 22:43:18 driver-btm-soc.c:3682:check_asic_number: Chain 0 only find 0 asic, will power off hash board 0
2020-08-09 22:43:19 pic.c:234:hashboard_power_cntl: [0] ok, i2c=0!
2020-08-09 22:43:19 zynq.c:192:set_reset_hashboard: set_reset_hashboard = 0x0000fffe
2020-08-09 22:43:22 pic.c:234:hashboard_power_cntl: [1] ok, i2c=1!
2020-08-09 22:43:24 zynq.c:192:set_reset_hashboard: set_reset_hashboard = 0x0000fffc
2020-08-09 22:43:29 driver-btm-soc.c:3657:check_asic_number_with_power_on: Chain[1]: find 0 asic, times 0
2020-08-09 22:43:29 zynq.c:192:set_reset_hashboard: set_reset_hashboard = 0x0000fffe
2020-08-09 22:43:32 pic.c:234:hashboard_power_cntl: [1] ok, i2c=1!
2020-08-09 22:43:34 zynq.c:192:set_reset_hashboard: set_reset_hashboard = 0x0000fffc
2020-08-09 22:43:38 driver-btm-soc.c:3657:check_asic_number_with_power_on: Chain[1]: find 0 asic, times 1
2020-08-09 22:43:38 zynq.c:192:set_reset_hashboard: set_reset_hashboard = 0x0000fffe
2020-08-09 22:43:42 pic.c:234:hashboard_power_cntl: [1] ok, i2c=1!
2020-08-09 22:43:44 zynq.c:192:set_reset_hashboard: set_reset_hashboard = 0x0000fffc
2020-08-09 22:43:48 driver-btm-soc.c:3657:check_asic_number_with_power_on: Chain[1]: find 0 asic, times 2
2020-08-09 22:43:48 driver-btm-soc.c:3682:check_asic_number: Chain 1 only find 0 asic, will power off hash board 1
2020-08-09 22:43:49 pic.c:234:hashboard_power_cntl: [0] ok, i2c=1!
2020-08-09 22:43:49 zynq.c:192:set_reset_hashboard: set_reset_hashboard = 0x0000fffc
2020-08-09 22:43:52 pic.c:234:hashboard_power_cntl: [1] ok, i2c=2!
2020-08-09 22:43:54 zynq.c:192:set_reset_hashboard: set_reset_hashboard = 0x0000fff8
2020-08-09 22:43:58 driver-btm-soc.c:3657:check_asic_number_with_power_on: Chain[2]: find 0 asic, times 0
2020-08-09 22:43:58 zynq.c:192:set_reset_hashboard: set_reset_hashboard = 0x0000fffc
2020-08-09 22:44:02 pic.c:234:hashboard_power_cntl: [1] ok, i2c=2!
2020-08-09 22:44:04 zynq.c:192:set_reset_hashboard: set_reset_hashboard = 0x0000fff8
2020-08-09 22:44:08 driver-btm-soc.c:3657:check_asic_number_with_power_on: Chain[2]: find 0 asic, times 1
2020-08-09 22:44:08 zynq.c:192:set_reset_hashboard: set_reset_hashboard = 0x0000fffc
2020-08-09 22:44:12 pic.c:234:hashboard_power_cntl: [1] ok, i2c=2!
2020-08-09 22:44:14 zynq.c:192:set_reset_hashboard: set_reset_hashboard = 0x0000fff8
2020-08-09 22:44:18 driver-btm-soc.c:3657:check_asic_number_with_power_on: Chain[2]: find 0 asic, times 2
2020-08-09 22:44:18 driver-btm-soc.c:3682:check_asic_number: Chain 2 only find 0 asic, will power off hash board 2
2020-08-09 22:44:19 pic.c:234:hashboard_power_cntl: [0] ok, i2c=2!
2020-08-09 22:44:19 util.c:2178:process_version_mask: Pool 1 Verion num is 4
2020-08-09 22:44:19 util.c:2178:process_version_mask: Pool 0 Verion num is 4
2020-08-09 22:44:19 util.c:2178:process_version_mask: Pool 0 Verion num is 4
total rate = 0
total rate = 0
total rate = 0
total rate = 0
total rate = 0
total rate = 0
total rate = 0

favebook

sr. member

Activity: 604

Merit: 416

Exactly the same thing happened to me. Ran on Normal/Turbo for months and then one day it just dropped one hashboard, I immediately went LP mode and it worked for a few days w/o problems, and then from that point every day was worse and worse. It wouldn't run Turbo and Normal at all, or sometime it would run all 3 hashboards on Turbo but none on LP. Other times, it would see couple of chips on couple of boards but not run them. A lot of restarting kinda got me to use it for a month before I RMA-ed it.

But yeah, when I went with Vnish firmware, I literally started fiddling with all the different combos of voltage and frequency, it kept working on one hashboard or maximum two. And the one week it decided it was over. It just said: "NO! You've abused me enough, I will not mine for you anymore". And that's where I decided to RMA it's ass.

mikeywith

legendary

Activity: 2394

Merit: 6581

be constructive or S.T.F.U

Quote from: favebook on August 07, 2020, 06:26:32 AM

I couldn't get it to work properly but custom firmware helped to run it at least with 1 or 2 hashboards at the time. Didn't really narrow the problem down to either hashboards or PSU but I assume PSU was bad. Couldn't wait for new one to be in shop so I RMA-ed it (this was before corona).

It was more than likely a PSU issue, I have had the same issue on one of friend's S17 pro as well, and running the miner on low-power-mode fixed the issue.

So what happened was that the PSU wasn't exactly dead but it couldn't deliver enough power to run the hash boards on turbo or normal mode, what the custom firmware did to your miner was probably nothing different, it has probably tuned the hashboards to work on a lower frequency and voltage so then the PSU was good enough to run 1-2 hashboards.

It's worth saying that after running this bad PSU for about 2 weeks, it finally got to the point whereby it couldn't handle the low-power-mode either and it had to be replaced, this, of course, depends on the how damaged the PSU is, but as long as it can't run the miner with the stock firmware on the default settings then it's always a good idea to get a replacement as soon as possible.

favebook

sr. member

Activity: 604

Merit: 416

Quote from: philipma1957 on August 02, 2020, 10:42:16 PM

as bitmain stopped selling them. or any other gear.

https://shop.bitmain.com/product/detail?pid=00020200403105249382Ow2fHTq80690

Was on sale for brief moment but seems to be sold out now. There are other PSUs on sale however.

To OP:

Try using custom firmware if you are up for doing testing yourself. If not, try putting your miner on one side horizontally instead of vertically (low chance of success but worth trying). I had exactly the same problem with my S17 Pro 50T before as I wrote in many threads before, I couldn't get it to work properly but custom firmware helped to run it at least with 1 or 2 hashboards at the time. Didn't really narrow the problem down to either hashboards or PSU but I assume PSU was bad. Couldn't wait for new one to be in shop so I RMA-ed it (this was before corona).

Not really sure what you should do here, but try checking the link I gave above every day to see if PSU comes back to shop.

Philipma1957cellphone

full member

Activity: 416

Merit: 125

Good as I dropped the last 4 digits of phone. Let him know that you found him from bitcointalk. He fixed two of my m20s and he fixed steamtyme m20s.

PopoJeff

full member

Activity: 414

Merit: 182

Found it... thanks.

Philipma1957cellphone

full member

Activity: 416

Merit: 125

Quote from: PopoJeff on August 05, 2020, 10:30:40 AM

@philipma1957

Was it you that said somewhere you have a repair contact in NC somewhere? I got and S17+ for almost free with my Bitmain credit just prior to the virus. One board isnt reading (temp sensor error). I created a DOA repair ticket with Bitmain, and they wanted me to ship it to Asia for repair because CA faculty was closed due to virus. The agreed to honor my request to wait for CA to re-open..... but..... I'm still waiting.
It's running fine on two boards, but was wonder what kind of costs i might incur to ship to NC dude for repair. Might even be able to hand deliver... I have several friends from here in PA who work down there, and they go back n forth often.

I do. I need to look at my threads here. Major storm knocked out power. Internet. Cable. Slowed cell phones. Let me see if I posted the link in another thread.

Go to page 2 of this section. Steamtyme has a repair thread on his m20s. I gave a phone and a link copying links on a cell phone is hard for me. But the number is 919 283

PopoJeff

full member

Activity: 414

Merit: 182

@philipma1957

Was it you that said somewhere you have a repair contact in NC somewhere? I got and S17+ for almost free with my Bitmain credit just prior to the virus. One board isnt reading (temp sensor error). I created a DOA repair ticket with Bitmain, and they wanted me to ship it to Asia for repair because CA faculty was closed due to virus. The agreed to honor my request to wait for CA to re-open..... but..... I'm still waiting.
It's running fine on two boards, but was wonder what kind of costs i might incur to ship to NC dude for repair. Might even be able to hand deliver... I have several friends from here in PA who work down there, and they go back n forth often.

mikeywith

legendary

Activity: 2394

Merit: 6581

be constructive or S.T.F.U

You should have waited 30 seconds before copying the Kernel log, it' missing all the important details, after the last line it should show

Code:

power.c:216:power_init: power init ...

and then a whole bunch of other details, so please post again, also none of the links you posted contain any images, please use imgur.com or imgbb.com to upload the pictures.

agilmore

jr. member

Activity: 40

Merit: 13

Quote from: ?? on ??

Thanks All for the suggestions. I'll give these a shot tomorrow and report back. FYI, I am in the USA.

Heres the log after switching to Low Power mode. Also, maybe it was there before, but I didnt notice it, but this time the Miner Status was temporarily displayed.
See the screenshots at the bottom.

Code:

Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
CPU: Testing write buffer coherency: ok
CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
Setting up static identity map for 0x100000 - 0x100058
CPU1: failed to boot: -1
Brought up 1 CPUs
SMP: Total of 1 processors activated (666.66 BogoMIPS).
CPU: All CPU(s) started in SVC mode.
devtmpfs: initialized
VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4
clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
pinctrl core: initialized pinctrl subsystem
NET: Registered protocol family 16
DMA: preallocated 256 KiB pool for atomic coherent allocations
cpuidle: using governor menu
hw-breakpoint: found 5 (+1 reserved) breakpoint and 1 watchpoint registers.
hw-breakpoint: maximum watchpoint size is 4 bytes.
zynq-ocm f800c000.ps7-ocmc: ZYNQ OCM pool: 256 KiB @ 0xcf880000
vgaarb: loaded
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
media: Linux media interface: v0.10
Linux video capture interface: v2.00
pps_core: LinuxPPS API ver. 1 registered
pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti 
PTP clock support registered
EDAC MC: Ver: 3.0.0
Advanced Linux Sound Architecture Driver Initialized.
clocksource: Switched to clocksource arm_global_timer
NET: Registered protocol family 2
TCP established hash table entries: 2048 (order: 1, 8192 bytes)
TCP bind hash table entries: 2048 (order: 2, 16384 bytes)
TCP: Hash tables configured (established 2048 bind 2048)
UDP hash table entries: 256 (order: 1, 8192 bytes)
UDP-Lite hash table entries: 256 (order: 1, 8192 bytes)
NET: Registered protocol family 1
RPC: Registered named UNIX socket transport module.
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
PCI: CLS 0 bytes, default 64
Trying to unpack rootfs image as initramfs...
rootfs image is not initramfs (no cpio magic); looks like an initrd
Freeing initrd memory: 25980K (cc1a2000 - cdb01000)
hw perfevents: enabled with armv7_cortex_a9 PMU driver, 7 counters available
futex hash table entries: 512 (order: 3, 32768 bytes)
workingset: timestamp_bits=28 max_order=16 bucket_order=0
jffs2: version 2.2. (NAND) (SUMMARY)  © 2001-2006 Red Hat, Inc.
io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered (default)
dma-pl330 f8003000.ps7-dma: Loaded driver for PL330 DMAC-241330
dma-pl330 f8003000.ps7-dma: 	DBUFF-128x8bytes Num_Chans-8 Num_Peri-4 Num_Events-16
e0000000.serial: ttyPS0 at MMIO 0xe0000000 (irq = 158, base_baud = 6249999) is a xuartps
console [ttyPS0] enabled
xdevcfg f8007000.ps7-dev-cfg: ioremap 0xf8007000 to cf86e000
[drm] Initialized drm 1.1.0 20060810
brd: module loaded
loop: module loaded
CAN device driver interface
gpiod_set_value: invalid GPIO
libphy: MACB_mii_bus: probed
macb e000b000.ethernet eth0: Cadence GEM rev 0x00020118 at 0xe000b000 irq 31 (00:0a:35:00:00:00)
Generic PHY e000b000.etherne:00: attached PHY driver [Generic PHY] (mii_bus:phy_addr=e000b000.etherne:00, irq=-1)
e1000e: Intel(R) PRO/1000 Network Driver - 3.2.6-k
e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
ehci-pci: EHCI PCI platform driver
usbcore: registered new interface driver usb-storage
mousedev: PS/2 mouse device common for all mice
i2c /dev entries driver
Xilinx Zynq CpuIdle Driver started
sdhci: Secure Digital Host Controller Interface driver
sdhci: Copyright(c) Pierre Ossman
sdhci-pltfm: SDHCI platform and OF driver helper
mmc0: SDHCI controller on e0100000.ps7-sdio [e0100000.ps7-sdio] using ADMA
ledtrig-cpu: registered to indicate activity on CPUs
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
nand: device found, Manufacturer ID: 0x2c, Chip ID: 0xda
nand: Micron MT29F2G08ABAGAWP
nand: 256 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 128
nand: WARNING: pl35x-nand: the ECC used on your system is too weak compared to the one required by the NAND chip
Bad block table found at page 131008, version 0x01
Bad block table found at page 130944, version 0x01
6 ofpart partitions found on MTD device pl35x-nand
Creating 6 MTD partitions on "pl35x-nand":
0x000000000000-0x000002800000 : "BOOT.bin-env-dts-kernel"
0x000002800000-0x000004800000 : "ramfs"
0x000004800000-0x000005000000 : "configs"
0x000005000000-0x000006000000 : "reserve"
0x000006000000-0x000008000000 : "ramfs-bak"
0x000008000000-0x000010000000 : "reserve1"
NET: Registered protocol family 10
sit: IPv6 over IPv4 tunneling driver
NET: Registered protocol family 17
can: controller area network core (rev 20120528 abi 9)
NET: Registered protocol family 29
can: raw protocol (rev 20120528)
can: broadcast manager protocol (rev 20120528 t)
can: netlink gateway (rev 20130117) max_hops=1
zynq_pm_ioremap: no compatible node found for 'xlnx,zynq-ddrc-a05'
zynq_pm_late_init: Unable to map DDRC IO memory.
Registering SWP/SWPB emulation handler
hctosys: unable to open rtc device (rtc0)
ALSA device list:
  No soundcards found.
RAMDISK: gzip image found at block 0
EXT4-fs (ram0): couldn't mount as ext3 due to feature incompatibilities
EXT4-fs (ram0): mounted filesystem without journal. Opts: (null)
VFS: Mounted root (ext4 filesystem) on device 1:0.
devtmpfs: mounted
Freeing unused kernel memory: 1024K (c0a00000 - c0b00000)
EXT4-fs (ram0): re-mounted. Opts: block_validity,delalloc,barrier,user_xattr
random: dd urandom read with 0 bits of entropy available
ubi0: attaching mtd2
ubi0: scanning is finished
ubi0: attached mtd2 (name "configs", size 8 MiB)
ubi0: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
ubi0: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
ubi0: VID header offset: 2048 (aligned 2048), data offset: 4096
ubi0: good PEBs: 64, bad PEBs: 0, corrupted PEBs: 0
ubi0: user volume: 1, internal volumes: 1, max. volumes count: 128
ubi0: max/mean erase counter: 5/2, 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): recovery needed
UBIFS (ubi0:0): recovery completed
UBIFS (ubi0:0): UBIFS: mounted UBI device 0, volume 0, name "configs"
UBIFS (ubi0:0): LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
UBIFS (ubi0:0): FS size: 1396736 bytes (1 MiB, 11 LEBs), journal size 888833 bytes (0 MiB, 5 LEBs)
UBIFS (ubi0:0): reserved for root: 65970 bytes (64 KiB)
UBIFS (ubi0:0): media format: w4/r0 (latest is w4/r0), UUID 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: 4353/1931, 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): recovery needed
UBIFS (ubi1:0): recovery completed
UBIFS (ubi1:0): UBIFS: mounted UBI device 1, volume 0, name "reserve1"
UBIFS (ubi1:0): LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
UBIFS (ubi1:0): FS size: 123039744 bytes (117 MiB, 969 LEBs), journal size 6221824 bytes (5 MiB, 49 LEBs)
UBIFS (ubi1:0): reserved for root: 4952683 bytes (4836 KiB)
UBIFS (ubi1:0): media format: w4/r0 (latest is w4/r0), UUID 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 = 0xab011
In fpga mem driver!
request_mem_region OK!
fpga mem virtual address is 0xd2000000
random: nonblocking pool is initialized
Alignment trap: cg@0/RStratum (1324) PC=0x00020c54 Instr=0xedd20b1a Address=0x00000089 FSR 0x001
Alignment trap: not handling instruction edd20b1a at [<00020c54>]
Unhandled fault: alignment exception (0x001) at 0x00000089
pgd = c4150000
[00000089] *pgd=0983a831, *pte=00000000, *ppte=00000000
Alignment trap: cg@0/RStratum (1663) PC=0x00020c54 Instr=0xedd20b1a Address=0x00000089 FSR 0x001
Alignment trap: not handling instruction edd20b1a at [<00020c54>]
Unhandled fault: alignment exception (0x001) at 0x00000089
pgd = cbf58000
[00000089] *pgd=09e42831, *pte=00000000, *ppte=00000000
Alignment trap: cg@0/RStratum (2003) PC=0x00020c54 Instr=0xedd20b1a Address=0x00000089 FSR 0x001
Alignment trap: not handling instruction edd20b1a at [<00020c54>]
Unhandled fault: alignment exception (0x001) at 0x00000089
pgd = cbf54000
[00000089] *pgd=08256831, *pte=00000000, *ppte=00000000
Alignment trap: cg@0/RStratum (3090) PC=0x00020c54 Instr=0xedd20b1a Address=0x00000089 FSR 0x001
Alignment trap: not handling instruction edd20b1a at [<00020c54>]
Unhandled fault: alignment exception (0x001) at 0x00000089
pgd = c3bbc000
[00000089] *pgd=0d591831, *pte=00000000, *ppte=00000000
Alignment trap: cg@0/RStratum (3793) PC=0x00020c54 Instr=0xedd20b1a Address=0x00000089 FSR 0x001
Alignment trap: not handling instruction edd20b1a at [<00020c54>]
Unhandled fault: alignment exception (0x001) at 0x00000089
pgd = c9c0c000
[00000089] *pgd=0bccd831, *pte=00000000, *ppte=00000000
Alignment trap: cg@0/RStratum (4855) PC=0x00020c54 Instr=0xedd20b1a Address=0x00000089 FSR 0x001
Alignment trap: not handling instruction edd20b1a at [<00020c54>]
Unhandled fault: alignment exception (0x001) at 0x00000089
pgd = c6ef4000
[00000089] *pgd=09e42831, *pte=00000000, *ppte=00000000
Alignment trap: cg@0/RStratum (5194) PC=0x00020c54 Instr=0xedd20b1a Address=0x00000089 FSR 0x001
Alignment trap: not handling instruction edd20b1a at [<00020c54>]
Unhandled fault: alignment exception (0x001) at 0x00000089
pgd = c3d6c000
[00000089] *pgd=0bf51831, *pte=00000000, *ppte=00000000
Alignment trap: cg@0/RStratum (5533) PC=0x00020c54 Instr=0xedd20b1a Address=0x00000089 FSR 0x001
Alignment trap: not handling instruction edd20b1a at [<00020c54>]
Unhandled fault: alignment exception (0x001) at 0x00000089
pgd = c9c0c000
[00000089] *pgd=09e42831, *pte=00000000, *ppte=00000000
Alignment trap: cg@0/RStratum (5872) PC=0x00020c54 Instr=0xedd20b1a Address=0x00000089 FSR 0x001
Alignment trap: not handling instruction edd20b1a at [<00020c54>]
Unhandled fault: alignment exception (0x001) at 0x00000089
pgd = c9c14000
[00000089] *pgd=0bf5f831, *pte=00000000, *ppte=00000000
Alignment trap: cg@0/RStratum (6211) PC=0x00020c54 Instr=0xedd20b1a Address=0x00000089 FSR 0x001
Alignment trap: not handling instruction edd20b1a at [<00020c54>]
Unhandled fault: alignment exception (0x001) at 0x00000089
pgd = c433c000
[00000089] *pgd=08253831, *pte=00000000, *ppte=00000000
Alignment trap: cg@0/RStratum (6578) PC=0x00020c54 Instr=0xedd20b1a Address=0x00000089 FSR 0x001
Alignment trap: not handling instruction edd20b1a at [<00020c54>]
Unhandled fault: alignment exception (0x001) at 0x00000089
pgd = c9c14000
[00000089] *pgd=0bf5c831, *pte=00000000, *ppte=00000000
Alignment trap: cg@0/RStratum (7212) PC=0x00020c54 Instr=0xedd20b1a Address=0x00000089 FSR 0x001
Alignment trap: not handling instruction edd20b1a at [<00020c54>]
Unhandled fault: alignment exception (0x001) at 0x00000089
pgd = c8d94000
[00000089] *pgd=06ef6831, *pte=00000000, *ppte=00000000
 [2020-08-04 02:09:32.242] httpListenThread start ret=0
2020-08-04 02:09:32 driver-btm-soc.c:3160:init_freq_mode: This is scan-user version
2020-08-04 02:09:32 driver-btm-soc.c:3896:bitmain_soc_init: opt_multi_version=1
2020-08-04 02:09:32 driver-btm-soc.c:3897:bitmain_soc_init: opt_bitmain_ab=1
2020-08-04 02:09:32 driver-btm-soc.c:3898:bitmain_soc_init: opt_bitmain_work_mode=0
2020-08-04 02:09:32 driver-btm-soc.c:3521:_show_sn: no SN got, please write SN to /nvdata/sn
2020-08-04 02:09:32 driver-btm-soc.c:3191:init_phy_mem_nonce2_jobid_address: Detect 256MB control board of XILINX
2020-08-04 02:09:32 driver-btm-soc.c:3904:bitmain_soc_init: Miner compile time: Tue Apr 16 19:05:06 CST 2019
2020-08-04 02:09:32 driver-btm-soc.c:3906:bitmain_soc_init: last commit version: 8b856e7 commit time: 2019-04-16 16:36:14 build: 2019-04-16 19:09:46
2020-08-04 02:09:32 driver-btm-soc.c:3223:check_fan_multi: check fan for 20 times...
2020-08-04 02:09:34 driver-btm-soc.c:3299:init_miner_version: miner ID : 813275ce57408854
2020-08-04 02:09:34 driver-btm-soc.c:3305:init_miner_version: FPGA Version = 0xB011
2020-08-04 02:09:34 driver-btm-soc.c:404:check_chain: !! chain[0]is exist
2020-08-04 02:09:34 driver-btm-soc.c:404:check_chain: !! chain[1]is exist
2020-08-04 02:09:34 driver-btm-soc.c:404:check_chain: !! chain[2]is exist
2020-08-04 02:09:38 driver-btm-soc.c:3722:get_product_id: product_id[0] = 0
2020-08-04 02:09:38 driver-btm-soc.c:3722:get_product_id: product_id[1] = 0
2020-08-04 02:09:38 driver-btm-soc.c:3722:get_product_id: product_id[2] = 0
2020-08-04 02:09:38 driver-btm-soc.c:3823:bitmain_board_init: g_product_id = 0
2020-08-04 02:09:38 driver-btm-soc.c:3574:_set_project_type: Project type: Antminer S17 Pro
2020-08-04 02:09:38 driver-btm-soc.c:3321:dump_pcb_bom_version: Chain [0] PCB Version: 0x0101
2020-08-04 02:09:38 driver-btm-soc.c:3322:dump_pcb_bom_version: Chain [0] BOM Version: 0x0103
2020-08-04 02:09:38 driver-btm-soc.c:3321:dump_pcb_bom_version: Chain [1] PCB Version: 0x0101
2020-08-04 02:09:38 driver-btm-soc.c:3322:dump_pcb_bom_version: Chain [1] BOM Version: 0x0103
2020-08-04 02:09:38 driver-btm-soc.c:3321:dump_pcb_bom_version: Chain [2] PCB Version: 0x0101
2020-08-04 02:09:38 driver-btm-soc.c:3322:dump_pcb_bom_version: Chain [2] BOM Version: 0x0103
2020-08-04 02:09:38 pic.c:619:pic_reset: chain[0] ok
2020-08-04 02:09:43 pic.c:898:jump_to_app_from_loader: chain[0] ok
2020-08-04 02:09:43 pic.c:619:pic_reset: chain[1] ok
2020-08-04 02:09:48 pic.c:898:jump_to_app_from_loader: chain[1] ok
2020-08-04 02:09:48 pic.c:619:pic_reset: chain[2] ok
2020-08-04 02:09:53 pic.c:898:jump_to_app_from_loader: chain[2] ok
2020-08-04 02:09:53 driver-btm-soc.c:3840:bitmain_board_init: Enter 30s sleep to make sure power release finish.
2020-08-04 02:09:53 driver-btm-soc.c:1156:heart_beat_func_one_chain: for chain 2
2020-08-04 02:09:53 driver-btm-soc.c:1156:heart_beat_func_one_chain: for chain 1
2020-08-04 02:09:53 driver-btm-soc.c:1156:heart_beat_func_one_chain: for chain 0

https://photos.google.com/album/AF1QipPE5gJFdH8kH6BxaXAJxQkTA3bski1-pR7Qk0Df/photo/AF1QipPIgDdruwhtQCOXEe724dG4PuUMf3A16duMEUP2
https://photos.google.com/album/AF1QipPE5gJFdH8kH6BxaXAJxQkTA3bski1-pR7Qk0Df/photo/AF1QipNlom_28Ix6hduzLlLS1jraraU15WaWFMOsrzPD

philipma1957

legendary

Activity: 4256

Merit: 8551

'The right to privacy matters'

yeah i think he killed psu.

if he killed the psu it will be hard to get one.

as bitmain stopped selling them. or any other gear.

Op are you usa based?

i may have a source for psu.

first listen to mikey

set to low
check all power plugs to psu
make sure you have 210-240 power.

mikeywith

legendary

Activity: 2394

Merit: 6581

be constructive or S.T.F.U

This >

Code:

2020-08-03 00:03:07 driver-btm-soc.c:3657:check_asic_number_with_power_on: Chain[0]: find 0 asic, times 2

Code:

2020-08-03 00:03:37 driver-btm-soc.c:3657:check_asic_number_with_power_on: Chain[1]: find 0 asic, times 2

Code:

2020-08-03 00:03:48 driver-btm-soc.c:3657:check_asic_number_with_power_on: Chain[2]: find 0 asic, times 0

In plain English implies that the contorl board isn't sensing/seeing any asics on all 3 hash boards, now if it was only on a single chain I would say it's a taosted chain, but what are the chances of 3 hash boards going down at the same time? I would say slim to nothing which leads me to think that this has to be a POWER related issue.

- Your feeding the PSU with a higher/lower AC voltage that it can handle, so you need to tell us what is the voltage

or

- Your PSU has gone bad and needs replacement, but before you do that, give it a good dusting and set the miner on "low" settings, the results that come out of this troubleshooting will probably lead us to know what the problem actually is.

agilmore

jr. member

Activity: 40

Merit: 13

Quote from: philipma1957 on August 02, 2020, 07:35:01 PM

did you ever use any firmware other then bitmain.

No.

Quote from: philipma1957 on August 02, 2020, 07:35:01 PM

what setting is it on low normal turbo.

Turbo.

Quote from: philipma1957 on August 02, 2020, 07:35:01 PM

is it the s17pro 50th 53th 56th

I dont recall. How can I find out?

Quote from: philipma1957 on August 02, 2020, 07:35:01 PM

which one are you using?

Kernel Version: Linux 4.6.0-xilinx-gff8137b-dirty #25 SMP PREEMPT Fri Nov 23 15:30:52 CST 2018
Hardware Version: 17.10.1.3

philipma1957

legendary

Activity: 4256

Merit: 8551

'The right to privacy matters'

i am looking at it.

unplug it let it sit.

lets play 20 questions.

did you ever use any firmware other then bitmain.

what setting is it on low normal turbo.

is it the s17pro 50th 53th 56th

do not use a different firmware but if you have always had bitmain firmware

which one are you using?

do not upgrade the bitmain firmware just tell which one you have.

Topic: S17 Pro no longer hashing. Bad ASICs ? - page 3. (Read 1160 times)