Pages:
Author

Topic: Bitmain will be releasing S15 and T15 on 8/11/2018 - page 2. (Read 31497 times)

legendary
Activity: 1554
Merit: 2037
True. Honestly if I had not heard their story I would already have an S15, or an order for a couple T15's.

I'm just not prepared to be the guinea pig. This would really sink my hardware upgrades to have a failure without warranty protection. The email request I sent for clarification has gone unanswered so far; which was expected.
legendary
Activity: 4256
Merit: 8551
'The right to privacy matters'
this is bad news, let's hope bitmain will revert to the old psu specs for the future batches.

well remember only 1 person  has had confirmed psu death at 243-247 volts

I would love to know if someone else has had this happen.
legendary
Activity: 2394
Merit: 6581
be constructive or S.T.F.U
First test was 242-244V. Same results consistently for the next hour and a half. That's all I needed to see for now.

this is bad news, let's hope bitmain will revert to the old psu specs for the future batches.
legendary
Activity: 1554
Merit: 2037
Well at this point I'm saying the 15 series is not for me.

I did just do the manual checks on the unused summer circuit I have in the garage. The plan was to test it a few times throughout the day  as I went in and out while working on the house.

First test was 242-244V. Same results consistently for the next hour and a half. That's all I needed to see for now.
legendary
Activity: 2394
Merit: 6581
be constructive or S.T.F.U
Not sure how are you going to make certain, voltage can change a bit depending on the time of the day, based on a few factors, so when you test it, it may be 238v but that doesn't mean it's not going to go any higher 3 hours later.

The easiest and cheapest way to test this to be 100% sure that everything will work as you want them to be would buy installing the voltage protector and using 1 of the miners you have (s9 or anything else), set the voltage peak to say 239 ,then watch the hashrate graph on the pool after say 24-48 hours, if you get a lot of V shapes then diffidently S15 is not for you  Sad

* there are other ways , but i do think this is the easiest and the cheapest and requires 0 skills.
legendary
Activity: 1554
Merit: 2037
hmm set it to 239 or 240 or 241

I'll have to head out to the garage tonight and check out the circuits I have out there, as that's where these would be installed. For my concern though I don't think the settings will help me if I'm consistently over Voltage. Those settings would be great for a stabilizer, at say 239 to keep it under their apparent hardcap for voltage. I am more concerned of the constant power cycling this device brings if I am indeed consistently over 240, sure I don't burn out the PSU by going over voltage, but flipping the switch on and off over and over again isn't going to help the equipment either.

To big a gamble for that bit improvement in efficiency until I know more. When I know I can run an M10 without worry, it's still the better option for me atm. I say this knowing that there is an S15 that I could grab in Canada for a decent price.
full member
Activity: 1022
Merit: 221
We are not retail.
T15s look available for now.
member
Activity: 287
Merit: 18
it's pretty much safe to assume that anything above 240v will put the psu in danger, i also wouldn't take bitmain support word's very seriously.

if you have a constant >240 voltage then that will be an issue, but if you are only worried about once in a while spikes then you can use something like this > https://www.aliexpress.com/item/60A-220V-adjustable-automatic-reconnect-over-voltage-and-under-voltage-protection-device-relay-with-Voltmeter-voltage/32814064058.html

it's more or less a voltage protector, it does not regulate voltage whatsoever, but it does close the circuit when voltage is higher than whatever you set it to, same goes for voltage drop, i use something very similar to this "not on miners but on a sensitive fridge"  and it works like magic.

thanks for info/tip...
legendary
Activity: 4256
Merit: 8551
'The right to privacy matters'
Looks similar to something I was thinking of installing to actually monitor my power draw. Did I read it right that it opens the circuit and then re-establishes in less than 25 seconds? Problem is I'm not positive how often I go above. I may have to put more effort into confirming this if more hardware goes this way with a hard cap right at 240V. I would be okay with it kicking out the odd time, but would be hesitant to have it potentially cycle on and off several times in succession.

Thanks for the tip as I hadn't even considered something like this.

hmm set it to 239 or 240 or 241

it can do 2 x 30amp circuits  which is 6 s15's
legendary
Activity: 1554
Merit: 2037
it's pretty much safe to assume that anything above 240v will put the psu in danger, i also wouldn't take bitmain support word's very seriously.

if you have a constant >240 voltage then that will be an issue, but if you are only worried about once in a while spikes then you can use something like this > https://www.aliexpress.com/item/60A-220V-adjustable-automatic-reconnect-over-voltage-and-under-voltage-protection-device-relay-with-Voltmeter-voltage/32814064058.html

it's more or less a voltage protector, it does not regulate voltage whatsoever, but it does close the circuit when voltage is higher than whatever you set it to, same goes for voltage drop, i use something very similar to this "not on miners but on a sensitive fridge"  and it works like magic.

Looks similar to something I was thinking of installing to actually monitor my power draw. Did I read it right that it opens the circuit and then re-establishes in less than 25 seconds? Problem is I'm not positive how often I go above. I may have to put more effort into confirming this if more hardware goes this way with a hard cap right at 240V. I would be okay with it kicking out the odd time, but would be hesitant to have it potentially cycle on and off several times in succession.

Thanks for the tip as I hadn't even considered something like this.
full member
Activity: 1022
Merit: 221
We are not retail.
Looks like we're still waiting on new batches for the US market odd though that the CN site is pushing T15 for April. Wonder if our groups fill what date Bitmain give us.
legendary
Activity: 2394
Merit: 6581
be constructive or S.T.F.U
it's pretty much safe to assume that anything above 240v will put the psu in danger, i also wouldn't take bitmain support word's very seriously.

if you have a constant >240 voltage then that will be an issue, but if you are only worried about once in a while spikes then you can use something like this > https://www.aliexpress.com/item/60A-220V-adjustable-automatic-reconnect-over-voltage-and-under-voltage-protection-device-relay-with-Voltmeter-voltage/32814064058.html

it's more or less a voltage protector, it does not regulate voltage whatsoever, but it does close the circuit when voltage is higher than whatever you set it to, same goes for voltage drop, i use something very similar to this "not on miners but on a sensitive fridge"  and it works like magic.
legendary
Activity: 1554
Merit: 2037
Yeah I noticed that before. I actually got all those same coupons for the 1 miner I bought direct - it was a T9+. Funny thing is I bought it with a very good coupon as well.

Either way I'm going to hold off until I hear from Bitmain. Without a solid yay or nay I won't risk having the failure, my power costs allow me to happily buy m10's in the meantime.
legendary
Activity: 2394
Merit: 6581
be constructive or S.T.F.U
Yeah it was only the larger coupons that went to some of their preferred larger clientele I imagine. So the 395$ as opposed to the 340$, and the 300$ as opposed to the 250$

I haven't talked to anyone who held those coupons so I can't be sure when or how they were distributed, but apparently they were usable at any time.

here is a breakdown of how they distributed  the coupons

For every S9 bought they gave out 3 x coupons with face value of (160$,250$,340$).

For every S11/T15/S15 they gave out the same as the S9 + another 3 coupons with face value of ( 195,300,395).

those who want buy new gears from bitmain should buy those higher values coupons, even if they have the s9 coupons in their account.

S15 coupon   395 - 340  = 45$ , so anything you pay that is less than 45$ = more saving

same thing goes for the other coupons.
full member
Activity: 1022
Merit: 221
We are not retail.
We'll see whats available Sunday night. Looks like our orders we're all submitted to them yesterday.

Might be tough on timing for the next batches as these last were a month away.
legendary
Activity: 4256
Merit: 8551
'The right to privacy matters'
Looks like the T15 has also sold out for April delivery. I held off on ordering when i realised it was more than a month until shipdate. It's a little short sighted on my part.; but i have no need to take 28TH of inefficient 741's offline until May.

I have decided to take this time to reach out to Bitmain support and ask about max input voltage of 240. I know it wad only a couple and could have been a cold/moisture issue, but it doesn't sit well with me to have a potential problem that would definitely void the warranty.

I am the worst at pulling the trigger on new gear

So bitmain is sold out of

S15
T15
S11

innosilicon is  insanely expensive with a long wait for the T3

M10's are the only new gear around at the moment.
legendary
Activity: 1554
Merit: 2037
Looks like the T15 has also sold out for April delivery. I held off on ordering when i realised it was more than a month until shipdate. It's a little short sighted on my part.; but i have no need to take 28TH of inefficient 741's offline until May.

I have decided to take this time to reach out to Bitmain support and ask about max input voltage of 240. I know it wad only a couple and could have been a cold/moisture issue, but it doesn't sit well with me to have a potential problem that would definitely void the warranty.

I am the worst at pulling the trigger on new gear
newbie
Activity: 12
Merit: 1
I loaded the new firmware on a T15 that was taking forever to boot up and now it is rebooting itself every 30 minutes or so. Maybe it is a firmware issue, maybe it's the miner...

Has Anyone else have any issues with the new firmware? I went to flash the old firmware from an older T15 but it seems they have made it so we can no longer download backups from the interface. How can I find the old T15 firmware?
legendary
Activity: 2030
Merit: 1569
CLEAN non GPL infringing code made in Rust lang
So can you no longer ssh to it? Make sure you keep backups of the older firmware!
copper member
Activity: 330
Merit: 103
Quote of changes implemented by these new FW's (same for T/S15):

Add low temperature protection function
Security issues fixed

Below is the startup sequence immediately after upgrading to the newest firmware:

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: 197300K/245760K available (6345K kernel code, 231K rwdata, 1896K rodata, 1024K init, 223K bss, 32076K reserved, 16384K cma-reserved, 0K highmem)
Virtual kernel memory layout:
    vector  : 0xffff0000 - 0xffff1000   (   4 kB)
    fixmap  : 0xffc00000 - 0xfff00000   (3072 kB)
    vmalloc : 0xcf800000 - 0xff800000   ( 768 MB)
    lowmem  : 0xc0000000 - 0xcf000000   ( 240 MB)
    pkmap   : 0xbfe00000 - 0xc0000000   (   2 MB)
    modules : 0xbf000000 - 0xbfe00000   (  14 MB)
      .text : 0xc0008000 - 0xc090c424   (9234 kB)
      .init : 0xc0a00000 - 0xc0b00000   (1024 kB)
      .data : 0xc0b00000 - 0xc0b39fe0   ( 232 kB)
       .bss : 0xc0b39fe0 - 0xc0b71c28   ( 224 kB)
Preemptible hierarchical RCU implementation.
Build-time adjustment of leaf fanout to 32.
RCU restricting CPUs from NR_CPUS=4 to nr_cpu_ids=2.
RCU: Adjusting geometry for rcu_fanout_leaf=32, nr_cpu_ids=2
NR_IRQS:16 nr_irqs:16 16
efuse mapped to cf800000
ps7-slcr mapped to cf802000
L2C: platform modifies aux control register: 0x72360000 -> 0x72760000
L2C: DT/platform modifies aux control register: 0x72360000 -> 0x72760000
L2C-310 erratum 769419 enabled
L2C-310 enabling early BRESP for Cortex-A9
L2C-310 full line of zeros enabled for Cortex-A9
L2C-310 ID prefetch enabled, offset 1 lines
L2C-310 dynamic clock gating enabled, standby mode enabled
L2C-310 cache controller enabled, 8 ways, 512 kB
L2C-310: CACHE_ID 0x410000c8, AUX_CTRL 0x76760001
zynq_clock_init: clkc starts at cf802100
Zynq clock init
sched_clock: 64 bits at 333MHz, resolution 3ns, wraps every 4398046511103ns
clocksource: arm_global_timer: mask: 0xffffffffffffffff max_cycles: 0x4ce07af025, max_idle_ns: 440795209040 ns
Switching to timer-based delay loop, resolution 3ns
clocksource: ttc_clocksource: mask: 0xffff max_cycles: 0xffff, max_idle_ns: 537538477 ns
ps7-ttc #0 at cf80a000, irq=18
Console: colour dummy device 80x30
Calibrating delay loop (skipped), value calculated using timer frequency.. 666.66 BogoMIPS (lpj=3333333)
pid_max: default: 32768 minimum: 301
Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
CPU: Testing write buffer coherency: ok
CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
Setting up static identity map for 0x100000 - 0x100058
CPU1: failed to boot: -1
Brought up 1 CPUs
SMP: Total of 1 processors activated (666.66 BogoMIPS).
CPU: All CPU(s) started in SVC mode.
devtmpfs: initialized
VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4
clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
pinctrl core: initialized pinctrl subsystem
NET: Registered protocol family 16
DMA: preallocated 256 KiB pool for atomic coherent allocations
cpuidle: using governor menu
hw-breakpoint: found 5 (+1 reserved) breakpoint and 1 watchpoint registers.
hw-breakpoint: maximum watchpoint size is 4 bytes.
zynq-ocm f800c000.ps7-ocmc: ZYNQ OCM pool: 256 KiB @ 0xcf880000
vgaarb: loaded
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
media: Linux media interface: v0.10
Linux video capture interface: v2.00
pps_core: LinuxPPS API ver. 1 registered
pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti
PTP clock support registered
EDAC MC: Ver: 3.0.0
Advanced Linux Sound Architecture Driver Initialized.
clocksource: Switched to clocksource arm_global_timer
NET: Registered protocol family 2
TCP established hash table entries: 2048 (order: 1, 8192 bytes)
TCP bind hash table entries: 2048 (order: 2, 16384 bytes)
TCP: Hash tables configured (established 2048 bind 2048)
UDP hash table entries: 256 (order: 1, 8192 bytes)
UDP-Lite hash table entries: 256 (order: 1, 8192 bytes)
NET: Registered protocol family 1
RPC: Registered named UNIX socket transport module.
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
PCI: CLS 0 bytes, default 64
Trying to unpack rootfs image as initramfs...
rootfs image is not initramfs (no cpio magic); looks like an initrd
Freeing initrd memory: 19036K (cc869000 - cdb00000)
hw perfevents: enabled with armv7_cortex_a9 PMU driver, 7 counters available
futex hash table entries: 512 (order: 3, 32768 bytes)
workingset: timestamp_bits=28 max_order=16 bucket_order=0
jffs2: version 2.2. (NAND) (SUMMARY)  © 2001-2006 Red Hat, Inc.
io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered (default)
dma-pl330 f8003000.ps7-dma: Loaded driver for PL330 DMAC-241330
dma-pl330 f8003000.ps7-dma: DBUFF-128x8bytes Num_Chans-8 Num_Peri-4 Num_Events-16
e0000000.serial: ttyPS0 at MMIO 0xe0000000 (irq = 158, base_baud = 6249999) is a xuartps
console [ttyPS0] enabled
xdevcfg f8007000.ps7-dev-cfg: ioremap 0xf8007000 to cf86e000
[drm] Initialized drm 1.1.0 20060810
brd: module loaded
loop: module loaded
CAN device driver interface
gpiod_set_value: invalid GPIO
libphy: MACB_mii_bus: probed
macb e000b000.ethernet eth0: Cadence GEM rev 0x00020118 at 0xe000b000 irq 31 (00:0a:35:00:00:00)
Generic PHY e000b000.etherne:00: attached PHY driver [Generic PHY] (mii_bus:phy_addr=e000b000.etherne:00, irq=-1)
e1000e: Intel(R) PRO/1000 Network Driver - 3.2.6-k
e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
ehci-pci: EHCI PCI platform driver
usbcore: registered new interface driver usb-storage
mousedev: PS/2 mouse device common for all mice
i2c /dev entries driver
Xilinx Zynq CpuIdle Driver started
sdhci: Secure Digital Host Controller Interface driver
sdhci: Copyright(c) Pierre Ossman
sdhci-pltfm: SDHCI platform and OF driver helper
mmc0: SDHCI controller on e0100000.ps7-sdio [e0100000.ps7-sdio] using ADMA
ledtrig-cpu: registered to indicate activity on CPUs
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
nand: device found, Manufacturer ID: 0x2c, Chip ID: 0xda
nand: Micron MT29F2G08ABAEAWP
nand: 256 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 64
nand: WARNING: pl35x-nand: the ECC used on your system is too weak compared to the one required by the NAND chip
Bad block table found at page 131008, version 0x01
Bad block table found at page 130944, version 0x01
nand_read_bbt: bad block at 0x000002420000
nand_read_bbt: bad block at 0x000002440000
nand_read_bbt: bad block at 0x000002460000
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/0, WL threshold: 4096, image sequence number: 1612620144
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 657494A9-6816-44F8-9CFC-4645028DD4A2, 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: 282/177, WL threshold: 4096, image sequence number: 671793871
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 B5297183-49EC-4496-895A-CD02D5F99059, 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 0xcfb34000
*base_vir_addr = 0xab00d
In fpga mem driver!
request_mem_region OK!
fpga mem virtual address is 0xd2000000
random: nonblocking pool is initialized
 [2019-02-28 15:15:15.736] httpListenThread start ret=0
 [2019-02-28 15:15:45.737] start listen on 6060 ...
 [2019-02-28 15:20:52.439] set_start_time_point total_tv_start_sys=357 total_tv_end_sys=358

2019-02-28 15:15:15 driver-btm-soc.c:7206:init_freq_mode: This is scan-user version
2019-02-28 15:15:15 driver-btm-soc.c:7709:bitmain_soc_init: T15
2019-02-28 15:15:15 driver-btm-soc.c:7710:bitmain_soc_init: opt_multi_version=1
2019-02-28 15:15:15 driver-btm-soc.c:7711:bitmain_soc_init: opt_bitmain_ab=1
2019-02-28 15:15:15 driver-btm-soc.c:7712:bitmain_soc_init: opt_bitmain_economic_mode=false
2019-02-28 15:15:15 driver-btm-soc.c:7584:_show_sn: no SN got, please write SN to /nvdata/sn
2019-02-28 15:15:15 driver-btm-soc.c:7237:init_phy_mem_nonce2_jobid_address: Detect 256MB control board of XILINX
2019-02-28 15:15:15 driver-btm-soc.c:7719:bitmain_soc_init: Miner compile time: Mon Feb 25 11:17:06 CST 2019 type: Antminer T15
2019-02-28 15:15:15 driver-btm-soc.c:7721:bitmain_soc_init: last commit version: 276a2d2 commit time: 2019-02-23 14:47:27 build: 2019-02-25 11:22:43
2019-02-28 15:15:15 driver-btm-soc.c:7268:check_fan_multi: check fan for 20 times...
2019-02-28 15:15:17 driver-btm-soc.c:7767:bitmain_soc_init: miner ID : 8174f42429e04814
2019-02-28 15:15:17 driver-btm-soc.c:7337:init_miner_version: FPGA Version = 0xB00D
2019-02-28 15:15:17 driver-btm-soc.c:1059:check_chain: get_hash_on_plug is 0x7
2019-02-28 15:15:17 driver-btm-soc.c:1071:check_chain: !! chain[0]is exist
2019-02-28 15:15:17 driver-btm-soc.c:1071:check_chain: !! chain[1]is exist
2019-02-28 15:15:17 driver-btm-soc.c:1071:check_chain: !! chain[2]is exist
2019-02-28 15:15:20 eeprom.c:1408:eeprom_load: eeprom load chain [0]
         00 01 02 03 04 05 06 07   08 09 0A 0B 0C 0D 0E 0F
00000000 7f ac 58 5e 5e 5b 5e 5e   5b 5e 5e 58 5b 5e 5e 58
00000010 5e 5b 58 5e 5e 5e 5e 5e   5e 58 5b 5b 58 5e 5e 5e
00000020 5e 5e 5e 5b 58 5e 5e 5e   58 5b 5e 5e 5e 5b 58 58
00000030 5e 5e 5b 5e 5e 5e 5e 5b   58 58 5b 5e 5e 5e ff ff
00000040 ff ff ff ff ff ff ff ff   ff ff ff ff ff ff ff ff
00000050 ff ff ff ff ff ff ff ff   ff ff ff ff ff ff ff ff
00000060 ff ff ff ff ff ff ff ff   ff ff ff ff ff ff 8e 1b
00000070 00 00 ff ff ff ff ff ff   ff 00 04 0b 00 0f 00 2d
00000080 00 2d 00 ff ff ff ff ba   65 65 65 65 65 65 65 65
00000090 65 65 65 65 65 65 65 65   65 65 65 65 65 65 65 65
000000a0 65 65 65 65 65 65 65 65   65 65 65 65 65 65 65 65
000000b0 65 65 65 65 65 65 65 65   65 65 65 65 65 65 65 65
000000c0 65 65 65 65 ff ff ff ff   ff ff ff ff ff ff ff ff
000000d0 ff ff ff ff ff ff ff ff   ff ff ff ff ff ff ff ff
000000e0 ff ff ff ff ff ff ff ff   ff ff ff ff ff ff ff ff
000000f0 ff ff ff ff 36 1e 00 00   ff ff 01 01 01 00 cd dd
2019-02-28 15:15:22 eeprom.c:1408:eeprom_load: eeprom load chain [1]
         00 01 02 03 04 05 06 07   08 09 0A 0B 0C 0D 0E 0F
00000000 7f ac 58 5b 5b 5b 5b 5b   5b 58 5b 5b 5b 58 5b 5b
00000010 5b 58 5b 5b 5b 5b 5b 5b   58 5b 5b 58 5b 5b 5b 5b
00000020 5b 5b 5b 5b 58 5b 5b 5b   5b 58 5b 5b 5b 58 5b 5b
00000030 5b 58 5b 5b 58 5b 5b 5b   5b 58 5b 5b 5b 5b ff ff
00000040 ff ff ff ff ff ff ff ff   ff ff ff ff ff ff ff ff
00000050 ff ff ff ff ff ff ff ff   ff ff ff ff ff ff ff ff
00000060 ff ff ff ff ff ff ff ff   ff ff ff ff ff ff fd 1a
00000070 00 00 ff ff ff ff ff ff   ff 00 04 0b 00 0f 00 2d
00000080 00 2d 00 ff ff ff ff ba   66 66 66 66 66 66 66 66
00000090 66 66 66 66 66 66 66 66   66 66 66 66 66 66 66 66
000000a0 66 66 66 66 66 66 66 66   66 66 66 66 66 66 66 66
000000b0 66 66 66 66 66 66 66 66   66 66 66 66 66 66 66 66
000000c0 66 66 66 66 ff ff ff ff   ff ff ff ff ff ff ff ff
000000d0 ff ff ff ff ff ff ff ff   ff ff ff ff ff ff ff ff
000000e0 ff ff ff ff ff ff ff ff   ff ff ff ff ff ff ff ff
000000f0 ff ff ff ff 75 1e 00 00   ff ff 01 01 01 00 10 76
2019-02-28 15:15:25 eeprom.c:1408:eeprom_load: eeprom load chain [2]
         00 01 02 03 04 05 06 07   08 09 0A 0B 0C 0D 0E 0F
00000000 7f ac 5e 5e 5e 5b 5b 5b   5b 5e 5e 5e 5e 5e 5e 5b
00000010 5b 5b 5b 5e 5e 5e 5b 5e   5b 5e 5e 5e 5e 5e 5b 5b
00000020 5e 5e 5e 5b 5b 5e 5e 5b   5e 5b 5e 5e 5b 5e 5b 5e
00000030 5e 5e 5b 5b 5e 5e 5e 5b   5b 5b 5e 5e 5e 5b ff ff
00000040 ff ff ff ff ff ff ff ff   ff ff ff ff ff ff ff ff
00000050 ff ff ff ff ff ff ff ff   ff ff ff ff ff ff ff ff
00000060 ff ff ff ff ff ff ff ff   ff ff ff ff ff ff be 1b
00000070 00 00 ff ff ff ff ff ff   ff 00 04 0b 00 0f 00 2d
00000080 00 2d 00 ff ff ff ff ba   66 66 66 66 66 66 66 66
00000090 66 66 66 66 66 66 66 66   66 66 66 66 66 66 66 66
000000a0 66 66 66 66 66 66 66 66   66 66 66 66 66 66 66 66
000000b0 66 66 66 66 66 66 66 66   66 66 66 66 66 66 66 66
000000c0 66 66 66 66 ff ff ff ff   ff ff ff ff ff ff ff ff
000000d0 ff ff ff ff ff ff ff ff   ff ff ff ff ff ff ff ff
000000e0 ff ff ff ff ff ff ff ff   ff ff ff ff ff ff ff ff
000000f0 ff ff ff ff 77 1e 00 00   ff ff 01 01 01 00 e1 80
2019-02-28 15:15:25 eeprom.c:1417:eeprom_load: done
2019-02-28 15:15:25 driver-btm-soc.c:7358:init_pcb_version: chain[0] PCB Version : 0x0101
2019-02-28 15:15:25 driver-btm-soc.c:7377:init_pcb_version: chain[0] BOM Version : 0x0100
2019-02-28 15:15:25 driver-btm-soc.c:7358:init_pcb_version: chain[1] PCB Version : 0x0101
2019-02-28 15:15:25 driver-btm-soc.c:7377:init_pcb_version: chain[1] BOM Version : 0x0100
2019-02-28 15:15:25 driver-btm-soc.c:7358:init_pcb_version: chain[2] PCB Version : 0x0101
2019-02-28 15:15:25 driver-btm-soc.c:7377:init_pcb_version: chain[2] BOM Version : 0x0100
2019-02-28 15:15:26 dspic33ep16gs202.c:545:reset_pic: chain[0] ok
2019-02-28 15:15:30 dspic33ep16gs202.c:509:jump_to_app_from_loader: chain[0] ok
2019-02-28 15:15:31 dspic33ep16gs202.c:545:reset_pic: chain[1] ok
2019-02-28 15:15:35 dspic33ep16gs202.c:509:jump_to_app_from_loader: chain[1] ok
2019-02-28 15:15:36 dspic33ep16gs202.c:545:reset_pic: chain[2] ok
2019-02-28 15:15:40 dspic33ep16gs202.c:509:jump_to_app_from_loader: chain[2] ok
2019-02-28 15:15:40 power.c:124:power_init: power init ...
2019-02-28 15:15:40 driver-btm-soc.c:3061:heart_beat_func_one_chain: for chain 2
2019-02-28 15:15:40 driver-btm-soc.c:3061:heart_beat_func_one_chain: for chain 1
2019-02-28 15:15:40 driver-btm-soc.c:3061:heart_beat_func_one_chain: for chain 0
2019-02-28 15:15:40 power.c:101:power_on: init gpio907
2019-02-28 15:15:43 dspic33ep16gs202.c:410:hashboard_power_cntl: [0] ok, i2c=0!
2019-02-28 15:15:43 dspic33ep16gs202.c:410:hashboard_power_cntl: [0] ok, i2c=1!
2019-02-28 15:15:44 dspic33ep16gs202.c:410:hashboard_power_cntl: [0] ok, i2c=2!
2019-02-28 15:15:47 driver-btm-soc.c:7790:bitmain_soc_init: Enter 30s sleep to make sure power release finish.
2019-02-28 15:16:17 driver-btm-soc.c:7545:set_working_voltage_by_eeprom: eeprom voltage[0] = 19.300000
2019-02-28 15:16:17 driver-btm-soc.c:7545:set_working_voltage_by_eeprom: eeprom voltage[1] = 19.300000
2019-02-28 15:16:17 driver-btm-soc.c:7545:set_working_voltage_by_eeprom: eeprom voltage[2] = 19.300000
2019-02-28 15:16:17 power.c:136:set_working_voltage: working_voltage = 19.300000
2019-02-28 15:16:17 power.c:259:set_iic_power_to_highest_voltage: setting to voltage: 20.00 ...
2019-02-28 15:16:17 power.c:211:set_iic_power_by_voltage: now setting voltage to : 20.000000
2019-02-28 15:16:17 eeprom.c:839:travel_eeprom_store: chain[0] data in eeprom is:
magic number: 0x7f
freq data per ASIC:
IC[000]:440 IC[001]:470 IC[002]:470 IC[003]:455 IC[004]:470
IC[005]:470 IC[006]:455 IC[007]:470 IC[008]:470 IC[009]:440
IC[010]:455 IC[011]:470 IC[012]:470 IC[013]:440 IC[014]:470
IC[015]:455 IC[016]:440 IC[017]:470 IC[018]:470 IC[019]:470
IC[020]:470 IC[021]:470 IC[022]:470 IC[023]:440 IC[024]:455
IC[025]:455 IC[026]:440 IC[027]:470 IC[028]:470 IC[029]:470
IC[030]:470 IC[031]:470 IC[032]:470 IC[033]:455 IC[034]:440
IC[035]:470 IC[036]:470 IC[037]:470 IC[038]:440 IC[039]:455
IC[040]:470 IC[041]:470 IC[042]:470 IC[043]:455 IC[044]:440
IC[045]:440 IC[046]:470 IC[047]:470 IC[048]:455 IC[049]:470
IC[050]:470 IC[051]:470 IC[052]:470 IC[053]:455 IC[054]:440
IC[055]:440 IC[056]:455 IC[057]:470 IC[058]:470 IC[059]:470
voltage: 18.60 V
hash rate: 07054 GH/s

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

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

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

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

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

2019-02-28 15:16:18 dspic33ep16gs202.c:410:hashboard_power_cntl: [1] ok, i2c=0!
2019-02-28 15:16:18 znyq.c:193:set_reset_hashboard: set_reset_hashboard = 0x0000ffff
2019-02-28 15:16:21 znyq.c:193:set_reset_hashboard: set_reset_hashboard = 0x0000fffe
2019-02-28 15:16:24 driver-btm-soc.c:5395:check_asic_num_by_pre_open_core: Try to find asic by pre core: times 0
2019-02-28 15:16:24 driver-btm-soc.c:5351:check_asic_num_without_power_off: Open 16 core for chain 0
2019-02-28 15:16:24 driver-btm-soc.c:3953:open_core_BM1391_pre_open: pre open core = 16
2019-02-28 15:16:25 driver-btm-soc.c:3928:pre_open_core_one_chain: for chain 0
2019-02-28 15:16:25 driver-btm-soc.c:3953:open_core_BM1391_pre_open: pre open core = 16
2019-02-28 15:16:25 driver-btm-soc.c:3928:pre_open_core_one_chain: for chain 0
2019-02-28 15:16:25 driver-btm-soc.c:3953:open_core_BM1391_pre_open: pre open core = 16
2019-02-28 15:16:26 driver-btm-soc.c:3928:pre_open_core_one_chain: for chain 0
2019-02-28 15:16:26 driver-btm-soc.c:3953:open_core_BM1391_pre_open: pre open core = 16
2019-02-28 15:16:27 driver-btm-soc.c:3928:pre_open_core_one_chain: for chain 0
2019-02-28 15:16:27 znyq.c:193:set_reset_hashboard: set_reset_hashboard = 0x0000ffff
2019-02-28 15:16:30 znyq.c:193:set_reset_hashboard: set_reset_hashboard = 0x0000fffe
2019-02-28 15:16:33 driver-btm-soc.c:5365:check_asic_num_without_power_off: chain 0, find asic num = 60
2019-02-28 15:16:34 dspic33ep16gs202.c:410:hashboard_power_cntl: [1] ok, i2c=1!
2019-02-28 15:16:34 znyq.c:193:set_reset_hashboard: set_reset_hashboard = 0x0000fffe
2019-02-28 15:16:37 znyq.c:193:set_reset_hashboard: set_reset_hashboard = 0x0000fffc
2019-02-28 15:16:40 driver-btm-soc.c:5395:check_asic_num_by_pre_open_core: Try to find asic by pre core: times 0
2019-02-28 15:16:40 driver-btm-soc.c:5351:check_asic_num_without_power_off: Open 16 core for chain 1
2019-02-28 15:16:40 driver-btm-soc.c:3953:open_core_BM1391_pre_open: pre open core = 16
2019-02-28 15:16:40 driver-btm-soc.c:3928:pre_open_core_one_chain: for chain 1
2019-02-28 15:16:40 driver-btm-soc.c:3953:open_core_BM1391_pre_open: pre open core = 16
2019-02-28 15:16:41 driver-btm-soc.c:3928:pre_open_core_one_chain: for chain 1
2019-02-28 15:16:41 driver-btm-soc.c:3953:open_core_BM1391_pre_open: pre open core = 16
2019-02-28 15:16:42 driver-btm-soc.c:3928:pre_open_core_one_chain: for chain 1
2019-02-28 15:16:42 driver-btm-soc.c:3953:open_core_BM1391_pre_open: pre open core = 16
2019-02-28 15:16:43 driver-btm-soc.c:3928:pre_open_core_one_chain: for chain 1
2019-02-28 15:16:43 znyq.c:193:set_reset_hashboard: set_reset_hashboard = 0x0000fffe
2019-02-28 15:16:46 znyq.c:193:set_reset_hashboard: set_reset_hashboard = 0x0000fffc
2019-02-28 15:16:49 driver-btm-soc.c:5365:check_asic_num_without_power_off: chain 1, find asic num = 60
2019-02-28 15:16:49 dspic33ep16gs202.c:410:hashboard_power_cntl: [1] ok, i2c=2!
2019-02-28 15:16:49 znyq.c:193:set_reset_hashboard: set_reset_hashboard = 0x0000fffc
2019-02-28 15:16:52 znyq.c:193:set_reset_hashboard: set_reset_hashboard = 0x0000fff8
2019-02-28 15:16:55 driver-btm-soc.c:5395:check_asic_num_by_pre_open_core: Try to find asic by pre core: times 0
2019-02-28 15:16:55 driver-btm-soc.c:5351:check_asic_num_without_power_off: Open 16 core for chain 2
2019-02-28 15:16:55 driver-btm-soc.c:3953:open_core_BM1391_pre_open: pre open core = 16
2019-02-28 15:16:56 driver-btm-soc.c:3928:pre_open_core_one_chain: for chain 2
2019-02-28 15:16:56 driver-btm-soc.c:3953:open_core_BM1391_pre_open: pre open core = 16
2019-02-28 15:16:57 driver-btm-soc.c:3928:pre_open_core_one_chain: for chain 2
2019-02-28 15:16:57 driver-btm-soc.c:3953:open_core_BM1391_pre_open: pre open core = 16
2019-02-28 15:16:58 driver-btm-soc.c:3928:pre_open_core_one_chain: for chain 2
2019-02-28 15:16:58 driver-btm-soc.c:3953:open_core_BM1391_pre_open: pre open core = 16
2019-02-28 15:16:58 driver-btm-soc.c:3928:pre_open_core_one_chain: for chain 2
2019-02-28 15:16:58 znyq.c:193:set_reset_hashboard: set_reset_hashboard = 0x0000fffc
2019-02-28 15:17:01 znyq.c:193:set_reset_hashboard: set_reset_hashboard = 0x0000fff8
2019-02-28 15:17:05 driver-btm-soc.c:5365:check_asic_num_without_power_off: chain 2, find asic num = 60
2019-02-28 15:17:05 driver-btm-soc.c:7171:balance_domain_voltage: To balance voltage domain, open all core and reset hash board after find asic num.
2019-02-28 15:17:05 driver-btm-soc.c:7182:balance_domain_voltage: Open core 16 for chain 0
2019-02-28 15:17:05 driver-btm-soc.c:3953:open_core_BM1391_pre_open: pre open core = 16
2019-02-28 15:17:05 driver-btm-soc.c:3928:pre_open_core_one_chain: for chain 0
2019-02-28 15:17:05 znyq.c:193:set_reset_hashboard: set_reset_hashboard = 0x0000fff9
2019-02-28 15:17:08 znyq.c:193:set_reset_hashboard: set_reset_hashboard = 0x0000fff8
2019-02-28 15:17:11 driver-btm-soc.c:7182:balance_domain_voltage: Open core 16 for chain 1
2019-02-28 15:17:11 driver-btm-soc.c:3953:open_core_BM1391_pre_open: pre open core = 16
2019-02-28 15:17:12 driver-btm-soc.c:3928:pre_open_core_one_chain: for chain 1
2019-02-28 15:17:12 znyq.c:193:set_reset_hashboard: set_reset_hashboard = 0x0000fffa
2019-02-28 15:17:15 znyq.c:193:set_reset_hashboard: set_reset_hashboard = 0x0000fff8
2019-02-28 15:17:18 driver-btm-soc.c:7182:balance_domain_voltage: Open core 16 for chain 2
2019-02-28 15:17:18 driver-btm-soc.c:3953:open_core_BM1391_pre_open: pre open core = 16
2019-02-28 15:17:19 driver-btm-soc.c:3928:pre_open_core_one_chain: for chain 2
2019-02-28 15:17:19 znyq.c:193:set_reset_hashboard: set_reset_hashboard = 0x0000fffc
2019-02-28 15:17:22 znyq.c:193:set_reset_hashboard: set_reset_hashboard = 0x0000fff8
2019-02-28 15:17:25 driver-btm-soc.c:7182:balance_domain_voltage: Open core 32 for chain 0
2019-02-28 15:17:25 driver-btm-soc.c:3953:open_core_BM1391_pre_open: pre open core = 32
2019-02-28 15:17:26 driver-btm-soc.c:3928:pre_open_core_one_chain: for chain 0
2019-02-28 15:17:26 znyq.c:193:set_reset_hashboard: set_reset_hashboard = 0x0000fff9
2019-02-28 15:17:29 znyq.c:193:set_reset_hashboard: set_reset_hashboard = 0x0000fff8
2019-02-28 15:17:32 driver-btm-soc.c:7182:balance_domain_voltage: Open core 32 for chain 1
2019-02-28 15:17:32 driver-btm-soc.c:3953:open_core_BM1391_pre_open: pre open core = 32
2019-02-28 15:17:34 driver-btm-soc.c:3928:pre_open_core_one_chain: for chain 1
2019-02-28 15:17:34 znyq.c:193:set_reset_hashboard: set_reset_hashboard = 0x0000fffa
2019-02-28 15:17:37 znyq.c:193:set_reset_hashboard: set_reset_hashboard = 0x0000fff8
2019-02-28 15:17:40 driver-btm-soc.c:7182:balance_domain_voltage: Open core 32 for chain 2
2019-02-28 15:17:40 driver-btm-soc.c:3953:open_core_BM1391_pre_open: pre open core = 32
2019-02-28 15:17:41 driver-btm-soc.c:3928:pre_open_core_one_chain: for chain 2
2019-02-28 15:17:41 znyq.c:193:set_reset_hashboard: set_reset_hashboard = 0x0000fffc
2019-02-28 15:17:44 znyq.c:193:set_reset_hashboard: set_reset_hashboard = 0x0000fff8
2019-02-28 15:17:47 driver-btm-soc.c:7182:balance_domain_voltage: Open core 64 for chain 0
2019-02-28 15:17:47 driver-btm-soc.c:3953:open_core_BM1391_pre_open: pre open core = 64
2019-02-28 15:17:50 driver-btm-soc.c:3928:pre_open_core_one_chain: for chain 0
2019-02-28 15:17:50 znyq.c:193:set_reset_hashboard: set_reset_hashboard = 0x0000fff9
2019-02-28 15:17:53 znyq.c:193:set_reset_hashboard: set_reset_hashboard = 0x0000fff8
2019-02-28 15:17:56 driver-btm-soc.c:7182:balance_domain_voltage: Open core 64 for chain 1
2019-02-28 15:17:56 driver-btm-soc.c:3953:open_core_BM1391_pre_open: pre open core = 64
2019-02-28 15:17:59 driver-btm-soc.c:3928:pre_open_core_one_chain: for chain 1
2019-02-28 15:17:59 znyq.c:193:set_reset_hashboard: set_reset_hashboard = 0x0000fffa
2019-02-28 15:18:02 znyq.c:193:set_reset_hashboard: set_reset_hashboard = 0x0000fff8
2019-02-28 15:18:05 driver-btm-soc.c:7182:balance_domain_voltage: Open core 64 for chain 2
2019-02-28 15:18:05 driver-btm-soc.c:3953:open_core_BM1391_pre_open: pre open core = 64
2019-02-28 15:18:08 driver-btm-soc.c:3928:pre_open_core_one_chain: for chain 2
2019-02-28 15:18:08 znyq.c:193:set_reset_hashboard: set_reset_hashboard = 0x0000fffc
2019-02-28 15:18:11 znyq.c:193:set_reset_hashboard: set_reset_hashboard = 0x0000fff8
2019-02-28 15:18:25 driver-btm-soc.c:7403:calculate_timeout: dev->timeout = 857
2019-02-28 15:18:25 driver-btm-soc.c:2961:set_baud: set baud=1
2019-02-28 15:18:25 chip1391.c:336:set_baud_one_chain: cmd_buf[0]=0x51090018, cmd_buf[1]=0x2101, cmd_buf[2]=0x11000000, misc=0x2101
2019-02-28 15:18:25 chip1391.c:336:set_baud_one_chain: cmd_buf[0]=0x51090018, cmd_buf[1]=0x2101, cmd_buf[2]=0x11000000, misc=0x2101
2019-02-28 15:18:25 chip1391.c:336:set_baud_one_chain: cmd_buf[0]=0x51090018, cmd_buf[1]=0x2101, cmd_buf[2]=0x11000000, misc=0x2101
2019-02-28 15:18:25 driver-btm-soc.c:2972:set_baud: read bc write is 0x82001a
2019-02-28 15:18:25 driver-btm-soc.c:4037:set_clock_delay_control: core_data = 0x04
2019-02-28 15:18:25 driver-btm-soc.c:7831:bitmain_soc_init: Open 1/4 core for reading temperature.
2019-02-28 15:18:25 driver-btm-soc.c:3953:open_core_BM1391_pre_open: pre open core = 16
2019-02-28 15:18:26 driver-btm-soc.c:3928:pre_open_core_one_chain: for chain 0
2019-02-28 15:18:26 driver-btm-soc.c:3928:pre_open_core_one_chain: for chain 1
2019-02-28 15:18:27 driver-btm-soc.c:3928:pre_open_core_one_chain: for chain 2
2019-02-28 15:18:27 temperature.c:240:is_tempsensor_data_correct: Bad,temp_info.type = 0
2019-02-28 15:18:27 temperature.c:356:calibration_sensor_offset: chain[0] temp info,Bad. Reload from eeprom..
sensor type = 0,sensor num = 4
sensor pos: 15  11  45  41  0  0  0  0
sensor offset: 0  0  0  0  0  0  0  0
2019-02-28 15:18:27 temperature.c:382:calibration_sensor_offset: chain[0] temp chip I2C addr=0x98
2019-02-28 15:18:27 temperature.c:240:is_tempsensor_data_correct: Bad,temp_info.type = 0
2019-02-28 15:18:27 temperature.c:465:calibration_sensor_offset: Warning: Chain[0] has no temp info ! we will fix it
2019-02-28 15:18:27 chip1391.c:723:set_misc_control: cmd_buf[0]=0x41093818, cmd_buf[1]=0x6131, cmd_buf[2]=0x2000000, misc=0x6131
2019-02-28 15:18:28 temperature.c:487:calibration_sensor_offset: Chain[0] use default temp chip[14]
2019-02-28 15:18:28 temperature.c:496:calibration_sensor_offset: Chain[0] Chip[14] get middle temp offset=-5 typeID=55
2019-02-28 15:18:28 chip1391.c:723:set_misc_control: cmd_buf[0]=0x41092818, cmd_buf[1]=0x6131, cmd_buf[2]=0x1000000, misc=0x6131
2019-02-28 15:18:29 temperature.c:487:calibration_sensor_offset: Chain[0] use default temp chip[10]
2019-02-28 15:18:29 temperature.c:496:calibration_sensor_offset: Chain[0] Chip[10] get middle temp offset=-5 typeID=55
2019-02-28 15:18:29 chip1391.c:723:set_misc_control: cmd_buf[0]=0x4109b018, cmd_buf[1]=0x6131, cmd_buf[2]=0x9000000, misc=0x6131
2019-02-28 15:18:30 temperature.c:487:calibration_sensor_offset: Chain[0] use default temp chip[44]
2019-02-28 15:18:30 temperature.c:496:calibration_sensor_offset: Chain[0] Chip[44] get middle temp offset=-5 typeID=55
2019-02-28 15:18:30 chip1391.c:723:set_misc_control: cmd_buf[0]=0x4109a018, cmd_buf[1]=0x6131, cmd_buf[2]=0xa000000, misc=0x6131
2019-02-28 15:18:30 temperature.c:487:calibration_sensor_offset: Chain[0] use default temp chip[40]
2019-02-28 15:18:31 temperature.c:496:calibration_sensor_offset: Chain[0] Chip[40] get middle temp offset=-5 typeID=55
2019-02-28 15:18:31 temperature.c:240:is_tempsensor_data_correct: Bad,temp_info.type = 0
2019-02-28 15:18:31 temperature.c:356:calibration_sensor_offset: chain[1] temp info,Bad. Reload from eeprom..
sensor type = 0,sensor num = 4
sensor pos: 15  11  45  41  0  0  0  0
sensor offset: 0  0  0  0  0  0  0  0
2019-02-28 15:18:31 temperature.c:382:calibration_sensor_offset: chain[1] temp chip I2C addr=0x98
2019-02-28 15:18:31 temperature.c:240:is_tempsensor_data_correct: Bad,temp_info.type = 0
2019-02-28 15:18:31 temperature.c:465:calibration_sensor_offset: Warning: Chain[1] has no temp info ! we will fix it
2019-02-28 15:18:31 chip1391.c:723:set_misc_control: cmd_buf[0]=0x41093818, cmd_buf[1]=0x6131, cmd_buf[2]=0x2000000, misc=0x6131
2019-02-28 15:18:31 temperature.c:487:calibration_sensor_offset: Chain[1] use default temp chip[14]
2019-02-28 15:18:32 temperature.c:496:calibration_sensor_offset: Chain[1] Chip[14] get middle temp offset=-5 typeID=55
2019-02-28 15:18:32 chip1391.c:723:set_misc_control: cmd_buf[0]=0x41092818, cmd_buf[1]=0x6131, cmd_buf[2]=0x1000000, misc=0x6131
2019-02-28 15:18:32 temperature.c:487:calibration_sensor_offset: Chain[1] use default temp chip[10]
2019-02-28 15:18:33 temperature.c:496:calibration_sensor_offset: Chain[1] Chip[10] get middle temp offset=-5 typeID=55
2019-02-28 15:18:33 chip1391.c:723:set_misc_control: cmd_buf[0]=0x4109b018, cmd_buf[1]=0x6131, cmd_buf[2]=0x9000000, misc=0x6131
2019-02-28 15:18:33 temperature.c:487:calibration_sensor_offset: Chain[1] use default temp chip[44]
2019-02-28 15:18:34 temperature.c:496:calibration_sensor_offset: Chain[1] Chip[44] get middle temp offset=-5 typeID=55
2019-02-28 15:18:34 chip1391.c:723:set_misc_control: cmd_buf[0]=0x4109a018, cmd_buf[1]=0x6131, cmd_buf[2]=0xa000000, misc=0x6131
2019-02-28 15:18:34 temperature.c:487:calibration_sensor_offset: Chain[1] use default temp chip[40]
2019-02-28 15:18:35 temperature.c:496:calibration_sensor_offset: Chain[1] Chip[40] get middle temp offset=-5 typeID=55
2019-02-28 15:18:35 temperature.c:240:is_tempsensor_data_correct: Bad,temp_info.type = 0
2019-02-28 15:18:35 temperature.c:356:calibration_sensor_offset: chain[2] temp info,Bad. Reload from eeprom..
sensor type = 0,sensor num = 4
sensor pos: 15  11  45  41  0  0  0  0
sensor offset: 0  0  0  0  0  0  0  0
2019-02-28 15:18:35 temperature.c:382:calibration_sensor_offset: chain[2] temp chip I2C addr=0x98
2019-02-28 15:18:35 temperature.c:240:is_tempsensor_data_correct: Bad,temp_info.type = 0
2019-02-28 15:18:35 temperature.c:465:calibration_sensor_offset: Warning: Chain[2] has no temp info ! we will fix it
2019-02-28 15:18:35 chip1391.c:723:set_misc_control: cmd_buf[0]=0x41093818, cmd_buf[1]=0x6131, cmd_buf[2]=0x2000000, misc=0x6131
2019-02-28 15:18:35 temperature.c:487:calibration_sensor_offset: Chain[2] use default temp chip[14]
2019-02-28 15:18:36 temperature.c:496:calibration_sensor_offset: Chain[2] Chip[14] get middle temp offset=-5 typeID=55
2019-02-28 15:18:36 chip1391.c:723:set_misc_control: cmd_buf[0]=0x41092818, cmd_buf[1]=0x6131, cmd_buf[2]=0x1000000, misc=0x6131
2019-02-28 15:18:36 temperature.c:487:calibration_sensor_offset: Chain[2] use default temp chip[10]
2019-02-28 15:18:37 temperature.c:496:calibration_sensor_offset: Chain[2] Chip[10] get middle temp offset=-5 typeID=55
2019-02-28 15:18:37 chip1391.c:723:set_misc_control: cmd_buf[0]=0x4109b018, cmd_buf[1]=0x6131, cmd_buf[2]=0x9000000, misc=0x6131
2019-02-28 15:18:37 temperature.c:487:calibration_sensor_offset: Chain[2] use default temp chip[44]
2019-02-28 15:18:38 temperature.c:496:calibration_sensor_offset: Chain[2] Chip[44] get middle temp offset=-5 typeID=55
2019-02-28 15:18:38 chip1391.c:723:set_misc_control: cmd_buf[0]=0x4109a018, cmd_buf[1]=0x6131, cmd_buf[2]=0xa000000, misc=0x6131
2019-02-28 15:18:38 temperature.c:487:calibration_sensor_offset: Chain[2] use default temp chip[40]
2019-02-28 15:18:39 temperature.c:496:calibration_sensor_offset: Chain[2] Chip[40] get middle temp offset=-5 typeID=55
2019-02-28 15:18:42 temperature.c:521:do_calibration_temperature_sensor: bring up lowest temperature is 26
2019-02-28 15:18:42 driver-btm-soc.c:7838:bitmain_soc_init: set TICKET_MASK
2019-02-28 15:18:42 driver-btm-soc.c:4091:open_core_bm1391: Start Open Core!!
2019-02-28 15:18:49 driver-btm-soc.c:4163:open_core_bm1391: End Open Core!!
2019-02-28 15:18:49 freq_tuning.c:291:freq_tuning_get_max_freq: Max freq of tuning is 550
2019-02-28 15:18:50 driver-btm-soc.c:1384:get_eeprom_total_hash_rate: total rate = 23330
2019-02-28 15:18:50 power.c:381:slowly_set_iic_power_to_working_voltage: slowly setting to voltage: 19.30 ...
2019-02-28 15:18:50 power.c:198:get_power_voltage_from_iic_value: iic_index for voltage[24] = 19.887610
2019-02-28 15:18:50 power.c:229:set_iic_power_by_iic_data: now setting voltage to : 20.000000
2019-02-28 15:18:51 power.c:198:get_power_voltage_from_iic_value: iic_index for voltage[31] = 19.770810
2019-02-28 15:18:51 power.c:229:set_iic_power_by_iic_data: now setting voltage to : 19.887610
2019-02-28 15:18:52 power.c:198:get_power_voltage_from_iic_value: iic_index for voltage[38] = 19.654010
2019-02-28 15:18:52 power.c:229:set_iic_power_by_iic_data: now setting voltage to : 19.770810
2019-02-28 15:18:53 power.c:198:get_power_voltage_from_iic_value: iic_index for voltage[45] = 19.537210
2019-02-28 15:18:53 power.c:229:set_iic_power_by_iic_data: now setting voltage to : 19.654010
2019-02-28 15:18:54 power.c:198:get_power_voltage_from_iic_value: iic_index for voltage[52] = 19.420410
2019-02-28 15:18:54 power.c:229:set_iic_power_by_iic_data: now setting voltage to : 19.537210
2019-02-28 15:18:55 power.c:198:get_power_voltage_from_iic_value: iic_index for voltage[54] = 19.387039
2019-02-28 15:18:55 power.c:229:set_iic_power_by_iic_data: now setting voltage to : 19.420410
2019-02-28 15:18:56 power.c:198:get_power_voltage_from_iic_value: iic_index for voltage[56] = 19.353667
2019-02-28 15:18:56 power.c:229:set_iic_power_by_iic_data: now setting voltage to : 19.387039
2019-02-28 15:18:57 power.c:198:get_power_voltage_from_iic_value: iic_index for voltage[58] = 19.320296
2019-02-28 15:18:57 power.c:229:set_iic_power_by_iic_data: now setting voltage to : 19.353667
2019-02-28 15:18:58 power.c:198:get_power_voltage_from_iic_value: iic_index for voltage[59] = 19.303610
2019-02-28 15:18:58 power.c:229:set_iic_power_by_iic_data: now setting voltage to : 19.320296
2019-02-28 15:18:59 driver-btm-soc.c:6589:increase_freq_by_eeprom_slowly: Increase eeprom frequency slowly for chain 0. to 505
2019-02-28 15:18:59 driver-btm-soc.c:4924:increase_freq_slowly:

Increase frequency to 125.00M
2019-02-28 15:19:00 driver-btm-soc.c:4924:increase_freq_slowly:

Increase frequency to 150.00M
2019-02-28 15:19:01 driver-btm-soc.c:4924:increase_freq_slowly:

Increase frequency to 175.00M
2019-02-28 15:19:02 driver-btm-soc.c:4924:increase_freq_slowly:

Increase frequency to 200.00M
2019-02-28 15:19:03 driver-btm-soc.c:4924:increase_freq_slowly:

Increase frequency to 225.00M
2019-02-28 15:19:04 driver-btm-soc.c:4924:increase_freq_slowly:

Increase frequency to 250.00M
2019-02-28 15:19:05 driver-btm-soc.c:4924:increase_freq_slowly:

Increase frequency to 275.00M
2019-02-28 15:19:06 driver-btm-soc.c:4924:increase_freq_slowly:

Increase frequency to 300.00M
2019-02-28 15:19:07 driver-btm-soc.c:4924:increase_freq_slowly:

Increase frequency to 325.00M
2019-02-28 15:19:08 driver-btm-soc.c:4924:increase_freq_slowly:

Increase frequency to 350.00M
2019-02-28 15:19:09 driver-btm-soc.c:4924:increase_freq_slowly:

Increase frequency to 375.00M
2019-02-28 15:19:11 driver-btm-soc.c:4924:increase_freq_slowly:

Increase frequency to 400.00M
2019-02-28 15:19:12 driver-btm-soc.c:4924:increase_freq_slowly:

Increase frequency to 425.00M
2019-02-28 15:19:13 driver-btm-soc.c:4924:increase_freq_slowly:

Increase frequency to 450.00M
2019-02-28 15:19:14 driver-btm-soc.c:4924:increase_freq_slowly:

Increase frequency to 475.00M
2019-02-28 15:19:15 driver-btm-soc.c:4924:increase_freq_slowly:

Increase frequency to 500.00M
2019-02-28 15:19:16 driver-btm-soc.c:4924:increase_freq_slowly:

Increase frequency to 505.00M
2019-02-28 15:19:17 driver-btm-soc.c:6589:increase_freq_by_eeprom_slowly: Increase eeprom frequency slowly for chain 1. to 510
2019-02-28 15:19:17 driver-btm-soc.c:4924:increase_freq_slowly:

Increase frequency to 125.00M
2019-02-28 15:19:18 driver-btm-soc.c:4924:increase_freq_slowly:

Increase frequency to 150.00M
2019-02-28 15:19:19 driver-btm-soc.c:4924:increase_freq_slowly:

Increase frequency to 175.00M
2019-02-28 15:19:20 driver-btm-soc.c:4924:increase_freq_slowly:

Increase frequency to 200.00M
2019-02-28 15:19:21 driver-btm-soc.c:4924:increase_freq_slowly:

Increase frequency to 225.00M
2019-02-28 15:19:22 driver-btm-soc.c:4924:increase_freq_slowly:

Increase frequency to 250.00M
2019-02-28 15:19:23 driver-btm-soc.c:4924:increase_freq_slowly:

Increase frequency to 275.00M
2019-02-28 15:19:24 driver-btm-soc.c:4924:increase_freq_slowly:

Increase frequency to 300.00M
2019-02-28 15:19:25 driver-btm-soc.c:4924:increase_freq_slowly:

Increase frequency to 325.00M
2019-02-28 15:19:26 driver-btm-soc.c:4924:increase_freq_slowly:

Increase frequency to 350.00M
2019-02-28 15:19:27 driver-btm-soc.c:4924:increase_freq_slowly:

Increase frequency to 375.00M
2019-02-28 15:19:28 driver-btm-soc.c:4924:increase_freq_slowly:

Increase frequency to 400.00M
2019-02-28 15:19:29 driver-btm-soc.c:4924:increase_freq_slowly:

Increase frequency to 425.00M
2019-02-28 15:19:30 driver-btm-soc.c:4924:increase_freq_slowly:

Increase frequency to 450.00M
2019-02-28 15:19:31 driver-btm-soc.c:4924:increase_freq_slowly:

Increase frequency to 475.00M
2019-02-28 15:19:32 driver-btm-soc.c:4924:increase_freq_slowly:

Increase frequency to 500.00M
2019-02-28 15:19:33 driver-btm-soc.c:4924:increase_freq_slowly:

Increase frequency to 510.00M
2019-02-28 15:19:34 driver-btm-soc.c:6589:increase_freq_by_eeprom_slowly: Increase eeprom frequency slowly for chain 2. to 510
2019-02-28 15:19:34 driver-btm-soc.c:4924:increase_freq_slowly:

Increase frequency to 125.00M
2019-02-28 15:19:36 driver-btm-soc.c:4924:increase_freq_slowly:

Increase frequency to 150.00M
2019-02-28 15:19:37 driver-btm-soc.c:4924:increase_freq_slowly:

Increase frequency to 175.00M
2019-02-28 15:19:38 driver-btm-soc.c:4924:increase_freq_slowly:

Increase frequency to 200.00M
2019-02-28 15:19:39 driver-btm-soc.c:4924:increase_freq_slowly:

Increase frequency to 225.00M
2019-02-28 15:19:40 driver-btm-soc.c:4924:increase_freq_slowly:

Increase frequency to 250.00M
2019-02-28 15:19:41 driver-btm-soc.c:4924:increase_freq_slowly:

Increase frequency to 275.00M
2019-02-28 15:19:42 driver-btm-soc.c:4924:increase_freq_slowly:

Increase frequency to 300.00M
2019-02-28 15:19:43 driver-btm-soc.c:4924:increase_freq_slowly:

Increase frequency to 325.00M
2019-02-28 15:19:44 driver-btm-soc.c:4924:increase_freq_slowly:

Increase frequency to 350.00M
2019-02-28 15:19:45 driver-btm-soc.c:4924:increase_freq_slowly:

Increase frequency to 375.00M
2019-02-28 15:19:46 driver-btm-soc.c:4924:increase_freq_slowly:

Increase frequency to 400.00M
2019-02-28 15:19:47 driver-btm-soc.c:4924:increase_freq_slowly:

Increase frequency to 425.00M
2019-02-28 15:19:48 driver-btm-soc.c:4924:increase_freq_slowly:

Increase frequency to 450.00M
2019-02-28 15:19:49 driver-btm-soc.c:4924:increase_freq_slowly:

Increase frequency to 475.00M
2019-02-28 15:19:50 driver-btm-soc.c:4924:increase_freq_slowly:

Increase frequency to 500.00M
2019-02-28 15:19:51 driver-btm-soc.c:4924:increase_freq_slowly:

Increase frequency to 510.00M
2019-02-28 15:19:52 driver-btm-soc.c:5989:set_timeout: freq 510 final timeout=462
2019-02-28 15:19:53 freq_tuning.c:1812:freq_tuning_pre_test_for_user_mode: Pre-test: start.
2019-02-28 15:19:53 freq_tuning.c:1816:freq_tuning_pre_test_for_user_mode: Pre-test: times 0
2019-02-28 15:19:53 freq_tuning.c:966:freq_tuning_send_work: Frequency tuning: send work start.
2019-02-28 15:19:53 freq_tuning.c:881:freq_tuning_send_work_one_chain: Frequency tuning: send work for chain 2
2019-02-28 15:19:53 freq_tuning.c:881:freq_tuning_send_work_one_chain: Frequency tuning: send work for chain 1
2019-02-28 15:19:53 freq_tuning.c:881:freq_tuning_send_work_one_chain: Frequency tuning: send work for chain 0
2019-02-28 15:20:50 freq_tuning.c:954:freq_tuning_send_work_one_chain: Frequency tuning: send work for chain 2 done, time cost 56s, sleep_count = 52340
2019-02-28 15:20:50 freq_tuning.c:954:freq_tuning_send_work_one_chain: Frequency tuning: send work for chain 1 done, time cost 56s, sleep_count = 52342
2019-02-28 15:20:50 freq_tuning.c:954:freq_tuning_send_work_one_chain: Frequency tuning: send work for chain 0 done, time cost 56s, sleep_count = 52338
2019-02-28 15:20:50 freq_tuning.c:1016:freq_tuning_send_work: Frequency tuning: send work done, time cost 57s
2019-02-28 15:20:51 freq_tuning.c:432:freq_tuning_parameter_dump: ======== dump freq tuning result ========
chain 0
send_work_num                  : 122880
valid_nonce_num                : 122787
nonce_return_rate              : 0.999243
repeated_nonce_num             : 2596
extra_nonce_num                : 1594
invalid_nonce_num              : 0
crc_err_nonce_num              : 0
err_nonce_num                  : 0
chain_hw_num                   : 0

chain 1
send_work_num                  : 122880
valid_nonce_num                : 122707
nonce_return_rate              : 0.998592
repeated_nonce_num             : 2640
extra_nonce_num                : 1606
invalid_nonce_num              : 0
crc_err_nonce_num              : 0
err_nonce_num                  : 0
chain_hw_num                   : 0

chain 2
send_work_num                  : 122880
valid_nonce_num                : 122799
nonce_return_rate              : 0.999341
repeated_nonce_num             : 2598
extra_nonce_num                : 1608
invalid_nonce_num              : 0
crc_err_nonce_num              : 0
err_nonce_num                  : 0
chain_hw_num                   : 0

asic_invalid_num               : 0
chain_invalid_num              : 0
nonce_recv_num_all             : 380935
nonce_recv_num_diff            : 0

chain 0 asic_nonce_num:
IC[00]:2044 IC[01]:2047 IC[02]:2048 IC[03]:2046 IC[04]:2048
IC[05]:2048 IC[06]:2047 IC[07]:2048 IC[08]:2048 IC[09]:2046
IC[10]:2044 IC[11]:2039 IC[12]:2047 IC[13]:2047 IC[14]:2045
IC[15]:2048 IC[16]:2048 IC[17]:2048 IC[18]:2047 IC[19]:2047
IC[20]:2046 IC[21]:2046 IC[22]:2048 IC[23]:2047 IC[24]:2045
IC[25]:2048 IC[26]:2048 IC[27]:2045 IC[28]:2048 IC[29]:2047
IC[30]:2047 IC[31]:2047 IC[32]:2043 IC[33]:2048 IC[34]:2048
IC[35]:2048 IC[36]:2048 IC[37]:2046 IC[38]:2048 IC[39]:2041
IC[40]:2045 IC[41]:2033 IC[42]:2045 IC[43]:2048 IC[44]:2048
IC[45]:2048 IC[46]:2048 IC[47]:2047 IC[48]:2048 IC[49]:2048
IC[50]:2048 IC[51]:2044 IC[52]:2046 IC[53]:2044 IC[54]:2048
IC[55]:2048 IC[56]:2048 IC[57]:2048 IC[58]:2048 IC[59]:2045

