Bitcoin Forum>Bitcoin>Mining>Mining support
Author

Topic: S17+ Wont mine, socket failed to connect, total packet loss (Read 404 times)

massivegoatdynamic
newbie
Activity: 19
Merit: 0
S17+ Wont mine, socket failed to connect, total packet loss
February 12, 2023, 11:03:21 PM
#36
@ BitMaxz

I do have autotuning enabled but the efficiency doesn't seem much different if at all. Granted I only have one hashboard working and that might be part of why the efficiency gains aren't there. In the "total power for all hashboards" my default is 2800 watts, I dialed it back to 2,100 watts which I thought would make a significant impact but its about the same ~ 37 watts best but more hovering around 39-40 watts. I made some extension cords where I could measure current and physical measurements backs up the efficiency readings.

I had added on a large blower fan to move more air and I am measuring about 665 watts including the fan and I am mining at 15-17.5 TH. Perhaps with more working hashboards I would significantly improve but don't know.

I am on the fence about investing in a zeus miner deal to check out my bad hashboards or just springing for a new miner. I think if I ever go the used route again I need all the equipment to diagnose and fix them. Otherwise maybe new + immersion cooling + under clocking will yield a miner that wont have any sick days ever?

BitMaxz
legendary
Activity: 3472
Merit: 3217
Playbet.io - Crypto Casino and Sportsbook
Re: S17+ Wont mine, socket failed to connect, total packet loss
February 12, 2023, 06:20:42 PM
#35
Quote from: massivegoatdynamic on February 12, 2023, 12:45:12 PM
~snip~

I would say the main benefit I have seen so far is the lower operating temp of the chips dialing back the power. Granted I am not sure how you can predict how much longer the rig would last at a lower power setting.

Have you tried Bitmain's low-power mode for the S19 series? I have seen some pretty impressive efficiency improvements with that latest power mode. I only have the one S17+ currently, debating on if I should buy another rig or just buy the bitty.


Like the above said it helps to increase the lifespan of your unit if you run the miner at LPM and it should improve a bit efficiency.

And about Braiins OS efficiency did you turn on the autotuning?
If LPM does not work then try manually setup the power and frequency from the braiins OS dashboard just make sure to read the documentation below and make sure to limit temp.

- https://docs.braiins.com/os/open-source-en/Configuration/index_configuration.html
mikeywith
legendary
Activity: 2436
Merit: 6643
be constructive or S.T.F.U
Re: S17+ Wont mine, socket failed to connect, total packet loss
February 12, 2023, 02:58:40 PM
#34
Quote from: massivegoatdynamic on February 12, 2023, 12:45:12 PM
Granted I am not sure how you can predict how much longer the rig would last at a lower power setting.

You can't, it just happens when it does, in theory, lower power mode should increase the lifespan of the miner, but is it going to be 6 months instead of 3, or 13 days instead of 12, you simply can't tell.

Quote
Have you tried Bitmain's low power mode for the S19 series? I have seen some pretty impressive efficiency improvements with that latest power mode. I only have the one S17+ currently, debating on if I should buy another rig or just buy the bitty.

I don't own any of those, but I can assure you the low power mode works and does improve efficiency, in fact, most custom firmware do the same long before the release of the stock firmware, every gear should gain some efficiency when underclocked, the manufacturer tunes the gears to get the perfect match between a few factors (total hashrate, temps, warranty, and efficiency) they want the most hashrate at the best efficiency that can reasonably run safe thought the period of warranty and a few more months/years.

They can tune a 30w/th gear to do 25w/th but that will mean a lot less hashrate, which means they probably can't sell it for the same price despite the 5w improvements, they can also turn a 100th gear into 120th gear, but that means an extra 5w/th or a higher power need than their PSUs or what most clients want, so this "balancing" of things isn't always the best for everyone.

It's actually a pity that they announced the firmware as a Christmas gift, as if they invented the wheel when some other folks have already been running at the same efficiency or better using custom firmware long before Christmas, the clock settings should be open by default, at least the ones that are lower than the default, in many places temps get pretty high on 20-40 days a year, gears can't run stock, it makes no sense to invest in cooling just too cool the miner for 20-40 days, also makes no sense to let it toast, a perfect solution would be to underclock it, even better, doing so on the stock firmware without having to pay dev fees.

massivegoatdynamic
newbie
Activity: 19
Merit: 0
Re: S17+ Wont mine, socket failed to connect, total packet loss
February 12, 2023, 12:45:12 PM
#33
I haven't had a chance to try the freezer technique but did manage to install Braiins OS+. Granted I am very new to this so I could be running it incorrectly. It has an option to vary the power for all the hashboards, in my case the nominal is ~ 2,800 watts and allows you to choose a higher power or lower power. I am more interested in the efficiency side of things and have dialed it down to 1,700 watts. Unfortunately I haven't been able to realize any serious efficiency improvements. The best I have seen is 5% but it is only temporary.

Nominal should be 40 watts/TH but at best I have seen it touch 38 watts but only briefly, it seems to hover around the 39-40 watt/TH range. I may try Hive OS next or ASIC.TO to see if there is a difference. It also could be that my miner is dying too. The kernel log for Braiins is reading a temp sensor error on my last good hashboard so it is only a matter of time before my rig becomes a full-on paper weight.

I would say the main benefit I have seen so far is the lower operating temp of the chips dialing back the power. Granted I am not sure how you can predict how much longer the rig would last at a lower power setting.

Have you tried Bitmain's low power mode for the S19 series? I have seen some pretty impressive efficiency improvements with that latest power mode. I only have the one S17+ currently, debating on if I should buy another rig or just buy the bitty.
mikeywith
legendary
Activity: 2436
Merit: 6643
be constructive or S.T.F.U
Re: S17+ Wont mine, socket failed to connect, total packet loss
January 24, 2023, 06:54:40 PM
#32
Quote from: massivegoatdynamic on January 24, 2023, 05:48:25 PM
Thanks for the feedback. I have heard of the freezer technique for hard drives but not this.

I tried the freezer thing on a few boards, there is a good chance the board might come back to life.


Quote
I am going to look at the zeusbtc manual and see what it says. I have a small power supply that can do 20 volts and a hot air station but am wondering if you actually need to buy their tester or an equivalent to troubleshoot what chip is bad. I have very limited experience but have swapped a chip for a hard drive before.


the tool doesn't really tell you which chip is bad, same for the other tools some are a lot better than zeus tool like "Asicrepair", all the tool does is give continues voltage to the hashboard so you can measure the pins, the firmware will only give that pulse for a few seconds and then stops, so you won't have enough time to measure the board, these tools make the job easier, but you will still need to read the manual and measure all required pins.

These tools will also give you a rough guess, a similar one to the one in the kernel log, your log says

Quote
2023-01-24 17:30:41 temperature.c:843:get_temp_info: read temp sensor failed: chain = 2, sensor = 0, chip = 14, reg = 1

So it's suggesting the issue is at chip no 14, could be 14 or the chip before/after it, could also be another chip for all that matters.

Quote
I saw Braiins has a firmware that sounds similar to asic.to but wouldn't cost an extra percentage as long as you mine with them. Have you had any experience with them? It seems Hive OS also has something similar.
Hive OS is not that good, Braiins > I don't have enough experience with the firmware to judge, vnish (asic.to/awesome miner) I have a long experience with, but anyways, they should all do the trick of tuning the board to hopefully bring it back to life, the chances are slim but worth trying.
massivegoatdynamic
newbie
Activity: 19
Merit: 0
Re: S17+ Wont mine, socket failed to connect, total packet loss
January 24, 2023, 05:48:25 PM
#31
@ Mikeywith

Thanks for the feedback. I have heard of the freezer technique for hard drives but not this. I am going to look at the zeusbtc manual and see what it says. I have a small power supply that can do 20 volts and a hot air station but am wondering if you actually need to buy their tester or an equivalent to troubleshoot what chip is bad. I have very limited experience but have swapped a chip for a hard drive before.

I saw Braiins has a firmware that sounds similar to asic.to but wouldn't cost an extra percentage as long as you mine with them. Have you had any experience with them? It seems Hive OS also has something similar.
mikeywith
legendary
Activity: 2436
Merit: 6643
be constructive or S.T.F.U
Re: S17+ Wont mine, socket failed to connect, total packet loss
January 24, 2023, 05:41:26 PM
#30
Code:
2023-01-24 17:30:41 temperature.c:843:get_temp_info: read temp sensor failed: chain = 2, sensor = 0, chip = 14, reg = 1

This is most likely a hardware issue, nothing much you can do about it, here are two things to try

1- Flash custom firmware like Vnish (use Awseomeiner or Asic.to distributions) chose a low power profile and let it tune for a couple of hours that might fix the issues
2- Unplug chain 2 which causes the problem, put it in a plastic bag, drop it in the freezer for a day, and plug it back.

if all fail, you will need to inspect the hash board and see if there are any solder balls accumulating underneath the heatsinks (shorting the chips), aside from that, you are going to need a tested and a lot of experience to fix it, I have personally threw away a dozen of these boards because I don't have what it takes to fix them and I have no time nor desire to learn how to fix them.
massivegoatdynamic
newbie
Activity: 19
Merit: 0
Re: S17+ Wont mine, socket failed to connect, total packet loss
January 24, 2023, 03:05:47 PM
#29
I did see that voltage and frequency thing in the developer so when I get free time this weekend I will poke around. I did not see any other settings other that sleep and normal, I guess the S17+ didn't have a low power and turbo mode?

I still have the "read temp sensor failed" message but at least that board is hashing. Chain 1 seems to be dead, it has a note that it found zero asics. Do you think it would be possible to bring it back to life by lowering the voltage? Or possibly trying Braiins OS+ to see if that can bring it back?

