Bitcoin Forum
January 17, 2021, 10:56:17 PM *
News: Latest Bitcoin Core release: 0.21.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: « 1 2 3 4 5 6 7 8 [9] 10 11 12 13 14 15 16 17 »  All
  Print  
Author Topic: T17/S17 malfunction: cases, solutions, remedies, RMA history  (Read 4229 times)
This is a self-moderated topic. If you do not want to be moderated by the person who started this topic, create a new topic.
Scorpyy
Jr. Member
*
Offline Offline

Activity: 42
Merit: 57


View Profile
September 15, 2020, 10:30:16 AM
Merited by suchmoon (4), frodocooper (3)
 #161

Man i wish i could bring any good news but i submitted all documentation, was polite, sent tons of e-mails, told them that we had 3k+ usd in expenses due to fail equipment and 300+ USD in expenses due to DOA returned units.

And you know what their response was?

"we double checked with our leader we can apply for 23USD coupon for you " IS THIS A JOKE?

And then guess what, they doubled it:

"sorry what we can max compensate is 50 usd "

This has to be a joke? Jessica L. is bored and she-s joking with me.
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1610924177
Hero Member
*
Offline Offline

Posts: 1610924177

View Profile Personal Message (Offline)

Ignore
1610924177
Reply with quote  #2

1610924177
Report to moderator
1610924177
Hero Member
*
Offline Offline

Posts: 1610924177

View Profile Personal Message (Offline)

Ignore
1610924177
Reply with quote  #2

1610924177
Report to moderator
1610924177
Hero Member
*
Offline Offline

Posts: 1610924177

View Profile Personal Message (Offline)

Ignore
1610924177
Reply with quote  #2

1610924177
Report to moderator
NotFuzzyWarm
Legendary
*
Offline Offline

Activity: 2422
Merit: 1587


Evil beware: We have waffles!


View Profile
September 15, 2020, 01:01:28 PM
 #162

Nope, not joking. That ^^ kind of stunts is why I stopped using BM gear years ago. Much prefer MicroBT (Whatsminers) and Canaan (Avalons). MicroBT are more efficient but the Avalons are better built.

- For bitcoin to succeed the community must police itself -    My info useful? Donations welcome! 1FuzzyWc2J8TMqeUQZ8yjE43Rwr7K3cxs9
How a miner mfgr SHOULD operate:  HaggsFIN trip to Canaan
-Support Sidehacks miner development. Donations to:   1BURGERAXHH6Yi6LRybRJK7ybEm5m5HwTr
Scorpyy
Jr. Member
*
Offline Offline

Activity: 42
Merit: 57


View Profile
September 15, 2020, 02:20:42 PM
Merited by philipma1957 (12)
 #163

you will at least manage to get some refund in the end.

When you said some refund i wasn't thinking about value equal to 2 large pizza-s and a coca cola. And the value is in COUPON. Not only that they don't have anything for sale for months but also why would i even consider buying from them again.
philipma1957
Legendary
*
Offline Offline

Activity: 2912
Merit: 2974



View Profile
September 15, 2020, 03:51:23 PM
Last edit: September 16, 2020, 12:11:29 AM by frodocooper
 #164

you must be persistent
be patient
be professional
be persuasive
be polite.

tell them that 50usd is far too small.
ask for 1000usd in btc to an address for a  refund

you are in for 3300 and have two working boards.

you should get 2200 usd

but are willing to take 1000usd.

point to this thread. tell them they have given much larger amounts to other customers.

I see BTC as the super highway and alt coins as taxis and trucks needed to move transactions.
mikeywith
Legendary
*
Online Online

Activity: 1022
Merit: 3413


be constructive or S.T.F.U


View Profile
September 16, 2020, 10:49:20 AM
Last edit: September 17, 2020, 02:33:34 AM by frodocooper
 #165

Oh boy, a $50 coupon to make up for $3300 loss is nuts, i was not expecting them to send you a full refund, not even a half but most certainly not a $50 coupons.

It seems like they have gone broke or lost a ton of money during the past a few months, but you stay on it, stay persistent don't give up just yet.

Tell them you will go to court for this if they don't refund you some serious amount.

PopoJeff
Full Member
***
Offline Offline

Activity: 378
Merit: 168


View Profile
September 18, 2020, 09:55:15 PM
 #166

Rather than wait for Bitmain repair location to open post-covid to fix my DOA claim, I just sold my unit on eBay.
The S17+ 70 I got cost me less than $200 after applying Bitmain credit.  It arrived with one dead board.  
I got $650 for it on eBay.  

And bought a S17+73 from a friend for $650.

All in all..... it was much better than dealing with Bitmain

Home garage miner:  (5) S17+ 73th
wndsnb
Sr. Member
****
Offline Offline

Activity: 276
Merit: 337


View Profile
October 06, 2020, 02:58:47 PM
Merited by frodocooper (2)
 #167

I've had 2 out of 7 S17 Pros that came from Malaysia go down. One was RMAed to the CA site months ago ... still waiting for updates. The other one I just picked up from my host to try to fix myself. My host did all they could do and had no luck.

Interestingly, I have 10 S17s and 3 S17pros that came from China at a host in Canada and not a single one has gone down. Wondering if quality control at the Malaysia plant is not so good...
mikeywith
Legendary
*
Online Online

Activity: 1022
Merit: 3413


be constructive or S.T.F.U


View Profile
October 06, 2020, 05:18:42 PM
Last edit: October 06, 2020, 11:44:09 PM by frodocooper
 #168

As far as I know, Bitmain doesn't make any mining gears in Malaysia, it's probably just a sorting hub to reduce import/tax costs for countries that aren't so friendly with goods coming in directly from China, what happened to you was probably nothing but a bad luck with one of the batches, Someone said that the recent batches are slightly better build as far as the thermal/glue is is concerned, which does make sense.

Please keep us updated with your attempt to fix this broken S17 pro, if possible, describe the issues you are facing just in case someone had the same problem and they could help you fix it.

NotFuzzyWarm
Legendary
*
Offline Offline

Activity: 2422
Merit: 1587


Evil beware: We have waffles!


View Profile
October 06, 2020, 05:29:30 PM
Last edit: October 06, 2020, 06:06:06 PM by NotFuzzyWarm
Merited by frodocooper (2)
 #169

Quote
As far as I know, Bitmain doesn't make any mining gears in Malaysia, it's probably just a sorting hub to reduce import/tax costs for countries that aren't so friendly with goods coming in directly from China,
Incorrect. The Trump Tax tariff and ones from a few other countries forbid that by using Country of Origin as the deciding factor. That means where the miners are assembled so BM does have at least 1 assembly plant in Malaysia that does at least final assembly of them using parts made in China. Given the quality issues they may also stuff the hash boards there...

- For bitcoin to succeed the community must police itself -    My info useful? Donations welcome! 1FuzzyWc2J8TMqeUQZ8yjE43Rwr7K3cxs9
How a miner mfgr SHOULD operate:  HaggsFIN trip to Canaan
-Support Sidehacks miner development. Donations to:   1BURGERAXHH6Yi6LRybRJK7ybEm5m5HwTr
mikeywith
Legendary
*
Online Online

Activity: 1022
Merit: 3413


be constructive or S.T.F.U


View Profile
October 06, 2020, 08:00:38 PM
Last edit: October 06, 2020, 11:46:20 PM by frodocooper
 #170

I stand corrected then, I confrimed from a Malaysian source that Bitmain does indeed assemble some of it's miners in Malaysia, still "assembly" is quite a broad word as in we don't know to which level of assembly they go to.

I still think the quality isn't very different because 90% of the issues that all of these 17 series gears have in common is the thermal paste/solder, whereby the whole chip fall down or just the heatsink drops (both lead to a none-working hash board) I highly doubt soldering the chips nor glueing the heatsinks on them is done in Malaysia, it's more likely that they receive ready to use hash boards, control boards, PSUs and a bunch of screws and all they do is put them all together, and just by doing so, you can't really harm the hash boars unless you intentionally do it, and even then, you need a lot of time and effort.

on the other hand,  if the assembly goes to a much lower level like soldering the chips and all, then the difference in quality will vary greatly, however, all the 17 series gears I ordered came from China, and the quality is terrible overall, so I still believe it's a matter of luck after all.

I shall confirm what does actually happen in the warehouse of Malaysia in a few days, will keep you updated.

philipma1957
Legendary
*
Offline Offline

Activity: 2912
Merit: 2974



View Profile
October 06, 2020, 08:15:43 PM
Last edit: October 06, 2020, 11:46:47 PM by frodocooper
 #171

Maybe you don't let us know. Since you never know who is reading this.

My partner buysolar got a 700 import tax bill today. I am hoping I don't get any bills for the gear I purchased last fall.

I see BTC as the super highway and alt coins as taxis and trucks needed to move transactions.
mikeywith
Legendary
*
Online Online

Activity: 1022
Merit: 3413


be constructive or S.T.F.U


View Profile
October 06, 2020, 10:46:51 PM
Last edit: October 06, 2020, 11:49:00 PM by frodocooper
 #172

I don't think that is confidential information, assembling thousands of miners isn't something you can keep a secret, unless specified otherwise by my source then i will not reveal the information.

wndsnb
Sr. Member
****
Offline Offline

Activity: 276
Merit: 337


View Profile
October 06, 2020, 11:16:31 PM
Last edit: October 07, 2020, 12:12:36 PM by wndsnb
Merited by frodocooper (3)
 #173

Yeah, this miner even has a label saying it was made in Malaysia.



My host reported that some heatsinks had fallen off. They put them back on but it still did not come back up completely, reporting 0 asics on two of the hashboards and some temperature sensor issues. Just hooked it up last night and it came up just fine ran for about 30 minutes and then died. So already better than what my host was reporting. Maybe the bumping around/vibration from the 8 hours of being in my car on the drive home did it some good.

After it died, I updated it to the latest firmware and started it back up before going to bed. It was still running when I got up this morning. It's reasonably cool here so fans are running around 50%. I'm going to figure out a way to limit cooling to stress test it before I declare it fixed.

Here's the log where it ran for 30 min then went dead:

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: 190264K/245760K available (6345K kernel code, 231K rwdata, 1896K rodata, 1024K init, 223K bss, 39112K reserved, 16384K cma-reserved, 0K highmem)
Virtual kernel memory layout:
    vector  : 0xffff0000 - 0xffff1000   (   4 kB)
    fixmap  : 0xffc00000 - 0xfff00000   (3072 kB)
    vmalloc : 0xcf800000 - 0xff800000   ( 768 MB)
    lowmem  : 0xc0000000 - 0xcf000000   ( 240 MB)
    pkmap   : 0xbfe00000 - 0xc0000000   (   2 MB)
    modules : 0xbf000000 - 0xbfe00000   (  14 MB)
      .text : 0xc0008000 - 0xc090c424   (9234 kB)
      .init : 0xc0a00000 - 0xc0b00000   (1024 kB)
      .data : 0xc0b00000 - 0xc0b39fe0   ( 232 kB)
       .bss : 0xc0b39fe0 - 0xc0b71c28   ( 224 kB)
Preemptible hierarchical RCU implementation.
Build-time adjustment of leaf fanout to 32.
RCU restricting CPUs from NR_CPUS=4 to nr_cpu_ids=2.
RCU: Adjusting geometry for rcu_fanout_leaf=32, nr_cpu_ids=2
NR_IRQS:16 nr_irqs:16 16
efuse mapped to cf800000
ps7-slcr mapped to cf802000
L2C: platform modifies aux control register: 0x72360000 -> 0x72760000
L2C: DT/platform modifies aux control register: 0x72360000 -> 0x72760000
L2C-310 erratum 769419 enabled
L2C-310 enabling early BRESP for Cortex-A9
L2C-310 full line of zeros enabled for Cortex-A9
L2C-310 ID prefetch enabled, offset 1 lines
L2C-310 dynamic clock gating enabled, standby mode enabled
L2C-310 cache controller enabled, 8 ways, 512 kB
L2C-310: CACHE_ID 0x410000c8, AUX_CTRL 0x76760001
zynq_clock_init: clkc starts at cf802100
Zynq clock init
sched_clock: 64 bits at 333MHz, resolution 3ns, wraps every 4398046511103ns
clocksource: arm_global_timer: mask: 0xffffffffffffffff max_cycles: 0x4ce07af025, max_idle_ns: 440795209040 ns
Switching to timer-based delay loop, resolution 3ns
clocksource: ttc_clocksource: mask: 0xffff max_cycles: 0xffff, max_idle_ns: 537538477 ns
ps7-ttc #0 at cf80a000, irq=18
Console: colour dummy device 80x30
Calibrating delay loop (skipped), value calculated using timer frequency.. 666.66 BogoMIPS (lpj=3333333)
pid_max: default: 32768 minimum: 301
Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
CPU: Testing write buffer coherency: ok
CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
Setting up static identity map for 0x100000 - 0x100058
CPU1: failed to boot: -1
Brought up 1 CPUs
SMP: Total of 1 processors activated (666.66 BogoMIPS).
CPU: All CPU(s) started in SVC mode.
devtmpfs: initialized
VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4
clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
pinctrl core: initialized pinctrl subsystem
NET: Registered protocol family 16
DMA: preallocated 256 KiB pool for atomic coherent allocations
cpuidle: using governor menu
hw-breakpoint: found 5 (+1 reserved) breakpoint and 1 watchpoint registers.
hw-breakpoint: maximum watchpoint size is 4 bytes.
zynq-ocm f800c000.ps7-ocmc: ZYNQ OCM pool: 256 KiB @ 0xcf880000
vgaarb: loaded
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
media: Linux media interface: v0.10
Linux video capture interface: v2.00
pps_core: LinuxPPS API ver. 1 registered
pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
PTP clock support registered
EDAC MC: Ver: 3.0.0
Advanced Linux Sound Architecture Driver Initialized.
clocksource: Switched to clocksource arm_global_timer
NET: Registered protocol family 2
TCP established hash table entries: 2048 (order: 1, 8192 bytes)
TCP bind hash table entries: 2048 (order: 2, 16384 bytes)
TCP: Hash tables configured (established 2048 bind 2048)
UDP hash table entries: 256 (order: 1, 8192 bytes)
UDP-Lite hash table entries: 256 (order: 1, 8192 bytes)
NET: Registered protocol family 1
RPC: Registered named UNIX socket transport module.
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
PCI: CLS 0 bytes, default 64
Trying to unpack rootfs image as initramfs...
rootfs image is not initramfs (no cpio magic); looks like an initrd
Freeing initrd memory: 26072K (cc18b000 - 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: 2/1, WL threshold: 4096, image sequence number: 1099087952
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 CD1BC056-7E24-4E3E-BCAF-EAA178A77B8B, 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: 972/211, WL threshold: 4096, image sequence number: 4185749592
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 4829CF2C-7435-4146-B2FD-0826AAE8443A, small LPT model
IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
macb e000b000.ethernet eth0: unable to generate target frequency: 25000000 Hz
macb e000b000.ethernet eth0: link up (100/Full)
IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
In axi fpga driver!
request_mem_region OK!
AXI fpga dev virtual address is 0xcfb38000
*base_vir_addr = 0xab011
In fpga mem driver!
request_mem_region OK!
fpga mem virtual address is 0xd2000000
random: nonblocking pool is initialized
2020-10-06 00:22:35 driver-btm-api.c:773:init_freq_mode: This is scan-user version
2020-10-06 00:22:35 driver-btm-api.c:1891:bitmain_soc_init: opt_multi_version     = 1
2020-10-06 00:22:35 driver-btm-api.c:1892:bitmain_soc_init: opt_bitmain_ab        = 1
2020-10-06 00:22:35 driver-btm-api.c:1893:bitmain_soc_init: opt_bitmain_work_mode = 1
2020-10-06 00:22:35 driver-btm-api.c:1894:bitmain_soc_init: Miner compile time: Mon May 27 10:57:13 CST 2019 type: Antminer S17 Pro
2020-10-06 00:22:35 driver-btm-api.c:1895:bitmain_soc_init: commit version: c0bb7cc 2019-05-23 10:59:44, build by: lol 2019-05-27 11:08:02
2020-10-06 00:22:35 driver-btm-api.c:1778:show_sn: no SN got, please write SN to /nvdata/sn
2020-10-06 00:22:35 driver-btm-api.c:1251:miner_device_init: Detect 256MB control board of XILINX
2020-10-06 00:22:35 driver-btm-api.c:1199:init_fan_parameter: fan_eft : 0  fan_pwm : 0
2020-10-06 00:22:35 thread.c:627:create_read_nonce_reg_thread: create thread
2020-10-06 00:22:41 driver-btm-api.c:1183:init_miner_version: miner ID : 800a1dce57408854
2020-10-06 00:22:41 driver-btm-api.c:1189:init_miner_version: FPGA Version = 0xB011
2020-10-06 00:22:47 driver-btm-api.c:835:get_product_id: product_id[0] = 0
2020-10-06 00:22:47 driver-btm-api.c:835:get_product_id: product_id[1] = 0
2020-10-06 00:22:47 driver-btm-api.c:835:get_product_id: product_id[2] = 0
2020-10-06 00:22:47 driver-btm-api.c:786:_set_project_type: project:0
2020-10-06 00:22:47 driver-btm-api.c:811:_set_project_type: Project type: Antminer S17 Pro
2020-10-06 00:22:47 driver-btm-api.c:822:dump_pcb_bom_version: Chain [0] PCB Version: 0x0101
2020-10-06 00:22:47 driver-btm-api.c:823:dump_pcb_bom_version: Chain [0] BOM Version: 0x0103
2020-10-06 00:22:47 driver-btm-api.c:822:dump_pcb_bom_version: Chain [1] PCB Version: 0x0101
2020-10-06 00:22:47 driver-btm-api.c:823:dump_pcb_bom_version: Chain [1] BOM Version: 0x0103
2020-10-06 00:22:47 driver-btm-api.c:822:dump_pcb_bom_version: Chain [2] PCB Version: 0x0101
2020-10-06 00:22:47 driver-btm-api.c:823:dump_pcb_bom_version: Chain [2] BOM Version: 0x0103
2020-10-06 00:22:48 driver-btm-api.c:1841:bitmain_board_init: Fan check passed.
2020-10-06 00:22:50 board.c:36:jump_and_app_check_restore_pic: chain[0] PIC jump to app
2020-10-06 00:22:53 board.c:40:jump_and_app_check_restore_pic: Check chain[0] PIC fw version=0xb9
2020-10-06 00:22:55 board.c:36:jump_and_app_check_restore_pic: chain[1] PIC jump to app
2020-10-06 00:22:58 board.c:40:jump_and_app_check_restore_pic: Check chain[1] PIC fw version=0xb9
2020-10-06 00:23:00 board.c:36:jump_and_app_check_restore_pic: chain[2] PIC jump to app
2020-10-06 00:23:03 board.c:40:jump_and_app_check_restore_pic: Check chain[2] PIC fw version=0xb9
2020-10-06 00:23:03 thread.c:622:create_pic_heart_beat_thread: create thread
2020-10-06 00:23:03 power_api.c:55:power_init: power init ...
2020-10-06 00:23:03 driver-btm-api.c:1851:bitmain_board_init: Enter 30s sleep to make sure power release finish.
2020-10-06 00:23:35 power_api.c:164:set_iic_power_to_highest_voltage: setting to voltage: 21.00 ...
2020-10-06 00:23:41 power_api.c:113:set_iic_power_by_voltage: now setting voltage to : 21.000000
2020-10-06 00:23:53 driver-btm-api.c:1126:check_asic_number_with_power_on: Chain[0]: find 48 asic, times 0
2020-10-06 00:24:05 driver-btm-api.c:1126:check_asic_number_with_power_on: Chain[1]: find 48 asic, times 0
2020-10-06 00:24:17 driver-btm-api.c:1126:check_asic_number_with_power_on: Chain[2]: find 48 asic, times 0
2020-10-06 00:24:17 driver-btm-api.c:336:set_order_clock: chain[0]: set order clock, stragegy 3
2020-10-06 00:24:17 driver-btm-api.c:336:set_order_clock: chain[1]: set order clock, stragegy 3
2020-10-06 00:24:17 driver-btm-api.c:336:set_order_clock: chain[2]: set order clock, stragegy 3
2020-10-06 00:24:22 driver-hash-chip.c:453:set_clock_delay_control: core_data = 0x34
2020-10-06 00:24:22 voltage[0] = 1800
2020-10-06 00:24:22 voltage[1] = 1800
2020-10-06 00:24:22 voltage[2] = 1800
2020-10-06 00:24:22 power_api.c:76:set_working_voltage: working_voltage = 18.000000
2020-10-06 00:24:24 temperature.c:267:calibrate_temp_sensor_one_chain: Temperature sensor calibration: chain 0 success.
2020-10-06 00:24:25 temperature.c:267:calibrate_temp_sensor_one_chain: Temperature sensor calibration: chain 1 success.
2020-10-06 00:24:26 temperature.c:267:calibrate_temp_sensor_one_chain: Temperature sensor calibration: chain 2 success.
2020-10-06 00:24:26 driver-hash-chip.c:229:dhash_chip_set_baud_v2: chain[0]: chip baud = 6000000, chip_divider = 7
2020-10-06 00:24:26 driver-hash-chip.c:229:dhash_chip_set_baud_v2: chain[1]: chip baud = 6000000, chip_divider = 7
2020-10-06 00:24:26 driver-hash-chip.c:229:dhash_chip_set_baud_v2: chain[2]: chip baud = 6000000, chip_divider = 7
2020-10-06 00:24:26 uart.c:80:set_baud: set fpga_baud = 6000000, fpga_divider = 3
2020-10-06 00:24:28 driver-btm-api.c:236:check_bringup_temp: Bring up temperature is 25
2020-10-06 00:24:28 thread.c:642:create_check_miner_status_thread: create thread
2020-10-06 00:24:28 thread.c:632:create_set_miner_status_thread: create thread
2020-10-06 00:24:28 driver-btm-api.c:723:calculate_timeout: dev->timeout = 245
2020-10-06 00:24:28 freq_tuning.c:173:freq_tuning_get_max_freq: Max freq of tuning is 690
2020-10-06 00:24:28 frequency.c:484:increase_freq_by_frequency_list_slowly: Increase freq slowly for all chain to 565
2020-10-06 00:24:28 frequency.c:341:auto_adaption_high_voltage_increase_frequency: auto adaption increase frequency from 50.000000 to 500.000000 @20.80V.
2020-10-06 00:24:28 frequency.c:342:auto_adaption_high_voltage_increase_frequency: index 0 2
2020-10-06 00:24:28 power_api.c:344:slowly_set_iic_power_to_custom_voltage: slowly setting to voltage: 20.80 ...
2020-10-06 00:24:52 power_api.c:219:get_average_voltage: chain[0], voltage is: 21.149004
2020-10-06 00:24:54 power_api.c:219:get_average_voltage: chain[1], voltage is: 21.179619
2020-10-06 00:24:57 power_api.c:219:get_average_voltage: chain[2], voltage is: 21.057158
2020-10-06 00:24:57 power_api.c:229:get_average_voltage: average voltage is: 21.128593
2020-10-06 00:24:57 driver-btm-api.c:657:increase_freq_slowly: init_freq = 50.00, final_freq = 500.00, freq_step = 5.00, chain = 255
2020-10-06 00:26:28 frequency.c:341:auto_adaption_high_voltage_increase_frequency: auto adaption increase frequency from 500.000000 to 550.000000 @20.30V.
2020-10-06 00:26:28 frequency.c:342:auto_adaption_high_voltage_increase_frequency: index 1 2
2020-10-06 00:26:28 power_api.c:344:slowly_set_iic_power_to_custom_voltage: slowly setting to voltage: 20.30 ...
2020-10-06 00:27:07 power_api.c:219:get_average_voltage: chain[0], voltage is: 20.683652
2020-10-06 00:27:09 power_api.c:219:get_average_voltage: chain[1], voltage is: 20.708144
2020-10-06 00:27:11 power_api.c:219:get_average_voltage: chain[2], voltage is: 20.604052
2020-10-06 00:27:11 power_api.c:229:get_average_voltage: average voltage is: 20.665283
2020-10-06 00:27:11 driver-btm-api.c:657:increase_freq_slowly: init_freq = 500.00, final_freq = 550.00, freq_step = 5.00, chain = 255
2020-10-06 00:27:21 frequency.c:341:auto_adaption_high_voltage_increase_frequency: auto adaption increase frequency from 550.000000 to 565.000000 @19.60V.
2020-10-06 00:27:21 frequency.c:342:auto_adaption_high_voltage_increase_frequency: index 2 2
2020-10-06 00:27:21 power_api.c:344:slowly_set_iic_power_to_custom_voltage: slowly setting to voltage: 19.60 ...
2020-10-06 00:27:56 power_api.c:219:get_average_voltage: chain[0], voltage is: 19.942763
2020-10-06 00:27:57 power_api.c:219:get_average_voltage: chain[1], voltage is: 19.961133
2020-10-06 00:27:59 power_api.c:219:get_average_voltage: chain[2], voltage is: 19.875410
2020-10-06 00:27:59 power_api.c:229:get_average_voltage: average voltage is: 19.926435
2020-10-06 00:27:59 driver-btm-api.c:657:increase_freq_slowly: init_freq = 550.00, final_freq = 565.00, freq_step = 5.00, chain = 255
2020-10-06 00:28:02 frequency.c:491:increase_freq_by_frequency_list_slowly: Increase freq slowly for chain 2 to 580
2020-10-06 00:28:02 frequency.c:341:auto_adaption_high_voltage_increase_frequency: auto adaption increase frequency from 565.000000 to 580.000000 @19.60V.
2020-10-06 00:28:02 frequency.c:342:auto_adaption_high_voltage_increase_frequency: index 2 2
2020-10-06 00:28:02 driver-btm-api.c:657:increase_freq_slowly: init_freq = 565.00, final_freq = 580.00, freq_step = 5.00, chain = 2
2020-10-06 00:28:05 frequency.c:499:increase_freq_by_frequency_list_slowly: Increase diff freq slowly for chain 2 to maximum 620
2020-10-06 00:28:05 power_api.c:344:slowly_set_iic_power_to_custom_voltage: slowly setting to voltage: 19.30 ...
2020-10-06 00:28:33 power_api.c:219:get_average_voltage: chain[0], voltage is: 19.667226
2020-10-06 00:28:36 power_api.c:219:get_average_voltage: chain[1], voltage is: 19.679472
2020-10-06 00:28:39 power_api.c:219:get_average_voltage: chain[2], voltage is: 19.605996
2020-10-06 00:28:39 power_api.c:229:get_average_voltage: average voltage is: 19.650898
2020-10-06 00:28:44 driver-btm-api.c:754:set_timeout: freq 620 final timeout=118
2020-10-06 00:28:44 power_api.c:362:slowly_set_iic_power_to_working_voltage: slowly setting to voltage: 18.00 ...
2020-10-06 00:29:31 power_api.c:219:get_average_voltage: chain[0], voltage is: 18.307910
2020-10-06 00:29:33 power_api.c:219:get_average_voltage: chain[1], voltage is: 18.326279
2020-10-06 00:29:34 power_api.c:219:get_average_voltage: chain[2], voltage is: 18.265049
2020-10-06 00:29:34 power_api.c:229:get_average_voltage: average voltage is: 18.299746
2020-10-06 00:29:34 thread.c:617:create_temperature_monitor_thread: create thread
2020-10-06 00:29:34 thread.c:637:create_check_system_status_thread: create thread
2020-10-06 00:29:35 driver-btm-api.c:1988:bitmain_soc_init: Init done!
2020-10-06 00:29:35 driver-btm-api.c:194:set_miner_status: STATUS_INIT
2020-10-06 00:29:41 driver-btm-api.c:194:set_miner_status: STATUS_OKAY
2020-10-06 00:29:45 driver-btm-api.c:1423:dhash_chip_send_job: Verion num 4
2020-10-06 00:59:47 thread.c:164:calc_hashrate_avg: avg rate is 52382.95 in 30 mins
2020-10-06 00:59:47 temperature.c:435:temp_statistics_show:   pcb temp 35~62  chip temp 46~80
2020-10-06 00:59:47 thread.c:245:check_hashrate: latest avg rate < 0.98......
2020-10-06 00:59:47 thread.c:246:check_hashrate: current PCB min temperature 35
2020-10-06 00:59:47 thread.c:247:check_hashrate: current voltage is 18.00V, working voltage is 18.00V
2020-10-06 00:59:47 thread.c:278:check_hashrate: high temp, increase voltage 0.1V/0.2V to 18.10V
2020-10-06 00:59:47 driver-btm-api.c:1999:bitmain_reopen_core: reopen_core start!
2020-10-06 00:59:54 driver-btm-api.c:1183:init_miner_version: miner ID : 800a1dce57408854
2020-10-06 00:59:54 driver-btm-api.c:1189:init_miner_version: FPGA Version = 0xB011
2020-10-06 00:59:55 chain = 0, mode = 1, load_done = false.
2020-10-06 00:59:55 chain = 1, mode = 1, load_done = false.
2020-10-06 00:59:55 chain = 2, mode = 1, load_done = false.
2020-10-06 00:59:56 chain = 0, mode = 1, load_done = false.
2020-10-06 00:59:56 chain = 1, mode = 1, load_done = false.
2020-10-06 00:59:56 chain = 2, mode = 1, load_done = false.
2020-10-06 00:59:57 chain = 0, mode = 1, load_done = false.
2020-10-06 00:59:57 chain = 1, mode = 1, load_done = false.
2020-10-06 00:59:57 chain = 2, mode = 1, load_done = false.
2020-10-06 00:59:58 chain = 0, mode = 1, load_done = false.
2020-10-06 00:59:58 chain = 1, mode = 1, load_done = false.
2020-10-06 00:59:58 chain = 2, mode = 1, load_done = false.
2020-10-06 00:59:59 chain = 0, mode = 1, load_done = false.
2020-10-06 00:59:59 chain = 1, mode = 1, load_done = false.
2020-10-06 00:59:59 chain = 2, mode = 1, load_done = false.
2020-10-06 00:59:59 driver-btm-api.c:835:get_product_id: product_id[0] = 0
2020-10-06 00:59:59 driver-btm-api.c:835:get_product_id: product_id[1] = 0
2020-10-06 00:59:59 driver-btm-api.c:835:get_product_id: product_id[2] = 0
2020-10-06 00:59:59 driver-btm-api.c:786:_set_project_type: project:0
2020-10-06 00:59:59 driver-btm-api.c:811:_set_project_type: Project type: Antminer S17 Pro
2020-10-06 00:59:59 driver-btm-api.c:822:dump_pcb_bom_version: Chain [0] PCB Version: 0x0101
2020-10-06 00:59:59 driver-btm-api.c:823:dump_pcb_bom_version: Chain [0] BOM Version: 0x0103
2020-10-06 00:59:59 driver-btm-api.c:822:dump_pcb_bom_version: Chain [1] PCB Version: 0x0101
2020-10-06 00:59:59 driver-btm-api.c:823:dump_pcb_bom_version: Chain [1] BOM Version: 0x0103
2020-10-06 00:59:59 driver-btm-api.c:822:dump_pcb_bom_version: Chain [2] PCB Version: 0x0101
2020-10-06 00:59:59 driver-btm-api.c:823:dump_pcb_bom_version: Chain [2] BOM Version: 0x0103
2020-10-06 01:00:00 driver-btm-api.c:1841:bitmain_board_init: Fan check passed.
2020-10-06 01:00:03 board.c:36:jump_and_app_check_restore_pic: chain[0] PIC jump to app
2020-10-06 01:00:08 board.c:40:jump_and_app_check_restore_pic: Check chain[0] PIC fw version=0xb9
2020-10-06 01:00:10 board.c:36:jump_and_app_check_restore_pic: chain[1] PIC jump to app
2020-10-06 01:00:13 board.c:40:jump_and_app_check_restore_pic: Check chain[1] PIC fw version=0xb9
2020-10-06 01:00:13 register.c:282:get_register: !!! reg crc error
2020-10-06 01:00:15 board.c:36:jump_and_app_check_restore_pic: chain[2] PIC jump to app

edit: I checked last night and didn't see any markings on the hashboards indicating where they were made. I wonder what the actual rules are for what US customs calls made in China. If all they have to do is send hashboards separate from the main body to Malaysia and have them just plug them together to bypass the tariff, I'd think all of the other manufacturers would have jumped on that to try to capture more of the US market, and Bitmain would have made it easier to order from Malaysia instead of only offering it to larger customers.

Turns out my host has about 25 dead S17 pros, not sure what % of his total that is. We've struck a deal so I'm going to attempt to fix his dead miners, I'll update the thread on what I find.
NotFuzzyWarm
Legendary
*
Offline Offline

Activity: 2422
Merit: 1587


Evil beware: We have waffles!


View Profile
October 07, 2020, 02:18:25 PM
Last edit: October 08, 2020, 01:11:35 AM by frodocooper
 #174

I wonder what the actual rules are for what US customs calls made in China. If all they have to do is send hashboards separate from the main body to Malaysia and have them just plug them together to bypass the tariff, I'd think all of the other manufacturers would have jumped on that...

Not positive but am pretty sure it takes more than sending a plug-together kit of parts to get around the tariffs hence my guess about the boards being stuffed in Malaysia as well PSU's being made there as well. Someone needs to check the Customs category breakdown on them.

- For bitcoin to succeed the community must police itself -    My info useful? Donations welcome! 1FuzzyWc2J8TMqeUQZ8yjE43Rwr7K3cxs9
How a miner mfgr SHOULD operate:  HaggsFIN trip to Canaan
-Support Sidehacks miner development. Donations to:   1BURGERAXHH6Yi6LRybRJK7ybEm5m5HwTr
mikeywith
Legendary
*
Online Online

Activity: 1022
Merit: 3413


be constructive or S.T.F.U


View Profile
October 07, 2020, 05:57:36 PM
 #175

It's reasonably cool here so fans are running around 50%. I'm going to figure out a way to limit cooling to stress test it before I declare it fixed.

Limit the fans speed to 10-20% by following this guide , this used to work on all previous firmware versions but I am not sure about the latest firmware, however, I think it's likely going to work just fine.

By the way, upgrading to the latest firmware means you are now stuck with it forever, I hope you were aware of this before actually doing it.

wndsnb
Sr. Member
****
Offline Offline

Activity: 276
Merit: 337


View Profile
October 07, 2020, 07:54:31 PM
Merited by frodocooper (2)
 #176

...

Thanks! I just put the miner in a box, cut an intake and exhaust hole, and then slowly covered up the intake until I got the temperatures up. But your way is way better obviously ...

I tried it on this miner with the latest firmware and it does still work.

While testing that out, I changed the setting multiple times and ran into an issue where the miner did not come up after applying changes to the configuration page. I saw this once before and figured it was just a fluke, but it happened again. Comes back up with a reboot though, so not much of an issue.

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: 203608K/245760K available (6345K kernel code, 231K rwdata, 1896K rodata, 1024K init, 223K bss, 25768K reserved, 16384K cma-reserved, 0K highmem)
Virtual kernel memory layout:
    vector  : 0xffff0000 - 0xffff1000   (   4 kB)
    fixmap  : 0xffc00000 - 0xfff00000   (3072 kB)
    vmalloc : 0xcf800000 - 0xff800000   ( 768 MB)
    lowmem  : 0xc0000000 - 0xcf000000   ( 240 MB)
    pkmap   : 0xbfe00000 - 0xc0000000   (   2 MB)
    modules : 0xbf000000 - 0xbfe00000   (  14 MB)
      .text : 0xc0008000 - 0xc090c424   (9234 kB)
      .init : 0xc0a00000 - 0xc0b00000   (1024 kB)
      .data : 0xc0b00000 - 0xc0b39fe0   ( 232 kB)
       .bss : 0xc0b39fe0 - 0xc0b71c28   ( 224 kB)
Preemptible hierarchical RCU implementation.
Build-time adjustment of leaf fanout to 32.
RCU restricting CPUs from NR_CPUS=4 to nr_cpu_ids=2.
RCU: Adjusting geometry for rcu_fanout_leaf=32, nr_cpu_ids=2
NR_IRQS:16 nr_irqs:16 16
efuse mapped to cf800000
ps7-slcr mapped to cf802000
L2C: platform modifies aux control register: 0x72360000 -> 0x72760000
L2C: DT/platform modifies aux control register: 0x72360000 -> 0x72760000
L2C-310 erratum 769419 enabled
L2C-310 enabling early BRESP for Cortex-A9
L2C-310 full line of zeros enabled for Cortex-A9
L2C-310 ID prefetch enabled, offset 1 lines
L2C-310 dynamic clock gating enabled, standby mode enabled
L2C-310 cache controller enabled, 8 ways, 512 kB
L2C-310: CACHE_ID 0x410000c8, AUX_CTRL 0x76760001
zynq_clock_init: clkc starts at cf802100
Zynq clock init
sched_clock: 64 bits at 333MHz, resolution 3ns, wraps every 4398046511103ns
clocksource: arm_global_timer: mask: 0xffffffffffffffff max_cycles: 0x4ce07af025, max_idle_ns: 440795209040 ns
Switching to timer-based delay loop, resolution 3ns
clocksource: ttc_clocksource: mask: 0xffff max_cycles: 0xffff, max_idle_ns: 537538477 ns
ps7-ttc #0 at cf80a000, irq=18
Console: colour dummy device 80x30
Calibrating delay loop (skipped), value calculated using timer frequency.. 666.66 BogoMIPS (lpj=3333333)
pid_max: default: 32768 minimum: 301
Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
CPU: Testing write buffer coherency: ok
CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
Setting up static identity map for 0x100000 - 0x100058
CPU1: failed to boot: -1
Brought up 1 CPUs
SMP: Total of 1 processors activated (666.66 BogoMIPS).
CPU: All CPU(s) started in SVC mode.
devtmpfs: initialized
VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4
clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
pinctrl core: initialized pinctrl subsystem
NET: Registered protocol family 16
DMA: preallocated 256 KiB pool for atomic coherent allocations
cpuidle: using governor menu
hw-breakpoint: found 5 (+1 reserved) breakpoint and 1 watchpoint registers.
hw-breakpoint: maximum watchpoint size is 4 bytes.
zynq-ocm f800c000.ps7-ocmc: ZYNQ OCM pool: 256 KiB @ 0xcf880000
vgaarb: loaded
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
media: Linux media interface: v0.10
Linux video capture interface: v2.00
pps_core: LinuxPPS API ver. 1 registered
pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
PTP clock support registered
EDAC MC: Ver: 3.0.0
Advanced Linux Sound Architecture Driver Initialized.
clocksource: Switched to clocksource arm_global_timer
NET: Registered protocol family 2
TCP established hash table entries: 2048 (order: 1, 8192 bytes)
TCP bind hash table entries: 2048 (order: 2, 16384 bytes)
TCP: Hash tables configured (established 2048 bind 2048)
UDP hash table entries: 256 (order: 1, 8192 bytes)
UDP-Lite hash table entries: 256 (order: 1, 8192 bytes)
NET: Registered protocol family 1
RPC: Registered named UNIX socket transport module.
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
PCI: CLS 0 bytes, default 64
Trying to unpack rootfs image as initramfs...
rootfs image is not initramfs (no cpio magic); looks like an initrd
Freeing initrd memory: 12728K (cce93000 - 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: 3/1, WL threshold: 4096, image sequence number: 1099087952
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 CD1BC056-7E24-4E3E-BCAF-EAA178A77B8B, 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: 974/212, WL threshold: 4096, image sequence number: 4185749592
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 4829CF2C-7435-4146-B2FD-0826AAE8443A, 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 = 0xab013
In fpga mem driver!
request_mem_region OK!
fpga mem virtual address is 0xd2000000
random: nonblocking pool is initialized
Oct  7 19:00:19 (none) local0.info bmminer: (null) 0: invalid nonce - HW error
Oct  7 19:00:19 (none) local0.info bmminer: (null) 0: invalid nonce - HW error
Oct  7 19:00:19 (none) local0.info bmminer: (null) 0: invalid nonce - HW error
Oct  7 19:00:19 (none) local0.info bmminer: (null) 0: invalid nonce - HW error
Oct  7 19:00:19 (none) local0.info bmminer: (null) 0: invalid nonce - HW error
Oct  7 19:00:19 (none) local0.info bmminer: (null) 0: invalid nonce - HW error
Oct  7 19:00:19 (none) local0.info bmminer: (null) 0: invalid nonce - HW error
Oct  7 19:00:19 (none) local0.info bmminer: (null) 0: invalid nonce - HW error
Oct  7 19:00:19 (none) local0.info bmminer: (null) 0: invalid nonce - HW error
Oct  7 19:00:19 (none) local0.info bmminer: (null) 0: invalid nonce - HW error
Oct  7 19:00:19 (none) local0.info bmminer: (null) 0: invalid nonce - HW error
Oct  7 19:00:19 (none) local0.info bmminer: (null) 0: invalid nonce - HW error
Oct  7 19:00:19 (none) local0.info bmminer: (null) 0: invalid nonce - HW error
Oct  7 19:00:19 (none) local0.info bmminer: (null) 0: invalid nonce - HW error
Oct  7 19:00:19 (none) local0.info bmminer: (null) 0: invalid nonce - HW error
Oct  7 19:00:19 (none) local0.info bmminer: (null) 0: invalid nonce - HW error
Oct  7 19:00:19 (none) local0.info bmminer: (null) 0: invalid nonce - HW error
Oct  7 19:00:19 (none) local0.info bmminer: (null) 0: invalid nonce - HW error
Oct  7 19:00:19 (none) local0.info bmminer: (null) 0: invalid nonce - HW error
Oct  7 19:00:19 (none) local0.info bmminer: (null) 0: invalid nonce - HW error
Oct  7 19:00:19 (none) local0.info bmminer: (null) 0: invalid nonce - HW error
Oct  7 19:00:19 (none) local0.info bmminer: (null) 0: invalid nonce - HW error
Oct  7 19:00:19 (none) local0.info bmminer: (null) 0: invalid nonce - HW error
Oct  7 19:00:19 (none) local0.info bmminer: (null) 0: invalid nonce - HW error
Oct  7 19:00:19 (none) local0.info bmminer: (null) 0: invalid nonce - HW error
Oct  7 19:00:19 (none) local0.info bmminer: (null) 0: invalid nonce - HW error
Oct  7 19:00:19 (none) local0.info bmminer: (null) 0: invalid nonce - HW error
Oct  7 19:00:19 (none) local0.info bmminer: (null) 0: invalid nonce - HW error
Oct  7 19:00:19 (none) local0.info bmminer: (null) 0: invalid nonce - HW error
Oct  7 19:00:19 (none) local0.info bmminer: (null) 0: invalid nonce - HW error
Oct  7 19:00:19 (none) local0.info bmminer: (null) 0: invalid nonce - HW error
Oct  7 19:00:19 (none) local0.info bmminer: (null) 0: invalid nonce - HW error
Oct  7 19:00:19 (none) local0.info bmminer: (null) 0: invalid nonce - HW error
Oct  7 19:00:19 (none) local0.info bmminer: (null) 0: invalid nonce - HW error
Oct  7 19:00:19 (none) local0.info bmminer: (null) 0: invalid nonce - HW error
Oct  7 19:00:19 (none) local0.info bmminer: (null) 0: invalid nonce - HW error
Oct  7 19:00:19 (none) local0.info bmminer: (null) 0: invalid nonce - HW error
Oct  7 19:00:19 (none) local0.info bmminer: (null) 0: invalid nonce - HW error
Oct  7 19:00:19 (none) local0.info bmminer: (null) 0: invalid nonce - HW error
Oct  7 19:00:19 (none) local0.info bmminer: (null) 0: invalid nonce - HW error
Oct  7 19:00:19 (none) local0.info bmminer: (null) 0: invalid nonce - HW error


[deleted]


Oct  7 19:00:30 (none) local0.info bmminer: (null) 0: invalid nonce - HW error
Oct  7 19:00:30 (none) local0.info bmminer: (null) 0: invalid nonce - HW error
Oct  7 19:00:30 (none) local0.info bmminer: (null) 0: invalid nonce - HW error
Oct  7 19:00:30 (none) local0.info bmminer: (null) 0: invalid nonce - HW error
2020-10-07 18:53:36 driver-btm-api.c:542:init_freq_mode: This is scan-user version
2020-10-07 18:53:36 driver-btm-api.c:1877:bitmain_soc_init: opt_multi_version     = 1
2020-10-07 18:53:36 driver-btm-api.c:1878:bitmain_soc_init: opt_bitmain_ab        = 1
2020-10-07 18:53:36 driver-btm-api.c:1879:bitmain_soc_init: opt_bitmain_work_mode = 0
2020-10-07 18:53:36 driver-btm-api.c:1880:bitmain_soc_init: Miner compile time: Mon Apr 27 13:25:08 CST 2020 type: Antminer S17 Pro
2020-10-07 18:53:36 driver-btm-api.c:1881:bitmain_soc_init: commit version: d22f356 2020-04-24 18:30:49, build by: lol 2020-04-27 13:31:45
2020-10-07 18:53:36 driver-btm-api.c:1691:show_sn: no SN got, please write SN to /nvdata/sn
2020-10-07 18:53:36 driver-btm-api.c:1040:miner_device_init: Detect 256MB control board of XILINX
2020-10-07 18:53:36 driver-btm-api.c:988:init_fan_parameter: fan_eft : 1  fan_pwm : 30
2020-10-07 18:53:36 thread.c:783:create_read_nonce_reg_thread: create thread
2020-10-07 18:53:42 driver-btm-api.c:972:init_miner_version: miner ID : 800a1dce57408854
2020-10-07 18:53:42 driver-btm-api.c:978:init_miner_version: FPGA Version = 0xB013
2020-10-07 18:53:47 driver-btm-api.c:616:get_product_id: product_id[0] = 0
2020-10-07 18:53:47 driver-btm-api.c:616:get_product_id: product_id[1] = 0
2020-10-07 18:53:47 driver-btm-api.c:616:get_product_id: product_id[2] = 0
2020-10-07 18:53:47 driver-btm-api.c:560:_set_project_type: project:0
2020-10-07 18:53:47 driver-btm-api.c:585:_set_project_type: Project type: Antminer S17 Pro
2020-10-07 18:53:47 driver-btm-api.c:596:dump_pcb_bom_version: Chain [0] PCB Version: 0x0101
2020-10-07 18:53:47 driver-btm-api.c:597:dump_pcb_bom_version: Chain [0] BOM Version: 0x0103
2020-10-07 18:53:47 driver-btm-api.c:596:dump_pcb_bom_version: Chain [1] PCB Version: 0x0101
2020-10-07 18:53:47 driver-btm-api.c:597:dump_pcb_bom_version: Chain [1] BOM Version: 0x0103
2020-10-07 18:53:47 driver-btm-api.c:596:dump_pcb_bom_version: Chain [2] PCB Version: 0x0101
2020-10-07 18:53:47 driver-btm-api.c:597:dump_pcb_bom_version: Chain [2] BOM Version: 0x0103
2020-10-07 18:53:48 driver-btm-api.c:1802:bitmain_board_init: Fan check passed.
2020-10-07 18:53:49 board.c:36:jump_and_app_check_restore_pic: chain[0] PIC jump to app
2020-10-07 18:53:51 board.c:40:jump_and_app_check_restore_pic: Check chain[0] PIC fw version=0xb9
2020-10-07 18:53:53 board.c:36:jump_and_app_check_restore_pic: chain[1] PIC jump to app
2020-10-07 18:53:55 board.c:40:jump_and_app_check_restore_pic: Check chain[1] PIC fw version=0xb9
2020-10-07 18:53:56 board.c:36:jump_and_app_check_restore_pic: chain[2] PIC jump to app
2020-10-07 18:53:58 board.c:40:jump_and_app_check_restore_pic: Check chain[2] PIC fw version=0xb9
2020-10-07 18:53:58 thread.c:778:create_pic_heart_beat_thread: create thread
2020-10-07 18:53:58 power_api.c:207:power_init: Power init:
2020-10-07 18:53:58 power_api.c:208:power_init: current_voltage_raw = 0
2020-10-07 18:53:58 power_api.c:209:power_init: highest_voltage_raw = 2100
2020-10-07 18:53:58 power_api.c:210:power_init: working_voltage_raw = 1830
2020-10-07 18:53:58 power_api.c:211:power_init: higher_voltage_raw  = 1950
2020-10-07 18:53:58 driver-btm-api.c:1812:bitmain_board_init: Enter 30s sleep to make sure power release finish.
2020-10-07 18:54:30 power_api.c:251:set_to_highest_voltage: Set to voltage raw 2100, one step.
2020-10-07 18:54:32 power_api.c:87:check_voltage_multi: retry time: 0
2020-10-07 18:54:33 power_api.c:37:_get_avg_voltage: chain = 0, voltage = 21.369433
2020-10-07 18:54:34 power_api.c:37:_get_avg_voltage: chain = 1, voltage = 21.424541
2020-10-07 18:54:35 power_api.c:37:_get_avg_voltage: chain = 2, voltage = 21.289834
2020-10-07 18:54:35 power_api.c:50:_get_avg_voltage: average_voltage = 21.361269
2020-10-07 18:54:35 power_api.c:68:check_voltage: target_vol = 21.00, actural_vol = 21.36, check voltage passed.
2020-10-07 18:54:35 uart.c:71:set_baud: set fpga_baud to 115200
2020-10-07 18:54:46 driver-btm-api.c:915:check_asic_number_with_power_on: Chain[0]: find 48 asic, times 0
2020-10-07 18:54:57 driver-btm-api.c:915:check_asic_number_with_power_on: Chain[1]: find 48 asic, times 0
2020-10-07 18:55:08 driver-btm-api.c:915:check_asic_number_with_power_on: Chain[2]: find 48 asic, times 0
2020-10-07 18:55:13 driver-btm-api.c:345:set_order_clock: chain[0]: set order clock, stragegy 3
2020-10-07 18:55:14 driver-btm-api.c:345:set_order_clock: chain[1]: set order clock, stragegy 3
2020-10-07 18:55:14 driver-btm-api.c:345:set_order_clock: chain[2]: set order clock, stragegy 3
2020-10-07 18:55:14 driver-hash-chip.c:502:set_clock_delay_control: core_data = 0x34
2020-10-07 18:55:14 uart.c:71:set_baud: set fpga_baud to 3000000
2020-10-07 18:55:14 driver-btm-api.c:1574:check_clock_counter: freq 50 clock_counter_limit 6
2020-10-07 18:55:16 uart.c:71:set_baud: set fpga_baud to 115200
2020-10-07 18:55:16 voltage[0] = 1700
2020-10-07 18:55:16 voltage[1] = 1700
2020-10-07 18:55:16 voltage[2] = 1700
2020-10-07 18:55:16 power_api.c:219:set_working_voltage_raw: working_voltage_raw = 1700
2020-10-07 18:55:17 temperature.c:281:calibrate_temp_sensor_one_chain: Temperature sensor calibration: chain 0 success.
2020-10-07 18:55:19 temperature.c:281:calibrate_temp_sensor_one_chain: Temperature sensor calibration: chain 1 success.
2020-10-07 18:55:20 temperature.c:281:calibrate_temp_sensor_one_chain: Temperature sensor calibration: chain 2 success.
2020-10-07 18:55:20 uart.c:71:set_baud: set fpga_baud to 6000000
2020-10-07 18:55:22 driver-btm-api.c:245:check_bringup_temp: Bring up temperature is 31
2020-10-07 18:55:22 thread.c:798:create_check_miner_status_thread: create thread
2020-10-07 18:55:22 thread.c:788:create_set_miner_status_thread: create thread
2020-10-07 18:55:22 thread.c:773:create_temperature_monitor_thread: create thread
2020-10-07 18:55:22 frequency.c:749:inc_freq_with_fixed_vco: chain = 255, freq = 425, is_higher_voltage = true
2020-10-07 18:55:22 power_api.c:287:set_to_voltage_by_steps: Set to voltage raw 2020, step by step.
2020-10-07 18:55:40 power_api.c:87:check_voltage_multi: retry time: 0
2020-10-07 18:55:41 power_api.c:37:_get_avg_voltage: chain = 0, voltage = 20.530576
2020-10-07 18:55:42 power_api.c:37:_get_avg_voltage: chain = 1, voltage = 20.573437
2020-10-07 18:55:43 power_api.c:37:_get_avg_voltage: chain = 2, voltage = 20.469345
2020-10-07 18:55:43 power_api.c:50:_get_avg_voltage: average_voltage = 20.524453
2020-10-07 18:55:43 power_api.c:68:check_voltage: target_vol = 20.20, actural_vol = 20.52, check voltage passed.
2020-10-07 18:56:15 frequency.c:801:inc_freq_with_fixed_step: chain = 0, freq_start = 425, freq_end = 425, freq_step = 5, is_higher_voltage = true
2020-10-07 18:56:15 frequency.c:801:inc_freq_with_fixed_step: chain = 1, freq_start = 425, freq_end = 425, freq_step = 5, is_higher_voltage = true
2020-10-07 18:56:15 frequency.c:801:inc_freq_with_fixed_step: chain = 2, freq_start = 425, freq_end = 425, freq_step = 5, is_higher_voltage = true
2020-10-07 18:56:15 frequency.c:801:inc_freq_with_fixed_step: chain = 2, freq_start = 425, freq_end = 450, freq_step = 5, is_higher_voltage = true
2020-10-07 18:56:17 power_api.c:287:set_to_voltage_by_steps: Set to voltage raw 1920, step by step.
2020-10-07 18:56:33 power_api.c:87:check_voltage_multi: retry time: 0
2020-10-07 18:56:34 power_api.c:37:_get_avg_voltage: chain = 0, voltage = 19.514150
2020-10-07 18:56:35 power_api.c:37:_get_avg_voltage: chain = 1, voltage = 19.544765
2020-10-07 18:56:36 power_api.c:37:_get_avg_voltage: chain = 2, voltage = 19.471289
2020-10-07 18:56:36 power_api.c:50:_get_avg_voltage: average_voltage = 19.510068
2020-10-07 18:56:36 power_api.c:68:check_voltage: target_vol = 19.20, actural_vol = 19.51, check voltage passed.
2020-10-07 18:56:36 frequency.c:618:inc_asic_diff_freq_by_steps: chain = 0, start = 425, freq_step = 5
2020-10-07 18:56:40 frequency.c:618:inc_asic_diff_freq_by_steps: chain = 1, start = 425, freq_step = 5
2020-10-07 18:56:43 frequency.c:618:inc_asic_diff_freq_by_steps: chain = 2, start = 450, freq_step = 5
2020-10-07 18:56:50 driver-btm-api.c:528:set_timeout: freq = 510, percent = 90, hcn = 73728, timeout = 144
2020-10-07 18:56:50 power_api.c:269:set_to_working_voltage_by_steps: Set to voltage raw 1700, step by step.
2020-10-07 18:57:11 power_api.c:87:check_voltage_multi: retry time: 0
2020-10-07 18:57:12 power_api.c:37:_get_avg_voltage: chain = 0, voltage = 17.273115
2020-10-07 18:57:13 power_api.c:37:_get_avg_voltage: chain = 1, voltage = 17.291484
2020-10-07 18:57:14 power_api.c:37:_get_avg_voltage: chain = 2, voltage = 17.211885
2020-10-07 18:57:14 power_api.c:50:_get_avg_voltage: average_voltage = 17.258828
2020-10-07 18:57:14 power_api.c:68:check_voltage: target_vol = 17.00, actural_vol = 17.26, check voltage passed.
2020-10-07 18:57:14 thread.c:793:create_check_system_status_thread: create thread
2020-10-07 18:57:15 driver-btm-api.c:1988:bitmain_soc_init: Init done!
2020-10-07 18:57:15 driver-btm-api.c:198:set_miner_status: STATUS_INIT
2020-10-07 18:57:20 driver-btm-api.c:198:set_miner_status: STATUS_OKAY
2020-10-07 18:57:21 frequency.c:216:get_ideal_hash_rate_GH: ideal_hash_rate = 44486
2020-10-07 18:57:21 frequency.c:236:get_sale_hash_rate_GH: sale_hash_rate = 44000
2020-10-07 18:57:24 driver-btm-api.c:1199:dhash_chip_send_job: Version num 4
2020-10-07 18:57:33 register.c:313:get_register: !!! REG_TYPE = 1. 842137602
2020-10-07 18:57:33 register.c:313:get_register: !!! REG_TYPE = 1. 607911938
2020-10-07 18:57:33 register.c:313:get_register: !!! REG_TYPE = 1. 776667138
2020-10-07 18:57:33 register.c:313:get_register: !!! REG_TYPE = 1. 877985794
2020-10-07 18:57:33 register.c:313:get_register: !!! REG_TYPE = 1. 962199554
2020-10-07 18:57:33 register.c:313:get_register: !!! REG_TYPE = 1. 996409346
2020-10-07 18:57:33 register.c:313:get_register: !!! REG_TYPE = 1. 778960898
2020-10-07 18:57:33 register.c:313:get_register: !!! REG_TYPE = 1. 1014169602
2020-10-07 18:57:33 register.c:313:get_register: !!! REG_TYPE = 1. 712835074
2020-10-07 18:57:33 register.c:313:get_register: !!! REG_TYPE = 1. 830930946
2020-10-07 18:57:33 register.c:313:get_register: !!! REG_TYPE = 1. 1066139650
2020-10-07 18:57:33 register.c:313:get_register: !!! REG_TYPE = 1. 764477442
2020-10-07 18:57:33 register.c:313:get_register: !!! REG_TYPE = 1. 647364610
2020-10-07 18:57:33 register.c:313:get_register: !!! REG_TYPE = 1. 580911106
2020-10-07 18:57:33 register.c:313:get_register: !!! REG_TYPE = 1. 983891970
2020-10-07 18:57:33 register.c:313:get_register: !!! REG_TYPE = 1. 799997954
2020-10-07 18:57:33 register.c:313:get_register: !!! REG_TYPE = 1. 867762178

[deleted]

2020-10-07 18:57:35 register.c:313:get_register: !!! REG_TYPE = 1. 835518466
2020-10-07 18:57:35 register.c:313:get_register: !!! REG_TYPE = 1. 669384706
2020-10-07 18:57:35 register.c:313:get_register: !!! REG_TYPE = 1. 867762178
2020-10-07 18:57:35 register.c:313:get_register: !!! REG_TYPE = 1. 669384706
2020-10-07 18:57:35 register.c:313:get_register: !!! REG_TYPE = 1. 974389250
2020-10-07 18:57:35 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 0, chip = 55, reg = 0
2020-10-07 18:57:35 register.c:313:get_register: !!! REG_TYPE = 1. 607911938
2020-10-07 18:57:35 register.c:313:get_register: !!! REG_TYPE = 1. 776667138
2020-10-07 18:57:35 register.c:313:get_register: !!! REG_TYPE = 1. 877985794
2020-10-07 18:57:35 register.c:313:get_register: !!! REG_TYPE = 1. 962199554

[deleted]

2020-10-07 18:57:35 register.c:313:get_register: !!! REG_TYPE = 1. 799997954
2020-10-07 18:57:35 register.c:313:get_register: !!! REG_TYPE = 1. 867762178
2020-10-07 18:57:35 register.c:313:get_register: !!! REG_TYPE = 1. 669384706
2020-10-07 18:57:35 register.c:313:get_register: !!! REG_TYPE = 1. 1429907970
2020-10-07 18:57:35 register.c:313:get_register: !!! REG_TYPE = 1. 607911938
2020-10-07 18:57:35 register.c:313:get_register: !!! REG_TYPE = 1. 877985794
2020-10-07 18:57:35 register.c:313:get_register: !!! REG_TYPE = 1. 647364610
2020-10-07 18:57:35 register.c:313:get_register: !!! REG_TYPE = 1. 983891970
2020-10-07 18:57:35 register.c:313:get_register: !!! REG_TYPE = 1. 799997954
2020-10-07 18:57:35 register.c:313:get_register: !!! REG_TYPE = 1. 867762178
2020-10-07 18:57:35 register.c:313:get_register: !!! REG_TYPE = 1. 951975938
2020-10-07 18:57:35 register.c:313:get_register: !!! REG_TYPE = 1. 835518466
2020-10-07 18:57:35 register.c:313:get_register: !!! REG_TYPE = 1. 669384706
2020-10-07 18:57:35 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 55, reg = 28, got chain = 2, chip = 170, reg = 85
2020-10-07 18:57:35 register.c:313:get_register: !!! REG_TYPE = 1. 842137602
2020-10-07 18:57:35 register.c:313:get_register: !!! REG_TYPE = 1. 607911938
2020-10-07 18:57:35 register.c:313:get_register: !!! REG_TYPE = 1. 776667138
2020-10-07 18:57:35 register.c:313:get_register: !!! REG_TYPE = 1. 877985794
2020-10-07 18:57:35 register.c:313:get_register: !!! REG_TYPE = 1. 996409346

[deleted]


2020-10-07 18:57:37 register.c:313:get_register: !!! REG_TYPE = 1. 669384706
2020-10-07 18:57:37 register.c:313:get_register: !!! REG_TYPE = 1. 830930946
2020-10-07 18:57:37 register.c:313:get_register: !!! REG_TYPE = 1. 669384706
2020-10-07 18:57:38 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 40, reg = 28, got chain = 0, chip = 55, reg = 28
2020-10-07 18:57:38 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 40, reg = 28, got chain = 0, chip = 55, reg = 28
2020-10-07 18:57:38 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 40, reg = 28, got chain = 0, chip = 55, reg = 28
2020-10-07 18:57:38 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 40, reg = 28, got chain = 0, chip = 55, reg = 28
2020-10-07 18:57:38 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 40, reg = 28, got chain = 0, chip = 55, reg = 28
2020-10-07 18:57:38 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 40, reg = 28, got chain = 0, chip = 55, reg = 28
2020-10-07 18:57:38 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 40, reg = 28, got chain = 0, chip = 55, reg = 28
2020-10-07 18:57:38 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 40, reg = 28, got chain = 0, chip = 55, reg = 28
2020-10-07 18:57:38 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 40, reg = 28, got chain = 0, chip = 55, reg = 28
2020-10-07 18:57:38 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 40, reg = 28, got chain = 0, chip = 55, reg = 28
2020-10-07 18:57:38 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 40, reg = 28, got chain = 0, chip = 55, reg = 28
2020-10-07 18:57:38 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 40, reg = 28, got chain = 0, chip = 55, reg = 28
2020-10-07 18:57:38 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 40, reg = 28, got chain = 0, chip = 55, reg = 28
2020-10-07 18:57:38 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 40, reg = 28, got chain = 0, chip = 55, reg = 28
2020-10-07 18:57:38 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 40, reg = 28, got chain = 0, chip = 55, reg = 28

[deleted]

2020-10-07 18:57:39 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 40, reg = 28, got chain = 0, chip = 55, reg = 28
2020-10-07 18:57:39 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 40, reg = 28, got chain = 0, chip = 55, reg = 28
2020-10-07 18:57:39 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 40, reg = 28, got chain = 0, chip = 55, reg = 28
2020-10-07 18:57:39 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 40, reg = 28, got chain = 0, chip = 55, reg = 28
2020-10-07 18:57:39 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 40, reg = 28, got chain = 0, chip = 55, reg = 28
2020-10-07 18:57:39 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 40, reg = 28, got chain = 0, chip = 55, reg = 28
2020-10-07 18:57:39 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 1, chip = 40, reg = 1
2020-10-07 18:57:39 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 180, reg = 28, got chain = 0, chip = 55, reg = 28
2020-10-07 18:57:39 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 180, reg = 28, got chain = 0, chip = 55, reg = 28
2020-10-07 18:57:39 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 180, reg = 28, got chain = 0, chip = 55, reg = 28

[deleted]


2020-10-07 18:57:39 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 180, reg = 28, got chain = 0, chip = 55, reg = 28
2020-10-07 18:57:39 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 180, reg = 28, got chain = 0, chip = 55, reg = 28
2020-10-07 18:57:39 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 180, reg = 28, got chain = 0, chip = 55, reg = 28
2020-10-07 18:57:39 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 180, reg = 28, got chain = 0, chip = 55, reg = 28
2020-10-07 18:57:39 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 2, chip = 180, reg = 0
2020-10-07 18:57:39 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 180, reg = 28, got chain = 0, chip = 55, reg = 28
2020-10-07 18:57:39 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 180, reg = 28, got chain = 0, chip = 55, reg = 28
2020-10-07 18:57:39 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 180, reg = 28, got chain = 0, chip = 55, reg = 28


[deleted]


2020-10-07 18:57:41 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 180, reg = 28, got chain = 0, chip = 40, reg = 28
2020-10-07 18:57:41 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 180, reg = 28, got chain = 0, chip = 40, reg = 28
2020-10-07 18:57:41 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 180, reg = 28, got chain = 0, chip = 40, reg = 28
2020-10-07 18:57:41 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 2, chip = 180, reg = 1
2020-10-07 18:57:41 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 195, reg = 28, got chain = 0, chip = 40, reg = 28
2020-10-07 18:57:41 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 195, reg = 28, got chain = 0, chip = 40, reg = 28
2020-10-07 18:57:41 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 195, reg = 28, got chain = 0, chip = 40, reg = 28
2020-10-07 18:57:41 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 195, reg = 28, got chain = 0, chip = 40, reg = 28
2020-10-07 18:57:41 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 195, reg = 28, got chain = 0, chip = 40, reg = 28
2020-10-07 18:57:41 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 195, reg = 28, got chain = 0, chip = 40, reg = 28
2020-10-07 18:57:41 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 195, reg = 28, got chain = 0, chip = 40, reg = 28
2020-10-07 18:57:41 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 195, reg = 28, got chain = 0, chip = 40, reg = 28
2020-10-07 18:57:41 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 195, reg = 28, got chain = 0, chip = 40, reg = 28
2020-10-07 18:57:41 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 195, reg = 28, got chain = 0, chip = 40, reg = 28
2020-10-07 18:57:41 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 195, reg = 28, got chain = 0, chip = 40, reg = 28
2020-10-07 18:57:41 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 195, reg = 28, got chain = 0, chip = 40, reg = 28
2020-10-07 18:57:41 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 195, reg = 28, got chain = 0, chip = 40, reg = 28
2020-10-07 18:57:41 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 195, reg = 28, got chain = 0, chip = 40, reg = 28
2020-10-07 18:57:41 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 195, reg = 28, got chain = 0, chip = 40, reg = 28
2020-10-07 18:57:41 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 195, reg = 28, got chain = 0, chip = 40, reg = 28
2020-10-07 18:57:41 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 195, reg = 28, got chain = 0, chip = 40, reg = 28
2020-10-07 18:57:41 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 195, reg = 28, got chain = 0, chip = 40, reg = 28
2020-10-07 18:57:41 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 195, reg = 28, got chain = 0, chip = 40, reg = 28
2020-10-07 18:57:41 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 195, reg = 28, got chain = 0, chip = 40, reg = 28
2020-10-07 18:57:41 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 195, reg = 28, got chain = 0, chip = 40, reg = 28
2020-10-07 18:57:41 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 195, reg = 28, got chain = 0, chip = 40, reg = 28
2020-10-07 18:57:41 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 195, reg = 28, got chain = 0, chip = 40, reg = 28
2020-10-07 18:57:41 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 3, chip = 195, reg = 0
2020-10-07 18:57:41 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 195, reg = 28, got chain = 0, chip = 40, reg = 28
2020-10-07 18:57:41 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 195, reg = 28, got chain = 0, chip = 40, reg = 28
2020-10-07 18:57:42 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 195, reg = 28, got chain = 0, chip = 40, reg = 28
2020-10-07 18:57:42 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 195, reg = 28, got chain = 0, chip = 40, reg = 28
2020-10-07 18:57:42 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 195, reg = 28, got chain = 0, chip = 40, reg = 28
2020-10-07 18:57:42 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 195, reg = 28, got chain = 0, chip = 40, reg = 28
2020-10-07 18:57:42 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 195, reg = 28, got chain = 0, chip = 40, reg = 28
2020-10-07 18:57:42 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 195, reg = 28, got chain = 0, chip = 40, reg = 28
2020-10-07 18:57:42 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 195, reg = 28, got chain = 0, chip = 40, reg = 28
2020-10-07 18:57:42 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 195, reg = 28, got chain = 0, chip = 40, reg = 28
2020-10-07 18:57:42 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 195, reg = 28, got chain = 0, chip = 40, reg = 28
2020-10-07 18:57:42 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 195, reg = 28, got chain = 0, chip = 40, reg = 28
2020-10-07 18:57:42 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 195, reg = 28, got chain = 0, chip = 180, reg = 28
2020-10-07 18:57:42 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 195, reg = 28, got chain = 0, chip = 180, reg = 28
2020-10-07 18:57:42 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 195, reg = 28, got chain = 0, chip = 180, reg = 28
2020-10-07 18:57:42 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 195, reg = 28, got chain = 0, chip = 180, reg = 28
2020-10-07 18:57:42 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 195, reg = 28, got chain = 0, chip = 180, reg = 28
2020-10-07 18:57:42 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 195, reg = 28, got chain = 0, chip = 180, reg = 28
2020-10-07 18:57:42 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 195, reg = 28, got chain = 0, chip = 180, reg = 28
2020-10-07 18:57:42 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 195, reg = 28, got chain = 0, chip = 180, reg = 28
2020-10-07 18:57:42 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 195, reg = 28, got chain = 0, chip = 180, reg = 28
2020-10-07 18:57:42 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 195, reg = 28, got chain = 0, chip = 180, reg = 28
2020-10-07 18:57:42 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 195, reg = 28, got chain = 0, chip = 180, reg = 28
2020-10-07 18:57:42 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 195, reg = 28, got chain = 0, chip = 180, reg = 28
2020-10-07 18:57:42 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 195, reg = 28, got chain = 0, chip = 180, reg = 28
2020-10-07 18:57:42 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 195, reg = 28, got chain = 0, chip = 180, reg = 28
2020-10-07 18:57:42 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 195, reg = 28, got chain = 0, chip = 180, reg = 28
2020-10-07 18:57:42 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 195, reg = 28, got chain = 0, chip = 180, reg = 28
2020-10-07 18:57:42 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 195, reg = 28, got chain = 0, chip = 180, reg = 28
2020-10-07 18:57:42 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 195, reg = 28, got chain = 0, chip = 180, reg = 28
2020-10-07 18:57:42 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 195, reg = 28, got chain = 0, chip = 180, reg = 28
2020-10-07 18:57:42 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 195, reg = 28, got chain = 0, chip = 180, reg = 28
2020-10-07 18:57:42 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 195, reg = 28, got chain = 0, chip = 180, reg = 28
2020-10-07 18:57:42 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 195, reg = 28, got chain = 0, chip = 180, reg = 28
2020-10-07 18:57:42 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 195, reg = 28, got chain = 0, chip = 180, reg = 28
2020-10-07 18:57:42 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 195, reg = 28, got chain = 0, chip = 180, reg = 28
2020-10-07 18:57:42 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 195, reg = 28, got chain = 0, chip = 180, reg = 28
2020-10-07 18:57:42 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 195, reg = 28, got chain = 0, chip = 180, reg = 28
2020-10-07 18:57:43 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 195, reg = 28, got chain = 0, chip = 180, reg = 28
2020-10-07 18:57:43 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 195, reg = 28, got chain = 0, chip = 180, reg = 28
2020-10-07 18:57:43 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 195, reg = 28, got chain = 0, chip = 180, reg = 28
2020-10-07 18:57:43 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 195, reg = 28, got chain = 0, chip = 180, reg = 28
2020-10-07 18:57:43 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 195, reg = 28, got chain = 0, chip = 180, reg = 28
2020-10-07 18:57:43 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 195, reg = 28, got chain = 0, chip = 180, reg = 28
2020-10-07 18:57:43 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 195, reg = 28, got chain = 0, chip = 180, reg = 28
2020-10-07 18:57:43 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 195, reg = 28, got chain = 0, chip = 180, reg = 28
2020-10-07 18:57:43 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 195, reg = 28, got chain = 0, chip = 180, reg = 28
2020-10-07 18:57:43 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 195, reg = 28, got chain = 0, chip = 180, reg = 28
2020-10-07 18:57:43 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 195, reg = 28, got chain = 0, chip = 180, reg = 28
2020-10-07 18:57:43 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 195, reg = 28, got chain = 0, chip = 180, reg = 28
2020-10-07 18:57:43 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 195, reg = 28, got chain = 0, chip = 180, reg = 28
2020-10-07 18:57:43 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 195, reg = 28, got chain = 0, chip = 180, reg = 28
2020-10-07 18:57:43 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 195, reg = 28, got chain = 0, chip = 180, reg = 28
2020-10-07 18:57:43 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 3, chip = 195, reg = 1
2020-10-07 18:57:43 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 1, chip = 55, reg = 28, got chain = 0, chip = 180, reg = 28
2020-10-07 18:57:43 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 1, chip = 55, reg = 28, got chain = 0, chip = 180, reg = 28
2020-10-07 18:57:43 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 1, chip = 55, reg = 28, got chain = 0, chip = 180, reg = 28
2020-10-07 18:57:43 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 1, chip = 55, reg = 28, got chain = 0, chip = 180, reg = 28
2020-10-07 18:57:43 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 1, chip = 55, reg = 28, got chain = 0, chip = 180, reg = 28
2020-10-07 18:57:43 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 1, chip = 55, reg = 28, got chain = 0, chip = 180, reg = 28
2020-10-07 18:57:43 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 1, chip = 55, reg = 28, got chain = 0, chip = 180, reg = 28
2020-10-07 18:57:43 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 1, chip = 55, reg = 28, got chain = 0, chip = 180, reg = 28
2020-10-07 18:57:43 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 1, chip = 55, reg = 28, got chain = 0, chip = 180, reg = 28




mikeywith
Legendary
*
Online Online

Activity: 1022
Merit: 3413


be constructive or S.T.F.U


View Profile
October 07, 2020, 10:51:16 PM
Last edit: October 08, 2020, 01:13:53 AM by frodocooper
 #177

I tried it on this miner with the latest firmware and it does still work.

Would be great if you could mention that in the thread so that others know it works on the latest firmware as well.

While testing that out, I changed the setting multiple times and ran into an issue where the miner did not come up after applying changes to the configuration page. I saw this once before and figured it was just a fluke, but it happened again. Comes back up with a reboot though, so not much of an issue.

Actually, this could be much of an issue, or at least, it will eventually be ( sorry to let you know), but if you follow the kernel closely, you will see these 4 lines.

Code:
2020-10-07 18:57:35 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 0, chip = 55, reg = 0

Code:
2020-10-07 18:57:39 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 1, chip = 40, reg = 1

Code:
2020-10-07 18:57:39 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 2, chip = 180, reg = 0

Code:
2020-10-07 18:57:43 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 3, chip = 195, reg = 1

I think your Chain 0 has a bad contact, nothing is wrong with all 4 temp sensors (0,1,2,3), this is a loose chip/heat sink, it hasn't exactly fallen, but it isn't 100% in contact, what usually happens when you see all 4 senors down is that the hash board will work at times, fail to work on another, sometimes it works for a whole week and then goes down, a reboot may fix it, you may need to reboot it 2-3 times, then it works for an hour and drops, the whole miner reboots, eventually and after x period of time (x is purely based on your luck) it will stop hashing and you will have to remove it from the miner for the other two boards to work uninterrupted.

To anyone else, I would advise against the attempt of fixing it, but since you said you are planning to fix your host's hash boards, then this chian 0 could be a great start to practice, you will need to figure out which chip is loose, remove it and then solder it back.

wndsnb
Sr. Member
****
Offline Offline

Activity: 276
Merit: 337


View Profile
October 07, 2020, 11:28:38 PM
Last edit: October 08, 2020, 01:14:37 AM by frodocooper
 #178

When this happens all of the chains have the same error though, this would lead me to believe that the issue would be not be specific to a single hashboard. Also, I have power cycled and rebooted many times and never saw this issue. It only seems to happen when I update settings and click the "save&apply".

Code:
2020-10-07 18:57:35 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 0, chip = 55, reg = 0

2020-10-07 18:57:37 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 1, chip = 40, reg = 0

2020-10-07 18:57:41 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 2, chip = 180, reg = 1

2020-10-07 18:57:43 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 3, chip = 195, reg = 1

2020-10-07 18:57:44 temperature.c:695:get_temp_info: read temp sensor failed: chain = 1, sensor = 0, chip = 55, reg = 0

2020-10-07 18:57:46 temperature.c:695:get_temp_info: read temp sensor failed: chain = 1, sensor = 1, chip = 40, reg = 0

2020-10-07 18:57:48 temperature.c:695:get_temp_info: read temp sensor failed: chain = 1, sensor = 2, chip = 180, reg = 0

2020-10-07 18:57:50 temperature.c:695:get_temp_info: read temp sensor failed: chain = 1, sensor = 3, chip = 195, reg = 0

2020-10-07 18:57:52 temperature.c:695:get_temp_info: read temp sensor failed: chain = 2, sensor = 0, chip = 55, reg = 0

2020-10-07 18:57:54 temperature.c:695:get_temp_info: read temp sensor failed: chain = 2, sensor = 1, chip = 40, reg = 0

2020-10-07 18:57:56 temperature.c:695:get_temp_info: read temp sensor failed: chain = 2, sensor = 2, chip = 180, reg = 0

2020-10-07 18:57:58 temperature.c:695:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 195, reg = 0
mikeywith
Legendary
*
Online Online

Activity: 1022
Merit: 3413


be constructive or S.T.F.U


View Profile
October 08, 2020, 01:18:28 AM
 #179

When this happens all of the chains have the same error though, this would lead me to believe that the issue would be not be specific to a single hashboard. Also, I have power cycled and rebooted many times and never saw this issue. It only seems to happen when I update settings and click the "save&apply".

Is that specific to just this latest firmware? I never had an issue when hitting save and apply, it actually seems like it performs a full reboot when that happens, but since I have not used the latest firmware so I can't really tell, I can only assume it's some sort of a bug, but if a complete reboot solves the problem then I shouldn't worry about it.

By the way, thanks for sharing all of this information, only a few people here do, the majority would disappear the moment their miners start hashing away. Grin

wndsnb
Sr. Member
****
Offline Offline

Activity: 276
Merit: 337


View Profile
October 08, 2020, 12:08:01 PM
 #180

Is that specific to just this latest firmware?

It is possible, but I didn't do much testing on the miner before I updated the firmware so no way to know. I'll report back if I see it in any of my hosts miners with older firmware. This one is headed back to my host today or tomorrow.
Pages: « 1 2 3 4 5 6 7 8 [9] 10 11 12 13 14 15 16 17 »  All
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!