Title: S19 Stop running randomly Post by: Snowballx on January 21, 2021, 11:36:56 PM hello, I started a mining farm (small one) 4 S19Pros there was 2 of them working good and the other too shows a disconnected still didn't get the reason why?
can anyone help me. Miner log 1 Code: ===========================================Miner log=========================================== Miner log 2 Code: ===========================================Miner log=========================================== the others are keep disconnected. Title: Re: S19 Stop running randomly Post by: philipma1957 on January 22, 2021, 01:42:10 AM it says they are too hot.
so is the room hot. are the fans set to at least 90% my board temps are much lower than yours. 46 41 67 67 46 39 69 66 47 42 70 68 it says you are over 95 Title: Re: S19 Stop running randomly Post by: mikeywith on January 22, 2021, 03:18:02 AM Dude, you are you going to fry these expensive gears, each of these gears costs above $7000 to buy today, and you are torturing them. >:(
Code: 2021-01-20 18:16:36 over max temp, pcb temp 81 (max 80), chip temp 96(max 95) pcb temp rise 0 chip temp rise 0, total_exit_failure 0 Both miners show PCB temps of 81 where the maximum temp of S19 is just 80, and one or more chips are at 96 degrees Cellius, they shouldn't be close to the max by any means, when the max temp is 95c you should start to worry when the approach 85c, you need better cooling, it seems like you are not exhausting enough hot air and it's going back to the miners, for starters, try 100% fan speed and see how it goes. Title: Re: S19 Stop running randomly Post by: Snowballx on January 22, 2021, 11:13:15 PM Thank you guys I replaced the AC in the room and yes the room was so hot without exhaust and weather where I live is such a hot as hell.
Title: Re: S19 Stop running randomly Post by: mikeywith on January 23, 2021, 04:07:56 AM Thank you guys I replaced the AC in the room and yes the room was so hot without exhaust and weather where I live is such a hot as hell. I used to think that I need an AC to cool the miners down where I live, temps go over 40c in the summer, but I came to understand that sufficient airflow is more than enough, you could add an AC (if you don't care about the power bill) but without exhausting the hot air fast enough, you will always run into over temp issues. Title: Re: S19 Stop running randomly Post by: Snowballx on January 23, 2021, 05:24:49 PM am living in Middle East so some how in summer I'll face over 50 degree for sure what am planning to do adding 2 AC's 2.5 ton or 3 ton one would be facing the machines and the other one would be in the back the room is small for the small farm I have it's only 4 S19PRO for now might jump to 8 as maximum later the room size is 4x4msq so cooling it won't be an issue the problems am thinking to face is what if it really need to be exhausting the heat even with the two Ac's running 24/7.
Title: Re: S19 Stop running randomly Post by: philipma1957 on January 23, 2021, 05:37:54 PM lets say you do not exhaust heat.
each s19 unit is 3300 watts which is about 13200 btu. so 4 pieces are 52800 btu. a 1 ton ac is 12000 so if you commingle the ac with the hot air from the miners. two 2.5 ton ac units can cool 4 s19pros. as they would have 5 x 12000= 60000 cool btu vs the 52800 hot btu. you have to vent the hot air. think about the summer heat of 50c or 120f. only 7200 btu is left from the two 2.5 ton ac units. Title: Re: S19 Stop running randomly Post by: Snowballx on January 23, 2021, 06:57:12 PM himmm the truth sometimes are a dream breaker what should I do with this small room can you help me more how can I exhaust the heat out of this room cause am not planning to stop the mining.
not sure if I'll have big exhaust fans here and will keep the room clean with our dusty summer. "the summer months are June, July, August and part of September. These months are mostly dry, HOT and dusty! Temperatures exceeding 48c, dust lasting for over a week, all in summer." NOTE: I like how you miss that click from btu to btc. appreciate your times guys. regards. Title: Re: S19 Stop running randomly Post by: philipma1957 on January 23, 2021, 07:06:36 PM Okay 1 s19 unit expels about 500cfm.
so I think this will do 2 units and put a fan on the end. https://www.homedepot.com/p/Master-Flow-12-in-x-25-ft-Insulated-Flexible-Duct-R8-Silver-Jacket-F8IFD12X300/202562743 https://www.ebay.com/itm/12-Inch-Inline-Duct-Fan-Vent-Exhaust-Air-Cooled-Hydroponic-Fan-Blower-1200CFM/121181455603? So 2 tube and 2 fans could pull as much as 2400 cfm out of the room. Ac >>>>> miners >>>>> tubes >>>>fans>>> outside Title: Re: S19 Stop running randomly Post by: Snowballx on January 23, 2021, 07:35:03 PM order placed thank you so much sir for your time.
Title: Re: S19 Stop running randomly Post by: mikeywith on January 24, 2021, 12:24:25 AM how can I exhaust the heat out of this room cause am not planning to stop the mining. You can do a split-room setup, check my mini mining farm (https://bitcointalk.org/index.php?topic=5087770.0), I initially had an AC there but it was removed later own and I added more fans both on the intake and the exhaust, this design helps you control dust and noise by trapping all the hot air in one place, make sure you don't have pressure imbalances. Title: Re: S19 Stop running randomly Post by: Snowballx on January 24, 2021, 01:26:05 PM that post you just share is full of good information I just saved them and will start pressing the new mining room cause my miners now in my friend house and am planning to move them to mine in the middle of April and this post would help me a lot building a better mining area.
Appreciate your support guys. can't thank you enough. Title: Re: S19 Stop running randomly Post by: kalafe2006 on September 28, 2021, 01:54:14 PM dear friends
i have an S19pro , it's work one minute then will power off. anybody know whats the proble it's my kernel log 2021-09-28 13:49:27 STATUS_OKAY 2021-09-28 13:49:27 start the cached job 2021-09-28 13:49:27 Version num 8 2021-09-28 13:49:27 Mask num 0xe000 2021-09-28 13:49:27 freq = 525, percent = 90, hcn = 12480, timeout = 449 2021-09-28 13:49:27 set_start_time_point total_tv_start_sys=111 total_tv_end_sys=112 2021-09-28 13:49:27 set_voltage_by_steps to 1335. 2021-09-28 13:49:43 over max temp, pcb temp 0 (max 80), chip temp 15(max 95) pcb temp rise 0 chip temp rise 0, total_exit_failure 0 2021-09-28 13:49:43 ERROR_TEMP_TOO_HIGH: over max temp 2021-09-28 13:49:43 stop_mining: over max temp 2021-09-28 13:49:43 uninit_temp_info 2021-09-28 13:49:43 do not read temp anymore... 2021-09-28 13:49:43 cancel thread 2021-09-28 13:49:43 cancel thread 2021-09-28 13:49:43 cancel thread 2021-09-28 13:49:43 ****power off hashboard**** 2021-09-28 13:49:45 temp monitor thread exit Title: Re: S19 Stop running randomly Post by: rust-project on September 29, 2021, 11:24:50 AM 2021-09-28 13:49:43 over max temp, pcb temp 0 (max 80), chip temp 15(max 95) pcb temp rise 0 chip temp rise 0, total_exit_failure 0
2021-09-28 13:49:43 stop_mining: over max temp 2021-09-28 13:49:43 uninit_temp_info 2021-09-28 13:49:43 do not read temp anymore... 2021-09-28 13:49:43 cancel thread 2021-09-28 13:49:43 cancel thread 2021-09-28 13:49:43 cancel thread 2021-09-28 13:49:43 ****power off hashboard**** 2021-09-28 13:49:45 temp monitor thread exit too hot. Title: Re: S19 Stop running randomly Post by: kalafe2006 on September 29, 2021, 02:52:11 PM It's work under 2 cooler
Title: Re: S19 Stop running randomly Post by: BitMaxz on September 29, 2021, 06:02:58 PM i have an S19pro , it's work one minute then will power off. anybody know whats the proble Can you post the whole kernel logs let me analyze them for you? If you have a limit then you can try to paste it here https://pastebin.com/ and then paste the URL here. What is your room temperature? If the error on this "stop_mining: over max temp" try to manually set the fan speed to 100 you can find it under miner's settings and set it to normal mode. If it doesn't solve your issue try to upgrade it first with the latest version available on Bitmain and test it again. Title: Re: S19 Stop running randomly Post by: kalafe2006 on September 30, 2021, 12:06:13 PM Thank you my friend
My room temperature in under 30 centigrade I update it several times Try to set fans on 100 percent and will send you complete kernel log Title: Re: S19 Stop running randomly Post by: kalafe2006 on October 03, 2021, 06:47:19 AM I set fans on 100%, but didn't work more than 1 minute.
It's my kernel ANTMINER Antminer S19 Pro Algorithm SHA256dOnlineLocate miner Refresh Timer 2021-10-03 10:15:16 English Current logHistory log On node 0 totalpages: 61440 free_area_init_node: node 0, pgdat c0b3c040, 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 @cddf0000 s19916 r8192 d21044 u49152 pcpu-alloc: s19916 r8192 d21044 u49152 alloc=12*4096 pcpu-alloc:
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: 209672K/245760K available (6317K kernel code, 243K rwdata, 1932K rodata, 1024K init, 232K bss, 19704K 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 - 0xc090e410 (9242 kB) .init : 0xc0a00000 - 0xc0b00000 (1024 kB) .data : 0xc0b00000 - 0xc0b3cda0 ( 244 kB) .bss : 0xc0b3cda0 - 0xc0b77024 ( 233 kB) Preemptible hierarchical RCU implementation. Build-time adjustment of leaf fanout to 32. RCU restricting CPUs from NR_CPUS=4 to nr_cpu_ids=2. RCU: Adjusting geometry for rcu_fanout_leaf=32, nr_cpu_ids=2 NR_IRQS:16 nr_irqs:16 16 efuse mapped to cf800000 ps7-slcr mapped to cf802000 L2C: platform modifies aux control register: 0x72360000 -> 0x72760000 L2C: DT/platform modifies aux control register: 0x72360000 -> 0x72760000 L2C-310 erratum 769419 enabled L2C-310 enabling early BRESP for Cortex-A9 L2C-310 full line of zeros enabled for Cortex-A9 L2C-310 ID prefetch enabled, offset 1 lines L2C-310 dynamic clock gating enabled, standby mode enabled L2C-310 cache controller enabled, 8 ways, 512 kB L2C-310: CACHE_ID 0x410000c8, AUX_CTRL 0x76760001 zynq_clock_init: clkc starts at cf802100 Zynq clock init sched_clock: 64 bits at 333MHz, resolution 3ns, wraps every 4398046511103ns clocksource: arm_global_timer: mask: 0xffffffffffffffff max_cycles: 0x4ce07af025, max_idle_ns: 440795209040 ns Switching to timer-based delay loop, resolution 3ns clocksource: ttc_clocksource: mask: 0xffff max_cycles: 0xffff, max_idle_ns: 537538477 ns ps7-ttc #0 at cf80a000, irq=18 Console: colour dummy device 80x30 Calibrating delay loop (skipped), value calculated using timer frequency.. 666.66 BogoMIPS (lpj=3333333) pid_max: default: 32768 minimum: 301 Mount-cache hash table entries: 1024 (order: 0, 4096 bytes) Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes) CPU: Testing write buffer coherency: ok CPU0: thread -1, cpu 0, socket 0, mpidr 80000000 Setting up static identity map for 0x100000 - 0x100058 CPU1: failed to boot: -1 Brought up 1 CPUs SMP: Total of 1 processors activated (666.66 BogoMIPS). CPU: All CPU(s) started in SVC mode. devtmpfs: initialized VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4 clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns pinctrl core: initialized pinctrl subsystem NET: Registered protocol family 16 DMA: preallocated 256 KiB pool for atomic coherent allocations cpuidle: using governor menu hw-breakpoint: found 5 (+1 reserved) breakpoint and 1 watchpoint registers. hw-breakpoint: maximum watchpoint size is 4 bytes. zynq-ocm f800c000.ps7-ocmc: ZYNQ OCM pool: 256 KiB @ 0xcf880000 vgaarb: loaded SCSI subsystem initialized usbcore: registered new interface driver usbfs usbcore: registered new interface driver hub usbcore: registered new device driver usb media: Linux media interface: v0.10 Linux video capture interface: v2.00 pps_core: LinuxPPS API ver. 1 registered pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it> PTP clock support registered EDAC MC: Ver: 3.0.0 Advanced Linux Sound Architecture Driver Initialized. clocksource: Switched to clocksource arm_global_timer NET: Registered protocol family 2 TCP established hash table entries: 2048 (order: 1, 8192 bytes) TCP bind hash table entries: 2048 (order: 2, 16384 bytes) TCP: Hash tables configured (established 2048 bind 2048) UDP hash table entries: 256 (order: 1, 8192 bytes) UDP-Lite hash table entries: 256 (order: 1, 8192 bytes) NET: Registered protocol family 1 RPC: Registered named UNIX socket transport module. RPC: Registered udp transport module. RPC: Registered tcp transport module. RPC: Registered tcp NFSv4.1 backchannel transport module. PCI: CLS 0 bytes, default 64 Trying to unpack rootfs image as initramfs... rootfs image is not initramfs (no cpio magic); looks like an initrd Freeing initrd memory: 6632K (cd480000 - cdafa000) 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 = 159, 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 cdns-i2c e0005000.ps7_i2c: 100 kHz mmio e0005000 irq 154 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: disable subpage write 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: NAND_ECC_HW nand: NAND_ECC_HW_SYNDROME mtd->writesize = 2048 ecc->strength = 1 ecc->size = 2048 mtd->writesize = 2048 chip->ecc_strength_ds = 4 chip->ecc_step_ds = 512 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 8 ofpart partitions found on MTD device pl35x-nand Creating 8 MTD partitions on "pl35x-nand": 0x000000000000-0x000002800000 : "BOOT.bin-dts-marker-kernel" 0x000002800000-0x000004800000 : "ramfs" 0x000004800000-0x000005000000 : "configs" 0x000005000000-0x000005200000 : "sig" 0x000005200000-0x000006000000 : "reserve1" 0x000006000000-0x000007000000 : "upgrade-ramfs" 0x000007000000-0x00000a800000 : "upgrade-file" 0x00000a800000-0x000010000000 : "reserve2" nf_conntrack version 0.5.0 (3635 buckets, 14540 max) ip_tables: (C) 2000-2006 Netfilter Core Team NET: Registered protocol family 10 ip6_tables: (C) 2000-2006 Netfilter Core Team 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 warning (device ram0): ext4_update_dynamic_rev:746: updating to rev 1 because of new feature flag, running e2fsck is recommended 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,errors=remount-ro devpts: called with bogus options 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: 36/15, WL threshold: 4096, image sequence number: 2611976551 ubi0: available PEBs: 0, total reserved PEBs: 64, PEBs reserved for bad PEB handling: 4 ubi0: background thread "ubi_bgt0d" started, PID 729 UBIFS (ubi0:0): background thread "ubifs_bgt0_0" started, PID 733 UBIFS (ubi0:0): recovery needed UBIFS (ubi0:0): recovery completed UBIFS (ubi0:0): UBIFS: mounted UBI device 0, volume 0, name "config_data" UBIFS (ubi0:0): LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes UBIFS (ubi0:0): FS size: 5840896 bytes (5 MiB, 46 LEBs), journal size 1015809 bytes (0 MiB, 6 LEBs) UBIFS (ubi0:0): reserved for root: 275879 bytes (269 KiB) UBIFS (ubi0:0): media format: w4/r0 (latest is w4/r0), UUID 4ABCA522-4FEC-4B0B-88CC-0B5AE24EB0C6, small LPT model ubi2: attaching mtd4 ubi2: scanning is finished ubi2: attached mtd4 (name "reserve1", size 14 MiB) ubi2: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes ubi2: min./max. I/O unit sizes: 2048/2048, sub-page size 2048 ubi2: VID header offset: 2048 (aligned 2048), data offset: 4096 ubi2: good PEBs: 112, bad PEBs: 0, corrupted PEBs: 0 ubi2: user volume: 1, internal volumes: 1, max. volumes count: 128 ubi2: max/mean erase counter: 2/1, WL threshold: 4096, image sequence number: 18977471 ubi2: available PEBs: 0, total reserved PEBs: 112, PEBs reserved for bad PEB handling: 4 ubi2: background thread "ubi_bgt2d" started, PID 740 UBIFS (ubi2:0): background thread "ubifs_bgt2_0" started, PID 744 UBIFS (ubi2:0): recovery needed UBIFS (ubi2:0): recovery completed UBIFS (ubi2:0): UBIFS: mounted UBI device 2, volume 0, name "misc" UBIFS (ubi2:0): LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes UBIFS (ubi2:0): FS size: 11935744 bytes (11 MiB, 94 LEBs), journal size 1015809 bytes (0 MiB, 6 LEBs) UBIFS (ubi2:0): reserved for root: 563754 bytes (550 KiB) UBIFS (ubi2:0): media format: w4/r0 (latest is w4/r0), UUID 6426876F-F1B8-4189-B081-1CCD07ADB9DE, small LPT model IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready random: avahi-daemon urandom read with 2 bits of entropy available 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 0xcfbc8000 *base_vir_addr = 0xb031 In fpga mem driver! request_mem_region OK! fpga mem virtual address is 0xd2000000 ===========================================Miner log=========================================== 1970-01-01 00:00:09 Miner compile time: Fri Dec 11 11:23:44 CST 2020 type: Antminer S19 Pro 1970-01-01 00:00:10 This is fix-freq version 1970-01-01 00:00:10 Miner compile time: Fri Dec 11 11:23:44 CST 2020 type: Antminer S19 Pro 1970-01-01 00:00:10 commit version: 1821c90 2020-11-16 16:05:37, build by: jenkins 2020-12-11 11:35:43 1970-01-01 00:00:10 opt_multi_version = 1 1970-01-01 00:00:10 opt_bitmain_ab = 1 1970-01-01 00:00:10 mid_auto_gen = 0 1970-01-01 00:00:10 opt_bitmain_work_mode = 0 1970-01-01 00:00:10 mmap fpga_mem_addr_hal = 0xb5800000 1970-01-01 00:00:10 HASH_ON_PLUG V9 = 0x5 1970-01-01 00:00:10 Note: front fan is power on! 1970-01-01 00:00:10 Note: rear fan is power on! 1970-01-01 00:00:10 start the http log. 1970-01-01 00:00:10 httpListenThread start ret=0 1970-01-01 00:00:10 start listen on 6060 ... 1970-01-01 00:00:10 load machine NBP1901 conf 1970-01-01 00:00:10 machine : NBP1901 1970-01-01 00:00:10 chain_num 4, chain_domain_num 38, chain_asic_num 114, domain_asic_num 3 2021-10-03 06:42:30 miner ID : 8144a4205710481c 2021-10-03 06:42:30 FPGA Version = 0xB031 2021-10-03 06:42:30 HASH_ON_PLUG V9 = 0x5 2021-10-03 06:42:30 ==========================capability start========================== 2021-10-03 06:42:30 board num = 2 2021-10-03 06:42:30 board id = 0, chain num = 1 2021-10-03 06:42:30 chain id = 0 2021-10-03 06:42:30 board id = 2, chain num = 1 2021-10-03 06:42:30 chain id = 2 2021-10-03 06:42:30 ==========================capability end============================ 2021-10-03 06:42:30 chain num = 2 2021-10-03 06:42:32 [chain 0] 2021-10-03 06:42:32 0x0000 11 42 00 DF 7C D0 71 4F A6 CC 2F 6D 26 E3 B2 95 2021-10-03 06:42:32 0x0010 2B 1B F7 C4 13 32 5E EA 73 84 CC DF CA 00 73 6A 2021-10-03 06:42:32 0x0020 B8 06 E0 C2 C0 4E 1F E7 8C AD C0 37 1F 31 12 8A 2021-10-03 06:42:32 0x0030 EE D2 E3 11 14 C1 F0 5E 50 F6 2A 8E 29 72 7D 4C 2021-10-03 06:42:32 0x0040 1A 33 FF FF FF FF FF FF FF FF FF FF FF FF FF FF 2021-10-03 06:42:32 0x0050 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF 2021-10-03 06:42:32 0x0060 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF 2021-10-03 06:42:32 0x0070 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF 2021-10-03 06:42:32 0x0080 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF 2021-10-03 06:42:32 0x0090 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF 2021-10-03 06:42:32 0x00A0 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF 2021-10-03 06:42:32 0x00B0 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF 2021-10-03 06:42:32 0x00C0 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF 2021-10-03 06:42:32 0x00D0 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF 2021-10-03 06:42:32 0x00E0 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF 2021-10-03 06:42:32 0x00F0 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF 5A 2021-10-03 06:42:32 2021-10-03 06:42:34 [chain 2] 2021-10-03 06:42:34 0x0000 11 42 00 DF 7C D0 71 4F A6 CC 2F 6D 26 E3 B2 95 2021-10-03 06:42:34 0x0010 2B 1B F7 C4 13 32 5E EA 73 84 CC DF CA 00 73 6A 2021-10-03 06:42:34 0x0020 B8 06 E0 C2 C0 4E 1F E7 8C AD C0 37 1F 31 12 8A 2021-10-03 06:42:34 0x0030 EE D2 E3 11 14 C1 F0 5E 50 F6 2A 8E 29 72 7D 4C 2021-10-03 06:42:34 0x0040 1A 33 FF FF FF FF FF FF FF FF FF FF FF FF FF FF 2021-10-03 06:42:34 0x0050 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF 2021-10-03 06:42:34 0x0060 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF 2021-10-03 06:42:34 0x0070 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF 2021-10-03 06:42:34 0x0080 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF 2021-10-03 06:42:34 0x0090 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF 2021-10-03 06:42:34 0x00A0 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF 2021-10-03 06:42:34 0x00B0 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF 2021-10-03 06:42:34 0x00C0 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF 2021-10-03 06:42:34 0x00D0 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF 2021-10-03 06:42:34 0x00E0 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF 2021-10-03 06:42:34 0x00F0 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF 5A 2021-10-03 06:42:34 2021-10-03 06:42:34 fan_eft : 1 fan_pwm : 100 2021-10-03 06:42:34 create thread 2021-10-03 06:42:34 fixed working voltage = 1260 2021-10-03 06:42:34 Chain
2021-10-03 06:42:34 Chain [2] BOM Version: 0x0100 2021-10-03 06:42:40 Fan check passed. 2021-10-03 06:42:41 chain[0] PIC jump to app 2021-10-03 06:42:42 Check chain[0] PIC fw version=0x89 2021-10-03 06:42:43 chain[2] PIC jump to app 2021-10-03 06:42:45 Check chain[2] PIC fw version=0x89 2021-10-03 06:42:45 create thread 2021-10-03 06:42:45 max sensor num = 4 2021-10-03 06:42:45 temperature_monitor_thread start... 2021-10-03 06:42:49 power type version: 0x0071 2021-10-03 06:42:49 Enter sleep to make sure power release finish. 2021-10-03 06:43:20 Slept 30 seconds, diff = 0. 2021-10-03 06:43:20 set_voltage_by_steps to 1500. 2021-10-03 06:43:26 start up min temp by 75a = 0 2021-10-03 06:43:26 set UART baud to 115200 2021-10-03 06:43:27 chain avg vol rise to 15.23 2021-10-03 06:43:34 Chain[0]: find 114 asic, times 0 2021-10-03 06:43:42 Chain[2]: find 114 asic, times 0 2021-10-03 06:43:42 pulse_mode = 1, ccdly_sel = 1, pwth_sel = 1 2021-10-03 06:43:45 min freq in eeprom = 525 2021-10-03 06:43:45 fixed frequency is 525 2021-10-03 06:43:45 Bring up temperature is 0 2021-10-03 06:43:45 set UART baud to 12000000 2021-10-03 06:43:45 set_voltage_by_steps to 1310. 2021-10-03 06:43:53 STATUS_INITED: soc init done! 2021-10-03 06:43:53 create thread 2021-10-03 06:43:53 create thread 2021-10-03 06:43:53 fan_etf: Set fixed fan speed=100 2021-10-03 06:43:55 start to init... 2021-10-03 06:44:04 Init done! 2021-10-03 06:44:04 STATUS_OKAY 2021-10-03 06:44:04 start the cached job 2021-10-03 06:44:04 Version num 8 2021-10-03 06:44:04 Mask num 0xe000 2021-10-03 06:44:04 freq = 525, percent = 90, hcn = 12480, timeout = 449 2021-10-03 06:44:04 set_start_time_point total_tv_start_sys=111 total_tv_end_sys=112 2021-10-03 06:44:04 set_voltage_by_steps to 1335. 2021-10-03 06:44:19 over max temp, pcb temp 0 (max 80), chip temp 15(max 95) pcb temp rise 0 chip temp rise 0, total_exit_failure 0 2021-10-03 06:44:19 ERROR_TEMP_TOO_HIGH: over max temp 2021-10-03 06:44:19 stop_mining: over max temp 2021-10-03 06:44:19 uninit_temp_info 2021-10-03 06:44:19 do not read temp anymore... 2021-10-03 06:44:19 cancel thread 2021-10-03 06:44:19 cancel thread 2021-10-03 06:44:19 cancel thread 2021-10-03 06:44:19 ****power off hashboard**** 2021-10-03 06:44:21 temp monitor thread exit Title: Re: S19 Stop running randomly Post by: Artemis3 on October 03, 2021, 07:39:42 PM I wonder what is the problem with people not reading.
See, it says so in caps, exactly the same as op: ERROR_TEMP_TOO_HIGH: over max temp Why do you need others to tell you what your miner is telling you and previous posters even talked at length about? The S19 needs 500CFM. Else check if your fans are all working correctly. Its not "just fans", you can't just put the miner in a closed room. When we say 500CFM, that means air coming FROM OUTSIDE to the miner and then again TO OUTSIDE, A/C is irrelevant, move that air!. Title: Re: S19 Stop running randomly Post by: kalafe2006 on October 04, 2021, 06:50:45 AM All fans work correctly in 500cfm
Room is not closed Air come in and out in best positions Other S19PRO work in this room correctly,just this one has problem Title: Re: S19 Stop running randomly Post by: danieleither on October 04, 2021, 05:32:36 PM I wonder what is the problem with people not reading. See, it says so in caps, exactly the same as op: ERROR_TEMP_TOO_HIGH: over max temp Why do you need others to tell you what your miner is telling you and previous posters even talked at length about? The S19 needs 500CFM. Else check if your fans are all working correctly. Its not "just fans", you can't just put the miner in a closed room. When we say 500CFM, that means air coming FROM OUTSIDE to the miner and then again TO OUTSIDE, A/C is irrelevant, move that air!. That seems harsh - since immediately before this error message, the kernel log indicates that the measured temperatures are actually below the max thresholds and therefore the 'over max temp' message makes no sense. So perhaps this issues is a little more complex than simply 'too hot'? Since the measured PCB temp is reported as '0' - perhaps it's a sensor issue? Title: Re: S19 Stop running randomly Post by: Artemis3 on October 05, 2021, 04:37:34 PM If the board sensors are bad, well... depends what the firmware does with it.
Quote 2021-10-03 06:44:19 over max temp, pcb temp 0 (max 80), chip temp 15(max 95) pcb temp rise 0 chip temp rise 0, total_exit_failure 0 2021-10-03 06:44:19 ERROR_TEMP_TOO_HIGH: over max temp So chip temp 15 is a reason to declare TEMP_TOO_HIGH? Title: Re: S19 Stop running randomly Post by: mikeywith on October 05, 2021, 09:02:59 PM All fans work correctly in 500cfm Room is not closed Air come in and out in best positions Other S19PRO work in this room correctly,just this one has problem The kernel log clearly states "heat problems" which are usually associated with high room temps, inadequate moving of air, slow fans, dirty heatsinks, and all that basic and common sense things, but sometimes there is more to it than meets the eye. Can you shake the miner to check if there is anything loose inside? I had an issue with one of my S17 pros, the fans were good, cooling was fine but the miner would show temp error just a minute or two after it starts, it suspected it was a loose heatsink which was the case. Title: Re: S19 Stop running randomly Post by: kalafe2006 on October 12, 2021, 04:13:12 PM Thank you friends
I opened it, all heat sinks are safe , I thought may be silicon's may be removed, I pulished every chips with Z9 silicon, but the problem isn't remove Title: Re: S19 Stop running randomly Post by: BitMaxz on October 12, 2021, 11:12:07 PM Just noticed your kernel logs shows that the miner is running only with two hashboard
Code: 2021-10-03 06:43:34 Chain[0]: find 114 asic, times 0 It seems one of your hashboard is giving you a false signal that leads to this "ERROR_TEMP_TOO_HIGH: over max temp" What I think is to test the miner with one hashboard but I don't know if it's capable to test it one by one. Thank you friends I opened it, all heat sinks are safe , I thought may be silicon's may be removed, I pulished every chips with Z9 silicon, but the problem isn't remove Do you have the same unit s19pro? Try to use the control board from a known working one and let see if the issue is only from hashboards. If the logs still show the same error after you replace the control board then the issue is in one of your hashboard. You must find that hashboard to remove this error so try to run it one by one to find which hashboard giving you this error. Title: Re: S19 Stop running randomly Post by: kalafe2006 on October 17, 2021, 09:26:07 AM My friends, you right , but I tested with 1 hashboard , 2 hashboards and 3 hashboards, all of them have this error
Changed control board with another one, changed pau with another one, changes all fans, but this error is still and Miner can't work more than 1 minute Title: Re: S19 Stop running randomly Post by: kalafe2006 on November 14, 2021, 10:59:30 AM dear friends
I have with this problem with 3 others S19pro after changed PIC this problem showed Title: Re: S19 Stop running randomly Post by: smopsus on December 12, 2021, 06:00:14 AM Boss, I'm in the same situation with 2 x S19a brand new units and extreme noob here 🙋♂️, do you have any good info on PIC? Are you referring the firmware?
Any info is greatly appreciated! Title: Re: S19 Stop running randomly Post by: mikeywith on December 12, 2021, 10:55:50 PM At this point I tend to believe this has to be a problem with the temp sensor on the hash board, however, given we had a similar issue with the 17 series miners whereby the temp sensor issues were 99% of the time caused by a single bad chip, this could also be the problem with the 19 series.
To be sure I would try a different firmware just to make sure the problem isn't software-related. Title: Re: S19 Stop running randomly Post by: djc200 on January 23, 2022, 12:30:51 AM I'm also in the same boat here with an S19a Pro. Can anyone help me? Here's the current log:
Code: Normal zone: 0 pages reserved Boss, I'm in the same situation with 2 x S19a brand new units and extreme noob here 🙋♂️, do you have any good info on PIC? Are you referring the firmware? Any info is greatly appreciated! |