Please see the attached log and let me know how I can fiddle around with the board to bring it back.

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: 203432K/245760K available (6345K kernel code, 231K rwdata, 1896K rodata, 1024K init, 223K bss, 25944K 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: 12904K (cce67000 - 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: 24/12, 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: 4101/1017, WL threshold: 4096, image sequence number: 3265111179
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 1AF6F1E1-61F0-462C-AE44-C7D9596CF7E2, 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 = 0xb023
In fpga mem driver!
request_mem_region OK!
fpga mem virtual address is 0xd2000000
random: nonblocking pool is initialized
2023-01-24 17:21:35 driver-btm-api.c:779:init_freq_mode: This is scan-user version
2023-01-24 17:21:35 driver-btm-api.c:2451:bitmain_soc_init: opt_multi_version     = 1
2023-01-24 17:21:35 driver-btm-api.c:2452:bitmain_soc_init: opt_bitmain_ab        = 1
2023-01-24 17:21:35 driver-btm-api.c:2453:bitmain_soc_init: opt_bitmain_work_mode = 0
2023-01-24 17:21:35 driver-btm-api.c:2454:bitmain_soc_init: Miner compile time: Tue Jun  2 10:31:07 CST 2020 type: Antminer S17+
2023-01-24 17:21:35 driver-btm-api.c:2455:bitmain_soc_init: commit version: 1ca50a5 2020-06-01 18:51:22, build by: lol 2020-06-02 10:37:21
2023-01-24 17:21:35 driver-btm-api.c:2083:show_sn: len:16, 80244d0c2b104814
2023-01-24 17:21:35 driver-btm-api.c:2461:bitmain_soc_init: show sn return 1
2023-01-24 17:21:35 driver-btm-api.c:2103:handle_sn_for_factory_mode: show sn return 1
2023-01-24 17:21:35 driver-btm-api.c:2141:handle_sn_for_factory_mode: read sn success, 80244d0c2b104814
2023-01-24 17:21:35 fan.c:284:front_fan_power_on: Note: front fan is power on!
2023-01-24 17:21:35 fan.c:296:rear_fan_power_on: Note: rear fan is power on!
2023-01-24 17:21:35 driver-btm-api.c:1314:miner_device_init: Detect 256MB control board of XILINX
2023-01-24 17:21:35 driver-btm-api.c:1255:init_fan_parameter: fan_eft : 0  fan_pwm : 0
2023-01-24 17:21:41 driver-btm-api.c:1239:init_miner_version: miner ID : 80244d0c2b104814
2023-01-24 17:21:41 driver-btm-api.c:1245:init_miner_version: FPGA Version = 0xB023
2023-01-24 17:21:46 driver-btm-api.c:837:get_product_id: product_id[0] = 0
2023-01-24 17:21:46 driver-btm-api.c:837:get_product_id: product_id[1] = 0
2023-01-24 17:21:46 driver-btm-api.c:837:get_product_id: product_id[2] = 0
2023-01-24 17:21:46 driver-btm-api.c:2234:update_conf_by_power_feedback: Power feedback is disabled
2023-01-24 17:21:46 driver-btm-api.c:2202:get_calibration_voltage: calibration voltage flag is error data.
2023-01-24 17:21:46 driver-btm-api.c:2268:update_conf_by_power_feedback: Note: no calibration voltage, default diff = 0
2023-01-24 17:21:46 frequency.c:1457:adjust_higer_max_vol_table: adjust_higer_max_vol_table, adjust_vol = 0
2023-01-24 17:21:46 thread.c:1363:create_read_nonce_reg_thread: create thread
2023-01-24 17:21:52 driver-btm-api.c:1239:init_miner_version: miner ID : 80244d0c2b104814
2023-01-24 17:21:52 driver-btm-api.c:1245:init_miner_version: FPGA Version = 0xB023
2023-01-24 17:21:58 driver-btm-api.c:837:get_product_id: product_id[0] = 0
2023-01-24 17:21:58 driver-btm-api.c:837:get_product_id: product_id[1] = 0
2023-01-24 17:21:58 driver-btm-api.c:837:get_product_id: product_id[2] = 0
2023-01-24 17:21:58 driver-btm-api.c:792:_set_project_type: project:0
2023-01-24 17:21:58 driver-btm-api.c:813:_set_project_type: Project type: Antminer S17+
2023-01-24 17:21:58 driver-btm-api.c:824:dump_pcb_bom_version: Chain [0] PCB Version: 0x0100
2023-01-24 17:21:58 driver-btm-api.c:825:dump_pcb_bom_version: Chain [0] BOM Version: 0x0100
2023-01-24 17:21:58 driver-btm-api.c:824:dump_pcb_bom_version: Chain [1] PCB Version: 0x0100
2023-01-24 17:21:58 driver-btm-api.c:825:dump_pcb_bom_version: Chain [1] BOM Version: 0x0100
2023-01-24 17:21:58 driver-btm-api.c:824:dump_pcb_bom_version: Chain [2] PCB Version: 0x0100
2023-01-24 17:21:58 driver-btm-api.c:825:dump_pcb_bom_version: Chain [2] BOM Version: 0x0100
2023-01-24 17:21:58 driver-btm-api.c:2372:bitmain_board_init: Fan check passed.
2023-01-24 17:21:59 board.c:36:jump_and_app_check_restore_pic: chain[0] PIC jump to app
2023-01-24 17:22:01 board.c:40:jump_and_app_check_restore_pic: Check chain[0] PIC fw version=0x88
2023-01-24 17:22:02 board.c:36:jump_and_app_check_restore_pic: chain[1] PIC jump to app
2023-01-24 17:22:04 board.c:40:jump_and_app_check_restore_pic: Check chain[1] PIC fw version=0x88
2023-01-24 17:22:05 board.c:36:jump_and_app_check_restore_pic: chain[2] PIC jump to app
2023-01-24 17:22:07 board.c:40:jump_and_app_check_restore_pic: Check chain[2] PIC fw version=0x88
2023-01-24 17:22:07 thread.c:1358:create_pic_heart_beat_thread: create thread
2023-01-24 17:22:07 power_api.c:213:power_init: Power init:
2023-01-24 17:22:07 power_api.c:214:power_init: current_voltage_raw = 0
2023-01-24 17:22:07 power_api.c:215:power_init: highest_voltage_raw = 2100
2023-01-24 17:22:07 power_api.c:216:power_init: working_voltage_raw = 1950
2023-01-24 17:22:07 power_api.c:217:power_init: higher_voltage_raw  = 2040
2023-01-24 17:22:07 power_api.c:218:power_init: check_asic_voltage_raw  = 2100
2023-01-24 17:22:07 driver-btm-api.c:2382:bitmain_board_init: Enter 30s sleep to make sure power release finish.
2023-01-24 17:22:07 power_api.c:186:power_off: init gpio907
2023-01-24 17:22:39 power_api.c:324:set_to_highest_voltage_by_steps: Set to voltage raw 2100, step by step.
2023-01-24 17:23:05 power_api.c:85:check_voltage_multi: retry time: 0
2023-01-24 17:23:06 power_api.c:40:_get_avg_voltage: chain = 0, voltage = 21.156368
2023-01-24 17:23:07 power_api.c:40:_get_avg_voltage: chain = 1, voltage = 21.180327
2023-01-24 17:23:08 power_api.c:40:_get_avg_voltage: chain = 2, voltage = 21.132408
2023-01-24 17:23:08 power_api.c:53:_get_avg_voltage: average_voltage = 21.156368
2023-01-24 17:23:08 power_api.c:71:check_voltage: target_vol = 21.00, actural_vol = 21.16, check voltage passed.
2023-01-24 17:23:08 uart.c:72:set_baud: set fpga_baud to 115200
2023-01-24 17:23:19 driver-btm-api.c:1134:check_asic_number_with_power_on: Chain[0]: find 65 asic, times 0
2023-01-24 17:23:30 driver-btm-api.c:1134:check_asic_number_with_power_on: Chain[1]: find 0 asic, times 0
2023-01-24 17:23:41 driver-btm-api.c:1134:check_asic_number_with_power_on: Chain[1]: find 0 asic, times 1
2023-01-24 17:23:51 driver-btm-api.c:1134:check_asic_number_with_power_on: Chain[1]: find 0 asic, times 2
2023-01-24 17:23:51 power_api.c:380:modify_check_asic_voltage: check_asic_voltage_raw  = 2100
chain 1, IO_DRIVE_STRENGTH_CONFIGURATION reg = 0x f1fffff
2023-01-24 17:24:00 driver-btm-api.c:1157:check_asic_number_with_power_on: Chain[1]: find 0 asic, times 3
2023-01-24 17:24:00 power_api.c:380:modify_check_asic_voltage: check_asic_voltage_raw  = 2050
2023-01-24 17:24:00 power_api.c:364:set_to_check_asic_voltage_by_steps: Set to voltage raw 2050, step by step.
2023-01-24 17:24:04 power_api.c:85:check_voltage_multi: retry time: 0
2023-01-24 17:24:05 power_api.c:40:_get_avg_voltage: chain = 0, voltage = 20.627205
2023-01-24 17:24:06 power_api.c:40:_get_avg_voltage: chain = 1, voltage = 20.651134
2023-01-24 17:24:07 power_api.c:40:_get_avg_voltage: chain = 2, voltage = 20.629256
2023-01-24 17:24:07 power_api.c:53:_get_avg_voltage: average_voltage = 20.635865
2023-01-24 17:24:07 power_api.c:71:check_voltage: target_vol = 20.50, actural_vol = 20.64, check voltage passed.
chain 1, IO_DRIVE_STRENGTH_CONFIGURATION reg = 0x f1fffff
2023-01-24 17:24:16 driver-btm-api.c:1157:check_asic_number_with_power_on: Chain[1]: find 0 asic, times 4
2023-01-24 17:24:16 power_api.c:380:modify_check_asic_voltage: check_asic_voltage_raw  = 2000
2023-01-24 17:24:16 power_api.c:364:set_to_check_asic_voltage_by_steps: Set to voltage raw 2000, step by step.
2023-01-24 17:24:19 power_api.c:85:check_voltage_multi: retry time: 0
2023-01-24 17:24:20 power_api.c:40:_get_avg_voltage: chain = 0, voltage = 20.150063
2023-01-24 17:24:22 power_api.c:40:_get_avg_voltage: chain = 1, voltage = 20.123270
2023-01-24 17:24:23 power_api.c:40:_get_avg_voltage: chain = 2, voltage = 20.175506
2023-01-24 17:24:23 power_api.c:53:_get_avg_voltage: average_voltage = 20.149613
2023-01-24 17:24:23 power_api.c:71:check_voltage: target_vol = 20.00, actural_vol = 20.15, check voltage passed.
chain 1, IO_DRIVE_STRENGTH_CONFIGURATION reg = 0x f1fffff
2023-01-24 17:24:31 driver-btm-api.c:1157:check_asic_number_with_power_on: Chain[1]: find 0 asic, times 5
2023-01-24 17:24:31 power_api.c:380:modify_check_asic_voltage: check_asic_voltage_raw  = 2100
2023-01-24 17:24:31 power_api.c:364:set_to_check_asic_voltage_by_steps: Set to voltage raw 2100, step by step.
2023-01-24 17:24:37 power_api.c:85:check_voltage_multi: retry time: 0
2023-01-24 17:24:38 power_api.c:40:_get_avg_voltage: chain = 0, voltage = 21.105794
2023-01-24 17:24:39 power_api.c:40:_get_avg_voltage: chain = 1, voltage = 21.129724
2023-01-24 17:24:40 power_api.c:40:_get_avg_voltage: chain = 2, voltage = 21.132408
2023-01-24 17:24:40 power_api.c:53:_get_avg_voltage: average_voltage = 21.122642
2023-01-24 17:24:40 power_api.c:71:check_voltage: target_vol = 21.00, actural_vol = 21.12, check voltage passed.
2023-01-24 17:24:40 driver-btm-api.c:1193:check_asic_number: Chain 1 only find 0 asic, will power off hash board 1
2023-01-24 17:24:41 driver-btm-api.c:1195:check_asic_number: Chain 1 voltage: an0 = 2.838710, an2 2.848387, an6 2.561290.
2023-01-24 17:24:53 driver-btm-api.c:1134:check_asic_number_with_power_on: Chain[2]: find 65 asic, times 0
2023-01-24 17:24:59 driver-hash-chip.c:266:set_uart_relay: set uart relay to 0x330003
2023-01-24 17:24:59 driver-btm-api.c:435:set_order_clock: chain[0]: set order clock, stragegy 3
2023-01-24 17:24:59 driver-btm-api.c:435:set_order_clock: chain[2]: set order clock, stragegy 3
2023-01-24 17:25:00 driver-hash-chip.c:502:set_clock_delay_control: core_data = 0x34
2023-01-24 17:25:00 driver-btm-api.c:1892:check_clock_counter: freq 50 clock_counter_limit 6
2023-01-24 17:25:00 voltage[0] = 1980
2023-01-24 17:25:00 voltage[2] = 1980
2023-01-24 17:25:00 power_api.c:226:set_working_voltage_raw: working_voltage_raw = 1980
2023-01-24 17:25:01 temperature.c:340:calibrate_temp_sensor_one_chain: chain 0 temp sensor TMP451
2023-01-24 17:25:02 temperature.c:340:calibrate_temp_sensor_one_chain: chain 2 temp sensor NCT218
2023-01-24 17:25:02 uart.c:72:set_baud: set fpga_baud to 12000000
2023-01-24 17:25:03 temperature.c:843:get_temp_info: read temp sensor failed: chain = 2, sensor = 0, chip = 14, reg = 1
2023-01-24 17:25:03 driver-btm-api.c:293:check_bringup_temp: Bring up temperature is 17
2023-01-24 17:25:03 thread.c:1378:create_check_miner_status_thread: create thread
2023-01-24 17:25:03 thread.c:1368:create_show_miner_status_thread: create thread
2023-01-24 17:25:03 thread.c:1348:create_temperature_monitor_thread: create thread
2023-01-24 17:25:03 frequency.c:514:check_bringup_temp_dec_freq: dec freq = 0 when bringup temp = 17 dec_freq_index=0
2023-01-24 17:25:03 freq_tuning.c:183:freq_tuning_get_max_freq: Max freq of tuning is 650
2023-01-24 17:25:03 driver-btm-api.c:1765:send_null_work: [DEBUG] Send null work.
2023-01-24 17:25:03 thread.c:1338:create_asic_status_monitor_thread: create thread
2023-01-24 17:25:03 frequency.c:1110:inc_freq_with_fixed_vco: chain = 255, freq = 550, is_higher_voltage = true
2023-01-24 17:25:04 temperature.c:843:get_temp_info: read temp sensor failed: chain = 2, sensor = 0, chip = 14, reg = 1

2023-01-24 17:30:35 temperature.c:843:get_temp_info: read temp sensor failed: chain = 2, sensor = 0, chip = 14, reg = 1
2023-01-24 17:30:36 driver-btm-api.c:765:set_timeout: freq = 550, percent = 90, hcn = 44236, timeout = 80
2023-01-24 17:30:36 frequency.c:1429:check_initial_temperature_status: need to set higer voltage,vol_higher:2080,vol_limit:2100
2023-01-24 17:30:36 power_api.c:232:set_higher_voltage_raw: higher_voltage_raw = 2080
2023-01-24 17:30:36 power_api.c:338:set_to_higher_voltage_by_steps: Set to voltage raw 2080, step by step.
2023-01-24 17:30:37 temperature.c:843:get_temp_info: read temp sensor failed: chain = 2, sensor = 0, chip = 14, reg = 1
2023-01-24 17:30:37 power_api.c:85:check_voltage_multi: retry time: 0
2023-01-24 17:30:39 temperature.c:843:get_temp_info: read temp sensor failed: chain = 2, sensor = 0, chip = 14, reg = 1
2023-01-24 17:30:39 power_api.c:40:_get_avg_voltage: chain = 0, voltage = 20.866499
2023-01-24 17:30:40 power_api.c:40:_get_avg_voltage: chain = 2, voltage = 20.868852
2023-01-24 17:30:40 power_api.c:53:_get_avg_voltage: average_voltage = 20.867676
2023-01-24 17:30:40 power_api.c:71:check_voltage: target_vol = 20.80, actural_vol = 20.87, check voltage passed.
2023-01-24 17:30:40 thread.c:1373:create_check_system_status_thread: create thread
2023-01-24 17:30:40 driver-btm-api.c:2618:bitmain_soc_init: Init done!
2023-01-24 17:30:40 driver-btm-api.c:222:set_miner_status: STATUS_INIT
2023-01-24 17:30:41 temperature.c:843:get_temp_info: read temp sensor failed: chain = 2, sensor = 0, chip = 14, reg = 1
2023-01-24 17:30:43 temperature.c:843:get_temp_info: read temp sensor failed: chain = 2, sensor = 0, chip = 14, reg = 1
2023-01-24 17:30:45 temperature.c:843:get_temp_info: read temp sensor failed: chain = 2, sensor = 0, chip = 14, reg = 1
2023-01-24 17:30:45 driver-btm-api.c:222:set_miner_status: STATUS_OKAY
2023-01-24 17:30:46 frequency.c:205:get_ideal_hash_rate_GH: ideal_hash_rate = 46846
2023-01-24 17:30:46 frequency.c:223:get_sale_hash_rate_GH: sale_hash_rate = 46000
2023-01-24 17:30:46 temperature.c:843:get_temp_info: read temp sensor failed: chain = 2, sensor = 0, chip = 14, reg = 1
2023-01-24 17:30:48 temperature.c:843:get_temp_info: read temp sensor failed: chain = 2, sensor = 0, chip = 14, reg = 1
2023-01-24 17:30:50 driver-btm-api.c:1496:dhash_chip_send_job: Version num 4.
2023-01-24 17:30:50 driver-btm-api.c:1644:dhash_chip_send_job: stime.tv_sec 1674581450, block_ntime 1674581449
2023-01-24 17:30:50 temperature.c:843:get_temp_info: read temp sensor failed: chain = 2, sensor = 0, chip = 14, reg = 1

2023-01-24 17:40:54 thread.c:506:check_working_voltage: current PCB min temperature is 29
2023-01-24 17:40:54 thread.c:507:check_working_voltage: current voltage is 2080, recovery to 1980
2023-01-24 17:40:54 power_api.c:310:set_to_working_voltage_by_steps: Set to voltage raw 1980, step by step.
2023-01-24 17:40:55 temperature.c:843:get_temp_info: read temp sensor failed: chain = 2, sensor = 0, chip = 14, reg = 1
2023-01-24 17:40:57 temperature.c:843:get_temp_info: read temp sensor failed: chain = 2, sensor = 0, chip = 14, reg = 1
2023-01-24 17:40:59 temperature.c:843:get_temp_info: read temp sensor failed: chain = 2, sensor = 0, chip = 14, reg = 1
2023-01-24 17:41:00 power_api.c:85:check_voltage_multi: retry time: 0
2023-01-24 17:41:01 temperature.c:843:get_temp_info: read temp sensor failed: chain = 2, sensor = 0, chip = 14, reg = 1
2023-01-24 17:41:01 power_api.c:40:_get_avg_voltage: chain = 0, voltage = 19.933250
2023-01-24 17:41:02 power_api.c:40:_get_avg_voltage: chain = 2, voltage = 19.934426
2023-01-24 17:41:02 power_api.c:53:_get_avg_voltage: average_voltage = 19.933838
2023-01-24 17:41:02 power_api.c:71:check_voltage: target_vol = 19.80, actural_vol = 19.93, check voltage passed.

2023-01-24 18:11:03 thread.c:259:calc_hashrate_avg: avg rate is 47692.29 in 40 mins
2023-01-24 18:11:03 temperature.c:516:temp_statistics_show:   pcb temp 30~40  chip temp 46~57

2023-01-24 18:41:04 thread.c:259:calc_hashrate_avg: avg rate is 47213.07 in 30 mins
2023-01-24 18:41:04 temperature.c:516:temp_statistics_show:   pcb temp 31~41  chip temp 46~59
mikeywith
legendary
Activity: 2436
Merit: 6643
be constructive or S.T.F.U
Re: S17+ Wont mine, socket failed to connect, total packet loss
January 23, 2023, 07:27:03 AM
#28
Quote from: massivegoatdynamic on January 22, 2023, 11:15:26 PM
To get the ability to adjust the voltage is it as simple as going to "more tools" and "developer tools" in Chrome to get that to pop up? Currently I only have the normal and sleep mode available.

No, it takes more than that, you need to inspect the page and change some parameters to un-hide the voltage and frequency settings, everything is explained in great detail in my topic which Bitmaxz posted the link to above, but just in case you missed the post, here is the link > https://bitcointalksearch.org/topic/antminer-s17-pro-fixed-frequency-and-voltage-default-firmware-5247179
BitMaxz
legendary
Activity: 3472
Merit: 3217
Playbet.io - Crypto Casino and Sportsbook
Re: S17+ Wont mine, socket failed to connect, total packet loss
January 23, 2023, 06:29:40 AM
#27
If my suggestion does not work I think you can try flashing it with different firmware like Braiins OS and then set up the braiins OS settings into auto-tuning and then let it run for a while.

Let's see if auto-tuning can help to fix overheating issue and post the logs here.

If it didn't solve your problem I think you can manually set chip frequency but the problem you need to find which chip is overheating so that you can reduce power and frequency on that chip.

This is just my suggestion for those who do not have technical knowledge and don't have experience in hardware repair. The solution above might be temporary but if you are looking for a permanent fix then hire a technician near your area check zeusbtc for the list of repair centers.
massivegoatdynamic
newbie
Activity: 19
Merit: 0
Re: S17+ Wont mine, socket failed to connect, total packet loss
January 22, 2023, 11:15:26 PM
#26
@ Mikewith

To get the ability to adjust the voltage is it as simple as going to "more tools" and "developer tools" in Chrome to get that to pop up? Currently I only have the normal and sleep mode available.





mikeywith
legendary
Activity: 2436
Merit: 6643
be constructive or S.T.F.U
Re: S17+ Wont mine, socket failed to connect, total packet loss
January 22, 2023, 02:57:24 PM
#25
Quote from: massivegoatdynamic on January 20, 2023, 08:28:39 PM
Which vendor do you think makes the best miner? The lady that sold me this one was trying to push me to a whatsminer but it was more expensive which is why I chose this one.

Hard to say which one makes the best, it's not just the manufacturer, they differ from one model to another, the S9s that bitmain made were tanks, S17s was trash, and the S19 series is A LOT better than the 17 series, with some people complaining about bad PSU quality, whatsminer/microbt is knowing to make robust gears in general, in my personal experience and the people I know, whatsminer beats everything else (speaking of the newer gen miners) because both Avalon and Bitmain made some exceptional tanks back in the day.

Sadly, nothing is perfect, Whatsminers require more space (can't be spaced too close to one another), and they are generally less efficient and/or more expensive, and not much firmware options unlike Bitmain.
massivegoatdynamic
newbie
Activity: 19
Merit: 0
Re: S17+ Wont mine, socket failed to connect, total packet loss
January 21, 2023, 08:19:34 PM
#24
I took out the boards today and saw that a crane fly was on board one. I am not sure if it was causing issues for the board but after removing the fly and using canned air and blew off the boards and haven't had the high temp issues and boards 1 and 3 are working. Board 2 still has the temp sensor error.

2023-01-09 14:47:13 temperature.c:843:get_temp_info: read temp sensor failed: chain = 2, sensor = 0, chip = 14, reg = 1

Any idea on the best way to tackle that?
massivegoatdynamic
newbie
Activity: 19
Merit: 0
Re: S17+ Wont mine, socket failed to connect, total packet loss
January 21, 2023, 10:17:33 AM
#23
@ Mikewith

I did try to edit the "Miner Configuration Page" of the to edit the frequency and the voltage. Is it as simple as going to "more tools" and "developer tools" in Chrome to get that to pop up? Currently I only have the normal and sleep mode available.


massivegoatdynamic
newbie
Activity: 19
Merit: 0
Re: S17+ Wont mine, socket failed to connect, total packet loss
January 20, 2023, 08:28:39 PM
#22
@ Mikeywith

Which vendor do you think makes the best miner? The lady that sold me this one was trying to push me to a whatsminer but it was more expensive which is why I chose this one.

I think my miner might have kicked the bucket. I can get it to connect for about a minute and then the hashrate drops off and that's it. Here is the latest code, I removed a good bit of it because of the file size.

Code:

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: 203432K/245760K available (6345K kernel code, 231K rwdata, 1896K rodata, 1024K init, 223K bss, 25944K 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: 12904K (cce67000 - 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: 24/12, WL threshold: 4096, image sequence number: 237714726
ubi0: available PEBs: 0, total reserved PEBs: 64, PEBs reserved for bad PEB handling: 40
ubi0: background thread "ubi_bgt0d" started, PID 708
UBIFS (ubi0:0): background thread "ubifs_bgt0_0" started, PID 711
UBIFS (ubi0:0): UBIFS: mounted UBI device 0, volume 0, name "configs"
UBIFS (ubi0:0): LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
UBIFS (ubi0:0): FS size: 1396736 bytes (1 MiB, 11 LEBs), journal size 888833 bytes (0 MiB, 5 LEBs)
UBIFS (ubi0:0): reserved for root: 65970 bytes (64 KiB)
UBIFS (ubi0:0): media format: w4/r0 (latest is w4/r0), UUID FF09433B-E002-4C29-97EC-6220DDC4BB36, small LPT model
ubi1: attaching mtd5
ubi1: scanning is finished
ubi1: attached mtd5 (name "reserve1", size 128 MiB)
ubi1: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
ubi1: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
ubi1: VID header offset: 2048 (aligned 2048), data offset: 4096
ubi1: good PEBs: 1020, bad PEBs: 4, corrupted PEBs: 0
ubi1: user volume: 1, internal volumes: 1, max. volumes count: 128
ubi1: max/mean erase counter: 4100/1015, WL threshold: 4096, image sequence number: 3265111179
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 1AF6F1E1-61F0-462C-AE44-C7D9596CF7E2, 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 = 0xb023
In fpga mem driver!
request_mem_region OK!
fpga mem virtual address is 0xd2000000
macb e000b000.ethernet eth0: link down
macb e000b000.ethernet eth0: unable to generate target frequency: 25000000 Hz
macb e000b000.ethernet eth0: link up (100/Full)
macb e000b000.ethernet eth0: link down
macb e000b000.ethernet eth0: unable to generate target frequency: 25000000 Hz
macb e000b000.ethernet eth0: link up (100/Full)
random: nonblocking pool is initialized
macb e000b000.ethernet eth0: link down
macb e000b000.ethernet eth0: unable to generate target frequency: 25000000 Hz
macb e000b000.ethernet eth0: link up (100/Full)
macb e000b000.ethernet eth0: link down
macb e000b000.ethernet eth0: unable to generate target frequency: 25000000 Hz
macb e000b000.ethernet eth0: link up (100/Full)
2023-01-20 23:56:15 driver-btm-api.c:779:init_freq_mode: This is scan-user version
2023-01-20 23:56:15 driver-btm-api.c:2451:bitmain_soc_init: opt_multi_version     = 1
2023-01-20 23:56:15 driver-btm-api.c:2452:bitmain_soc_init: opt_bitmain_ab        = 1
2023-01-20 23:56:15 driver-btm-api.c:2453:bitmain_soc_init: opt_bitmain_work_mode = 0
2023-01-20 23:56:15 driver-btm-api.c:2454:bitmain_soc_init: Miner compile time: Tue Jun  2 10:31:07 CST 2020 type: Antminer S17+
2023-01-20 23:56:15 driver-btm-api.c:2455:bitmain_soc_init: commit version: 1ca50a5 2020-06-01 18:51:22, build by: lol 2020-06-02 10:37:21
2023-01-20 23:56:15 driver-btm-api.c:2083:show_sn: len:16, 80244d0c2b104814
2023-01-20 23:56:15 driver-btm-api.c:2461:bitmain_soc_init: show sn return 1
2023-01-20 23:56:15 driver-btm-api.c:2103:handle_sn_for_factory_mode: show sn return 1
2023-01-20 23:56:15 driver-btm-api.c:2141:handle_sn_for_factory_mode: read sn success, 80244d0c2b104814
2023-01-20 23:56:15 fan.c:284:front_fan_power_on: Note: front fan is power on!
2023-01-20 23:56:15 fan.c:296:rear_fan_power_on: Note: rear fan is power on!
2023-01-20 23:56:15 driver-btm-api.c:1314:miner_device_init: Detect 256MB control board of XILINX
2023-01-20 23:56:15 driver-btm-api.c:1255:init_fan_parameter: fan_eft : 0  fan_pwm : 0
2023-01-20 23:56:21 driver-btm-api.c:1239:init_miner_version: miner ID : 80244d0c2b104814
2023-01-20 23:56:21 driver-btm-api.c:1245:init_miner_version: FPGA Version = 0xB023
2023-01-20 23:56:24 driver-btm-api.c:837:get_product_id: product_id[0] = 0
2023-01-20 23:56:24 driver-btm-api.c:837:get_product_id: product_id[1] = 0
2023-01-20 23:56:24 driver-btm-api.c:2234:update_conf_by_power_feedback: Power feedback is disabled
2023-01-20 23:56:24 driver-btm-api.c:2202:get_calibration_voltage: calibration voltage flag is error data.
2023-01-20 23:56:24 driver-btm-api.c:2268:update_conf_by_power_feedback: Note: no calibration voltage, default diff = 0
2023-01-20 23:56:24 frequency.c:1457:adjust_higer_max_vol_table: adjust_higer_max_vol_table, adjust_vol = 0
2023-01-20 23:56:24 thread.c:1363:create_read_nonce_reg_thread: create thread
2023-01-20 23:56:30 driver-btm-api.c:1239:init_miner_version: miner ID : 80244d0c2b104814
2023-01-20 23:56:30 driver-btm-api.c:1245:init_miner_version: FPGA Version = 0xB023
2023-01-20 23:56:34 driver-btm-api.c:837:get_product_id: product_id[0] = 0
2023-01-20 23:56:34 driver-btm-api.c:837:get_product_id: product_id[1] = 0
2023-01-20 23:56:34 driver-btm-api.c:792:_set_project_type: project:0
2023-01-20 23:56:34 driver-btm-api.c:813:_set_project_type: Project type: Antminer S17+
2023-01-20 23:56:34 driver-btm-api.c:824:dump_pcb_bom_version: Chain [0] PCB Version: 0x0100
2023-01-20 23:56:34 driver-btm-api.c:825:dump_pcb_bom_version: Chain [0] BOM Version: 0x0100
2023-01-20 23:56:34 driver-btm-api.c:824:dump_pcb_bom_version: Chain [1] PCB Version: 0x0100
2023-01-20 23:56:34 driver-btm-api.c:825:dump_pcb_bom_version: Chain [1] BOM Version: 0x0100
2023-01-20 23:56:38 driver-btm-api.c:2372:bitmain_board_init: Fan check passed.
2023-01-20 23:56:39 board.c:36:jump_and_app_check_restore_pic: chain[0] PIC jump to app
2023-01-20 23:56:41 board.c:40:jump_and_app_check_restore_pic: Check chain[0] PIC fw version=0x88
2023-01-20 23:56:42 board.c:36:jump_and_app_check_restore_pic: chain[1] PIC jump to app
2023-01-20 23:56:44 board.c:40:jump_and_app_check_restore_pic: Check chain[1] PIC fw version=0x88
2023-01-20 23:56:44 thread.c:1358:create_pic_heart_beat_thread: create thread
2023-01-20 23:56:44 power_api.c:213:power_init: Power init:
2023-01-20 23:56:44 power_api.c:214:power_init: current_voltage_raw = 0
2023-01-20 23:56:44 power_api.c:215:power_init: highest_voltage_raw = 2100
2023-01-20 23:56:44 power_api.c:216:power_init: working_voltage_raw = 1950
2023-01-20 23:56:44 power_api.c:217:power_init: higher_voltage_raw  = 2040
2023-01-20 23:56:44 power_api.c:218:power_init: check_asic_voltage_raw  = 2100
2023-01-20 23:56:44 driver-btm-api.c:2382:bitmain_board_init: Enter 30s sleep to make sure power release finish.
2023-01-20 23:56:44 power_api.c:186:power_off: init gpio907
2023-01-20 23:57:16 power_api.c:324:set_to_highest_voltage_by_steps: Set to voltage raw 2100, step by step.
2023-01-20 23:57:42 power_api.c:85:check_voltage_multi: retry time: 0
2023-01-20 23:57:43 power_api.c:40:_get_avg_voltage: chain = 0, voltage = 21.180327
2023-01-20 23:57:44 power_api.c:40:_get_avg_voltage: chain = 1, voltage = 21.155860
2023-01-20 23:57:44 power_api.c:53:_get_avg_voltage: average_voltage = 21.168094
2023-01-20 23:57:44 power_api.c:71:check_voltage: target_vol = 21.00, actural_vol = 21.17, check voltage passed.
2023-01-20 23:57:44 uart.c:72:set_baud: set fpga_baud to 115200
2023-01-20 23:57:55 driver-btm-api.c:1134:check_asic_number_with_power_on: Chain[0]: find 65 asic, times 0
2023-01-20 23:58:06 driver-btm-api.c:1134:check_asic_number_with_power_on: Chain[1]: find 65 asic, times 0
2023-01-20 23:58:12 driver-hash-chip.c:266:set_uart_relay: set uart relay to 0x330003
2023-01-20 23:58:12 driver-btm-api.c:435:set_order_clock: chain[0]: set order clock, stragegy 3
2023-01-20 23:58:12 driver-btm-api.c:435:set_order_clock: chain[1]: set order clock, stragegy 3
2023-01-20 23:58:12 driver-hash-chip.c:502:set_clock_delay_control: core_data = 0x34
2023-01-20 23:58:12 driver-btm-api.c:1892:check_clock_counter: freq 50 clock_counter_limit 6
2023-01-20 23:58:12 register.c:979:register_process_asic_response: Get another asic response: chain = 1, asic = 63
2023-01-20 23:58:12 register.c:979:register_process_asic_response: Get another asic response: chain = 1, asic = 63
2023-01-20 23:58:12 register.c:979:register_process_asic_response: Get another asic response: chain = 1, asic = 63
2023-01-20 23:58:13 register.c:979:register_process_asic_response: Get another asic response: chain = 1, asic = 63
2023-01-20 23:58:13 voltage[0] = 1980
2023-01-20 23:58:13 voltage[1] = 1980
2023-01-20 23:58:13 power_api.c:226:set_working_voltage_raw: working_voltage_raw = 1980
2023-01-20 23:58:14 temperature.c:340:calibrate_temp_sensor_one_chain: chain 0 temp sensor TMP451
2023-01-20 23:58:15 temperature.c:340:calibrate_temp_sensor_one_chain: chain 1 temp sensor NCT218
2023-01-20 23:58:15 uart.c:72:set_baud: set fpga_baud to 12000000
2023-01-20 23:58:16 driver-btm-api.c:293:check_bringup_temp: Bring up temperature is 17
2023-01-20 23:58:16 thread.c:1378:create_check_miner_status_thread: create thread
2023-01-20 23:58:16 thread.c:1368:create_show_miner_status_thread: create thread
2023-01-20 23:58:16 thread.c:1348:create_temperature_monitor_thread: create thread
2023-01-20 23:58:16 frequency.c:514:check_bringup_temp_dec_freq: dec freq = 0 when bringup temp = 17 dec_freq_index=0
2023-01-20 23:58:16 freq_tuning.c:183:freq_tuning_get_max_freq: Max freq of tuning is 650
2023-01-20 23:58:16 driver-btm-api.c:1765:send_null_work: [DEBUG] Send null work.
2023-01-20 23:58:16 register.c:313:get_register: !!! REG_TYPE = 1. 1049821185
2023-01-20 23:58:16 thread.c:1338:create_asic_status_monitor_thread: create thread
2023-01-20 23:58:16 frequency.c:1110:inc_freq_with_fixed_vco: chain = 255, freq = 550, is_higher_voltage = true
2023-01-21 00:03:48 driver-btm-api.c:765:set_timeout: freq = 550, percent = 90, hcn = 44236, timeout = 80
2023-01-21 00:03:48 frequency.c:1429:check_initial_temperature_status: need to set higer voltage,vol_higher:2080,vol_limit:2100
2023-01-21 00:03:48 power_api.c:232:set_higher_voltage_raw: higher_voltage_raw = 2080
2023-01-21 00:03:48 power_api.c:338:set_to_higher_voltage_by_steps: Set to voltage raw 2080, step by step.
2023-01-21 00:03:50 power_api.c:85:check_voltage_multi: retry time: 0
2023-01-21 00:03:51 power_api.c:40:_get_avg_voltage: chain = 0, voltage = 20.866499
2023-01-21 00:03:52 power_api.c:40:_get_avg_voltage: chain = 1, voltage = 20.869241
2023-01-21 00:03:52 power_api.c:53:_get_avg_voltage: average_voltage = 20.867870
2023-01-21 00:03:52 power_api.c:71:check_voltage: target_vol = 20.80, actural_vol = 20.87, check voltage passed.
2023-01-21 00:03:52 thread.c:1373:create_check_system_status_thread: create thread
2023-01-21 00:03:53 driver-btm-api.c:2618:bitmain_soc_init: Init done!
2023-01-21 00:03:53 driver-btm-api.c:222:set_miner_status: STATUS_INIT
2023-01-21 00:03:59 driver-btm-api.c:222:set_miner_status: STATUS_OKAY
2023-01-21 00:04:00 frequency.c:205:get_ideal_hash_rate_GH: ideal_hash_rate = 46846
2023-01-21 00:04:00 frequency.c:223:get_sale_hash_rate_GH: sale_hash_rate = 46000
2023-01-21 00:04:04 driver-btm-api.c:1496:dhash_chip_send_job: Version num 4.
2023-01-21 00:04:04 driver-btm-api.c:1644:dhash_chip_send_job: stime.tv_sec 1674259444, block_ntime 1674259443
2023-01-21 00:04:15 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 42, reg = 28, got chain = 6, chip = 0, reg = 28
2023-01-21 00:04:15 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 42, reg = 28, got chain = 12, chip = 0, reg = 78
2023-01-21 00:04:15 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 42, reg = 28, got chain = 9, chip = 0, reg = 78
2023-01-21 00:04:15 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 42, reg = 28, got chain = 7, chip = 1, reg = 74
2023-01-21 00:04:15 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 42, reg = 28, got chain = 6, chip = 0, reg = 82
2023-01-21 00:04:15 thread.c:1273:asic_status_monitor_thread: ERROR: chain 0 get hashrate_reg_counter 6, require 65, failed times 1: xxxxo xxxxx xxxxx xoxxx xxoxx xxxxx xoxxx xxxxx oxoxx xxxxx xxxxx xxxxx xxxxx
2023-01-21 00:04:15 thread.c:1265:asic_status_monitor_thread: ERROR: chain 1 get hashrate_reg_counter 0, require 65, failed times 1
2023-01-21 00:04:15 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 42, reg = 28, got chain = 12, chip = 1, reg = 115
2023-01-21 00:04:15 2023-01-21 00:04:15 temperature.c:843:get_temp_info: read temp sensor failed: chain = 0, sensor = 0, chip = 14, reg = 0
register.c:313:get_register: !!! REG_TYPE = 1. 549273628
2023-01-21 00:04:15 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 42, reg = 28, got chain = 8, chip = 0, reg = 36
2023-01-21 00:04:15 2023-01-21 00:04:15 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 42, reg = 28, got chain = 12, chip = 1, reg = 32
register.c:313:get_register: !!! REG_TYPE = 1. 1895845517
2023-01-21 00:04:16 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 42, reg = 28, got chain = 12, chip = 1, reg = 28
2023-01-21 00:04:16 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 42, reg = 28, got chain = 1, chip = 1, reg = 61
2023-01-21 00:04:16 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 42, reg = 28, got chain = 0, chip = 0, reg = 85
2023-01-21 00:04:16 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 42, reg = 28, got chain = 10, chip = 0, reg = 47
2023-01-21 00:04:16 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 42, reg = 28, got chain = 15, chip = 0, reg = 39
2023-01-21 00:04:16 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 42, reg = 28, got chain = 3, chip = 0, reg = 114
2023-01-21 00:04:16 2023-01-21 00:04:16 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 42, reg = 28, got chain = 2, chip = 0, reg = 41
register.c:313:get_register: !!! REG_TYPE = 1. 549273601
2023-01-21 00:04:16 temperature.c:843:get_temp_info: read temp sensor failed: chain = 0, sensor = 0, chip = 14, reg = 1
2023-01-21 00:04:16 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 30, reg = 28, got chain = 4, chip = 1, reg = 5
2023-01-21 00:04:16 2023-01-21 00:04:16 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 30, reg = 28, got chain = 9, chip = 1, reg = 0
2023-01-21 00:04:16 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 30, reg = 28, got chain = 13, chip = 0, reg = 12
2023-01-21 00:04:16 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 30, reg = 28, got chain = 7, chip = 0, reg = 51
2023-01-21 00:04:16 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 30, reg = 28, got chain = 3, chip = 0, reg = 96
2023-01-21 00:04:16 2023-01-21 00:04:16 temperature.c:843:get_temp_info: read temp sensor failed: chain = 0, sensor = 1, chip = 10, reg = 0
2023-01-21 00:04:16 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 30, reg = 28, got chain = 15, chip = 0, reg = 123
2023-01-21 00:04:16 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 30, reg = 28, got chain = 6, chip = 2, reg = 30
2023-01-21 00:04:16 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 30, reg = 28, got chain = 14, chip = 6, reg = 52
2023-01-21 00:04:16 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 30, reg = 28, got chain = 4, chip = 0, reg = 106
2023-01-21 00:04:16 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 30, reg = 28, got chain = 11, chip = 5, reg = 3
2023-01-21 00:04:16 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 30, reg = 28, got chain = 7, chip = 0, reg = 81
2023-01-21 00:04:16 temperature.c:843:get_temp_info: read temp sensor failed: chain = 0, sensor = 1, chip = 10, reg = 1
2023-01-21 00:04:17 2023-01-21 00:04:17 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 162, reg = 28, got chain = 1, chip = 1, reg = 47
2023-01-21 00:04:17 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 162, reg = 28, got chain = 13, chip = 0, reg = 79
2023-01-21 00:04:17 2023-01-21 00:04:17 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 162, reg = 28, got chain = 6, chip = 0, reg = 97
2023-01-21 00:04:17 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 162, reg = 28, got chain = 2, chip = 0, reg = 17
2023-01-21 00:04:17 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 162, reg = 28, got chain = 9, chip = 0, reg = 47
2023-01-21 00:04:17 2023-01-21 00:04:17 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 162, reg = 28, got chain = 11, chip = 0, reg = 124
register.c:313:get_register: !!! REG_TYPE = 1. 549273628
2023-01-21 00:04:17 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 162, reg = 28, got chain = 11, chip = 0, reg = 92
2023-01-21 00:04:17 temperature.c:843:get_temp_info: read temp sensor failed: chain = 0, sensor = 2, chip = 54, reg = 0
2023-01-21 00:04:17 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 162, reg = 28, got chain = 1, chip = 0, reg = 89
2023-01-21 00:04:17 thread.c:1293:asic_status_monitor_thread: chain 0 can't get enough hashrate reg val for 0 times.
2023-01-21 00:04:17 thread.c:1293:asic_status_monitor_thread: chain 1 can't get enough hashrate reg val for 0 times.
2023-01-21 00:04:17 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 162, reg = 28, got chain = 0, chip = 2, reg = 2
2023-01-21 00:04:17 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 162, reg = 28, got chain = 13, chip = 0, reg = 13
2023-01-21 00:04:17 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 162, reg = 28, got chain = 14, chip = 2, reg = 103
2023-01-21 00:04:17 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 162, reg = 28, got chain = 5, chip = 2, reg = 10
2023-01-21 00:04:17 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 162, reg = 28, got chain = 9, chip = 1, reg = 70
2023-01-21 00:04:17 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 162, reg = 28, got chain = 10, chip = 5, reg = 13
2023-01-21 00:04:17 temperature.c:843:get_temp_info: read temp sensor failed: chain = 0, sensor = 2, chip = 54, reg = 1
2023-01-21 00:04:17 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 150, reg = 28, got chain = 12, chip = 2, reg = 120
2023-01-21 00:04:17 thread.c:1273:asic_status_monitor_thread: ERROR: chain 0 get hashrate_reg_counter 3, require 65, failed times 1: xxxxx xxxxx xxxxx xxxxx oxxxx xoxxx xxxxx xxxxx xxxxx xxxxx xxxxx xoxxx xxxxx
2023-01-21 00:04:17 thread.c:1273:asic_status_monitor_thread: ERROR: chain 1 get hashrate_reg_counter 2, require 65, failed times 1: xxxxx xxxxx xxxxx xxxxx xxxxx xxxxx xxxxx xxxxx xxxxx xxxxx xxoxx xoxxx xxxxx
2023-01-21 00:04:17 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 150, reg = 28, got chain = 1, chip = 0, reg = 2
2023-01-21 00:04:17 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 150, reg = 28, got chain = 14, chip = 0, reg = 32
2023-01-21 00:04:17 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 150, reg = 28, got chain = 6, chip = 1, reg = 13
2023-01-21 00:04:17 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 150, reg = 28, got chain = 9, chip = 0, reg = 53
2023-01-21 00:04:17 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 150, reg = 28, got chain = 7, chip = 1, reg = 47
2023-01-21 00:04:17 2023-01-21 00:04:17 temperature.c:843:get_temp_info: read temp sensor failed: chain = 0, sensor = 3, chip = 50, reg = 0
2023-01-21 00:04:17 2023-01-21 00:04:17 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 150, reg = 28, got chain = 10, chip = 0, reg = 69
2023-01-21 00:04:17 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 150, reg = 28, got chain = 5, chip = 0, reg = 11
2023-01-21 00:04:17 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 150, reg = 28, got chain = 5, chip = 0, reg = 88
2023-01-21 00:04:18 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 150, reg = 28, got chain = 10, chip = 1, reg = 68
2023-01-21 00:04:18 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 150, reg = 28, got chain = 0, chip = 0, reg = 0
2023-01-21 00:04:18 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 150, reg = 28, got chain = 8, chip = 0, reg = 41
2023-01-21 00:04:18 register.c:313:get_register: !!! REG_TYPE = 1. 822098049
2023-01-21 00:04:18 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 150, reg = 28, got chain = 5, chip = 0, reg = 21
2023-01-21 00:04:18 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 150, reg = 28, got chain = 1, chip = 3, reg = 80
2023-01-21 00:04:18 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 150, reg = 28, got chain = 13, chip = 1, reg = 104
2023-01-21 00:04:18 temperature.c:843:get_temp_info: read temp sensor failed: chain = 0, sensor = 3, chip = 50, reg = 1
2023-01-21 00:04:18 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 1, chip = 42, reg = 28, got chain = 8, chip = 1, reg = 82
2023-01-21 00:04:18 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 1, chip = 42, reg = 28, got chain = 10, chip = 0, reg = 95
2023-01-21 00:04:18 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 1, chip = 42, reg = 28, got chain = 12, chip = 1, reg = 109
2023-01-21 00:04:18 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 1, chip = 42, reg = 28, got chain = 3, chip = 1, reg = 26
2023-01-21 00:04:18 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 1, chip = 42, reg = 28, got chain = 13, chip = 0, reg = 48
2023-01-21 00:04:18 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 1, chip = 42, reg = 28, got chain = 1, chip = 1, reg = 72
2023-01-21 00:04:18 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 1, chip = 42, reg = 28, got chain = 3, chip = 0, reg = 27
2023-01-21 00:04:18 temperature.c:843:get_temp_info: read temp sensor failed: chain = 1, sensor = 0, chip = 14, reg = 0
2023-01-21 00:04:18 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 1, chip = 42, reg = 28, got chain = 11, chip = 1, reg = 13
2023-01-21 00:04:18 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 1, chip = 42, reg = 28, got chain = 3, chip = 0, reg = 124
2023-01-21 00:04:18 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 1, chip = 42, reg = 28, got chain = 10, chip = 0, reg = 69
2023-01-21 00:04:18 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 1, chip = 42, reg = 28, got chain = 2, chip = 0, reg = 39
2023-01-21 00:04:18 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 1, chip = 42, reg = 28, got chain = 8, chip = 2, reg = 36
2023-01-21 00:04:18 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 1, chip = 42, reg = 28, got chain = 4, chip = 3, reg = 68
2023-01-21 00:04:18 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 1, chip = 42, reg = 28, got chain = 5, chip = 0, reg = 71
2023-01-21 00:04:18 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 1, chip = 42, reg = 28, got chain = 3, chip = 0, reg = 118
2023-01-21 00:04:19 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 1, chip = 42, reg = 28, got chain = 11, chip = 3, reg = 82
2023-01-21 00:04:19 temperature.c:843:get_temp_info: read temp sensor failed: chain = 1, sensor = 0, chip = 14, reg = 1
2023-01-21 00:04:19 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 1, chip = 30, reg = 28, got chain = 11, chip = 1, reg = 58
2023-01-21 00:04:19 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 1, chip = 30, reg = 28, got chain = 11, chip = 0, reg = 96
2023-01-21 00:04:19 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 1, chip = 30, reg = 28, got chain = 8, chip = 4, reg = 8
2023-01-21 00:04:19 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 1, chip = 30, reg = 28, got chain = 0, chip = 0, reg = 76
2023-01-21 00:04:19 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 1, chip = 30, reg = 28, got chain = 0, chip = 2, reg = 113
2023-01-21 00:04:19 2023-01-21 00:04:19 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 1, chip = 30, reg = 28, got chain = 13, chip = 0, reg = 3
2023-01-21 00:04:19 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 1, chip = 30, reg = 28, got chain = 15, chip = 2, reg = 66
register.c:313:get_register: !!! REG_TYPE = 1. 549273628
2023-01-21 00:04:19 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 1, chip = 30, reg = 28, got chain = 2, chip = 2, reg = 71
2023-01-21 00:04:19 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 1, chip = 30, reg = 28, got chain = 7, chip = 0, reg = 98
2023-01-21 00:04:19 thread.c:1293:asic_status_monitor_thread: chain 0 can't get enough hashrate reg val for 1 times.
2023-01-21 00:04:19 thread.c:1293:asic_status_monitor_thread: chain 1 can't get enough hashrate reg val for 1 times.
2023-01-21 00:04:19 temperature.c:843:get_temp_info: read temp sensor failed: chain = 1, sensor = 1, chip = 10, reg = 0
2023-01-21 00:04:19 register.c:313:get_register: !!! REG_TYPE = 1. 1369768982
2023-01-21 00:04:19 register.c:313:get_register: !!! REG_TYPE = 1. 2007499785
2023-01-21 00:04:19 register.c:227:get_nonce: !!! nonce invalid
2023-01-21 00:04:19 register.c:313:get_register: !!! REG_TYPE = 1. 732824591
2023-01-21 00:04:19 register.c:227:get_nonce: !!! nonce invalid
2023-01-21 00:04:19 register.c:227:get_nonce: !!! nonce invalid
2023-01-21 00:04:19 register.c:227:get_nonce: !!! nonce invalid
2023-01-21 00:04:19 register.c:313:get_register: !!! REG_TYPE = 1. 1371145218
2023-01-21 00:04:19 register.c:227:get_nonce: !!! nonce invalid
2023-01-21 00:04:19 register.c:227:get_nonce: !!! nonce invalid
2023-01-21 00:04:19 register.c:313:get_register: !!! REG_TYPE = 1. 1897798681
2023-01-21 00:04:19 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 1, chip = 30, reg = 28, got chain = 13, chip = 4, reg = 29
2023-01-21 00:04:19 register.c:313:get_register: !!! REG_TYPE = 1. 1438254106
2023-01-21 00:04:19 register.c:227:get_nonce: !!! nonce invalid
2023-01-21 00:04:19 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 1, chip = 30, reg = 28, got chain = 13, chip = 1, reg = 38
2023-01-21 00:04:19 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 1, chip = 30, reg = 28, got chain = 12, chip = 0, reg = 100
2023-01-21 00:04:19 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 1, chip = 30, reg = 28, got chain = 0, chip = 1, reg = 17
2023-01-21 00:04:19 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 1, chip = 30, reg = 28, got chain = 7, chip = 0, reg = 55
2023-01-21 00:04:19 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 1, chip = 30, reg = 28, got chain = 0, chip = 1, reg = 120
2023-01-21 00:04:19 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 1, chip = 30, reg = 28, got chain = 9, chip = 1, reg = 60
2023-01-21 00:04:19 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 1, chip = 30, reg = 28, got chain = 15, chip = 0, reg = 120
2023-01-21 00:04:19 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 1, chip = 30, reg = 28, got chain = 0, chip = 1, reg = 38
2023-01-21 00:04:19 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 1, chip = 30, reg = 28, got chain = 12, chip = 2, reg = 37
2023-01-21 00:04:19 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 1, chip = 30, reg = 28, got chain = 14, chip = 0, reg = 123
2023-01-21 00:04:19 temperature.c:843:get_temp_info: read temp sensor failed: chain = 1, sensor = 1, chip = 10, reg = 1
2023-01-21 00:04:19 2023-01-21 00:04:19 thread.c:1273:asic_status_monitor_thread: ERROR: chain 0 get hashrate_reg_counter 3, require 65, failed times 1: xxxxx xoxxx xxxxx xxxxx oxxxx xxxxx xxxxx xxxxx xxxxx xxxox xxxxx xxxxx xxxxx
2023-01-21 00:04:19 thread.c:1273:asic_status_monitor_thread: ERROR: chain 1 get hashrate_reg_counter 3, require 65, failed times 1: xxxxx xxxxx xxxxx xxxxx xooxx xxxxx xxxxx xxxxx oxxxx xxxxx xxxxx xxxxx xxxxx
register.c:313:get_register: !!! REG_TYPE = 1. 549273628
2023-01-21 00:04:19 register.c:313:get_register: !!! REG_TYPE = 1. 1241529474
2023-01-21 00:04:19 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 1, chip = 162, reg = 28, got chain = 14, chip = 0, reg = 51
2023-01-21 00:04:19 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 1, chip = 162, reg = 28, got chain = 3, chip = 0, reg = 42
2023-01-21 00:04:19 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 1, chip = 162, reg = 28, got chain = 13, chip = 0, reg = 101
2023-01-21 00:04:19 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 1, chip = 162, reg = 28, got chain = 0, chip = 0, reg = 78
2023-01-21 00:04:19 2023-01-21 00:04:19 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 1, chip = 162, reg = 28, got chain = 6, chip = 1, reg = 89
register.c:313:get_register: !!! REG_TYPE = 1. 549273601
2023-01-21 00:04:19 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 1, chip = 162, reg = 28, got chain = 1, chip = 1, reg = 68
2023-01-21 00:04:20 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 1, chip = 162, reg = 28, got chain = 1, chip = 1, reg = 58
2023-01-21 00:04:20 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 1, chip = 162, reg = 28, got chain = 6, chip = 0, reg = 92
2023-01-21 00:04:20 temperature.c:843:get_temp_info: read temp sensor failed: chain = 1, sensor = 2, chip = 54, reg = 0
2023-01-21 00:04:20 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 1, chip = 162, reg = 28, got chain = 5, chip = 0, reg = 50
2023-01-21 00:04:20 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 1, chip = 162, reg = 28, got chain = 6, chip = 1, reg = 53
2023-01-21 00:04:20 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 1, chip = 162, reg = 28, got chain = 9, chip = 0, reg = 31
2023-01-21 00:04:20 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 1, chip = 162, reg = 28, got chain = 11, chip = 0, reg = 105
2023-01-21 00:04:20 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 1, chip = 162, reg = 28, got chain = 15, chip = 0, reg = 92
2023-01-21 00:04:20 2023-01-21 00:04:20 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 1, chip = 162, reg = 28, got chain = 8, chip = 0, reg = 49
2023-01-21 00:04:20 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 1, chip = 162, reg = 28, got chain = 13, chip = 6, reg = 62
2023-01-21 00:04:20 temperature.c:843:get_temp_info: read temp sensor failed: chain = 1, sensor = 2, chip = 54, reg = 1
2023-01-21 00:04:20 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 1, chip = 150, reg = 28, got chain = 4, chip = 1, reg = 11
2023-01-21 00:04:20 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 1, chip = 150, reg = 28, got chain = 13, chip = 0, reg = 74
2023-01-21 00:04:20 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 1, chip = 150, reg = 28, got chain = 0, chip = 3, reg = 87
2023-01-21 00:04:20 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 1, chip = 150, reg = 28, got chain = 10, chip = 0, reg = 115
2023-01-21 00:04:20 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 1, chip = 150, reg = 28, got chain = 12, chip = 2, reg = 7
2023-01-21 00:04:20 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 1, chip = 150, reg = 28, got chain = 8, chip = 1, reg = 101
2023-01-21 00:04:20 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 1, chip = 150, reg = 28, got chain = 5, chip = 0, reg = 10
2023-01-21 00:04:20 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 1, chip = 150, reg = 28, got chain = 4, chip = 0, reg = 108
2023-01-21 00:04:20 temperature.c:843:get_temp_info: read temp sensor failed: chain = 1, sensor = 3, chip = 50, reg = 0
2023-01-21 00:04:20 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 1, chip = 150, reg = 28, got chain = 15, chip = 5, reg = 16
2023-01-21 00:04:20 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 1, chip = 150, reg = 28, got chain = 10, chip = 0, reg = 117
2023-01-21 00:04:20 2023-01-21 00:04:20 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 1, chip = 150, reg = 28, got chain = 13, chip = 0, reg = 51
register.c:313:get_register: !!! REG_TYPE = 1. 549273616
2023-01-21 00:04:21 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 1, chip = 150, reg = 28, got chain = 11, chip = 0, reg = 10
2023-01-21 00:04:21 2023-01-21 00:04:21 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 1, chip = 150, reg = 28, got chain = 3, chip = 0, reg = 16
2023-01-21 00:04:21 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 1, chip = 150, reg = 28, got chain = 13, chip = 0, reg = 69
register.c:313:get_register: !!! REG_TYPE = 1. 549273628
2023-01-21 00:04:21 temperature.c:843:get_temp_info: read temp sensor failed: chain = 1, sensor = 3, chip = 50, reg = 1
2023-01-21 00:04:21 temperature.c:875:get_temp_info: ERROR: chain 0 can get NONE temp info or temp value abnormal, power it off
2023-01-21 00:04:21 thread.c:1293:asic_status_monitor_thread: chain 0 can't get enough hashrate reg val for 2 times.
2023-01-21 00:04:21 thread.c:1293:asic_status_monitor_thread: chain 1 can't get enough hashrate reg val for 2 times.
2023-01-21 00:04:21 register.c:313:get_register: !!! REG_TYPE = 1. 549273601
2023-01-21 00:04:21 thread.c:1273:asic_status_monitor_thread: ERROR: chain 0 get hashrate_reg_counter 2, require 65, failed times 1: xxxxx xxoxx xxxxx xxxxx xxxxx xxxxx xxxxx xxxxx xxxxx xxxxx xxxxx xxxxo xxxxx
2023-01-21 00:04:21 thread.c:1273:asic_status_monitor_thread: ERROR: chain 1 get hashrate_reg_counter 2, require 65, failed times 1: xxxxx xxxxx xxxxx xxxxx xxxxx xxxxx xxxxx xxxxx xxxxx xxxox xxxxx xxxxx xoxxx
2023-01-21 00:04:22 temperature.c:875:get_temp_info: ERROR: chain 1 can get NONE temp info or temp value abnormal, power it off 
2023-01-21 00:04:23 frequency.c:205:get_ideal_hash_rate_GH: ideal_hash_rate = 23423
2023-01-21 00:04:23 frequency.c:223:get_sale_hash_rate_GH: sale_hash_rate = 22000
2023-01-21 00:04:23 thread.c:1293:asic_status_monitor_thread: chain 1 can't get enough hashrate reg val for 3 times.
2023-01-21 00:04:23 driver-btm-api.c:222:set_miner_status: ERROR_TEMP_LOST
2023-01-21 00:04:23 driver-btm-api.c:156:stop_mining: stop mining: no chain exists, maybe caused by sensor lost
2023-01-21 00:04:23 thread.c:1419:cancel_check_miner_status_thread: cancel thread
2023-01-21 00:04:23 thread.c:1414:cancel_check_system_status_thread: cancel thread
2023-01-21 00:04:23 thread.c:1403:cancel_read_nonce_reg_thread: cancel thread
2023-01-21 00:04:23 thread.c:1343:cancel_asic_status_monitor_thread: cancel thread
2023-01-21 00:04:23 driver-btm-api.c:141:killall_hashboard: ****power off hashboard****
mikeywith
legendary
Activity: 2436
Merit: 6643
be constructive or S.T.F.U
Re: S17+ Wont mine, socket failed to connect, total packet loss
January 20, 2023, 06:11:13 PM
#21
Quote from: massivegoatdynamic on January 20, 2023, 03:21:09 PM
@ Mikeywith

This one is different in that each board has the monolithic heat sink. Each board only has chips on one side right?

I would think that the solder issue should be less since the chip side has a different heat sink. The backside still has the old style. I would post a picture of my boards but don't know how.  

I know what the modified hashboard looks like, it is just a marketing stuff.

Most folks think the issu is in the solder between hearsinks and chips, so someone made a large heatsink that sticks better than the average one, with screws on it, like the Avalons and the newer Antminer versions, and started selling them as (modifed version which fixed the factory issues).

Of course none of that  is correct, the chip <> heatsink solder probably makes less than 5% of the issue, the 95% lies between the chip and the board/pcb, the new heatsink does NOT fix that, however, to be fair, it makes fixing the boards easier since removing one large heatsink to fix the board is a lot easier than removing a dozen, aside from that, it is just the same.
massivegoatdynamic
newbie
Activity: 19
Merit: 0
Re: S17+ Wont mine, socket failed to connect, total packet loss
January 20, 2023, 03:21:09 PM
#20
@ Mikeywith

This one is different in that each board has the monolithic heat sink. Each board only has chips on one side right?

I would think that the solder issue should be less since the chip side has a different heat sink. The backside still has the old style. I would post a picture of my boards but don't know how. 
mikeywith
legendary
Activity: 2436
Merit: 6643
be constructive or S.T.F.U
Re: S17+ Wont mine, socket failed to connect, total packet loss
January 20, 2023, 03:14:59 PM
#19
The 17 series is the worst thing made by mankind, there is nothing much you can do to make them survive longer, the main issue is in the solder quality between the chips and the board itself, running them cooler delays the issues from happening and that is it.
massivegoatdynamic
newbie
Activity: 19
Merit: 0
Re: S17+ Wont mine, socket failed to connect, total packet loss
January 20, 2023, 01:46:52 PM
#18
@ BitMaxz

Room temp was 55 (this is out in the barn for now) and I have the miner hooked up to a 10" ducted fan that can move a lot of air. I would post a picture of the setup but I don't know how. Do you have to post pictures to another site and then link it here?

I looked into to the post of mikeywith but I did not see that on mine. I have an S17+ if that makes a difference. I am guessing you went to "more tools" and "developer tools" to get that to pop up? Currently I only have the normal and sleep mode available.

Side note, when I turn on the miner I got a voltage of 20 volts across the buss bars going to the hashboards. I let it run and it connected again today but you see the hashrate slowly dropping off. Once I saw the 127 C chip temp I went back to measure the voltage and it was reading 0 volts.

So at least when you first turn on the power supply it appears to be working, but could the voltage dropping off be from the miner telling it to dial back the frequency/Voltage?

@ Mikeywith

Agreed that it is almost not worth it to fix at current prices. I got this miner to learn the ropes and see what you can do with them. Seems like a bought a lemon or just a really finicky miner. I eventually would like to have several miners and was hoping to get into immersion cooling them and trying to power them with solar. I was planning on messing with overclocking but now it seems you may want to baby these things to make them last longer.
mikeywith
legendary
Activity: 2436
Merit: 6643
be constructive or S.T.F.U
Re: S17+ Wont mine, socket failed to connect, total packet loss
January 20, 2023, 08:49:37 AM
#17
Quote from: massivegoatdynamic on January 19, 2023, 08:59:48 PM
I may consider taking you up with telegram (which I don't have yet) and anydesk. I am scared of stranger danger though...

The fact that you got to connect to the pool even for a while eliminates the network related issues, which means you no longer need my help in network diagnoisis, your issue is now hardware related and I am not the best person for that.

One thing I know is that if all temp sensors are acting weird it usually means a bad PSU, so you might need to replace the PSU, if it turns out to be actually sensor issues, it will require a pro to fix it, not something the average person can do, there is a pinned thread in this sections that is dedicated to repair services which you can check.

Although with all honesty, that gear is worth less than 300$ fully working with no issues, fixing it will cost probably 100-200$, with shipping and all that you may go past the 300$.
BitMaxz
legendary
Activity: 3472
Merit: 3217
Playbet.io - Crypto Casino and Sportsbook
Re: S17+ Wont mine, socket failed to connect, total packet loss
January 20, 2023, 07:32:26 AM
#16
Quote from: massivegoatdynamic on January 19, 2023, 09:46:29 PM
After messing around with it, all chips and all PCB's are registering super high temps even though its pretty chilly at the moment. Looking at some earlier posts if all boards and chips are registering high temps that means the power supply has crapped out?

No usually high chip temps sometimes it is due to loose heatsinks or no proper ventilation. Do you mind telling us what exactly your room temp is?
You can try to run the miner with low power mode let's see if it can help to drop the chip temps.

There is other thing that I would like you to try there and maybe this unit also has hidden settings where you can able to adjust frequency and voltages.
Check the Mikeywith guide here https://bitcointalksearch.org/topic/antminer-s17-pro-fixed-frequency-and-voltage-default-firmware-5247179
And then set the voltage/frequency to the lowest and gradually increase it depending on the chip temps until you find the right spot.
massivegoatdynamic
newbie
Activity: 19
Merit: 0
Re: S17+ Wont mine, socket failed to connect, total packet loss
January 19, 2023, 09:46:29 PM
#15
After messing around with it, all chips and all PCB's are registering super high temps even though its pretty chilly at the moment. Looking at some earlier posts if all boards and chips are registering high temps that means the power supply has crapped out?
massivegoatdynamic
newbie
Activity: 19
Merit: 0
Re: S17+ Wont mine, socket failed to connect, total packet loss
January 19, 2023, 08:59:48 PM
#14
Mikey I think you are right. I finally managed to connect to a mining pool and am finally earning negative money but it is neat to say I have mined. My miner's has rate dropped off and when i went to go check the miner it had disconnected and was reporting chip temps on 127°C even though I am pumping a ton of air through it and previously the chips were setting at 55°C.

I looked at your earlier post referenced by zeus and it seems I have to do the same thing (Step 1. Reboot miner, Step 2. In my case hit the IPS report, Step 3. Un-plug and plug in the network cable) and it seems to come back to life. I am guessing when the miner senses high temps it is trying to save it self by shutting down.

The good and bad is that the side that the chips are mounted on are covered with a monolithic heat sink so I have to remove that to test the chips. I had gently tried to do it after removing the screws and I am guessing they used the thermal glue? Any idea how to remove the heat sink to get to the chips?

Do you know if the thermal paste/glue is typically non-electrically conductive? I have dreams of eventually trying to immersion cool these things and I am wondering if the dielectric would dissolve the paste/glue and then you would have bits of conductive stuff floating in the fluid.

I may consider taking you up with telegram (which I don't have yet) and anydesk. I am scared of stranger danger though...

BitMaxz
legendary
Activity: 3472
Merit: 3217
Playbet.io - Crypto Casino and Sportsbook
Re: S17+ Wont mine, socket failed to connect, total packet loss
January 19, 2023, 06:59:50 PM
#13
Quote from: mikeywith on January 17, 2023, 02:57:51 PM

What guide? nobody wrote a better guide on the 17 series temp sensor than mine  Cheesy, jokes aside, I just noticed they used my guide in their post, and to be honest most of the knowledge I acquired regarding the 17 series when dozen of issues were coming my way when I bought those piece of shit gears actually came from ZeusBTC, they were probably the only reliable source of information, I "mined" the info they had online, got in direct touch with the founder whom I had a good relationship with, they never failed to provide me with the info I needed, add to that my awful experience with those gears which made me eager to learn about them, so ya I might have summed up the issue better, but ZeusBTC still remains the source of the most of that knowledge (gotta give credit where credit is due).

I'm thinking about this account ZeusBtc.com registered this month they can make a guide and point people to their own guide but this one is not.
What I think is that he might be pretending as Zeusbtc and grow up using that name without real Zeusbtc knowing that someone uses their name here on the forum.
Like last year someone pretending to be Electrum support but the real purpose they use that name to scam people.
mikeywith
legendary
Activity: 2436
Merit: 6643
be constructive or S.T.F.U
Re: S17+ Wont mine, socket failed to connect, total packet loss
January 17, 2023, 11:22:31 PM
#12
You do have an issue with temp sensor but has nothing to do with ping/diagnostics , send me your telegram id in PM, let us arrange for anydesk session so I can help troubleshoot this faster if you want. (For free of course).

Not being able to ping suggests a network-related issue, probably something wrong with the DNS settings, or maybe your firewall, could be one of a few things, there are a few things that I can trouble shoot in 15 mins if I have access to the miner, whereby I'll need double or triple the time explaining it and then probably even more time on your side to perform them, so if anydesk is not an option, please just start by checking your DNS.
massivegoatdynamic
newbie
Activity: 19
Merit: 0
Re: S17+ Wont mine, socket failed to connect, total packet loss
January 17, 2023, 08:58:20 PM
#11
Quote from: mikeywith on January 17, 2023, 02:57:51 PM
Quote from: BitMaxz on January 11, 2023, 11:40:59 AM
Oh wow, zeusbtc has a new account here but it's weird he is promoting a different link instead of their own guide.

What guide? nobody wrote a better guide on the 17 series temp sensor than mine  Cheesy, jokes aside, I just noticed they used my guide in their post, and to be honest most of the knowledge I acquired regarding the 17 series when dozen of issues were coming my way when I bought those piece of shit gears actually came from ZeusBTC, they were probably the only reliable source of information, I "mined" the info they had online, got in direct touch with the founder whom I had a good relationship with, they never failed to provide me with the info I needed, add to that my awful experience with those gears which made me eager to learn about them, so ya I might have summed up the issue better, but ZeusBTC still remains the source of the most of that knowledge (gotta give credit where credit is due).

MikeyWith, could you point me to your "guide" on the matter? I am guessing I either need to pick up one of these testers:

https://www.zeusbtc.com/ASIC-Miner-Repair/Parts-Tools-Details.asp?ID=1467

Or

https://tester.asic.repair/en

Did you have a chance to look at my logs to see if it was something obvious? Also, since I have a monolithic heatsink on the S17 are those best removed by putting the entire thing in an oven and if so what temp? All of the videos I have seen so far deal with individual heat sinks. On my most recent test I got rid of the stock fans and used a monster fan to push air through so that it will run cooler. Mission accomplished on that front however the miner still wasn't working. I never been able to connect to my mining pool, always fail the ping diagnostic test and get the "socked failed to connect" message.

mikeywith
legendary
Activity: 2436
Merit: 6643
be constructive or S.T.F.U
Re: S17+ Wont mine, socket failed to connect, total packet loss
January 17, 2023, 02:57:51 PM
#10
Quote from: BitMaxz on January 11, 2023, 11:40:59 AM
Oh wow, zeusbtc has a new account here but it's weird he is promoting a different link instead of their own guide.

What guide? nobody wrote a better guide on the 17 series temp sensor than mine  Cheesy, jokes aside, I just noticed they used my guide in their post, and to be honest most of the knowledge I acquired regarding the 17 series when dozen of issues were coming my way when I bought those piece of shit gears actually came from ZeusBTC, they were probably the only reliable source of information, I "mined" the info they had online, got in direct touch with the founder whom I had a good relationship with, they never failed to provide me with the info I needed, add to that my awful experience with those gears which made me eager to learn about them, so ya I might have summed up the issue better, but ZeusBTC still remains the source of the most of that knowledge (gotta give credit where credit is due).
massivegoatdynamic
newbie
Activity: 19
Merit: 0
Re: S17+ Wont mine, socket failed to connect, total packet loss
January 16, 2023, 10:26:16 PM
#9
I did not know that inserting code was a feature, thank you.

I did unplug board 3 and 1 and managed to get board 2 to run but it eventually stopped (was only running at 11000 GH/S). I think unplugged board 2 and got board 1 to run for a bit (was running at 23,600 GH/S) but I still get the "socket connect failed: connection refused". It seems random, if I reset on the miner and then hit the IP report occasionally you can connect to the miner but it has always failed the "ping" diagnostic in network.

I also hooked up a monster fan and used spoofers on this latest test. The board and chips were running cooler but maybe some chips aren't working. While running one board the highest temp the chip saw was 50°C, max PCB temp was 36°C. Maybe the damage was done the first time I ever turned it on. Before running my monster fan setup my chip temps were up to 77°C.

The heat sinks all felt good, nothing was loose. That being said I think on the chip side it uses the mono-lithic type heat sinks that are held in place with screws. Not sure if there is poor contact or not. I can say for a used machine it at least looks like its in pretty good shape. The attached Kernel log was with just board 2 hooked up.

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: 203432K/245760K available (6345K kernel code, 231K rwdata, 1896K rodata, 1024K init, 223K bss, 25944K 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: 12904K (cce67000 - 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: 23/11, WL threshold: 4096, image sequence number: 237714726
ubi0: available PEBs: 0, total reserved PEBs: 64, PEBs reserved for bad PEB handling: 40
ubi0: background thread "ubi_bgt0d" started, PID 708
UBIFS (ubi0:0): background thread "ubifs_bgt0_0" started, PID 711
UBIFS (ubi0:0): UBIFS: mounted UBI device 0, volume 0, name "configs"
UBIFS (ubi0:0): LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
UBIFS (ubi0:0): FS size: 1396736 bytes (1 MiB, 11 LEBs), journal size 888833 bytes (0 MiB, 5 LEBs)
UBIFS (ubi0:0): reserved for root: 65970 bytes (64 KiB)
UBIFS (ubi0:0): media format: w4/r0 (latest is w4/r0), UUID FF09433B-E002-4C29-97EC-6220DDC4BB36, small LPT model
ubi1: attaching mtd5
ubi1: scanning is finished
ubi1: attached mtd5 (name "reserve1", size 128 MiB)
ubi1: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
ubi1: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
ubi1: VID header offset: 2048 (aligned 2048), data offset: 4096
ubi1: good PEBs: 1020, bad PEBs: 4, corrupted PEBs: 0
ubi1: user volume: 1, internal volumes: 1, max. volumes count: 128
ubi1: max/mean erase counter: 4099/1014, WL threshold: 4096, image sequence number: 3265111179
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 1AF6F1E1-61F0-462C-AE44-C7D9596CF7E2, 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 = 0xb023
In fpga mem driver!
request_mem_region OK!
fpga mem virtual address is 0xd2000000
random: nonblocking pool is initialized
2023-01-17 02:02:25 driver-btm-api.c:779:init_freq_mode: This is scan-user version
2023-01-17 02:02:25 driver-btm-api.c:2451:bitmain_soc_init: opt_multi_version     = 1
2023-01-17 02:02:25 driver-btm-api.c:2452:bitmain_soc_init: opt_bitmain_ab        = 1
2023-01-17 02:02:25 driver-btm-api.c:2453:bitmain_soc_init: opt_bitmain_work_mode = 0
2023-01-17 02:02:25 driver-btm-api.c:2454:bitmain_soc_init: Miner compile time: Tue Jun  2 10:31:07 CST 2020 type: Antminer S17+
2023-01-17 02:02:25 driver-btm-api.c:2455:bitmain_soc_init: commit version: 1ca50a5 2020-06-01 18:51:22, build by: lol 2020-06-02 10:37:21
2023-01-17 02:02:25 driver-btm-api.c:2083:show_sn: len:16, 80244d0c2b104814
2023-01-17 02:02:25 driver-btm-api.c:2461:bitmain_soc_init: show sn return 1
2023-01-17 02:02:25 driver-btm-api.c:2103:handle_sn_for_factory_mode: show sn return 1
2023-01-17 02:02:25 driver-btm-api.c:2141:handle_sn_for_factory_mode: read sn success, 80244d0c2b104814
2023-01-17 02:02:25 fan.c:284:front_fan_power_on: Note: front fan is power on!
2023-01-17 02:02:25 fan.c:296:rear_fan_power_on: Note: rear fan is power on!
2023-01-17 02:02:25 driver-btm-api.c:1314:miner_device_init: Detect 256MB control board of XILINX
2023-01-17 02:02:25 driver-btm-api.c:1255:init_fan_parameter: fan_eft : 0  fan_pwm : 0
2023-01-17 02:02:31 driver-btm-api.c:1239:init_miner_version: miner ID : 80244d0c2b104814
2023-01-17 02:02:31 driver-btm-api.c:1245:init_miner_version: FPGA Version = 0xB023
2023-01-17 02:02:33 driver-btm-api.c:837:get_product_id: product_id[1] = 0
2023-01-17 02:02:33 driver-btm-api.c:2234:update_conf_by_power_feedback: Power feedback is disabled
2023-01-17 02:02:33 driver-btm-api.c:2202:get_calibration_voltage: calibration voltage flag is error data.
2023-01-17 02:02:33 driver-btm-api.c:2268:update_conf_by_power_feedback: Note: no calibration voltage, default diff = 0
2023-01-17 02:02:33 frequency.c:1457:adjust_higer_max_vol_table: adjust_higer_max_vol_table, adjust_vol = 0
2023-01-17 02:02:33 thread.c:1363:create_read_nonce_reg_thread: create thread
2023-01-17 02:02:39 driver-btm-api.c:1239:init_miner_version: miner ID : 80244d0c2b104814
2023-01-17 02:02:39 driver-btm-api.c:1245:init_miner_version: FPGA Version = 0xB023
2023-01-17 02:02:41 driver-btm-api.c:837:get_product_id: product_id[1] = 0
2023-01-17 02:02:41 driver-btm-api.c:792:_set_project_type: project:0
2023-01-17 02:02:41 driver-btm-api.c:813:_set_project_type: Project type: Antminer S17+
2023-01-17 02:02:41 driver-btm-api.c:824:dump_pcb_bom_version: Chain [1] PCB Version: 0x0100
2023-01-17 02:02:41 driver-btm-api.c:825:dump_pcb_bom_version: Chain [1] BOM Version: 0x0100
2023-01-17 02:02:45 driver-btm-api.c:2372:bitmain_board_init: Fan check passed.
2023-01-17 02:02:46 board.c:36:jump_and_app_check_restore_pic: chain[1] PIC jump to app
2023-01-17 02:02:48 board.c:40:jump_and_app_check_restore_pic: Check chain[1] PIC fw version=0x88
2023-01-17 02:02:48 thread.c:1358:create_pic_heart_beat_thread: create thread
2023-01-17 02:02:48 power_api.c:213:power_init: Power init:
2023-01-17 02:02:48 power_api.c:214:power_init: current_voltage_raw = 0
2023-01-17 02:02:48 power_api.c:215:power_init: highest_voltage_raw = 2100
2023-01-17 02:02:48 power_api.c:216:power_init: working_voltage_raw = 1950
2023-01-17 02:02:48 power_api.c:217:power_init: higher_voltage_raw  = 2040
2023-01-17 02:02:48 power_api.c:218:power_init: check_asic_voltage_raw  = 2100
2023-01-17 02:02:48 driver-btm-api.c:2382:bitmain_board_init: Enter 30s sleep to make sure power release finish.
BitMaxz
legendary
Activity: 3472
Merit: 3217
Playbet.io - Crypto Casino and Sportsbook
Re: S17+ Wont mine, socket failed to connect, total packet loss
January 16, 2023, 06:44:43 PM
#8
I hope that you know how to use the insert code tag a sharp # button while editing your post it may look better than pasting the whole logs without it.

Anyway, what I see most of your logs are read temp/sensor errors it might be overheating or maybe the 3rd hashboard has a loose heatsink, and actually the miner itself is trying to fix the issue by gradually reducing the frequency.
Miner heatsinks sometimes loosen during delivery that's a common issue the only solution for that is to find that loose heatsink and reglue it with thermal glue/adhesive most recommended glue is an artic silver thermal adhesive to reattach the loose heatsink.

Another thing that I notice is the fan doesn't have signals

Here's mine with an insert code tag do this in your post above it will attract more people to come here and help you.
Code:
2023-01-10 23:26:26 driver-btm-api.c:1255:init_fan_parameter: fan_eft : 0  fan_pwm : 0

Would you mind to try to remove the 3rd hashboard first and let it run and let see if the two fan are running fine because sometimes abnormal fan can give different logs to other hashboard but the only culprit is the fan. So make sure to check if the two fan is working fine.
massivegoatdynamic
newbie
Activity: 19
Merit: 0
Re: S17+ Wont mine, socket failed to connect, total packet loss
January 16, 2023, 03:19:58 PM
#7
Quote from: BitMaxz on January 11, 2023, 11:40:59 AM
Oh wow, zeusbtc has a new account here but it's weird he is promoting a different link instead of their own guide.

@OP would you mind posting the whole kernel logs here so that we can check exactly what your miner problem is?

If it's not normally running fine try to remove the 3rd hashboard and let it run while the other hash board is connected.

If it's running fine the 3rd hashboard is bad without the whole kernel logs I can't give you a few suggestions so try to post the whole kernel logs here or paste it to pastebin.com and paste the link here.

Any chance you could make sense of the kernel log? I am going to try using a monster fan to cool it while running to see if that helps. Other than that might buy a diagnostic computer from Zeus.
massivegoatdynamic
newbie
Activity: 19
Merit: 0
Re: S17+ Wont mine, socket failed to connect, total packet loss
January 13, 2023, 12:02:36 AM
#6
This was the kernel log from before i removed hashboard 3. Do you think chip 14 is the likely culprit of what is hurting hasboard 3?

We are having cold weather tomorrow, perhaps I will have some luck getting it to hash if temperature is killing it.

Aside from my sadness that this expensive paperweight I bought isn't working. Have you ever tried immersion cooling miners with the monolithic heat sink? I am wondering if the thermal paste could muck up the fluid. When I bought this miner it claimed to have upgraded heat sinks but ended up being the old individual type. I am wondering with the monolithic heat sink maybe there is less chance of board failure since there is less solder floating around.

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: 203432K/245760K available (6345K kernel code, 231K rwdata, 1896K rodata, 1024K init, 223K bss, 25944K 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: 12904K (cce67000 - 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: 21/10, 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: 4099/1014, WL threshold: 4096, image sequence number: 3265111179
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 1AF6F1E1-61F0-462C-AE44-C7D9596CF7E2, 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 = 0xb023
In fpga mem driver!
request_mem_region OK!
fpga mem virtual address is 0xd2000000
random: nonblocking pool is initialized
2023-01-10 23:26:26 driver-btm-api.c:779:init_freq_mode: This is scan-user version
2023-01-10 23:26:26 driver-btm-api.c:2451:bitmain_soc_init: opt_multi_version     = 1
2023-01-10 23:26:26 driver-btm-api.c:2452:bitmain_soc_init: opt_bitmain_ab        = 1
2023-01-10 23:26:26 driver-btm-api.c:2453:bitmain_soc_init: opt_bitmain_work_mode = 0
2023-01-10 23:26:26 driver-btm-api.c:2454:bitmain_soc_init: Miner compile time: Tue Jun  2 10:31:07 CST 2020 type: Antminer S17+
2023-01-10 23:26:26 driver-btm-api.c:2455:bitmain_soc_init: commit version: 1ca50a5 2020-06-01 18:51:22, build by: lol 2020-06-02 10:37:21
2023-01-10 23:26:26 driver-btm-api.c:2083:show_sn: len:16, 80244d0c2b104814
2023-01-10 23:26:26 driver-btm-api.c:2461:bitmain_soc_init: show sn return 1
2023-01-10 23:26:26 driver-btm-api.c:2103:handle_sn_for_factory_mode: show sn return 1
2023-01-10 23:26:26 driver-btm-api.c:2141:handle_sn_for_factory_mode: read sn success, 80244d0c2b104814
2023-01-10 23:26:26 fan.c:284:front_fan_power_on: Note: front fan is power on!
2023-01-10 23:26:26 fan.c:296:rear_fan_power_on: Note: rear fan is power on!
2023-01-10 23:26:26 driver-btm-api.c:1314:miner_device_init: Detect 256MB control board of XILINX
2023-01-10 23:26:26 driver-btm-api.c:1255:init_fan_parameter: fan_eft : 0  fan_pwm : 0
2023-01-10 23:26:32 driver-btm-api.c:1239:init_miner_version: miner ID : 80244d0c2b104814
2023-01-10 23:26:32 driver-btm-api.c:1245:init_miner_version: FPGA Version = 0xB023
2023-01-10 23:26:36 driver-btm-api.c:837:get_product_id: product_id[0] = 0
2023-01-10 23:26:36 driver-btm-api.c:837:get_product_id: product_id[2] = 0
2023-01-10 23:26:36 driver-btm-api.c:2234:update_conf_by_power_feedback: Power feedback is disabled
2023-01-10 23:26:36 driver-btm-api.c:2202:get_calibration_voltage: calibration voltage flag is error data.
2023-01-10 23:26:36 driver-btm-api.c:2268:update_conf_by_power_feedback: Note: no calibration voltage, default diff = 0
2023-01-10 23:26:36 frequency.c:1457:adjust_higer_max_vol_table: adjust_higer_max_vol_table, adjust_vol = 0
2023-01-10 23:26:36 thread.c:1363:create_read_nonce_reg_thread: create thread
2023-01-10 23:26:42 driver-btm-api.c:1239:init_miner_version: miner ID : 80244d0c2b104814
2023-01-10 23:26:42 driver-btm-api.c:1245:init_miner_version: FPGA Version = 0xB023
2023-01-10 23:26:45 driver-btm-api.c:837:get_product_id: product_id[0] = 0
2023-01-10 23:26:45 driver-btm-api.c:837:get_product_id: product_id[2] = 0
2023-01-10 23:26:45 driver-btm-api.c:792:_set_project_type: project:0
2023-01-10 23:26:45 driver-btm-api.c:813:_set_project_type: Project type: Antminer S17+
2023-01-10 23:26:45 driver-btm-api.c:824:dump_pcb_bom_version: Chain [0] PCB Version: 0x0100
2023-01-10 23:26:45 driver-btm-api.c:825:dump_pcb_bom_version: Chain [0] BOM Version: 0x0100
2023-01-10 23:26:45 driver-btm-api.c:824:dump_pcb_bom_version: Chain [2] PCB Version: 0x0100
2023-01-10 23:26:45 driver-btm-api.c:825:dump_pcb_bom_version: Chain [2] BOM Version: 0x0100
2023-01-10 23:26:49 driver-btm-api.c:2372:bitmain_board_init: Fan check passed.
2023-01-10 23:26:50 board.c:36:jump_and_app_check_restore_pic: chain[0] PIC jump to app
2023-01-10 23:26:53 board.c:40:jump_and_app_check_restore_pic: Check chain[0] PIC fw version=0x88
2023-01-10 23:26:54 board.c:36:jump_and_app_check_restore_pic: chain[2] PIC jump to app
2023-01-10 23:26:56 board.c:40:jump_and_app_check_restore_pic: Check chain[2] PIC fw version=0x88
2023-01-10 23:26:56 thread.c:1358:create_pic_heart_beat_thread: create thread
2023-01-10 23:26:56 power_api.c:213:power_init: Power init:
2023-01-10 23:26:56 power_api.c:214:power_init: current_voltage_raw = 0
2023-01-10 23:26:56 power_api.c:215:power_init: highest_voltage_raw = 2100
2023-01-10 23:26:56 power_api.c:216:power_init: working_voltage_raw = 1950
2023-01-10 23:26:56 power_api.c:217:power_init: higher_voltage_raw  = 2040
2023-01-10 23:26:56 power_api.c:218:power_init: check_asic_voltage_raw  = 2100
2023-01-10 23:26:56 driver-btm-api.c:2382:bitmain_board_init: Enter 30s sleep to make sure power release finish.
2023-01-10 23:27:28 power_api.c:324:set_to_highest_voltage_by_steps: Set to voltage raw 2100, step by step.
2023-01-10 23:27:53 power_api.c:85:check_voltage_multi: retry time: 0
2023-01-10 23:27:55 power_api.c:40:_get_avg_voltage: chain = 0, voltage = 21.159092
2023-01-10 23:27:56 power_api.c:40:_get_avg_voltage: chain = 2, voltage = 21.156368
2023-01-10 23:27:56 power_api.c:53:_get_avg_voltage: average_voltage = 21.157730
2023-01-10 23:27:56 power_api.c:71:check_voltage: target_vol = 21.00, actural_vol = 21.16, check voltage passed.
2023-01-10 23:27:56 uart.c:72:set_baud: set fpga_baud to 115200
2023-01-10 23:28:07 driver-btm-api.c:1134:check_asic_number_with_power_on: Chain[0]: find 65 asic, times 0
2023-01-10 23:28:18 driver-btm-api.c:1134:check_asic_number_with_power_on: Chain[2]: find 65 asic, times 0
2023-01-10 23:28:23 driver-hash-chip.c:266:set_uart_relay: set uart relay to 0x330003
2023-01-10 23:28:23 driver-btm-api.c:435:set_order_clock: chain[0]: set order clock, stragegy 3
2023-01-10 23:28:23 driver-btm-api.c:435:set_order_clock: chain[2]: set order clock, stragegy 3
2023-01-10 23:28:24 driver-hash-chip.c:502:set_clock_delay_control: core_data = 0x34
2023-01-10 23:28:24 driver-btm-api.c:1892:check_clock_counter: freq 50 clock_counter_limit 6
2023-01-10 23:28:24 voltage[0] = 1980
2023-01-10 23:28:24 voltage[2] = 1980
2023-01-10 23:28:24 power_api.c:226:set_working_voltage_raw: working_voltage_raw = 1980
2023-01-10 23:28:25 temperature.c:340:calibrate_temp_sensor_one_chain: chain 0 temp sensor TMP451
2023-01-10 23:28:26 temperature.c:340:calibrate_temp_sensor_one_chain: chain 2 temp sensor NCT218
2023-01-10 23:28:26 uart.c:72:set_baud: set fpga_baud to 12000000
2023-01-10 23:28:27 temperature.c:843:get_temp_info: read temp sensor failed: chain = 2, sensor = 0, chip = 14, reg = 1
2023-01-10 23:28:27 driver-btm-api.c:293:check_bringup_temp: Bring up temperature is 24
2023-01-10 23:28:27 thread.c:1378:create_check_miner_status_thread: create thread
2023-01-10 23:28:27 thread.c:1368:create_show_miner_status_thread: create thread
2023-01-10 23:28:27 thread.c:1348:create_temperature_monitor_thread: create thread
2023-01-10 23:28:27 frequency.c:514:check_bringup_temp_dec_freq: dec freq = 0 when bringup temp = 24 dec_freq_index=0
2023-01-10 23:28:27 freq_tuning.c:183:freq_tuning_get_max_freq: Max freq of tuning is 650
2023-01-10 23:28:27 driver-btm-api.c:1765:send_null_work: [DEBUG] Send null work.
2023-01-10 23:28:27 thread.c:1338:create_asic_status_monitor_thread: create thread
2023-01-10 23:28:27 frequency.c:1110:inc_freq_with_fixed_vco: chain = 255, freq = 550, is_higher_voltage = true
2023-01-10 23:28:28 temperature.c:843:get_temp_info: read temp sensor failed: chain = 2, sensor = 0, chip = 14, reg = 1
2023-01-10 23:28:30 temperature.c:843:get_temp_info: read temp sensor failed: chain = 2, sensor = 0, chip = 14, reg = 1
2023-01-10 23:28:32 temperature.c:843:get_temp_info: read temp sensor failed: chain = 2, sensor = 0, chip = 14, reg = 1
2023-01-10 23:29:20 power_api.c:352:set_to_voltage_by_steps: Set to voltage raw 2090, step by step.
2023-01-10 23:29:21 temperature.c:843:get_temp_info: read temp sensor failed: chain = 2, sensor = 0, chip = 14, reg = 1
2023-01-10 23:29:22 power_api.c:85:check_voltage_multi: retry time: 0
2023-01-10 23:29:23 power_api.c:40:_get_avg_voltage: chain = 0, voltage = 20.988650
2023-01-10 23:29:23 temperature.c:843:get_temp_info: read temp sensor failed: chain = 2, sensor = 0, chip = 14, reg = 1
2023-01-10 23:29:24 power_api.c:40:_get_avg_voltage: chain = 2, voltage = 20.962217
2023-01-10 23:29:24 power_api.c:53:_get_avg_voltage: average_voltage = 20.975434
2023-01-10 23:29:24 power_api.c:71:check_voltage: target_vol = 20.90, actural_vol = 20.98, check voltage passed.
2023-01-10 23:29:25 temperature.c:843:get_temp_info: read temp sensor failed: chain = 2, sensor = 0, chip = 14, reg = 1
2023-01-10 23:34:03 driver-btm-api.c:765:set_timeout: freq = 550, percent = 90, hcn = 44236, timeout = 80
2023-01-10 23:34:03 power_api.c:310:set_to_working_voltage_by_steps: Set to voltage raw 1980, step by step.
2023-01-10 23:34:04 temperature.c:843:get_temp_info: read temp sensor failed: chain = 2, sensor = 0, chip = 14, reg = 1
2023-01-10 23:34:06 temperature.c:843:get_temp_info: read temp sensor failed: chain = 2, sensor = 0, chip = 14, reg = 1
2023-01-10 23:34:08 temperature.c:843:get_temp_info: read temp sensor failed: chain = 2, sensor = 0, chip = 14, reg = 1
2023-01-10 23:34:09 power_api.c:85:check_voltage_multi: retry time: 0
2023-01-10 23:34:09 temperature.c:843:get_temp_info: read temp sensor failed: chain = 2, sensor = 0, chip = 14, reg = 1
2023-01-10 23:34:10 power_api.c:40:_get_avg_voltage: chain = 0, voltage = 19.910466
2023-01-10 23:34:11 power_api.c:40:_get_avg_voltage: chain = 2, voltage = 19.910466
2023-01-10 23:34:11 power_api.c:53:_get_avg_voltage: average_voltage = 19.910466
2023-01-10 23:34:11 power_api.c:71:check_voltage: target_vol = 19.80, actural_vol = 19.91, check voltage passed.
2023-01-10 23:34:11 thread.c:1373:create_check_system_status_thread: create thread
2023-01-10 23:34:11 temperature.c:843:get_temp_info: read temp sensor failed: chain = 2, sensor = 0, chip = 14, reg = 1
2023-01-10 23:34:12 driver-btm-api.c:2618:bitmain_soc_init: Init done!
2023-01-10 23:34:12 driver-btm-api.c:222:set_miner_status: STATUS_INIT
2023-01-10 23:34:13 temperature.c:843:get_temp_info: read temp sensor failed: chain = 2, sensor = 0, chip = 14, reg = 1
2023-01-10 23:34:15 temperature.c:843:get_temp_info: read temp sensor failed: chain = 2, sensor = 0, chip = 14, reg = 1
2023-01-10 23:34:16 driver-btm-api.c:222:set_miner_status: STATUS_OKAY
2023-01-10 23:34:17 temperature.c:843:get_temp_info: read temp sensor failed: chain = 2, sensor = 0, chip = 14, reg = 1
2023-01-10 23:34:17 frequency.c:205:get_ideal_hash_rate_GH: ideal_hash_rate = 46846
2023-01-10 23:34:17 frequency.c:223:get_sale_hash_rate_GH: sale_hash_rate = 46000
2023-01-10 23:34:19 temperature.c:843:get_temp_info: read temp sensor failed: chain = 2, sensor = 0, chip = 14, reg = 1
2023-01-10 23:34:21 temperature.c:843:get_temp_info: read temp sensor failed: chain = 2, sensor = 0, chip = 14, reg = 1
2023-01-10 23:34:21 driver-btm-api.c:1496:dhash_chip_send_job: Version num 4.
2023-01-10 23:34:21 driver-btm-api.c:1644:dhash_chip_send_job: stime.tv_sec 1673393661, block_ntime 1673393660
2023-01-10 23:34:23 temperature.c:843:get_temp_info: read temp sensor failed: chain = 2, sensor = 0, chip = 14, reg = 1





massivegoatdynamic
newbie
Activity: 19
Merit: 0
Re: S17+ Wont mine, socket failed to connect, total packet loss
January 11, 2023, 09:58:12 PM
#5
I had peeked under the hood before but didn't notice what appears to be QC stickers on the 3rd hash board. I guess that board has had issues before and they did a bad patch job.

I unplugged the third hash board turned the unit on and got a fault light. Hit the reset button on the back and after hitting the IP report button it seemed to try to mine (Normal Light was on) and heat coming off of the miner.

The hardware error went away and it seemed to be trying but I still cant get a good "ping" diagnostic. Also of note was the fan was throttling down and up. No luck Sad

What are the odds that I get a video of the thing working in china and then it arriving here, sitting for a few months and my first attempt at mining I get these errors? Are these issues typical of something happening during transit?

Apologies for the large amount of text, I didn't see a button to attach a file. This is the kernel log after removing the third hashboard and it sounding like it was trying to mine.

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: 203432K/245760K available (6345K kernel code, 231K rwdata, 1896K rodata, 1024K init, 223K bss, 25944K 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: 12904K (cce67000 - 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: 21/10, 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: 4099/1014, WL threshold: 4096, image sequence number: 3265111179
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 1AF6F1E1-61F0-462C-AE44-C7D9596CF7E2, 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 = 0xb023
In fpga mem driver!
request_mem_region OK!
fpga mem virtual address is 0xd2000000
random: nonblocking pool is initialized
macb e000b000.ethernet eth0: link down
macb e000b000.ethernet eth0: unable to generate target frequency: 25000000 Hz
macb e000b000.ethernet eth0: link up (100/Full)
2023-01-12 01:47:32 driver-btm-api.c:779:init_freq_mode: This is scan-user version
2023-01-12 01:47:32 driver-btm-api.c:2451:bitmain_soc_init: opt_multi_version     = 1
2023-01-12 01:47:32 driver-btm-api.c:2452:bitmain_soc_init: opt_bitmain_ab        = 1
2023-01-12 01:47:32 driver-btm-api.c:2453:bitmain_soc_init: opt_bitmain_work_mode = 0
2023-01-12 01:47:32 driver-btm-api.c:2454:bitmain_soc_init: Miner compile time: Tue Jun  2 10:31:07 CST 2020 type: Antminer S17+
2023-01-12 01:47:32 driver-btm-api.c:2455:bitmain_soc_init: commit version: 1ca50a5 2020-06-01 18:51:22, build by: lol 2020-06-02 10:37:21
2023-01-12 01:47:32 driver-btm-api.c:2083:show_sn: len:16, 80244d0c2b104814
2023-01-12 01:47:32 driver-btm-api.c:2461:bitmain_soc_init: show sn return 1
2023-01-12 01:47:32 driver-btm-api.c:2103:handle_sn_for_factory_mode: show sn return 1
2023-01-12 01:47:32 driver-btm-api.c:2141:handle_sn_for_factory_mode: read sn success, 80244d0c2b104814
2023-01-12 01:47:32 fan.c:284:front_fan_power_on: Note: front fan is power on!
2023-01-12 01:47:32 fan.c:296:rear_fan_power_on: Note: rear fan is power on!
2023-01-12 01:47:32 driver-btm-api.c:1314:miner_device_init: Detect 256MB control board of XILINX
2023-01-12 01:47:32 driver-btm-api.c:1255:init_fan_parameter: fan_eft : 0  fan_pwm : 0
2023-01-12 01:47:38 driver-btm-api.c:1239:init_miner_version: miner ID : 80244d0c2b104814
2023-01-12 01:47:38 driver-btm-api.c:1245:init_miner_version: FPGA Version = 0xB023
2023-01-12 01:47:42 driver-btm-api.c:837:get_product_id: product_id[0] = 0
2023-01-12 01:47:42 driver-btm-api.c:837:get_product_id: product_id[1] = 0
2023-01-12 01:47:42 driver-btm-api.c:2234:update_conf_by_power_feedback: Power feedback is disabled
2023-01-12 01:47:42 driver-btm-api.c:2202:get_calibration_voltage: calibration voltage flag is error data.
2023-01-12 01:47:42 driver-btm-api.c:2268:update_conf_by_power_feedback: Note: no calibration voltage, default diff = 0
2023-01-12 01:47:42 frequency.c:1457:adjust_higer_max_vol_table: adjust_higer_max_vol_table, adjust_vol = 0
2023-01-12 01:47:42 thread.c:1363:create_read_nonce_reg_thread: create thread
2023-01-12 01:47:48 driver-btm-api.c:1239:init_miner_version: miner ID : 80244d0c2b104814
2023-01-12 01:47:48 driver-btm-api.c:1245:init_miner_version: FPGA Version = 0xB023
2023-01-12 01:47:51 driver-btm-api.c:837:get_product_id: product_id[0] = 0
2023-01-12 01:47:51 driver-btm-api.c:837:get_product_id: product_id[1] = 0
2023-01-12 01:47:51 driver-btm-api.c:792:_set_project_type: project:0
2023-01-12 01:47:51 driver-btm-api.c:813:_set_project_type: Project type: Antminer S17+
2023-01-12 01:47:51 driver-btm-api.c:824:dump_pcb_bom_version: Chain [0] PCB Version: 0x0100
2023-01-12 01:47:51 driver-btm-api.c:825:dump_pcb_bom_version: Chain [0] BOM Version: 0x0100
2023-01-12 01:47:51 driver-btm-api.c:824:dump_pcb_bom_version: Chain [1] PCB Version: 0x0100
2023-01-12 01:47:51 driver-btm-api.c:825:dump_pcb_bom_version: Chain [1] BOM Version: 0x0100
2023-01-12 01:47:55 driver-btm-api.c:2372:bitmain_board_init: Fan check passed.
2023-01-12 01:47:56 board.c:36:jump_and_app_check_restore_pic: chain[0] PIC jump to app
2023-01-12 01:47:58 board.c:40:jump_and_app_check_restore_pic: Check chain[0] PIC fw version=0x88
2023-01-12 01:47:59 board.c:36:jump_and_app_check_restore_pic: chain[1] PIC jump to app
2023-01-12 01:48:01 board.c:40:jump_and_app_check_restore_pic: Check chain[1] PIC fw version=0x88
2023-01-12 01:48:01 thread.c:1358:create_pic_heart_beat_thread: create thread
2023-01-12 01:48:01 power_api.c:213:power_init: Power init:
2023-01-12 01:48:01 power_api.c:214:power_init: current_voltage_raw = 0
2023-01-12 01:48:01 power_api.c:215:power_init: highest_voltage_raw = 2100
2023-01-12 01:48:01 power_api.c:216:power_init: working_voltage_raw = 1950
2023-01-12 01:48:01 power_api.c:217:power_init: higher_voltage_raw  = 2040
2023-01-12 01:48:01 power_api.c:218:power_init: check_asic_voltage_raw  = 2100
2023-01-12 01:48:01 driver-btm-api.c:2382:bitmain_board_init: Enter 30s sleep to make sure power release finish.
2023-01-12 01:48:33 power_api.c:324:set_to_highest_voltage_by_steps: Set to voltage raw 2100, step by step.
2023-01-12 01:48:59 power_api.c:85:check_voltage_multi: retry time: 0
2023-01-12 01:49:00 power_api.c:40:_get_avg_voltage: chain = 0, voltage = 21.156368
2023-01-12 01:49:01 power_api.c:40:_get_avg_voltage: chain = 1, voltage = 21.148242
2023-01-12 01:49:01 power_api.c:53:_get_avg_voltage: average_voltage = 21.152305
2023-01-12 01:49:01 power_api.c:71:check_voltage: target_vol = 21.00, actural_vol = 21.15, check voltage passed.
2023-01-12 01:49:01 uart.c:72:set_baud: set fpga_baud to 115200
2023-01-12 01:49:12 driver-btm-api.c:1134:check_asic_number_with_power_on: Chain[0]: find 65 asic, times 0
2023-01-12 01:49:23 driver-btm-api.c:1134:check_asic_number_with_power_on: Chain[1]: find 65 asic, times 0
2023-01-12 01:49:29 driver-hash-chip.c:266:set_uart_relay: set uart relay to 0x330003
2023-01-12 01:49:29 driver-btm-api.c:435:set_order_clock: chain[0]: set order clock, stragegy 3
2023-01-12 01:49:29 driver-btm-api.c:435:set_order_clock: chain[1]: set order clock, stragegy 3
2023-01-12 01:49:29 driver-hash-chip.c:502:set_clock_delay_control: core_data = 0x34
2023-01-12 01:49:29 driver-btm-api.c:1892:check_clock_counter: freq 50 clock_counter_limit 6
2023-01-12 01:49:30 voltage[0] = 1980
2023-01-12 01:49:30 voltage[1] = 1980
2023-01-12 01:49:30 power_api.c:226:set_working_voltage_raw: working_voltage_raw = 1980
2023-01-12 01:49:31 temperature.c:340:calibrate_temp_sensor_one_chain: chain 0 temp sensor TMP451
2023-01-12 01:49:32 temperature.c:340:calibrate_temp_sensor_one_chain: chain 1 temp sensor NCT218
2023-01-12 01:49:32 uart.c:72:set_baud: set fpga_baud to 12000000
2023-01-12 01:49:33 driver-btm-api.c:293:check_bringup_temp: Bring up temperature is 23
2023-01-12 01:49:33 thread.c:1378:create_check_miner_status_thread: create thread
2023-01-12 01:49:33 thread.c:1368:create_show_miner_status_thread: create thread
2023-01-12 01:49:33 thread.c:1348:create_temperature_monitor_thread: create thread
2023-01-12 01:49:33 frequency.c:514:check_bringup_temp_dec_freq: dec freq = 0 when bringup temp = 23 dec_freq_index=0
2023-01-12 01:49:33 freq_tuning.c:183:freq_tuning_get_max_freq: Max freq of tuning is 650
2023-01-12 01:49:33 driver-btm-api.c:1765:send_null_work: [DEBUG] Send null work.
2023-01-12 01:49:33 thread.c:1338:create_asic_status_monitor_thread: create thread
2023-01-12 01:49:33 frequency.c:1110:inc_freq_with_fixed_vco: chain = 255, freq = 550, is_higher_voltage = true
2023-01-12 01:50:46 power_api.c:352:set_to_voltage_by_steps: Set to voltage raw 2090, step by step.
2023-01-12 01:50:48 power_api.c:85:check_voltage_multi: retry time: 0
2023-01-12 01:50:50 power_api.c:40:_get_avg_voltage: chain = 0, voltage = 20.986147
2023-01-12 01:50:51 power_api.c:40:_get_avg_voltage: chain = 1, voltage = 20.978669
2023-01-12 01:50:51 power_api.c:53:_get_avg_voltage: average_voltage = 20.982408
2023-01-12 01:50:51 power_api.c:71:check_voltage: target_vol = 20.90, actural_vol = 20.98, check voltage passed.
2023-01-12 01:55:10 driver-btm-api.c:765:set_timeout: freq = 550, percent = 90, hcn = 44236, timeout = 80
2023-01-12 01:55:10 power_api.c:310:set_to_working_voltage_by_steps: Set to voltage raw 1980, step by step.
2023-01-12 01:55:15 power_api.c:85:check_voltage_multi: retry time: 0
2023-01-12 01:55:17 power_api.c:40:_get_avg_voltage: chain = 0, voltage = 19.933250
2023-01-12 01:55:18 power_api.c:40:_get_avg_voltage: chain = 1, voltage = 19.882057
2023-01-12 01:55:18 power_api.c:53:_get_avg_voltage: average_voltage = 19.907653
2023-01-12 01:55:18 power_api.c:71:check_voltage: target_vol = 19.80, actural_vol = 19.91, check voltage passed.
2023-01-12 01:55:18 thread.c:1373:create_check_system_status_thread: create thread
2023-01-12 01:55:19 driver-btm-api.c:2618:bitmain_soc_init: Init done!
2023-01-12 01:55:19 driver-btm-api.c:222:set_miner_status: STATUS_INIT
2023-01-12 01:55:23 driver-btm-api.c:222:set_miner_status: STATUS_OKAY
2023-01-12 01:55:24 frequency.c:205:get_ideal_hash_rate_GH: ideal_hash_rate = 46846
2023-01-12 01:55:24 frequency.c:223:get_sale_hash_rate_GH: sale_hash_rate = 46000
2023-01-12 01:55:28 driver-btm-api.c:1496:dhash_chip_send_job: Version num 4.
2023-01-12 01:55:28 driver-btm-api.c:1644:dhash_chip_send_job: stime.tv_sec 1673488528, block_ntime 1673488527
2023-01-12 01:58:45 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 30, reg = 28, got chain = 0, chip = 42, reg = 28
2023-01-12 01:58:45 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 30, reg = 28, got chain = 0, chip = 42, reg = 28
2023-01-12 01:58:45 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 30, reg = 28, got chain = 0, chip = 42, reg = 28
2023-01-12 01:58:45 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 162, reg = 28, got chain = 0, chip = 30, reg = 28
2023-01-12 01:58:45 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 150, reg = 28, got chain = 0, chip = 162, reg = 28
2023-01-12 01:58:45 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 1, chip = 42, reg = 28, got chain = 0, chip = 150, reg = 28
2023-01-12 01:58:45 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 1, chip = 30, reg = 28, got chain = 1, chip = 42, reg = 28
2023-01-12 01:58:45 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 1, chip = 162, reg = 28, got chain = 1, chip = 30, reg = 28
2023-01-12 01:58:45 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 1, chip = 162, reg = 28, got chain = 1, chip = 30, reg = 28
2023-01-12 01:58:45 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 1, chip = 162, reg = 28, got chain = 1, chip = 30, reg = 28
2023-01-12 01:58:45 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 1, chip = 150, reg = 28, got chain = 1, chip = 162, reg = 28
2023-01-12 01:58:47 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 162, reg = 28, got chain = 0, chip = 30, reg = 28
2023-01-12 01:58:47 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 1, chip = 162, reg = 28, got chain = 1, chip = 30, reg = 28
2023-01-12 01:58:49 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 30, reg = 28, got chain = 0, chip = 42, reg = 28
2023-01-12 01:58:49 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 30, reg = 28, got chain = 0, chip = 42, reg = 28
2023-01-12 01:58:49 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 150, reg = 28, got chain = 0, chip = 162, reg = 28
2023-01-12 01:58:50 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 1, chip = 42, reg = 28, got chain = 0, chip = 150, reg = 28
2023-01-12 01:58:50 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 1, chip = 42, reg = 28, got chain = 0, chip = 150, reg = 28
2023-01-12 01:58:50 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 1, chip = 30, reg = 28, got chain = 1, chip = 42, reg = 28
2023-01-12 01:58:50 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 1, chip = 162, reg = 28, got chain = 1, chip = 30, reg = 28
2023-01-12 01:58:50 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 1, chip = 150, reg = 28, got chain = 1, chip = 162, reg = 28
2023-01-12 01:58:50 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 1, chip = 150, reg = 28, got chain = 1, chip = 162, reg = 28

2023-01-12 02:03:22 thread.c:1383:create_shutdown_thread: create thread
2023-01-12 02:03:22 driver-btm-api.c:222:set_miner_status: STATUS_SHUTDOWN
2023-01-12 02:03:22 thread.c:1419:cancel_check_miner_status_thread: cancel thread
2023-01-12 02:03:22 thread.c:1388:cancel_temperature_monitor_thread: cancel thread
2023-01-12 02:03:22 thread.c:1414:cancel_check_system_status_thread: cancel thread
2023-01-12 02:03:22 thread.c:1403:cancel_read_nonce_reg_thread: cancel thread
2023-01-12 02:03:22 thread.c:1343:cancel_asic_status_monitor_thread: cancel thread
2023-01-12 02:03:24 thread.c:575:slowly_decrease_freq: set to 550M, delay 3000
2023-01-12 02:03:27 thread.c:575:slowly_decrease_freq: set to 545M, delay 3000
2023-01-12 02:03:30 thread.c:575:slowly_decrease_freq: set to 540M, delay 3000
2023-01-12 02:03:33 thread.c:575:slowly_decrease_freq: set to 535M, delay 3000
2023-01-12 02:03:36 thread.c:575:slowly_decrease_freq: set to 530M, delay 3000
2023-01-12 02:03:39 thread.c:575:slowly_decrease_freq: set to 525M, delay 3000
2023-01-12 02:03:42 thread.c:575:slowly_decrease_freq: set to 520M, delay 3000
2023-01-12 02:03:45 thread.c:575:slowly_decrease_freq: set to 515M, delay 3000
2023-01-12 02:03:48 thread.c:575:slowly_decrease_freq: set to 510M, delay 3000
2023-01-12 02:03:52 thread.c:575:slowly_decrease_freq: set to 505M, delay 3000
2023-01-12 02:03:55 thread.c:575:slowly_decrease_freq: set to 500M, delay 3000
2023-01-12 02:03:58 thread.c:575:slowly_decrease_freq: set to 495M, delay 3000
2023-01-12 02:04:01 thread.c:575:slowly_decrease_freq: set to 490M, delay 3000
2023-01-12 02:04:04 thread.c:575:slowly_decrease_freq: set to 485M, delay 3000
2023-01-12 02:04:07 thread.c:575:slowly_decrease_freq: set to 480M, delay 3000
2023-01-12 02:04:10 thread.c:575:slowly_decrease_freq: set to 475M, delay 3000
2023-01-12 02:04:13 thread.c:575:slowly_decrease_freq: set to 470M, delay 3000
2023-01-12 02:04:16 thread.c:575:slowly_decrease_freq: set to 465M, delay 3000
2023-01-12 02:04:19 thread.c:575:slowly_decrease_freq: set to 460M, delay 3000
2023-01-12 02:04:22 thread.c:575:slowly_decrease_freq: set to 455M, delay 3000
2023-01-12 02:04:25 thread.c:575:slowly_decrease_freq: set to 450M, delay 3000
2023-01-12 02:04:28 thread.c:575:slowly_decrease_freq: set to 445M, delay 3000
2023-01-12 02:04:31 thread.c:575:slowly_decrease_freq: set to 440M, delay 3000
2023-01-12 02:04:34 thread.c:575:slowly_decrease_freq: set to 435M, delay 3000
2023-01-12 02:04:37 thread.c:575:slowly_decrease_freq: set to 430M, delay 3000
2023-01-12 02:04:40 thread.c:575:slowly_decrease_freq: set to 425M, delay 3000
2023-01-12 02:04:43 thread.c:575:slowly_decrease_freq: set to 420M, delay 3000
2023-01-12 02:04:46 thread.c:575:slowly_decrease_freq: set to 415M, delay 3000
2023-01-12 02:04:49 thread.c:575:slowly_decrease_freq: set to 410M, delay 3000
2023-01-12 02:04:52 thread.c:575:slowly_decrease_freq: set to 405M, delay 3000
2023-01-12 02:04:55 thread.c:575:slowly_decrease_freq: set to 400M, delay 3000
2023-01-12 02:04:58 thread.c:575:slowly_decrease_freq: set to 395M, delay 3000
2023-01-12 02:05:01 thread.c:575:slowly_decrease_freq: set to 390M, delay 3000
2023-01-12 02:05:04 thread.c:575:slowly_decrease_freq: set to 385M, delay 3000
2023-01-12 02:05:07 thread.c:575:slowly_decrease_freq: set to 380M, delay 3000
2023-01-12 02:05:10 thread.c:575:slowly_decrease_freq: set to 375M, delay 3000
2023-01-12 02:05:13 thread.c:575:slowly_decrease_freq: set to 370M, delay 3000
2023-01-12 02:05:16 thread.c:575:slowly_decrease_freq: set to 365M, delay 3000
2023-01-12 02:05:19 thread.c:575:slowly_decrease_freq: set to 360M, delay 3000
2023-01-12 02:05:22 thread.c:575:slowly_decrease_freq: set to 355M, delay 3000
2023-01-12 02:05:25 thread.c:575:slowly_decrease_freq: set to 350M, delay 3000
2023-01-12 02:05:28 thread.c:575:slowly_decrease_freq: set to 345M, delay 3000
2023-01-12 02:05:31 thread.c:575:slowly_decrease_freq: set to 340M, delay 3000
2023-01-12 02:05:34 thread.c:575:slowly_decrease_freq: set to 335M, delay 3000
2023-01-12 02:05:37 thread.c:575:slowly_decrease_freq: set to 330M, delay 3000
2023-01-12 02:05:40 thread.c:575:slowly_decrease_freq: set to 325M, delay 3000
2023-01-12 02:05:43 thread.c:575:slowly_decrease_freq: set to 320M, delay 3000
2023-01-12 02:05:46 thread.c:575:slowly_decrease_freq: set to 315M, delay 3000
2023-01-12 02:05:49 thread.c:575:slowly_decrease_freq: set to 310M, delay 3000
2023-01-12 02:05:52 thread.c:575:slowly_decrease_freq: set to 305M, delay 3000
2023-01-12 02:05:55 thread.c:575:slowly_decrease_freq: set to 300M, delay 3000
2023-01-12 02:05:58 thread.c:575:slowly_decrease_freq: set to 295M, delay 3000
2023-01-12 02:06:01 thread.c:575:slowly_decrease_freq: set to 290M, delay 3000
2023-01-12 02:06:04 thread.c:575:slowly_decrease_freq: set to 285M, delay 3000
2023-01-12 02:06:07 thread.c:575:slowly_decrease_freq: set to 280M, delay 3000
2023-01-12 02:06:10 thread.c:575:slowly_decrease_freq: set to 275M, delay 3000
2023-01-12 02:06:13 thread.c:575:slowly_decrease_freq: set to 270M, delay 3000
2023-01-12 02:06:16 thread.c:575:slowly_decrease_freq: set to 265M, delay 3000
2023-01-12 02:06:19 thread.c:575:slowly_decrease_freq: set to 260M, delay 3000
2023-01-12 02:06:22 thread.c:575:slowly_decrease_freq: set to 255M, delay 3000
2023-01-12 02:06:25 thread.c:575:slowly_decrease_freq: set to 250M, delay 3000
2023-01-12 02:06:28 thread.c:575:slowly_decrease_freq: set to 245M, delay 3000
2023-01-12 02:06:31 thread.c:575:slowly_decrease_freq: set to 240M, delay 3000
2023-01-12 02:06:34 thread.c:575:slowly_decrease_freq: set to 235M, delay 3000
2023-01-12 02:06:37 thread.c:575:slowly_decrease_freq: set to 230M, delay 3000
2023-01-12 02:06:40 thread.c:575:slowly_decrease_freq: set to 225M, delay 3000
2023-01-12 02:06:43 thread.c:575:slowly_decrease_freq: set to 220M, delay 3000
2023-01-12 02:06:46 thread.c:575:slowly_decrease_freq: set to 215M, delay 3000
2023-01-12 02:06:49 thread.c:575:slowly_decrease_freq: set to 210M, delay 3000
2023-01-12 02:06:52 thread.c:575:slowly_decrease_freq: set to 205M, delay 3000
2023-01-12 02:06:55 thread.c:575:slowly_decrease_freq: set to 200M, delay 3000
2023-01-12 02:06:58 thread.c:575:slowly_decrease_freq: set to 195M, delay 3000
2023-01-12 02:07:01 thread.c:575:slowly_decrease_freq: set to 190M, delay 3000
2023-01-12 02:07:04 thread.c:575:slowly_decrease_freq: set to 185M, delay 3000
2023-01-12 02:07:07 thread.c:575:slowly_decrease_freq: set to 180M, delay 3000
2023-01-12 02:07:10 thread.c:575:slowly_decrease_freq: set to 175M, delay 3000
2023-01-12 02:07:13 thread.c:575:slowly_decrease_freq: set to 170M, delay 3000
2023-01-12 02:07:16 thread.c:575:slowly_decrease_freq: set to 165M, delay 3000
2023-01-12 02:07:19 thread.c:575:slowly_decrease_freq: set to 160M, delay 3000
BitMaxz
legendary
Activity: 3472
Merit: 3217
Playbet.io - Crypto Casino and Sportsbook
Re: S17+ Wont mine, socket failed to connect, total packet loss
January 11, 2023, 11:40:59 AM
#4
Oh wow, zeusbtc has a new account here but it's weird he is promoting a different link instead of their own guide.

@OP would you mind posting the whole kernel logs here so that we can check exactly what your miner problem is?

If it's not normally running fine try to remove the 3rd hashboard and let it run while the other hash board is connected.

If it's running fine the 3rd hashboard is bad without the whole kernel logs I can't give you a few suggestions so try to post the whole kernel logs here or paste it to pastebin.com and paste the link here.
massivegoatdynamic
newbie
Activity: 19
Merit: 0
Re: S17+ Wont mine, socket failed to connect, total packet loss
January 11, 2023, 07:21:59 AM
#3
Do you think the "temp issue" which is likely a bad chip or solder job could explain the "socket connect failed" message or the "6 packets transmitted, 0 packets received" message? The socket connect failed message is intermittent, it occasionally goes away and you can go to the Miner status stab and see 2/3 hashboards attemping to work.
ZeusBtc.com
jr. member
Activity: 43
Merit: 22
Re: S17+ Wont mine, socket failed to connect, total packet loss
January 11, 2023, 03:56:58 AM
#2
Yes, chain 2 refers to the third hashboard. For temp sensor issues, you can check this thread: https://bitcointalksearch.org/topic/antminer-t17s17-temp-sensor-problem-discussion-5244120
massivegoatdynamic
newbie
Activity: 19
Merit: 0
Re: S17+ Wont mine, socket failed to connect, total packet loss
January 10, 2023, 11:17:48 PM
#1
Hello all. I bought a used S17+ last year and didn't get around to plugging it in until this past week. The seller sent me a video of the thing working before shipping and of course I get it and I can't get it to mine. I get 2 error messages "Socket Connect Failed: Connection refused" and when I go into network diagnostic and hit "ping" I get the message "6 packets transmitted, 0 packets received, 100% packet loss. I have put the latest firmware from bitmain on there, rebooted it, hit the reset button on the machine, the IP search button and occasionally the "socket connect failed" message disappears but it never mines. Any thoughts on how I could get it to move? I am thinking of trying Slush Pools firmware to see if it acts any different.

The kernel readout has a ton of output, the only thing that stands out is: 2023-01-10 23:28:28 temperature.c:843:get_temp_info: read temp sensor failed: chain = 2, sensor = 0, chip = 14, reg = 1

And does this mean it is actually the third hashboard "chain 2"? I am guessing that means the 14th chip on the third hashboard might be bad?

Any input would be greatly appreciated.

Also is there a cheat sheet of sorts to understand what all is going on in the kernel log? It kicks out a lot of information but I don't know what it means.
Bitcoin Forum>Bitcoin>Mining>Mining support
Jump to: