Bitcoin Forum
April 25, 2024, 12:27:01 AM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
  Home Help Search Login Register More  
  Show Posts
Pages: [1] 2 »
1  Bitcoin / Mining support / Re: Any ideas why my S17 53th keeps showing 127 degrees and 0.00 hash? on: September 10, 2021, 02:24:43 PM
Not sure if I understood correctly but if you're seeing 127-127-127-127 temp readouts that's almost certainly a PSU issue. Try swapping PSU's with another miner that you know works fine to eliminate or confirm. I've had 127-127-127-127 errors on 4 different 17-series miners and replacing the PSU fixed every one.

so far installing the recovery via SD and then flashing the most recent firmware seems to have made it run well again.
2  Bitcoin / Mining support / Re: Any ideas why my S17 53th keeps showing 127 degrees and 0.00 hash? on: September 08, 2021, 06:30:04 PM
Ok so I did the SD card recovery, had some issues, but finally got that to work. Then I saw in the dashboard it was back to the 2019 firmware, so I flashed the newest firmware and rebooted the rig.

Seems to be running great now! No 127 degrees, so far it's 30 minutes with 40-60 degrees on all chips like before, and it seems to be ok, this is the longest it ran before crapping out on me.

So hopefully this works out, and I appreciate your help, I learned some new stuff!
3  Bitcoin / Mining support / Re: Any ideas why my S17 53th keeps showing 127 degrees and 0.00 hash? on: September 08, 2021, 02:37:16 PM
I'm running it directly to a PDU on a 30 amp breaker like I always do on my 100amp service.

This is irrelevant to the question, it doesn't matter how you connect it, the AC voltage is what matters, these PSUs need a consistent voltage rate of 220-240v, they might survive a 200V but nothing below that, also above 240v is going to cause issues, you need to measure the input VOLTAGE and not the amps, the problem could be caused by something else, but everything as of now points to a power related issue, it's either a bad PSU or bad voltage.

My electrician just told me I have 240V
4  Bitcoin / Mining support / Re: Any ideas why my S17 53th keeps showing 127 degrees and 0.00 hash? on: September 07, 2021, 07:00:02 PM
Where do you find the recovery firmware for the SD card?

You can find it on the Bitmain download page check this link below

- https://service.bitmain.com/support/download?product=Flashing%20SD%20card%20with%20image

But I don't if it could fix this issue but it is worth trying.

Have you already tried to run your miner with only one hashboard? If not yet then test them one by one.

Good call, I'll try running them one hashboard at a time.

I did order a replacement PSU to see if that's the issue. Would be weird since the PSU is basically new.
5  Bitcoin / Mining support / Re: Any ideas why my S17 53th keeps showing 127 degrees and 0.00 hash? on: September 07, 2021, 04:16:52 PM
it ran for 7 minutes fine before showing 127 degrees across all chips  Cry
6  Bitcoin / Mining support / Re: Any ideas why my S17 53th keeps showing 127 degrees and 0.00 hash? on: September 07, 2021, 04:08:26 PM
After the reinstall I hadn't rebooted it and it wasn't running, so I rebooted it, now the temps look normal and the kernel log says this. I guess I'll see how long it runs for...

2021-09-07 16:04:14 power_api.c:219:set_working_voltage_raw: working_voltage_raw = 1800
2021-09-07 16:04:15 temperature.c:281:calibrate_temp_sensor_one_chain: Temperature sensor calibration: chain 0 success.
2021-09-07 16:04:17 temperature.c:281:calibrate_temp_sensor_one_chain: Temperature sensor calibration: chain 1 success.
2021-09-07 16:04:18 temperature.c:281:calibrate_temp_sensor_one_chain: Temperature sensor calibration: chain 2 success.
2021-09-07 16:04:18 uart.c:71:set_baud: set fpga_baud to 6000000
2021-09-07 16:04:20 driver-btm-api.c:245:check_bringup_temp: Bring up temperature is 28
2021-09-07 16:04:20 thread.c:798:create_check_miner_status_thread: create thread
2021-09-07 16:04:20 thread.c:788:create_set_miner_status_thread: create thread
2021-09-07 16:04:20 thread.c:773:create_temperature_monitor_thread: create thread
2021-09-07 16:04:20 frequency.c:749:inc_freq_with_fixed_vco: chain = 255, freq = 565, is_higher_voltage = true
2021-09-07 16:04:20 power_api.c:287:set_to_voltage_by_steps: Set to voltage raw 2020, step by step.
2021-09-07 16:04:38 power_api.c:87:check_voltage_multi: retry time: 0
2021-09-07 16:04:39 power_api.c:37:_get_avg_voltage: chain = 0, voltage = 20.108086
2021-09-07 16:04:40 power_api.c:37:_get_avg_voltage: chain = 1, voltage = 20.089717
2021-09-07 16:04:41 power_api.c:37:_get_avg_voltage: chain = 2, voltage = 20.101963
2021-09-07 16:04:41 power_api.c:50:_get_avg_voltage: average_voltage = 20.099922
2021-09-07 16:04:41 power_api.c:68:check_voltage: target_vol = 20.20, actural_vol = 20.10, check voltage passed.
2021-09-07 16:05:11 power_api.c:287:set_to_voltage_by_steps: Set to voltage raw 1880, step by step.
2021-09-07 16:05:31 power_api.c:87:check_voltage_multi: retry time: 0
2021-09-07 16:05:32 power_api.c:37:_get_avg_voltage: chain = 0, voltage = 18.730400
2021-09-07 16:05:34 power_api.c:37:_get_avg_voltage: chain = 1, voltage = 18.656924
2021-09-07 16:05:35 power_api.c:37:_get_avg_voltage: chain = 2, voltage = 18.693662
2021-09-07 16:05:35 power_api.c:50:_get_avg_voltage: average_voltage = 18.693662
2021-09-07 16:05:35 power_api.c:68:check_voltage: target_vol = 18.80, actural_vol = 18.69, check voltage passed.
2021-09-07 16:05:41 frequency.c:801:inc_freq_with_fixed_step: chain = 0, freq_start = 565, freq_end = 565, freq_step = 5, is_higher_voltage = true
2021-09-07 16:05:41 frequency.c:801:inc_freq_with_fixed_step: chain = 1, freq_start = 565, freq_end = 565, freq_step = 5, is_higher_voltage = true
2021-09-07 16:05:41 frequency.c:801:inc_freq_with_fixed_step: chain = 2, freq_start = 565, freq_end = 565, freq_step = 5, is_higher_voltage = true
2021-09-07 16:05:41 frequency.c:801:inc_freq_with_fixed_step: chain = 0, freq_start = 565, freq_end = 565, freq_step = 5, is_higher_voltage = true
2021-09-07 16:05:41 frequency.c:801:inc_freq_with_fixed_step: chain = 1, freq_start = 565, freq_end = 565, freq_step = 5, is_higher_voltage = true
2021-09-07 16:05:41 frequency.c:801:inc_freq_with_fixed_step: chain = 2, freq_start = 565, freq_end = 565, freq_step = 5, is_higher_voltage = true
2021-09-07 16:05:41 frequency.c:618:inc_asic_diff_freq_by_steps: chain = 0, start = 565, freq_step = 5
2021-09-07 16:05:44 frequency.c:618:inc_asic_diff_freq_by_steps: chain = 1, start = 565, freq_step = 5
2021-09-07 16:05:47 frequency.c:618:inc_asic_diff_freq_by_steps: chain = 2, start = 565, freq_step = 5
2021-09-07 16:05:50 driver-btm-api.c:528:set_timeout: freq = 595, percent = 90, hcn = 73728, timeout = 123
2021-09-07 16:05:50 power_api.c:269:set_to_working_voltage_by_steps: Set to voltage raw 1800, step by step.
2021-09-07 16:06:11 power_api.c:87:check_voltage_multi: retry time: 0
2021-09-07 16:06:12 power_api.c:37:_get_avg_voltage: chain = 0, voltage = 17.897666
2021-09-07 16:06:13 power_api.c:37:_get_avg_voltage: chain = 1, voltage = 17.867051
2021-09-07 16:06:14 power_api.c:37:_get_avg_voltage: chain = 2, voltage = 17.879297
2021-09-07 16:06:14 power_api.c:50:_get_avg_voltage: average_voltage = 17.881338
2021-09-07 16:06:14 power_api.c:68:check_voltage: target_vol = 18.00, actural_vol = 17.88, check voltage passed.
2021-09-07 16:06:14 thread.c:793:create_check_system_status_thread: create thread
2021-09-07 16:06:15 driver-btm-api.c:1988:bitmain_soc_init: Init done!
2021-09-07 16:06:15 driver-btm-api.c:198:set_miner_status: STATUS_INIT
2021-09-07 16:06:19 driver-btm-api.c:198:set_miner_status: STATUS_OKAY
2021-09-07 16:06:20 frequency.c:216:get_ideal_hash_rate_GH: ideal_hash_rate = 54675
2021-09-07 16:06:20 frequency.c:236:get_sale_hash_rate_GH: sale_hash_rate = 53000
2021-09-07 16:06:24 driver-btm-api.c:1199:dhash_chip_send_job: Version num 4
7  Bitcoin / Mining support / Re: Any ideas why my S17 53th keeps showing 127 degrees and 0.00 hash? on: September 07, 2021, 04:02:45 PM
The weird thing about it is that the PSU

There is nothing weird about that, the s17 series are a piece of trash and you should expect everything. What is your input AC voltage?

I'm running it directly to a PDU on a 30 amp breaker like I always do on my 100amp service.
8  Bitcoin / Mining support / Re: Any ideas why my S17 53th keeps showing 127 degrees and 0.00 hash? on: September 07, 2021, 03:44:58 PM
I reinstalled the S17 pro firmware and the kernel log still says:

2021-09-07 15:43:12 thread.c:127:pic_heart_beat_thread: chain[1] heart beat fail 9 times.
2021-09-07 15:43:13 temperature.c:695:get_temp_info: read temp sensor failed: chain = 1, sensor = 0, chip = 55, reg = 1
2021-09-07 15:43:13 temperature.c:695:get_temp_info: read temp sensor failed: chain = 1, sensor = 1, chip = 40, reg = 0
2021-09-07 15:43:15 temperature.c:695:get_temp_info: read temp sensor failed: chain = 1, sensor = 1, chip = 40, reg = 1
2021-09-07 15:43:16 temperature.c:695:get_temp_info: read temp sensor failed: chain = 1, sensor = 2, chip = 180, reg = 0
2021-09-07 15:43:17 temperature.c:695:get_temp_info: read temp sensor failed: chain = 1, sensor = 2, chip = 180, reg = 1
2021-09-07 15:43:18 temperature.c:695:get_temp_info: read temp sensor failed: chain = 1, sensor = 3, chip = 195, reg = 0
2021-09-07 15:43:19 temperature.c:695:get_temp_info: read temp sensor failed: chain = 1, sensor = 3, chip = 195, reg = 1
2021-09-07 15:43:20 temperature.c:695:get_temp_info: read temp sensor failed: chain = 2, sensor = 0, chip = 55, reg = 0
2021-09-07 15:43:20 power_api.c:37:_get_avg_voltage: chain = 0, voltage = 0.000000
2021-09-07 15:43:21 temperature.c:695:get_temp_info: read temp sensor failed: chain = 2, sensor = 0, chip = 55, reg = 1
2021-09-07 15:43:21 thread.c:127:pic_heart_beat_thread: chain[2] heart beat fail 9 times.
2021-09-07 15:43:22 temperature.c:695:get_temp_info: read temp sensor failed: chain = 2, sensor = 1, chip = 40, reg = 0
2021-09-07 15:43:23 temperature.c:695:get_temp_info: read temp sensor failed: chain = 2, sensor = 1, chip = 40, reg = 1
2021-09-07 15:43:24 temperature.c:695:get_temp_info: read temp sensor failed: chain = 2, sensor = 2, chip = 180, reg = 0
2021-09-07 15:43:25 temperature.c:695:get_temp_info: read temp sensor failed: chain = 2, sensor = 2, chip = 180, reg = 1
2021-09-07 15:43:26 temperature.c:695:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 195, reg = 0
2021-09-07 15:43:27 temperature.c:695:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 195, reg = 1
2021-09-07 15:43:29 power_api.c:37:_get_avg_voltage: chain = 1, voltage = 0.000000
2021-09-07 15:43:29 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 0, chip = 55, reg = 0
2021-09-07 15:43:30 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 0, chip = 55, reg = 1
2021-09-07 15:43:31 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 1, chip = 40, reg = 0
2021-09-07 15:43:33 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 1, chip = 40, reg = 1
2021-09-07 15:43:33 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 2, chip = 180, reg = 0
2021-09-07 15:43:35 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 2, chip = 180, reg = 1
2021-09-07 15:43:35 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 3, chip = 195, reg = 0
2021-09-07 15:43:37 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 3, chip = 195, reg = 1
2021-09-07 15:43:37 power_api.c:37:_get_avg_voltage: chain = 2, voltage = 0.000000
2021-09-07 15:43:37 power_api.c:50:_get_avg_voltage: average_voltage = 0.000000
2021-09-07 15:43:37 power_api.c:63:check_voltage: target_vol = 18.80, actural_vol = 0.00, more than 1.0v diff.
2021-09-07 15:43:37 temperature.c:695:get_temp_info: read temp sensor failed: chain = 1, sensor = 0, chip = 55, reg = 0
2021-09-07 15:43:38 power_api.c:87:check_voltage_multi: retry time: 10
2021-09-07 15:43:39 temperature.c:695:get_temp_info: read temp sensor failed: chain = 1, sensor = 0, chip = 55, reg = 1
2021-09-07 15:43:40 temperature.c:695:get_temp_info: read temp sensor failed: chain = 1, sensor = 1, chip = 40, reg = 0
2021-09-07 15:43:41 temperature.c:695:get_temp_info: read temp sensor failed: chain = 1, sensor = 1, chip = 40, reg = 1
2021-09-07 15:43:41 thread.c:127:pic_heart_beat_thread: chain[0] heart beat fail 9 times.
2021-09-07 15:43:42 temperature.c:695:get_temp_info: read temp sensor failed: chain = 1, sensor = 2, chip = 180, reg = 0
2021-09-07 15:43:43 temperature.c:695:get_temp_info: read temp sensor failed: chain = 1, sensor = 2, chip = 180, reg = 1
2021-09-07 15:43:44 temperature.c:695:get_temp_info: read temp sensor failed: chain = 1, sensor = 3, chip = 195, reg = 0
2021-09-07 15:43:45 temperature.c:695:get_temp_info: read temp sensor failed: chain = 1, sensor = 3, chip = 195, reg = 1
2021-09-07 15:43:46 temperature.c:695:get_temp_info: read temp sensor failed: chain = 2, sensor = 0, chip = 55, reg = 0
2021-09-07 15:43:46 power_api.c:37:_get_avg_voltage: chain = 0, voltage = 0.000000
2021-09-07 15:43:47 temperature.c:695:get_temp_info: read temp sensor failed: chain = 2, sensor = 0, chip = 55, reg = 1
2021-09-07 15:43:48 temperature.c:695:get_temp_info: read temp sensor failed: chain = 2, sensor = 1, chip = 40, reg = 0
2021-09-07 15:43:49 temperature.c:695:get_temp_info: read temp sensor failed: chain = 2, sensor = 1, chip = 40, reg = 1
2021-09-07 15:43:50 thread.c:127:pic_heart_beat_thread: chain[1] heart beat fail 10 times.
2021-09-07 15:43:50 temperature.c:695:get_temp_info: read temp sensor failed: chain = 2, sensor = 2, chip = 180, reg = 0
2021-09-07 15:43:51 temperature.c:695:get_temp_info: read temp sensor failed: chain = 2, sensor = 2, chip = 180, reg = 1
2021-09-07 15:43:52 temperature.c:695:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 195, reg = 0
2021-09-07 15:43:54 temperature.c:695:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 195, reg = 1
2021-09-07 15:43:55 power_api.c:37:_get_avg_voltage: chain = 1, voltage = 0.000000
2021-09-07 15:43:55 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 0, chip = 55, reg = 0
2021-09-07 15:43:57 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 0, chip = 55, reg = 1
9  Bitcoin / Mining support / Re: Any ideas why my S17 53th keeps showing 127 degrees and 0.00 hash? on: September 07, 2021, 03:30:00 PM
It seems that the temp sensor is reading abnormal or it is broken.

Have you tried to flash it? If not then try it first then try to test the hashboard one by one

Also, a little bit of research here on the forum will bring you here https://bitcointalk.org/index.php?topic=5244120.0
Reading that would help you to get rid of the sensor problem.

I've been searching online but can't seem to find the recovery firmware to use the SD card with. But I found the normal S17 firmware I can install.

Where do you find the recovery firmware for the SD card?
10  Bitcoin / Mining support / Re: Any ideas why my S17 53th keeps showing 127 degrees and 0.00 hash? on: September 07, 2021, 02:55:13 PM
Code:
2021-09-02 16:20:19 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 0, chip = 55, reg = 0
2021-09-02 16:20:09 temperature.c:695:get_temp_info: read temp sensor failed: chain = 1, sensor = 3, chip = 195, reg = 1
2021-09-02 16:20:10 temperature.c:695:get_temp_info: read temp sensor failed: chain = 2, sensor = 0, chip = 55, reg = 0

As the kernel log, it's not being able to read the temps out of these temp sensors, but the problem isn't exactly that, it's very unlikely for a temp sensor to break, in most cases it's actually a bad chip that tricks the firmware into thinking that issue with one of the sensors.

However, the above is valid when the error only shows for 1 hash board, but then you said the 3 hash boards were working fine and then stopped together, and since it's highly unlikely that ALL there boards will fail at the same time, this confirms Zeusbtc's tech's theory which suggests that in most cases when you get a temp error on all three boards it means your PSU is bad.

The weird thing about it is that the PSU is pretty much brand new.
11  Bitcoin / Mining support / Re: Any ideas why my S17 53th keeps showing 127 degrees and 0.00 hash? on: September 07, 2021, 02:39:20 PM
It seems that the temp sensor is reading abnormal or it is broken.

Have you tried to flash it? If not then try it first then try to test the hashboard one by one

Also, a little bit of research here on the forum will bring you here https://bitcointalk.org/index.php?topic=5244120.0
Reading that would help you to get rid of the sensor problem.

I was thinking of trying the SD card / flashing but wasn't 100% sure how to do it and didn't want to mess up the rig.


Thanks for the link, I'll try to do this today and see if it works.
12  Bitcoin / Mining support / Re: Any ideas why my S17 53th keeps showing 127 degrees and 0.00 hash? on: September 06, 2021, 05:51:35 PM
I took apart the rig and checked everything, cleaned it thoroughly, put it back together, and it's still giving me the 127 degrees on each chip after 5 minutes of running it. I have no idea why. Everything looks good, and the power supply is pretty much brand new. Any ideas?  Cry
13  Bitcoin / Mining support / Re: Any ideas why my S17 53th keeps showing 127 degrees and 0.00 hash? on: September 03, 2021, 02:11:00 PM
Thanks for the tip! Hadn't heard of paste bin, just signed up and pasted it there, good to know of this resource, I would've liked to have used it for the past several years lol  Grin
14  Bitcoin / Mining support / Any ideas why my S17 53th keeps showing 127 degrees and 0.00 hash? on: September 02, 2021, 04:25:58 PM
This is driving me nuts. My S17 53th rig was working fine for the past few months, and now all of a sudden it keeps showing 127 degrees and 0.00 hash. I have to keep resetting it, I'm not sure why. Here is the kernel log. Any ideas?  Cry

It says the kernel log is too long to paste here, so I put it on a paste bin if anyone can help I would appreciate it!

https://pastebin.com/1t1sErVe
15  Bitcoin / Mining support / Re: S17 Pro 53th Troubleshooting on: April 14, 2021, 07:29:29 PM
Well I would check with the shop you bought from first. See if there is any sort of Warranty/RMA that they offer, Either way it was damaged in shipping so hopefully you have some option. If that doesn't work Look into this thread here =Where to fix your Asic miners.

I've had a good experience with HMtech if you are North America based. Apart from that make sure it's worth the cost of repair for that board. (You'll earn back what it costs to repair in mining rewards)

Perfect thank you for that referral! I just sent them an email!

And yes I am talking to the seller to see if I can file a claim with DHL for the damage.

Hi Carl,

just found this topic as I have the same issue and also with the same Supplier Shenzhen Dovina! I have sent them the defect hashboard, they have said they repaired the hashboard and sent it back to me. But again the exact same issue! They didnīt do anything imo and a video is not proof enough! Anyway I have paid 3 times for shipping...

Did they offer you any other solution? I will write a realy bad review, they are a bit afraid of that. But I donīt believe there is more I can do and unfortunately there is nothing I can get...

They were the worst seller on Alibaba, and I bought T17 42T miners from another company on Alibaba around the same time I bought the S17 53 rigs, from Shandong Jiyun co, and same thing, half of them showed up with non working hashboards, questionable PSUs, and all of the miners showed up filthy as all hell, some of them were broken.

I fought with both companies through Alibaba, and I barely got anything of a refund. Just $200.

Thankfully I was able to file claims for both shipments through DHL for the damages, and was able to get a decent amount of claim money back.

I sent all the damaged rigs to HMTech for repair. So far one S53 they said they aren't able to repair the hashboard. They have 5 more miners, and I am hoping they can repair the hashboards on all of them.

I'm done buying from China on Alibaba, they are the worst. They send you the crappiest, dirtiest, most used, barely functioning rigs. And once they get your money, they don't help you at all!
16  Bitcoin / Mining support / Re: S9 powers up but not hashing - have kernel logs on: April 09, 2021, 08:05:59 PM
Ok I'll give that a shot, thanks for the tip!  Grin
17  Bitcoin / Mining support / S9 powers up but not hashing - have kernel logs on: April 09, 2021, 06:57:28 PM
Hey guys, you helped me with my last S9, turns out the fans weren't working. I learned a little about kernel logs thanks to you guys.

I have another S9 that this time won't hash at all, and I'm not sure why based on the kernel logs. Any ideas?

[    0.000000] Booting Linux on physical CPU 0x0
[    0.000000] Linux version 3.14.0-xilinx-ga36f3af-dirty (lzq@ubuntu) (gcc version 4.8.3 20140320 (prerelease) (Sourcery CodeBench Lite 2014.05-23) ) #90 SMP PREEMPT Thu Jun 20 15:01:47 CST 2019
[    0.000000] CPU: ARMv7 Processor [413fc090] revision 0 (ARMv7), cr=18c5387d
[    0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
[    0.000000] Machine model: Xilinx Zynq
[    0.000000] cma: CMA: reserved 128 MiB at 16800000
[    0.000000] Memory policy: Data cache writealloc
[    0.000000] On node 0 totalpages: 126976
[    0.000000] free_area_init_node: node 0, pgdat c075a640, node_mem_map debd8000
[    0.000000]   Normal zone: 992 pages used for memmap
[    0.000000]   Normal zone: 0 pages reserved
[    0.000000]   Normal zone: 126976 pages, LIFO batch:31
[    0.000000] PERCPU: Embedded 8 pages/cpu @debc1000 s9344 r8192 d15232 u32768
[    0.000000] pcpu-alloc: s9344 r8192 d15232 u32768 alloc=8*4096
[    0.000000] pcpu-alloc:
  • 0
  • 1
[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 125984
[    0.000000] Kernel command line: noinitrd mem=496M console=ttyPS0,115200 root=ubi0:rootfs ubi.mtd=1 rootfstype=ubifs rw rootwait
[    0.000000] PID hash table entries: 2048 (order: 1, 8192 bytes)
[    0.000000] Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
[    0.000000] Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
[    0.000000] Memory: 364252K/507904K available (5094K kernel code, 292K rwdata, 1948K rodata, 209K init, 259K bss, 143652K reserved, 0K highmem)
[    0.000000] Virtual kernel memory layout:
[    0.000000]     vector  : 0xffff0000 - 0xffff1000   (   4 kB)
[    0.000000]     fixmap  : 0xfff00000 - 0xfffe0000   ( 896 kB)
[    0.000000]     vmalloc : 0xdf800000 - 0xff000000   ( 504 MB)
[    0.000000]     lowmem  : 0xc0000000 - 0xdf000000   ( 496 MB)
[    0.000000]     pkmap   : 0xbfe00000 - 0xc0000000   (   2 MB)
[    0.000000]     modules : 0xbf000000 - 0xbfe00000   (  14 MB)
[    0.000000]       .text : 0xc0008000 - 0xc06e8cf4   (7044 kB)
[    0.000000]       .init : 0xc06e9000 - 0xc071d480   ( 210 kB)
[    0.000000]       .data : 0xc071e000 - 0xc0767058   ( 293 kB)
[    0.000000]        .bss : 0xc0767064 - 0xc07a7d64   ( 260 kB)
[    0.000000] Preemptible hierarchical RCU implementation.
[    0.000000]    Dump stacks of tasks blocking RCU-preempt GP.
[    0.000000]    RCU restricting CPUs from NR_CPUS=4 to nr_cpu_ids=2.
[    0.000000] RCU: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=2
[    0.000000] NR_IRQS:16 nr_irqs:16 16
[    0.000000] ps7-slcr mapped to df802000
[    0.000000] zynq_clock_init: clkc starts at df802100
[    0.000000] Zynq clock init
[    0.000014] sched_clock: 64 bits at 333MHz, resolution 3ns, wraps every 3298534883328ns
[    0.000292] ps7-ttc #0 at df804000, irq=43
[    0.000594] Console: colour dummy device 80x30
[    0.000624] Calibrating delay loop... 1332.01 BogoMIPS (lpj=6660096)
[    0.090240] pid_max: default: 32768 minimum: 301
[    0.090451] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
[    0.090471] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
[    0.092668] CPU: Testing write buffer coherency: ok
[    0.092984] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
[    0.093041] Setting up static identity map for 0x4d3ec0 - 0x4d3f18
[    0.093261] L310 cache controller enabled
[    0.093280] l2x0: 8 ways, CACHE_ID 0x410000c8, AUX_CTRL 0x72760000, Cache size: 512 kB
[    0.170985] CPU1: Booted secondary processor
[    0.260217] CPU1: thread -1, cpu 1, socket 0, mpidr 80000001
[    0.260345] Brought up 2 CPUs
[    0.260365] SMP: Total of 2 processors activated.
[    0.260373] CPU: All CPU(s) started in SVC mode.
[    0.261031] devtmpfs: initialized
[    0.263482] VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4
[    0.264685] regulator-dummy: no parameters
[    0.271754] NET: Registered protocol family 16
[    0.273979] DMA: preallocated 256 KiB pool for atomic coherent allocations
[    0.276260] cpuidle: using governor ladder
[    0.276273] cpuidle: using governor menu
[    0.283674] syscon f8000000.ps7-slcr: regmap [mem 0xf8000000-0xf8000fff] registered
[    0.285202] hw-breakpoint: found 5 (+1 reserved) breakpoint and 1 watchpoint registers.
[    0.285216] hw-breakpoint: maximum watchpoint size is 4 bytes.
[    0.285325] zynq-ocm f800c000.ps7-ocmc: ZYNQ OCM pool: 256 KiB @ 0xdf880000
[    0.307792] bio: create slab <bio-0> at 0
[    0.309179] vgaarb: loaded
[    0.309891] SCSI subsystem initialized
[    0.310929] usbcore: registered new interface driver usbfs
[    0.311134] usbcore: registered new interface driver hub
[    0.311357] usbcore: registered new device driver usb
[    0.311896] media: Linux media interface: v0.10
[    0.312054] Linux video capture interface: v2.00
[    0.312294] pps_core: LinuxPPS API ver. 1 registered
[    0.312306] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
[    0.312429] PTP clock support registered
[    0.312787] EDAC MC: Ver: 3.0.0
[    0.313843] Advanced Linux Sound Architecture Driver Initialized.
[    0.316594] DMA-API: preallocated 4096 debug entries
[    0.316606] DMA-API: debugging enabled by kernel config
[    0.316683] Switched to clocksource arm_global_timer
[    0.337584] NET: Registered protocol family 2
[    0.338237] TCP established hash table entries: 4096 (order: 2, 16384 bytes)
[    0.338293] TCP bind hash table entries: 4096 (order: 3, 32768 bytes)
[    0.338378] TCP: Hash tables configured (established 4096 bind 4096)
[    0.338426] TCP: reno registered
[    0.338443] UDP hash table entries: 256 (order: 1, 8192 bytes)
[    0.338475] UDP-Lite hash table entries: 256 (order: 1, 8192 bytes)
[    0.338713] NET: Registered protocol family 1
[    0.339049] RPC: Registered named UNIX socket transport module.
[    0.339061] RPC: Registered udp transport module.
[    0.339070] RPC: Registered tcp transport module.
[    0.339077] RPC: Registered tcp NFSv4.1 backchannel transport module.
[    0.339090] PCI: CLS 0 bytes, default 64
[    0.339524] hw perfevents: enabled with ARMv7 Cortex-A9 PMU driver, 7 counters available
[    0.341509] futex hash table entries: 512 (order: 3, 32768 bytes)
[    0.343582] jffs2: version 2.2. (NAND) Đ 2001-2006 Red Hat, Inc.
[    0.343781] msgmni has been set to 967
[    0.344542] io scheduler noop registered
[    0.344555] io scheduler deadline registered
[    0.344595] io scheduler cfq registered (default)
[    0.355566] dma-pl330 f8003000.ps7-dma: Loaded driver for PL330 DMAC-2364208
[    0.355586] dma-pl330 f8003000.ps7-dma:    DBUFF-128x8bytes Num_Chans-8 Num_Peri-4 Num_Events-16
[    0.478054] e0001000.serial: ttyPS0 at MMIO 0xe0001000 (irq = 82, base_baud = 3124999) is a xuartps
[    1.045485] console [ttyPS0] enabled
[    1.049776] xdevcfg f8007000.ps7-dev-cfg: ioremap 0xf8007000 to df866000
[    1.057418] [drm] Initialized drm 1.1.0 20060810
[    1.074419] brd: module loaded
[    1.083819] loop: module loaded
[    1.093226] e1000e: Intel(R) PRO/1000 Network Driver - 2.3.2-k
[    1.099059] e1000e: Copyright(c) 1999 - 2013 Intel Corporation.
[    1.106816] libphy: XEMACPS mii bus: probed
[    1.111185] ------------- phy_id = 0x3625e62
[    1.115905] xemacps e000b000.ps7-ethernet: pdev->id -1, baseaddr 0xe000b000, irq 54
[    1.124812] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[    1.131657] ehci-pci: EHCI PCI platform driver
[    1.138887] zynq-dr e0002000.ps7-usb: Unable to init USB phy, missing?
[    1.145685] usbcore: registered new interface driver usb-storage
[    1.152577] mousedev: PS/2 mouse device common for all mice
[    1.158700] i2c /dev entries driver
[    1.165565] zynq-edac f8006000.ps7-ddrc: ecc not enabled
[    1.171094] cpufreq_cpu0: failed to get cpu0 regulator: -19
[    1.177025] Xilinx Zynq CpuIdle Driver started
[    1.181862] sdhci: Secure Digital Host Controller Interface driver
[    1.188040] sdhci: Copyright(c) Pierre Ossman
[    1.192308] sdhci-pltfm: SDHCI platform and OF driver helper
[    1.199123] mmc0: no vqmmc regulator found
[    1.203135] mmc0: no vmmc regulator found
[    1.246707] mmc0: SDHCI controller on e0100000.ps7-sdio [e0100000.ps7-sdio] using ADMA
[    1.255385] usbcore: registered new interface driver usbhid
[    1.260901] usbhid: USB HID core driver
[    1.265596] nand: device found, Manufacturer ID: 0x2c, Chip ID: 0xda
[    1.271893] nand: Micron MT29F2G08ABAEAWP
[    1.275864] nand: 256MiB, SLC, page size: 2048, OOB size: 64
[    1.281815] Bad block table found at page 131008, version 0x01
[    1.288049] Bad block table found at page 130944, version 0x01
[    1.294099] 3 ofpart partitions found on MTD device pl353-nand
[    1.299876] Creating 3 MTD partitions on "pl353-nand":
[    1.304972] 0x000000000000-0x000002000000 : "BOOT.bin-env-dts-kernel"
[    1.313020] 0x000002000000-0x00000b000000 : "angstram-rootfs"
[    1.320348] 0x00000b000000-0x000010000000 : "upgrade-rootfs"
[    1.329074] nf_conntrack version 0.5.0 (7739 buckets, 30956 max)
[    1.335607] ip_tables: (C) 2000-2006 Netfilter Core Team
[    1.340929] TCP: cubic registered
[    1.344160] NET: Registered protocol family 17
[    1.348861] Registering SWP/SWPB emulation handler
[    1.354752] regulator-dummy: disabling
[    1.359114] UBI: attaching mtd1 to ubi0
[    1.882704] UBI: scanning is finished
[    1.894316] UBI: attached mtd1 (name "angstram-rootfs", size 144 MiB) to ubi0
[    1.901397] UBI: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
[    1.908159] UBI: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
[    1.914824] UBI: VID header offset: 2048 (aligned 2048), data offset: 4096
[    1.921702] UBI: good PEBs: 1152, bad PEBs: 0, corrupted PEBs: 0
[    1.927682] UBI: user volume: 1, internal volumes: 1, max. volumes count: 128
[    1.934790] UBI: max/mean erase counter: 2/0, WL threshold: 4096, image sequence number: 408383306
[    1.943746] UBI: available PEBs: 0, total reserved PEBs: 1152, PEBs reserved for bad PEB handling: 40
[    1.952961] UBI: background thread "ubi_bgt0d" started, PID 1085
[    1.952966] drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
[    1.957037] ALSA device list:
[    1.957041]   No soundcards found.
[    1.973293] UBIFS: background thread "ubifs_bgt0_0" started, PID 1087
[    2.031949] UBIFS: mounted UBI device 0, volume 0, name "rootfs"
[    2.037907] UBIFS: LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
[    2.047088] UBIFS: FS size: 128626688 bytes (122 MiB, 1013 LEBs), journal size 9023488 bytes (8 MiB, 72 LEBs)
[    2.056931] UBIFS: reserved for root: 0 bytes (0 KiB)
[    2.061956] UBIFS: media format: w4/r0 (latest is w4/r0), UUID 3AB50DA4-F7D1-4711-9EEE-D3D8DA845970, small LPT model
[    2.073259] VFS: Mounted root (ubifs filesystem) on device 0:11.
[    2.080226] devtmpfs: mounted
[    2.083338] Freeing unused kernel memory: 208K (c06e9000 - c071d000)
[    2.922233] random: dd urandom read with 0 bits of entropy available
[    3.336735]
[    3.336735] bcm54xx_config_init
[    4.396726]
[    4.396726] bcm54xx_config_init
[    7.397571] xemacps e000b000.ps7-ethernet: Set clk to 24999999 Hz
[    7.403662] xemacps e000b000.ps7-ethernet: link up (100/FULL)
[   26.935642] In axi fpga driver!
[   26.938738] request_mem_region OK!
[   26.942103] AXI fpga dev virtual address is 0xdf9fc000
[   26.947234] *base_vir_addr = 0xc51e
[   26.962579] In fpga mem driver!
[   26.965647] request_mem_region OK!
[   26.969261] fpga mem virtual address is 0xe2000000
[   27.766706]
[   27.766706] bcm54xx_config_init
[   28.856705]
[   28.856705] bcm54xx_config_init
[   31.857560] xemacps e000b000.ps7-ethernet: Set clk to 24999999 Hz
[   31.863575] xemacps e000b000.ps7-ethernet: link up (100/FULL)
[  356.639376] random: nonblocking pool is initialized
main.c:13992: log_level = 4
main.c:14019: This is XILINX board. Totalram:       507424768
main.c:14031: Detect 512MB control board of XILINX
driver-bitmain.c:1776: mmap axi_fpga_addr = 0xb6f61000
driver-bitmain.c:1781: axi_fpga_addr data = 0xc51e
driver-bitmain.c:1797: mmap fpga_mem_addr = 0xb5d5a000
driver-bitmain.c:994: forceFreq=-1 forceFlag=0
driver-bitmain.c:1696: min work minertest[0]:912


main.c:8570: DETECT HW version=0000c51e
main.c:14064: miner ID : 8044c4425c20881c
main.c:14089: Miner Type = S9
main.c:14101: AsicType = 1387
main.c:14104: real AsicNum = 63
main.c:14197: use critical mode to search freq...
driver-bitmain.c:1876: get PLUG ON=0x000000e0
driver-bitmain.c:1946: Find hashboard on Chain[5]
driver-bitmain.c:1946: Find hashboard on Chain[6]
driver-bitmain.c:1946: Find hashboard on Chain[7]
main.c:2282: Check chain[5] PIC fw version=0x00
main.c:2282: Check chain[6] PIC fw version=0x03
main.c:2282: Check chain[7] PIC fw version=0x03
main.c:8940: read pic freq and badcore num...
driver-bitmain.c:5051: Error of set PIC FLASH addr: addr_H=f(3) addr_L=a0(3) on Chain[5]
driver-bitmain.c:5051: Error of set PIC FLASH addr: addr_H=f(3) addr_L=a0(3) on Chain[5]
driver-bitmain.c:5051: Error of set PIC FLASH addr: addr_H=f(3) addr_L=a0(3) on Chain[5]
driver-bitmain.c:5051: Error of set PIC FLASH addr: addr_H=f(3) addr_L=a0(3) on Chain[5]
driver-bitmain.c:5051: Error of set PIC FLASH addr: addr_H=f(3) addr_L=80(3) on Chain[5]
driver-bitmain.c:5051: Error of set PIC FLASH addr: addr_H=f(3) addr_L=80(3) on Chain[5]
driver-bitmain.c:5051: Error of set PIC FLASH addr: addr_H=f(3) addr_L=80(3) on Chain[5]
driver-bitmain.c:5051: Error of set PIC FLASH addr: addr_H=f(3) addr_L=80(3) on Chain[5]
driver-bitmain.c:5051: Error of set PIC FLASH addr: addr_H=f(3) addr_L=e8(3) on Chain[5]
driver-bitmain.c:5051: Error of set PIC FLASH addr: addr_H=f(3) addr_L=e8(3) on Chain[5]
driver-bitmain.c:5051: Error of set PIC FLASH addr: addr_H=f(3) addr_L=e8(3) on Chain[5]
driver-bitmain.c:5051: Error of set PIC FLASH addr: addr_H=f(3) addr_L=e8(3) on Chain[5]
main.c:8961: chain[5]: [3:3] [3:3] [3:3] [3:3] [3:3] [3:3] [3:3] [3:3]
main.c:9148: chain[5] has no freq in PIC! Will use default freq=500 and jump over...
main.c:2282: Check chain[5] PIC fw version=0x03
main.c:8940: read pic freq and badcore num...
main.c:8961: chain[6]: [63:255] [63:255] [63:255] [63:255] [63:255] [63:255] [63:255] [63:255]
main.c:9003: has freq in PIC, will disable freq setting.
main.c:9099: chain[6] has freq in PIC and will jump over...
main.c:9103: Chain[6] has core num in PIC
main.c:9113: Chain[6] ASIC[43] has core num=1
main.c:9113: Chain[6] ASIC[46] has core num=1
main.c:2282: Check chain[6] PIC fw version=0x03
main.c:8940: read pic freq and badcore num...
main.c:8961: chain[7]: [63:255] [63:255] [63:255] [63:255] [63:255] [63:255] [63:255] [63:255]
main.c:9003: has freq in PIC, will disable freq setting.
main.c:9099: chain[7] has freq in PIC and will jump over...
main.c:9103: Chain[7] has core num in PIC
main.c:9113: Chain[7] ASIC[43] has core num=1
main.c:9113: Chain[7] ASIC[46] has core num=1
main.c:2282: Check chain[7] PIC fw version=0x03
main.c:9183: get PIC voltage=3 on chain[5], value=940
main.c:9183: get PIC voltage=57 on chain[6], value=910
main.c:9183: get PIC voltage=57 on chain[7], value=910
main.c:9349: chain[5] temp offset record: 57,57,57,57,57,57,57,57
main.c:9366: chain[5] temp chip I2C addr=0x98
main.c:9349: chain[6] temp offset record: 62,0,0,0,0,0,35,28
main.c:9366: chain[6] temp chip I2C addr=0x98
main.c:9372: chain[6] has no middle temp, use special fix mode.
main.c:9349: chain[7] temp offset record: 62,0,0,0,0,0,35,28
main.c:9366: chain[7] temp chip I2C addr=0x98
main.c:9372: chain[7] has no middle temp, use special fix mode.
main.c:13956: total_exist_chain_num = 3
board_frq_tuning.c:628: single_board_frq_tuning enter
board_frq_tuning.c:629: min_rate, des_rate, fix_volt:13800, 14000, 880
board_frq_tuning.c:254: force_freq not set, don't need tuning
main.c:14645: restart Miner chance num=2
main.c:14685: waiting for receive_func to exit!
main.c:14699: waiting for pic heart to exit!
main.c:13927: bmminer not found= 1994 root       0:00 grep bmminer

main.c:14758: bmminer not found, restart bmminer ...
driver-btm-c5.c:12285:bitmain_c5_init: This is user mode for mining
driver-btm-c5.c:12334:bitmain_c5_init: Detect 512MB control board of XILINX
driver-btm-c5.c:12355:bitmain_c5_init: Miner Type = S9
driver-btm-c5.c:12366:bitmain_c5_init: Miner compile time: Tue Jul 30 20:56:49 CST 2019 type: Antminer S9j
driver-btm-c5.c:12456:bitmain_c5_init: miner ID : 8044c4425c20881c
driver-btm-c5.c:12613:bitmain_c5_init: Checking fans...
driver-btm-c5.c:2990:check_fan_beforeInit: get fan[4] speed=5880
driver-btm-c5.c:2990:check_fan_beforeInit: get fan[4] speed=5880
driver-btm-c5.c:2990:check_fan_beforeInit: get fan[5] speed=4560
driver-btm-c5.c:2990:check_fan_beforeInit: get fan[4] speed=5880
driver-btm-c5.c:2990:check_fan_beforeInit: get fan[5] speed=4560
driver-btm-c5.c:2990:check_fan_beforeInit: get fan[4] speed=5880
driver-btm-c5.c:2990:check_fan_beforeInit: get fan[5] speed=4560
driver-btm-c5.c:1310:set_pic_iic_flash_addr_pointer: Error of set PIC FLASH addr: addr_H=f(0) addr_L=e8(0) on Chain[5]
driver-btm-c5.c:1310:set_pic_iic_flash_addr_pointer: Error of set PIC FLASH addr: addr_H=f(0) addr_L=e8(0) on Chain[5]
driver-btm-c5.c:1310:set_pic_iic_flash_addr_pointer: Error of set PIC FLASH addr: addr_H=f(0) addr_L=e8(0) on Chain[5]
driver-btm-c5.c:1310:set_pic_iic_flash_addr_pointer: Error of set PIC FLASH addr: addr_H=f(0) addr_L=e8(0) on Chain[5]
driver-btm-c5.c:13148:bitmain_c5_init: chain[5]: [0:0] [0:0] [0:0] [0:0] [0:0] [0:0] [0:0] [0:0]
driver-btm-c5.c:1310:set_pic_iic_flash_addr_pointer: Error of set PIC FLASH addr: addr_H=f(0) addr_L=a0(0) on Chain[5]
driver-btm-c5.c:1310:set_pic_iic_flash_addr_pointer: Error of set PIC FLASH addr: addr_H=f(0) addr_L=a0(0) on Chain[5]
driver-btm-c5.c:1310:set_pic_iic_flash_addr_pointer: Error of set PIC FLASH addr: addr_H=f(0) addr_L=a0(0) on Chain[5]
driver-btm-c5.c:1310:set_pic_iic_flash_addr_pointer: Error of set PIC FLASH addr: addr_H=f(0) addr_L=a0(0) on Chain[5]
driver-btm-c5.c:13162:bitmain_c5_init: last_freq: 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00
driver-btm-c5.c:1310:set_pic_iic_flash_addr_pointer: Error of set PIC FLASH addr: addr_H=f(0) addr_L=80(0) on Chain[5]
driver-btm-c5.c:1310:set_pic_iic_flash_addr_pointer: Error of set PIC FLASH addr: addr_H=f(0) addr_L=80(0) on Chain[5]
driver-btm-c5.c:1310:set_pic_iic_flash_addr_pointer: Error of set PIC FLASH addr: addr_H=f(0) addr_L=80(0) on Chain[5]
driver-btm-c5.c:1310:set_pic_iic_flash_addr_pointer: Error of set PIC FLASH addr: addr_H=f(0) addr_L=80(0) on Chain[5]
driver-btm-c5.c:13233:bitmain_c5_init: scan based on domain
driver-btm-c5.c:1883:jump_to_app_CheckAndRestorePIC: Check chain[5] PIC fw version=0x00
driver-btm-c5.c:13148:bitmain_c5_init: chain[6]: [63:255] [63:255] [63:255] [63:255] [63:255] [63:255] [63:255] [63:255]
driver-btm-c5.c:13162:bitmain_c5_init: last_freq: 0x00 0x7d 0x00 0x4e 0x00 0x4e 0x04 0x4e 0x0e 0x4e 0x00 0x4e 0x03 0x4e 0x03 0x4e 0x03 0x4e 0x03 0x4e 0x03 0x4e 0x03 0x4e 0x01 0x4e 0x01 0x4e 0x0f 0x4e 0x0f 0x4e 0x0f 0x4e 0x0f 0x4e 0x05 0x4e 0x06 0x4e 0x23 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e
driver-btm-c5.c:13189:bitmain_c5_init: Detect: use voltage limit rules on single board!
driver-btm-c5.c:13195:bitmain_c5_init: Detect: S9_63 use voltage level=1 : 1
driver-btm-c5.c:13211:bitmain_c5_init: Chain[J7] has backup chain_voltage=860
driver-btm-c5.c:13228:bitmain_c5_init: No scan based on domain
driver-btm-c5.c:1883:jump_to_app_CheckAndRestorePIC: Check chain[6] PIC fw version=0x03
driver-btm-c5.c:13148:bitmain_c5_init: chain[7]: [63:255] [63:255] [63:255] [63:255] [63:255] [63:255] [63:255] [63:255]
driver-btm-c5.c:13162:bitmain_c5_init: last_freq: 0x00 0x7d 0x00 0x4e 0x00 0x4e 0x04 0x4e 0x0e 0x4e 0x00 0x4e 0x03 0x4e 0x03 0x4e 0x03 0x4e 0x03 0x4e 0x03 0x4e 0x03 0x4e 0x01 0x4e 0x01 0x4e 0x0f 0x4e 0x0f 0x4e 0x0f 0x4e 0x0f 0x4e 0x05 0x4e 0x06 0x4e 0x23 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e
driver-btm-c5.c:13189:bitmain_c5_init: Detect: use voltage limit rules on single board!
driver-btm-c5.c:13195:bitmain_c5_init: Detect: S9_63 use voltage level=1 : 1
driver-btm-c5.c:13211:bitmain_c5_init: Chain[J8] has backup chain_voltage=860
driver-btm-c5.c:13228:bitmain_c5_init: No scan based on domain
driver-btm-c5.c:1883:jump_to_app_CheckAndRestorePIC: Check chain[7] PIC fw version=0x03
driver-btm-c5.c:12237:init_exist_chain_table: total_exist_chain_num = 3
driver-btm-c5.c:13361:bitmain_c5_init: Chain[J6] orignal chain_voltage_pic=3 value=940
driver-btm-c5.c:13362:bitmain_c5_init: Chain[J6] original chain_voltage_value=880 adjusted chain_voltage_value:880, value=940
driver-btm-c5.c:13361:bitmain_c5_init: Chain[J7] orignal chain_voltage_pic=57 value=910
driver-btm-c5.c:13362:bitmain_c5_init: Chain[J7] original chain_voltage_value=860 adjusted chain_voltage_value:860, value=910
driver-btm-c5.c:13379:bitmain_c5_init: Chain[J7] will use backup chain_voltage_pic=860 [142]
driver-btm-c5.c:13389:bitmain_c5_init: Chain[J7] get working chain_voltage_pic=142
driver-btm-c5.c:13361:bitmain_c5_init: Chain[J8] orignal chain_voltage_pic=57 value=910
driver-btm-c5.c:13362:bitmain_c5_init: Chain[J8] original chain_voltage_value=860 adjusted chain_voltage_value:860, value=910
driver-btm-c5.c:13379:bitmain_c5_init: Chain[J8] will use backup chain_voltage_pic=860 [142]
driver-btm-c5.c:13389:bitmain_c5_init: Chain[J8] get working chain_voltage_pic=142
driver-btm-c5.c:13494:bitmain_c5_init: Chain[J6] has 0 asic
driver-btm-c5.c:13522:bitmain_c5_init: retry Chain[J6] has 0 asic
driver-btm-c5.c:13522:bitmain_c5_init: retry Chain[J6] has 0 asic
driver-btm-c5.c:13522:bitmain_c5_init: retry Chain[J6] has 0 asic
driver-btm-c5.c:13522:bitmain_c5_init: retry Chain[J6] has 0 asic
driver-btm-c5.c:13522:bitmain_c5_init: retry Chain[J6] has 0 asic
driver-btm-c5.c:13522:bitmain_c5_init: retry Chain[J6] has 0 asic
driver-btm-c5.c:13494:bitmain_c5_init: Chain[J7] has 63 asic
driver-btm-c5.c:13494:bitmain_c5_init: Chain[J8] has 63 asic
driver-btm-c5.c:4543:set_frequency: Chain[J7] has core num in PIC
driver-btm-c5.c:4553:set_frequency: Chain[J7] ASIC[43] has core num=1
driver-btm-c5.c:4553:set_frequency: Chain[J7] ASIC[46] has core num=1
driver-btm-c5.c:4543:set_frequency: Chain[J8] has core num in PIC
driver-btm-c5.c:4553:set_frequency: Chain[J8] ASIC[43] has core num=1
driver-btm-c5.c:4553:set_frequency: Chain[J8] ASIC[46] has core num=1
driver-btm-c5.c:4583:set_frequency: miner total rate=9693GH/s ideal_total_hash_rate = 9500GH/s
driver-btm-c5.c:4608:set_frequency: read PIC voltage=910 on chain[6]
driver-btm-c5.c:4610:set_frequency: Chain:6 chipnum=63
driver-btm-c5.c:4630:set_frequency: Chain[J7] voltage added=0.0V
driver-btm-c5.c:4780:set_frequency: Chain:6 temp offset=0
driver-btm-c5.c:4785:set_frequency: Chain:6 base freq=675
Asic[ 0]:675 Asic[ 1]:675 Asic[ 2]:675 Asic[ 3]:675 Asic[ 4]:675 Asic[ 5]:675 Asic[ 6]:675 Asic[ 7]:675
Asic[ 8]:675 Asic[ 9]:675 Asic[10]:675 Asic[11]:675 Asic[12]:675 Asic[13]:675 Asic[14]:675 Asic[15]:675
Asic[16]:675 Asic[17]:675 Asic[18]:675 Asic[19]:675 Asic[20]:675 Asic[21]:675 Asic[22]:675 Asic[23]:675
Asic[24]:675 Asic[25]:675 Asic[26]:675 Asic[27]:675 Asic[28]:675 Asic[29]:675 Asic[30]:675 Asic[31]:675
Asic[32]:675 Asic[33]:675 Asic[34]:675 Asic[35]:675 Asic[36]:675 Asic[37]:675 Asic[38]:675 Asic[39]:675
Asic[40]:675 Asic[41]:675 Asic[42]:675 Asic[43]:675 Asic[44]:675 Asic[45]:675 Asic[46]:675 Asic[47]:675
Asic[48]:675 Asic[49]:675 Asic[50]:675 Asic[51]:675 Asic[52]:675 Asic[53]:675 Asic[54]:675 Asic[55]:675
Asic[56]:675 Asic[57]:675 Asic[58]:675 Asic[59]:675 Asic[60]:675 Asic[61]:675 Asic[62]:675
driver-btm-c5.c:4821:set_frequency: Chain:6 max freq=675
driver-btm-c5.c:4822:set_frequency: Chain:6 min freq=675

driver-btm-c5.c:4608:set_frequency: read PIC voltage=910 on chain[7]
driver-btm-c5.c:4610:set_frequency: Chain:7 chipnum=63
driver-btm-c5.c:4630:set_frequency: Chain[J8] voltage added=0.0V
driver-btm-c5.c:4780:set_frequency: Chain:7 temp offset=0
driver-btm-c5.c:4785:set_frequency: Chain:7 base freq=675
Asic[ 0]:675 Asic[ 1]:675 Asic[ 2]:675 Asic[ 3]:675 Asic[ 4]:675 Asic[ 5]:675 Asic[ 6]:675 Asic[ 7]:675
Asic[ 8]:675 Asic[ 9]:675 Asic[10]:675 Asic[11]:675 Asic[12]:675 Asic[13]:675 Asic[14]:675 Asic[15]:675
Asic[16]:675 Asic[17]:675 Asic[18]:675 Asic[19]:675 Asic[20]:675 Asic[21]:675 Asic[22]:675 Asic[23]:675
Asic[24]:675 Asic[25]:675 Asic[26]:675 Asic[27]:675 Asic[28]:675 Asic[29]:675 Asic[30]:675 Asic[31]:675
Asic[32]:675 Asic[33]:675 Asic[34]:675 Asic[35]:675 Asic[36]:675 Asic[37]:675 Asic[38]:675 Asic[39]:675
Asic[40]:675 Asic[41]:675 Asic[42]:675 Asic[43]:675 Asic[44]:675 Asic[45]:675 Asic[46]:675 Asic[47]:675
Asic[48]:675 Asic[49]:675 Asic[50]:675 Asic[51]:675 Asic[52]:675 Asic[53]:675 Asic[54]:675 Asic[55]:675
Asic[56]:675 Asic[57]:675 Asic[58]:675 Asic[59]:675 Asic[60]:675 Asic[61]:675 Asic[62]:675
driver-btm-c5.c:4821:set_frequency: Chain:7 max freq=675
driver-btm-c5.c:4822:set_frequency: Chain:7 min freq=675


driver-btm-c5.c:4831:set_frequency: Miner fix freq ...
driver-btm-c5.c:4866:set_frequency: read PIC voltage=910 on chain[6]
driver-btm-c5.c:4867:set_frequency: Chain:6 chipnum=63
driver-btm-c5.c:4886:set_frequency: Chain[J7] voltage added=0.0V
driver-btm-c5.c:5070:set_frequency: Chain:6 temp offset=0
driver-btm-c5.c:5075:set_frequency: Chain:6 base freq=675
Asic[ 0]:675 Asic[ 1]:675 Asic[ 2]:675 Asic[ 3]:675 Asic[ 4]:675 Asic[ 5]:675 Asic[ 6]:675 Asic[ 7]:675
Asic[ 8]:675 Asic[ 9]:675 Asic[10]:675 Asic[11]:675 Asic[12]:675 Asic[13]:675 Asic[14]:675 Asic[15]:675
Asic[16]:675 Asic[17]:675 Asic[18]:675 Asic[19]:675 Asic[20]:675 Asic[21]:675 Asic[22]:675 Asic[23]:675
Asic[24]:675 Asic[25]:675 Asic[26]:675 Asic[27]:675 Asic[28]:675 Asic[29]:675 Asic[30]:675 Asic[31]:675
Asic[32]:675 Asic[33]:675 Asic[34]:675 Asic[35]:675 Asic[36]:675 Asic[37]:675 Asic[38]:675 Asic[39]:675
Asic[40]:675 Asic[41]:675 Asic[42]:675 Asic[43]:675 Asic[44]:675 Asic[45]:675 Asic[46]:675 Asic[47]:675
Asic[48]:675 Asic[49]:675 Asic[50]:675 Asic[51]:675 Asic[52]:675 Asic[53]:675 Asic[54]:675 Asic[55]:675
Asic[56]:675 Asic[57]:675 Asic[58]:675 Asic[59]:675 Asic[60]:675 Asic[61]:675 Asic[62]:675
driver-btm-c5.c:5122:set_frequency: Chain:6 max freq=675
driver-btm-c5.c:5123:set_frequency: Chain:6 min freq=675

driver-btm-c5.c:4866:set_frequency: read PIC voltage=910 on chain[7]
driver-btm-c5.c:4867:set_frequency: Chain:7 chipnum=63
driver-btm-c5.c:4886:set_frequency: Chain[J8] voltage added=0.0V
driver-btm-c5.c:5070:set_frequency: Chain:7 temp offset=0
driver-btm-c5.c:5075:set_frequency: Chain:7 base freq=675
Asic[ 0]:675 Asic[ 1]:675 Asic[ 2]:675 Asic[ 3]:675 Asic[ 4]:675 Asic[ 5]:675 Asic[ 6]:675 Asic[ 7]:675
Asic[ 8]:675 Asic[ 9]:675 Asic[10]:675 Asic[11]:675 Asic[12]:675 Asic[13]:675 Asic[14]:675 Asic[15]:675
Asic[16]:675 Asic[17]:675 Asic[18]:675 Asic[19]:675 Asic[20]:675 Asic[21]:675 Asic[22]:675 Asic[23]:675
Asic[24]:675 Asic[25]:675 Asic[26]:675 Asic[27]:675 Asic[28]:675 Asic[29]:675 Asic[30]:675 Asic[31]:675
Asic[32]:675 Asic[33]:675 Asic[34]:675 Asic[35]:675 Asic[36]:675 Asic[37]:675 Asic[38]:675 Asic[39]:675
Asic[40]:675 Asic[41]:675 Asic[42]:675 Asic[43]:675 Asic[44]:675 Asic[45]:675 Asic[46]:675 Asic[47]:675
Asic[48]:675 Asic[49]:675 Asic[50]:675 Asic[51]:675 Asic[52]:675 Asic[53]:675 Asic[54]:675 Asic[55]:675
Asic[56]:675 Asic[57]:675 Asic[58]:675 Asic[59]:675 Asic[60]:675 Asic[61]:675 Asic[62]:675
driver-btm-c5.c:5122:set_frequency: Chain:7 max freq=675
driver-btm-c5.c:5123:set_frequency: Chain:7 min freq=675

driver-btm-c5.c:5131:set_frequency: max freq = 675
driver-btm-c5.c:4149:ProcessFixFreq: totalRate = 9693, fixed_totalRate = 9500
driver-btm-c5.c:9614:init_uart_baud: set baud=1
driver-btm-c5.c:6605:calibration_sensor_offset: Chain[J7] PIC temp offset: 62,0,0,0,0,0,35,28,0,0,0,0,0,0,0,0,0,0,
driver-btm-c5.c:6639:calibration_sensor_offset: chain[7] temp chip I2C addr=0x98
driver-btm-c5.c:6647:calibration_sensor_offset: chain[7] has no middle temp, use special fix mode.
driver-btm-c5.c:6672:calibration_sensor_offset: Chain[J7] chip[244] use PIC middle temp offset=0 typeID=1a
driver-btm-c5.c:6389:do_calibration_sensor_offset: Warning: Chain[6] chip[244] local:18 remote:96 offset:-48, will fixed offset=27
driver-btm-c5.c:6396:do_calibration_sensor_offset: New offset Chain[7] chip[244] local:18 remote:96 offset:27
driver-btm-c5.c:6765:calibration_sensor_offset: Chain[J7] chip[244] get middle temp offset=27 typeID=1a
driver-btm-c5.c:6605:calibration_sensor_offset: Chain[J8] PIC temp offset: 62,0,0,0,0,0,35,28,0,0,0,0,0,0,0,0,0,0,
driver-btm-c5.c:6639:calibration_sensor_offset: chain[8] temp chip I2C addr=0x98
driver-btm-c5.c:6647:calibration_sensor_offset: chain[8] has no middle temp, use special fix mode.
driver-btm-c5.c:6672:calibration_sensor_offset: Chain[J8] chip[244] use PIC middle temp offset=0 typeID=55
driver-btm-c5.c:6396:do_calibration_sensor_offset: New offset Chain[8] chip[244] local:20 remote:22 offset:27
driver-btm-c5.c:6765:calibration_sensor_offset: Chain[J8] chip[244] get middle temp offset=27 typeID=55
driver-btm-c5.c:12129:set_working_voltage: setting to working voltage...
driver-btm-c5.c:12109:slowly_downgrade_voltage_all_chain: chain[6] set voltage to 900
driver-btm-c5.c:12109:slowly_downgrade_voltage_all_chain: chain[7] set voltage to 900
driver-btm-c5.c:12109:slowly_downgrade_voltage_all_chain: chain[6] set voltage to 890
driver-btm-c5.c:12109:slowly_downgrade_voltage_all_chain: chain[7] set voltage to 890
driver-btm-c5.c:12109:slowly_downgrade_voltage_all_chain: chain[6] set voltage to 880
driver-btm-c5.c:12109:slowly_downgrade_voltage_all_chain: chain[7] set voltage to 880
driver-btm-c5.c:12109:slowly_downgrade_voltage_all_chain: chain[6] set voltage to 870
driver-btm-c5.c:12109:slowly_downgrade_voltage_all_chain: chain[7] set voltage to 870
driver-btm-c5.c:12109:slowly_downgrade_voltage_all_chain: chain[6] set voltage to 860
driver-btm-c5.c:12109:slowly_downgrade_voltage_all_chain: chain[7] set voltage to 860
driver-btm-c5.c:14027:bitmain_c5_init: start thread for read temp
setStartTimePoint total_tv_start_sys=291 total_tv_end_sys=292
driver-btm-c5.c:10330:check_system_work: restartNum = 2 , auto-reinit enabled...
util.c:3207:initiate_stratum: mining.subscribe:{"id": 0, "method": "mining.subscribe", "params": ["bmminer/2.0.0/Antminer S9j/9500"]}
util.c:3207:initiate_stratum: mining.subscribe:{"id": 1, "method": "mining.subscribe", "params": ["bmminer/2.0.0/Antminer S9j/9500"]}
util.c:3207:initiate_stratum: mining.subscribe:{"id": 2, "method": "mining.subscribe", "params": ["bmminer/2.0.0/Antminer S9j/9500"]}
do read_temp_func once...

get RT hashrate from Chain[6]: (asic index start from 1-63)

get RT hashrate from Chain[7]: (asic index start from 1-63)
Check Chain[J7] ASIC RT error: (asic index start from 1-63)
Check Chain[J8] ASIC RT error: (asic index start from 1-63)
Done check_asic_reg
read failed on Chain[6] Chip[62] middle Temp old value:15
Special fix Chain[6] Chip[62] middle Temp = 15
Done read temp on Chain[6]
read failed on Chain[7] Chip[62] middle Temp old value:15
Special fix Chain[7] Chip[62] middle Temp = 15
Done read temp on Chain[7]
Max pcb temp : 0
Read temp failed, set fixed full fan speed
FAN PWM: 100
read_temp_func Done!
CRC error counter=0
18  Bitcoin / Mining support / Re: S9 still not working after swapping out faulty control board on: April 08, 2021, 05:34:22 PM
so after trying a couple of different fans and reading the logs, you guys were 100% right, it was faulty fans - 2 of them to be exact. Luckily I had a spare L3 that wasn't working, so I used the fans from that rig and it seems to be working fine now with get 4 and get 5 - two fans operating and it began to hash. So thank you guys not only for solving the issue, but for teaching me a bit about how to read the logs!  Grin Grin Grin
19  Bitcoin / Mining support / Re: S9 still not working after swapping out faulty control board on: April 07, 2021, 11:49:06 PM
Ok great guys, thank you so much for your help! I will test it out with some fans and see what the problem is.  Grin
20  Bitcoin / Mining support / Re: S9 still not working after swapping out faulty control board on: April 07, 2021, 09:50:02 PM
My other S9 kernel logs look completely different than that one, so I'm really not sure  Cry
Pages: [1] 2 »
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!