chain 1 asic_nonce_num:
IC[00]:2040 IC[01]:2045 IC[02]:2047 IC[03]:2046 IC[04]:2047
IC[05]:2047 IC[06]:2045 IC[07]:2035 IC[08]:2043 IC[09]:2039
IC[10]:2047 IC[11]:2048 IC[12]:2045 IC[13]:2047 IC[14]:2048
IC[15]:2048 IC[16]:2046 IC[17]:2048 IC[18]:2045 IC[19]:2044
IC[20]:2048 IC[21]:2044 IC[22]:2041 IC[23]:2047 IC[24]:2048
IC[25]:2046 IC[26]:2038 IC[27]:2048 IC[28]:2048 IC[29]:2048
IC[30]:2044 IC[31]:2046 IC[32]:2047 IC[33]:2048 IC[34]:2043
IC[35]:2045 IC[36]:2048 IC[37]:2046 IC[38]:2048 IC[39]:2044
IC[40]:2038 IC[41]:2047 IC[42]:2047 IC[43]:2043 IC[44]:2048
IC[45]:2046 IC[46]:2046 IC[47]:2038 IC[48]:2043 IC[49]:2046
IC[50]:2037 IC[51]:2044 IC[52]:2048 IC[53]:2044 IC[54]:2046
IC[55]:2045 IC[56]:2046 IC[57]:2045 IC[58]:2047 IC[59]:2048

chain 2 asic_nonce_num:
IC[00]:2046 IC[01]:2048 IC[02]:2048 IC[03]:2048 IC[04]:2048
IC[05]:2045 IC[06]:2048 IC[07]:2048 IC[08]:2047 IC[09]:2047
IC[10]:2044 IC[11]:2043 IC[12]:2048 IC[13]:2048 IC[14]:2046
IC[15]:2048 IC[16]:2048 IC[17]:2046 IC[18]:2047 IC[19]:2048
IC[20]:2048 IC[21]:2048 IC[22]:2044 IC[23]:2046 IC[24]:2048
IC[25]:2048 IC[26]:2048 IC[27]:2048 IC[28]:2046 IC[29]:2048
IC[30]:2046 IC[31]:2047 IC[32]:2048 IC[33]:2043 IC[34]:2048
IC[35]:2047 IC[36]:2048 IC[37]:2047 IC[38]:2048 IC[39]:2047
IC[40]:2033 IC[41]:2048 IC[42]:2048 IC[43]:2048 IC[44]:2045
IC[45]:2047 IC[46]:2047 IC[47]:2048 IC[48]:2047 IC[49]:2043
IC[50]:2048 IC[51]:2048 IC[52]:2048 IC[53]:2047 IC[54]:2045
IC[55]:2046 IC[56]:2047 IC[57]:2048 IC[58]:2046 IC[59]:2042

chain 0 domain_nonce_num:
D[00]:2560 D[01]:2559 D[02]:2557 D[03]:2557  D_BIG[00]:10233
D[04]:2558 D[05]:2559 D[06]:2560 D[07]:2560  D_BIG[01]:10237
D[08]:2559 D[09]:2554 D[10]:2555 D[11]:2554  D_BIG[02]:10222
D[12]:2560 D[13]:2560 D[14]:2560 D[15]:2558  D_BIG[03]:10238
D[16]:2559 D[17]:2558 D[18]:2559 D[19]:2556  D_BIG[04]:10232
D[20]:2559 D[21]:2560 D[22]:2557 D[23]:2560  D_BIG[05]:10236
D[24]:2560 D[25]:2557 D[26]:2556 D[27]:2560  D_BIG[06]:10233
D[28]:2559 D[29]:2554 D[30]:2558 D[31]:2560  D_BIG[07]:10231
D[32]:2556 D[33]:2551 D[34]:2559 D[35]:2553  D_BIG[08]:10219
D[36]:2560 D[37]:2560 D[38]:2560 D[39]:2559  D_BIG[09]:10239
D[40]:2559 D[41]:2555 D[42]:2556 D[43]:2560  D_BIG[10]:10230
D[44]:2559 D[45]:2560 D[46]:2560 D[47]:2558  D_BIG[11]:10237

chain 1 domain_nonce_num:
D[00]:2558 D[01]:2558 D[02]:2550 D[03]:2559  D_BIG[00]:10225
D[04]:2550 D[05]:2558 D[06]:2552 D[07]:2549  D_BIG[01]:10209
D[08]:2556 D[09]:2560 D[10]:2559 D[11]:2560  D_BIG[02]:10235
D[12]:2555 D[13]:2559 D[14]:2559 D[15]:2558  D_BIG[03]:10231
D[16]:2558 D[17]:2560 D[18]:2554 D[19]:2556  D_BIG[04]:10228
D[20]:2555 D[21]:2560 D[22]:2554 D[23]:2559  D_BIG[05]:10228
D[24]:2559 D[25]:2554 D[26]:2559 D[27]:2556  D_BIG[06]:10228
D[28]:2557 D[29]:2557 D[30]:2560 D[31]:2557  D_BIG[07]:10231
D[32]:2556 D[33]:2558 D[34]:2558 D[35]:2551  D_BIG[08]:10223
D[36]:2554 D[37]:2554 D[38]:2559 D[39]:2552  D_BIG[09]:10219
D[40]:2555 D[41]:2553 D[42]:2553 D[43]:2558  D_BIG[10]:10219
D[44]:2559 D[45]:2557 D[46]:2558 D[47]:2557  D_BIG[11]:10231

chain 2 domain_nonce_num:
D[00]:2560 D[01]:2558 D[02]:2560 D[03]:2560  D_BIG[00]:10238
D[04]:2559 D[05]:2560 D[06]:2560 D[07]:2556  D_BIG[01]:10235
D[08]:2560 D[09]:2556 D[10]:2554 D[11]:2559  D_BIG[02]:10229
D[12]:2560 D[13]:2560 D[14]:2560 D[15]:2557  D_BIG[03]:10237
D[16]:2560 D[17]:2560 D[18]:2558 D[19]:2556  D_BIG[04]:10234
D[20]:2558 D[21]:2560 D[22]:2560 D[23]:2560  D_BIG[05]:10238
D[24]:2560 D[25]:2554 D[26]:2558 D[27]:2560  D_BIG[06]:10232
D[28]:2559 D[29]:2559 D[30]:2559 D[31]:2560  D_BIG[07]:10237
D[32]:2554 D[33]:2557 D[34]:2553 D[35]:2558  D_BIG[08]:10222
D[36]:2556 D[37]:2558 D[38]:2560 D[39]:2558  D_BIG[09]:10232
D[40]:2557 D[41]:2560 D[42]:2559 D[43]:2560  D_BIG[10]:10236
D[44]:2557 D[45]:2560 D[46]:2559 D[47]:2553  D_BIG[11]:10229

2019-02-28 15:20:51 freq_tuning.c:1111:freq_tuning_wait_recv_nonce: ++++ CRC ERROR = 51680
2019-02-28 15:20:51 freq_tuning.c:1051:freq_tuning_check_domain_unbalance: Check domain unbalance.
2019-02-28 15:20:51 freq_tuning.c:1769:freq_tuning_single_pre_test_for_user_mode: Pre-test: already balance.
2019-02-28 15:20:51 freq_tuning.c:1834:freq_tuning_pre_test_for_user_mode: Pre-test: done.
2019-02-28 15:20:51 freq_tuning.c:2974:do_pre_test_for_user_mode: Pre-test cost 59s.
2019-02-28 15:20:53 power.c:439:get_chain_voltage: chain[0], voltage is: 19.29
2019-02-28 15:20:53 power.c:439:get_chain_voltage: chain[1], voltage is: 19.36
2019-02-28 15:20:54 power.c:439:get_chain_voltage: chain[2], voltage is: 19.24
2019-02-28 15:20:54 power.c:462:get_average_voltage: average  voltage is: 19.30
2019-02-28 15:20:54 driver-btm-soc.c:7909:bitmain_soc_init: Init done!
2019-02-28 15:20:54 util.c:2178:process_version_mask: Pool 0 Verion num is 2
2019-02-28 15:20:54 util.c:2178:process_version_mask: Pool 0 Verion num is 2
2019-02-28 15:20:54 temperature.c:1026:read_temp_func: bring_up_pcb_temp = 32
2019-02-28 15:20:55 driver-btm-soc.c:8291:send_job: Version num 2
2019-02-28 15:21:22 dspic33ep16gs202.c:65:volt_clamp: failed on Chain[0], b[0] = 254, b[2] = 254!
2019-02-28 15:21:23 dspic33ep16gs202.c:65:volt_clamp: failed on Chain[0], b[0] = 254, b[2] = 254!
2019-02-28 15:21:25 dspic33ep16gs202.c:65:volt_clamp: failed on Chain[0], b[0] = 254, b[2] = 254!
2019-02-28 15:21:26 dspic33ep16gs202.c:65:volt_clamp: failed on Chain[1], b[0] = 254, b[2] = 254!
2019-02-28 15:21:28 dspic33ep16gs202.c:65:volt_clamp: failed on Chain[1], b[0] = 254, b[2] = 254!
2019-02-28 15:21:30 dspic33ep16gs202.c:65:volt_clamp: failed on Chain[1], b[0] = 254, b[2] = 254!
2019-02-28 15:21:32 dspic33ep16gs202.c:65:volt_clamp: failed on Chain[2], b[0] = 254, b[2] = 254!
2019-02-28 15:21:34 dspic33ep16gs202.c:65:volt_clamp: failed on Chain[2], b[0] = 254, b[2] = 254!
2019-02-28 15:21:35 dspic33ep16gs202.c:65:volt_clamp: failed on Chain[2], b[0] = 254, b[2] = 254!
Pages:
Jump to: