Jump to content
urikedr

Проблема с S17

Recommended Posts

Скрытый текст

 

Доброго времени дня! Купил 3 недели назад s17, Работал норм. Сегодня смотрю одна плата пошла крестами, попробовал перезагрузить он не запускается. Пробовал восстановить заводские настройки, перепрошил, не помогает. При запуске в Karnel Log пишет следующее:

2019-06-08 07:05:35 driver-btm-api.c:773:init_freq_mode: This is scan-user version
2019-06-08 07:05:35 driver-btm-api.c:1891:bitmain_soc_init: opt_multi_version     = 1
2019-06-08 07:05:35 driver-btm-api.c:1892:bitmain_soc_init: opt_bitmain_ab        = 1
2019-06-08 07:05:35 driver-btm-api.c:1893:bitmain_soc_init: opt_bitmain_work_mode = 0
2019-06-08 07:05:35 driver-btm-api.c:1894:bitmain_soc_init: Miner compile time: Mon May 27 10:57:13 CST 2019 type: Antminer S17 Pro
2019-06-08 07:05: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
2019-06-08 07:05:35 driver-btm-api.c:1778:show_sn: no SN got, please write SN to /nvdata/sn
2019-06-08 07:05:35 driver-btm-api.c:1251:miner_device_init: Detect 256MB control board of XILINX
2019-06-08 07:05:35 driver-btm-api.c:1199:init_fan_parameter: fan_eft : 0  fan_pwm : 0
2019-06-08 07:05:35 thread.c:627:create_read_nonce_reg_thread: create thread
2019-06-08 07:05:41 driver-btm-api.c:1183:init_miner_version: miner ID : 804ce54e57408854
2019-06-08 07:05:41 driver-btm-api.c:1189:init_miner_version: FPGA Version = 0xB011
2019-06-08 07:05:46 driver-btm-api.c:835:get_product_id: product_id[0] = 0
2019-06-08 07:05:46 driver-btm-api.c:835:get_product_id: product_id[1] = 0
2019-06-08 07:05:46 driver-btm-api.c:835:get_product_id: product_id[2] = 0
2019-06-08 07:05:46 driver-btm-api.c:786:_set_project_type: project:0
2019-06-08 07:05:46 driver-btm-api.c:811:_set_project_type: Project type: Antminer S17 Pro
2019-06-08 07:05:46 driver-btm-api.c:822:dump_pcb_bom_version: Chain [0] PCB Version: 0x0101
2019-06-08 07:05:46 driver-btm-api.c:823:dump_pcb_bom_version: Chain [0] BOM Version: 0x0103
2019-06-08 07:05:46 driver-btm-api.c:822:dump_pcb_bom_version: Chain [1] PCB Version: 0x0101
2019-06-08 07:05:46 driver-btm-api.c:823:dump_pcb_bom_version: Chain [1] BOM Version: 0x0103
2019-06-08 07:05:46 driver-btm-api.c:822:dump_pcb_bom_version: Chain [2] PCB Version: 0x0101
2019-06-08 07:05:46 driver-btm-api.c:823:dump_pcb_bom_version: Chain [2] BOM Version: 0x0103
2019-06-08 07:05:47 driver-btm-api.c:1841:bitmain_board_init: Fan check passed.
2019-06-08 07:05:49 board.c:36:jump_and_app_check_restore_pic: chain[0] PIC jump to app
2019-06-08 07:05:52 board.c:40:jump_and_app_check_restore_pic: Check chain[0] PIC fw version=0xb9
2019-06-08 07:05:54 board.c:36:jump_and_app_check_restore_pic: chain[1] PIC jump to app
2019-06-08 07:05:58 board.c:40:jump_and_app_check_restore_pic: Check chain[1] PIC fw version=0xb9
2019-06-08 07:05:59 board.c:36:jump_and_app_check_restore_pic: chain[2] PIC jump to app
2019-06-08 07:06:03 board.c:40:jump_and_app_check_restore_pic: Check chain[2] PIC fw version=0xb9
2019-06-08 07:06:03 thread.c:622:create_pic_heart_beat_thread: create thread
2019-06-08 07:06:03 power_api.c:55:power_init: power init ... 
2019-06-08 07:06:03 driver-btm-api.c:1851:bitmain_board_init: Enter 30s sleep to make sure power release finish.
2019-06-08 07:06:35 power_api.c:164:set_iic_power_to_highest_voltage: setting to voltage: 21.00 ...
2019-06-08 07:06:40 power_api.c:113:set_iic_power_by_voltage: now setting voltage to : 21.000000 
2019-06-08 07:06:52 driver-btm-api.c:1126:check_asic_number_with_power_on: Chain[0]: find 48 asic, times 0
2019-06-08 07:07:04 driver-btm-api.c:1126:check_asic_number_with_power_on: Chain[1]: find 48 asic, times 0
2019-06-08 07:07:16 driver-btm-api.c:1126:check_asic_number_with_power_on: Chain[2]: find 48 asic, times 0
2019-06-08 07:07:16 driver-btm-api.c:336:set_order_clock: chain[0]: set order clock, stragegy 3
2019-06-08 07:07:16 driver-btm-api.c:336:set_order_clock: chain[1]: set order clock, stragegy 3
2019-06-08 07:07:16 driver-btm-api.c:336:set_order_clock: chain[2]: set order clock, stragegy 3
2019-06-08 07:07:21 driver-hash-chip.c:453:set_clock_delay_control: core_data = 0x34
2019-06-08 07:07:21 voltage[0] = 1700
2019-06-08 07:07:21 voltage[1] = 1700
2019-06-08 07:07:21 voltage[2] = 1700
2019-06-08 07:07:21 power_api.c:76:set_working_voltage: working_voltage = 17.000000
2019-06-08 07:07:23 temperature.c:267:calibrate_temp_sensor_one_chain: Temperature sensor calibration: chain 0 success.
2019-06-08 07:07:24 temperature.c:267:calibrate_temp_sensor_one_chain: Temperature sensor calibration: chain 1 success.
2019-06-08 07:07:26 temperature.c:267:calibrate_temp_sensor_one_chain: Temperature sensor calibration: chain 2 success.
2019-06-08 07:07:26 driver-hash-chip.c:229:dhash_chip_set_baud_v2: chain[0]: chip baud = 6000000, chip_divider = 7
2019-06-08 07:07:26 driver-hash-chip.c:229:dhash_chip_set_baud_v2: chain[1]: chip baud = 6000000, chip_divider = 7
2019-06-08 07:07:26 driver-hash-chip.c:229:dhash_chip_set_baud_v2: chain[2]: chip baud = 6000000, chip_divider = 7
2019-06-08 07:07:26 uart.c:80:set_baud: set fpga_baud = 6000000, fpga_divider = 3
2019-06-08 07:07:28 temperature.c:681:get_temp_info: read temp sensor failed: chain = 0, chip = 40, reg = 1
2019-06-08 07:07:48 temperature.c:681:get_temp_info: read temp sensor failed: chain = 0, chip = 180, reg = 1
2019-06-08 07:08:07 temperature.c:681:get_temp_info: read temp sensor failed: chain = 0, chip = 195, reg = 1
2019-06-08 07:08:09 driver-btm-api.c:236:check_bringup_temp: Bring up temperature is -64
2019-06-08 07:08:09 driver-btm-api.c:194:set_miner_status: ERROR_TEMP_TOO_LOW
2019-06-08 07:08:09 driver-btm-api.c:135:stop_mining: stop mining: Environment temperature is too low!
2019-06-08 07:08:09 thread.c:672:cancel_read_nonce_reg_thread: cancel thread
2019-06-08 07:08:09 driver-btm-api.c:121:killall_hashboard: ****power off hashboard****

 

Подскажите, кто знает, что мне теперь делать?

 

 

Share this post


Link to post
Share on other sites
6 минут назад, urikedr сказал:

что мне теперь делать?

Придерживаться плана.  Какой план был изначально, в случае если железка сломается?

Share this post


Link to post
Share on other sites
24 минуты назад, urikedr сказал:

что мне теперь делать?

я бы для начала отключил линейку на которой пошли кресты, а не перешивал

и проверил бы интернет

 

Edited by ranko

Share this post


Link to post
Share on other sites
9 минут назад, ranko сказал:

я бы для начала отключил линейку на которой пошли кресты, а не перешивал

и проверил бы интернет

 

Повлияет ли отключение платы на гарантию? И я не знаю как это сделать. интернет работает, у меня запущен второй асик.

Share this post


Link to post
Share on other sites
Скрытый текст

 

Полный лог:

 

Booting Linux on physical CPU 0x0
Linux version 4.6.0-xilinx-gff8137b-dirty ([email protected]) (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 <[email protected]>
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 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: 12/6, WL threshold: 4096, image sequence number: 892827981
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 50879C9C-F33B-4D12-980A-80D93F150810, 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: 90/51, WL threshold: 4096, image sequence number: 37638575
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 0D892CBB-C57D-4CA7-A539-370B84C781E4, 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
2019-06-08 07:54:22 driver-btm-api.c:773:init_freq_mode: This is scan-user version
2019-06-08 07:54:22 driver-btm-api.c:1891:bitmain_soc_init: opt_multi_version     = 1
2019-06-08 07:54:22 driver-btm-api.c:1892:bitmain_soc_init: opt_bitmain_ab        = 1
2019-06-08 07:54:22 driver-btm-api.c:1893:bitmain_soc_init: opt_bitmain_work_mode = 1
2019-06-08 07:54:22 driver-btm-api.c:1894:bitmain_soc_init: Miner compile time: Mon May 27 10:57:13 CST 2019 type: Antminer S17 Pro
2019-06-08 07:54:22 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
2019-06-08 07:54:22 driver-btm-api.c:1778:show_sn: no SN got, please write SN to /nvdata/sn
2019-06-08 07:54:22 driver-btm-api.c:1251:miner_device_init: Detect 256MB control board of XILINX
2019-06-08 07:54:22 driver-btm-api.c:1199:init_fan_parameter: fan_eft : 0  fan_pwm : 0
2019-06-08 07:54:22 thread.c:627:create_read_nonce_reg_thread: create thread
2019-06-08 07:54:28 driver-btm-api.c:1183:init_miner_version: miner ID : 804ce54e57408854
2019-06-08 07:54:28 driver-btm-api.c:1189:init_miner_version: FPGA Version = 0xB011
2019-06-08 07:54:34 driver-btm-api.c:835:get_product_id: product_id[0] = 0
2019-06-08 07:54:34 driver-btm-api.c:835:get_product_id: product_id[1] = 0
2019-06-08 07:54:34 driver-btm-api.c:835:get_product_id: product_id[2] = 0
2019-06-08 07:54:34 driver-btm-api.c:786:_set_project_type: project:0
2019-06-08 07:54:34 driver-btm-api.c:811:_set_project_type: Project type: Antminer S17 Pro
2019-06-08 07:54:34 driver-btm-api.c:822:dump_pcb_bom_version: Chain [0] PCB Version: 0x0101
2019-06-08 07:54:34 driver-btm-api.c:823:dump_pcb_bom_version: Chain [0] BOM Version: 0x0103
2019-06-08 07:54:34 driver-btm-api.c:822:dump_pcb_bom_version: Chain [1] PCB Version: 0x0101
2019-06-08 07:54:34 driver-btm-api.c:823:dump_pcb_bom_version: Chain [1] BOM Version: 0x0103
2019-06-08 07:54:34 driver-btm-api.c:822:dump_pcb_bom_version: Chain [2] PCB Version: 0x0101
2019-06-08 07:54:34 driver-btm-api.c:823:dump_pcb_bom_version: Chain [2] BOM Version: 0x0103
2019-06-08 07:54:34 driver-btm-api.c:1841:bitmain_board_init: Fan check passed.
2019-06-08 07:54:35 board.c:36:jump_and_app_check_restore_pic: chain[0] PIC jump to app
2019-06-08 07:54:39 board.c:40:jump_and_app_check_restore_pic: Check chain[0] PIC fw version=0xb9
2019-06-08 07:54:41 board.c:36:jump_and_app_check_restore_pic: chain[1] PIC jump to app
2019-06-08 07:54:44 board.c:40:jump_and_app_check_restore_pic: Check chain[1] PIC fw version=0xb9
2019-06-08 07:54:46 board.c:36:jump_and_app_check_restore_pic: chain[2] PIC jump to app
2019-06-08 07:54:49 board.c:40:jump_and_app_check_restore_pic: Check chain[2] PIC fw version=0xb9
2019-06-08 07:54:49 thread.c:622:create_pic_heart_beat_thread: create thread
2019-06-08 07:54:49 power_api.c:55:power_init: power init ... 
2019-06-08 07:54:49 driver-btm-api.c:1851:bitmain_board_init: Enter 30s sleep to make sure power release finish.
2019-06-08 07:54:49 power_api.c:46:power_off: init gpio907
2019-06-08 07:55:21 power_api.c:164:set_iic_power_to_highest_voltage: setting to voltage: 21.00 ...
2019-06-08 07:55:27 power_api.c:113:set_iic_power_by_voltage: now setting voltage to : 21.000000 
2019-06-08 07:55:39 driver-btm-api.c:1126:check_asic_number_with_power_on: Chain[0]: find 48 asic, times 0
2019-06-08 07:55:51 driver-btm-api.c:1126:check_asic_number_with_power_on: Chain[1]: find 48 asic, times 0
2019-06-08 07:56:03 driver-btm-api.c:1126:check_asic_number_with_power_on: Chain[2]: find 48 asic, times 0
2019-06-08 07:56:03 driver-btm-api.c:336:set_order_clock: chain[0]: set order clock, stragegy 3
2019-06-08 07:56:03 driver-btm-api.c:336:set_order_clock: chain[1]: set order clock, stragegy 3
2019-06-08 07:56:03 driver-btm-api.c:336:set_order_clock: chain[2]: set order clock, stragegy 3
2019-06-08 07:56:08 driver-hash-chip.c:453:set_clock_delay_control: core_data = 0x34
2019-06-08 07:56:08 voltage[0] = 1780
2019-06-08 07:56:08 voltage[1] = 1780
2019-06-08 07:56:08 voltage[2] = 1780
2019-06-08 07:56:08 power_api.c:76:set_working_voltage: working_voltage = 17.800000
2019-06-08 07:56:09 temperature.c:267:calibrate_temp_sensor_one_chain: Temperature sensor calibration: chain 0 success.
2019-06-08 07:56:11 temperature.c:267:calibrate_temp_sensor_one_chain: Temperature sensor calibration: chain 1 success.
2019-06-08 07:56:12 temperature.c:267:calibrate_temp_sensor_one_chain: Temperature sensor calibration: chain 2 success.
2019-06-08 07:56:12 driver-hash-chip.c:229:dhash_chip_set_baud_v2: chain[0]: chip baud = 6000000, chip_divider = 7
2019-06-08 07:56:12 driver-hash-chip.c:229:dhash_chip_set_baud_v2: chain[1]: chip baud = 6000000, chip_divider = 7
2019-06-08 07:56:12 driver-hash-chip.c:229:dhash_chip_set_baud_v2: chain[2]: chip baud = 6000000, chip_divider = 7
2019-06-08 07:56:12 uart.c:80:set_baud: set fpga_baud = 6000000, fpga_divider = 3
2019-06-08 07:56:14 temperature.c:681:get_temp_info: read temp sensor failed: chain = 0, chip = 40, reg = 1
2019-06-08 07:56:33 temperature.c:681:get_temp_info: read temp sensor failed: chain = 0, chip = 180, reg = 1
2019-06-08 07:56:53 temperature.c:681:get_temp_info: read temp sensor failed: chain = 0, chip = 195, reg = 1
2019-06-08 07:56:54 driver-btm-api.c:236:check_bringup_temp: Bring up temperature is -64
2019-06-08 07:56:54 driver-btm-api.c:194:set_miner_status: ERROR_TEMP_TOO_LOW
2019-06-08 07:56:54 driver-btm-api.c:135:stop_mining: stop mining: Environment temperature is too low!
2019-06-08 07:56:54 thread.c:672:cancel_read_nonce_reg_thread: cancel thread
2019-06-08 07:56:54 driver-btm-api.c:121:killall_hashboard: ****power off hashboard****

 

 

Share this post


Link to post
Share on other sites

Отключил линейку на котором пошли x, асик запустился. Её можно оживить только в сервисе? И будет ли распространяться на это гарантия?

Share this post


Link to post
Share on other sites

с сервисом и гарантиями  я не в курсе, а так чем смог тем посоветовал)))

читайте форум где то и про гарантии найдёте ( на примере других моделей асиков )

Share this post


Link to post
Share on other sites
40 минут назад, ranko сказал:

с сервисом и гарантиями  я не в курсе, а так чем смог тем посоветовал)))

читайте форум где то и про гарантии найдёте ( на примере других моделей асиков )

Спасибо за помочь, далее сам разберусь!

Share this post


Link to post
Share on other sites

Тему гарантии нужно оговаривать сразу. У меня приехал S15 поломанным. Продавец отморозился сразу, сказал, что может отправить за мой счет обратно в Китай, чтобы по заводской гарантии чинили.

В итоге, плюнул, отправил мастерам в Киев, где асик привели в чувство за три дня. Был убит процессор. Обошлось в $50.

Покупал по договору (там только обязательства доставки) у OptSale. 

Share this post


Link to post
Share on other sites
08.06.2019 в 12:13, urikedr сказал:

Спасибо за помочь, далее сам разберусь!

Похожая ситуация, отработал нормально 3 дня. Потом в морде вообще не показывало ни одной платы. Ни сброс, ни перепрошивка не помогла. Начал искать какое лезвие портачит. Вытащил 3 лезвия, вставлял по одной. И о чудо- по одной все работают. Соединил обратно все вместе- заработало. Не знаю с чем было связано. Может контакт плохой был, в логи не смотрел по незнанию. Хотя сейчас все равно какие то проблемы проскакивают. Ты решил свою проблему?

Скрытый текст

2019-06-10 12:52:27 temperature.c:435:temp_statistics_show:   pcb temp 40~63  chip temp 61~80
2019-06-10 13:22:30 thread.c:164:calc_hashrate_avg: avg rate is 54347.13 in 30 mins
2019-06-10 13:22:30 temperature.c:435:temp_statistics_show:   pcb temp 40~63  chip temp 61~80
2019-06-10 13:52:33 thread.c:164:calc_hashrate_avg: avg rate is 54261.65 in 30 mins
2019-06-10 13:52:33 temperature.c:435:temp_statistics_show:   pcb temp 40~63  chip temp 61~80
2019-06-10 14:22:36 thread.c:164:calc_hashrate_avg: avg rate is 54404.05 in 30 mins
2019-06-10 14:22:36 temperature.c:435:temp_statistics_show:   pcb temp 40~63  chip temp 61~80
2019-06-10 14:52:39 thread.c:164:calc_hashrate_avg: avg rate is 54324.36 in 30 mins
2019-06-10 14:52:39 temperature.c:435:temp_statistics_show:   pcb temp 40~63  chip temp 62~80
2019-06-10 15:22:42 thread.c:164:calc_hashrate_avg: avg rate is 54407.88 in 30 mins
2019-06-10 15:22:42 temperature.c:435:temp_statistics_show:   pcb temp 42~64  chip temp 63~81
2019-06-10 15:52:45 thread.c:164:calc_hashrate_avg: avg rate is 54389.57 in 30 mins
2019-06-10 15:52:45 temperature.c:435:temp_statistics_show:   pcb temp 41~62  chip temp 61~79
2019-06-10 16:22:48 thread.c:164:calc_hashrate_avg: avg rate is 54596.93 in 30 mins
2019-06-10 16:22:48 temperature.c:435:temp_statistics_show:   pcb temp 40~63  chip temp 61~80
2019-06-10 16:52:51 thread.c:164:calc_hashrate_avg: avg rate is 54401.59 in 30 mins
2019-06-10 16:52:51 temperature.c:435:temp_statistics_show:   pcb temp 42~64  chip temp 63~80
2019-06-10 17:01:05 temperature.c:681:get_temp_info: read temp sensor failed: chain = 0, chip = 195, reg = 0
2019-06-10 17:22:54 thread.c:164:calc_hashrate_avg: avg rate is 54118.01 in 30 mins
2019-06-10 17:22:54 temperature.c:435:temp_statistics_show:   pcb temp 41~63  chip temp 62~80
2019-06-10 17:52:57 thread.c:164:calc_hashrate_avg: avg rate is 54625.70 in 30 mins
2019-06-10 17:52:57 temperature.c:435:temp_statistics_show:   pcb temp 41~63  chip temp 62~80
2019-06-10 18:18:08 temperature.c:681:get_temp_info: read temp sensor failed: chain = 0, chip = 180, reg = 1
2019-06-10 18:23:00 thread.c:164:calc_hashrate_avg: avg rate is 54379.19 in 30 mins
2019-06-10 18:23:00 temperature.c:435:temp_statistics_show:   pcb temp 41~63  chip temp 62~80
2019-06-10 18:53:02 thread.c:164:calc_hashrate_avg: avg rate is 54364.03 in 30 mins
2019-06-10 18:53:02 temperature.c:435:temp_statistics_show:   pcb temp 40~63  chip temp 62~80
2019-06-10 19:23:05 thread.c:164:calc_hashrate_avg: avg rate is 54513.18 in 30 mins
2019-06-10 19:23:05 temperature.c:435:temp_statistics_show:   pcb temp 40~63  chip temp 61~80
2019-06-10 19:53:08 thread.c:164:calc_hashrate_avg: avg rate is 54268.84 in 30 mins
2019-06-10 19:53:08 temperature.c:435:temp_statistics_show:   pcb temp 40~63  chip temp 61~80
2019-06-10 20:23:11 thread.c:164:calc_hashrate_avg: avg rate is 54445.25 in 30 mins
2019-06-10 20:23:11 temperature.c:435:temp_statistics_show:   pcb temp 39~63  chip temp 60~80
2019-06-10 20:53:14 thread.c:164:calc_hashrate_avg: avg rate is 54314.69 in 30 mins
2019-06-10 20:53:14 temperature.c:435:temp_statistics_show:   pcb temp 39~62  chip temp 60~80
2019-06-10 21:23:17 thread.c:164:calc_hashrate_avg: avg rate is 54244.91 in 30 mins
2019-06-10 21:23:17 temperature.c:435:temp_statistics_show:   pcb temp 39~63  chip temp 60~81
2019-06-10 21:53:20 thread.c:164:calc_hashrate_avg: avg rate is 54068.25 in 30 mins
2019-06-10 21:53:20 temperature.c:435:temp_statistics_show:   pcb temp 39~63  chip temp 60~80
2019-06-10 22:23:23 thread.c:164:calc_hashrate_avg: avg rate is 54655.74 in 30 mins
2019-06-10 22:23:23 temperature.c:435:temp_statistics_show:   pcb temp 38~63  chip temp 59~80
2019-06-10 22:53:26 thread.c:164:calc_hashrate_avg: avg rate is 54222.52 in 30 mins
2019-06-10 22:53:26 temperature.c:435:temp_statistics_show:   pcb temp 38~63  chip temp 60~80
2019-06-10 23:23:29 thread.c:164:calc_hashrate_avg: avg rate is 54382.25 in 30 mins
2019-06-10 23:23:29 temperature.c:435:temp_statistics_show:   pcb temp 38~62  chip temp 59~80
2019-06-10 23:53:32 thread.c:164:calc_hashrate_avg: avg rate is 54584.01 in 30 mins
2019-06-10 23:53:32 temperature.c:435:temp_statistics_show:   pcb temp 38~63  chip temp 59~81
2019-06-11 00:23:35 thread.c:164:calc_hashrate_avg: avg rate is 54157.59 in 30 mins
2019-06-11 00:23:35 temperature.c:435:temp_statistics_show:   pcb temp 37~63  chip temp 58~80
2019-06-11 00:53:38 thread.c:164:calc_hashrate_avg: avg rate is 54493.51 in 30 mins
2019-06-11 00:53:38 temperature.c:435:temp_statistics_show:   pcb temp 38~63  chip temp 59~80
2019-06-11 01:23:41 thread.c:164:calc_hashrate_avg: avg rate is 54368.66 in 30 mins
2019-06-11 01:23:41 temperature.c:435:temp_statistics_show:   pcb temp 37~63  chip temp 59~80
2019-06-11 01:53:44 thread.c:164:calc_hashrate_avg: avg rate is 54239.12 in 30 mins
2019-06-11 01:53:44 temperature.c:435:temp_statistics_show:   pcb temp 38~63  chip temp 59~80
2019-06-11 02:23:47 thread.c:164:calc_hashrate_avg: avg rate is 54194.69 in 30 mins
2019-06-11 02:23:47 temperature.c:435:temp_statistics_show:   pcb temp 38~63  chip temp 59~81
2019-06-11 02:53:50 thread.c:164:calc_hashrate_avg: avg rate is 54489.68 in 30 mins
2019-06-11 02:53:50 temperature.c:435:temp_statistics_show:   pcb temp 37~63  chip temp 59~80
2019-06-11 03:23:53 thread.c:164:calc_hashrate_avg: avg rate is 54344.21 in 30 mins
2019-06-11 03:23:53 temperature.c:435:temp_statistics_show:   pcb temp 38~62  chip temp 59~79
2019-06-11 03:53:56 thread.c:164:calc_hashrate_avg: avg rate is 54423.75 in 30 mins
2019-06-11 03:53:56 temperature.c:435:temp_statistics_show:   pcb temp 38~62  chip temp 59~80
2019-06-11 04:23:59 thread.c:164:calc_hashrate_avg: avg rate is 54114.58 in 30 mins
2019-06-11 04:23:59 temperature.c:435:temp_statistics_show:   pcb temp 40~63  chip temp 61~81
2019-06-11 04:54:02 thread.c:164:calc_hashrate_avg: avg rate is 54393.21 in 30 mins
2019-06-11 04:54:02 temperature.c:435:temp_statistics_show:   pcb temp 39~63  chip temp 60~80
2019-06-11 05:04:28 temperature.c:681:get_temp_info: read temp sensor failed: chain = 2, chip = 55, reg = 1
2019-06-11 05:07:20 temperature.c:681:get_temp_info: read temp sensor failed: chain = 2, chip = 195, reg = 1
2019-06-11 05:24:05 thread.c:164:calc_hashrate_avg: avg rate is 54264.75 in 30 mins
2019-06-11 05:24:05 temperature.c:435:temp_statistics_show:   pcb temp 40~63  chip temp 61~80
2019-06-11 05:54:08 thread.c:164:calc_hashrate_avg: avg rate is 54213.89 in 30 mins
2019-06-11 05:54:08 temperature.c:435:temp_statistics_show:   pcb temp 41~63  chip temp 62~80
2019-06-11 06:24:11 thread.c:164:calc_hashrate_avg: avg rate is 54607.56 in 30 mins
2019-06-11 06:24:11 temperature.c:435:temp_statistics_show:   pcb temp 39~63  chip temp 60~80
2019-06-11 06:54:14 thread.c:164:calc_hashrate_avg: avg rate is 54133.35 in 30 mins
2019-06-11 06:54:14 temperature.c:435:temp_statistics_show:   pcb temp 40~64  chip temp 62~81
2019-06-11 07:24:17 thread.c:164:calc_hashrate_avg: avg rate is 54012.19 in 30 mins
2019-06-11 07:24:17 temperature.c:435:temp_statistics_show:   pcb temp 39~63  chip temp 60~80
2019-06-11 07:54:20 thread.c:164:calc_hashrate_avg: avg rate is 53972.74 in 30 mins
2019-06-11 07:54:20 temperature.c:435:temp_statistics_show:   pcb temp 39~63  chip temp 60~80
2019-06-11 08:24:23 thread.c:164:calc_hashrate_avg: avg rate is 54635.36 in 30 mins
2019-06-11 08:24:23 temperature.c:435:temp_statistics_show:   pcb temp 40~64  chip temp 61~81
2019-06-11 08:54:26 thread.c:164:calc_hashrate_avg: avg rate is 54265.68 in 30 mins
2019-06-11 08:54:26 temperature.c:435:temp_statistics_show:   pcb temp 40~64  chip temp 61~81
2019-06-11 09:24:29 thread.c:164:calc_hashrate_avg: avg rate is 54418.80 in 30 mins
2019-06-11 09:24:29 temperature.c:435:temp_statistics_show:   pcb temp 40~63  chip temp 61~80
2019-06-11 09:54:32 thread.c:164:calc_hashrate_avg: avg rate is 54361.27 in 30 mins
2019-06-11 09:54:32 temperature.c:435:temp_statistics_show:   pcb temp 41~63  chip temp 62~80
2019-06-11 10:24:35 thread.c:164:calc_hashrate_avg: avg rate is 54238.61 in 30 mins
2019-06-11 10:24:35 temperature.c:435:temp_statistics_show:   pcb temp 41~63  chip temp 62~80

 

Edited by paschok81

Share this post


Link to post
Share on other sites

Добрый вечер, после того как я отключил x плату, 2 остальные работали. спустя некоторое время я продул, почистил и снова подключил третью x плату и асик запустился, всё заработало! Единственное что не могу понять, в minerStatus во вкладке Summary не отоброжает никакой информации. Хотя асик работает, и судя по пулу манит нормально. Кто сталкивался с такой проблемой?

Снимок экрана 2019-06-15 в 20.01.01.png

Edited by urikedr

Share this post


Link to post
Share on other sites
11 минут назад, urikedr сказал:

Добрый вечер, после того как я отключил x плату, 2 остальные работали. спустя некоторое время я продул, почистил и снова подключил третью x плату и асик запустился, всё заработало! Единственное что не могу понять, в minerStatus во вкладке Summary не отоброжает никакой информации. Хотя асик работает, и судя по пулу манит нормально. Кто сталкивался с такой проблемой?

Снимок экрана 2019-06-15 в 20.01.01.png

Попробуй смени браузер. У меня в хроме вкладка POOLS пустая, а в опере все нормально.

Склоняюсь что контакты плохие были, поэтому происходил отвал.

Share this post


Link to post
Share on other sites
1 час назад, paschok81 сказал:

Попробуй смени браузер. У меня в хроме вкладка POOLS пустая, а в опере все нормально.

Склоняюсь что контакты плохие были, поэтому происходил отвал.

У меня 2 акиса, один нормально отображается, а один вот так. Пробовал в разных браузерах, отображается так же. Асик сбрасывал до заводских, перепрошивал. После перезагрузки норм, спустя минут 10 обновляю, снова пропадает. В целом не мешает, просто интересно, из за чего такое может быть.

Share this post


Link to post
Share on other sites
10 часов назад, urikedr сказал:

просто интересно, из за чего такое может быть.

 

 

потому, что со времени s5 ничего не изменилось.

такое же Гавно, этот ваш битмайн.

Share this post


Link to post
Share on other sites

@urikedr 

плату в ремонт....

Share this post


Link to post
Share on other sites
8 часов назад, adv сказал:

@urikedr 

плату в ремонт....

Ещё бы найти кто ремонтирует

Тоже на одном S17 Pro умерла плата

Share this post


Link to post
Share on other sites

@isazon4ik он же на гарантии. Не идеально, но хоть что-то

Share this post


Link to post
Share on other sites

@urikedr 

Под спойлер надо прятать такие простыни.

Share this post


Link to post
Share on other sites

@urikedr 

отвал чипов

плату в ремонт

 

Share this post


Link to post
Share on other sites
10 часов назад, isazon4ik сказал:

Ещё бы найти кто ремонтирует

Тоже на одном S17 Pro умерла плата

 

Рекомендую https://forum.bits.media/index.php?/topic/144866-allроссиямосква-ремонт-асиков-bitmain-antminer-s9-s9i-s9j-t15-s15-s11-t9-l3-d3-ремонт-хеш-плат-асиков-от-1999₽-с-заменой-чипов-сервис-myrig-service/

Share this post


Link to post
Share on other sites
12 часов назад, Dm77 сказал:

Написал им, говорят не чинят семнадцатое поколение пока что

Share this post


Link to post
Share on other sites

Ребят, у вас же гарантия есть. Отправляйте напрямую в Битмайн. Сейчас, например, ремонт С9 проходит в несколько дней. Отправляйте в Иркутск. Ремонт будет бесплатным. Только за отправку заплатить придется.

Кому подсказать, как отправлять, в личку.

Edited by maximF

Share this post


Link to post
Share on other sites
08.06.2019 в 16:00, urikedr сказал:
  Скрыть содержимое

 

Полный лог:

 

Booting Linux on physical CPU 0x0
Linux version 4.6.0-xilinx-gff8137b-dirty ([email protected]) (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 <[email protected]>
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 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: 12/6, WL threshold: 4096, image sequence number: 892827981
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 50879C9C-F33B-4D12-980A-80D93F150810, 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: 90/51, WL threshold: 4096, image sequence number: 37638575
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 0D892CBB-C57D-4CA7-A539-370B84C781E4, 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
2019-06-08 07:54:22 driver-btm-api.c:773:init_freq_mode: This is scan-user version
2019-06-08 07:54:22 driver-btm-api.c:1891:bitmain_soc_init: opt_multi_version     = 1
2019-06-08 07:54:22 driver-btm-api.c:1892:bitmain_soc_init: opt_bitmain_ab        = 1
2019-06-08 07:54:22 driver-btm-api.c:1893:bitmain_soc_init: opt_bitmain_work_mode = 1
2019-06-08 07:54:22 driver-btm-api.c:1894:bitmain_soc_init: Miner compile time: Mon May 27 10:57:13 CST 2019 type: Antminer S17 Pro
2019-06-08 07:54:22 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
2019-06-08 07:54:22 driver-btm-api.c:1778:show_sn: no SN got, please write SN to /nvdata/sn
2019-06-08 07:54:22 driver-btm-api.c:1251:miner_device_init: Detect 256MB control board of XILINX
2019-06-08 07:54:22 driver-btm-api.c:1199:init_fan_parameter: fan_eft : 0  fan_pwm : 0
2019-06-08 07:54:22 thread.c:627:create_read_nonce_reg_thread: create thread
2019-06-08 07:54:28 driver-btm-api.c:1183:init_miner_version: miner ID : 804ce54e57408854
2019-06-08 07:54:28 driver-btm-api.c:1189:init_miner_version: FPGA Version = 0xB011
2019-06-08 07:54:34 driver-btm-api.c:835:get_product_id: product_id[0] = 0
2019-06-08 07:54:34 driver-btm-api.c:835:get_product_id: product_id[1] = 0
2019-06-08 07:54:34 driver-btm-api.c:835:get_product_id: product_id[2] = 0
2019-06-08 07:54:34 driver-btm-api.c:786:_set_project_type: project:0
2019-06-08 07:54:34 driver-btm-api.c:811:_set_project_type: Project type: Antminer S17 Pro
2019-06-08 07:54:34 driver-btm-api.c:822:dump_pcb_bom_version: Chain [0] PCB Version: 0x0101
2019-06-08 07:54:34 driver-btm-api.c:823:dump_pcb_bom_version: Chain [0] BOM Version: 0x0103
2019-06-08 07:54:34 driver-btm-api.c:822:dump_pcb_bom_version: Chain [1] PCB Version: 0x0101
2019-06-08 07:54:34 driver-btm-api.c:823:dump_pcb_bom_version: Chain [1] BOM Version: 0x0103
2019-06-08 07:54:34 driver-btm-api.c:822:dump_pcb_bom_version: Chain [2] PCB Version: 0x0101
2019-06-08 07:54:34 driver-btm-api.c:823:dump_pcb_bom_version: Chain [2] BOM Version: 0x0103
2019-06-08 07:54:34 driver-btm-api.c:1841:bitmain_board_init: Fan check passed.
2019-06-08 07:54:35 board.c:36:jump_and_app_check_restore_pic: chain[0] PIC jump to app
2019-06-08 07:54:39 board.c:40:jump_and_app_check_restore_pic: Check chain[0] PIC fw version=0xb9
2019-06-08 07:54:41 board.c:36:jump_and_app_check_restore_pic: chain[1] PIC jump to app
2019-06-08 07:54:44 board.c:40:jump_and_app_check_restore_pic: Check chain[1] PIC fw version=0xb9
2019-06-08 07:54:46 board.c:36:jump_and_app_check_restore_pic: chain[2] PIC jump to app
2019-06-08 07:54:49 board.c:40:jump_and_app_check_restore_pic: Check chain[2] PIC fw version=0xb9
2019-06-08 07:54:49 thread.c:622:create_pic_heart_beat_thread: create thread
2019-06-08 07:54:49 power_api.c:55:power_init: power init ... 
2019-06-08 07:54:49 driver-btm-api.c:1851:bitmain_board_init: Enter 30s sleep to make sure power release finish.
2019-06-08 07:54:49 power_api.c:46:power_off: init gpio907
2019-06-08 07:55:21 power_api.c:164:set_iic_power_to_highest_voltage: setting to voltage: 21.00 ...
2019-06-08 07:55:27 power_api.c:113:set_iic_power_by_voltage: now setting voltage to : 21.000000 
2019-06-08 07:55:39 driver-btm-api.c:1126:check_asic_number_with_power_on: Chain[0]: find 48 asic, times 0
2019-06-08 07:55:51 driver-btm-api.c:1126:check_asic_number_with_power_on: Chain[1]: find 48 asic, times 0
2019-06-08 07:56:03 driver-btm-api.c:1126:check_asic_number_with_power_on: Chain[2]: find 48 asic, times 0
2019-06-08 07:56:03 driver-btm-api.c:336:set_order_clock: chain[0]: set order clock, stragegy 3
2019-06-08 07:56:03 driver-btm-api.c:336:set_order_clock: chain[1]: set order clock, stragegy 3
2019-06-08 07:56:03 driver-btm-api.c:336:set_order_clock: chain[2]: set order clock, stragegy 3
2019-06-08 07:56:08 driver-hash-chip.c:453:set_clock_delay_control: core_data = 0x34
2019-06-08 07:56:08 voltage[0] = 1780
2019-06-08 07:56:08 voltage[1] = 1780
2019-06-08 07:56:08 voltage[2] = 1780
2019-06-08 07:56:08 power_api.c:76:set_working_voltage: working_voltage = 17.800000
2019-06-08 07:56:09 temperature.c:267:calibrate_temp_sensor_one_chain: Temperature sensor calibration: chain 0 success.
2019-06-08 07:56:11 temperature.c:267:calibrate_temp_sensor_one_chain: Temperature sensor calibration: chain 1 success.
2019-06-08 07:56:12 temperature.c:267:calibrate_temp_sensor_one_chain: Temperature sensor calibration: chain 2 success.
2019-06-08 07:56:12 driver-hash-chip.c:229:dhash_chip_set_baud_v2: chain[0]: chip baud = 6000000, chip_divider = 7
2019-06-08 07:56:12 driver-hash-chip.c:229:dhash_chip_set_baud_v2: chain[1]: chip baud = 6000000, chip_divider = 7
2019-06-08 07:56:12 driver-hash-chip.c:229:dhash_chip_set_baud_v2: chain[2]: chip baud = 6000000, chip_divider = 7
2019-06-08 07:56:12 uart.c:80:set_baud: set fpga_baud = 6000000, fpga_divider = 3
2019-06-08 07:56:14 temperature.c:681:get_temp_info: read temp sensor failed: chain = 0, chip = 40, reg = 1
2019-06-08 07:56:33 temperature.c:681:get_temp_info: read temp sensor failed: chain = 0, chip = 180, reg = 1
2019-06-08 07:56:53 temperature.c:681:get_temp_info: read temp sensor failed: chain = 0, chip = 195, reg = 1
2019-06-08 07:56:54 driver-btm-api.c:236:check_bringup_temp: Bring up temperature is -64
2019-06-08 07:56:54 driver-btm-api.c:194:set_miner_status: ERROR_TEMP_TOO_LOW
2019-06-08 07:56:54 driver-btm-api.c:135:stop_mining: stop mining: Environment temperature is too low!
2019-06-08 07:56:54 thread.c:672:cancel_read_nonce_reg_thread: cancel thread
2019-06-08 07:56:54 driver-btm-api.c:121:killall_hashboard: ****power off hashboard****

 

 

Похоже что-то с датчиком температуры (возможно он встроен в чип??)  ERROR_TEMP_TOO_LOW Environment temperature is too low! Или вы морозите плату до -64С

Share this post


Link to post
Share on other sites
21.07.2019 в 12:58, isazon4ik сказал:

Ещё бы найти кто ремонтирует

Тоже на одном S17 Pro умерла плата

asicfox.com.ua

одна из лучших компаний по ремонту и продаже 

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Topics

    • Bitmain анонсировали новые модели майнеров Antminer S17+ и Antminer T17+

      Вчера на мероприятии World Digital Mining Summit сооснователь Bitmain Цзихань У анонсировал новые модели ASIC-майнеров серии S17 с увеличенным количеством чипов - Antminer S17+ и Antminer T17+.   «Новые майнеры стали более производительными и энергоэффективными. Хэшрейт Antminer S17+ равен 73 Тх/с, а показатель энергоэффективности равен 40 Дж/Тх плюс-минус 10%. У Antminer T17+ хэшрейт равен 64 Тх/с, а энергоэффективность 50 Дж/Тх + 10%», - написано в блоге компании Bitmain.

      in Новости криптовалют

    • Постоянная перезагрузка S17.

      Вообщем ситуация такая.    Майнеры ( все S17) стоят в отеле и на некоторых из них постоянно происходит перезагрузка, а потом ни с того ни с сего все начинает работать нормально 3-7 дней, потом опять начинается такие зигзаги, либо перезагружается каждые 1-3 часа. Ошибок никаких не пишет. Кто-нибубь сталкивался с таким и в чем может быть причина?     

      in ASIC/FPGA майнеры

    • Проблема с Control board на antminer s9

      Контрольная плата на майнере не дает питание или не видит хэш платы, так же не возможно подключится к майнеру по сети. На кнопки перезагрузки и ip reporter плата не реагирует, хотя внтиляторы крутятся и все диоды на плате горят. Отзовитесь у ого возникла такая проблема, решили или нет?

      in ASIC/FPGA майнеры

    • Проблема трекинга Antminer'ов в стойке

      Приветствую, господа! Вопрос связан больше с железками, чем с майнингом непосредственно. Излагаю суть: есть 2 стойки с майнерами Antminer S9 в количестве 45 штук каждая, 2 неуправляемых (в потенциале задумываюсь над покупкой управляемых для создания vlan, но об этом чуть позже) свича Dlink на 48 портов и роутер Mikrotic. Проблема заключается в их обслуживании, а именно в определении какой майнер использует какой ip. То есть при определении поломки майнера, в идеале, сразу же (путём маркировки ме

      in ASIC/FPGA майнеры

    • IOTA Проблема с кошельком

      Камрады, подскажите что делать. В 2017 регистрировал кошелек через iota light и тогда секретный ключ состоял из 62 символов. На данный момент софт не работает и я скачал Trinity. При попытке зайти в кошелек пишет - ключ должен быть длинной в 81 символ 😐

      in Кошельки для криптовалют

×
×
  • Create New...