Title: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: Biodom on January 15, 2020, 08:43:38 PM
I would like to use this thread for people to document potential problems with their miners and maybe give some tips on reliabilty, RMAs, settings, etc.
I'll start: in the first two mo of operation I got one T17e that dropped a board (out of 9 machines combination of T17, T17e, S17 and S17pro).
I would like to see people opine on t17e/S17e vs other types specifically.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: favebook on January 15, 2020, 09:59:22 PM
My S17e has been running for quite some time without any real problems. Maybe once it dropped the hashrate to 0 but that is a problem I could not repeat and I am not sure what caused it so I cannot blame the unit for it (for now). My T17e has just arrived and I will update you if I have any problems with it.
However, I think I have posted about this somewhere already but I'll say it again here... My S17 Pro which arrived during May or June if I remember correctly had 2 dead hashboards after running on Turbo mode for 2 months. I had it RMA-ed and it comunication was fast as well as the process. I lost about 6 days (including 2 non-working days) of mining and most of those were due to shipping. I shipped from Serbia to Netherlands and it cost me around 150$ if I remember correctly. However, due to our utterly BAD customs, I had to pay 20% VAT on already imported unit. So that RMA cost me alot. And after 5 months of that unit working perfectly, that unit lost all three hashboards and now only if I reboot it a DOZEN times, sometimes one hashboard comes alive and if I am lucky, 2 will come alive, third one seems to be dead as a doornail. I would RMA it again, but I would have to pay another 20% VAT due to problem I previously noted and that is way too expensive considering that my unit is now out of warranty and 20% is calculated for price I paid it in middle of 2019 which is around 2500$ if I remember correctly.
I'd like to note that using Taserz custom firmware for S17 Pro helped me regain some speed as it is now running at 38TH/s with 2 hashboards.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: taserz on January 27, 2020, 04:09:32 AM
My S17e has been running for quite some time without any real problems. Maybe once it dropped the hashrate to 0 but that is a problem I could not repeat and I am not sure what caused it so I cannot blame the unit for it (for now). My T17e has just arrived and I will update you if I have any problems with it.
However, I think I have posted about this somewhere already but I'll say it again here... My S17 Pro which arrived during May or June if I remember correctly had 2 dead hashboards after running on Turbo mode for 2 months. I had it RMA-ed and it comunication was fast as well as the process. I lost about 6 days (including 2 non-working days) of mining and most of those were due to shipping. I shipped from Serbia to Netherlands and it cost me around 150$ if I remember correctly. However, due to our utterly BAD customs, I had to pay 20% VAT on already imported unit. So that RMA cost me alot. And after 5 months of that unit working perfectly, that unit lost all three hashboards and now only if I reboot it a DOZEN times, sometimes one hashboard comes alive and if I am lucky, 2 will come alive, third one seems to be dead as a doornail. I would RMA it again, but I would have to pay another 20% VAT due to problem I previously noted and that is way too expensive considering that my unit is now out of warranty and 20% is calculated for price I paid it in middle of 2019 which is around 2500$ if I remember correctly.
I'd like to note that using Taserz custom firmware for S17 Pro helped me regain some speed as it is now running at 38TH/s with 2 hashboards.
Ayyyyy I still think you should fight the vat on a warranty item. Also I am seeing a lot of bad temp sensors on the new units... Which sucks because if they don't work it won't mine...
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: philipma1957 on January 27, 2020, 05:26:41 AM
Nice thread idea.
All s17 pro work 16 of them
the t17e works 2 of them but pull a lot of power
the t17+ works 1 of them but it is dropping a board.
the t17 2 of them work
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: favebook on January 27, 2020, 02:38:01 PM
Ayyyyy
I still think you should fight the vat on a warranty item.
Also I am seeing a lot of bad temp sensors on the new units... Which sucks because if they don't work it won't mine...
I fought and fought last time, but they warned me that if I do not pay it, they will ship it back to sender. I lost about month or two fighting and explaining them that it was only sent to Bitmain for repair (I had proof). After that time, I gave up and decided to have as little communication as possible with them. They actually disgust me now. I am professional towards them, but when they become arrogant, I am even worse. And yes, bad temperature sensors are becoming quite common problem here as well, I had it personally on two different S17 PRO and I had one friend who had it on all three boards...
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: akagi82 on January 28, 2020, 09:07:26 AM
shipment of 30 T17 42TH
3 problems units:
1) Wont detect hashboard from new, mines with 2
2) After a month, temperature sensor problem and entire machine wont hash
3) Solid Red and Green light
If anyone has solutions to 1 and 3 please reply.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: taserz on January 30, 2020, 01:24:28 PM
shipment of 30 T17 42TH
3 problems units:
1) Wont detect hashboard from new, mines with 2
2) After a month, temperature sensor problem and entire machine wont hash
3) Solid Red and Green light
If anyone has solutions to 1 and 3 please reply.
Number 2.... IS SO COMMON... I hate it
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: akagi82 on February 03, 2020, 05:01:41 PM
Which machines are you running? Are their flagship S17s also experiencing this problem? S9s don't have this game-over problem with sensor errors in later firmware... wtf is up with bitmain, they are literally creating problems for miners.
Adding a fourth problem: 2020-02-02 15:38:53 power_api.c:91:get_average_voltage: error: total_chain get 0 !!
2020-02-02 15:38:53 power_api.c:109:check_voltage: target_vol = 17.90, actural_vol = 0.00, more than 0.5v diff.
2020-02-02 15:38:54 driver-btm-api.c:141:stop_mining: stop mining: power set failed!
2020-02-02 15:38:54 thread.c:832:cancel_check_miner_status_thread: cancel thread
2020-02-02 15:38:54 thread.c:806:cancel_temperature_monitor_thread: cancel thread
2020-02-02 15:38:54 thread.c:816:cancel_read_nonce_reg_thread: cancel thread
2020-02-02 15:38:54 driver-btm-api.c:127:killall_hashboard: ****power off hashboard****
Remedy is to reboot the machine remotely, thus far.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: mikeywith on February 04, 2020, 06:21:09 PM
Here is another case I would like to add, I bought 2 S17s+ 67th, brand new ordered from Bitmain, I am overseas at the moment so I had someone receive and install them, the first gear worked just fine, started hashing right away, but the second one did not turn on.
The PSU works just fine, PSU fans spin the way they are supposed to, however, no lights coming out of the control board, the miner's fan do not spin.
At first, we suspected a PSU-Control Board connection problem, so I asked him to check the wires and everything seems to be in place, he had to leave before he could troubleshoot any further, so probably tomorrow. What I suspect is the PSU, there is a tiny chance that the control board might be bad, but that is unlikely, how often do you hear someone complain about a control board compared to PSU?
Anyway, I will keep you guys updated, unfortunately I can't send the gear back to them, so whatever the problem may be, I have to fix it on my own, I will of course "bother" them every day with emails until I get tried or they compensate me (whichever comes first).
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: philipma1957 on February 04, 2020, 06:39:06 PM
my t17+ has a hot middle board.
it goes to 86 on one chip and the board shuts off.
the fans never ramp up past 3900-4100
i would think if fans went to 4800 i would be good.
also 1 speed not 2 speeds.
would be nice to have a lower speed.
or faster fans.
i will need to figure a way to save that board.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: thierry4wd on February 04, 2020, 06:45:40 PM
Hi , if you need more speed by easy mod, just unplug blue wire on each fan if you want for fix it at full speed ;)
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: philipma1957 on February 04, 2020, 06:53:59 PM
Hi , if you need more speed by easy mod, just unplug blue wire on each fan if you want for fix it at full speed ;)
yeah when I go back up to clifton i will try this.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: mikeywith on February 04, 2020, 08:45:11 PM
The problem is both Asic.to aka Taserz as well as AwesomeMiner have not released anything for the T17+ yet, so you can't undervolt that middle board, therefore I would set all fans at static speed of 100% for now, T17+'s hash board costs more than a large box full of those 12mm fans, so I would risk the fans but not the board.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: akagi82 on February 05, 2020, 12:10:59 AM
Umm.. is Bitmain only accept S17s for RMA? All of the other options for all other miner types dissapeered. Can someone please verify? Is it only me?
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: mikeywith on February 06, 2020, 11:50:49 AM
The PSU works just fine, PSU fans spin the way they are supposed to, however, no lights coming out of the control board, the miner's fan do not spin.
an update on the quoted issue, trying another known to work PSU did not solve the problem, trying a different control board fixed the problem and all hash boards work just fine. This is probably the first time ever that I receive a miner with a faulty control board, what I am going to do now is order a new control board for the S17+ and then start "my war" against Bitmain, it makes no sense to delay the order to wait for them to respond to my complaints. the board costs about 100$ shipped, negotiating with Bitmain will take forever and chances are not high enough. When I have the chance, I will try to inspect the control board and try to figure out what's wrong with it, will keep updating the situation.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: Philipma1957cellphone on February 06, 2020, 01:31:02 PM
So new miner with a brick for a control board.
And it never worked. At all correct.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: mikeywith on February 06, 2020, 04:06:57 PM
That is correct, straight out of the box, installed on a good voltage regulator of 220v so this rules out any power related issues, there does not seem to be any physical damage from DHL shipping so this in a nutshell is a faulty control bored. I will still mess with it to find out what's wrong and why isn't any lights coming up, that will take sometime but i will post my findings. I did order a new one and it ships whiting 20 days so i might end up with at least a month of an expensive gear sitting there doing pretty nothing but loses value.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: Biodom on March 07, 2020, 01:49:09 AM
A new miner (T17+) only hashes on two boards out of three directly from the box.
Pure thievery as it would cost more to send it back than to keep hashing on two boards.
Not pleased.
DO NOT order T17+
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: philipma1957 on March 07, 2020, 09:06:32 PM
A new miner (T17+) only hashes on two boards out of three directly from the box.
Pure thievery as it would cost more to send it back than to keep hashing on two boards.
Not pleased.
DO NOT order T17+
same issue for me. and shipping it back is pretty senseless as ½ ing is coming. It is a PayPal purchase I am under 40 days. I wonder if I ask for a 33% refund if I can get it. I have not pushed very hard on this issue with bitmain as my wife has been sick for 70+ days Since Dec 29 2019. I have had a lot more important things to do. THEN TO FIGHT OVER 1 HASH BOARD. BUT I think doctors have finally figured out my wife health issues and have a treatment plan that is working. I may pursue a 33% refund on the t17+ I will post back on this idea on Monday the 16th of March.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: mikeywith on March 08, 2020, 01:30:49 AM
Glad to hear about your wife's health improvements. As for the 33% refund I'd say it's highly unlikely, Bitmain has very weird "scamy" rules regarding DOA and warranty, if you claim that this was DOA, then they will say that 30 days have passed from the day they shipped the miner, assuming shipping from China takes 10 days, you have only 20 days to act, if you take more than 20 days to send it then it can't be treated as DOA anymore, so even if for some reason DHL, FedEx or whoever your courier may be fails to deliver the miner under 30 days, and say you get it 31 days after it's shipped, and it arrives dead, Bitmain will refuse to treat it as such because their rule states the following: Please ship back them within 30 days from Order Ship out date, otherwise, the devices cannot be treated as DOA.
If you decide to go for RMA, on all the new models you MUST ship the WHOLE miner, you might get lucky enough to be asked to ship only the bad part such as a hash board, but Bitmain reserves all the right to tell you that YOU were the one who toasted the board and that they owe you nothing. Bitmain warranty is a joke, they know that most people will rather keep a half-working miner than waste time returning it and wait for the replacement to arrive due to the nature of mining where time = money. Having said that, I noticed that being persistent can sometimes (actually seldom) grant you some sort of compensation (in a form of coupon/s) without having to send the whole miner nor the defective part. That of course, depends heavily on your purchase history and the mood of whoever is handling your case ;D.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: TeslaWatt.com on March 16, 2020, 09:38:07 PM
A new miner (T17+) only hashes on two boards out of three directly from the box.
Pure thievery as it would cost more to send it back than to keep hashing on two boards.
Not pleased.
DO NOT order T17+
They have RMA facility at "4704 Roseville Road, Suite 108, north highlands CA 95660". USPS should not be to expensive. Here you have more addresses you can ship to: https://support.bitmain.com/hc/en-us/articles/220138027-Global-repair-site-delivery-addresses.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: mikeywith on March 18, 2020, 01:20:07 AM
He MUST create a repair ticket and only send the miner when instructed, he should also send the WHOLE miner and not just the bad hash boards, and if they don't receive it within 30 days from the day THEY shipped it from china, it will not be treated as DOA, if he sends it before 30 days have past - hey can still get paid for the shipping fees in the form of a coupon, so you want to make sure to use the fastest shipping method possible and not exceed the 30 days period if you want to be compensated for the shipping fees.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: TheYankeesWin! on March 18, 2020, 01:51:03 AM
This is good info. I have one of this missing a board units.
It worked for 26 days and now the one board is fuck you.
I will still be under warranty on may 15 which is the ½ ing I may send it in then.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: jbillk on April 24, 2020, 04:37:28 PM
I recently purchased a dead S17. the previous owner said this machine experienced problems with dropping hashboards right out of the box.
He RMA back to Bitmain. He eventually got it back, but only 2 hashbords were working. Eventually the other 2 went later on. I paid scrap value for it.
I changed out the data cables, re-flashed it, took it apart, tightened some connections, played with grounding, etc...
The log shows:
hashboard 0 has 0/48 chips detected
hashboard 1 has 40/48 chips detected
hashboard 2 has 32/48 chips detected
Shuts them all down.
I've been able to get 2 boards working by heating up the unit on startup. I basically put another miner's exhaust on the intake, and block the exhaust fans and get the unit very hot. Once it starts hashing i unblock the fans and remove from heat.
Seems like the boards are very sensitive to temperature on startup, so it may be worth trying if you have bricked units. it just frustrating because sometimes they work fine, and when i reboot they are dead again unless i do my startup procedure.
Now its running 2 of the boards, but randomly the second one drops out do to the temperature sensor issue.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: Scorpyy on April 25, 2020, 01:15:00 PM
Im having identical issues. I own 2x T17+ units ( 2-3 months old ), and i am having issues with temp sensors. One T17+ machine just dropped a temp sensor on 1 chain: [2020/04/21 04:11:03] ERROR: src/temp.c:218 chain[0] sen[2] - Lost, no updates for 10 sec
[2020/04/21 04:11:03] ERROR: src/temp.c:218 chain[0] sen[3] - Lost, no updates for 10 sec
[2020/04/21 04:11:03] WARN: chain[0] - 2 sensor(s) reported their temps!
[2020/04/21 04:11:04] ERROR: src/temp.c:218 chain[0] sen[0] - Lost, no updates for 10 sec
[2020/04/21 04:11:04] ERROR: src/temp.c:218 chain[0] sen[1] - Lost, no updates for 10 sec
[2020/04/21 04:11:04] WARN: chain[0] - 0 sensor(s) reported their temps!
[2020/04/21 04:11:04] ERROR: driver-btm-chain.c:950 chain[0] - Failed to read temp from all sensors!
[2020/04/21 04:11:04] INFO: chain[0] - Shutting down the chain
I tried re-flashing with every possible firmware and issue persisted. Asic.to and Awesome miner firmwares helped me a lot since they auto restart on unbalance. So i usually let it run with 2 boards, however sometimes the third board re-appears but this time some of the chips have an X on them: https://prntscr.com/s5qm51 but im fine with this as long as it stays like this at least. The 2nd T17+ machine - i tough i broke it. I was frustrated that my first T17+ machine is working at 2/3 of power so i decided to up-clock the other machine that was fully operational. But right after the tuning process, 2 sensors on the chain started dropping. [2020/04/24 11:07:43] INFO: chain[2] - 44 chips detected
[2020/04/24 11:07:44] INFO: chain[1] - 44 chips detected
[2020/04/24 11:07:46] INFO: chain[0] - 44 chips detected
[2020/04/24 11:07:53] INFO: Start-up temperature is 24 C (min -15 C)
[2020/04/24 11:07:53] INFO: Switching to manual fan control (100 %)
[2020/04/24 11:07:53] INFO: Setting voltage from 19500 to 19300 mV gradually
[2020/04/24 11:08:11] INFO: Setting freq from 50 to 750 Mhz gradually
[2020/04/24 11:08:11] INFO: Warming up the chips
[2020/04/24 11:08:21] WARN: Target temp 85 C is too high
[2020/04/24 11:08:21] WARN: Overriding target temp to 77 C
[2020/04/24 11:08:21] INFO: Switching to automatic fan control (77 C)
[2020/04/24 11:08:21] INFO: Start mining!
[2020/04/24 11:08:35] ERROR: src/temp.c:218 chain[0] sen[2] - Lost, no updates for 10 sec
[2020/04/24 11:08:35] ERROR: src/temp.c:218 chain[0] sen[3] - Lost, no updates for 10 sec
[2020/04/24 11:08:35] WARN: chain[0] - 2 sensor(s) reported their temps!
As the machine was using Awesome miner firmware, which requires at least 1 sensor our of 4 to be operational i was confused why did the board drop? I contacted support and they are currently investigating this. But then issue became worse: [2020/04/25 02:50:15] INFO: chain[2] - Initializing
[2020/04/25 02:50:15] INFO: chain[1] - Initializing
[2020/04/25 02:50:15] INFO: chain[0] - Initializing
[2020/04/25 02:50:28] INFO: chain[2] - 44 chips detected
[2020/04/25 02:50:32] WARN: chain[1] - 40 of 44 chips detected
[2020/04/25 02:50:35] WARN: chain[0] - 14 of 44 chips detected
[2020/04/25 02:50:43] WARN: chain[1] - 40 of 44 chips detected
[2020/04/25 02:50:46] WARN: chain[0] - 14 of 44 chips detected
[2020/04/25 02:50:55] WARN: chain[1] - 40 of 44 chips detected
[2020/04/25 02:50:55] ERROR: driver-btm-chain.c:487 chain[1] - Failed to detect ASIC chips
[2020/04/25 02:50:55] INFO: chain[1] - Shutting down the chain
[2020/04/25 02:50:55] ERROR: driver-btm-base.c:358 chain[1] - Initialization failed
[2020/04/25 02:50:58] WARN: chain[0] - 14 of 44 chips detected
[2020/04/25 02:50:58] ERROR: driver-btm-chain.c:487 chain[0] - Failed to detect ASIC chips
[2020/04/25 02:50:58] INFO: chain[0] - Shutting down the chain
It now appeared that chips were dead on some boards. I tried switching slots and data cables, all pointed out to 2 dead boards. And this morning i was planning to open the machine and visually inspect if the chips were burnt and guess what? They re-appeared by themselves. [2020/04/25 11:31:15] INFO: chain[2] - Initializing
[2020/04/25 11:31:15] INFO: chain[1] - Initializing
[2020/04/25 11:31:15] INFO: chain[0] - Initializing
[2020/04/25 11:31:28] INFO: chain[2] - 44 chips detected
[2020/04/25 11:31:29] INFO: chain[1] - 44 chips detected
[2020/04/25 11:31:30] INFO: chain[0] - 44 chips detected
However some of the chips have an X: https://prntscr.com/s5qp07 But still better then 1 board. I also contacted Bitmain regarding temp sensors issue, they have told me to ship it back to China ( Europe office is closed due to pandemic ). I have decided to keep the half-working machines as shipping cost + possible complications were not worth it. If i encounter any more issues i will post it here. The post above that said he used to warm up the chips sounds interesting. I will give it a try if boards start dropping again. T17e machine works fine for now.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: favebook on April 25, 2020, 03:49:11 PM
Im having identical issues. I own 2x T17+ units ( 2-3 months old ), and i am having issues with temp sensors.
Try using Asic.to firmware and undervolt or overvolt it a bit. That seemed to be a fix in most instances. Also, if that does not work, try lower frequency with higher voltage.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: Scorpyy on April 25, 2020, 06:12:34 PM
I have Awesome miner firmware currently, but it has the same options.
Here are results.
Starting point:
Pre-set profile @ 61 TH/s 700 Mhz 18.4 voltage = All boards and chips detected, sensors ok, some chips have an "X". Outcome 50 TH/s instead of 60 TH/s. No errors in kernel log
Undervolting:
700 Mhz with 17.8 voltage = chain[0] - 0 of 44 chips detected & chain[1] - 40 of 44 chips detected, shutted down both chains = 1 board operational - 20 TH/s
700 Mhz with 18.0 voltage = chain[0] - 0 of 44 chips detected & chain[1] - 40 of 44 chips detected, shutted down both chains = 1 board operational - 20 TH/s
700 Mhz with 18.2 voltage = 0 of 44 chips detected on 2 boards = 1 board operational, 20 TH/s
Overvolting:
700 Mhz with 18.5 voltage = chain[0] - 0 of 44 chips detected & chain[1] - 40 of 44 chips detected, shutted down both chains = 1 board operational - 20 TH/s
700 Mhz with 18.6 voltage = same as above.
700 Mhz with 18.8 voltage = same as above.
780 Mhz with 19.6 voltage = chain 0 and 1 0 of 44 chips detected. 1 board operational = 23 TH/s
800 Mhz with 19.5 voltage = same as above.
800 Mhz with 19.6 voltage = same as above.
Lowering hashrate:
600 Mhz with 18.4 voltage = chain[0] - 0 of 44 chips detected & chain[1] - 40 of 44 chips detected, shutted down both chains = 1 board operational
550 Mhz with 18.4 voltage = temps sensors error. 0 chains active. Machine is in a reboot loop.
Thing to note that even tho i changed frequency in settings it didn't change on machine, preset was disabled, chains set to "use global".
INFO: Setting freq from 50 to 695 Mhz gradually
and also voltage seems to be starting from same value anyway:
INFO: Setting voltage from 19500 to 18750 mV gradually
Ending point:
Pre-set profile @ 61 TH/s 700 Mhz 18.4 voltage - chain[0] - 0 of 44 chips detected & chain[1] - 40 of 44 chips detected, shutted down both chains = 1 board operational 20 TH/s
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: favebook on April 25, 2020, 07:10:34 PM
Try doing something insane like 600MHz and 18v or 700MHz and 19v to see if that wakes up hashboards. Or go even lower (something like 400/500 MHz with 17-19v).
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: Scorpyy on April 25, 2020, 07:30:01 PM
600 MHz - 18.0 v - 0 of 44 chips detected on 2 boards, 1 board boots up.
600 MHz - 19.0 v -chain[0] - 14 of 44 chain[1] - 0 of 44 chips detected, 1 board boots up.
400 MHz - 19.0 v - 0 of 44 chips detected on 2 boards. 1 board boots up.
I am wondering if i should try what jbillke did by warming up the chips during booting process. Is it safe to try 73 TH/s with 825 ? Is it safe to enable quiet fan on startup?
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: favebook on April 25, 2020, 10:26:23 PM
Yeah, it is safe to enable quiet fan on startup especially in your case...
Idk what your unit default settings are but T17+ are usually 58 TH/s... You can try going for 73, but if all other didn't work, I doubt that will, but please, do try.
Also, try warming up chips before turning machine on as he suggested, might work, but I doubt.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: mysticbitcoin on April 25, 2020, 10:52:00 PM
Hey guys, I'm having an issue with a T17 40TH that I just picked up as well. I picked up a batch of three of them and two of them are hashing at 40TH no problem. One of them has been intermittent and ends up only doing 31TH, where the third board chain [2] is only hashing at 40% ~4TH. I've tried resetting the settings, then updating to the latest firmware from Bitmain, but same problem. Kernel Log: Booting Linux on physical CPU 0x0
Linux version 4.6.0-xilinx-gff8137b-dirty (lzq@armdev2) (gcc version 4.8.3 20140320 (prerelease) (Sourcery CodeBench Lite 2014.05-23) ) #25 SMP PREEMPT Fri Nov 23 15:30:52 CST 2018
CPU: ARMv7 Processor [413fc090] revision 0 (ARMv7), cr=18c5387d
CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
Machine model: Xilinx Zynq
cma: Reserved 16 MiB at 0x0e000000
Memory policy: Data cache writealloc
On node 0 totalpages: 61440
free_area_init_node: node 0, pgdat c0b39280, node_mem_map cde10000
Normal zone: 480 pages used for memmap
Normal zone: 0 pages reserved
Normal zone: 61440 pages, LIFO batch:15
percpu: Embedded 12 pages/cpu @cddf1000 s19776 r8192 d21184 u49152
pcpu-alloc: s19776 r8192 d21184 u49152 alloc=12*4096
pcpu-alloc: [0] 0 [0] 1
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 60960
Kernel command line: mem=240M console=ttyPS0,115200 ramdisk_size=33554432 root=/dev/ram rw earlyprintk
PID hash table entries: 1024 (order: 0, 4096 bytes)
Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
Memory: 195068K/245760K available (6345K kernel code, 231K rwdata, 1896K rodata, 1024K init, 223K bss, 34308K reserved, 16384K cma-reserved, 0K highmem)
Virtual kernel memory layout:
vector : 0xffff0000 - 0xffff1000 ( 4 kB)
fixmap : 0xffc00000 - 0xfff00000 (3072 kB)
vmalloc : 0xcf800000 - 0xff800000 ( 768 MB)
lowmem : 0xc0000000 - 0xcf000000 ( 240 MB)
pkmap : 0xbfe00000 - 0xc0000000 ( 2 MB)
modules : 0xbf000000 - 0xbfe00000 ( 14 MB)
.text : 0xc0008000 - 0xc090c424 (9234 kB)
.init : 0xc0a00000 - 0xc0b00000 (1024 kB)
.data : 0xc0b00000 - 0xc0b39fe0 ( 232 kB)
.bss : 0xc0b39fe0 - 0xc0b71c28 ( 224 kB)
Preemptible hierarchical RCU implementation.
Build-time adjustment of leaf fanout to 32.
RCU restricting CPUs from NR_CPUS=4 to nr_cpu_ids=2.
RCU: Adjusting geometry for rcu_fanout_leaf=32, nr_cpu_ids=2
NR_IRQS:16 nr_irqs:16 16
efuse mapped to cf800000
ps7-slcr mapped to cf802000
L2C: platform modifies aux control register: 0x72360000 -> 0x72760000
L2C: DT/platform modifies aux control register: 0x72360000 -> 0x72760000
L2C-310 erratum 769419 enabled
L2C-310 enabling early BRESP for Cortex-A9
L2C-310 full line of zeros enabled for Cortex-A9
L2C-310 ID prefetch enabled, offset 1 lines
L2C-310 dynamic clock gating enabled, standby mode enabled
L2C-310 cache controller enabled, 8 ways, 512 kB
L2C-310: CACHE_ID 0x410000c8, AUX_CTRL 0x76760001
zynq_clock_init: clkc starts at cf802100
Zynq clock init
sched_clock: 64 bits at 333MHz, resolution 3ns, wraps every 4398046511103ns
clocksource: arm_global_timer: mask: 0xffffffffffffffff max_cycles: 0x4ce07af025, max_idle_ns: 440795209040 ns
Switching to timer-based delay loop, resolution 3ns
clocksource: ttc_clocksource: mask: 0xffff max_cycles: 0xffff, max_idle_ns: 537538477 ns
ps7-ttc #0 at cf80a000, irq=18
Console: colour dummy device 80x30
Calibrating delay loop (skipped), value calculated using timer frequency.. 666.66 BogoMIPS (lpj=3333333)
pid_max: default: 32768 minimum: 301
Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
CPU: Testing write buffer coherency: ok
CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
Setting up static identity map for 0x100000 - 0x100058
CPU1: failed to boot: -1
Brought up 1 CPUs
SMP: Total of 1 processors activated (666.66 BogoMIPS).
CPU: All CPU(s) started in SVC mode.
devtmpfs: initialized
VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4
clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
pinctrl core: initialized pinctrl subsystem
NET: Registered protocol family 16
DMA: preallocated 256 KiB pool for atomic coherent allocations
cpuidle: using governor menu
hw-breakpoint: found 5 (+1 reserved) breakpoint and 1 watchpoint registers.
hw-breakpoint: maximum watchpoint size is 4 bytes.
zynq-ocm f800c000.ps7-ocmc: ZYNQ OCM pool: 256 KiB @ 0xcf880000
vgaarb: loaded
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
media: Linux media interface: v0.10
Linux video capture interface: v2.00
pps_core: LinuxPPS API ver. 1 registered
pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
PTP clock support registered
EDAC MC: Ver: 3.0.0
Advanced Linux Sound Architecture Driver Initialized.
clocksource: Switched to clocksource arm_global_timer
NET: Registered protocol family 2
TCP established hash table entries: 2048 (order: 1, 8192 bytes)
TCP bind hash table entries: 2048 (order: 2, 16384 bytes)
TCP: Hash tables configured (established 2048 bind 2048)
UDP hash table entries: 256 (order: 1, 8192 bytes)
UDP-Lite hash table entries: 256 (order: 1, 8192 bytes)
NET: Registered protocol family 1
RPC: Registered named UNIX socket transport module.
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
PCI: CLS 0 bytes, default 64
Trying to unpack rootfs image as initramfs...
rootfs image is not initramfs (no cpio magic); looks like an initrd
Freeing initrd memory: 21268K (cc63c000 - cdb01000)
hw perfevents: enabled with armv7_cortex_a9 PMU driver, 7 counters available
futex hash table entries: 512 (order: 3, 32768 bytes)
workingset: timestamp_bits=28 max_order=16 bucket_order=0
jffs2: version 2.2. (NAND) (SUMMARY) © 2001-2006 Red Hat, Inc.
io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered (default)
dma-pl330 f8003000.ps7-dma: Loaded driver for PL330 DMAC-241330
dma-pl330 f8003000.ps7-dma: DBUFF-128x8bytes Num_Chans-8 Num_Peri-4 Num_Events-16
e0000000.serial: ttyPS0 at MMIO 0xe0000000 (irq = 158, base_baud = 6249999) is a xuartps
console [ttyPS0] enabled
xdevcfg f8007000.ps7-dev-cfg: ioremap 0xf8007000 to cf86e000
[drm] Initialized drm 1.1.0 20060810
brd: module loaded
loop: module loaded
CAN device driver interface
gpiod_set_value: invalid GPIO
libphy: MACB_mii_bus: probed
macb e000b000.ethernet eth0: Cadence GEM rev 0x00020118 at 0xe000b000 irq 31 (00:0a:35:00:00:00)
Generic PHY e000b000.etherne:00: attached PHY driver [Generic PHY] (mii_bus:phy_addr=e000b000.etherne:00, irq=-1)
e1000e: Intel(R) PRO/1000 Network Driver - 3.2.6-k
e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
ehci-pci: EHCI PCI platform driver
usbcore: registered new interface driver usb-storage
mousedev: PS/2 mouse device common for all mice
i2c /dev entries driver
Xilinx Zynq CpuIdle Driver started
sdhci: Secure Digital Host Controller Interface driver
sdhci: Copyright(c) Pierre Ossman
sdhci-pltfm: SDHCI platform and OF driver helper
mmc0: SDHCI controller on e0100000.ps7-sdio [e0100000.ps7-sdio] using ADMA
ledtrig-cpu: registered to indicate activity on CPUs
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
nand: device found, Manufacturer ID: 0x2c, Chip ID: 0xda
nand: Micron MT29F2G08ABAGAWP
nand: 256 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 128
nand: WARNING: pl35x-nand: the ECC used on your system is too weak compared to the one required by the NAND chip
Bad block table found at page 131008, version 0x01
Bad block table found at page 130944, version 0x01
6 ofpart partitions found on MTD device pl35x-nand
Creating 6 MTD partitions on "pl35x-nand":
0x000000000000-0x000002800000 : "BOOT.bin-env-dts-kernel"
0x000002800000-0x000004800000 : "ramfs"
0x000004800000-0x000005000000 : "configs"
0x000005000000-0x000006000000 : "reserve"
0x000006000000-0x000008000000 : "ramfs-bak"
0x000008000000-0x000010000000 : "reserve1"
NET: Registered protocol family 10
sit: IPv6 over IPv4 tunneling driver
NET: Registered protocol family 17
can: controller area network core (rev 20120528 abi 9)
NET: Registered protocol family 29
can: raw protocol (rev 20120528)
can: broadcast manager protocol (rev 20120528 t)
can: netlink gateway (rev 20130117) max_hops=1
zynq_pm_ioremap: no compatible node found for 'xlnx,zynq-ddrc-a05'
zynq_pm_late_init: Unable to map DDRC IO memory.
Registering SWP/SWPB emulation handler
hctosys: unable to open rtc device (rtc0)
ALSA device list:
No soundcards found.
RAMDISK: gzip image found at block 0
EXT4-fs (ram0): couldn't mount as ext3 due to feature incompatibilities
EXT4-fs (ram0): mounted filesystem without journal. Opts: (null)
VFS: Mounted root (ext4 filesystem) on device 1:0.
devtmpfs: mounted
Freeing unused kernel memory: 1024K (c0a00000 - c0b00000)
EXT4-fs (ram0): re-mounted. Opts: block_validity,delalloc,barrier,user_xattr
random: dd urandom read with 0 bits of entropy available
ubi0: attaching mtd2
ubi0: scanning is finished
ubi0: attached mtd2 (name "configs", size 8 MiB)
ubi0: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
ubi0: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
ubi0: VID header offset: 2048 (aligned 2048), data offset: 4096
ubi0: good PEBs: 64, bad PEBs: 0, corrupted PEBs: 0
ubi0: user volume: 1, internal volumes: 1, max. volumes count: 128
ubi0: max/mean erase counter: 5/2, WL threshold: 4096, image sequence number: 4244297529
ubi0: available PEBs: 0, total reserved PEBs: 64, PEBs reserved for bad PEB handling: 40
ubi0: background thread "ubi_bgt0d" started, PID 708
UBIFS (ubi0:0): background thread "ubifs_bgt0_0" started, PID 711
UBIFS (ubi0:0): UBIFS: mounted UBI device 0, volume 0, name "configs"
UBIFS (ubi0:0): LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
UBIFS (ubi0:0): FS size: 1396736 bytes (1 MiB, 11 LEBs), journal size 888833 bytes (0 MiB, 5 LEBs)
UBIFS (ubi0:0): reserved for root: 65970 bytes (64 KiB)
UBIFS (ubi0:0): media format: w4/r0 (latest is w4/r0), UUID 01559AD8-7B6A-42E6-A3FE-EDF3659527A9, 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: 1052/338, WL threshold: 4096, image sequence number: 4185749592
ubi1: available PEBs: 0, total reserved PEBs: 1020, PEBs reserved for bad PEB handling: 36
ubi1: background thread "ubi_bgt1d" started, PID 720
UBIFS (ubi1:0): background thread "ubifs_bgt1_0" started, PID 723
UBIFS (ubi1:0): UBIFS: mounted UBI device 1, volume 0, name "reserve1"
UBIFS (ubi1:0): LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
UBIFS (ubi1:0): FS size: 123039744 bytes (117 MiB, 969 LEBs), journal size 6221824 bytes (5 MiB, 49 LEBs)
UBIFS (ubi1:0): reserved for root: 4952683 bytes (4836 KiB)
UBIFS (ubi1:0): media format: w4/r0 (latest is w4/r0), UUID 4829CF2C-7435-4146-B2FD-0826AAE8443A, small LPT model
IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
macb e000b000.ethernet eth0: unable to generate target frequency: 25000000 Hz
macb e000b000.ethernet eth0: link up (100/Full)
IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
In axi fpga driver!
request_mem_region OK!
AXI fpga dev virtual address is 0xcfb38000
*base_vir_addr = 0xab013
In fpga mem driver!
request_mem_region OK!
fpga mem virtual address is 0xd2000000
random: nonblocking pool is initialized
2020-04-25 03:46:52 driver-btm-api.c:782:init_freq_mode: This is scan-user version
2020-04-25 03:46:52 driver-btm-api.c:2082:bitmain_soc_init: opt_multi_version = 1
2020-04-25 03:46:52 driver-btm-api.c:2083:bitmain_soc_init: opt_bitmain_ab = 1
2020-04-25 03:46:52 driver-btm-api.c:2084:bitmain_soc_init: opt_bitmain_work_mode = 0
2020-04-25 03:46:52 driver-btm-api.c:2085:bitmain_soc_init: Miner compile time: Mon Jul 29 00:19:06 CST 2019 type: Antminer T17
2020-04-25 03:46:52 driver-btm-api.c:2086:bitmain_soc_init: commit version: e33ca6d 2019-07-18 12:39:03, build by: lol 2019-07-29 00:27:27
2020-04-25 03:46:52 driver-btm-api.c:1937:show_sn: no SN got, please write SN to /nvdata/sn
2020-04-25 03:46:52 driver-btm-api.c:1271:miner_device_init: Detect 256MB control board of XILINX
2020-04-25 03:46:52 driver-btm-api.c:1219:init_fan_parameter: fan_eft : 0 fan_pwm : 0
2020-04-25 03:46:52 thread.c:745:create_read_nonce_reg_thread: create thread
2020-04-25 03:46:58 driver-btm-api.c:1203:init_miner_version: miner ID : 8042750618c0885c
2020-04-25 03:46:58 driver-btm-api.c:1209:init_miner_version: FPGA Version = 0xB013
2020-04-25 03:46:59 eeprom.c:425:check_pattern_test_level: invalid pattern test result. ignore
2020-04-25 03:47:01 eeprom.c:425:check_pattern_test_level: invalid pattern test result. ignore
2020-04-25 03:47:03 eeprom.c:425:check_pattern_test_level: invalid pattern test result. ignore
2020-04-25 03:47:03 driver-btm-api.c:849:get_product_id: product_id[0] = 1
2020-04-25 03:47:03 driver-btm-api.c:849:get_product_id: product_id[1] = 1
2020-04-25 03:47:03 driver-btm-api.c:849:get_product_id: product_id[2] = 1
2020-04-25 03:47:03 driver-btm-api.c:1760:get_ccdly_opt: ccdly_opt[0] = 1
2020-04-25 03:47:03 driver-btm-api.c:1760:get_ccdly_opt: ccdly_opt[1] = 1
2020-04-25 03:47:03 driver-btm-api.c:1760:get_ccdly_opt: ccdly_opt[2] = 1
2020-04-25 03:47:03 driver-btm-api.c:1995:bitmain_board_init: g_ccdly_opt = 1
2020-04-25 03:47:03 driver-btm-api.c:795:_set_project_type: project:2
2020-04-25 03:47:03 driver-btm-api.c:825:_set_project_type: Project type: Antminer T17
2020-04-25 03:47:03 driver-btm-api.c:836:dump_pcb_bom_version: Chain [0] PCB Version: 0x0100
2020-04-25 03:47:03 driver-btm-api.c:837:dump_pcb_bom_version: Chain [0] BOM Version: 0x0100
2020-04-25 03:47:03 driver-btm-api.c:836:dump_pcb_bom_version: Chain [1] PCB Version: 0x0100
2020-04-25 03:47:03 driver-btm-api.c:837:dump_pcb_bom_version: Chain [1] BOM Version: 0x0100
2020-04-25 03:47:03 driver-btm-api.c:836:dump_pcb_bom_version: Chain [2] PCB Version: 0x0100
2020-04-25 03:47:03 driver-btm-api.c:837:dump_pcb_bom_version: Chain [2] BOM Version: 0x0100
2020-04-25 03:47:04 driver-btm-api.c:2015:bitmain_board_init: Fan check passed.
2020-04-25 03:47:04 register.c:283:get_register: !!! reg crc error
2020-04-25 03:47:06 board.c:36:jump_and_app_check_restore_pic: chain[0] PIC jump to app
2020-04-25 03:47:09 board.c:40:jump_and_app_check_restore_pic: Check chain[0] PIC fw version=0xb9
2020-04-25 03:47:11 board.c:36:jump_and_app_check_restore_pic: chain[1] PIC jump to app
2020-04-25 03:47:14 board.c:40:jump_and_app_check_restore_pic: Check chain[1] PIC fw version=0xb9
2020-04-25 03:47:16 board.c:36:jump_and_app_check_restore_pic: chain[2] PIC jump to app
2020-04-25 03:47:20 board.c:40:jump_and_app_check_restore_pic: Check chain[2] PIC fw version=0xb9
2020-04-25 03:47:20 thread.c:740:create_pic_heart_beat_thread: create thread
2020-04-25 03:47:20 power_api.c:55:power_init: power init ...
2020-04-25 03:47:20 driver-btm-api.c:2025:bitmain_board_init: Enter 30s sleep to make sure power release finish.
2020-04-25 03:47:52 power_api.c:231:set_iic_power_to_highest_voltage: setting to voltage: 17.00 ...
2020-04-25 03:47:57 power_api.c:123:check_voltage_multi: retry time: 0
2020-04-25 03:47:59 power_api.c:85:get_average_voltage: chain[0], voltage is: 17.909912
2020-04-25 03:48:01 power_api.c:85:get_average_voltage: chain[1], voltage is: 17.358838
2020-04-25 03:48:03 power_api.c:85:get_average_voltage: chain[2], voltage is: 17.218008
2020-04-25 03:48:03 power_api.c:96:get_average_voltage: aveage voltage is: 17.495586
2020-04-25 03:48:03 power_api.c:181:set_iic_power_by_voltage: now set voltage to : 17.000000
2020-04-25 03:48:03 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[0]: chip baud = 115200, chip_divider = 26
2020-04-25 03:48:03 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[1]: chip baud = 115200, chip_divider = 26
2020-04-25 03:48:03 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[2]: chip baud = 115200, chip_divider = 26
2020-04-25 03:48:03 uart.c:80:set_baud: set fpga_baud = 115200, fpga_divider = 26
2020-04-25 03:48:14 driver-btm-api.c:1146:check_asic_number_with_power_on: Chain[0]: find 29 asic, times 0
2020-04-25 03:48:24 driver-btm-api.c:1146:check_asic_number_with_power_on: Chain[0]: find 30 asic, times 1
2020-04-25 03:48:34 driver-btm-api.c:1146:check_asic_number_with_power_on: Chain[1]: find 30 asic, times 0
2020-04-25 03:48:44 driver-btm-api.c:1146:check_asic_number_with_power_on: Chain[2]: find 30 asic, times 0
2020-04-25 03:48:48 driver-btm-api.c:339:set_order_clock: chain[0]: set order clock, stragegy 3 clock_en=0x1
2020-04-25 03:48:48 driver-btm-api.c:339:set_order_clock: chain[1]: set order clock, stragegy 3 clock_en=0x1
2020-04-25 03:48:48 driver-btm-api.c:339:set_order_clock: chain[2]: set order clock, stragegy 3 clock_en=0x1
2020-04-25 03:48:48 driver-hash-chip.c:490:set_clock_delay_control: core_data = 0xb4
2020-04-25 03:48:48 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[0]: chip baud = 3000000, chip_divider = 0
2020-04-25 03:48:48 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[1]: chip baud = 3000000, chip_divider = 0
2020-04-25 03:48:48 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[2]: chip baud = 3000000, chip_divider = 0
2020-04-25 03:48:48 uart.c:80:set_baud: set fpga_baud = 3000000, fpga_divider = 0
2020-04-25 03:48:48 driver-btm-api.c:1787:check_clock_counter: freq 50 clock_counter_limit 6
2020-04-25 03:48:49 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[0]: chip baud = 115200, chip_divider = 26
2020-04-25 03:48:49 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[1]: chip baud = 115200, chip_divider = 26
2020-04-25 03:48:49 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[2]: chip baud = 115200, chip_divider = 26
2020-04-25 03:48:49 uart.c:80:set_baud: set fpga_baud = 115200, fpga_divider = 26
2020-04-25 03:48:49 voltage[0] = 1710
2020-04-25 03:48:49 voltage[1] = 1710
2020-04-25 03:48:49 voltage[2] = 1710
2020-04-25 03:48:49 power_api.c:139:set_working_voltage: working_voltage = 17.100000
2020-04-25 03:48:50 temperature.c:268:calibrate_temp_sensor_one_chain: Temperature sensor calibration: chain 0 success.
2020-04-25 03:48:52 temperature.c:268:calibrate_temp_sensor_one_chain: Temperature sensor calibration: chain 1 success.
2020-04-25 03:48:53 temperature.c:268:calibrate_temp_sensor_one_chain: Temperature sensor calibration: chain 2 success.
2020-04-25 03:48:53 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[0]: chip baud = 6000000, chip_divider = 7
2020-04-25 03:48:53 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[1]: chip baud = 6000000, chip_divider = 7
2020-04-25 03:48:53 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[2]: chip baud = 6000000, chip_divider = 7
2020-04-25 03:48:53 uart.c:80:set_baud: set fpga_baud = 6000000, fpga_divider = 3
2020-04-25 03:48:55 driver-btm-api.c:239:check_bringup_temp: Bring up temperature is 21
2020-04-25 03:48:55 thread.c:760:create_check_miner_status_thread: create thread
2020-04-25 03:48:55 thread.c:750:create_set_miner_status_thread: create thread
2020-04-25 03:48:55 driver-btm-api.c:732:calculate_timeout: dev->timeout = 392
2020-04-25 03:48:55 freq_tuning.c:152:freq_tuning_get_max_freq: Max freq of tuning is 760
2020-04-25 03:48:55 frequency.c:483:increase_freq_by_frequency_list_slowly: Increase freq slowly for all chain to 670
2020-04-25 03:48:55 frequency.c:340:auto_adaption_high_voltage_increase_frequency: auto adaption increase frequency from 50.000000 to 600.000000 @18.00V.
2020-04-25 03:48:55 frequency.c:341:auto_adaption_high_voltage_increase_frequency: index 0 1
2020-04-25 03:48:55 power_api.c:378:slowly_set_iic_power_to_custom_voltage: slowly setting to voltage: 18.00 ...
2020-04-25 03:49:33 power_api.c:123:check_voltage_multi: retry time: 0
2020-04-25 03:49:34 power_api.c:85:get_average_voltage: chain[0], voltage is: 18.142588
2020-04-25 03:49:36 power_api.c:85:get_average_voltage: chain[1], voltage is: 18.118095
2020-04-25 03:49:38 power_api.c:85:get_average_voltage: chain[2], voltage is: 18.258926
2020-04-25 03:49:38 power_api.c:96:get_average_voltage: aveage voltage is: 18.173203
2020-04-25 03:49:38 driver-btm-api.c:662:increase_freq_slowly: init_freq = 50.00, final_freq = 600.00, freq_step = 5.00, chain = 255
2020-04-25 03:51:29 frequency.c:340:auto_adaption_high_voltage_increase_frequency: auto adaption increase frequency from 600.000000 to 650.000000 @18.00V.
2020-04-25 03:51:29 frequency.c:341:auto_adaption_high_voltage_increase_frequency: index 1 1
2020-04-25 03:51:29 driver-btm-api.c:662:increase_freq_slowly: init_freq = 600.00, final_freq = 650.00, freq_step = 5.00, chain = 255
2020-04-25 03:51:40 frequency.c:340:auto_adaption_high_voltage_increase_frequency: auto adaption increase frequency from 650.000000 to 670.000000 @18.00V.
2020-04-25 03:51:40 frequency.c:341:auto_adaption_high_voltage_increase_frequency: index 2 1
2020-04-25 03:51:40 driver-btm-api.c:662:increase_freq_slowly: init_freq = 650.00, final_freq = 670.00, freq_step = 5.00, chain = 255
2020-04-25 03:51:44 frequency.c:490:increase_freq_by_frequency_list_slowly: Increase freq slowly for chain 0 to 700
2020-04-25 03:51:44 frequency.c:340:auto_adaption_high_voltage_increase_frequency: auto adaption increase frequency from 670.000000 to 700.000000 @18.00V.
2020-04-25 03:51:44 frequency.c:341:auto_adaption_high_voltage_increase_frequency: index 2 1
2020-04-25 03:51:44 driver-btm-api.c:662:increase_freq_slowly: init_freq = 670.00, final_freq = 700.00, freq_step = 5.00, chain = 0
2020-04-25 03:51:50 driver-btm-api.c:763:set_timeout: freq 700 final timeout=168
2020-04-25 03:51:50 power_api.c:396:slowly_set_iic_power_to_working_voltage: slowly setting to voltage: 17.10 ...
2020-04-25 03:52:22 power_api.c:123:check_voltage_multi: retry time: 0
2020-04-25 03:52:24 power_api.c:85:get_average_voltage: chain[0], voltage is: 17.211885
2020-04-25 03:52:26 power_api.c:85:get_average_voltage: chain[1], voltage is: 17.187392
2020-04-25 03:52:27 power_api.c:85:get_average_voltage: chain[2], voltage is: 17.334345
2020-04-25 03:52:27 power_api.c:96:get_average_voltage: aveage voltage is: 17.244541
2020-04-25 03:52:27 frequency.c:582:get_current_min_freq: current min freq 670
2020-04-25 03:52:27 driver-btm-api.c:1787:check_clock_counter: freq 670 clock_counter_limit 85
2020-04-25 03:52:27 register.c:966:register_process_asic_response: Get another asic response: chain = 2, asic = 26
2020-04-25 03:52:27 register.c:1416:quick_dump_core_hash_clock_counter: bad clock counter. chain = 0, asic = 5, core = 0, found 1, clock counter 0x00000000
2020-04-25 03:52:27 driver-btm-api.c:2179:bitmain_soc_init: clock count check failed after retry, wait for hash rate protect later.
2020-04-25 03:52:27 thread.c:735:create_temperature_monitor_thread: create thread
2020-04-25 03:52:27 thread.c:755:create_check_system_status_thread: create thread
2020-04-25 03:52:28 driver-btm-api.c:2198:bitmain_soc_init: Init done!
2020-04-25 03:52:28 driver-btm-api.c:197:set_miner_status: STATUS_INIT
2020-04-25 03:52:32 driver-btm-api.c:197:set_miner_status: STATUS_OKAY
2020-04-25 03:52:37 driver-btm-api.c:1443:dhash_chip_send_job: Verion num 4
2020-04-25 03:57:37 thread.c:384:is_zero_nonce_happened: chain_nonce[0] = 15320
2020-04-25 03:57:37 thread.c:384:is_zero_nonce_happened: chain_nonce[1] = 14787
2020-04-25 03:57:37 thread.c:384:is_zero_nonce_happened: chain_nonce[2] = 12441
2020-04-25 03:57:37 thread.c:440:clear_zero_nonce_mark: 0 nonce protect succeed.
These screen shots are from before updating firmware: https://drive.google.com/file/d/1g6OLOJpkJbIvsySUGZgQwTcQq2ywgsFV/view?usp=sharing https://drive.google.com/file/d/1bgXIlyCkS8awDIgnV9w30f6BQCyrqgXO/view?usp=sharing I've not run the machine for more than 30-40min just in case there could be any further damage. The third board just drops down and stays there! The message I see in the Kernel Log regarding Chain [2] is: 2020-04-25 03:52:27 register.c:966:register_process_asic_response: Get another asic response: chain = 2, asic = 26. What can should I do?
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: favebook on April 25, 2020, 11:20:31 PM
Probably dead chips. Either RMA, try custom firmware undervolt/overvolt or deal with it and keep it like that.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: jbillk on April 26, 2020, 01:29:07 AM
I am wondering if i should try what jbillke did by warming up the chips during booting process.
I don't think the frequency and voltage adjustments will help if the chains aren't initialized. I haven't had much luck with that. Looks like in the log that the pre-heat, voltage tuning, and frequency tuning is done after the board detects all the chips are good to go. Perhaps this is why i've had luck manually pre-heating the boards, as it gets them up to temperature before it attempts to detect all the asic chips. Try to get the startup temp to 75 C and see what happens. [2020/04/25 19:41:01] ERROR: driver-btm-chain.c:487 chain[0] - Failed to detect ASIC chips
[2020/04/25 19:41:01] INFO: chain[0] - Shutting down the chain
[2020/04/25 19:41:02] ERROR: driver-btm-base.c:358 chain[0] - Initialization failed
[2020/04/25 19:41:05] INFO: Start-up temperature is 28 C (min -15 C)
[2020/04/25 19:41:05] INFO: Switching to manual fan control (100 %)
[2020/04/25 19:41:05] INFO: Setting voltage from 21000 to 19400 mV gradually
[2020/04/25 19:41:33] INFO: Setting freq from 50 to 700 Mhz gradually
[2020/04/25 19:41:33] INFO: Warming up the chips
[2020/04/25 19:41:41] INFO: Switching to automatic fan control (75 C)
[2020/04/25 19:41:41] INFO: Start mining!
[2020/04/25 19:42:41] INFO: Setting voltage from 19400 to 19200 mV gradually
[2020/04/25 19:43:03] INFO: Setting voltage from 19200 to 19000 mV gradually
[2020/04/25 19:43:26] INFO: Setting voltage from 19000 to 18800 mV gradually
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: Scorpyy on April 29, 2020, 11:48:09 PM
I have succeeded to get the 2nd board operational by heating up the machine ( previously he saw 40 of 44 chips and when heated 44/44 ). But it was just a matter of time before it dropped out again. I found out that you can do the same thing with his original paper box if miner can see at least 1 board. ( upclock board, cover with a box, let it run for 10s, unplug from wall socket, re-plug again ). On the other machine i found the best solution to be the following: - Machine usually works with 2/3 boards only.
- Up-clock the unit to 800 Mhz.
- Set Disable chips at 92 C.
- Set the unit to downscale if chip overheat.
- Quiet fan mode at startup.
- After it restarts all 3 hashboards are visible ( for a 12hr or a day ).
- Up-clock to 800mhz again but select Pre-save option this time.
[2020/05/01 17:35:06] INFO: Power ON
[2020/05/01 17:35:08] INFO: Starting FPGA queue
[2020/05/01 17:35:08] INFO: Initializing hash boards
[2020/05/01 17:35:08] INFO: chain[2] - Initializing
[2020/05/01 17:35:08] INFO: chain[1] - Initializing
[2020/05/01 17:35:08] INFO: chain[0] - Initializing
[2020/05/01 17:35:22] INFO: chain[2] - 44 chips detected
[2020/05/01 17:35:23] INFO: chain[1] - 44 chips detected
[2020/05/01 17:35:24] ERROR: src/chip139x.c:1006 chain[0] - Failed to receive chip replies
[2020/05/01 17:35:25] ERROR: src/chip139x.c:1006 chain[0] - Failed to receive chip replies
[2020/05/01 17:35:26] ERROR: src/chip139x.c:1006 chain[0] - Failed to receive chip replies
[2020/05/01 17:35:26] WARN: chain[0] - 0 of 44 chips detected
[2020/05/01 17:35:49] ERROR: driver-btm-chain.c:487 chain[0] - Failed to detect ASIC chips
[2020/05/01 17:35:49] INFO: chain[0] - Shutting down the chain
[2020/05/01 17:35:50] ERROR: driver-btm-base.c:358 chain[0] - Initialization failed
[2020/05/01 17:35:53] INFO: Start-up temperature is 22 C (min -15 C)
[2020/05/01 17:35:53] INFO: Activating silent start-up mode
[2020/05/01 17:35:53] INFO: Switching to warm-up fan control (62 C)
[2020/05/01 17:35:53] INFO: Setting voltage from 19500 to 19800 mV gradually
[2020/05/01 17:36:15] INFO: Setting freq from 50 to 800 Mhz gradually
[2020/05/01 17:36:15] INFO: Warming up the chips
[2020/05/01 17:36:24] INFO: Switching to automatic fan control (80 C)
[2020/05/01 17:36:24] INFO: Start mining!
[2020/05/01 17:37:24] INFO: Setting voltage from 19800 to 19600 mV gradually
[2020/05/01 17:37:47] INFO: Setting voltage from 19600 to 19400 mV gradually
[2020/05/02 06:11:10] WARN: chain[1] - Overheated, chip temp=92
[2020/05/02 06:11:10] WARN: Switching to emergency fan control
[2020/05/02 06:11:10] INFO: chain[1] - Shutting down the chain
[2020/05/02 06:11:10] INFO: Shutting down the miner
[2020/05/02 06:11:11] INFO: Stopping FPGA queue
[2020/05/02 06:11:11] INFO: chain[0] - Shutting down the chain
[2020/05/02 06:11:11] INFO: chain[1] - Shutting down the chain
[2020/05/02 06:11:11] INFO: chain[2] - Shutting down the chain
[2020/05/02 06:11:11] INFO: Power OFF
[2020/05/02 06:11:27] INFO: Detected 256 Mb of RAM
[2020/05/02 06:11:27] INFO: Switching to manual fan control (30 %)
[2020/05/02 06:11:27] INFO: Checking fans
[2020/05/02 06:11:27] INFO: fan[0] - OK
[2020/05/02 06:11:27] INFO: fan[1] - OK
[2020/05/02 06:11:27] INFO: fan[2] - OK
[2020/05/02 06:11:27] INFO: fan[3] - OK
[2020/05/02 06:11:33] INFO: Power ON
[2020/05/02 06:11:35] INFO: Starting FPGA queue
[2020/05/02 06:11:35] INFO: Initializing hash boards
[2020/05/02 06:11:35] INFO: chain[2] - Initializing
[2020/05/02 06:11:35] INFO: chain[1] - Initializing
[2020/05/02 06:11:35] INFO: chain[0] - Initializing
[2020/05/02 06:11:48] INFO: chain[2] - 44 chips detected
[2020/05/02 06:11:49] INFO: chain[1] - 44 chips detected
[2020/05/02 06:11:50] INFO: chain[0] - 44 chips detected
[2020/05/02 06:11:57] INFO: Start-up temperature is 24 C (min -15 C)
[2020/05/02 06:11:57] INFO: Activating silent start-up mode
[2020/05/02 06:11:57] INFO: Switching to warm-up fan control (62 C)
[2020/05/02 06:11:57] INFO: Setting voltage from 19500 to 19300 mV gradually
[2020/05/02 06:12:15] INFO: Setting freq from 50 to 750 Mhz gradually
[2020/05/02 06:12:15] INFO: Warming up the chips
[2020/05/02 06:12:25] INFO: Switching to automatic fan control (80 C)
[2020/05/02 06:12:25] INFO: Start mining!
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: PopoJeff on May 03, 2020, 12:35:57 AM
What fresh hell is this? Ran fine for about 16hrs out of the box.... then I dropped one board due to the temp sensor error. Now this crc error. Been thru about a dozen reboots. Comes up runs all 3 boards fine for about 20 min, then drops the one. Also did a reset via interface. 2020-05-03 00:25:10 register.c:306:get_register: !!! reg crc error
2020-05-03 00:25:10 register.c:306:get_register: !!! reg crc error
2020-05-03 00:25:10 register.c:306:get_register: !!! reg crc error
2020-05-03 00:25:10 register.c:306:get_register: !!! reg crc error
2020-05-03 00:25:10 register.c:306:get_register: !!! reg crc error
2020-05-03 00:25:10 register.c:306:get_register: !!! reg crc error
2020-05-03 00:25:10 register.c:306:get_register: !!! reg crc error
2020-05-03 00:25:10 register.c:306:get_register: !!! reg crc error
2020-05-03 00:25:10 register.c:306:get_register: !!! reg crc error
2020-05-03 00:25:10 register.c:306:get_register: !!! reg crc error
2020-05-03 00:25:10 register.c:306:get_register: !!! reg crc error
2020-05-03 00:25:10 register.c:306:get_register: !!! reg crc error
2020-05-03 00:25:10 register.c:306:get_register: !!! reg crc error
2020-05-03 00:25:10 register.c:306:get_register: !!! reg crc error
2020-05-03 00:25:10 register.c:306:get_register: !!! reg crc error
2020-05-03 00:25:10 register.c:306:get_register: !!! reg crc error
2020-05-03 00:25:10 register.c:306:get_register: !!! reg crc error
2020-05-03 00:25:10 register.c:306:get_register: !!! reg crc error
2020-05-03 00:31:23 register.c:313:get_register: !!! REG_TYPE = 1. 679740416
2020-05-03 00:31:23 register.c:313:get_register: !!! REG_TYPE = 1. 545719296
2020-05-03 00:31:23 register.c:313:get_register: !!! REG_TYPE = 1. 1049232384
2020-05-03 00:31:23 register.c:313:get_register: !!! REG_TYPE = 1. 898434048
2020-05-03 00:31:23 register.c:313:get_register: !!! REG_TYPE = 1. 663749632
2020-05-03 00:31:23 register.c:313:get_register: !!! REG_TYPE = 1. 798163968
2020-05-03 00:31:23 register.c:313:get_register: !!! REG_TYPE = 1. 932578304
2020-05-03 00:31:23 register.c:313:get_register: !!! REG_TYPE = 1. 983106560
2020-05-03 00:31:23 register.c:313:get_register: !!! REG_TYPE = 1. 580649984
2020-05-03 00:31:23 register.c:313:get_register: !!! REG_TYPE = 1. 715064320
2020-05-03 00:31:23 register.c:313:get_register: !!! REG_TYPE = 1. 547488768
2020-05-03 00:31:23 register.c:313:get_register: !!! REG_TYPE = 1. 732234752
2020-05-03 00:31:23 register.c:313:get_register: !!! REG_TYPE = 1. 900203520
2020-05-03 00:31:23 register.c:313:get_register: !!! REG_TYPE = 1. 1034617856
2020-05-03 00:31:23 register.c:313:get_register: !!! REG_TYPE = 1. 632161280
2020-05-03 00:31:23 register.c:313:get_register: !!! REG_TYPE = 1. 615580672
2020-05-03 00:31:23 register.c:313:get_register: !!! REG_TYPE = 1. 1018430464
2020-05-03 00:31:23 register.c:313:get_register: !!! REG_TYPE = 1. 884409344
2020-05-03 00:31:23 register.c:313:get_register: !!! REG_TYPE = 1. 716833792
2020-05-03 00:31:23 register.c:313:get_register: !!! REG_TYPE = 1. 566035456
2020-05-03 00:31:23 register.c:313:get_register: !!! REG_TYPE = 1. 1052771328
2020-05-03 00:32:00 register.c:313:get_register: !!! REG_TYPE = 1. 806683648
2020-05-03 00:32:51 register.c:313:get_register: !!! REG_TYPE = 1. 806683648
2020-05-03 00:32:51 register.c:313:get_register: !!! REG_TYPE = 1. 773325824
2020-05-03 00:32:51 register.c:313:get_register: !!! REG_TYPE = 1. 639304704
2020-05-03 00:32:51 register.c:313:get_register: !!! REG_TYPE = 1. 1042154496
2020-05-03 00:32:51 register.c:313:get_register: !!! REG_TYPE = 1. 656475136
2020-05-03 00:32:51 register.c:313:get_register: !!! REG_TYPE = 1. 1059324928
2020-05-03 00:32:51 register.c:313:get_register: !!! REG_TYPE = 1. 925303808
2020-05-03 00:32:51 register.c:313:get_register: !!! REG_TYPE = 1. 690619392
2020-05-03 00:32:51 register.c:313:get_register: !!! REG_TYPE = 1. 573375488
2020-05-03 00:32:51 register.c:313:get_register: !!! REG_TYPE = 1. 808453120
2020-05-03 00:32:51 register.c:313:get_register: !!! REG_TYPE = 1. 942867456
2020-05-03 00:32:51 register.c:313:get_register: !!! REG_TYPE = 1. 540410880
2020-05-03 00:32:51 register.c:313:get_register: !!! REG_TYPE = 1. 758711296
2020-05-03 00:32:51 register.c:313:get_register: !!! REG_TYPE = 1. 893125632
2020-05-03 00:32:51 register.c:313:get_register: !!! REG_TYPE = 1. 1027539968
2020-05-03 00:32:51 register.c:313:get_register: !!! REG_TYPE = 1. 574751744
2020-05-03 00:32:51 register.c:313:get_register: !!! REG_TYPE = 1. 692388864
2020-05-03 00:32:51 register.c:313:get_register: !!! REG_TYPE = 1. 927466496
2020-05-03 00:32:51 register.c:313:get_register: !!! REG_TYPE = 1. 1061880832
2020-05-03 00:32:51 register.c:313:get_register: !!! REG_TYPE = 1. 659424256
2020-05-03 00:32:51 register.c:313:get_register: !!! REG_TYPE = 1. 642843648
2020-05-03 00:32:51 register.c:313:get_register: !!! REG_TYPE = 1. 1045693440
2020-05-03 00:32:51 register.c:313:get_register: !!! REG_TYPE = 1. 911672320
2020-05-03 00:32:51 register.c:313:get_register: !!! REG_TYPE = 1. 676987904
2020-05-03 00:32:51 register.c:313:get_register: !!! REG_TYPE = 1. 593298432
2020-05-03 00:32:51 register.c:313:get_register: !!! REG_TYPE = 1. 694158336
2020-05-03 00:32:51 register.c:313:get_register: !!! REG_TYPE = 1. 560137216
2020-05-03 00:32:51 register.c:313:get_register: !!! REG_TYPE = 1. 962987008
2020-05-03 00:32:51 register.c:313:get_register: !!! REG_TYPE = 1. 879297536
2020-05-03 00:32:51 register.c:313:get_register: !!! REG_TYPE = 1. 745276416
2020-05-03 00:32:51 register.c:313:get_register: !!! REG_TYPE = 1. 611255296
2020-05-03 00:32:51 register.c:313:get_register: !!! REG_TYPE = 1. 913441792
2020-05-03 00:32:51 register.c:313:get_register: !!! REG_TYPE = 1. 1031078912
2020-05-03 00:32:51 register.c:313:get_register: !!! REG_TYPE = 1. 595067904
2020-05-03 00:32:51 register.c:313:get_register: !!! REG_TYPE = 1. 729482240
2020-05-03 00:32:51 register.c:313:get_register: !!! REG_TYPE = 1. 863896576
2020-05-03 00:32:51 register.c:313:get_register: !!! REG_TYPE = 1. 813761536
2020-05-03 00:32:51 register.c:313:get_register: !!! REG_TYPE = 1. 679740416
2020-05-03 00:32:51 register.c:313:get_register: !!! REG_TYPE = 1. 545719296
2020-05-03 00:32:51 register.c:313:get_register: !!! REG_TYPE = 1. 1049232384
2020-05-03 00:32:51 register.c:313:get_register: !!! REG_TYPE = 1. 898434048
2020-05-03 00:32:51 register.c:313:get_register: !!! REG_TYPE = 1. 663749632
2020-05-03 00:32:51 register.c:313:get_register: !!! REG_TYPE = 1. 798163968
2020-05-03 00:32:51 register.c:313:get_register: !!! REG_TYPE = 1. 932578304
2020-05-03 00:32:51 register.c:313:get_register: !!! REG_TYPE = 1. 983106560
2020-05-03 00:32:51 register.c:313:get_register: !!! REG_TYPE = 1. 580649984
2020-05-03 00:32:51 register.c:313:get_register: !!! REG_TYPE = 1. 715064320
2020-05-03 00:32:51 register.c:313:get_register: !!! REG_TYPE = 1. 547488768
2020-05-03 00:32:51 register.c:313:get_register: !!! REG_TYPE = 1. 732234752
2020-05-03 00:34:51 temperature.c:838:get_temp_info: read temp sensor failed: chain = 0, sensor = 2, chip = 54, reg = 0
2020-05-03 00:34:52 temperature.c:838:get_temp_info: read temp sensor failed: chain = 0, sensor = 2, chip = 54, reg = 1
2020-05-03 00:34:52 temperature.c:838:get_temp_info: read temp sensor failed: chain = 0, sensor = 3, chip = 50, reg = 0
2020-05-03 00:34:52 temperature.c:838:get_temp_info: read temp sensor failed: chain = 0, sensor = 3, chip = 50, reg = 1
2020-05-03 00:34:52 thread.c:996:asic_status_monitor_thread: chain 0 can't get enough hashrate reg val for 0 times.
2020-05-03 00:34:53 thread.c:976:asic_status_monitor_thread: ERROR: chain 0 get hashrate_reg_counter 13, require 65, failed times 1: ooooo ooxxx ooooo oxxxx xxxxx xxxxx xxxxx xxxxx xxxxx xxxxx xxxxx xxxxx xxxxx
2020-05-03 00:34:54 thread.c:996:asic_status_monitor_thread: chain 0 can't get enough hashrate reg val for 1 times.
2020-05-03 00:34:55 temperature.c:838:get_temp_info: read temp sensor failed: chain = 0, sensor = 2, chip = 54, reg = 0
2020-05-03 00:34:55 thread.c:976:asic_status_monitor_thread: ERROR: chain 0 get hashrate_reg_counter 13, require 65, failed times 1: ooooo ooxxx ooooo oxxxx xxxxx xxxxx xxxxx xxxxx xxxxx xxxxx xxxxx xxxxx xxxxx
2020-05-03 00:34:55 temperature.c:838:get_temp_info: read temp sensor failed: chain = 0, sensor = 2, chip = 54, reg = 1
2020-05-03 00:34:55 temperature.c:838:get_temp_info: read temp sensor failed: chain = 0, sensor = 3, chip = 50, reg = 0
2020-05-03 00:34:56 temperature.c:838:get_temp_info: read temp sensor failed: chain = 0, sensor = 3, chip = 50, reg = 1
2020-05-03 00:34:56 thread.c:996:asic_status_monitor_thread: chain 0 can't get enough hashrate reg val for 2 times.
2020-05-03 00:34:57 thread.c:976:asic_status_monitor_thread: ERROR: chain 0 get hashrate_reg_counter 13, require 65, failed times 1: ooooo ooxxx ooooo oxxxx xxxxx xxxxx xxxxx xxxxx xxxxx xxxxx xxxxx xxxxx xxxxx
2020-05-03 00:34:58 temperature.c:838:get_temp_info: read temp sensor failed: chain = 0, sensor = 2, chip = 54, reg = 0
2020-05-03 00:34:58 thread.c:996:asic_status_monitor_thread: chain 0 can't get enough hashrate reg val for 3 times.
2020-05-03 00:34:59 temperature.c:838:get_temp_info: read temp sensor failed: chain = 0, sensor = 2, chip = 54, reg = 1
2020-05-03 00:34:59 thread.c:976:asic_status_monitor_thread: ERROR: chain 0 get hashrate_reg_counter 13, require 65, failed times 1: ooooo ooxxx ooooo oxxxx xxxxx xxxxx xxxxx xxxxx xxxxx xxxxx xxxxx xxxxx xxxxx
2020-05-03 00:34:59 temperature.c:838:get_temp_info: read temp sensor failed: chain = 0, sensor = 3, chip = 50, reg = 0
2020-05-03 00:34:59 temperature.c:838:get_temp_info: read temp sensor failed: chain = 0, sensor = 3, chip = 50, reg = 1
2020-05-03 00:35:01 thread.c:996:asic_status_monitor_thread: chain 0 can't get enough hashrate reg val for 4 times.
2020-05-03 00:35:01 thread.c:976:asic_status_monitor_thread: ERROR: chain 0 get hashrate_reg_counter 13, require 65, failed times 1: ooooo ooxxx ooooo oxxxx xxxxx xxxxx xxxxx xxxxx xxxxx xxxxx xxxxx xxxxx xxxxx
2020-05-03 00:35:02 temperature.c:838:get_temp_info: read temp sensor failed: chain = 0, sensor = 2, chip = 54, reg = 0
2020-05-03 00:35:02 temperature.c:838:get_temp_info: read temp sensor failed: chain = 0, sensor = 2, chip = 54, reg = 1
2020-05-03 00:35:03 thread.c:996:asic_status_monitor_thread: chain 0 can't get enough hashrate reg val for 5 times.
2020-05-03 00:35:03 temperature.c:838:get_temp_info: read temp sensor failed: chain = 0, sensor = 3, chip = 50, reg = 0
2020-05-03 00:35:03 temperature.c:838:get_temp_info: read temp sensor failed: chain = 0, sensor = 3, chip = 50, reg = 1
2020-05-03 00:35:03 thread.c:976:asic_status_monitor_thread: ERROR: chain 0 get hashrate_reg_counter 13, require 65, failed times 1: ooooo ooxxx ooooo oxxxx xxxxx xxxxx xxxxx xxxxx xxxxx xxxxx xxxxx xxxxx xxxxx
2020-05-03 00:35:05 thread.c:996:asic_status_monitor_thread: chain 0 can't get enough hashrate reg val for 6 times.
2020-05-03 00:35:05 thread.c:976:asic_status_monitor_thread: ERROR: chain 0 get hashrate_reg_counter 13, require 65, failed times 1: ooooo ooxxx ooooo oxxxx xxxxx xxxxx xxxxx xxxxx xxxxx xxxxx xxxxx xxxxx xxxxx
2020-05-03 00:35:05 temperature.c:838:get_temp_info: read temp sensor failed: chain = 0, sensor = 2, chip = 54, reg = 0
2020-05-03 00:35:06 temperature.c:838:get_temp_info: read temp sensor failed: chain = 0, sensor = 2, chip = 54, reg = 1
2020-05-03 00:35:06 temperature.c:838:get_temp_info: read temp sensor failed: chain = 0, sensor = 3, chip = 50, reg = 0
2020-05-03 00:35:06 temperature.c:838:get_temp_info: read temp sensor failed: chain = 0, sensor = 3, chip = 50, reg = 1
2020-05-03 00:35:07 thread.c:996:asic_status_monitor_thread: chain 0 can't get enough hashrate reg val for 7 times.
2020-05-03 00:35:07 thread.c:976:asic_status_monitor_thread: ERROR: chain 0 get hashrate_reg_counter 13, require 65, failed times 1: ooooo ooxxx ooooo oxxxx xxxxx xxxxx xxxxx xxxxx xxxxx xxxxx xxxxx xxxxx xxxxx
2020-05-03 00:35:09 thread.c:996:asic_status_monitor_thread: chain 0 can't get enough hashrate reg val for 8 times.
2020-05-03 00:35:09 temperature.c:838:get_temp_info: read temp sensor failed: chain = 0, sensor = 2, chip = 54, reg = 0
2020-05-03 00:35:09 thread.c:976:asic_status_monitor_thread: ERROR: chain 0 get hashrate_reg_counter 13, require 65, failed times 1: ooooo ooxxx ooooo oxxxx xxxxx xxxxx xxxxx xxxxx xxxxx xxxxx xxxxx xxxxx xxxxx
2020-05-03 00:35:09 temperature.c:838:get_temp_info: read temp sensor failed: chain = 0, sensor = 2, chip = 54, reg = 1
2020-05-03 00:35:10 temperature.c:838:get_temp_info: read temp sensor failed: chain = 0, sensor = 3, chip = 50, reg = 0
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: mysticbitcoin on May 03, 2020, 02:57:25 AM
Hey, Guys did a full cleaning on this T17 and found that it was running at Full Hash speed for a while, but started going down hill fast! Here is the Kernel Log: (Before it rebooted) Booting Linux on physical CPU 0x0
Linux version 4.6.0-xilinx-gff8137b-dirty (lzq@armdev2) (gcc version 4.8.3 20140320 (prerelease) (Sourcery CodeBench Lite 2014.05-23) ) #25 SMP PREEMPT Fri Nov 23 15:30:52 CST 2018
CPU: ARMv7 Processor [413fc090] revision 0 (ARMv7), cr=18c5387d
CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
Machine model: Xilinx Zynq
cma: Reserved 16 MiB at 0x0e000000
Memory policy: Data cache writealloc
On node 0 totalpages: 61440
free_area_init_node: node 0, pgdat c0b39280, node_mem_map cde10000
Normal zone: 480 pages used for memmap
Normal zone: 0 pages reserved
Normal zone: 61440 pages, LIFO batch:15
percpu: Embedded 12 pages/cpu @cddf1000 s19776 r8192 d21184 u49152
pcpu-alloc: s19776 r8192 d21184 u49152 alloc=12*4096
pcpu-alloc: [0] 0 [0] 1
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 60960
Kernel command line: mem=240M console=ttyPS0,115200 ramdisk_size=33554432 root=/dev/ram rw earlyprintk
PID hash table entries: 1024 (order: 0, 4096 bytes)
Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
Memory: 203756K/245760K available (6345K kernel code, 231K rwdata, 1896K rodata, 1024K init, 223K bss, 25620K reserved, 16384K cma-reserved, 0K highmem)
Virtual kernel memory layout:
vector : 0xffff0000 - 0xffff1000 ( 4 kB)
fixmap : 0xffc00000 - 0xfff00000 (3072 kB)
vmalloc : 0xcf800000 - 0xff800000 ( 768 MB)
lowmem : 0xc0000000 - 0xcf000000 ( 240 MB)
pkmap : 0xbfe00000 - 0xc0000000 ( 2 MB)
modules : 0xbf000000 - 0xbfe00000 ( 14 MB)
.text : 0xc0008000 - 0xc090c424 (9234 kB)
.init : 0xc0a00000 - 0xc0b00000 (1024 kB)
.data : 0xc0b00000 - 0xc0b39fe0 ( 232 kB)
.bss : 0xc0b39fe0 - 0xc0b71c28 ( 224 kB)
Preemptible hierarchical RCU implementation.
Build-time adjustment of leaf fanout to 32.
RCU restricting CPUs from NR_CPUS=4 to nr_cpu_ids=2.
RCU: Adjusting geometry for rcu_fanout_leaf=32, nr_cpu_ids=2
NR_IRQS:16 nr_irqs:16 16
efuse mapped to cf800000
ps7-slcr mapped to cf802000
L2C: platform modifies aux control register: 0x72360000 -> 0x72760000
L2C: DT/platform modifies aux control register: 0x72360000 -> 0x72760000
L2C-310 erratum 769419 enabled
L2C-310 enabling early BRESP for Cortex-A9
L2C-310 full line of zeros enabled for Cortex-A9
L2C-310 ID prefetch enabled, offset 1 lines
L2C-310 dynamic clock gating enabled, standby mode enabled
L2C-310 cache controller enabled, 8 ways, 512 kB
L2C-310: CACHE_ID 0x410000c8, AUX_CTRL 0x76760001
zynq_clock_init: clkc starts at cf802100
Zynq clock init
sched_clock: 64 bits at 333MHz, resolution 3ns, wraps every 4398046511103ns
clocksource: arm_global_timer: mask: 0xffffffffffffffff max_cycles: 0x4ce07af025, max_idle_ns: 440795209040 ns
Switching to timer-based delay loop, resolution 3ns
clocksource: ttc_clocksource: mask: 0xffff max_cycles: 0xffff, max_idle_ns: 537538477 ns
ps7-ttc #0 at cf80a000, irq=18
Console: colour dummy device 80x30
Calibrating delay loop (skipped), value calculated using timer frequency.. 666.66 BogoMIPS (lpj=3333333)
pid_max: default: 32768 minimum: 301
Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
CPU: Testing write buffer coherency: ok
CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
Setting up static identity map for 0x100000 - 0x100058
CPU1: failed to boot: -1
Brought up 1 CPUs
SMP: Total of 1 processors activated (666.66 BogoMIPS).
CPU: All CPU(s) started in SVC mode.
devtmpfs: initialized
VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4
clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
pinctrl core: initialized pinctrl subsystem
NET: Registered protocol family 16
DMA: preallocated 256 KiB pool for atomic coherent allocations
cpuidle: using governor menu
hw-breakpoint: found 5 (+1 reserved) breakpoint and 1 watchpoint registers.
hw-breakpoint: maximum watchpoint size is 4 bytes.
zynq-ocm f800c000.ps7-ocmc: ZYNQ OCM pool: 256 KiB @ 0xcf880000
vgaarb: loaded
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
media: Linux media interface: v0.10
Linux video capture interface: v2.00
pps_core: LinuxPPS API ver. 1 registered
pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
PTP clock support registered
EDAC MC: Ver: 3.0.0
Advanced Linux Sound Architecture Driver Initialized.
clocksource: Switched to clocksource arm_global_timer
NET: Registered protocol family 2
TCP established hash table entries: 2048 (order: 1, 8192 bytes)
TCP bind hash table entries: 2048 (order: 2, 16384 bytes)
TCP: Hash tables configured (established 2048 bind 2048)
UDP hash table entries: 256 (order: 1, 8192 bytes)
UDP-Lite hash table entries: 256 (order: 1, 8192 bytes)
NET: Registered protocol family 1
RPC: Registered named UNIX socket transport module.
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
PCI: CLS 0 bytes, default 64
Trying to unpack rootfs image as initramfs...
rootfs image is not initramfs (no cpio magic); looks like an initrd
Freeing initrd memory: 12580K (cceb8000 - cdb01000)
hw perfevents: enabled with armv7_cortex_a9 PMU driver, 7 counters available
futex hash table entries: 512 (order: 3, 32768 bytes)
workingset: timestamp_bits=28 max_order=16 bucket_order=0
jffs2: version 2.2. (NAND) (SUMMARY) © 2001-2006 Red Hat, Inc.
io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered (default)
dma-pl330 f8003000.ps7-dma: Loaded driver for PL330 DMAC-241330
dma-pl330 f8003000.ps7-dma: DBUFF-128x8bytes Num_Chans-8 Num_Peri-4 Num_Events-16
e0000000.serial: ttyPS0 at MMIO 0xe0000000 (irq = 158, base_baud = 6249999) is a xuartps
console [ttyPS0] enabled
xdevcfg f8007000.ps7-dev-cfg: ioremap 0xf8007000 to cf86e000
[drm] Initialized drm 1.1.0 20060810
brd: module loaded
loop: module loaded
CAN device driver interface
gpiod_set_value: invalid GPIO
libphy: MACB_mii_bus: probed
macb e000b000.ethernet eth0: Cadence GEM rev 0x00020118 at 0xe000b000 irq 31 (00:0a:35:00:00:00)
Generic PHY e000b000.etherne:00: attached PHY driver [Generic PHY] (mii_bus:phy_addr=e000b000.etherne:00, irq=-1)
e1000e: Intel(R) PRO/1000 Network Driver - 3.2.6-k
e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
ehci-pci: EHCI PCI platform driver
usbcore: registered new interface driver usb-storage
mousedev: PS/2 mouse device common for all mice
i2c /dev entries driver
Xilinx Zynq CpuIdle Driver started
sdhci: Secure Digital Host Controller Interface driver
sdhci: Copyright(c) Pierre Ossman
sdhci-pltfm: SDHCI platform and OF driver helper
mmc0: SDHCI controller on e0100000.ps7-sdio [e0100000.ps7-sdio] using ADMA
ledtrig-cpu: registered to indicate activity on CPUs
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
nand: device found, Manufacturer ID: 0x2c, Chip ID: 0xda
nand: Micron MT29F2G08ABAGAWP
nand: 256 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 128
nand: WARNING: pl35x-nand: the ECC used on your system is too weak compared to the one required by the NAND chip
Bad block table found at page 131008, version 0x01
Bad block table found at page 130944, version 0x01
6 ofpart partitions found on MTD device pl35x-nand
Creating 6 MTD partitions on "pl35x-nand":
0x000000000000-0x000002800000 : "BOOT.bin-env-dts-kernel"
0x000002800000-0x000004800000 : "ramfs"
0x000004800000-0x000005000000 : "configs"
0x000005000000-0x000006000000 : "reserve"
0x000006000000-0x000008000000 : "ramfs-bak"
0x000008000000-0x000010000000 : "reserve1"
NET: Registered protocol family 10
sit: IPv6 over IPv4 tunneling driver
NET: Registered protocol family 17
can: controller area network core (rev 20120528 abi 9)
NET: Registered protocol family 29
can: raw protocol (rev 20120528)
can: broadcast manager protocol (rev 20120528 t)
can: netlink gateway (rev 20130117) max_hops=1
zynq_pm_ioremap: no compatible node found for 'xlnx,zynq-ddrc-a05'
zynq_pm_late_init: Unable to map DDRC IO memory.
Registering SWP/SWPB emulation handler
hctosys: unable to open rtc device (rtc0)
ALSA device list:
No soundcards found.
RAMDISK: gzip image found at block 0
EXT4-fs (ram0): couldn't mount as ext3 due to feature incompatibilities
EXT4-fs (ram0): mounted filesystem without journal. Opts: (null)
VFS: Mounted root (ext4 filesystem) on device 1:0.
devtmpfs: mounted
Freeing unused kernel memory: 1024K (c0a00000 - c0b00000)
EXT4-fs (ram0): re-mounted. Opts: block_validity,delalloc,barrier,user_xattr
random: dd urandom read with 0 bits of entropy available
ubi0: attaching mtd2
ubi0: scanning is finished
ubi0: attached mtd2 (name "configs", size 8 MiB)
ubi0: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
ubi0: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
ubi0: VID header offset: 2048 (aligned 2048), data offset: 4096
ubi0: good PEBs: 64, bad PEBs: 0, corrupted PEBs: 0
ubi0: user volume: 1, internal volumes: 1, max. volumes count: 128
ubi0: max/mean erase counter: 5/2, WL threshold: 4096, image sequence number: 4244297529
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 01559AD8-7B6A-42E6-A3FE-EDF3659527A9, 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: 1052/338, WL threshold: 4096, image sequence number: 4185749592
ubi1: available PEBs: 0, total reserved PEBs: 1020, PEBs reserved for bad PEB handling: 36
ubi1: background thread "ubi_bgt1d" started, PID 720
UBIFS (ubi1:0): background thread "ubifs_bgt1_0" started, PID 723
UBIFS (ubi1:0): recovery needed
UBIFS (ubi1:0): recovery completed
UBIFS (ubi1:0): UBIFS: mounted UBI device 1, volume 0, name "reserve1"
UBIFS (ubi1:0): LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
UBIFS (ubi1:0): FS size: 123039744 bytes (117 MiB, 969 LEBs), journal size 6221824 bytes (5 MiB, 49 LEBs)
UBIFS (ubi1:0): reserved for root: 4952683 bytes (4836 KiB)
UBIFS (ubi1:0): media format: w4/r0 (latest is w4/r0), UUID 4829CF2C-7435-4146-B2FD-0826AAE8443A, small LPT model
IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
macb e000b000.ethernet eth0: unable to generate target frequency: 25000000 Hz
macb e000b000.ethernet eth0: link up (100/Full)
IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
In axi fpga driver!
request_mem_region OK!
AXI fpga dev virtual address is 0xcfb38000
*base_vir_addr = 0xab013
In fpga mem driver!
request_mem_region OK!
fpga mem virtual address is 0xd2000000
random: nonblocking pool is initialized
2020-04-29 16:46:29 driver-btm-api.c:631:init_freq_mode: This is scan-user version
2020-04-29 16:46:29 driver-btm-api.c:1994:bitmain_soc_init: opt_multi_version = 1
2020-04-29 16:46:29 driver-btm-api.c:1995:bitmain_soc_init: opt_bitmain_ab = 1
2020-04-29 16:46:29 driver-btm-api.c:1996:bitmain_soc_init: opt_bitmain_work_mode = 0
2020-04-29 16:46:29 driver-btm-api.c:1997:bitmain_soc_init: Miner compile time: Tue Dec 24 16:13:07 CST 2019 type: Antminer T17
2020-04-29 16:46:29 driver-btm-api.c:1998:bitmain_soc_init: commit version: e93a09b 2019-12-24 16:03:45, build by: lol 2019-12-24 16:19:49
2020-04-29 16:46:29 driver-btm-api.c:1810:show_sn: no SN got, please write SN to /nvdata/sn
2020-04-29 16:46:29 driver-btm-api.c:1135:miner_device_init: Detect 256MB control board of XILINX
2020-04-29 16:46:29 driver-btm-api.c:1083:init_fan_parameter: fan_eft : 0 fan_pwm : 0
2020-04-29 16:46:29 thread.c:789:create_read_nonce_reg_thread: create thread
2020-04-29 16:46:35 driver-btm-api.c:1067:init_miner_version: miner ID : 8042750618c0885c
2020-04-29 16:46:35 driver-btm-api.c:1073:init_miner_version: FPGA Version = 0xB013
2020-04-29 16:46:37 eeprom.c:425:check_pattern_test_level: invalid pattern test result. ignore
2020-04-29 16:46:39 eeprom.c:425:check_pattern_test_level: invalid pattern test result. ignore
2020-04-29 16:46:40 eeprom.c:425:check_pattern_test_level: invalid pattern test result. ignore
2020-04-29 16:46:40 driver-btm-api.c:705:get_product_id: product_id[0] = 1
2020-04-29 16:46:40 driver-btm-api.c:705:get_product_id: product_id[1] = 1
2020-04-29 16:46:40 driver-btm-api.c:705:get_product_id: product_id[2] = 1
2020-04-29 16:46:40 driver-btm-api.c:1633:get_ccdly_opt: ccdly_opt[0] = 1
2020-04-29 16:46:40 driver-btm-api.c:1633:get_ccdly_opt: ccdly_opt[1] = 1
2020-04-29 16:46:40 driver-btm-api.c:1633:get_ccdly_opt: ccdly_opt[2] = 1
2020-04-29 16:46:40 driver-btm-api.c:1877:bitmain_board_init: g_ccdly_opt = 1
2020-04-29 16:46:40 driver-btm-api.c:644:_set_project_type: project:2
2020-04-29 16:46:40 driver-btm-api.c:674:_set_project_type: Project type: Antminer T17
2020-04-29 16:46:40 driver-btm-api.c:685:dump_pcb_bom_version: Chain [0] PCB Version: 0x0100
2020-04-29 16:46:40 driver-btm-api.c:686:dump_pcb_bom_version: Chain [0] BOM Version: 0x0100
2020-04-29 16:46:40 driver-btm-api.c:685:dump_pcb_bom_version: Chain [1] PCB Version: 0x0100
2020-04-29 16:46:40 driver-btm-api.c:686:dump_pcb_bom_version: Chain [1] BOM Version: 0x0100
2020-04-29 16:46:40 driver-btm-api.c:685:dump_pcb_bom_version: Chain [2] PCB Version: 0x0100
2020-04-29 16:46:40 driver-btm-api.c:686:dump_pcb_bom_version: Chain [2] BOM Version: 0x0100
2020-04-29 16:46:42 driver-btm-api.c:1897:bitmain_board_init: Fan check passed.
2020-04-29 16:46:42 register.c:283:get_register: !!! reg crc error
2020-04-29 16:46:44 board.c:36:jump_and_app_check_restore_pic: chain[0] PIC jump to app
2020-04-29 16:46:48 board.c:40:jump_and_app_check_restore_pic: Check chain[0] PIC fw version=0xb9
2020-04-29 16:46:49 board.c:36:jump_and_app_check_restore_pic: chain[1] PIC jump to app
2020-04-29 16:46:53 board.c:40:jump_and_app_check_restore_pic: Check chain[1] PIC fw version=0xb9
2020-04-29 16:46:55 board.c:36:jump_and_app_check_restore_pic: chain[2] PIC jump to app
2020-04-29 16:46:58 board.c:40:jump_and_app_check_restore_pic: Check chain[2] PIC fw version=0xb9
2020-04-29 16:46:58 thread.c:784:create_pic_heart_beat_thread: create thread
2020-04-29 16:46:58 power_api.c:55:power_init: power init ...
2020-04-29 16:46:58 driver-btm-api.c:1907:bitmain_board_init: Enter 30s sleep to make sure power release finish.
2020-04-29 16:47:30 power_api.c:232:set_iic_power_to_highest_voltage: setting to voltage: 17.00 ...
2020-04-29 16:47:36 power_api.c:124:check_voltage_multi: retry time: 0
2020-04-29 16:47:38 power_api.c:86:get_average_voltage: chain[0], voltage is: 17.903789
2020-04-29 16:47:39 power_api.c:86:get_average_voltage: chain[1], voltage is: 17.352715
2020-04-29 16:47:41 power_api.c:86:get_average_voltage: chain[2], voltage is: 17.211885
2020-04-29 16:47:41 power_api.c:97:get_average_voltage: aveage voltage is: 17.489463
2020-04-29 16:47:41 power_api.c:182:set_iic_power_by_voltage: now set voltage to : 17.000000
2020-04-29 16:47:41 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[0]: chip baud = 115200, chip_divider = 26
2020-04-29 16:47:41 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[1]: chip baud = 115200, chip_divider = 26
2020-04-29 16:47:41 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[2]: chip baud = 115200, chip_divider = 26
2020-04-29 16:47:41 uart.c:80:set_baud: set fpga_baud = 115200, fpga_divider = 26
2020-04-29 16:47:53 driver-btm-api.c:1010:check_asic_number_with_power_on: Chain[0]: find 30 asic, times 0
2020-04-29 16:48:03 driver-btm-api.c:1010:check_asic_number_with_power_on: Chain[1]: find 30 asic, times 0
2020-04-29 16:48:13 driver-btm-api.c:1010:check_asic_number_with_power_on: Chain[2]: find 30 asic, times 0
2020-04-29 16:48:16 driver-btm-api.c:348:set_order_clock: chain[0]: set order clock, stragegy 3 clock_en=0x1
2020-04-29 16:48:16 driver-btm-api.c:348:set_order_clock: chain[1]: set order clock, stragegy 3 clock_en=0x1
2020-04-29 16:48:17 driver-btm-api.c:348:set_order_clock: chain[2]: set order clock, stragegy 3 clock_en=0x1
2020-04-29 16:48:17 driver-hash-chip.c:490:set_clock_delay_control: core_data = 0xb4
2020-04-29 16:48:17 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[0]: chip baud = 3000000, chip_divider = 0
2020-04-29 16:48:17 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[1]: chip baud = 3000000, chip_divider = 0
2020-04-29 16:48:17 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[2]: chip baud = 3000000, chip_divider = 0
2020-04-29 16:48:17 uart.c:80:set_baud: set fpga_baud = 3000000, fpga_divider = 0
2020-04-29 16:48:17 driver-btm-api.c:1660:check_clock_counter: freq 50 clock_counter_limit 6
2020-04-29 16:48:17 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[0]: chip baud = 115200, chip_divider = 26
2020-04-29 16:48:17 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[1]: chip baud = 115200, chip_divider = 26
2020-04-29 16:48:17 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[2]: chip baud = 115200, chip_divider = 26
2020-04-29 16:48:17 uart.c:80:set_baud: set fpga_baud = 115200, fpga_divider = 26
2020-04-29 16:48:17 voltage[0] = 1710
2020-04-29 16:48:17 voltage[1] = 1710
2020-04-29 16:48:17 voltage[2] = 1710
2020-04-29 16:48:17 power_api.c:140:set_working_voltage: working_voltage = 17.100000
2020-04-29 16:48:19 temperature.c:282:calibrate_temp_sensor_one_chain: Temperature sensor calibration: chain 0 success.
2020-04-29 16:48:20 temperature.c:282:calibrate_temp_sensor_one_chain: Temperature sensor calibration: chain 1 success.
2020-04-29 16:48:22 temperature.c:282:calibrate_temp_sensor_one_chain: Temperature sensor calibration: chain 2 success.
2020-04-29 16:48:22 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[0]: chip baud = 6000000, chip_divider = 7
2020-04-29 16:48:22 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[1]: chip baud = 6000000, chip_divider = 7
2020-04-29 16:48:22 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[2]: chip baud = 6000000, chip_divider = 7
2020-04-29 16:48:22 uart.c:80:set_baud: set fpga_baud = 6000000, fpga_divider = 3
2020-04-29 16:48:23 driver-btm-api.c:248:check_bringup_temp: Bring up temperature is 19
2020-04-29 16:48:23 thread.c:804:create_check_miner_status_thread: create thread
2020-04-29 16:48:23 thread.c:794:create_set_miner_status_thread: create thread
2020-04-29 16:48:23 driver-btm-api.c:581:calculate_timeout: dev->timeout = 392
2020-04-29 16:48:23 thread.c:779:create_temperature_monitor_thread: create thread
2020-04-29 16:48:23 freq_tuning.c:154:freq_tuning_get_max_freq: Max freq of tuning is 760
2020-04-29 16:48:23 power_api.c:379:slowly_set_iic_power_to_custom_voltage: slowly setting to voltage: 18.00 ...
2020-04-29 16:48:56 power_api.c:124:check_voltage_multi: retry time: 0
2020-04-29 16:48:58 power_api.c:86:get_average_voltage: chain[0], voltage is: 18.142588
2020-04-29 16:48:59 power_api.c:86:get_average_voltage: chain[1], voltage is: 18.148711
2020-04-29 16:49:01 power_api.c:86:get_average_voltage: chain[2], voltage is: 18.271172
2020-04-29 16:49:01 power_api.c:97:get_average_voltage: aveage voltage is: 18.187490
2020-04-29 16:49:01 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 42 set refdiv: 2, fbdiv: 168, postdiv1: 7, postdiv2: 7, usr divider: 1
2020-04-29 16:49:01 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 50 set refdiv: 2, fbdiv: 168, postdiv1: 7, postdiv2: 6, usr divider: 1
2020-04-29 16:49:01 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 60 set refdiv: 2, fbdiv: 168, postdiv1: 7, postdiv2: 5, usr divider: 1
2020-04-29 16:49:01 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 75 set refdiv: 2, fbdiv: 168, postdiv1: 7, postdiv2: 4, usr divider: 1
2020-04-29 16:49:02 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 100 set refdiv: 2, fbdiv: 168, postdiv1: 7, postdiv2: 3, usr divider: 1
2020-04-29 16:49:02 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 150 set refdiv: 2, fbdiv: 168, postdiv1: 7, postdiv2: 2, usr divider: 1
2020-04-29 16:49:02 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 300 set refdiv: 2, fbdiv: 168, postdiv1: 7, postdiv2: 1, usr divider: 1
2020-04-29 16:49:02 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 350 set refdiv: 2, fbdiv: 168, postdiv1: 6, postdiv2: 1, usr divider: 1
2020-04-29 16:49:02 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 420 set refdiv: 2, fbdiv: 168, postdiv1: 5, postdiv2: 1, usr divider: 1
2020-04-29 16:49:02 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 525 set refdiv: 2, fbdiv: 168, postdiv1: 4, postdiv2: 1, usr divider: 1
2020-04-29 16:49:02 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 700 set refdiv: 2, fbdiv: 168, postdiv1: 3, postdiv2: 1, usr divider: 1
2020-04-29 16:49:02 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 41 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 7, usr divider: 1
2020-04-29 16:49:02 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 47 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 6, usr divider: 1
2020-04-29 16:49:02 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 57 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 5, usr divider: 1
2020-04-29 16:49:03 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 71 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 4, usr divider: 1
2020-04-29 16:49:03 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 95 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 3, usr divider: 1
2020-04-29 16:49:03 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 143 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 2, usr divider: 1
2020-04-29 16:49:03 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 287 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 1, usr divider: 1
2020-04-29 16:49:03 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 335 set refdiv: 2, fbdiv: 161, postdiv1: 6, postdiv2: 1, usr divider: 1
2020-04-29 16:49:03 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 402 set refdiv: 2, fbdiv: 161, postdiv1: 5, postdiv2: 1, usr divider: 1
2020-04-29 16:49:03 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 503 set refdiv: 2, fbdiv: 161, postdiv1: 4, postdiv2: 1, usr divider: 1
2020-04-29 16:49:03 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 670 set refdiv: 2, fbdiv: 161, postdiv1: 3, postdiv2: 1, usr divider: 1
2020-04-29 16:49:03 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 41 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 7, usr divider: 1
2020-04-29 16:49:04 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 47 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 6, usr divider: 1
2020-04-29 16:49:04 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 57 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 5, usr divider: 1
2020-04-29 16:49:04 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 71 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 4, usr divider: 1
2020-04-29 16:49:04 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 95 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 3, usr divider: 1
2020-04-29 16:49:04 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 143 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 2, usr divider: 1
2020-04-29 16:49:04 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 287 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 1, usr divider: 1
2020-04-29 16:49:04 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 335 set refdiv: 2, fbdiv: 161, postdiv1: 6, postdiv2: 1, usr divider: 1
2020-04-29 16:49:04 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 402 set refdiv: 2, fbdiv: 161, postdiv1: 5, postdiv2: 1, usr divider: 1
2020-04-29 16:49:04 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 503 set refdiv: 2, fbdiv: 161, postdiv1: 4, postdiv2: 1, usr divider: 1
2020-04-29 16:49:04 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 670 set refdiv: 2, fbdiv: 161, postdiv1: 3, postdiv2: 1, usr divider: 1
2020-04-29 16:49:05 driver-btm-api.c:612:set_timeout: freq 700 final timeout=168
2020-04-29 16:49:05 power_api.c:146:set_higher_voltage: higher_voltage = 18.000000
2020-04-29 16:49:05 power_api.c:428:slowly_set_iic_power_to_higher_voltage: slowly setting to voltage: 18.00 ...
2020-04-29 16:49:29 power_api.c:124:check_voltage_multi: retry time: 0
2020-04-29 16:49:31 power_api.c:86:get_average_voltage: chain[0], voltage is: 18.154834
2020-04-29 16:49:32 power_api.c:86:get_average_voltage: chain[1], voltage is: 18.130342
2020-04-29 16:49:34 power_api.c:86:get_average_voltage: chain[2], voltage is: 18.246679
2020-04-29 16:49:34 power_api.c:97:get_average_voltage: aveage voltage is: 18.177285
2020-04-29 16:49:34 frequency.c:540:get_current_min_freq: current min freq 670
2020-04-29 16:49:34 driver-btm-api.c:1660:check_clock_counter: freq 670 clock_counter_limit 85
2020-04-29 16:49:35 register.c:966:register_process_asic_response: Get another asic response: chain = 2, asic = 26
2020-04-29 16:49:35 register.c:1416:quick_dump_core_hash_clock_counter: bad clock counter. chain = 0, asic = 20, core = 105, found 1, clock counter 0x00000000
2020-04-29 16:49:35 driver-btm-api.c:2097:bitmain_soc_init: clock count check failed after retry, wait for hash rate protect later.
2020-04-29 16:49:35 thread.c:799:create_check_system_status_thread: create thread
2020-04-29 16:49:36 driver-btm-api.c:2113:bitmain_soc_init: Init done!
2020-04-29 16:49:36 driver-btm-api.c:201:set_miner_status: STATUS_INIT
2020-04-29 16:49:40 driver-btm-api.c:201:set_miner_status: STATUS_OKAY
2020-04-29 16:49:50 driver-btm-api.c:1293:dhash_chip_send_job: Version num 4
2020-04-29 16:49:54 thread.c:382:check_working_voltage: current PCB min temperature is 43
2020-04-29 16:49:54 thread.c:383:check_working_voltage: current voltage is 18.00V, recovery to 17.10V
2020-04-29 16:49:54 power_api.c:397:slowly_set_iic_power_to_working_voltage: slowly setting to voltage: 17.10 ...
2020-04-29 16:50:28 power_api.c:124:check_voltage_multi: retry time: 0
2020-04-29 16:50:30 power_api.c:86:get_average_voltage: chain[0], voltage is: 17.211885
2020-04-29 16:50:31 power_api.c:86:get_average_voltage: chain[1], voltage is: 17.175146
2020-04-29 16:50:33 power_api.c:86:get_average_voltage: chain[2], voltage is: 17.309853
2020-04-29 16:50:33 power_api.c:97:get_average_voltage: aveage voltage is: 17.232295
2020-04-29 16:55:32 thread.c:422:is_zero_nonce_happened: chain_nonce[0] = 17383
2020-04-29 16:55:32 thread.c:422:is_zero_nonce_happened: chain_nonce[1] = 16885
2020-04-29 16:55:32 thread.c:422:is_zero_nonce_happened: chain_nonce[2] = 14342
2020-04-29 16:55:32 thread.c:478:clear_zero_nonce_mark: 0 nonce protect succeed.
2020-04-29 17:20:33 thread.c:204:calc_hashrate_avg: avg rate is 39133.01 in 30 mins
2020-04-29 17:20:33 temperature.c:450:temp_statistics_show: pcb temp 41~56 chip temp 62~79
2020-04-29 17:20:33 thread.c:285:check_hashrate: latest avg rate < 0.98......
2020-04-29 17:20:33 thread.c:286:check_hashrate: current PCB min temperature 41
2020-04-29 17:20:33 thread.c:287:check_hashrate: current voltage is 17.10V, working voltage is 17.10V
2020-04-29 17:20:33 thread.c:318:check_hashrate: high temp, increase voltage 0.1V/0.2V to 17.20V
2020-04-29 17:20:33 driver-btm-api.c:2124:bitmain_reopen_core: reopen_core start!
2020-04-29 17:20:40 driver-btm-api.c:1067:init_miner_version: miner ID : 8042750618c0885c
2020-04-29 17:20:40 driver-btm-api.c:1073:init_miner_version: FPGA Version = 0xB013
2020-04-29 17:20:41 chain = 0, mode = 0, load_done = false.
2020-04-29 17:20:41 chain = 1, mode = 0, load_done = false.
2020-04-29 17:20:41 chain = 2, mode = 0, load_done = false.
2020-04-29 17:20:42 chain = 0, mode = 0, load_done = false.
2020-04-29 17:20:42 chain = 1, mode = 0, load_done = false.
2020-04-29 17:20:42 chain = 2, mode = 0, load_done = false.
2020-04-29 17:20:42 eeprom.c:425:check_pattern_test_level: invalid pattern test result. ignore
2020-04-29 17:20:43 chain = 0, mode = 0, load_done = false.
2020-04-29 17:20:43 chain = 1, mode = 0, load_done = false.
2020-04-29 17:20:43 chain = 2, mode = 0, load_done = false.
2020-04-29 17:20:44 chain = 0, mode = 0, load_done = false.
2020-04-29 17:20:44 chain = 1, mode = 0, load_done = false.
2020-04-29 17:20:44 chain = 2, mode = 0, load_done = false.
2020-04-29 17:20:44 eeprom.c:425:check_pattern_test_level: invalid pattern test result. ignore
2020-04-29 17:20:45 chain = 0, mode = 0, load_done = false.
2020-04-29 17:20:45 chain = 1, mode = 0, load_done = false.
2020-04-29 17:20:45 chain = 2, mode = 0, load_done = false.
2020-04-29 17:20:46 eeprom.c:425:check_pattern_test_level: invalid pattern test result. ignore
2020-04-29 17:20:46 driver-btm-api.c:705:get_product_id: product_id[0] = 1
2020-04-29 17:20:46 driver-btm-api.c:705:get_product_id: product_id[1] = 1
2020-04-29 17:20:46 driver-btm-api.c:705:get_product_id: product_id[2] = 1
2020-04-29 17:20:46 driver-btm-api.c:1633:get_ccdly_opt: ccdly_opt[0] = 1
2020-04-29 17:20:46 driver-btm-api.c:1633:get_ccdly_opt: ccdly_opt[1] = 1
2020-04-29 17:20:46 driver-btm-api.c:1633:get_ccdly_opt: ccdly_opt[2] = 1
2020-04-29 17:20:46 driver-btm-api.c:1877:bitmain_board_init: g_ccdly_opt = 1
2020-04-29 17:20:46 driver-btm-api.c:644:_set_project_type: project:2
2020-04-29 17:20:46 driver-btm-api.c:674:_set_project_type: Project type: Antminer T17
2020-04-29 17:20:46 driver-btm-api.c:685:dump_pcb_bom_version: Chain [0] PCB Version: 0x0100
2020-04-29 17:20:46 driver-btm-api.c:686:dump_pcb_bom_version: Chain [0] BOM Version: 0x0100
2020-04-29 17:20:46 driver-btm-api.c:685:dump_pcb_bom_version: Chain [1] PCB Version: 0x0100
2020-04-29 17:20:46 driver-btm-api.c:686:dump_pcb_bom_version: Chain [1] BOM Version: 0x0100
2020-04-29 17:20:46 driver-btm-api.c:685:dump_pcb_bom_version: Chain [2] PCB Version: 0x0100
2020-04-29 17:20:46 driver-btm-api.c:686:dump_pcb_bom_version: Chain [2] BOM Version: 0x0100
2020-04-29 17:20:48 driver-btm-api.c:1897:bitmain_board_init: Fan check passed.
[color=red][b]2020-04-29 17:20:49 register.c:283:get_register: !!! reg crc error[/b][/color]
2020-04-29 17:20:51 board.c:36:jump_and_app_check_restore_pic: chain[0] PIC jump to app
2020-04-29 17:20:54 board.c:40:jump_and_app_check_restore_pic: Check chain[0] PIC fw version=0xb9
2020-04-29 17:20:56 board.c:36:jump_and_app_check_restore_pic: chain[1] PIC jump to app
2020-04-29 17:21:00 board.c:40:jump_and_app_check_restore_pic: Check chain[1] PIC fw version=0xb9
2020-04-29 17:21:03 board.c:36:jump_and_app_check_restore_pic: chain[2] PIC jump to app
2020-04-29 17:21:09 board.c:40:jump_and_app_check_restore_pic: Check chain[2] PIC fw version=0xb9
2020-04-29 17:21:09 power_api.c:55:power_init: power init ...
2020-04-29 17:21:09 driver-btm-api.c:1907:bitmain_board_init: Enter 30s sleep to make sure power release finish.
2020-04-29 17:21:41 power_api.c:232:set_iic_power_to_highest_voltage: setting to voltage: 17.00 ...
2020-04-29 17:21:43 power_api.c:124:check_voltage_multi: retry time: 0
2020-04-29 17:21:44 power_api.c:86:get_average_voltage: chain[0], voltage is: 17.199638
2020-04-29 17:21:46 power_api.c:86:get_average_voltage: chain[1], voltage is: 17.113916
2020-04-29 17:21:48 power_api.c:86:get_average_voltage: chain[2], voltage is: 17.236377
2020-04-29 17:21:48 power_api.c:97:get_average_voltage: aveage voltage is: 17.183310
2020-04-29 17:21:48 power_api.c:182:set_iic_power_by_voltage: now set voltage to : 17.000000
2020-04-29 17:21:48 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[0]: chip baud = 115200, chip_divider = 26
2020-04-29 17:21:48 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[1]: chip baud = 115200, chip_divider = 26
2020-04-29 17:21:48 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[2]: chip baud = 115200, chip_divider = 26
2020-04-29 17:21:48 uart.c:80:set_baud: set fpga_baud = 115200, fpga_divider = 26
2020-04-29 17:21:58 driver-btm-api.c:1010:check_asic_number_with_power_on: Chain[0]: find 29 asic, times 0
2020-04-29 17:22:08 driver-btm-api.c:1010:check_asic_number_with_power_on: Chain[0]: find 30 asic, times 1
2020-04-29 17:22:18 driver-btm-api.c:1010:check_asic_number_with_power_on: Chain[1]: find 30 asic, times 0
2020-04-29 17:22:29 driver-btm-api.c:1010:check_asic_number_with_power_on: Chain[2]: find 30 asic, times 0
2020-04-29 17:22:32 driver-btm-api.c:348:set_order_clock: chain[0]: set order clock, stragegy 3 clock_en=0x1
2020-04-29 17:22:32 driver-btm-api.c:348:set_order_clock: chain[1]: set order clock, stragegy 3 clock_en=0x1
2020-04-29 17:22:32 driver-btm-api.c:348:set_order_clock: chain[2]: set order clock, stragegy 3 clock_en=0x1
2020-04-29 17:22:33 driver-hash-chip.c:490:set_clock_delay_control: core_data = 0xb4
2020-04-29 17:22:33 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[0]: chip baud = 3000000, chip_divider = 0
2020-04-29 17:22:33 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[1]: chip baud = 3000000, chip_divider = 0
2020-04-29 17:22:33 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[2]: chip baud = 3000000, chip_divider = 0
2020-04-29 17:22:33 uart.c:80:set_baud: set fpga_baud = 3000000, fpga_divider = 0
2020-04-29 17:22:33 driver-btm-api.c:1660:check_clock_counter: freq 50 clock_counter_limit 6
2020-04-29 17:22:33 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[0]: chip baud = 115200, chip_divider = 26
2020-04-29 17:22:33 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[1]: chip baud = 115200, chip_divider = 26
2020-04-29 17:22:33 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[2]: chip baud = 115200, chip_divider = 26
2020-04-29 17:22:33 uart.c:80:set_baud: set fpga_baud = 115200, fpga_divider = 26
2020-04-29 17:22:33 voltage[0] = 1710
2020-04-29 17:22:33 voltage[1] = 1710
2020-04-29 17:22:33 voltage[2] = 1710
2020-04-29 17:22:33 power_api.c:140:set_working_voltage: working_voltage = 17.100000
2020-04-29 17:22:35 temperature.c:282:calibrate_temp_sensor_one_chain: Temperature sensor calibration: chain 0 success.
2020-04-29 17:22:36 temperature.c:282:calibrate_temp_sensor_one_chain: Temperature sensor calibration: chain 1 success.
2020-04-29 17:22:37 temperature.c:282:calibrate_temp_sensor_one_chain: Temperature sensor calibration: chain 2 success.
2020-04-29 17:22:37 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[0]: chip baud = 6000000, chip_divider = 7
2020-04-29 17:22:37 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[1]: chip baud = 6000000, chip_divider = 7
2020-04-29 17:22:37 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[2]: chip baud = 6000000, chip_divider = 7
2020-04-29 17:22:37 uart.c:80:set_baud: set fpga_baud = 6000000, fpga_divider = 3
2020-04-29 17:22:39 driver-btm-api.c:248:check_bringup_temp: Bring up temperature is 18
2020-04-29 17:22:39 driver-btm-api.c:581:calculate_timeout: dev->timeout = 392
2020-04-29 17:22:39 power_api.c:379:slowly_set_iic_power_to_custom_voltage: slowly setting to voltage: 18.00 ...
2020-04-29 17:23:15 power_api.c:124:check_voltage_multi: retry time: 0
2020-04-29 17:23:17 power_api.c:86:get_average_voltage: chain[0], voltage is: 18.136465
2020-04-29 17:23:19 power_api.c:86:get_average_voltage: chain[1], voltage is: 18.118095
2020-04-29 17:23:20 power_api.c:86:get_average_voltage: chain[2], voltage is: 18.228310
2020-04-29 17:23:20 power_api.c:97:get_average_voltage: aveage voltage is: 18.160957
2020-04-29 17:23:20 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 42 set refdiv: 2, fbdiv: 168, postdiv1: 7, postdiv2: 7, usr divider: 1
2020-04-29 17:23:21 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 50 set refdiv: 2, fbdiv: 168, postdiv1: 7, postdiv2: 6, usr divider: 1
2020-04-29 17:23:21 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 60 set refdiv: 2, fbdiv: 168, postdiv1: 7, postdiv2: 5, usr divider: 1
2020-04-29 17:23:21 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 75 set refdiv: 2, fbdiv: 168, postdiv1: 7, postdiv2: 4, usr divider: 1
2020-04-29 17:23:21 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 100 set refdiv: 2, fbdiv: 168, postdiv1: 7, postdiv2: 3, usr divider: 1
2020-04-29 17:23:21 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 150 set refdiv: 2, fbdiv: 168, postdiv1: 7, postdiv2: 2, usr divider: 1
2020-04-29 17:23:21 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 300 set refdiv: 2, fbdiv: 168, postdiv1: 7, postdiv2: 1, usr divider: 1
2020-04-29 17:23:21 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 350 set refdiv: 2, fbdiv: 168, postdiv1: 6, postdiv2: 1, usr divider: 1
2020-04-29 17:23:21 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 420 set refdiv: 2, fbdiv: 168, postdiv1: 5, postdiv2: 1, usr divider: 1
2020-04-29 17:23:21 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 525 set refdiv: 2, fbdiv: 168, postdiv1: 4, postdiv2: 1, usr divider: 1
2020-04-29 17:23:22 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 700 set refdiv: 2, fbdiv: 168, postdiv1: 3, postdiv2: 1, usr divider: 1
2020-04-29 17:23:22 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 41 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 7, usr divider: 1
2020-04-29 17:23:22 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 47 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 6, usr divider: 1
2020-04-29 17:23:22 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 57 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 5, usr divider: 1
2020-04-29 17:23:22 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 71 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 4, usr divider: 1
2020-04-29 17:23:22 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 95 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 3, usr divider: 1
2020-04-29 17:23:22 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 143 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 2, usr divider: 1
2020-04-29 17:23:22 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 287 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 1, usr divider: 1
2020-04-29 17:23:22 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 335 set refdiv: 2, fbdiv: 161, postdiv1: 6, postdiv2: 1, usr divider: 1
2020-04-29 17:23:22 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 402 set refdiv: 2, fbdiv: 161, postdiv1: 5, postdiv2: 1, usr divider: 1
2020-04-29 17:23:23 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 503 set refdiv: 2, fbdiv: 161, postdiv1: 4, postdiv2: 1, usr divider: 1
2020-04-29 17:23:23 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 670 set refdiv: 2, fbdiv: 161, postdiv1: 3, postdiv2: 1, usr divider: 1
2020-04-29 17:23:23 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 41 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 7, usr divider: 1
2020-04-29 17:23:23 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 47 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 6, usr divider: 1
2020-04-29 17:23:23 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 57 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 5, usr divider: 1
2020-04-29 17:23:23 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 71 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 4, usr divider: 1
2020-04-29 17:23:23 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 95 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 3, usr divider: 1
2020-04-29 17:23:23 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 143 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 2, usr divider: 1
2020-04-29 17:23:23 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 287 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 1, usr divider: 1
2020-04-29 17:23:24 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 335 set refdiv: 2, fbdiv: 161, postdiv1: 6, postdiv2: 1, usr divider: 1
2020-04-29 17:23:24 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 402 set refdiv: 2, fbdiv: 161, postdiv1: 5, postdiv2: 1, usr divider: 1
2020-04-29 17:23:24 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 503 set refdiv: 2, fbdiv: 161, postdiv1: 4, postdiv2: 1, usr divider: 1
2020-04-29 17:23:24 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 670 set refdiv: 2, fbdiv: 161, postdiv1: 3, postdiv2: 1, usr divider: 1
2020-04-29 17:23:24 driver-btm-api.c:612:set_timeout: freq 700 final timeout=168
2020-04-29 17:23:24 power_api.c:146:set_higher_voltage: higher_voltage = 18.000000
2020-04-29 17:23:24 power_api.c:428:slowly_set_iic_power_to_higher_voltage: slowly setting to voltage: 18.00 ...
2020-04-29 17:23:48 power_api.c:124:check_voltage_multi: retry time: 0
2020-04-29 17:23:50 power_api.c:86:get_average_voltage: chain[0], voltage is: 18.118095
2020-04-29 17:23:52 power_api.c:86:get_average_voltage: chain[1], voltage is: 18.118095
2020-04-29 17:23:54 power_api.c:86:get_average_voltage: chain[2], voltage is: 18.240556
2020-04-29 17:23:54 power_api.c:97:get_average_voltage: aveage voltage is: 18.158916
2020-04-29 17:23:54 driver-btm-api.c:2186:bitmain_reopen_core: reopen_core done!
2020-04-29 17:23:54 power_api.c:379:slowly_set_iic_power_to_custom_voltage: slowly setting to voltage: 17.20 ...
2020-04-29 17:24:34 power_api.c:124:check_voltage_multi: retry time: 0
2020-04-29 17:24:36 power_api.c:86:get_average_voltage: chain[0], voltage is: 17.303730
2020-04-29 17:24:38 power_api.c:86:get_average_voltage: chain[1], voltage is: 17.273115
2020-04-29 17:24:40 power_api.c:86:get_average_voltage: chain[2], voltage is: 17.401699
2020-04-29 17:24:40 power_api.c:97:get_average_voltage: aveage voltage is: 17.326181
2020-04-29 17:24:40 power_api.c:140:set_working_voltage: working_voltage = 17.200001
2020-04-29 17:29:39 thread.c:422:is_zero_nonce_happened: chain_nonce[0] = 112803
2020-04-29 17:29:39 thread.c:422:is_zero_nonce_happened: chain_nonce[1] = 107268
2020-04-29 17:29:39 thread.c:422:is_zero_nonce_happened: chain_nonce[2] = 91851
2020-04-29 17:54:40 thread.c:204:calc_hashrate_avg: avg rate is 39117.71 in 30 mins
2020-04-29 17:54:40 temperature.c:450:temp_statistics_show: pcb temp 42~56 chip temp 63~80
2020-04-29 17:54:40 thread.c:285:check_hashrate: latest avg rate < 0.98......
2020-04-29 17:54:40 thread.c:286:check_hashrate: current PCB min temperature 42
2020-04-29 17:54:40 thread.c:287:check_hashrate: current voltage is 17.20V, working voltage is 17.20V
2020-04-29 17:54:40 thread.c:312:check_hashrate: high temp, voltage has already increased 0.1V/0.2V
2020-04-29 18:24:41 thread.c:204:calc_hashrate_avg: avg rate is 39320.85 in 30 mins
2020-04-29 18:24:41 temperature.c:450:temp_statistics_show: pcb temp 42~57 chip temp 63~81
2020-04-29 18:54:42 thread.c:204:calc_hashrate_avg: avg rate is 39045.15 in 30 mins
2020-04-29 18:54:42 temperature.c:450:temp_statistics_show: pcb temp 42~57 chip temp 63~80
2020-04-29 18:54:42 thread.c:285:check_hashrate: latest avg rate < 0.98......
2020-04-29 18:54:42 thread.c:286:check_hashrate: current PCB min temperature 42
2020-04-29 18:54:42 thread.c:287:check_hashrate: current voltage is 17.20V, working voltage is 17.20V
2020-04-29 18:54:42 thread.c:312:check_hashrate: high temp, voltage has already increased 0.1V/0.2V
2020-04-29 19:24:44 thread.c:204:calc_hashrate_avg: avg rate is 39035.09 in 30 mins
2020-04-29 19:24:44 temperature.c:450:temp_statistics_show: pcb temp 42~56 chip temp 63~81
2020-04-29 19:24:44 thread.c:285:check_hashrate: latest avg rate < 0.98......
2020-04-29 19:24:44 thread.c:286:check_hashrate: current PCB min temperature 42
2020-04-29 19:24:44 thread.c:287:check_hashrate: current voltage is 17.20V, working voltage is 17.20V
2020-04-29 19:24:44 thread.c:312:check_hashrate: high temp, voltage has already increased 0.1V/0.2V
2020-04-29 19:54:45 thread.c:204:calc_hashrate_avg: avg rate is 38942.28 in 30 mins
2020-04-29 19:54:45 temperature.c:450:temp_statistics_show: pcb temp 42~57 chip temp 63~81
2020-04-29 19:54:45 thread.c:285:check_hashrate: latest avg rate < 0.98......
2020-04-29 19:54:45 thread.c:286:check_hashrate: current PCB min temperature 42
2020-04-29 19:54:45 thread.c:287:check_hashrate: current voltage is 17.20V, working voltage is 17.20V
2020-04-29 19:54:45 thread.c:312:check_hashrate: high temp, voltage has already increased 0.1V/0.2V
2020-04-29 20:24:46 thread.c:204:calc_hashrate_avg: avg rate is 39099.22 in 30 mins
2020-04-29 20:24:46 temperature.c:450:temp_statistics_show: pcb temp 43~57 chip temp 63~80
2020-04-29 20:24:46 thread.c:285:check_hashrate: latest avg rate < 0.98......
2020-04-29 20:24:46 thread.c:286:check_hashrate: current PCB min temperature 43
2020-04-29 20:24:46 thread.c:287:check_hashrate: current voltage is 17.20V, working voltage is 17.20V
2020-04-29 20:24:46 thread.c:312:check_hashrate: high temp, voltage has already increased 0.1V/0.2V
2020-04-29 20:54:48 thread.c:204:calc_hashrate_avg: avg rate is 39243.94 in 30 mins
2020-04-29 20:54:48 temperature.c:450:temp_statistics_show: pcb temp 43~57 chip temp 64~80
2020-04-29 21:24:49 thread.c:204:calc_hashrate_avg: avg rate is 39079.01 in 30 mins
2020-04-29 21:24:49 temperature.c:450:temp_statistics_show: pcb temp 43~57 chip temp 64~80
2020-04-29 21:24:49 thread.c:285:check_hashrate: latest avg rate < 0.98......
2020-04-29 21:24:49 thread.c:286:check_hashrate: current PCB min temperature 43
2020-04-29 21:24:49 thread.c:287:check_hashrate: current voltage is 17.20V, working voltage is 17.20V
2020-04-29 21:24:49 thread.c:312:check_hashrate: high temp, voltage has already increased 0.1V/0.2V
2020-04-29 21:54:50 thread.c:204:calc_hashrate_avg: avg rate is 39195.28 in 30 mins
2020-04-29 21:54:50 temperature.c:450:temp_statistics_show: pcb temp 43~57 chip temp 64~80
2020-04-29 21:54:50 thread.c:285:check_hashrate: latest avg rate < 0.98......
2020-04-29 21:54:50 thread.c:286:check_hashrate: current PCB min temperature 43
2020-04-29 21:54:50 thread.c:287:check_hashrate: current voltage is 17.20V, working voltage is 17.20V
2020-04-29 21:54:50 thread.c:312:check_hashrate: high temp, voltage has already increased 0.1V/0.2V
2020-04-29 22:24:52 thread.c:204:calc_hashrate_avg: avg rate is 39376.48 in 30 mins
2020-04-29 22:24:52 temperature.c:450:temp_statistics_show: pcb temp 44~56 chip temp 66~80
2020-04-29 22:54:53 thread.c:204:calc_hashrate_avg: avg rate is 39147.83 in 30 mins
2020-04-29 22:54:53 temperature.c:450:temp_statistics_show: pcb temp 43~55 chip temp 64~79
2020-04-29 22:54:53 thread.c:285:check_hashrate: latest avg rate < 0.98......
2020-04-29 22:54:53 thread.c:286:check_hashrate: current PCB min temperature 43
2020-04-29 22:54:53 thread.c:287:check_hashrate: current voltage is 17.20V, working voltage is 17.20V
2020-04-29 22:54:53 thread.c:312:check_hashrate: high temp, voltage has already increased 0.1V/0.2V
2020-04-29 23:24:54 thread.c:204:calc_hashrate_avg: avg rate is 39294.97 in 30 mins
2020-04-29 23:24:54 temperature.c:450:temp_statistics_show: pcb temp 43~57 chip temp 64~80
2020-04-29 23:54:55 thread.c:204:calc_hashrate_avg: avg rate is 38966.09 in 30 mins
2020-04-29 23:54:55 temperature.c:450:temp_statistics_show: pcb temp 42~56 chip temp 63~79
2020-04-29 23:54:55 thread.c:285:check_hashrate: latest avg rate < 0.98......
2020-04-29 23:54:55 thread.c:286:check_hashrate: current PCB min temperature 42
2020-04-29 23:54:55 thread.c:287:check_hashrate: current voltage is 17.20V, working voltage is 17.20V
2020-04-29 23:54:55 thread.c:312:check_hashrate: high temp, voltage has already increased 0.1V/0.2V
Pictures of the Miner Status: https://drive.google.com/file/d/1o0hf-1KdEfxtyAs3ewfT3x7gPbpxzBXL/view?usp=sharing https://drive.google.com/open?id=1vJ8PzxGsONfzU43RouEbhy9a4RUeB9Mw Things to Note in the Kernel Log: 1.) 2020-04-29 16:49:35 register.c:966:register_process_asic_response: Get another asic response: chain = 2, asic = 26
2020-04-29 16:49:35 register.c:1416:quick_dump_core_hash_clock_counter: bad clock counter. chain = 0, asic = 20, core = 105, found 1, clock counter 0x00000000
2020-04-29 16:49:35 driver-btm-api.c:2097:bitmain_soc_init: clock count check failed after retry, wait for hash rate protect later.
2.) 2020-04-29 17:20:49 register.c:283:get_register: !!! reg crc error
3.) 2020-04-29 17:20:33 thread.c:318:check_hashrate: high temp, increase voltage 0.1V/0.2V to 17.20V
2020-04-29 17:20:33 driver-btm-api.c:2124:bitmain_reopen_core: reopen_core start!
- (Continually shows until it finally reboots)
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: mysticbitcoin on May 03, 2020, 03:16:01 AM
Ok, So it's official the 3rd Hash Board just died (Chain [2]). Here is the slow death of the Hash Board, starts operating at half hash. after this: Kernel Log: Booting Linux on physical CPU 0x0
Linux version 4.6.0-xilinx-gff8137b-dirty (lzq@armdev2) (gcc version 4.8.3 20140320 (prerelease) (Sourcery CodeBench Lite 2014.05-23) ) #25 SMP PREEMPT Fri Nov 23 15:30:52 CST 2018
CPU: ARMv7 Processor [413fc090] revision 0 (ARMv7), cr=18c5387d
CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
Machine model: Xilinx Zynq
cma: Reserved 16 MiB at 0x0e000000
Memory policy: Data cache writealloc
On node 0 totalpages: 61440
free_area_init_node: node 0, pgdat c0b39280, node_mem_map cde10000
Normal zone: 480 pages used for memmap
Normal zone: 0 pages reserved
Normal zone: 61440 pages, LIFO batch:15
percpu: Embedded 12 pages/cpu @cddf1000 s19776 r8192 d21184 u49152
pcpu-alloc: s19776 r8192 d21184 u49152 alloc=12*4096
pcpu-alloc: [0] 0 [0] 1
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 60960
Kernel command line: mem=240M console=ttyPS0,115200 ramdisk_size=33554432 root=/dev/ram rw earlyprintk
PID hash table entries: 1024 (order: 0, 4096 bytes)
Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
Memory: 203756K/245760K available (6345K kernel code, 231K rwdata, 1896K rodata, 1024K init, 223K bss, 25620K reserved, 16384K cma-reserved, 0K highmem)
Virtual kernel memory layout:
vector : 0xffff0000 - 0xffff1000 ( 4 kB)
fixmap : 0xffc00000 - 0xfff00000 (3072 kB)
vmalloc : 0xcf800000 - 0xff800000 ( 768 MB)
lowmem : 0xc0000000 - 0xcf000000 ( 240 MB)
pkmap : 0xbfe00000 - 0xc0000000 ( 2 MB)
modules : 0xbf000000 - 0xbfe00000 ( 14 MB)
.text : 0xc0008000 - 0xc090c424 (9234 kB)
.init : 0xc0a00000 - 0xc0b00000 (1024 kB)
.data : 0xc0b00000 - 0xc0b39fe0 ( 232 kB)
.bss : 0xc0b39fe0 - 0xc0b71c28 ( 224 kB)
Preemptible hierarchical RCU implementation.
Build-time adjustment of leaf fanout to 32.
RCU restricting CPUs from NR_CPUS=4 to nr_cpu_ids=2.
RCU: Adjusting geometry for rcu_fanout_leaf=32, nr_cpu_ids=2
NR_IRQS:16 nr_irqs:16 16
efuse mapped to cf800000
ps7-slcr mapped to cf802000
L2C: platform modifies aux control register: 0x72360000 -> 0x72760000
L2C: DT/platform modifies aux control register: 0x72360000 -> 0x72760000
L2C-310 erratum 769419 enabled
L2C-310 enabling early BRESP for Cortex-A9
L2C-310 full line of zeros enabled for Cortex-A9
L2C-310 ID prefetch enabled, offset 1 lines
L2C-310 dynamic clock gating enabled, standby mode enabled
L2C-310 cache controller enabled, 8 ways, 512 kB
L2C-310: CACHE_ID 0x410000c8, AUX_CTRL 0x76760001
zynq_clock_init: clkc starts at cf802100
Zynq clock init
sched_clock: 64 bits at 333MHz, resolution 3ns, wraps every 4398046511103ns
clocksource: arm_global_timer: mask: 0xffffffffffffffff max_cycles: 0x4ce07af025, max_idle_ns: 440795209040 ns
Switching to timer-based delay loop, resolution 3ns
clocksource: ttc_clocksource: mask: 0xffff max_cycles: 0xffff, max_idle_ns: 537538477 ns
ps7-ttc #0 at cf80a000, irq=18
Console: colour dummy device 80x30
Calibrating delay loop (skipped), value calculated using timer frequency.. 666.66 BogoMIPS (lpj=3333333)
pid_max: default: 32768 minimum: 301
Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
CPU: Testing write buffer coherency: ok
CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
Setting up static identity map for 0x100000 - 0x100058
CPU1: failed to boot: -1
Brought up 1 CPUs
SMP: Total of 1 processors activated (666.66 BogoMIPS).
CPU: All CPU(s) started in SVC mode.
devtmpfs: initialized
VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4
clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
pinctrl core: initialized pinctrl subsystem
NET: Registered protocol family 16
DMA: preallocated 256 KiB pool for atomic coherent allocations
cpuidle: using governor menu
hw-breakpoint: found 5 (+1 reserved) breakpoint and 1 watchpoint registers.
hw-breakpoint: maximum watchpoint size is 4 bytes.
zynq-ocm f800c000.ps7-ocmc: ZYNQ OCM pool: 256 KiB @ 0xcf880000
vgaarb: loaded
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
media: Linux media interface: v0.10
Linux video capture interface: v2.00
pps_core: LinuxPPS API ver. 1 registered
pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
PTP clock support registered
EDAC MC: Ver: 3.0.0
Advanced Linux Sound Architecture Driver Initialized.
clocksource: Switched to clocksource arm_global_timer
NET: Registered protocol family 2
TCP established hash table entries: 2048 (order: 1, 8192 bytes)
TCP bind hash table entries: 2048 (order: 2, 16384 bytes)
TCP: Hash tables configured (established 2048 bind 2048)
UDP hash table entries: 256 (order: 1, 8192 bytes)
UDP-Lite hash table entries: 256 (order: 1, 8192 bytes)
NET: Registered protocol family 1
RPC: Registered named UNIX socket transport module.
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
PCI: CLS 0 bytes, default 64
Trying to unpack rootfs image as initramfs...
rootfs image is not initramfs (no cpio magic); looks like an initrd
Freeing initrd memory: 12580K (cceb8000 - cdb01000)
hw perfevents: enabled with armv7_cortex_a9 PMU driver, 7 counters available
futex hash table entries: 512 (order: 3, 32768 bytes)
workingset: timestamp_bits=28 max_order=16 bucket_order=0
jffs2: version 2.2. (NAND) (SUMMARY) © 2001-2006 Red Hat, Inc.
io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered (default)
dma-pl330 f8003000.ps7-dma: Loaded driver for PL330 DMAC-241330
dma-pl330 f8003000.ps7-dma: DBUFF-128x8bytes Num_Chans-8 Num_Peri-4 Num_Events-16
e0000000.serial: ttyPS0 at MMIO 0xe0000000 (irq = 158, base_baud = 6249999) is a xuartps
console [ttyPS0] enabled
xdevcfg f8007000.ps7-dev-cfg: ioremap 0xf8007000 to cf86e000
[drm] Initialized drm 1.1.0 20060810
brd: module loaded
loop: module loaded
CAN device driver interface
gpiod_set_value: invalid GPIO
libphy: MACB_mii_bus: probed
macb e000b000.ethernet eth0: Cadence GEM rev 0x00020118 at 0xe000b000 irq 31 (00:0a:35:00:00:00)
Generic PHY e000b000.etherne:00: attached PHY driver [Generic PHY] (mii_bus:phy_addr=e000b000.etherne:00, irq=-1)
e1000e: Intel(R) PRO/1000 Network Driver - 3.2.6-k
e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
ehci-pci: EHCI PCI platform driver
usbcore: registered new interface driver usb-storage
mousedev: PS/2 mouse device common for all mice
i2c /dev entries driver
Xilinx Zynq CpuIdle Driver started
sdhci: Secure Digital Host Controller Interface driver
sdhci: Copyright(c) Pierre Ossman
sdhci-pltfm: SDHCI platform and OF driver helper
mmc0: SDHCI controller on e0100000.ps7-sdio [e0100000.ps7-sdio] using ADMA
ledtrig-cpu: registered to indicate activity on CPUs
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
nand: device found, Manufacturer ID: 0x2c, Chip ID: 0xda
nand: Micron MT29F2G08ABAGAWP
nand: 256 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 128
nand: WARNING: pl35x-nand: the ECC used on your system is too weak compared to the one required by the NAND chip
Bad block table found at page 131008, version 0x01
Bad block table found at page 130944, version 0x01
6 ofpart partitions found on MTD device pl35x-nand
Creating 6 MTD partitions on "pl35x-nand":
0x000000000000-0x000002800000 : "BOOT.bin-env-dts-kernel"
0x000002800000-0x000004800000 : "ramfs"
0x000004800000-0x000005000000 : "configs"
0x000005000000-0x000006000000 : "reserve"
0x000006000000-0x000008000000 : "ramfs-bak"
0x000008000000-0x000010000000 : "reserve1"
NET: Registered protocol family 10
sit: IPv6 over IPv4 tunneling driver
NET: Registered protocol family 17
can: controller area network core (rev 20120528 abi 9)
NET: Registered protocol family 29
can: raw protocol (rev 20120528)
can: broadcast manager protocol (rev 20120528 t)
can: netlink gateway (rev 20130117) max_hops=1
zynq_pm_ioremap: no compatible node found for 'xlnx,zynq-ddrc-a05'
zynq_pm_late_init: Unable to map DDRC IO memory.
Registering SWP/SWPB emulation handler
hctosys: unable to open rtc device (rtc0)
ALSA device list:
No soundcards found.
RAMDISK: gzip image found at block 0
EXT4-fs (ram0): couldn't mount as ext3 due to feature incompatibilities
EXT4-fs (ram0): mounted filesystem without journal. Opts: (null)
VFS: Mounted root (ext4 filesystem) on device 1:0.
devtmpfs: mounted
Freeing unused kernel memory: 1024K (c0a00000 - c0b00000)
EXT4-fs (ram0): re-mounted. Opts: block_validity,delalloc,barrier,user_xattr
random: dd urandom read with 0 bits of entropy available
ubi0: attaching mtd2
ubi0: scanning is finished
ubi0: attached mtd2 (name "configs", size 8 MiB)
ubi0: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
ubi0: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
ubi0: VID header offset: 2048 (aligned 2048), data offset: 4096
ubi0: good PEBs: 64, bad PEBs: 0, corrupted PEBs: 0
ubi0: user volume: 1, internal volumes: 1, max. volumes count: 128
ubi0: max/mean erase counter: 5/2, WL threshold: 4096, image sequence number: 4244297529
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 01559AD8-7B6A-42E6-A3FE-EDF3659527A9, 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: 1052/339, WL threshold: 4096, image sequence number: 4185749592
ubi1: available PEBs: 0, total reserved PEBs: 1020, PEBs reserved for bad PEB handling: 36
ubi1: background thread "ubi_bgt1d" started, PID 720
UBIFS (ubi1:0): background thread "ubifs_bgt1_0" started, PID 723
UBIFS (ubi1:0): recovery needed
UBIFS (ubi1:0): recovery completed
UBIFS (ubi1:0): UBIFS: mounted UBI device 1, volume 0, name "reserve1"
UBIFS (ubi1:0): LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
UBIFS (ubi1:0): FS size: 123039744 bytes (117 MiB, 969 LEBs), journal size 6221824 bytes (5 MiB, 49 LEBs)
UBIFS (ubi1:0): reserved for root: 4952683 bytes (4836 KiB)
UBIFS (ubi1:0): media format: w4/r0 (latest is w4/r0), UUID 4829CF2C-7435-4146-B2FD-0826AAE8443A, small LPT model
IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
macb e000b000.ethernet eth0: unable to generate target frequency: 25000000 Hz
macb e000b000.ethernet eth0: link up (100/Full)
IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
In axi fpga driver!
request_mem_region OK!
AXI fpga dev virtual address is 0xcfb38000
*base_vir_addr = 0xab013
In fpga mem driver!
request_mem_region OK!
fpga mem virtual address is 0xd2000000
random: nonblocking pool is initialized
1970-01-01 00:05:54 driver-btm-api.c:631:init_freq_mode: This is scan-user version
1970-01-01 00:05:54 driver-btm-api.c:1994:bitmain_soc_init: opt_multi_version = 1
1970-01-01 00:05:54 driver-btm-api.c:1995:bitmain_soc_init: opt_bitmain_ab = 1
1970-01-01 00:05:54 driver-btm-api.c:1996:bitmain_soc_init: opt_bitmain_work_mode = 0
1970-01-01 00:05:54 driver-btm-api.c:1997:bitmain_soc_init: Miner compile time: Tue Dec 24 16:13:07 CST 2019 type: Antminer T17
1970-01-01 00:05:54 driver-btm-api.c:1998:bitmain_soc_init: commit version: e93a09b 2019-12-24 16:03:45, build by: lol 2019-12-24 16:19:49
1970-01-01 00:05:54 driver-btm-api.c:1810:show_sn: no SN got, please write SN to /nvdata/sn
1970-01-01 00:05:54 driver-btm-api.c:1135:miner_device_init: Detect 256MB control board of XILINX
1970-01-01 00:05:54 driver-btm-api.c:1083:init_fan_parameter: fan_eft : 0 fan_pwm : 0
1970-01-01 00:05:54 thread.c:789:create_read_nonce_reg_thread: create thread
1970-01-01 00:06:00 driver-btm-api.c:1067:init_miner_version: miner ID : 8042750618c0885c
1970-01-01 00:06:00 driver-btm-api.c:1073:init_miner_version: FPGA Version = 0xB013
1970-01-01 00:06:02 eeprom.c:425:check_pattern_test_level: invalid pattern test result. ignore
1970-01-01 00:06:04 eeprom.c:425:check_pattern_test_level: invalid pattern test result. ignore
1970-01-01 00:06:05 eeprom.c:425:check_pattern_test_level: invalid pattern test result. ignore
1970-01-01 00:06:05 driver-btm-api.c:705:get_product_id: product_id[0] = 1
1970-01-01 00:06:05 driver-btm-api.c:705:get_product_id: product_id[1] = 1
1970-01-01 00:06:05 driver-btm-api.c:705:get_product_id: product_id[2] = 1
1970-01-01 00:06:05 driver-btm-api.c:1633:get_ccdly_opt: ccdly_opt[0] = 1
1970-01-01 00:06:05 driver-btm-api.c:1633:get_ccdly_opt: ccdly_opt[1] = 1
1970-01-01 00:06:05 driver-btm-api.c:1633:get_ccdly_opt: ccdly_opt[2] = 1
1970-01-01 00:06:05 driver-btm-api.c:1877:bitmain_board_init: g_ccdly_opt = 1
1970-01-01 00:06:05 driver-btm-api.c:644:_set_project_type: project:2
1970-01-01 00:06:05 driver-btm-api.c:674:_set_project_type: Project type: Antminer T17
1970-01-01 00:06:05 driver-btm-api.c:685:dump_pcb_bom_version: Chain [0] PCB Version: 0x0100
1970-01-01 00:06:05 driver-btm-api.c:686:dump_pcb_bom_version: Chain [0] BOM Version: 0x0100
1970-01-01 00:06:05 driver-btm-api.c:685:dump_pcb_bom_version: Chain [1] PCB Version: 0x0100
1970-01-01 00:06:05 driver-btm-api.c:686:dump_pcb_bom_version: Chain [1] BOM Version: 0x0100
1970-01-01 00:06:05 driver-btm-api.c:685:dump_pcb_bom_version: Chain [2] PCB Version: 0x0100
1970-01-01 00:06:05 driver-btm-api.c:686:dump_pcb_bom_version: Chain [2] BOM Version: 0x0100
1970-01-01 00:06:07 driver-btm-api.c:1897:bitmain_board_init: Fan check passed.
1970-01-01 00:06:08 register.c:283:get_register: !!! reg crc error
1970-01-01 00:06:09 board.c:36:jump_and_app_check_restore_pic: chain[0] PIC jump to app
1970-01-01 00:06:13 board.c:40:jump_and_app_check_restore_pic: Check chain[0] PIC fw version=0xb9
1970-01-01 00:06:14 board.c:36:jump_and_app_check_restore_pic: chain[1] PIC jump to app
1970-01-01 00:06:18 board.c:40:jump_and_app_check_restore_pic: Check chain[1] PIC fw version=0xb9
1970-01-01 00:06:20 board.c:36:jump_and_app_check_restore_pic: chain[2] PIC jump to app
1970-01-01 00:06:23 board.c:40:jump_and_app_check_restore_pic: Check chain[2] PIC fw version=0xb9
1970-01-01 00:06:23 thread.c:784:create_pic_heart_beat_thread: create thread
1970-01-01 00:06:23 power_api.c:55:power_init: power init ...
1970-01-01 00:06:23 driver-btm-api.c:1907:bitmain_board_init: Enter 30s sleep to make sure power release finish.
1970-01-01 00:06:55 power_api.c:232:set_iic_power_to_highest_voltage: setting to voltage: 17.00 ...
1970-01-01 00:07:01 power_api.c:124:check_voltage_multi: retry time: 0
1970-01-01 00:07:03 power_api.c:86:get_average_voltage: chain[0], voltage is: 17.916035
1970-01-01 00:07:04 power_api.c:86:get_average_voltage: chain[1], voltage is: 17.364961
1970-01-01 00:07:06 power_api.c:86:get_average_voltage: chain[2], voltage is: 17.242500
1970-01-01 00:07:06 power_api.c:97:get_average_voltage: aveage voltage is: 17.507832
1970-01-01 00:07:06 power_api.c:182:set_iic_power_by_voltage: now set voltage to : 17.000000
1970-01-01 00:07:06 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[0]: chip baud = 115200, chip_divider = 26
1970-01-01 00:07:06 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[1]: chip baud = 115200, chip_divider = 26
1970-01-01 00:07:06 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[2]: chip baud = 115200, chip_divider = 26
1970-01-01 00:07:06 uart.c:80:set_baud: set fpga_baud = 115200, fpga_divider = 26
1970-01-01 00:07:18 driver-btm-api.c:1010:check_asic_number_with_power_on: Chain[0]: find 30 asic, times 0
1970-01-01 00:07:28 driver-btm-api.c:1010:check_asic_number_with_power_on: Chain[1]: find 30 asic, times 0
1970-01-01 00:07:38 driver-btm-api.c:1010:check_asic_number_with_power_on: Chain[2]: find 30 asic, times 0
1970-01-01 00:07:41 driver-btm-api.c:348:set_order_clock: chain[0]: set order clock, stragegy 3 clock_en=0x1
1970-01-01 00:07:41 driver-btm-api.c:348:set_order_clock: chain[1]: set order clock, stragegy 3 clock_en=0x1
1970-01-01 00:07:42 driver-btm-api.c:348:set_order_clock: chain[2]: set order clock, stragegy 3 clock_en=0x1
1970-01-01 00:07:42 driver-hash-chip.c:490:set_clock_delay_control: core_data = 0xb4
1970-01-01 00:07:42 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[0]: chip baud = 3000000, chip_divider = 0
1970-01-01 00:07:42 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[1]: chip baud = 3000000, chip_divider = 0
1970-01-01 00:07:42 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[2]: chip baud = 3000000, chip_divider = 0
1970-01-01 00:07:42 uart.c:80:set_baud: set fpga_baud = 3000000, fpga_divider = 0
1970-01-01 00:07:42 driver-btm-api.c:1660:check_clock_counter: freq 50 clock_counter_limit 6
1970-01-01 00:07:42 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[0]: chip baud = 115200, chip_divider = 26
1970-01-01 00:07:42 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[1]: chip baud = 115200, chip_divider = 26
1970-01-01 00:07:42 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[2]: chip baud = 115200, chip_divider = 26
1970-01-01 00:07:43 uart.c:80:set_baud: set fpga_baud = 115200, fpga_divider = 26
1970-01-01 00:07:43 voltage[0] = 1710
1970-01-01 00:07:43 voltage[1] = 1710
1970-01-01 00:07:43 voltage[2] = 1710
1970-01-01 00:07:43 power_api.c:140:set_working_voltage: working_voltage = 17.100000
1970-01-01 00:07:44 temperature.c:282:calibrate_temp_sensor_one_chain: Temperature sensor calibration: chain 0 success.
1970-01-01 00:07:45 temperature.c:282:calibrate_temp_sensor_one_chain: Temperature sensor calibration: chain 1 success.
1970-01-01 00:07:47 temperature.c:282:calibrate_temp_sensor_one_chain: Temperature sensor calibration: chain 2 success.
1970-01-01 00:07:47 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[0]: chip baud = 6000000, chip_divider = 7
1970-01-01 00:07:47 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[1]: chip baud = 6000000, chip_divider = 7
1970-01-01 00:07:47 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[2]: chip baud = 6000000, chip_divider = 7
1970-01-01 00:07:47 uart.c:80:set_baud: set fpga_baud = 6000000, fpga_divider = 3
1970-01-01 00:07:49 driver-btm-api.c:248:check_bringup_temp: Bring up temperature is 17
1970-01-01 00:07:49 thread.c:804:create_check_miner_status_thread: create thread
1970-01-01 00:07:49 thread.c:794:create_set_miner_status_thread: create thread
1970-01-01 00:07:49 driver-btm-api.c:581:calculate_timeout: dev->timeout = 392
1970-01-01 00:07:49 thread.c:779:create_temperature_monitor_thread: create thread
1970-01-01 00:07:49 freq_tuning.c:154:freq_tuning_get_max_freq: Max freq of tuning is 760
1970-01-01 00:07:49 power_api.c:379:slowly_set_iic_power_to_custom_voltage: slowly setting to voltage: 18.00 ...
1970-01-01 00:08:21 power_api.c:124:check_voltage_multi: retry time: 0
1970-01-01 00:08:23 power_api.c:86:get_average_voltage: chain[0], voltage is: 18.124219
1970-01-01 00:08:24 power_api.c:86:get_average_voltage: chain[1], voltage is: 18.118095
1970-01-01 00:08:26 power_api.c:86:get_average_voltage: chain[2], voltage is: 18.246679
1970-01-01 00:08:26 power_api.c:97:get_average_voltage: aveage voltage is: 18.162998
1970-01-01 00:08:26 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 42 set refdiv: 2, fbdiv: 168, postdiv1: 7, postdiv2: 7, usr divider: 1
1970-01-01 00:08:26 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 50 set refdiv: 2, fbdiv: 168, postdiv1: 7, postdiv2: 6, usr divider: 1
1970-01-01 00:08:26 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 60 set refdiv: 2, fbdiv: 168, postdiv1: 7, postdiv2: 5, usr divider: 1
1970-01-01 00:08:27 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 75 set refdiv: 2, fbdiv: 168, postdiv1: 7, postdiv2: 4, usr divider: 1
1970-01-01 00:08:27 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 100 set refdiv: 2, fbdiv: 168, postdiv1: 7, postdiv2: 3, usr divider: 1
1970-01-01 00:08:27 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 150 set refdiv: 2, fbdiv: 168, postdiv1: 7, postdiv2: 2, usr divider: 1
1970-01-01 00:08:27 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 300 set refdiv: 2, fbdiv: 168, postdiv1: 7, postdiv2: 1, usr divider: 1
1970-01-01 00:08:27 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 350 set refdiv: 2, fbdiv: 168, postdiv1: 6, postdiv2: 1, usr divider: 1
1970-01-01 00:08:27 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 420 set refdiv: 2, fbdiv: 168, postdiv1: 5, postdiv2: 1, usr divider: 1
1970-01-01 00:08:27 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 525 set refdiv: 2, fbdiv: 168, postdiv1: 4, postdiv2: 1, usr divider: 1
1970-01-01 00:08:27 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 700 set refdiv: 2, fbdiv: 168, postdiv1: 3, postdiv2: 1, usr divider: 1
1970-01-01 00:08:27 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 41 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 7, usr divider: 1
1970-01-01 00:08:27 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 47 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 6, usr divider: 1
1970-01-01 00:08:28 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 57 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 5, usr divider: 1
1970-01-01 00:08:28 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 71 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 4, usr divider: 1
1970-01-01 00:08:28 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 95 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 3, usr divider: 1
1970-01-01 00:08:28 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 143 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 2, usr divider: 1
1970-01-01 00:08:28 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 287 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 1, usr divider: 1
1970-01-01 00:08:28 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 335 set refdiv: 2, fbdiv: 161, postdiv1: 6, postdiv2: 1, usr divider: 1
1970-01-01 00:08:28 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 402 set refdiv: 2, fbdiv: 161, postdiv1: 5, postdiv2: 1, usr divider: 1
1970-01-01 00:08:28 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 503 set refdiv: 2, fbdiv: 161, postdiv1: 4, postdiv2: 1, usr divider: 1
1970-01-01 00:08:28 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 670 set refdiv: 2, fbdiv: 161, postdiv1: 3, postdiv2: 1, usr divider: 1
1970-01-01 00:08:29 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 41 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 7, usr divider: 1
1970-01-01 00:08:29 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 47 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 6, usr divider: 1
1970-01-01 00:08:29 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 57 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 5, usr divider: 1
1970-01-01 00:08:29 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 71 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 4, usr divider: 1
1970-01-01 00:08:29 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 95 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 3, usr divider: 1
1970-01-01 00:08:29 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 143 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 2, usr divider: 1
1970-01-01 00:08:29 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 287 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 1, usr divider: 1
1970-01-01 00:08:29 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 335 set refdiv: 2, fbdiv: 161, postdiv1: 6, postdiv2: 1, usr divider: 1
1970-01-01 00:08:29 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 402 set refdiv: 2, fbdiv: 161, postdiv1: 5, postdiv2: 1, usr divider: 1
1970-01-01 00:08:29 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 503 set refdiv: 2, fbdiv: 161, postdiv1: 4, postdiv2: 1, usr divider: 1
1970-01-01 00:08:30 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 670 set refdiv: 2, fbdiv: 161, postdiv1: 3, postdiv2: 1, usr divider: 1
1970-01-01 00:08:30 driver-btm-api.c:612:set_timeout: freq 700 final timeout=168
1970-01-01 00:08:30 power_api.c:146:set_higher_voltage: higher_voltage = 18.000000
1970-01-01 00:08:30 power_api.c:428:slowly_set_iic_power_to_higher_voltage: slowly setting to voltage: 18.00 ...
1970-01-01 00:08:54 power_api.c:124:check_voltage_multi: retry time: 0
1970-01-01 00:08:56 power_api.c:86:get_average_voltage: chain[0], voltage is: 18.111972
1970-01-01 00:08:58 power_api.c:86:get_average_voltage: chain[1], voltage is: 18.093603
1970-01-01 00:08:59 power_api.c:86:get_average_voltage: chain[2], voltage is: 18.203818
1970-01-01 00:08:59 power_api.c:97:get_average_voltage: aveage voltage is: 18.136465
1970-01-01 00:08:59 frequency.c:540:get_current_min_freq: current min freq 670
1970-01-01 00:08:59 driver-btm-api.c:1660:check_clock_counter: freq 670 clock_counter_limit 85
1970-01-01 00:09:00 thread.c:478:clear_zero_nonce_mark: 0 nonce protect succeed.
1970-01-01 00:09:00 thread.c:799:create_check_system_status_thread: create thread
1970-01-01 00:09:01 driver-btm-api.c:2113:bitmain_soc_init: Init done!
1970-01-01 00:09:01 driver-btm-api.c:201:set_miner_status: STATUS_INIT
1970-01-01 00:09:06 driver-btm-api.c:201:set_miner_status: STATUS_OKAY
1970-01-01 00:09:11 driver-btm-api.c:1293:dhash_chip_send_job: Version num 4
1970-01-01 00:09:15 thread.c:382:check_working_voltage: current PCB min temperature is 40
1970-01-01 00:09:15 thread.c:383:check_working_voltage: current voltage is 18.00V, recovery to 17.10V
1970-01-01 00:09:15 power_api.c:397:slowly_set_iic_power_to_working_voltage: slowly setting to voltage: 17.10 ...
1970-01-01 00:09:53 power_api.c:124:check_voltage_multi: retry time: 0
1970-01-01 00:09:55 power_api.c:86:get_average_voltage: chain[0], voltage is: 17.169023
1970-01-01 00:09:56 power_api.c:86:get_average_voltage: chain[1], voltage is: 17.162900
1970-01-01 00:09:58 power_api.c:86:get_average_voltage: chain[2], voltage is: 17.273115
1970-01-01 00:09:58 power_api.c:97:get_average_voltage: aveage voltage is: 17.201679
1970-01-01 00:14:57 thread.c:422:is_zero_nonce_happened: chain_nonce[0] = 17980
1970-01-01 00:14:57 thread.c:422:is_zero_nonce_happened: chain_nonce[1] = 16935
1970-01-01 00:14:57 thread.c:422:is_zero_nonce_happened: chain_nonce[2] = 14659
1970-01-01 00:18:01 driver-btm-api.c:1293:dhash_chip_send_job: Version num 1
1970-01-01 00:18:09 driver-btm-api.c:201:set_miner_status: WARN_NET_LOST
1970-01-01 00:18:21 driver-btm-api.c:1293:dhash_chip_send_job: Version num 4
1970-01-01 00:18:22 driver-btm-api.c:201:set_miner_status: STATUS_OKAY
2020-05-01 04:33:01 driver-btm-api.c:201:set_miner_status: WARN_NET_LOST
2020-05-01 04:33:10 driver-btm-api.c:201:set_miner_status: STATUS_OKAY
2020-05-01 04:33:19 log.c:100:_log_update_name: _log_update_name
2020-05-01 04:33:19 log.c:100:_log_update_name: _log_update_name
2020-05-01 04:52:37 thread.c:204:calc_hashrate_avg: avg rate is 0.05 in 26471803 mins
2020-05-01 04:52:37 temperature.c:450:temp_statistics_show: pcb temp 42~56 chip temp 62~80
2020-05-01 04:52:37 thread.c:285:check_hashrate: latest avg rate < 0.98......
2020-05-01 04:52:37 thread.c:286:check_hashrate: current PCB min temperature 42
2020-05-01 04:52:37 thread.c:287:check_hashrate: current voltage is 17.10V, working voltage is 17.10V
2020-05-01 04:52:37 thread.c:318:check_hashrate: high temp, increase voltage 0.1V/0.2V to 17.20V
2020-05-01 04:52:37 driver-btm-api.c:2124:bitmain_reopen_core: reopen_core start!
2020-05-01 04:52:43 driver-btm-api.c:1067:init_miner_version: miner ID : 8042750618c0885c
2020-05-01 04:52:43 driver-btm-api.c:1073:init_miner_version: FPGA Version = 0xB013
2020-05-01 04:52:43 chain = 0, mode = 0, load_done = false.
2020-05-01 04:52:43 chain = 1, mode = 0, load_done = false.
2020-05-01 04:52:43 chain = 2, mode = 0, load_done = false.
2020-05-01 04:52:44 chain = 0, mode = 0, load_done = false.
2020-05-01 04:52:44 chain = 1, mode = 0, load_done = false.
2020-05-01 04:52:44 chain = 2, mode = 0, load_done = false.
2020-05-01 04:52:45 eeprom.c:425:check_pattern_test_level: invalid pattern test result. ignore
2020-05-01 04:52:45 chain = 0, mode = 0, load_done = false.
2020-05-01 04:52:45 chain = 1, mode = 0, load_done = false.
2020-05-01 04:52:45 chain = 2, mode = 0, load_done = false.
2020-05-01 04:52:46 chain = 0, mode = 0, load_done = false.
2020-05-01 04:52:46 chain = 1, mode = 0, load_done = false.
2020-05-01 04:52:46 chain = 2, mode = 0, load_done = false.
2020-05-01 04:52:47 eeprom.c:425:check_pattern_test_level: invalid pattern test result. ignore
2020-05-01 04:52:47 chain = 0, mode = 0, load_done = false.
2020-05-01 04:52:47 chain = 1, mode = 0, load_done = false.
2020-05-01 04:52:47 chain = 2, mode = 0, load_done = false.
2020-05-01 04:52:48 chain = 0, mode = 0, load_done = false.
2020-05-01 04:52:48 chain = 1, mode = 0, load_done = false.
2020-05-01 04:52:48 chain = 2, mode = 0, load_done = false.
2020-05-01 04:52:48 eeprom.c:425:check_pattern_test_level: invalid pattern test result. ignore
2020-05-01 04:52:48 driver-btm-api.c:705:get_product_id: product_id[0] = 1
2020-05-01 04:52:48 driver-btm-api.c:705:get_product_id: product_id[1] = 1
2020-05-01 04:52:48 driver-btm-api.c:705:get_product_id: product_id[2] = 1
2020-05-01 04:52:48 driver-btm-api.c:1633:get_ccdly_opt: ccdly_opt[0] = 1
2020-05-01 04:52:48 driver-btm-api.c:1633:get_ccdly_opt: ccdly_opt[1] = 1
2020-05-01 04:52:48 driver-btm-api.c:1633:get_ccdly_opt: ccdly_opt[2] = 1
2020-05-01 04:52:48 driver-btm-api.c:1877:bitmain_board_init: g_ccdly_opt = 1
2020-05-01 04:52:48 driver-btm-api.c:644:_set_project_type: project:2
2020-05-01 04:52:48 driver-btm-api.c:674:_set_project_type: Project type: Antminer T17
2020-05-01 04:52:48 driver-btm-api.c:685:dump_pcb_bom_version: Chain [0] PCB Version: 0x0100
2020-05-01 04:52:48 driver-btm-api.c:686:dump_pcb_bom_version: Chain [0] BOM Version: 0x0100
2020-05-01 04:52:48 driver-btm-api.c:685:dump_pcb_bom_version: Chain [1] PCB Version: 0x0100
2020-05-01 04:52:48 driver-btm-api.c:686:dump_pcb_bom_version: Chain [1] BOM Version: 0x0100
2020-05-01 04:52:48 driver-btm-api.c:685:dump_pcb_bom_version: Chain [2] PCB Version: 0x0100
2020-05-01 04:52:48 driver-btm-api.c:686:dump_pcb_bom_version: Chain [2] BOM Version: 0x0100
2020-05-01 04:52:50 driver-btm-api.c:1897:bitmain_board_init: Fan check passed.
2020-05-01 04:52:52 register.c:283:get_register: !!! reg crc error
2020-05-01 04:52:54 board.c:36:jump_and_app_check_restore_pic: chain[0] PIC jump to app
2020-05-01 04:52:57 board.c:40:jump_and_app_check_restore_pic: Check chain[0] PIC fw version=0xb9
2020-05-01 04:52:59 board.c:36:jump_and_app_check_restore_pic: chain[1] PIC jump to app
2020-05-01 04:53:02 board.c:40:jump_and_app_check_restore_pic: Check chain[1] PIC fw version=0xb9
2020-05-01 04:53:06 board.c:36:jump_and_app_check_restore_pic: chain[2] PIC jump to app
2020-05-01 04:53:12 board.c:40:jump_and_app_check_restore_pic: Check chain[2] PIC fw version=0xb9
2020-05-01 04:53:12 power_api.c:55:power_init: power init ...
2020-05-01 04:53:12 driver-btm-api.c:1907:bitmain_board_init: Enter 30s sleep to make sure power release finish.
2020-05-01 04:53:44 power_api.c:232:set_iic_power_to_highest_voltage: setting to voltage: 17.00 ...
2020-05-01 04:53:45 power_api.c:124:check_voltage_multi: retry time: 0
2020-05-01 04:53:47 power_api.c:86:get_average_voltage: chain[0], voltage is: 17.218008
2020-05-01 04:53:49 power_api.c:86:get_average_voltage: chain[1], voltage is: 17.095547
2020-05-01 04:53:51 power_api.c:86:get_average_voltage: chain[2], voltage is: 17.242500
2020-05-01 04:53:51 power_api.c:97:get_average_voltage: aveage voltage is: 17.185351
2020-05-01 04:53:51 power_api.c:182:set_iic_power_by_voltage: now set voltage to : 17.000000
2020-05-01 04:53:51 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[0]: chip baud = 115200, chip_divider = 26
2020-05-01 04:53:51 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[1]: chip baud = 115200, chip_divider = 26
2020-05-01 04:53:51 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[2]: chip baud = 115200, chip_divider = 26
2020-05-01 04:53:51 uart.c:80:set_baud: set fpga_baud = 115200, fpga_divider = 26
2020-05-01 04:54:01 driver-btm-api.c:1010:check_asic_number_with_power_on: Chain[0]: find 30 asic, times 0
2020-05-01 04:54:11 driver-btm-api.c:1010:check_asic_number_with_power_on: Chain[1]: find 30 asic, times 0
2020-05-01 04:54:21 driver-btm-api.c:1010:check_asic_number_with_power_on: Chain[2]: find 30 asic, times 0
2020-05-01 04:54:24 driver-btm-api.c:348:set_order_clock: chain[0]: set order clock, stragegy 3 clock_en=0x1
2020-05-01 04:54:25 driver-btm-api.c:348:set_order_clock: chain[1]: set order clock, stragegy 3 clock_en=0x1
2020-05-01 04:54:25 driver-btm-api.c:348:set_order_clock: chain[2]: set order clock, stragegy 3 clock_en=0x1
2020-05-01 04:54:25 driver-hash-chip.c:490:set_clock_delay_control: core_data = 0xb4
2020-05-01 04:54:25 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[0]: chip baud = 3000000, chip_divider = 0
2020-05-01 04:54:25 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[1]: chip baud = 3000000, chip_divider = 0
2020-05-01 04:54:25 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[2]: chip baud = 3000000, chip_divider = 0
2020-05-01 04:54:25 uart.c:80:set_baud: set fpga_baud = 3000000, fpga_divider = 0
2020-05-01 04:54:25 driver-btm-api.c:1660:check_clock_counter: freq 50 clock_counter_limit 6
2020-05-01 04:54:26 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[0]: chip baud = 115200, chip_divider = 26
2020-05-01 04:54:26 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[1]: chip baud = 115200, chip_divider = 26
2020-05-01 04:54:26 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[2]: chip baud = 115200, chip_divider = 26
2020-05-01 04:54:26 uart.c:80:set_baud: set fpga_baud = 115200, fpga_divider = 26
2020-05-01 04:54:26 voltage[0] = 1710
2020-05-01 04:54:26 voltage[1] = 1710
2020-05-01 04:54:26 voltage[2] = 1710
2020-05-01 04:54:26 power_api.c:140:set_working_voltage: working_voltage = 17.100000
2020-05-01 04:54:27 temperature.c:282:calibrate_temp_sensor_one_chain: Temperature sensor calibration: chain 0 success.
2020-05-01 04:54:29 temperature.c:282:calibrate_temp_sensor_one_chain: Temperature sensor calibration: chain 1 success.
2020-05-01 04:54:30 temperature.c:282:calibrate_temp_sensor_one_chain: Temperature sensor calibration: chain 2 success.
2020-05-01 04:54:30 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[0]: chip baud = 6000000, chip_divider = 7
2020-05-01 04:54:30 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[1]: chip baud = 6000000, chip_divider = 7
2020-05-01 04:54:30 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[2]: chip baud = 6000000, chip_divider = 7
2020-05-01 04:54:30 uart.c:80:set_baud: set fpga_baud = 6000000, fpga_divider = 3
2020-05-01 04:54:32 driver-btm-api.c:248:check_bringup_temp: Bring up temperature is 19
2020-05-01 04:54:32 driver-btm-api.c:581:calculate_timeout: dev->timeout = 392
2020-05-01 04:54:32 power_api.c:379:slowly_set_iic_power_to_custom_voltage: slowly setting to voltage: 18.00 ...
2020-05-01 04:55:04 power_api.c:124:check_voltage_multi: retry time: 0
2020-05-01 04:55:06 power_api.c:86:get_average_voltage: chain[0], voltage is: 18.136465
2020-05-01 04:55:08 power_api.c:86:get_average_voltage: chain[1], voltage is: 18.118095
2020-05-01 04:55:09 power_api.c:86:get_average_voltage: chain[2], voltage is: 18.240556
2020-05-01 04:55:09 power_api.c:97:get_average_voltage: aveage voltage is: 18.165039
2020-05-01 04:55:09 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 42 set refdiv: 2, fbdiv: 168, postdiv1: 7, postdiv2: 7, usr divider: 1
2020-05-01 04:55:10 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 50 set refdiv: 2, fbdiv: 168, postdiv1: 7, postdiv2: 6, usr divider: 1
2020-05-01 04:55:10 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 60 set refdiv: 2, fbdiv: 168, postdiv1: 7, postdiv2: 5, usr divider: 1
2020-05-01 04:55:10 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 75 set refdiv: 2, fbdiv: 168, postdiv1: 7, postdiv2: 4, usr divider: 1
2020-05-01 04:55:10 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 100 set refdiv: 2, fbdiv: 168, postdiv1: 7, postdiv2: 3, usr divider: 1
2020-05-01 04:55:10 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 150 set refdiv: 2, fbdiv: 168, postdiv1: 7, postdiv2: 2, usr divider: 1
2020-05-01 04:55:10 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 300 set refdiv: 2, fbdiv: 168, postdiv1: 7, postdiv2: 1, usr divider: 1
2020-05-01 04:55:10 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 350 set refdiv: 2, fbdiv: 168, postdiv1: 6, postdiv2: 1, usr divider: 1
2020-05-01 04:55:10 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 420 set refdiv: 2, fbdiv: 168, postdiv1: 5, postdiv2: 1, usr divider: 1
2020-05-01 04:55:10 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 525 set refdiv: 2, fbdiv: 168, postdiv1: 4, postdiv2: 1, usr divider: 1
2020-05-01 04:55:10 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 700 set refdiv: 2, fbdiv: 168, postdiv1: 3, postdiv2: 1, usr divider: 1
2020-05-01 04:55:11 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 41 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 7, usr divider: 1
2020-05-01 04:55:11 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 47 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 6, usr divider: 1
2020-05-01 04:55:11 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 57 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 5, usr divider: 1
2020-05-01 04:55:11 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 71 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 4, usr divider: 1
2020-05-01 04:55:11 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 95 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 3, usr divider: 1
2020-05-01 04:55:11 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 143 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 2, usr divider: 1
2020-05-01 04:55:11 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 287 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 1, usr divider: 1
2020-05-01 04:55:11 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 335 set refdiv: 2, fbdiv: 161, postdiv1: 6, postdiv2: 1, usr divider: 1
2020-05-01 04:55:11 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 402 set refdiv: 2, fbdiv: 161, postdiv1: 5, postdiv2: 1, usr divider: 1
2020-05-01 04:55:12 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 503 set refdiv: 2, fbdiv: 161, postdiv1: 4, postdiv2: 1, usr divider: 1
2020-05-01 04:55:12 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 670 set refdiv: 2, fbdiv: 161, postdiv1: 3, postdiv2: 1, usr divider: 1
2020-05-01 04:55:12 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 41 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 7, usr divider: 1
2020-05-01 04:55:12 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 47 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 6, usr divider: 1
2020-05-01 04:55:12 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 57 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 5, usr divider: 1
2020-05-01 04:55:12 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 71 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 4, usr divider: 1
2020-05-01 04:55:12 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 95 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 3, usr divider: 1
2020-05-01 04:55:12 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 143 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 2, usr divider: 1
2020-05-01 04:55:12 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 287 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 1, usr divider: 1
2020-05-01 04:55:12 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 335 set refdiv: 2, fbdiv: 161, postdiv1: 6, postdiv2: 1, usr divider: 1
2020-05-01 04:55:13 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 402 set refdiv: 2, fbdiv: 161, postdiv1: 5, postdiv2: 1, usr divider: 1
2020-05-01 04:55:13 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 503 set refdiv: 2, fbdiv: 161, postdiv1: 4, postdiv2: 1, usr divider: 1
2020-05-01 04:55:13 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 670 set refdiv: 2, fbdiv: 161, postdiv1: 3, postdiv2: 1, usr divider: 1
2020-05-01 04:55:13 driver-btm-api.c:612:set_timeout: freq 700 final timeout=168
2020-05-01 04:55:13 power_api.c:146:set_higher_voltage: higher_voltage = 18.000000
2020-05-01 04:55:13 power_api.c:428:slowly_set_iic_power_to_higher_voltage: slowly setting to voltage: 18.00 ...
2020-05-01 04:55:35 power_api.c:124:check_voltage_multi: retry time: 0
2020-05-01 04:55:37 power_api.c:86:get_average_voltage: chain[0], voltage is: 18.105849
2020-05-01 04:55:38 power_api.c:86:get_average_voltage: chain[1], voltage is: 18.099726
2020-05-01 04:55:40 power_api.c:86:get_average_voltage: chain[2], voltage is: 18.203818
2020-05-01 04:55:40 power_api.c:97:get_average_voltage: aveage voltage is: 18.136465
2020-05-01 04:55:41 driver-btm-api.c:2186:bitmain_reopen_core: reopen_core done!
2020-05-01 04:55:41 power_api.c:379:slowly_set_iic_power_to_custom_voltage: slowly setting to voltage: 17.20 ...
2020-05-01 04:56:21 power_api.c:124:check_voltage_multi: retry time: 0
2020-05-01 04:56:23 power_api.c:86:get_average_voltage: chain[0], voltage is: 17.279238
2020-05-01 04:56:25 power_api.c:86:get_average_voltage: chain[1], voltage is: 17.266992
2020-05-01 04:56:26 power_api.c:86:get_average_voltage: chain[2], voltage is: 17.371084
2020-05-01 04:56:26 power_api.c:97:get_average_voltage: aveage voltage is: 17.305771
2020-05-01 04:56:26 power_api.c:140:set_working_voltage: working_voltage = 17.200001
2020-05-01 05:01:25 thread.c:422:is_zero_nonce_happened: chain_nonce[0] = 112684
2020-05-01 05:01:25 thread.c:422:is_zero_nonce_happened: chain_nonce[1] = 107768
2020-05-01 05:01:25 thread.c:422:is_zero_nonce_happened: chain_nonce[2] = 92532
2020-05-01 05:26:26 thread.c:204:calc_hashrate_avg: avg rate is 39234.15 in 30 mins
2020-05-01 05:26:26 temperature.c:450:temp_statistics_show: pcb temp 42~56 chip temp 63~80
2020-05-01 05:56:28 thread.c:204:calc_hashrate_avg: avg rate is 39273.71 in 30 mins
2020-05-01 05:56:28 temperature.c:450:temp_statistics_show: pcb temp 42~57 chip temp 63~80
2020-05-01 06:26:29 thread.c:204:calc_hashrate_avg: avg rate is 38989.37 in 30 mins
2020-05-01 06:26:29 temperature.c:450:temp_statistics_show: pcb temp 42~56 chip temp 64~80
2020-05-01 06:26:29 thread.c:285:check_hashrate: latest avg rate < 0.98......
2020-05-01 06:26:29 thread.c:286:check_hashrate: current PCB min temperature 42
2020-05-01 06:26:29 thread.c:287:check_hashrate: current voltage is 17.20V, working voltage is 17.20V
2020-05-01 06:26:29 thread.c:312:check_hashrate: high temp, voltage has already increased 0.1V/0.2V
2020-05-01 06:56:30 thread.c:204:calc_hashrate_avg: avg rate is 39031.50 in 30 mins
2020-05-01 06:56:30 temperature.c:450:temp_statistics_show: pcb temp 42~57 chip temp 63~80
[...]
2020-05-02 04:27:26 thread.c:204:calc_hashrate_avg: avg rate is 39244.02 in 30 mins
2020-05-02 04:27:26 temperature.c:450:temp_statistics_show: pcb temp 38~56 chip temp 59~80
2020-05-02 04:57:27 thread.c:204:calc_hashrate_avg: avg rate is 39168.48 in 30 mins
2020-05-02 04:57:27 temperature.c:450:temp_statistics_show: pcb temp 41~56 chip temp 62~80
2020-05-02 04:57:27 thread.c:285:check_hashrate: latest avg rate < 0.98......
2020-05-02 04:57:27 thread.c:286:check_hashrate: current PCB min temperature 41
2020-05-02 04:57:27 thread.c:287:check_hashrate: current voltage is 17.20V, working voltage is 17.20V
2020-05-02 04:57:27 thread.c:312:check_hashrate: high temp, voltage has already increased 0.1V/0.2V
2020-05-02 05:27:28 thread.c:204:calc_hashrate_avg: avg rate is 39010.16 in 30 mins
2020-05-02 05:27:28 temperature.c:450:temp_statistics_show: pcb temp 42~56 chip temp 63~80
2020-05-02 05:27:28 thread.c:285:check_hashrate: latest avg rate < 0.98......
2020-05-02 05:27:28 thread.c:286:check_hashrate: current PCB min temperature 42
2020-05-02 05:27:28 thread.c:287:check_hashrate: current voltage is 17.20V, working voltage is 17.20V
2020-05-02 05:27:28 thread.c:312:check_hashrate: high temp, voltage has already increased 0.1V/0.2V
Miner Status Screen: https://drive.google.com/file/d/197SGfVUR8r7rLnQQDiwElOplCgagpMZC/view?usp=sharing
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: mysticbitcoin on May 03, 2020, 03:27:50 AM
DOWNHILL: Kernel Log - After reboot (many be a few): Booting Linux on physical CPU 0x0
Linux version 4.6.0-xilinx-gff8137b-dirty (lzq@armdev2) (gcc version 4.8.3 20140320 (prerelease) (Sourcery CodeBench Lite 2014.05-23) ) #25 SMP PREEMPT Fri Nov 23 15:30:52 CST 2018
CPU: ARMv7 Processor [413fc090] revision 0 (ARMv7), cr=18c5387d
CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
Machine model: Xilinx Zynq
cma: Reserved 16 MiB at 0x0e000000
Memory policy: Data cache writealloc
On node 0 totalpages: 61440
free_area_init_node: node 0, pgdat c0b39280, node_mem_map cde10000
Normal zone: 480 pages used for memmap
Normal zone: 0 pages reserved
Normal zone: 61440 pages, LIFO batch:15
percpu: Embedded 12 pages/cpu @cddf1000 s19776 r8192 d21184 u49152
pcpu-alloc: s19776 r8192 d21184 u49152 alloc=12*4096
pcpu-alloc: [0] 0 [0] 1
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 60960
Kernel command line: mem=240M console=ttyPS0,115200 ramdisk_size=33554432 root=/dev/ram rw earlyprintk
PID hash table entries: 1024 (order: 0, 4096 bytes)
Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
Memory: 203756K/245760K available (6345K kernel code, 231K rwdata, 1896K rodata, 1024K init, 223K bss, 25620K reserved, 16384K cma-reserved, 0K highmem)
Virtual kernel memory layout:
vector : 0xffff0000 - 0xffff1000 ( 4 kB)
fixmap : 0xffc00000 - 0xfff00000 (3072 kB)
vmalloc : 0xcf800000 - 0xff800000 ( 768 MB)
lowmem : 0xc0000000 - 0xcf000000 ( 240 MB)
pkmap : 0xbfe00000 - 0xc0000000 ( 2 MB)
modules : 0xbf000000 - 0xbfe00000 ( 14 MB)
.text : 0xc0008000 - 0xc090c424 (9234 kB)
.init : 0xc0a00000 - 0xc0b00000 (1024 kB)
.data : 0xc0b00000 - 0xc0b39fe0 ( 232 kB)
.bss : 0xc0b39fe0 - 0xc0b71c28 ( 224 kB)
Preemptible hierarchical RCU implementation.
Build-time adjustment of leaf fanout to 32.
RCU restricting CPUs from NR_CPUS=4 to nr_cpu_ids=2.
RCU: Adjusting geometry for rcu_fanout_leaf=32, nr_cpu_ids=2
NR_IRQS:16 nr_irqs:16 16
efuse mapped to cf800000
ps7-slcr mapped to cf802000
L2C: platform modifies aux control register: 0x72360000 -> 0x72760000
L2C: DT/platform modifies aux control register: 0x72360000 -> 0x72760000
L2C-310 erratum 769419 enabled
L2C-310 enabling early BRESP for Cortex-A9
L2C-310 full line of zeros enabled for Cortex-A9
L2C-310 ID prefetch enabled, offset 1 lines
L2C-310 dynamic clock gating enabled, standby mode enabled
L2C-310 cache controller enabled, 8 ways, 512 kB
L2C-310: CACHE_ID 0x410000c8, AUX_CTRL 0x76760001
zynq_clock_init: clkc starts at cf802100
Zynq clock init
sched_clock: 64 bits at 333MHz, resolution 3ns, wraps every 4398046511103ns
clocksource: arm_global_timer: mask: 0xffffffffffffffff max_cycles: 0x4ce07af025, max_idle_ns: 440795209040 ns
Switching to timer-based delay loop, resolution 3ns
clocksource: ttc_clocksource: mask: 0xffff max_cycles: 0xffff, max_idle_ns: 537538477 ns
ps7-ttc #0 at cf80a000, irq=18
Console: colour dummy device 80x30
Calibrating delay loop (skipped), value calculated using timer frequency.. 666.66 BogoMIPS (lpj=3333333)
pid_max: default: 32768 minimum: 301
Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
CPU: Testing write buffer coherency: ok
CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
Setting up static identity map for 0x100000 - 0x100058
CPU1: failed to boot: -1
Brought up 1 CPUs
SMP: Total of 1 processors activated (666.66 BogoMIPS).
CPU: All CPU(s) started in SVC mode.
devtmpfs: initialized
VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4
clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
pinctrl core: initialized pinctrl subsystem
NET: Registered protocol family 16
DMA: preallocated 256 KiB pool for atomic coherent allocations
cpuidle: using governor menu
hw-breakpoint: found 5 (+1 reserved) breakpoint and 1 watchpoint registers.
hw-breakpoint: maximum watchpoint size is 4 bytes.
zynq-ocm f800c000.ps7-ocmc: ZYNQ OCM pool: 256 KiB @ 0xcf880000
vgaarb: loaded
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
media: Linux media interface: v0.10
Linux video capture interface: v2.00
pps_core: LinuxPPS API ver. 1 registered
pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
PTP clock support registered
EDAC MC: Ver: 3.0.0
Advanced Linux Sound Architecture Driver Initialized.
clocksource: Switched to clocksource arm_global_timer
NET: Registered protocol family 2
TCP established hash table entries: 2048 (order: 1, 8192 bytes)
TCP bind hash table entries: 2048 (order: 2, 16384 bytes)
TCP: Hash tables configured (established 2048 bind 2048)
UDP hash table entries: 256 (order: 1, 8192 bytes)
UDP-Lite hash table entries: 256 (order: 1, 8192 bytes)
NET: Registered protocol family 1
RPC: Registered named UNIX socket transport module.
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
PCI: CLS 0 bytes, default 64
Trying to unpack rootfs image as initramfs...
rootfs image is not initramfs (no cpio magic); looks like an initrd
Freeing initrd memory: 12580K (cceb8000 - cdb01000)
hw perfevents: enabled with armv7_cortex_a9 PMU driver, 7 counters available
futex hash table entries: 512 (order: 3, 32768 bytes)
workingset: timestamp_bits=28 max_order=16 bucket_order=0
jffs2: version 2.2. (NAND) (SUMMARY) © 2001-2006 Red Hat, Inc.
io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered (default)
dma-pl330 f8003000.ps7-dma: Loaded driver for PL330 DMAC-241330
dma-pl330 f8003000.ps7-dma: DBUFF-128x8bytes Num_Chans-8 Num_Peri-4 Num_Events-16
e0000000.serial: ttyPS0 at MMIO 0xe0000000 (irq = 158, base_baud = 6249999) is a xuartps
console [ttyPS0] enabled
xdevcfg f8007000.ps7-dev-cfg: ioremap 0xf8007000 to cf86e000
[drm] Initialized drm 1.1.0 20060810
brd: module loaded
loop: module loaded
CAN device driver interface
gpiod_set_value: invalid GPIO
libphy: MACB_mii_bus: probed
macb e000b000.ethernet eth0: Cadence GEM rev 0x00020118 at 0xe000b000 irq 31 (00:0a:35:00:00:00)
Generic PHY e000b000.etherne:00: attached PHY driver [Generic PHY] (mii_bus:phy_addr=e000b000.etherne:00, irq=-1)
e1000e: Intel(R) PRO/1000 Network Driver - 3.2.6-k
e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
ehci-pci: EHCI PCI platform driver
usbcore: registered new interface driver usb-storage
mousedev: PS/2 mouse device common for all mice
i2c /dev entries driver
Xilinx Zynq CpuIdle Driver started
sdhci: Secure Digital Host Controller Interface driver
sdhci: Copyright(c) Pierre Ossman
sdhci-pltfm: SDHCI platform and OF driver helper
mmc0: SDHCI controller on e0100000.ps7-sdio [e0100000.ps7-sdio] using ADMA
ledtrig-cpu: registered to indicate activity on CPUs
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
nand: device found, Manufacturer ID: 0x2c, Chip ID: 0xda
nand: Micron MT29F2G08ABAGAWP
nand: 256 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 128
nand: WARNING: pl35x-nand: the ECC used on your system is too weak compared to the one required by the NAND chip
Bad block table found at page 131008, version 0x01
Bad block table found at page 130944, version 0x01
6 ofpart partitions found on MTD device pl35x-nand
Creating 6 MTD partitions on "pl35x-nand":
0x000000000000-0x000002800000 : "BOOT.bin-env-dts-kernel"
0x000002800000-0x000004800000 : "ramfs"
0x000004800000-0x000005000000 : "configs"
0x000005000000-0x000006000000 : "reserve"
0x000006000000-0x000008000000 : "ramfs-bak"
0x000008000000-0x000010000000 : "reserve1"
NET: Registered protocol family 10
sit: IPv6 over IPv4 tunneling driver
NET: Registered protocol family 17
can: controller area network core (rev 20120528 abi 9)
NET: Registered protocol family 29
can: raw protocol (rev 20120528)
can: broadcast manager protocol (rev 20120528 t)
can: netlink gateway (rev 20130117) max_hops=1
zynq_pm_ioremap: no compatible node found for 'xlnx,zynq-ddrc-a05'
zynq_pm_late_init: Unable to map DDRC IO memory.
Registering SWP/SWPB emulation handler
hctosys: unable to open rtc device (rtc0)
ALSA device list:
No soundcards found.
RAMDISK: gzip image found at block 0
EXT4-fs (ram0): couldn't mount as ext3 due to feature incompatibilities
EXT4-fs (ram0): mounted filesystem without journal. Opts: (null)
VFS: Mounted root (ext4 filesystem) on device 1:0.
devtmpfs: mounted
Freeing unused kernel memory: 1024K (c0a00000 - c0b00000)
EXT4-fs (ram0): re-mounted. Opts: block_validity,delalloc,barrier,user_xattr
random: dd urandom read with 0 bits of entropy available
ubi0: attaching mtd2
ubi0: scanning is finished
ubi0: attached mtd2 (name "configs", size 8 MiB)
ubi0: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
ubi0: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
ubi0: VID header offset: 2048 (aligned 2048), data offset: 4096
ubi0: good PEBs: 64, bad PEBs: 0, corrupted PEBs: 0
ubi0: user volume: 1, internal volumes: 1, max. volumes count: 128
ubi0: max/mean erase counter: 5/2, WL threshold: 4096, image sequence number: 4244297529
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 01559AD8-7B6A-42E6-A3FE-EDF3659527A9, 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: 1052/339, WL threshold: 4096, image sequence number: 4185749592
ubi1: available PEBs: 0, total reserved PEBs: 1020, PEBs reserved for bad PEB handling: 36
ubi1: background thread "ubi_bgt1d" started, PID 720
UBIFS (ubi1:0): background thread "ubifs_bgt1_0" started, PID 723
UBIFS (ubi1:0): recovery needed
UBIFS (ubi1:0): recovery completed
UBIFS (ubi1:0): UBIFS: mounted UBI device 1, volume 0, name "reserve1"
UBIFS (ubi1:0): LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
UBIFS (ubi1:0): FS size: 123039744 bytes (117 MiB, 969 LEBs), journal size 6221824 bytes (5 MiB, 49 LEBs)
UBIFS (ubi1:0): reserved for root: 4952683 bytes (4836 KiB)
UBIFS (ubi1:0): media format: w4/r0 (latest is w4/r0), UUID 4829CF2C-7435-4146-B2FD-0826AAE8443A, small LPT model
IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
macb e000b000.ethernet eth0: unable to generate target frequency: 25000000 Hz
macb e000b000.ethernet eth0: link up (100/Full)
IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
In axi fpga driver!
request_mem_region OK!
AXI fpga dev virtual address is 0xcfb38000
*base_vir_addr = 0xab013
In fpga mem driver!
request_mem_region OK!
fpga mem virtual address is 0xd2000000
random: nonblocking pool is initialized
2020-05-03 00:44:13 driver-btm-api.c:631:init_freq_mode: This is scan-user version
2020-05-03 00:44:13 driver-btm-api.c:1994:bitmain_soc_init: opt_multi_version = 1
2020-05-03 00:44:13 driver-btm-api.c:1995:bitmain_soc_init: opt_bitmain_ab = 1
2020-05-03 00:44:13 driver-btm-api.c:1996:bitmain_soc_init: opt_bitmain_work_mode = 0
2020-05-03 00:44:13 driver-btm-api.c:1997:bitmain_soc_init: Miner compile time: Tue Dec 24 16:13:07 CST 2019 type: Antminer T17
2020-05-03 00:44:13 driver-btm-api.c:1998:bitmain_soc_init: commit version: e93a09b 2019-12-24 16:03:45, build by: lol 2019-12-24 16:19:49
2020-05-03 00:44:13 driver-btm-api.c:1810:show_sn: no SN got, please write SN to /nvdata/sn
2020-05-03 00:44:13 driver-btm-api.c:1135:miner_device_init: Detect 256MB control board of XILINX
2020-05-03 00:44:13 driver-btm-api.c:1083:init_fan_parameter: fan_eft : 0 fan_pwm : 0
2020-05-03 00:44:13 thread.c:789:create_read_nonce_reg_thread: create thread
2020-05-03 00:44:19 driver-btm-api.c:1067:init_miner_version: miner ID : 8042750618c0885c
2020-05-03 00:44:19 driver-btm-api.c:1073:init_miner_version: FPGA Version = 0xB013
2020-05-03 00:44:21 eeprom.c:425:check_pattern_test_level: invalid pattern test result. ignore
2020-05-03 00:44:23 eeprom.c:425:check_pattern_test_level: invalid pattern test result. ignore
2020-05-03 00:44:25 eeprom.c:425:check_pattern_test_level: invalid pattern test result. ignore
2020-05-03 00:44:25 driver-btm-api.c:705:get_product_id: product_id[0] = 1
2020-05-03 00:44:25 driver-btm-api.c:705:get_product_id: product_id[1] = 1
2020-05-03 00:44:25 driver-btm-api.c:705:get_product_id: product_id[2] = 1
2020-05-03 00:44:25 driver-btm-api.c:1633:get_ccdly_opt: ccdly_opt[0] = 1
2020-05-03 00:44:25 driver-btm-api.c:1633:get_ccdly_opt: ccdly_opt[1] = 1
2020-05-03 00:44:25 driver-btm-api.c:1633:get_ccdly_opt: ccdly_opt[2] = 1
2020-05-03 00:44:25 driver-btm-api.c:1877:bitmain_board_init: g_ccdly_opt = 1
2020-05-03 00:44:25 driver-btm-api.c:644:_set_project_type: project:2
2020-05-03 00:44:25 driver-btm-api.c:674:_set_project_type: Project type: Antminer T17
2020-05-03 00:44:25 driver-btm-api.c:685:dump_pcb_bom_version: Chain [0] PCB Version: 0x0100
2020-05-03 00:44:25 driver-btm-api.c:686:dump_pcb_bom_version: Chain [0] BOM Version: 0x0100
2020-05-03 00:44:25 driver-btm-api.c:685:dump_pcb_bom_version: Chain [1] PCB Version: 0x0100
2020-05-03 00:44:25 driver-btm-api.c:686:dump_pcb_bom_version: Chain [1] BOM Version: 0x0100
2020-05-03 00:44:25 driver-btm-api.c:685:dump_pcb_bom_version: Chain [2] PCB Version: 0x0100
2020-05-03 00:44:25 driver-btm-api.c:686:dump_pcb_bom_version: Chain [2] BOM Version: 0x0100
2020-05-03 00:44:27 driver-btm-api.c:1897:bitmain_board_init: Fan check passed.
2020-05-03 00:44:28 board.c:36:jump_and_app_check_restore_pic: chain[0] PIC jump to app
2020-05-03 00:44:32 board.c:40:jump_and_app_check_restore_pic: Check chain[0] PIC fw version=0xb9
2020-05-03 00:44:34 board.c:36:jump_and_app_check_restore_pic: chain[1] PIC jump to app
2020-05-03 00:44:37 board.c:40:jump_and_app_check_restore_pic: Check chain[1] PIC fw version=0xb9
2020-05-03 00:44:39 board.c:36:jump_and_app_check_restore_pic: chain[2] PIC jump to app
2020-05-03 00:44:42 board.c:40:jump_and_app_check_restore_pic: Check chain[2] PIC fw version=0xb9
2020-05-03 00:44:42 thread.c:784:create_pic_heart_beat_thread: create thread
2020-05-03 00:44:42 power_api.c:55:power_init: power init ...
2020-05-03 00:44:42 driver-btm-api.c:1907:bitmain_board_init: Enter 30s sleep to make sure power release finish.
2020-05-03 00:45:14 power_api.c:232:set_iic_power_to_highest_voltage: setting to voltage: 17.00 ...
2020-05-03 00:45:20 power_api.c:124:check_voltage_multi: retry time: 0
2020-05-03 00:45:22 power_api.c:86:get_average_voltage: chain[0], voltage is: 17.113916
2020-05-03 00:45:24 power_api.c:86:get_average_voltage: chain[1], voltage is: 17.113916
2020-05-03 00:45:25 power_api.c:86:get_average_voltage: chain[2], voltage is: 17.224131
2020-05-03 00:45:25 power_api.c:97:get_average_voltage: aveage voltage is: 17.150654
2020-05-03 00:45:25 power_api.c:182:set_iic_power_by_voltage: now set voltage to : 17.000000
2020-05-03 00:45:25 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[0]: chip baud = 115200, chip_divider = 26
2020-05-03 00:45:25 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[1]: chip baud = 115200, chip_divider = 26
2020-05-03 00:45:25 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[2]: chip baud = 115200, chip_divider = 26
2020-05-03 00:45:26 uart.c:80:set_baud: set fpga_baud = 115200, fpga_divider = 26
2020-05-03 00:45:37 driver-btm-api.c:1010:check_asic_number_with_power_on: Chain[0]: find 30 asic, times 0
2020-05-03 00:45:47 driver-btm-api.c:1010:check_asic_number_with_power_on: Chain[1]: find 30 asic, times 0
2020-05-03 00:45:57 driver-btm-api.c:1010:check_asic_number_with_power_on: Chain[2]: find 30 asic, times 0
2020-05-03 00:46:01 driver-btm-api.c:348:set_order_clock: chain[0]: set order clock, stragegy 3 clock_en=0x1
2020-05-03 00:46:01 driver-btm-api.c:348:set_order_clock: chain[1]: set order clock, stragegy 3 clock_en=0x1
2020-05-03 00:46:01 driver-btm-api.c:348:set_order_clock: chain[2]: set order clock, stragegy 3 clock_en=0x1
2020-05-03 00:46:01 driver-hash-chip.c:490:set_clock_delay_control: core_data = 0xb4
2020-05-03 00:46:01 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[0]: chip baud = 3000000, chip_divider = 0
2020-05-03 00:46:01 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[1]: chip baud = 3000000, chip_divider = 0
2020-05-03 00:46:01 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[2]: chip baud = 3000000, chip_divider = 0
2020-05-03 00:46:01 uart.c:80:set_baud: set fpga_baud = 3000000, fpga_divider = 0
2020-05-03 00:46:01 driver-btm-api.c:1660:check_clock_counter: freq 50 clock_counter_limit 6
2020-05-03 00:46:02 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[0]: chip baud = 115200, chip_divider = 26
2020-05-03 00:46:02 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[1]: chip baud = 115200, chip_divider = 26
2020-05-03 00:46:02 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[2]: chip baud = 115200, chip_divider = 26
2020-05-03 00:46:02 uart.c:80:set_baud: set fpga_baud = 115200, fpga_divider = 26
2020-05-03 00:46:02 voltage[0] = 1710
2020-05-03 00:46:02 voltage[1] = 1710
2020-05-03 00:46:02 voltage[2] = 1710
2020-05-03 00:46:02 power_api.c:140:set_working_voltage: working_voltage = 17.100000
2020-05-03 00:46:03 temperature.c:282:calibrate_temp_sensor_one_chain: Temperature sensor calibration: chain 0 success.
2020-05-03 00:46:05 temperature.c:282:calibrate_temp_sensor_one_chain: Temperature sensor calibration: chain 1 success.
2020-05-03 00:46:06 temperature.c:282:calibrate_temp_sensor_one_chain: Temperature sensor calibration: chain 2 success.
2020-05-03 00:46:06 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[0]: chip baud = 6000000, chip_divider = 7
2020-05-03 00:46:06 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[1]: chip baud = 6000000, chip_divider = 7
2020-05-03 00:46:06 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[2]: chip baud = 6000000, chip_divider = 7
2020-05-03 00:46:06 uart.c:80:set_baud: set fpga_baud = 6000000, fpga_divider = 3
2020-05-03 00:46:08 driver-btm-api.c:248:check_bringup_temp: Bring up temperature is 24
2020-05-03 00:46:08 thread.c:804:create_check_miner_status_thread: create thread
2020-05-03 00:46:08 thread.c:794:create_set_miner_status_thread: create thread
2020-05-03 00:46:08 driver-btm-api.c:581:calculate_timeout: dev->timeout = 392
2020-05-03 00:46:08 thread.c:779:create_temperature_monitor_thread: create thread
2020-05-03 00:46:08 freq_tuning.c:154:freq_tuning_get_max_freq: Max freq of tuning is 760
2020-05-03 00:46:08 power_api.c:379:slowly_set_iic_power_to_custom_voltage: slowly setting to voltage: 18.00 ...
2020-05-03 00:46:40 power_api.c:124:check_voltage_multi: retry time: 0
2020-05-03 00:46:42 power_api.c:86:get_average_voltage: chain[0], voltage is: 18.130342
2020-05-03 00:46:44 power_api.c:86:get_average_voltage: chain[1], voltage is: 18.111972
2020-05-03 00:46:45 power_api.c:86:get_average_voltage: chain[2], voltage is: 18.228310
2020-05-03 00:46:45 power_api.c:97:get_average_voltage: aveage voltage is: 18.156875
2020-05-03 00:46:45 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 42 set refdiv: 2, fbdiv: 168, postdiv1: 7, postdiv2: 7, usr divider: 1
2020-05-03 00:46:46 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 50 set refdiv: 2, fbdiv: 168, postdiv1: 7, postdiv2: 6, usr divider: 1
2020-05-03 00:46:46 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 60 set refdiv: 2, fbdiv: 168, postdiv1: 7, postdiv2: 5, usr divider: 1
2020-05-03 00:46:46 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 75 set refdiv: 2, fbdiv: 168, postdiv1: 7, postdiv2: 4, usr divider: 1
2020-05-03 00:46:46 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 100 set refdiv: 2, fbdiv: 168, postdiv1: 7, postdiv2: 3, usr divider: 1
2020-05-03 00:46:46 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 150 set refdiv: 2, fbdiv: 168, postdiv1: 7, postdiv2: 2, usr divider: 1
2020-05-03 00:46:46 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 300 set refdiv: 2, fbdiv: 168, postdiv1: 7, postdiv2: 1, usr divider: 1
2020-05-03 00:46:46 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 350 set refdiv: 2, fbdiv: 168, postdiv1: 6, postdiv2: 1, usr divider: 1
2020-05-03 00:46:46 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 420 set refdiv: 2, fbdiv: 168, postdiv1: 5, postdiv2: 1, usr divider: 1
2020-05-03 00:46:46 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 525 set refdiv: 2, fbdiv: 168, postdiv1: 4, postdiv2: 1, usr divider: 1
2020-05-03 00:46:47 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 700 set refdiv: 2, fbdiv: 168, postdiv1: 3, postdiv2: 1, usr divider: 1
2020-05-03 00:46:47 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 41 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 7, usr divider: 1
2020-05-03 00:46:47 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 47 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 6, usr divider: 1
2020-05-03 00:46:47 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 57 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 5, usr divider: 1
2020-05-03 00:46:47 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 71 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 4, usr divider: 1
2020-05-03 00:46:47 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 95 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 3, usr divider: 1
2020-05-03 00:46:47 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 143 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 2, usr divider: 1
2020-05-03 00:46:47 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 287 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 1, usr divider: 1
2020-05-03 00:46:47 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 335 set refdiv: 2, fbdiv: 161, postdiv1: 6, postdiv2: 1, usr divider: 1
2020-05-03 00:46:47 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 402 set refdiv: 2, fbdiv: 161, postdiv1: 5, postdiv2: 1, usr divider: 1
2020-05-03 00:46:48 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 503 set refdiv: 2, fbdiv: 161, postdiv1: 4, postdiv2: 1, usr divider: 1
2020-05-03 00:46:48 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 670 set refdiv: 2, fbdiv: 161, postdiv1: 3, postdiv2: 1, usr divider: 1
2020-05-03 00:46:48 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 41 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 7, usr divider: 1
2020-05-03 00:46:48 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 47 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 6, usr divider: 1
2020-05-03 00:46:48 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 57 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 5, usr divider: 1
2020-05-03 00:46:48 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 71 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 4, usr divider: 1
2020-05-03 00:46:48 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 95 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 3, usr divider: 1
2020-05-03 00:46:48 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 143 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 2, usr divider: 1
2020-05-03 00:46:48 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 287 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 1, usr divider: 1
2020-05-03 00:46:49 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 335 set refdiv: 2, fbdiv: 161, postdiv1: 6, postdiv2: 1, usr divider: 1
2020-05-03 00:46:49 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 402 set refdiv: 2, fbdiv: 161, postdiv1: 5, postdiv2: 1, usr divider: 1
2020-05-03 00:46:49 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 503 set refdiv: 2, fbdiv: 161, postdiv1: 4, postdiv2: 1, usr divider: 1
2020-05-03 00:46:49 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 670 set refdiv: 2, fbdiv: 161, postdiv1: 3, postdiv2: 1, usr divider: 1
2020-05-03 00:46:49 driver-btm-api.c:612:set_timeout: freq 700 final timeout=168
2020-05-03 00:46:49 power_api.c:397:slowly_set_iic_power_to_working_voltage: slowly setting to voltage: 17.10 ...
2020-05-03 00:47:26 power_api.c:124:check_voltage_multi: retry time: 0
2020-05-03 00:47:28 power_api.c:86:get_average_voltage: chain[0], voltage is: 17.199638
2020-05-03 00:47:30 power_api.c:86:get_average_voltage: chain[1], voltage is: 17.175146
2020-05-03 00:47:31 power_api.c:86:get_average_voltage: chain[2], voltage is: 17.297607
2020-05-03 00:47:31 power_api.c:97:get_average_voltage: aveage voltage is: 17.224131
2020-05-03 00:47:31 frequency.c:540:get_current_min_freq: current min freq 670
2020-05-03 00:47:31 driver-btm-api.c:1660:check_clock_counter: freq 670 clock_counter_limit 85
2020-05-03 00:47:33 thread.c:799:create_check_system_status_thread: create thread
2020-05-03 00:47:33 driver-btm-api.c:2113:bitmain_soc_init: Init done!
2020-05-03 00:47:33 driver-btm-api.c:201:set_miner_status: STATUS_INIT
2020-05-03 00:47:38 driver-btm-api.c:201:set_miner_status: STATUS_OKAY
2020-05-03 00:48:14 driver-btm-api.c:1293:dhash_chip_send_job: Version num 4
2020-05-03 00:53:13 thread.c:422:is_zero_nonce_happened: chain_nonce[0] = 15397
2020-05-03 00:53:13 thread.c:422:is_zero_nonce_happened: chain_nonce[1] = 14678
2020-05-03 00:53:13 thread.c:422:is_zero_nonce_happened: chain_nonce[2] = 12461
2020-05-03 01:18:14 thread.c:204:calc_hashrate_avg: avg rate is 39088.74 in 30 mins
2020-05-03 01:18:14 temperature.c:450:temp_statistics_show: pcb temp 42~56 chip temp 64~80
2020-05-03 01:18:14 thread.c:285:check_hashrate: latest avg rate < 0.98......
2020-05-03 01:18:14 thread.c:286:check_hashrate: current PCB min temperature 42
2020-05-03 01:18:14 thread.c:287:check_hashrate: current voltage is 17.10V, working voltage is 17.10V
2020-05-03 01:18:14 thread.c:318:check_hashrate: high temp, increase voltage 0.1V/0.2V to 17.20V
2020-05-03 01:18:14 driver-btm-api.c:2124:bitmain_reopen_core: reopen_core start!
2020-05-03 01:18:20 driver-btm-api.c:1067:init_miner_version: miner ID : 8042750618c0885c
2020-05-03 01:18:20 driver-btm-api.c:1073:init_miner_version: FPGA Version = 0xB013
2020-05-03 01:18:21 chain = 0, mode = 0, load_done = false.
2020-05-03 01:18:21 chain = 1, mode = 0, load_done = false.
2020-05-03 01:18:21 chain = 2, mode = 0, load_done = false.
2020-05-03 01:18:22 chain = 0, mode = 0, load_done = false.
2020-05-03 01:18:22 chain = 1, mode = 0, load_done = false.
2020-05-03 01:18:22 chain = 2, mode = 0, load_done = false.
2020-05-03 01:18:22 eeprom.c:425:check_pattern_test_level: invalid pattern test result. ignore
2020-05-03 01:18:23 chain = 0, mode = 0, load_done = false.
2020-05-03 01:18:23 chain = 1, mode = 0, load_done = false.
2020-05-03 01:18:23 chain = 2, mode = 0, load_done = false.
2020-05-03 01:18:24 chain = 0, mode = 0, load_done = false.
2020-05-03 01:18:24 chain = 1, mode = 0, load_done = false.
2020-05-03 01:18:24 chain = 2, mode = 0, load_done = false.
2020-05-03 01:18:24 eeprom.c:425:check_pattern_test_level: invalid pattern test result. ignore
2020-05-03 01:18:25 chain = 0, mode = 0, load_done = false.
2020-05-03 01:18:25 chain = 1, mode = 0, load_done = false.
2020-05-03 01:18:25 chain = 2, mode = 0, load_done = false.
2020-05-03 01:18:26 chain = 0, mode = 0, load_done = false.
2020-05-03 01:18:26 chain = 1, mode = 0, load_done = false.
2020-05-03 01:18:26 chain = 2, mode = 0, load_done = false.
2020-05-03 01:18:26 eeprom.c:425:check_pattern_test_level: invalid pattern test result. ignore
2020-05-03 01:18:26 driver-btm-api.c:705:get_product_id: product_id[0] = 1
2020-05-03 01:18:26 driver-btm-api.c:705:get_product_id: product_id[1] = 1
2020-05-03 01:18:26 driver-btm-api.c:705:get_product_id: product_id[2] = 1
2020-05-03 01:18:26 driver-btm-api.c:1633:get_ccdly_opt: ccdly_opt[0] = 1
2020-05-03 01:18:26 driver-btm-api.c:1633:get_ccdly_opt: ccdly_opt[1] = 1
2020-05-03 01:18:26 driver-btm-api.c:1633:get_ccdly_opt: ccdly_opt[2] = 1
2020-05-03 01:18:26 driver-btm-api.c:1877:bitmain_board_init: g_ccdly_opt = 1
2020-05-03 01:18:26 driver-btm-api.c:644:_set_project_type: project:2
2020-05-03 01:18:26 driver-btm-api.c:674:_set_project_type: Project type: Antminer T17
2020-05-03 01:18:26 driver-btm-api.c:685:dump_pcb_bom_version: Chain [0] PCB Version: 0x0100
2020-05-03 01:18:26 driver-btm-api.c:686:dump_pcb_bom_version: Chain [0] BOM Version: 0x0100
2020-05-03 01:18:26 driver-btm-api.c:685:dump_pcb_bom_version: Chain [1] PCB Version: 0x0100
2020-05-03 01:18:26 driver-btm-api.c:686:dump_pcb_bom_version: Chain [1] BOM Version: 0x0100
2020-05-03 01:18:26 driver-btm-api.c:685:dump_pcb_bom_version: Chain [2] PCB Version: 0x0100
2020-05-03 01:18:26 driver-btm-api.c:686:dump_pcb_bom_version: Chain [2] BOM Version: 0x0100
2020-05-03 01:18:28 driver-btm-api.c:1897:bitmain_board_init: Fan check passed.
2020-05-03 01:18:28 register.c:283:get_register: !!! reg crc error
2020-05-03 01:18:30 board.c:36:jump_and_app_check_restore_pic: chain[0] PIC jump to app
2020-05-03 01:18:36 board.c:40:jump_and_app_check_restore_pic: Check chain[0] PIC fw version=0xb9
2020-05-03 01:18:38 board.c:36:jump_and_app_check_restore_pic: chain[1] PIC jump to app
2020-05-03 01:18:41 board.c:40:jump_and_app_check_restore_pic: Check chain[1] PIC fw version=0xb9
2020-05-03 01:18:43 board.c:36:jump_and_app_check_restore_pic: chain[2] PIC jump to app
2020-05-03 01:18:48 board.c:40:jump_and_app_check_restore_pic: Check chain[2] PIC fw version=0xb9
2020-05-03 01:18:48 power_api.c:55:power_init: power init ...
2020-05-03 01:18:48 driver-btm-api.c:1907:bitmain_board_init: Enter 30s sleep to make sure power release finish.
2020-05-03 01:19:20 power_api.c:232:set_iic_power_to_highest_voltage: setting to voltage: 17.00 ...
2020-05-03 01:19:24 power_api.c:124:check_voltage_multi: retry time: 0
2020-05-03 01:19:25 power_api.c:86:get_average_voltage: chain[0], voltage is: 17.120039
2020-05-03 01:19:27 power_api.c:86:get_average_voltage: chain[1], voltage is: 17.113916
2020-05-03 01:19:29 power_api.c:86:get_average_voltage: chain[2], voltage is: 17.224131
2020-05-03 01:19:29 power_api.c:97:get_average_voltage: aveage voltage is: 17.152695
2020-05-03 01:19:29 power_api.c:182:set_iic_power_by_voltage: now set voltage to : 17.000000
2020-05-03 01:19:29 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[0]: chip baud = 115200, chip_divider = 26
2020-05-03 01:19:29 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[1]: chip baud = 115200, chip_divider = 26
2020-05-03 01:19:29 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[2]: chip baud = 115200, chip_divider = 26
2020-05-03 01:19:29 uart.c:80:set_baud: set fpga_baud = 115200, fpga_divider = 26
2020-05-03 01:19:40 driver-btm-api.c:1010:check_asic_number_with_power_on: Chain[0]: find 30 asic, times 0
2020-05-03 01:19:50 driver-btm-api.c:1010:check_asic_number_with_power_on: Chain[1]: find 30 asic, times 0
2020-05-03 01:20:01 driver-btm-api.c:1010:check_asic_number_with_power_on: Chain[2]: find 23 asic, times 0
2020-05-03 01:20:11 driver-btm-api.c:1010:check_asic_number_with_power_on: Chain[2]: find 23 asic, times 1
2020-05-03 01:20:20 driver-btm-api.c:1010:check_asic_number_with_power_on: Chain[2]: find 23 asic, times 2
2020-05-03 01:20:20 driver-btm-api.c:1037:check_asic_number: Chain 2 only find 23 asic, will power off hash board 2
2020-05-03 01:20:26 driver-btm-api.c:348:set_order_clock: chain[0]: set order clock, stragegy 3 clock_en=0x1
2020-05-03 01:20:26 driver-btm-api.c:348:set_order_clock: chain[1]: set order clock, stragegy 3 clock_en=0x1
2020-05-03 01:20:26 driver-hash-chip.c:490:set_clock_delay_control: core_data = 0xb4
2020-05-03 01:20:27 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[0]: chip baud = 3000000, chip_divider = 0
2020-05-03 01:20:27 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[1]: chip baud = 3000000, chip_divider = 0
2020-05-03 01:20:27 uart.c:80:set_baud: set fpga_baud = 3000000, fpga_divider = 0
2020-05-03 01:20:27 driver-btm-api.c:1660:check_clock_counter: freq 50 clock_counter_limit 6
2020-05-03 01:20:27 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[0]: chip baud = 115200, chip_divider = 26
2020-05-03 01:20:27 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[1]: chip baud = 115200, chip_divider = 26
2020-05-03 01:20:27 uart.c:80:set_baud: set fpga_baud = 115200, fpga_divider = 26
2020-05-03 01:20:27 voltage[0] = 1710
2020-05-03 01:20:27 voltage[1] = 1710
2020-05-03 01:20:27 power_api.c:140:set_working_voltage: working_voltage = 17.100000
2020-05-03 01:20:28 temperature.c:282:calibrate_temp_sensor_one_chain: Temperature sensor calibration: chain 0 success.
2020-05-03 01:20:30 temperature.c:282:calibrate_temp_sensor_one_chain: Temperature sensor calibration: chain 1 success.
2020-05-03 01:20:30 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[0]: chip baud = 6000000, chip_divider = 7
2020-05-03 01:20:30 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[1]: chip baud = 6000000, chip_divider = 7
2020-05-03 01:20:30 uart.c:80:set_baud: set fpga_baud = 6000000, fpga_divider = 3
2020-05-03 01:20:31 driver-btm-api.c:248:check_bringup_temp: Bring up temperature is 20
2020-05-03 01:20:31 driver-btm-api.c:581:calculate_timeout: dev->timeout = 392
2020-05-03 01:20:31 power_api.c:379:slowly_set_iic_power_to_custom_voltage: slowly setting to voltage: 18.00 ...
2020-05-03 01:21:00 power_api.c:124:check_voltage_multi: retry time: 0
2020-05-03 01:21:02 power_api.c:86:get_average_voltage: chain[0], voltage is: 18.160957
2020-05-03 01:21:03 power_api.c:86:get_average_voltage: chain[1], voltage is: 18.148711
2020-05-03 01:21:03 power_api.c:97:get_average_voltage: aveage voltage is: 18.154834
2020-05-03 01:21:03 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 42 set refdiv: 2, fbdiv: 168, postdiv1: 7, postdiv2: 7, usr divider: 1
2020-05-03 01:21:04 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 50 set refdiv: 2, fbdiv: 168, postdiv1: 7, postdiv2: 6, usr divider: 1
2020-05-03 01:21:04 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 60 set refdiv: 2, fbdiv: 168, postdiv1: 7, postdiv2: 5, usr divider: 1
2020-05-03 01:21:04 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 75 set refdiv: 2, fbdiv: 168, postdiv1: 7, postdiv2: 4, usr divider: 1
2020-05-03 01:21:04 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 100 set refdiv: 2, fbdiv: 168, postdiv1: 7, postdiv2: 3, usr divider: 1
2020-05-03 01:21:04 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 150 set refdiv: 2, fbdiv: 168, postdiv1: 7, postdiv2: 2, usr divider: 1
2020-05-03 01:21:04 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 300 set refdiv: 2, fbdiv: 168, postdiv1: 7, postdiv2: 1, usr divider: 1
2020-05-03 01:21:04 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 350 set refdiv: 2, fbdiv: 168, postdiv1: 6, postdiv2: 1, usr divider: 1
2020-05-03 01:21:04 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 420 set refdiv: 2, fbdiv: 168, postdiv1: 5, postdiv2: 1, usr divider: 1
2020-05-03 01:21:04 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 525 set refdiv: 2, fbdiv: 168, postdiv1: 4, postdiv2: 1, usr divider: 1
2020-05-03 01:21:05 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 700 set refdiv: 2, fbdiv: 168, postdiv1: 3, postdiv2: 1, usr divider: 1
2020-05-03 01:21:05 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 41 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 7, usr divider: 1
2020-05-03 01:21:05 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 47 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 6, usr divider: 1
2020-05-03 01:21:05 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 57 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 5, usr divider: 1
2020-05-03 01:21:05 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 71 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 4, usr divider: 1
2020-05-03 01:21:05 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 95 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 3, usr divider: 1
2020-05-03 01:21:05 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 143 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 2, usr divider: 1
2020-05-03 01:21:05 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 287 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 1, usr divider: 1
2020-05-03 01:21:05 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 335 set refdiv: 2, fbdiv: 161, postdiv1: 6, postdiv2: 1, usr divider: 1
2020-05-03 01:21:05 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 402 set refdiv: 2, fbdiv: 161, postdiv1: 5, postdiv2: 1, usr divider: 1
2020-05-03 01:21:06 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 503 set refdiv: 2, fbdiv: 161, postdiv1: 4, postdiv2: 1, usr divider: 1
2020-05-03 01:21:06 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 670 set refdiv: 2, fbdiv: 161, postdiv1: 3, postdiv2: 1, usr divider: 1
2020-05-03 01:21:06 driver-btm-api.c:612:set_timeout: freq 700 final timeout=168
2020-05-03 01:21:06 power_api.c:146:set_higher_voltage: higher_voltage = 18.000000
2020-05-03 01:21:06 power_api.c:428:slowly_set_iic_power_to_higher_voltage: slowly setting to voltage: 18.00 ...
2020-05-03 01:21:25 power_api.c:124:check_voltage_multi: retry time: 0
2020-05-03 01:21:27 power_api.c:86:get_average_voltage: chain[0], voltage is: 18.142588
2020-05-03 01:21:29 power_api.c:86:get_average_voltage: chain[1], voltage is: 18.124219
2020-05-03 01:21:29 power_api.c:97:get_average_voltage: aveage voltage is: 18.133403
2020-05-03 01:21:29 driver-btm-api.c:2186:bitmain_reopen_core: reopen_core done!
2020-05-03 01:21:29 power_api.c:379:slowly_set_iic_power_to_custom_voltage: slowly setting to voltage: 17.20 ...
2020-05-03 01:22:04 power_api.c:124:check_voltage_multi: retry time: 0
2020-05-03 01:22:06 power_api.c:86:get_average_voltage: chain[0], voltage is: 17.297607
2020-05-03 01:22:08 power_api.c:86:get_average_voltage: chain[1], voltage is: 17.279238
2020-05-03 01:22:08 power_api.c:97:get_average_voltage: aveage voltage is: 17.288423
2020-05-03 01:22:08 power_api.c:140:set_working_voltage: working_voltage = 17.200001
2020-05-03 01:27:07 thread.c:422:is_zero_nonce_happened: chain_nonce[0] = 109508
2020-05-03 01:27:07 thread.c:422:is_zero_nonce_happened: chain_nonce[1] = 104312
2020-05-03 01:52:08 thread.c:204:calc_hashrate_avg: avg rate is 27576.08 in 30 mins
2020-05-03 01:52:08 temperature.c:450:temp_statistics_show: pcb temp 42~56 chip temp 65~80
2020-05-03 02:22:09 thread.c:204:calc_hashrate_avg: avg rate is 27625.39 in 30 mins
2020-05-03 02:22:09 temperature.c:450:temp_statistics_show: pcb temp 42~56 chip temp 64~79
Miner Status Screen: https://drive.google.com/file/d/1W87ewVEAnAqcX6uh8zDsLQMMoYNa7jg-/view?usp=sharing Things to Note: (Its rebooted a few times - this is what I could get for the kernel log) 2020-05-03 01:20:01 driver-btm-api.c:1010:check_asic_number_with_power_on: Chain[2]: find 23 asic, times 0
2020-05-03 01:20:11 driver-btm-api.c:1010:check_asic_number_with_power_on: Chain[2]: find 23 asic, times 1
2020-05-03 01:20:20 driver-btm-api.c:1010:check_asic_number_with_power_on: Chain[2]: find 23 asic, times 2
2020-05-03 01:20:20 driver-btm-api.c:1037:check_asic_number: Chain 2 only find 23 asic, will power off hash board 2
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: mikeywith on May 03, 2020, 05:04:55 AM
2020-05-03 01:52:08 temperature.c:450:temp_statistics_show: pcb temp 42~56 chip temp 65~80
2020-05-03 02:22:09 thread.c:204:calc_hashrate_avg: avg rate is 27625.39 in 30 mins
2020-05-03 02:22:09 temperature.c:450:temp_statistics_show: pcb temp 42~56 chip temp 64~79 Your temps are pretty high, chain 2 does show less ASICs than it should but that's not your only issue, your temps are pretty high forcing the miner to lower the voltage/frequency which may cause it to be unstable and then reboot/stop mining. When you remove the third board (Chain 2) the other two boards will cool down and there is a good chance they will mine on without an issue and you will think that chain 2 was the only problem when actually you have a heat problem. I suggest you set the fans at 100% and see if the miner works more stable with these settings if you don't know how to set a fixed speed for those fans let me know I'll show you.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: mysticbitcoin on May 03, 2020, 03:20:28 PM
Mikey, This is the only one of the T17s giving me grief. The ambient environment temp being an average of 22 degrees Celsius to a maximum of 24 degrees Celsius. The highest the boards get according to the logs is 45 Degrees, which is within operating spec according to Bitmain. But I agree with what your saying according to the logs. The funny thing is I was so fustrated I opened her up and re-seated the Chain [2] Cable (take it out and plug it in on the Hashboard side) and she came up online all 30 chips recognized. Could the cable be a problem? Ive never heard of such a case but Bitmain always gives a default trouble shooting of replacing the controller to hashboard cables (although I've never found that they have been particularly helpful). Here is the most Kernel recent log, running all night since I re-seated the cable. Booting Linux on physical CPU 0x0
Linux version 4.6.0-xilinx-gff8137b-dirty (lzq@armdev2) (gcc version 4.8.3 20140320 (prerelease) (Sourcery CodeBench Lite 2014.05-23) ) #25 SMP PREEMPT Fri Nov 23 15:30:52 CST 2018
CPU: ARMv7 Processor [413fc090] revision 0 (ARMv7), cr=18c5387d
CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
Machine model: Xilinx Zynq
cma: Reserved 16 MiB at 0x0e000000
Memory policy: Data cache writealloc
On node 0 totalpages: 61440
free_area_init_node: node 0, pgdat c0b39280, node_mem_map cde10000
Normal zone: 480 pages used for memmap
Normal zone: 0 pages reserved
Normal zone: 61440 pages, LIFO batch:15
percpu: Embedded 12 pages/cpu @cddf1000 s19776 r8192 d21184 u49152
pcpu-alloc: s19776 r8192 d21184 u49152 alloc=12*4096
pcpu-alloc: [0] 0 [0] 1
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 60960
Kernel command line: mem=240M console=ttyPS0,115200 ramdisk_size=33554432 root=/dev/ram rw earlyprintk
PID hash table entries: 1024 (order: 0, 4096 bytes)
Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
Memory: 203756K/245760K available (6345K kernel code, 231K rwdata, 1896K rodata, 1024K init, 223K bss, 25620K reserved, 16384K cma-reserved, 0K highmem)
Virtual kernel memory layout:
vector : 0xffff0000 - 0xffff1000 ( 4 kB)
fixmap : 0xffc00000 - 0xfff00000 (3072 kB)
vmalloc : 0xcf800000 - 0xff800000 ( 768 MB)
lowmem : 0xc0000000 - 0xcf000000 ( 240 MB)
pkmap : 0xbfe00000 - 0xc0000000 ( 2 MB)
modules : 0xbf000000 - 0xbfe00000 ( 14 MB)
.text : 0xc0008000 - 0xc090c424 (9234 kB)
.init : 0xc0a00000 - 0xc0b00000 (1024 kB)
.data : 0xc0b00000 - 0xc0b39fe0 ( 232 kB)
.bss : 0xc0b39fe0 - 0xc0b71c28 ( 224 kB)
Preemptible hierarchical RCU implementation.
Build-time adjustment of leaf fanout to 32.
RCU restricting CPUs from NR_CPUS=4 to nr_cpu_ids=2.
RCU: Adjusting geometry for rcu_fanout_leaf=32, nr_cpu_ids=2
NR_IRQS:16 nr_irqs:16 16
efuse mapped to cf800000
ps7-slcr mapped to cf802000
L2C: platform modifies aux control register: 0x72360000 -> 0x72760000
L2C: DT/platform modifies aux control register: 0x72360000 -> 0x72760000
L2C-310 erratum 769419 enabled
L2C-310 enabling early BRESP for Cortex-A9
L2C-310 full line of zeros enabled for Cortex-A9
L2C-310 ID prefetch enabled, offset 1 lines
L2C-310 dynamic clock gating enabled, standby mode enabled
L2C-310 cache controller enabled, 8 ways, 512 kB
L2C-310: CACHE_ID 0x410000c8, AUX_CTRL 0x76760001
zynq_clock_init: clkc starts at cf802100
Zynq clock init
sched_clock: 64 bits at 333MHz, resolution 3ns, wraps every 4398046511103ns
clocksource: arm_global_timer: mask: 0xffffffffffffffff max_cycles: 0x4ce07af025, max_idle_ns: 440795209040 ns
Switching to timer-based delay loop, resolution 3ns
clocksource: ttc_clocksource: mask: 0xffff max_cycles: 0xffff, max_idle_ns: 537538477 ns
ps7-ttc #0 at cf80a000, irq=18
Console: colour dummy device 80x30
Calibrating delay loop (skipped), value calculated using timer frequency.. 666.66 BogoMIPS (lpj=3333333)
pid_max: default: 32768 minimum: 301
Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
CPU: Testing write buffer coherency: ok
CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
Setting up static identity map for 0x100000 - 0x100058
CPU1: failed to boot: -1
Brought up 1 CPUs
SMP: Total of 1 processors activated (666.66 BogoMIPS).
CPU: All CPU(s) started in SVC mode.
devtmpfs: initialized
VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4
clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
pinctrl core: initialized pinctrl subsystem
NET: Registered protocol family 16
DMA: preallocated 256 KiB pool for atomic coherent allocations
cpuidle: using governor menu
hw-breakpoint: found 5 (+1 reserved) breakpoint and 1 watchpoint registers.
hw-breakpoint: maximum watchpoint size is 4 bytes.
zynq-ocm f800c000.ps7-ocmc: ZYNQ OCM pool: 256 KiB @ 0xcf880000
vgaarb: loaded
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
media: Linux media interface: v0.10
Linux video capture interface: v2.00
pps_core: LinuxPPS API ver. 1 registered
pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
PTP clock support registered
EDAC MC: Ver: 3.0.0
Advanced Linux Sound Architecture Driver Initialized.
clocksource: Switched to clocksource arm_global_timer
NET: Registered protocol family 2
TCP established hash table entries: 2048 (order: 1, 8192 bytes)
TCP bind hash table entries: 2048 (order: 2, 16384 bytes)
TCP: Hash tables configured (established 2048 bind 2048)
UDP hash table entries: 256 (order: 1, 8192 bytes)
UDP-Lite hash table entries: 256 (order: 1, 8192 bytes)
NET: Registered protocol family 1
RPC: Registered named UNIX socket transport module.
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
PCI: CLS 0 bytes, default 64
Trying to unpack rootfs image as initramfs...
rootfs image is not initramfs (no cpio magic); looks like an initrd
Freeing initrd memory: 12580K (cceb8000 - cdb01000)
hw perfevents: enabled with armv7_cortex_a9 PMU driver, 7 counters available
futex hash table entries: 512 (order: 3, 32768 bytes)
workingset: timestamp_bits=28 max_order=16 bucket_order=0
jffs2: version 2.2. (NAND) (SUMMARY) © 2001-2006 Red Hat, Inc.
io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered (default)
dma-pl330 f8003000.ps7-dma: Loaded driver for PL330 DMAC-241330
dma-pl330 f8003000.ps7-dma: DBUFF-128x8bytes Num_Chans-8 Num_Peri-4 Num_Events-16
e0000000.serial: ttyPS0 at MMIO 0xe0000000 (irq = 158, base_baud = 6249999) is a xuartps
console [ttyPS0] enabled
xdevcfg f8007000.ps7-dev-cfg: ioremap 0xf8007000 to cf86e000
[drm] Initialized drm 1.1.0 20060810
brd: module loaded
loop: module loaded
CAN device driver interface
gpiod_set_value: invalid GPIO
libphy: MACB_mii_bus: probed
macb e000b000.ethernet eth0: Cadence GEM rev 0x00020118 at 0xe000b000 irq 31 (00:0a:35:00:00:00)
Generic PHY e000b000.etherne:00: attached PHY driver [Generic PHY] (mii_bus:phy_addr=e000b000.etherne:00, irq=-1)
e1000e: Intel(R) PRO/1000 Network Driver - 3.2.6-k
e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
ehci-pci: EHCI PCI platform driver
usbcore: registered new interface driver usb-storage
mousedev: PS/2 mouse device common for all mice
i2c /dev entries driver
Xilinx Zynq CpuIdle Driver started
sdhci: Secure Digital Host Controller Interface driver
sdhci: Copyright(c) Pierre Ossman
sdhci-pltfm: SDHCI platform and OF driver helper
mmc0: SDHCI controller on e0100000.ps7-sdio [e0100000.ps7-sdio] using ADMA
ledtrig-cpu: registered to indicate activity on CPUs
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
nand: device found, Manufacturer ID: 0x2c, Chip ID: 0xda
nand: Micron MT29F2G08ABAGAWP
nand: 256 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 128
nand: WARNING: pl35x-nand: the ECC used on your system is too weak compared to the one required by the NAND chip
Bad block table found at page 131008, version 0x01
Bad block table found at page 130944, version 0x01
6 ofpart partitions found on MTD device pl35x-nand
Creating 6 MTD partitions on "pl35x-nand":
0x000000000000-0x000002800000 : "BOOT.bin-env-dts-kernel"
0x000002800000-0x000004800000 : "ramfs"
0x000004800000-0x000005000000 : "configs"
0x000005000000-0x000006000000 : "reserve"
0x000006000000-0x000008000000 : "ramfs-bak"
0x000008000000-0x000010000000 : "reserve1"
NET: Registered protocol family 10
sit: IPv6 over IPv4 tunneling driver
NET: Registered protocol family 17
can: controller area network core (rev 20120528 abi 9)
NET: Registered protocol family 29
can: raw protocol (rev 20120528)
can: broadcast manager protocol (rev 20120528 t)
can: netlink gateway (rev 20130117) max_hops=1
zynq_pm_ioremap: no compatible node found for 'xlnx,zynq-ddrc-a05'
zynq_pm_late_init: Unable to map DDRC IO memory.
Registering SWP/SWPB emulation handler
hctosys: unable to open rtc device (rtc0)
ALSA device list:
No soundcards found.
RAMDISK: gzip image found at block 0
EXT4-fs (ram0): couldn't mount as ext3 due to feature incompatibilities
EXT4-fs (ram0): mounted filesystem without journal. Opts: (null)
VFS: Mounted root (ext4 filesystem) on device 1:0.
devtmpfs: mounted
Freeing unused kernel memory: 1024K (c0a00000 - c0b00000)
EXT4-fs (ram0): re-mounted. Opts: block_validity,delalloc,barrier,user_xattr
random: dd urandom read with 0 bits of entropy available
ubi0: attaching mtd2
ubi0: scanning is finished
ubi0: attached mtd2 (name "configs", size 8 MiB)
ubi0: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
ubi0: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
ubi0: VID header offset: 2048 (aligned 2048), data offset: 4096
ubi0: good PEBs: 64, bad PEBs: 0, corrupted PEBs: 0
ubi0: user volume: 1, internal volumes: 1, max. volumes count: 128
ubi0: max/mean erase counter: 6/2, WL threshold: 4096, image sequence number: 4244297529
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 01559AD8-7B6A-42E6-A3FE-EDF3659527A9, 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: 1052/340, WL threshold: 4096, image sequence number: 4185749592
ubi1: available PEBs: 0, total reserved PEBs: 1020, PEBs reserved for bad PEB handling: 36
ubi1: background thread "ubi_bgt1d" started, PID 720
UBIFS (ubi1:0): background thread "ubifs_bgt1_0" started, PID 723
UBIFS (ubi1:0): recovery needed
UBIFS (ubi1:0): recovery completed
UBIFS (ubi1:0): UBIFS: mounted UBI device 1, volume 0, name "reserve1"
UBIFS (ubi1:0): LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
UBIFS (ubi1:0): FS size: 123039744 bytes (117 MiB, 969 LEBs), journal size 6221824 bytes (5 MiB, 49 LEBs)
UBIFS (ubi1:0): reserved for root: 4952683 bytes (4836 KiB)
UBIFS (ubi1:0): media format: w4/r0 (latest is w4/r0), UUID 4829CF2C-7435-4146-B2FD-0826AAE8443A, small LPT model
IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
macb e000b000.ethernet eth0: unable to generate target frequency: 25000000 Hz
macb e000b000.ethernet eth0: link up (100/Full)
IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
In axi fpga driver!
request_mem_region OK!
AXI fpga dev virtual address is 0xcfb38000
*base_vir_addr = 0xab013
In fpga mem driver!
request_mem_region OK!
fpga mem virtual address is 0xd2000000
random: nonblocking pool is initialized
2020-05-03 04:09:50 driver-btm-api.c:631:init_freq_mode: This is scan-user version
2020-05-03 04:09:50 driver-btm-api.c:1994:bitmain_soc_init: opt_multi_version = 1
2020-05-03 04:09:50 driver-btm-api.c:1995:bitmain_soc_init: opt_bitmain_ab = 1
2020-05-03 04:09:50 driver-btm-api.c:1996:bitmain_soc_init: opt_bitmain_work_mode = 0
2020-05-03 04:09:50 driver-btm-api.c:1997:bitmain_soc_init: Miner compile time: Tue Dec 24 16:13:07 CST 2019 type: Antminer T17
2020-05-03 04:09:50 driver-btm-api.c:1998:bitmain_soc_init: commit version: e93a09b 2019-12-24 16:03:45, build by: lol 2019-12-24 16:19:49
2020-05-03 04:09:50 driver-btm-api.c:1810:show_sn: no SN got, please write SN to /nvdata/sn
2020-05-03 04:09:50 driver-btm-api.c:1135:miner_device_init: Detect 256MB control board of XILINX
2020-05-03 04:09:50 driver-btm-api.c:1083:init_fan_parameter: fan_eft : 0 fan_pwm : 0
2020-05-03 04:09:50 thread.c:789:create_read_nonce_reg_thread: create thread
2020-05-03 04:09:56 driver-btm-api.c:1067:init_miner_version: miner ID : 8042750618c0885c
2020-05-03 04:09:56 driver-btm-api.c:1073:init_miner_version: FPGA Version = 0xB013
2020-05-03 04:09:58 eeprom.c:425:check_pattern_test_level: invalid pattern test result. ignore
2020-05-03 04:10:00 eeprom.c:425:check_pattern_test_level: invalid pattern test result. ignore
2020-05-03 04:10:02 eeprom.c:425:check_pattern_test_level: invalid pattern test result. ignore
2020-05-03 04:10:02 driver-btm-api.c:705:get_product_id: product_id[0] = 1
2020-05-03 04:10:02 driver-btm-api.c:705:get_product_id: product_id[1] = 1
2020-05-03 04:10:02 driver-btm-api.c:705:get_product_id: product_id[2] = 1
2020-05-03 04:10:02 driver-btm-api.c:1633:get_ccdly_opt: ccdly_opt[0] = 1
2020-05-03 04:10:02 driver-btm-api.c:1633:get_ccdly_opt: ccdly_opt[1] = 1
2020-05-03 04:10:02 driver-btm-api.c:1633:get_ccdly_opt: ccdly_opt[2] = 1
2020-05-03 04:10:02 driver-btm-api.c:1877:bitmain_board_init: g_ccdly_opt = 1
2020-05-03 04:10:02 driver-btm-api.c:644:_set_project_type: project:2
2020-05-03 04:10:02 driver-btm-api.c:674:_set_project_type: Project type: Antminer T17
2020-05-03 04:10:02 driver-btm-api.c:685:dump_pcb_bom_version: Chain [0] PCB Version: 0x0100
2020-05-03 04:10:02 driver-btm-api.c:686:dump_pcb_bom_version: Chain [0] BOM Version: 0x0100
2020-05-03 04:10:02 driver-btm-api.c:685:dump_pcb_bom_version: Chain [1] PCB Version: 0x0100
2020-05-03 04:10:02 driver-btm-api.c:686:dump_pcb_bom_version: Chain [1] BOM Version: 0x0100
2020-05-03 04:10:02 driver-btm-api.c:685:dump_pcb_bom_version: Chain [2] PCB Version: 0x0100
2020-05-03 04:10:02 driver-btm-api.c:686:dump_pcb_bom_version: Chain [2] BOM Version: 0x0100
2020-05-03 04:10:04 driver-btm-api.c:1897:bitmain_board_init: Fan check passed.
2020-05-03 04:10:05 board.c:36:jump_and_app_check_restore_pic: chain[0] PIC jump to app
2020-05-03 04:10:09 board.c:40:jump_and_app_check_restore_pic: Check chain[0] PIC fw version=0xb9
2020-05-03 04:10:11 board.c:36:jump_and_app_check_restore_pic: chain[1] PIC jump to app
2020-05-03 04:10:14 board.c:40:jump_and_app_check_restore_pic: Check chain[1] PIC fw version=0xb9
2020-05-03 04:10:16 board.c:36:jump_and_app_check_restore_pic: chain[2] PIC jump to app
2020-05-03 04:10:19 board.c:40:jump_and_app_check_restore_pic: Check chain[2] PIC fw version=0xb9
2020-05-03 04:10:19 thread.c:784:create_pic_heart_beat_thread: create thread
2020-05-03 04:10:19 power_api.c:55:power_init: power init ...
2020-05-03 04:10:19 driver-btm-api.c:1907:bitmain_board_init: Enter 30s sleep to make sure power release finish.
2020-05-03 04:10:19 power_api.c:46:power_off: init gpio907
2020-05-03 04:10:51 power_api.c:232:set_iic_power_to_highest_voltage: setting to voltage: 17.00 ...
2020-05-03 04:10:57 power_api.c:124:check_voltage_multi: retry time: 0
2020-05-03 04:10:59 power_api.c:86:get_average_voltage: chain[0], voltage is: 21.253095
2020-05-03 04:11:01 power_api.c:86:get_average_voltage: chain[1], voltage is: 20.573437
2020-05-03 04:11:02 power_api.c:86:get_average_voltage: chain[2], voltage is: 20.071347
2020-05-03 04:11:02 power_api.c:97:get_average_voltage: aveage voltage is: 20.632627
2020-05-03 04:11:02 power_api.c:110:check_voltage: target_vol = 17.00, actural_vol = 20.63, more than 1.0v diff.
2020-05-03 04:11:03 power_api.c:124:check_voltage_multi: retry time: 1
2020-05-03 04:11:05 power_api.c:86:get_average_voltage: chain[0], voltage is: 19.048799
2020-05-03 04:11:07 power_api.c:86:get_average_voltage: chain[1], voltage is: 18.454863
2020-05-03 04:11:10 power_api.c:86:get_average_voltage: chain[2], voltage is: 17.622129
2020-05-03 04:11:10 power_api.c:97:get_average_voltage: aveage voltage is: 18.375263
2020-05-03 04:11:10 power_api.c:110:check_voltage: target_vol = 17.00, actural_vol = 18.38, more than 1.0v diff.
2020-05-03 04:11:11 power_api.c:124:check_voltage_multi: retry time: 2
2020-05-03 04:11:13 power_api.c:86:get_average_voltage: chain[0], voltage is: 16.599580
2020-05-03 04:11:16 power_api.c:86:get_average_voltage: chain[1], voltage is: 15.748476
2020-05-03 04:11:18 power_api.c:86:get_average_voltage: chain[2], voltage is: 17.456806
2020-05-03 04:11:18 power_api.c:97:get_average_voltage: aveage voltage is: 16.601621
2020-05-03 04:11:18 power_api.c:182:set_iic_power_by_voltage: now set voltage to : 17.000000
2020-05-03 04:11:18 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[0]: chip baud = 115200, chip_divider = 26
2020-05-03 04:11:18 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[1]: chip baud = 115200, chip_divider = 26
2020-05-03 04:11:18 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[2]: chip baud = 115200, chip_divider = 26
2020-05-03 04:11:18 uart.c:80:set_baud: set fpga_baud = 115200, fpga_divider = 26
2020-05-03 04:11:28 driver-btm-api.c:1010:check_asic_number_with_power_on: Chain[0]: find 30 asic, times 0
2020-05-03 04:11:38 driver-btm-api.c:1010:check_asic_number_with_power_on: Chain[1]: find 30 asic, times 0
2020-05-03 04:11:49 driver-btm-api.c:1010:check_asic_number_with_power_on: Chain[2]: find 30 asic, times 0
2020-05-03 04:11:52 driver-btm-api.c:348:set_order_clock: chain[0]: set order clock, stragegy 3 clock_en=0x1
2020-05-03 04:11:52 driver-btm-api.c:348:set_order_clock: chain[1]: set order clock, stragegy 3 clock_en=0x1
2020-05-03 04:11:52 driver-btm-api.c:348:set_order_clock: chain[2]: set order clock, stragegy 3 clock_en=0x1
2020-05-03 04:11:53 driver-hash-chip.c:490:set_clock_delay_control: core_data = 0xb4
2020-05-03 04:11:53 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[0]: chip baud = 3000000, chip_divider = 0
2020-05-03 04:11:53 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[1]: chip baud = 3000000, chip_divider = 0
2020-05-03 04:11:53 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[2]: chip baud = 3000000, chip_divider = 0
2020-05-03 04:11:53 uart.c:80:set_baud: set fpga_baud = 3000000, fpga_divider = 0
2020-05-03 04:11:53 driver-btm-api.c:1660:check_clock_counter: freq 50 clock_counter_limit 6
2020-05-03 04:11:53 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[0]: chip baud = 115200, chip_divider = 26
2020-05-03 04:11:53 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[1]: chip baud = 115200, chip_divider = 26
2020-05-03 04:11:53 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[2]: chip baud = 115200, chip_divider = 26
2020-05-03 04:11:53 uart.c:80:set_baud: set fpga_baud = 115200, fpga_divider = 26
2020-05-03 04:11:53 voltage[0] = 1710
2020-05-03 04:11:53 voltage[1] = 1710
2020-05-03 04:11:53 voltage[2] = 1710
2020-05-03 04:11:53 power_api.c:140:set_working_voltage: working_voltage = 17.100000
2020-05-03 04:11:55 temperature.c:282:calibrate_temp_sensor_one_chain: Temperature sensor calibration: chain 0 success.
2020-05-03 04:11:56 temperature.c:282:calibrate_temp_sensor_one_chain: Temperature sensor calibration: chain 1 success.
2020-05-03 04:11:57 temperature.c:282:calibrate_temp_sensor_one_chain: Temperature sensor calibration: chain 2 success.
2020-05-03 04:11:57 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[0]: chip baud = 6000000, chip_divider = 7
2020-05-03 04:11:57 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[1]: chip baud = 6000000, chip_divider = 7
2020-05-03 04:11:57 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[2]: chip baud = 6000000, chip_divider = 7
2020-05-03 04:11:57 uart.c:80:set_baud: set fpga_baud = 6000000, fpga_divider = 3
2020-05-03 04:11:59 driver-btm-api.c:248:check_bringup_temp: Bring up temperature is 20
2020-05-03 04:11:59 thread.c:804:create_check_miner_status_thread: create thread
2020-05-03 04:11:59 thread.c:794:create_set_miner_status_thread: create thread
2020-05-03 04:11:59 driver-btm-api.c:581:calculate_timeout: dev->timeout = 392
2020-05-03 04:11:59 thread.c:779:create_temperature_monitor_thread: create thread
2020-05-03 04:11:59 freq_tuning.c:154:freq_tuning_get_max_freq: Max freq of tuning is 760
2020-05-03 04:11:59 power_api.c:379:slowly_set_iic_power_to_custom_voltage: slowly setting to voltage: 18.00 ...
2020-05-03 04:12:35 power_api.c:124:check_voltage_multi: retry time: 0
2020-05-03 04:12:37 power_api.c:86:get_average_voltage: chain[0], voltage is: 18.142588
2020-05-03 04:12:39 power_api.c:86:get_average_voltage: chain[1], voltage is: 18.124219
2020-05-03 04:12:40 power_api.c:86:get_average_voltage: chain[2], voltage is: 18.240556
2020-05-03 04:12:40 power_api.c:97:get_average_voltage: aveage voltage is: 18.169121
2020-05-03 04:12:40 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 42 set refdiv: 2, fbdiv: 168, postdiv1: 7, postdiv2: 7, usr divider: 1
2020-05-03 04:12:41 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 50 set refdiv: 2, fbdiv: 168, postdiv1: 7, postdiv2: 6, usr divider: 1
2020-05-03 04:12:41 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 60 set refdiv: 2, fbdiv: 168, postdiv1: 7, postdiv2: 5, usr divider: 1
2020-05-03 04:12:41 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 75 set refdiv: 2, fbdiv: 168, postdiv1: 7, postdiv2: 4, usr divider: 1
2020-05-03 04:12:41 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 100 set refdiv: 2, fbdiv: 168, postdiv1: 7, postdiv2: 3, usr divider: 1
2020-05-03 04:12:41 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 150 set refdiv: 2, fbdiv: 168, postdiv1: 7, postdiv2: 2, usr divider: 1
2020-05-03 04:12:41 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 300 set refdiv: 2, fbdiv: 168, postdiv1: 7, postdiv2: 1, usr divider: 1
2020-05-03 04:12:41 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 350 set refdiv: 2, fbdiv: 168, postdiv1: 6, postdiv2: 1, usr divider: 1
2020-05-03 04:12:41 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 420 set refdiv: 2, fbdiv: 168, postdiv1: 5, postdiv2: 1, usr divider: 1
2020-05-03 04:12:41 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 525 set refdiv: 2, fbdiv: 168, postdiv1: 4, postdiv2: 1, usr divider: 1
2020-05-03 04:12:41 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 700 set refdiv: 2, fbdiv: 168, postdiv1: 3, postdiv2: 1, usr divider: 1
2020-05-03 04:12:42 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 41 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 7, usr divider: 1
2020-05-03 04:12:42 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 47 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 6, usr divider: 1
2020-05-03 04:12:42 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 57 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 5, usr divider: 1
2020-05-03 04:12:42 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 71 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 4, usr divider: 1
2020-05-03 04:12:42 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 95 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 3, usr divider: 1
2020-05-03 04:12:42 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 143 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 2, usr divider: 1
2020-05-03 04:12:42 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 287 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 1, usr divider: 1
2020-05-03 04:12:42 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 335 set refdiv: 2, fbdiv: 161, postdiv1: 6, postdiv2: 1, usr divider: 1
2020-05-03 04:12:42 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 402 set refdiv: 2, fbdiv: 161, postdiv1: 5, postdiv2: 1, usr divider: 1
2020-05-03 04:12:43 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 503 set refdiv: 2, fbdiv: 161, postdiv1: 4, postdiv2: 1, usr divider: 1
2020-05-03 04:12:43 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 670 set refdiv: 2, fbdiv: 161, postdiv1: 3, postdiv2: 1, usr divider: 1
2020-05-03 04:12:43 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 41 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 7, usr divider: 1
2020-05-03 04:12:43 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 47 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 6, usr divider: 1
2020-05-03 04:12:43 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 57 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 5, usr divider: 1
2020-05-03 04:12:43 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 71 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 4, usr divider: 1
2020-05-03 04:12:43 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 95 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 3, usr divider: 1
2020-05-03 04:12:43 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 143 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 2, usr divider: 1
2020-05-03 04:12:43 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 287 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 1, usr divider: 1
2020-05-03 04:12:43 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 335 set refdiv: 2, fbdiv: 161, postdiv1: 6, postdiv2: 1, usr divider: 1
2020-05-03 04:12:44 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 402 set refdiv: 2, fbdiv: 161, postdiv1: 5, postdiv2: 1, usr divider: 1
2020-05-03 04:12:44 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 503 set refdiv: 2, fbdiv: 161, postdiv1: 4, postdiv2: 1, usr divider: 1
2020-05-03 04:12:44 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 670 set refdiv: 2, fbdiv: 161, postdiv1: 3, postdiv2: 1, usr divider: 1
2020-05-03 04:12:44 driver-btm-api.c:612:set_timeout: freq 700 final timeout=168
2020-05-03 04:12:44 power_api.c:146:set_higher_voltage: higher_voltage = 18.000000
2020-05-03 04:12:44 power_api.c:428:slowly_set_iic_power_to_higher_voltage: slowly setting to voltage: 18.00 ...
2020-05-03 04:13:08 power_api.c:124:check_voltage_multi: retry time: 0
2020-05-03 04:13:10 power_api.c:86:get_average_voltage: chain[0], voltage is: 18.118095
2020-05-03 04:13:12 power_api.c:86:get_average_voltage: chain[1], voltage is: 18.081357
2020-05-03 04:13:14 power_api.c:86:get_average_voltage: chain[2], voltage is: 18.197695
2020-05-03 04:13:14 power_api.c:97:get_average_voltage: aveage voltage is: 18.132383
2020-05-03 04:13:14 frequency.c:540:get_current_min_freq: current min freq 670
2020-05-03 04:13:14 driver-btm-api.c:1660:check_clock_counter: freq 670 clock_counter_limit 85
2020-05-03 04:13:14 thread.c:799:create_check_system_status_thread: create thread
2020-05-03 04:13:15 driver-btm-api.c:2113:bitmain_soc_init: Init done!
2020-05-03 04:13:15 driver-btm-api.c:201:set_miner_status: STATUS_INIT
2020-05-03 04:13:19 driver-btm-api.c:201:set_miner_status: STATUS_OKAY
2020-05-03 04:13:24 driver-btm-api.c:1293:dhash_chip_send_job: Version num 4
2020-05-03 04:13:28 thread.c:382:check_working_voltage: current PCB min temperature is 43
2020-05-03 04:13:28 thread.c:383:check_working_voltage: current voltage is 18.00V, recovery to 17.10V
2020-05-03 04:13:28 power_api.c:397:slowly_set_iic_power_to_working_voltage: slowly setting to voltage: 17.10 ...
2020-05-03 04:14:00 power_api.c:124:check_voltage_multi: retry time: 0
2020-05-03 04:14:04 power_api.c:86:get_average_voltage: chain[0], voltage is: 17.187392
2020-05-03 04:14:07 power_api.c:86:get_average_voltage: chain[1], voltage is: 17.162900
2020-05-03 04:14:10 power_api.c:86:get_average_voltage: chain[2], voltage is: 17.285361
2020-05-03 04:14:10 power_api.c:97:get_average_voltage: aveage voltage is: 17.211885
2020-05-03 04:19:09 thread.c:422:is_zero_nonce_happened: chain_nonce[0] = 17787
2020-05-03 04:19:09 thread.c:422:is_zero_nonce_happened: chain_nonce[1] = 16839
2020-05-03 04:19:09 thread.c:422:is_zero_nonce_happened: chain_nonce[2] = 14466
2020-05-03 04:43:05 driver-btm-api.c:201:set_miner_status: WARN_NET_LOST
2020-05-03 04:44:11 thread.c:204:calc_hashrate_avg: avg rate is 38861.96 in 30 mins
2020-05-03 04:44:11 temperature.c:450:temp_statistics_show: pcb temp 43~56 chip temp 64~80
2020-05-03 04:44:11 thread.c:285:check_hashrate: latest avg rate < 0.98......
2020-05-03 04:44:11 thread.c:286:check_hashrate: current PCB min temperature 43
2020-05-03 04:44:11 thread.c:287:check_hashrate: current voltage is 17.10V, working voltage is 17.10V
2020-05-03 04:44:11 thread.c:318:check_hashrate: high temp, increase voltage 0.1V/0.2V to 17.20V
2020-05-03 04:44:11 driver-btm-api.c:2124:bitmain_reopen_core: reopen_core start!
2020-05-03 04:44:17 driver-btm-api.c:1067:init_miner_version: miner ID : 8042750618c0885c
2020-05-03 04:44:17 driver-btm-api.c:1073:init_miner_version: FPGA Version = 0xB013
2020-05-03 04:44:18 chain = 0, mode = 0, load_done = false.
2020-05-03 04:44:18 chain = 1, mode = 0, load_done = false.
2020-05-03 04:44:18 chain = 2, mode = 0, load_done = false.
2020-05-03 04:44:19 eeprom.c:425:check_pattern_test_level: invalid pattern test result. ignore
2020-05-03 04:44:19 chain = 0, mode = 0, load_done = false.
2020-05-03 04:44:19 chain = 1, mode = 0, load_done = false.
2020-05-03 04:44:19 chain = 2, mode = 0, load_done = false.
2020-05-03 04:44:20 chain = 0, mode = 0, load_done = false.
2020-05-03 04:44:20 chain = 1, mode = 0, load_done = false.
2020-05-03 04:44:20 chain = 2, mode = 0, load_done = false.
2020-05-03 04:44:21 eeprom.c:425:check_pattern_test_level: invalid pattern test result. ignore
2020-05-03 04:44:21 chain = 0, mode = 0, load_done = false.
2020-05-03 04:44:21 chain = 1, mode = 0, load_done = false.
2020-05-03 04:44:21 chain = 2, mode = 0, load_done = false.
2020-05-03 04:44:22 chain = 0, mode = 0, load_done = false.
2020-05-03 04:44:22 chain = 1, mode = 0, load_done = false.
2020-05-03 04:44:22 chain = 2, mode = 0, load_done = false.
2020-05-03 04:44:23 eeprom.c:425:check_pattern_test_level: invalid pattern test result. ignore
2020-05-03 04:44:23 driver-btm-api.c:705:get_product_id: product_id[0] = 1
2020-05-03 04:44:23 driver-btm-api.c:705:get_product_id: product_id[1] = 1
2020-05-03 04:44:23 driver-btm-api.c:705:get_product_id: product_id[2] = 1
2020-05-03 04:44:23 driver-btm-api.c:1633:get_ccdly_opt: ccdly_opt[0] = 1
2020-05-03 04:44:23 driver-btm-api.c:1633:get_ccdly_opt: ccdly_opt[1] = 1
2020-05-03 04:44:23 driver-btm-api.c:1633:get_ccdly_opt: ccdly_opt[2] = 1
2020-05-03 04:44:23 driver-btm-api.c:1877:bitmain_board_init: g_ccdly_opt = 1
2020-05-03 04:44:23 driver-btm-api.c:644:_set_project_type: project:2
2020-05-03 04:44:23 driver-btm-api.c:674:_set_project_type: Project type: Antminer T17
2020-05-03 04:44:23 driver-btm-api.c:685:dump_pcb_bom_version: Chain [0] PCB Version: 0x0100
2020-05-03 04:44:23 driver-btm-api.c:686:dump_pcb_bom_version: Chain [0] BOM Version: 0x0100
2020-05-03 04:44:23 driver-btm-api.c:685:dump_pcb_bom_version: Chain [1] PCB Version: 0x0100
2020-05-03 04:44:23 driver-btm-api.c:686:dump_pcb_bom_version: Chain [1] BOM Version: 0x0100
2020-05-03 04:44:23 driver-btm-api.c:685:dump_pcb_bom_version: Chain [2] PCB Version: 0x0100
2020-05-03 04:44:23 driver-btm-api.c:686:dump_pcb_bom_version: Chain [2] BOM Version: 0x0100
2020-05-03 04:44:25 driver-btm-api.c:1897:bitmain_board_init: Fan check passed.
2020-05-03 04:44:25 register.c:283:get_register: !!! reg crc error
2020-05-03 04:44:27 board.c:36:jump_and_app_check_restore_pic: chain[0] PIC jump to app
2020-05-03 04:44:33 board.c:40:jump_and_app_check_restore_pic: Check chain[0] PIC fw version=0xb9
2020-05-03 04:44:36 board.c:36:jump_and_app_check_restore_pic: chain[1] PIC jump to app
2020-05-03 04:44:41 board.c:40:jump_and_app_check_restore_pic: Check chain[1] PIC fw version=0xb9
2020-05-03 04:44:43 board.c:36:jump_and_app_check_restore_pic: chain[2] PIC jump to app
2020-05-03 04:44:46 board.c:40:jump_and_app_check_restore_pic: Check chain[2] PIC fw version=0xb9
2020-05-03 04:44:46 power_api.c:55:power_init: power init ...
2020-05-03 04:44:46 driver-btm-api.c:1907:bitmain_board_init: Enter 30s sleep to make sure power release finish.
2020-05-03 04:45:18 power_api.c:232:set_iic_power_to_highest_voltage: setting to voltage: 17.00 ...
2020-05-03 04:45:20 power_api.c:124:check_voltage_multi: retry time: 0
2020-05-03 04:45:22 power_api.c:86:get_average_voltage: chain[0], voltage is: 17.230254
2020-05-03 04:45:25 power_api.c:86:get_average_voltage: chain[1], voltage is: 17.126162
2020-05-03 04:45:28 power_api.c:86:get_average_voltage: chain[2], voltage is: 17.211885
2020-05-03 04:45:28 power_api.c:97:get_average_voltage: aveage voltage is: 17.189433
2020-05-03 04:45:28 power_api.c:182:set_iic_power_by_voltage: now set voltage to : 17.000000
2020-05-03 04:45:28 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[0]: chip baud = 115200, chip_divider = 26
2020-05-03 04:45:28 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[1]: chip baud = 115200, chip_divider = 26
2020-05-03 04:45:28 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[2]: chip baud = 115200, chip_divider = 26
2020-05-03 04:45:28 uart.c:80:set_baud: set fpga_baud = 115200, fpga_divider = 26
2020-05-03 04:45:38 driver-btm-api.c:1010:check_asic_number_with_power_on: Chain[0]: find 30 asic, times 0
2020-05-03 04:45:48 driver-btm-api.c:1010:check_asic_number_with_power_on: Chain[1]: find 30 asic, times 0
2020-05-03 04:45:58 driver-btm-api.c:1010:check_asic_number_with_power_on: Chain[2]: find 30 asic, times 0
2020-05-03 04:46:01 driver-btm-api.c:348:set_order_clock: chain[0]: set order clock, stragegy 3 clock_en=0x1
2020-05-03 04:46:01 driver-btm-api.c:348:set_order_clock: chain[1]: set order clock, stragegy 3 clock_en=0x1
2020-05-03 04:46:02 driver-btm-api.c:348:set_order_clock: chain[2]: set order clock, stragegy 3 clock_en=0x1
2020-05-03 04:46:02 driver-hash-chip.c:490:set_clock_delay_control: core_data = 0xb4
2020-05-03 04:46:02 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[0]: chip baud = 3000000, chip_divider = 0
2020-05-03 04:46:02 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[1]: chip baud = 3000000, chip_divider = 0
2020-05-03 04:46:02 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[2]: chip baud = 3000000, chip_divider = 0
2020-05-03 04:46:02 uart.c:80:set_baud: set fpga_baud = 3000000, fpga_divider = 0
2020-05-03 04:46:02 driver-btm-api.c:1660:check_clock_counter: freq 50 clock_counter_limit 6
2020-05-03 04:46:02 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[0]: chip baud = 115200, chip_divider = 26
2020-05-03 04:46:02 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[1]: chip baud = 115200, chip_divider = 26
2020-05-03 04:46:02 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[2]: chip baud = 115200, chip_divider = 26
2020-05-03 04:46:02 uart.c:80:set_baud: set fpga_baud = 115200, fpga_divider = 26
2020-05-03 04:46:03 voltage[0] = 1710
2020-05-03 04:46:03 voltage[1] = 1710
2020-05-03 04:46:03 voltage[2] = 1710
2020-05-03 04:46:03 power_api.c:140:set_working_voltage: working_voltage = 17.100000
2020-05-03 04:46:04 temperature.c:282:calibrate_temp_sensor_one_chain: Temperature sensor calibration: chain 0 success.
2020-05-03 04:46:05 temperature.c:282:calibrate_temp_sensor_one_chain: Temperature sensor calibration: chain 1 success.
2020-05-03 04:46:07 temperature.c:282:calibrate_temp_sensor_one_chain: Temperature sensor calibration: chain 2 success.
2020-05-03 04:46:07 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[0]: chip baud = 6000000, chip_divider = 7
2020-05-03 04:46:07 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[1]: chip baud = 6000000, chip_divider = 7
2020-05-03 04:46:07 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[2]: chip baud = 6000000, chip_divider = 7
2020-05-03 04:46:07 uart.c:80:set_baud: set fpga_baud = 6000000, fpga_divider = 3
2020-05-03 04:46:08 driver-btm-api.c:248:check_bringup_temp: Bring up temperature is 21
2020-05-03 04:46:08 driver-btm-api.c:581:calculate_timeout: dev->timeout = 392
2020-05-03 04:46:08 power_api.c:379:slowly_set_iic_power_to_custom_voltage: slowly setting to voltage: 18.00 ...
2020-05-03 04:46:41 power_api.c:124:check_voltage_multi: retry time: 0
2020-05-03 04:46:43 power_api.c:86:get_average_voltage: chain[0], voltage is: 18.142588
2020-05-03 04:46:44 power_api.c:86:get_average_voltage: chain[1], voltage is: 18.130342
2020-05-03 04:46:48 power_api.c:86:get_average_voltage: chain[2], voltage is: 18.258926
2020-05-03 04:46:48 power_api.c:97:get_average_voltage: aveage voltage is: 18.177285
2020-05-03 04:46:48 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 42 set refdiv: 2, fbdiv: 168, postdiv1: 7, postdiv2: 7, usr divider: 1
2020-05-03 04:46:48 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 50 set refdiv: 2, fbdiv: 168, postdiv1: 7, postdiv2: 6, usr divider: 1
2020-05-03 04:46:48 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 60 set refdiv: 2, fbdiv: 168, postdiv1: 7, postdiv2: 5, usr divider: 1
2020-05-03 04:46:48 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 75 set refdiv: 2, fbdiv: 168, postdiv1: 7, postdiv2: 4, usr divider: 1
2020-05-03 04:46:48 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 100 set refdiv: 2, fbdiv: 168, postdiv1: 7, postdiv2: 3, usr divider: 1
2020-05-03 04:46:48 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 150 set refdiv: 2, fbdiv: 168, postdiv1: 7, postdiv2: 2, usr divider: 1
2020-05-03 04:46:48 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 300 set refdiv: 2, fbdiv: 168, postdiv1: 7, postdiv2: 1, usr divider: 1
2020-05-03 04:46:48 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 350 set refdiv: 2, fbdiv: 168, postdiv1: 6, postdiv2: 1, usr divider: 1
2020-05-03 04:46:48 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 420 set refdiv: 2, fbdiv: 168, postdiv1: 5, postdiv2: 1, usr divider: 1
2020-05-03 04:46:49 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 525 set refdiv: 2, fbdiv: 168, postdiv1: 4, postdiv2: 1, usr divider: 1
2020-05-03 04:46:49 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 700 set refdiv: 2, fbdiv: 168, postdiv1: 3, postdiv2: 1, usr divider: 1
2020-05-03 04:46:49 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 41 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 7, usr divider: 1
2020-05-03 04:46:49 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 47 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 6, usr divider: 1
2020-05-03 04:46:49 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 57 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 5, usr divider: 1
2020-05-03 04:46:49 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 71 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 4, usr divider: 1
2020-05-03 04:46:49 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 95 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 3, usr divider: 1
2020-05-03 04:46:49 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 143 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 2, usr divider: 1
2020-05-03 04:46:49 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 287 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 1, usr divider: 1
2020-05-03 04:46:49 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 335 set refdiv: 2, fbdiv: 161, postdiv1: 6, postdiv2: 1, usr divider: 1
2020-05-03 04:46:50 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 402 set refdiv: 2, fbdiv: 161, postdiv1: 5, postdiv2: 1, usr divider: 1
2020-05-03 04:46:50 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 503 set refdiv: 2, fbdiv: 161, postdiv1: 4, postdiv2: 1, usr divider: 1
2020-05-03 04:46:50 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 670 set refdiv: 2, fbdiv: 161, postdiv1: 3, postdiv2: 1, usr divider: 1
2020-05-03 04:46:50 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 41 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 7, usr divider: 1
2020-05-03 04:46:50 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 47 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 6, usr divider: 1
2020-05-03 04:46:50 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 57 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 5, usr divider: 1
2020-05-03 04:46:50 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 71 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 4, usr divider: 1
2020-05-03 04:46:50 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 95 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 3, usr divider: 1
2020-05-03 04:46:50 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 143 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 2, usr divider: 1
2020-05-03 04:46:50 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 287 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 1, usr divider: 1
2020-05-03 04:46:51 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 335 set refdiv: 2, fbdiv: 161, postdiv1: 6, postdiv2: 1, usr divider: 1
2020-05-03 04:46:51 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 402 set refdiv: 2, fbdiv: 161, postdiv1: 5, postdiv2: 1, usr divider: 1
2020-05-03 04:46:51 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 503 set refdiv: 2, fbdiv: 161, postdiv1: 4, postdiv2: 1, usr divider: 1
2020-05-03 04:46:51 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 670 set refdiv: 2, fbdiv: 161, postdiv1: 3, postdiv2: 1, usr divider: 1
2020-05-03 04:46:51 driver-btm-api.c:612:set_timeout: freq 700 final timeout=168
2020-05-03 04:46:51 power_api.c:397:slowly_set_iic_power_to_working_voltage: slowly setting to voltage: 17.10 ...
2020-05-03 04:47:24 power_api.c:124:check_voltage_multi: retry time: 0
2020-05-03 04:47:26 power_api.c:86:get_average_voltage: chain[0], voltage is: 17.181269
2020-05-03 04:47:28 power_api.c:86:get_average_voltage: chain[1], voltage is: 17.156777
2020-05-03 04:47:29 power_api.c:86:get_average_voltage: chain[2], voltage is: 17.279238
2020-05-03 04:47:29 power_api.c:97:get_average_voltage: aveage voltage is: 17.205762
2020-05-03 04:47:29 driver-btm-api.c:1293:dhash_chip_send_job: Version num 1
2020-05-03 04:47:29 driver-btm-api.c:1293:dhash_chip_send_job: Version num 4
2020-05-03 04:47:30 driver-btm-api.c:2186:bitmain_reopen_core: reopen_core done!
2020-05-03 04:47:30 power_api.c:379:slowly_set_iic_power_to_custom_voltage: slowly setting to voltage: 17.20 ...
2020-05-03 04:47:57 power_api.c:124:check_voltage_multi: retry time: 0
2020-05-03 04:47:59 power_api.c:86:get_average_voltage: chain[0], voltage is: 17.279238
2020-05-03 04:48:01 power_api.c:86:get_average_voltage: chain[1], voltage is: 17.266992
2020-05-03 04:48:03 power_api.c:86:get_average_voltage: chain[2], voltage is: 17.377207
2020-05-03 04:48:03 power_api.c:97:get_average_voltage: aveage voltage is: 17.307812
2020-05-03 04:48:03 power_api.c:140:set_working_voltage: working_voltage = 17.200001
2020-05-03 04:49:02 driver-btm-api.c:201:set_miner_status: STATUS_OKAY
2020-05-03 04:53:02 thread.c:422:is_zero_nonce_happened: chain_nonce[0] = 111804
2020-05-03 04:53:02 thread.c:422:is_zero_nonce_happened: chain_nonce[1] = 106763
2020-05-03 04:53:02 thread.c:422:is_zero_nonce_happened: chain_nonce[2] = 91522
2020-05-03 05:18:02 thread.c:204:calc_hashrate_avg: avg rate is 39414.58 in 30 mins
2020-05-03 05:18:02 temperature.c:450:temp_statistics_show: pcb temp 44~57 chip temp 65~80
2020-05-03 05:48:03 thread.c:204:calc_hashrate_avg: avg rate is 39042.75 in 30 mins
2020-05-03 05:48:03 temperature.c:450:temp_statistics_show: pcb temp 44~57 chip temp 65~80
2020-05-03 05:48:03 thread.c:285:check_hashrate: latest avg rate < 0.98......
2020-05-03 05:48:03 thread.c:286:check_hashrate: current PCB min temperature 44
2020-05-03 05:48:03 thread.c:287:check_hashrate: current voltage is 17.20V, working voltage is 17.20V
2020-05-03 05:48:03 thread.c:312:check_hashrate: high temp, voltage has already increased 0.1V/0.2V
2020-05-03 06:18:04 thread.c:204:calc_hashrate_avg: avg rate is 39262.43 in 30 mins
2020-05-03 06:18:04 temperature.c:450:temp_statistics_show: pcb temp 44~57 chip temp 65~80
2020-05-03 06:48:06 thread.c:204:calc_hashrate_avg: avg rate is 39010.80 in 30 mins
2020-05-03 06:48:06 temperature.c:450:temp_statistics_show: pcb temp 44~57 chip temp 65~80
2020-05-03 06:48:06 thread.c:285:check_hashrate: latest avg rate < 0.98......
2020-05-03 06:48:06 thread.c:286:check_hashrate: current PCB min temperature 44
2020-05-03 06:48:06 thread.c:287:check_hashrate: current voltage is 17.20V, working voltage is 17.20V
2020-05-03 06:48:06 thread.c:312:check_hashrate: high temp, voltage has already increased 0.1V/0.2V
2020-05-03 07:18:07 thread.c:204:calc_hashrate_avg: avg rate is 39115.22 in 30 mins
2020-05-03 07:18:07 temperature.c:450:temp_statistics_show: pcb temp 45~57 chip temp 66~81
2020-05-03 07:18:07 thread.c:285:check_hashrate: latest avg rate < 0.98......
2020-05-03 07:18:07 thread.c:286:check_hashrate: current PCB min temperature 45
2020-05-03 07:18:07 thread.c:287:check_hashrate: current voltage is 17.20V, working voltage is 17.20V
2020-05-03 07:18:07 thread.c:312:check_hashrate: high temp, voltage has already increased 0.1V/0.2V
2020-05-03 07:48:08 thread.c:204:calc_hashrate_avg: avg rate is 39039.77 in 30 mins
2020-05-03 07:48:08 temperature.c:450:temp_statistics_show: pcb temp 45~57 chip temp 66~80
2020-05-03 07:48:08 thread.c:285:check_hashrate: latest avg rate < 0.98......
2020-05-03 07:48:08 thread.c:286:check_hashrate: current PCB min temperature 45
2020-05-03 07:48:08 thread.c:287:check_hashrate: current voltage is 17.20V, working voltage is 17.20V
2020-05-03 07:48:08 thread.c:312:check_hashrate: high temp, voltage has already increased 0.1V/0.2V
2020-05-03 08:18:10 thread.c:204:calc_hashrate_avg: avg rate is 39204.20 in 30 mins
2020-05-03 08:18:10 temperature.c:450:temp_statistics_show: pcb temp 45~57 chip temp 66~80
2020-05-03 08:48:11 thread.c:204:calc_hashrate_avg: avg rate is 39071.31 in 30 mins
2020-05-03 08:48:11 temperature.c:450:temp_statistics_show: pcb temp 45~57 chip temp 66~80
2020-05-03 08:48:11 thread.c:285:check_hashrate: latest avg rate < 0.98......
2020-05-03 08:48:11 thread.c:286:check_hashrate: current PCB min temperature 45
2020-05-03 08:48:11 thread.c:287:check_hashrate: current voltage is 17.20V, working voltage is 17.20V
2020-05-03 08:48:11 thread.c:312:check_hashrate: high temp, voltage has already increased 0.1V/0.2V
2020-05-03 09:18:12 thread.c:204:calc_hashrate_avg: avg rate is 39131.81 in 30 mins
2020-05-03 09:18:12 temperature.c:450:temp_statistics_show: pcb temp 45~57 chip temp 66~80
2020-05-03 09:18:12 thread.c:285:check_hashrate: latest avg rate < 0.98......
2020-05-03 09:18:12 thread.c:286:check_hashrate: current PCB min temperature 45
2020-05-03 09:18:12 thread.c:287:check_hashrate: current voltage is 17.20V, working voltage is 17.20V
2020-05-03 09:18:12 thread.c:312:check_hashrate: high temp, voltage has already increased 0.1V/0.2V
2020-05-03 09:48:14 thread.c:204:calc_hashrate_avg: avg rate is 39150.20 in 30 mins
2020-05-03 09:48:14 temperature.c:450:temp_statistics_show: pcb temp 45~57 chip temp 66~80
2020-05-03 09:48:14 thread.c:285:check_hashrate: latest avg rate < 0.98......
2020-05-03 09:48:14 thread.c:286:check_hashrate: current PCB min temperature 45
2020-05-03 09:48:14 thread.c:287:check_hashrate: current voltage is 17.20V, working voltage is 17.20V
2020-05-03 09:48:14 thread.c:312:check_hashrate: high temp, voltage has already increased 0.1V/0.2V
2020-05-03 10:18:15 thread.c:204:calc_hashrate_avg: avg rate is 39184.80 in 30 mins
2020-05-03 10:18:15 temperature.c:450:temp_statistics_show: pcb temp 45~57 chip temp 66~80
2020-05-03 10:18:15 thread.c:285:check_hashrate: latest avg rate < 0.98......
2020-05-03 10:18:15 thread.c:286:check_hashrate: current PCB min temperature 45
2020-05-03 10:18:15 thread.c:287:check_hashrate: current voltage is 17.20V, working voltage is 17.20V
2020-05-03 10:18:15 thread.c:312:check_hashrate: high temp, voltage has already increased 0.1V/0.2V
2020-05-03 10:48:16 thread.c:204:calc_hashrate_avg: avg rate is 38965.19 in 30 mins
2020-05-03 10:48:16 temperature.c:450:temp_statistics_show: pcb temp 45~57 chip temp 66~80
2020-05-03 10:48:16 thread.c:285:check_hashrate: latest avg rate < 0.98......
2020-05-03 10:48:16 thread.c:286:check_hashrate: current PCB min temperature 45
2020-05-03 10:48:16 thread.c:287:check_hashrate: current voltage is 17.20V, working voltage is 17.20V
2020-05-03 10:48:16 thread.c:312:check_hashrate: high temp, voltage has already increased 0.1V/0.2V
2020-05-03 11:18:17 thread.c:204:calc_hashrate_avg: avg rate is 39314.97 in 30 mins
2020-05-03 11:18:17 temperature.c:450:temp_statistics_show: pcb temp 45~57 chip temp 66~80
2020-05-03 11:48:19 thread.c:204:calc_hashrate_avg: avg rate is 39373.88 in 30 mins
2020-05-03 11:48:19 temperature.c:450:temp_statistics_show: pcb temp 45~57 chip temp 66~80
2020-05-03 12:18:20 thread.c:204:calc_hashrate_avg: avg rate is 38999.76 in 30 mins
2020-05-03 12:18:20 temperature.c:450:temp_statistics_show: pcb temp 45~57 chip temp 66~81
2020-05-03 12:18:20 thread.c:285:check_hashrate: latest avg rate < 0.98......
2020-05-03 12:18:20 thread.c:286:check_hashrate: current PCB min temperature 45
2020-05-03 12:18:20 thread.c:287:check_hashrate: current voltage is 17.20V, working voltage is 17.20V
2020-05-03 12:18:20 thread.c:312:check_hashrate: high temp, voltage has already increased 0.1V/0.2V
2020-05-03 12:48:21 thread.c:204:calc_hashrate_avg: avg rate is 38962.77 in 30 mins
2020-05-03 12:48:21 temperature.c:450:temp_statistics_show: pcb temp 45~57 chip temp 66~80
2020-05-03 12:48:21 thread.c:285:check_hashrate: latest avg rate < 0.98......
2020-05-03 12:48:21 thread.c:286:check_hashrate: current PCB min temperature 45
2020-05-03 12:48:21 thread.c:287:check_hashrate: current voltage is 17.20V, working voltage is 17.20V
2020-05-03 12:48:21 thread.c:312:check_hashrate: high temp, voltage has already increased 0.1V/0.2V
2020-05-03 13:18:22 thread.c:204:calc_hashrate_avg: avg rate is 39077.63 in 30 mins
2020-05-03 13:18:22 temperature.c:450:temp_statistics_show: pcb temp 45~57 chip temp 66~80
2020-05-03 13:18:22 thread.c:285:check_hashrate: latest avg rate < 0.98......
2020-05-03 13:18:22 thread.c:286:check_hashrate: current PCB min temperature 45
2020-05-03 13:18:22 thread.c:287:check_hashrate: current voltage is 17.20V, working voltage is 17.20V
2020-05-03 13:18:22 thread.c:312:check_hashrate: high temp, voltage has already increased 0.1V/0.2V
2020-05-03 13:48:24 thread.c:204:calc_hashrate_avg: avg rate is 38996.33 in 30 mins
2020-05-03 13:48:24 temperature.c:450:temp_statistics_show: pcb temp 38~56 chip temp 59~79
2020-05-03 13:48:24 thread.c:285:check_hashrate: latest avg rate < 0.98......
2020-05-03 13:48:24 thread.c:286:check_hashrate: current PCB min temperature 38
2020-05-03 13:48:24 thread.c:287:check_hashrate: current voltage is 17.20V, working voltage is 17.20V
2020-05-03 13:48:24 thread.c:312:check_hashrate: high temp, voltage has already increased 0.1V/0.2V
2020-05-03 14:18:25 thread.c:204:calc_hashrate_avg: avg rate is 39111.03 in 30 mins
2020-05-03 14:18:25 temperature.c:450:temp_statistics_show: pcb temp 38~56 chip temp 59~80
2020-05-03 14:18:25 thread.c:285:check_hashrate: latest avg rate < 0.98......
2020-05-03 14:18:25 thread.c:286:check_hashrate: current PCB min temperature 38
2020-05-03 14:18:25 thread.c:287:check_hashrate: current voltage is 17.20V, working voltage is 17.20V
2020-05-03 14:18:25 thread.c:312:check_hashrate: high temp, voltage has already increased 0.1V/0.2V
2020-05-03 14:48:26 thread.c:204:calc_hashrate_avg: avg rate is 38897.26 in 30 mins
2020-05-03 14:48:26 temperature.c:450:temp_statistics_show: pcb temp 37~55 chip temp 58~79
2020-05-03 14:48:26 thread.c:285:check_hashrate: latest avg rate < 0.98......
2020-05-03 14:48:26 thread.c:286:check_hashrate: current PCB min temperature 37
2020-05-03 14:48:26 thread.c:287:check_hashrate: current voltage is 17.20V, working voltage is 17.20V
2020-05-03 14:48:26 thread.c:312:check_hashrate: high temp, voltage has already increased 0.1V/0.2V
Miner Status Page: https://drive.google.com/file/d/1bjfGsFdSOzZLzp9nSr2eEqf4AadNwMe3/view?usp=sharing Jacob
Mikey, I'll take you up and can you show me how to change the fan speed to 100%? Can you do it on Stock firmware? Jacob
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: philipma1957 on May 03, 2020, 09:40:23 PM
Mikey, I'll take you up and can you show me how to change the fan speed to 100%? Can you do it on Stock firmware?
Jacob
Remove the blue wire on the fan. you don't need to cut it. I will find a video for you https://www.youtube.com/watch?v=S9xeg_3eREc watch first 1:45 time it shows you how to non destructively remove a wire. If you do the blue wire it will do full speed and the miner will still be able to give rpm via the yellow wire and power via the red and black wires. I have a really fine flat tip screw driver to do it.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: mysticbitcoin on May 04, 2020, 07:51:39 PM
Update: Philip, Thanks for the video. I do have a pick that'll work to take that wire out. I will try it this afternoon and see if it has any affect on the logs and take that blooding message check_hashrate: high temp, voltage has already increased 0.1V/0.2V away! Current Kernel Log: Booting Linux on physical CPU 0x0
Linux version 4.6.0-xilinx-gff8137b-dirty (lzq@armdev2) (gcc version 4.8.3 20140320 (prerelease) (Sourcery CodeBench Lite 2014.05-23) ) #25 SMP PREEMPT Fri Nov 23 15:30:52 CST 2018
CPU: ARMv7 Processor [413fc090] revision 0 (ARMv7), cr=18c5387d
CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
Machine model: Xilinx Zynq
cma: Reserved 16 MiB at 0x0e000000
Memory policy: Data cache writealloc
On node 0 totalpages: 61440
free_area_init_node: node 0, pgdat c0b39280, node_mem_map cde10000
Normal zone: 480 pages used for memmap
Normal zone: 0 pages reserved
Normal zone: 61440 pages, LIFO batch:15
percpu: Embedded 12 pages/cpu @cddf1000 s19776 r8192 d21184 u49152
pcpu-alloc: s19776 r8192 d21184 u49152 alloc=12*4096
pcpu-alloc: [0] 0 [0] 1
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 60960
Kernel command line: mem=240M console=ttyPS0,115200 ramdisk_size=33554432 root=/dev/ram rw earlyprintk
PID hash table entries: 1024 (order: 0, 4096 bytes)
Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
Memory: 203756K/245760K available (6345K kernel code, 231K rwdata, 1896K rodata, 1024K init, 223K bss, 25620K reserved, 16384K cma-reserved, 0K highmem)
Virtual kernel memory layout:
vector : 0xffff0000 - 0xffff1000 ( 4 kB)
fixmap : 0xffc00000 - 0xfff00000 (3072 kB)
vmalloc : 0xcf800000 - 0xff800000 ( 768 MB)
lowmem : 0xc0000000 - 0xcf000000 ( 240 MB)
pkmap : 0xbfe00000 - 0xc0000000 ( 2 MB)
modules : 0xbf000000 - 0xbfe00000 ( 14 MB)
.text : 0xc0008000 - 0xc090c424 (9234 kB)
.init : 0xc0a00000 - 0xc0b00000 (1024 kB)
.data : 0xc0b00000 - 0xc0b39fe0 ( 232 kB)
.bss : 0xc0b39fe0 - 0xc0b71c28 ( 224 kB)
Preemptible hierarchical RCU implementation.
Build-time adjustment of leaf fanout to 32.
RCU restricting CPUs from NR_CPUS=4 to nr_cpu_ids=2.
RCU: Adjusting geometry for rcu_fanout_leaf=32, nr_cpu_ids=2
NR_IRQS:16 nr_irqs:16 16
efuse mapped to cf800000
ps7-slcr mapped to cf802000
L2C: platform modifies aux control register: 0x72360000 -> 0x72760000
L2C: DT/platform modifies aux control register: 0x72360000 -> 0x72760000
L2C-310 erratum 769419 enabled
L2C-310 enabling early BRESP for Cortex-A9
L2C-310 full line of zeros enabled for Cortex-A9
L2C-310 ID prefetch enabled, offset 1 lines
L2C-310 dynamic clock gating enabled, standby mode enabled
L2C-310 cache controller enabled, 8 ways, 512 kB
L2C-310: CACHE_ID 0x410000c8, AUX_CTRL 0x76760001
zynq_clock_init: clkc starts at cf802100
Zynq clock init
sched_clock: 64 bits at 333MHz, resolution 3ns, wraps every 4398046511103ns
clocksource: arm_global_timer: mask: 0xffffffffffffffff max_cycles: 0x4ce07af025, max_idle_ns: 440795209040 ns
Switching to timer-based delay loop, resolution 3ns
clocksource: ttc_clocksource: mask: 0xffff max_cycles: 0xffff, max_idle_ns: 537538477 ns
ps7-ttc #0 at cf80a000, irq=18
Console: colour dummy device 80x30
Calibrating delay loop (skipped), value calculated using timer frequency.. 666.66 BogoMIPS (lpj=3333333)
pid_max: default: 32768 minimum: 301
Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
CPU: Testing write buffer coherency: ok
CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
Setting up static identity map for 0x100000 - 0x100058
CPU1: failed to boot: -1
Brought up 1 CPUs
SMP: Total of 1 processors activated (666.66 BogoMIPS).
CPU: All CPU(s) started in SVC mode.
devtmpfs: initialized
VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4
clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
pinctrl core: initialized pinctrl subsystem
NET: Registered protocol family 16
DMA: preallocated 256 KiB pool for atomic coherent allocations
cpuidle: using governor menu
hw-breakpoint: found 5 (+1 reserved) breakpoint and 1 watchpoint registers.
hw-breakpoint: maximum watchpoint size is 4 bytes.
zynq-ocm f800c000.ps7-ocmc: ZYNQ OCM pool: 256 KiB @ 0xcf880000
vgaarb: loaded
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
media: Linux media interface: v0.10
Linux video capture interface: v2.00
pps_core: LinuxPPS API ver. 1 registered
pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
PTP clock support registered
EDAC MC: Ver: 3.0.0
Advanced Linux Sound Architecture Driver Initialized.
clocksource: Switched to clocksource arm_global_timer
NET: Registered protocol family 2
TCP established hash table entries: 2048 (order: 1, 8192 bytes)
TCP bind hash table entries: 2048 (order: 2, 16384 bytes)
TCP: Hash tables configured (established 2048 bind 2048)
UDP hash table entries: 256 (order: 1, 8192 bytes)
UDP-Lite hash table entries: 256 (order: 1, 8192 bytes)
NET: Registered protocol family 1
RPC: Registered named UNIX socket transport module.
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
PCI: CLS 0 bytes, default 64
Trying to unpack rootfs image as initramfs...
rootfs image is not initramfs (no cpio magic); looks like an initrd
Freeing initrd memory: 12580K (cceb8000 - cdb01000)
hw perfevents: enabled with armv7_cortex_a9 PMU driver, 7 counters available
futex hash table entries: 512 (order: 3, 32768 bytes)
workingset: timestamp_bits=28 max_order=16 bucket_order=0
jffs2: version 2.2. (NAND) (SUMMARY) © 2001-2006 Red Hat, Inc.
io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered (default)
dma-pl330 f8003000.ps7-dma: Loaded driver for PL330 DMAC-241330
dma-pl330 f8003000.ps7-dma: DBUFF-128x8bytes Num_Chans-8 Num_Peri-4 Num_Events-16
e0000000.serial: ttyPS0 at MMIO 0xe0000000 (irq = 158, base_baud = 6249999) is a xuartps
console [ttyPS0] enabled
xdevcfg f8007000.ps7-dev-cfg: ioremap 0xf8007000 to cf86e000
[drm] Initialized drm 1.1.0 20060810
brd: module loaded
loop: module loaded
CAN device driver interface
gpiod_set_value: invalid GPIO
libphy: MACB_mii_bus: probed
macb e000b000.ethernet eth0: Cadence GEM rev 0x00020118 at 0xe000b000 irq 31 (00:0a:35:00:00:00)
Generic PHY e000b000.etherne:00: attached PHY driver [Generic PHY] (mii_bus:phy_addr=e000b000.etherne:00, irq=-1)
e1000e: Intel(R) PRO/1000 Network Driver - 3.2.6-k
e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
ehci-pci: EHCI PCI platform driver
usbcore: registered new interface driver usb-storage
mousedev: PS/2 mouse device common for all mice
i2c /dev entries driver
Xilinx Zynq CpuIdle Driver started
sdhci: Secure Digital Host Controller Interface driver
sdhci: Copyright(c) Pierre Ossman
sdhci-pltfm: SDHCI platform and OF driver helper
mmc0: SDHCI controller on e0100000.ps7-sdio [e0100000.ps7-sdio] using ADMA
ledtrig-cpu: registered to indicate activity on CPUs
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
nand: device found, Manufacturer ID: 0x2c, Chip ID: 0xda
nand: Micron MT29F2G08ABAGAWP
nand: 256 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 128
nand: WARNING: pl35x-nand: the ECC used on your system is too weak compared to the one required by the NAND chip
Bad block table found at page 131008, version 0x01
Bad block table found at page 130944, version 0x01
6 ofpart partitions found on MTD device pl35x-nand
Creating 6 MTD partitions on "pl35x-nand":
0x000000000000-0x000002800000 : "BOOT.bin-env-dts-kernel"
0x000002800000-0x000004800000 : "ramfs"
0x000004800000-0x000005000000 : "configs"
0x000005000000-0x000006000000 : "reserve"
0x000006000000-0x000008000000 : "ramfs-bak"
0x000008000000-0x000010000000 : "reserve1"
NET: Registered protocol family 10
sit: IPv6 over IPv4 tunneling driver
NET: Registered protocol family 17
can: controller area network core (rev 20120528 abi 9)
NET: Registered protocol family 29
can: raw protocol (rev 20120528)
can: broadcast manager protocol (rev 20120528 t)
can: netlink gateway (rev 20130117) max_hops=1
zynq_pm_ioremap: no compatible node found for 'xlnx,zynq-ddrc-a05'
zynq_pm_late_init: Unable to map DDRC IO memory.
Registering SWP/SWPB emulation handler
hctosys: unable to open rtc device (rtc0)
ALSA device list:
No soundcards found.
RAMDISK: gzip image found at block 0
EXT4-fs (ram0): couldn't mount as ext3 due to feature incompatibilities
EXT4-fs (ram0): mounted filesystem without journal. Opts: (null)
VFS: Mounted root (ext4 filesystem) on device 1:0.
devtmpfs: mounted
Freeing unused kernel memory: 1024K (c0a00000 - c0b00000)
EXT4-fs (ram0): re-mounted. Opts: block_validity,delalloc,barrier,user_xattr
random: dd urandom read with 0 bits of entropy available
ubi0: attaching mtd2
ubi0: scanning is finished
ubi0: attached mtd2 (name "configs", size 8 MiB)
ubi0: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
ubi0: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
ubi0: VID header offset: 2048 (aligned 2048), data offset: 4096
ubi0: good PEBs: 64, bad PEBs: 0, corrupted PEBs: 0
ubi0: user volume: 1, internal volumes: 1, max. volumes count: 128
ubi0: max/mean erase counter: 6/2, WL threshold: 4096, image sequence number: 4244297529
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 01559AD8-7B6A-42E6-A3FE-EDF3659527A9, 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: 1052/340, WL threshold: 4096, image sequence number: 4185749592
ubi1: available PEBs: 0, total reserved PEBs: 1020, PEBs reserved for bad PEB handling: 36
ubi1: background thread "ubi_bgt1d" started, PID 720
UBIFS (ubi1:0): background thread "ubifs_bgt1_0" started, PID 723
UBIFS (ubi1:0): recovery needed
UBIFS (ubi1:0): recovery completed
UBIFS (ubi1:0): UBIFS: mounted UBI device 1, volume 0, name "reserve1"
UBIFS (ubi1:0): LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
UBIFS (ubi1:0): FS size: 123039744 bytes (117 MiB, 969 LEBs), journal size 6221824 bytes (5 MiB, 49 LEBs)
UBIFS (ubi1:0): reserved for root: 4952683 bytes (4836 KiB)
UBIFS (ubi1:0): media format: w4/r0 (latest is w4/r0), UUID 4829CF2C-7435-4146-B2FD-0826AAE8443A, small LPT model
IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
macb e000b000.ethernet eth0: unable to generate target frequency: 25000000 Hz
macb e000b000.ethernet eth0: link up (100/Full)
IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
In axi fpga driver!
request_mem_region OK!
AXI fpga dev virtual address is 0xcfb38000
*base_vir_addr = 0xab013
In fpga mem driver!
request_mem_region OK!
fpga mem virtual address is 0xd2000000
random: nonblocking pool is initialized
2020-05-03 04:09:50 driver-btm-api.c:631:init_freq_mode: This is scan-user version
2020-05-03 04:09:50 driver-btm-api.c:1994:bitmain_soc_init: opt_multi_version = 1
2020-05-03 04:09:50 driver-btm-api.c:1995:bitmain_soc_init: opt_bitmain_ab = 1
2020-05-03 04:09:50 driver-btm-api.c:1996:bitmain_soc_init: opt_bitmain_work_mode = 0
2020-05-03 04:09:50 driver-btm-api.c:1997:bitmain_soc_init: Miner compile time: Tue Dec 24 16:13:07 CST 2019 type: Antminer T17
2020-05-03 04:09:50 driver-btm-api.c:1998:bitmain_soc_init: commit version: e93a09b 2019-12-24 16:03:45, build by: lol 2019-12-24 16:19:49
2020-05-03 04:09:50 driver-btm-api.c:1810:show_sn: no SN got, please write SN to /nvdata/sn
2020-05-03 04:09:50 driver-btm-api.c:1135:miner_device_init: Detect 256MB control board of XILINX
2020-05-03 04:09:50 driver-btm-api.c:1083:init_fan_parameter: fan_eft : 0 fan_pwm : 0
2020-05-03 04:09:50 thread.c:789:create_read_nonce_reg_thread: create thread
2020-05-03 04:09:56 driver-btm-api.c:1067:init_miner_version: miner ID : 8042750618c0885c
2020-05-03 04:09:56 driver-btm-api.c:1073:init_miner_version: FPGA Version = 0xB013
2020-05-03 04:09:58 eeprom.c:425:check_pattern_test_level: invalid pattern test result. ignore
2020-05-03 04:10:00 eeprom.c:425:check_pattern_test_level: invalid pattern test result. ignore
2020-05-03 04:10:02 eeprom.c:425:check_pattern_test_level: invalid pattern test result. ignore
2020-05-03 04:10:02 driver-btm-api.c:705:get_product_id: product_id[0] = 1
2020-05-03 04:10:02 driver-btm-api.c:705:get_product_id: product_id[1] = 1
2020-05-03 04:10:02 driver-btm-api.c:705:get_product_id: product_id[2] = 1
2020-05-03 04:10:02 driver-btm-api.c:1633:get_ccdly_opt: ccdly_opt[0] = 1
2020-05-03 04:10:02 driver-btm-api.c:1633:get_ccdly_opt: ccdly_opt[1] = 1
2020-05-03 04:10:02 driver-btm-api.c:1633:get_ccdly_opt: ccdly_opt[2] = 1
2020-05-03 04:10:02 driver-btm-api.c:1877:bitmain_board_init: g_ccdly_opt = 1
2020-05-03 04:10:02 driver-btm-api.c:644:_set_project_type: project:2
2020-05-03 04:10:02 driver-btm-api.c:674:_set_project_type: Project type: Antminer T17
2020-05-03 04:10:02 driver-btm-api.c:685:dump_pcb_bom_version: Chain [0] PCB Version: 0x0100
2020-05-03 04:10:02 driver-btm-api.c:686:dump_pcb_bom_version: Chain [0] BOM Version: 0x0100
2020-05-03 04:10:02 driver-btm-api.c:685:dump_pcb_bom_version: Chain [1] PCB Version: 0x0100
2020-05-03 04:10:02 driver-btm-api.c:686:dump_pcb_bom_version: Chain [1] BOM Version: 0x0100
2020-05-03 04:10:02 driver-btm-api.c:685:dump_pcb_bom_version: Chain [2] PCB Version: 0x0100
2020-05-03 04:10:02 driver-btm-api.c:686:dump_pcb_bom_version: Chain [2] BOM Version: 0x0100
2020-05-03 04:10:04 driver-btm-api.c:1897:bitmain_board_init: Fan check passed.
2020-05-03 04:10:05 board.c:36:jump_and_app_check_restore_pic: chain[0] PIC jump to app
2020-05-03 04:10:09 board.c:40:jump_and_app_check_restore_pic: Check chain[0] PIC fw version=0xb9
2020-05-03 04:10:11 board.c:36:jump_and_app_check_restore_pic: chain[1] PIC jump to app
2020-05-03 04:10:14 board.c:40:jump_and_app_check_restore_pic: Check chain[1] PIC fw version=0xb9
2020-05-03 04:10:16 board.c:36:jump_and_app_check_restore_pic: chain[2] PIC jump to app
2020-05-03 04:10:19 board.c:40:jump_and_app_check_restore_pic: Check chain[2] PIC fw version=0xb9
2020-05-03 04:10:19 thread.c:784:create_pic_heart_beat_thread: create thread
2020-05-03 04:10:19 power_api.c:55:power_init: power init ...
2020-05-03 04:10:19 driver-btm-api.c:1907:bitmain_board_init: Enter 30s sleep to make sure power release finish.
2020-05-03 04:10:19 power_api.c:46:power_off: init gpio907
2020-05-03 04:10:51 power_api.c:232:set_iic_power_to_highest_voltage: setting to voltage: 17.00 ...
2020-05-03 04:10:57 power_api.c:124:check_voltage_multi: retry time: 0
2020-05-03 04:10:59 power_api.c:86:get_average_voltage: chain[0], voltage is: 21.253095
2020-05-03 04:11:01 power_api.c:86:get_average_voltage: chain[1], voltage is: 20.573437
2020-05-03 04:11:02 power_api.c:86:get_average_voltage: chain[2], voltage is: 20.071347
2020-05-03 04:11:02 power_api.c:97:get_average_voltage: aveage voltage is: 20.632627
2020-05-03 04:11:02 power_api.c:110:check_voltage: target_vol = 17.00, actural_vol = 20.63, more than 1.0v diff.
2020-05-03 04:11:03 power_api.c:124:check_voltage_multi: retry time: 1
2020-05-03 04:11:05 power_api.c:86:get_average_voltage: chain[0], voltage is: 19.048799
2020-05-03 04:11:07 power_api.c:86:get_average_voltage: chain[1], voltage is: 18.454863
2020-05-03 04:11:10 power_api.c:86:get_average_voltage: chain[2], voltage is: 17.622129
2020-05-03 04:11:10 power_api.c:97:get_average_voltage: aveage voltage is: 18.375263
2020-05-03 04:11:10 power_api.c:110:check_voltage: target_vol = 17.00, actural_vol = 18.38, more than 1.0v diff.
2020-05-03 04:11:11 power_api.c:124:check_voltage_multi: retry time: 2
2020-05-03 04:11:13 power_api.c:86:get_average_voltage: chain[0], voltage is: 16.599580
2020-05-03 04:11:16 power_api.c:86:get_average_voltage: chain[1], voltage is: 15.748476
2020-05-03 04:11:18 power_api.c:86:get_average_voltage: chain[2], voltage is: 17.456806
2020-05-03 04:11:18 power_api.c:97:get_average_voltage: aveage voltage is: 16.601621
2020-05-03 04:11:18 power_api.c:182:set_iic_power_by_voltage: now set voltage to : 17.000000
2020-05-03 04:11:18 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[0]: chip baud = 115200, chip_divider = 26
2020-05-03 04:11:18 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[1]: chip baud = 115200, chip_divider = 26
2020-05-03 04:11:18 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[2]: chip baud = 115200, chip_divider = 26
2020-05-03 04:11:18 uart.c:80:set_baud: set fpga_baud = 115200, fpga_divider = 26
2020-05-03 04:11:28 driver-btm-api.c:1010:check_asic_number_with_power_on: Chain[0]: find 30 asic, times 0
2020-05-03 04:11:38 driver-btm-api.c:1010:check_asic_number_with_power_on: Chain[1]: find 30 asic, times 0
2020-05-03 04:11:49 driver-btm-api.c:1010:check_asic_number_with_power_on: Chain[2]: find 30 asic, times 0
2020-05-03 04:11:52 driver-btm-api.c:348:set_order_clock: chain[0]: set order clock, stragegy 3 clock_en=0x1
2020-05-03 04:11:52 driver-btm-api.c:348:set_order_clock: chain[1]: set order clock, stragegy 3 clock_en=0x1
2020-05-03 04:11:52 driver-btm-api.c:348:set_order_clock: chain[2]: set order clock, stragegy 3 clock_en=0x1
2020-05-03 04:11:53 driver-hash-chip.c:490:set_clock_delay_control: core_data = 0xb4
2020-05-03 04:11:53 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[0]: chip baud = 3000000, chip_divider = 0
2020-05-03 04:11:53 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[1]: chip baud = 3000000, chip_divider = 0
2020-05-03 04:11:53 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[2]: chip baud = 3000000, chip_divider = 0
2020-05-03 04:11:53 uart.c:80:set_baud: set fpga_baud = 3000000, fpga_divider = 0
2020-05-03 04:11:53 driver-btm-api.c:1660:check_clock_counter: freq 50 clock_counter_limit 6
2020-05-03 04:11:53 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[0]: chip baud = 115200, chip_divider = 26
2020-05-03 04:11:53 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[1]: chip baud = 115200, chip_divider = 26
2020-05-03 04:11:53 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[2]: chip baud = 115200, chip_divider = 26
2020-05-03 04:11:53 uart.c:80:set_baud: set fpga_baud = 115200, fpga_divider = 26
2020-05-03 04:11:53 voltage[0] = 1710
2020-05-03 04:11:53 voltage[1] = 1710
2020-05-03 04:11:53 voltage[2] = 1710
2020-05-03 04:11:53 power_api.c:140:set_working_voltage: working_voltage = 17.100000
2020-05-03 04:11:55 temperature.c:282:calibrate_temp_sensor_one_chain: Temperature sensor calibration: chain 0 success.
2020-05-03 04:11:56 temperature.c:282:calibrate_temp_sensor_one_chain: Temperature sensor calibration: chain 1 success.
2020-05-03 04:11:57 temperature.c:282:calibrate_temp_sensor_one_chain: Temperature sensor calibration: chain 2 success.
2020-05-03 04:11:57 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[0]: chip baud = 6000000, chip_divider = 7
2020-05-03 04:11:57 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[1]: chip baud = 6000000, chip_divider = 7
2020-05-03 04:11:57 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[2]: chip baud = 6000000, chip_divider = 7
2020-05-03 04:11:57 uart.c:80:set_baud: set fpga_baud = 6000000, fpga_divider = 3
2020-05-03 04:11:59 driver-btm-api.c:248:check_bringup_temp: Bring up temperature is 20
2020-05-03 04:11:59 thread.c:804:create_check_miner_status_thread: create thread
2020-05-03 04:11:59 thread.c:794:create_set_miner_status_thread: create thread
2020-05-03 04:11:59 driver-btm-api.c:581:calculate_timeout: dev->timeout = 392
2020-05-03 04:11:59 thread.c:779:create_temperature_monitor_thread: create thread
2020-05-03 04:11:59 freq_tuning.c:154:freq_tuning_get_max_freq: Max freq of tuning is 760
2020-05-03 04:11:59 power_api.c:379:slowly_set_iic_power_to_custom_voltage: slowly setting to voltage: 18.00 ...
2020-05-03 04:12:35 power_api.c:124:check_voltage_multi: retry time: 0
2020-05-03 04:12:37 power_api.c:86:get_average_voltage: chain[0], voltage is: 18.142588
2020-05-03 04:12:39 power_api.c:86:get_average_voltage: chain[1], voltage is: 18.124219
2020-05-03 04:12:40 power_api.c:86:get_average_voltage: chain[2], voltage is: 18.240556
2020-05-03 04:12:40 power_api.c:97:get_average_voltage: aveage voltage is: 18.169121
2020-05-03 04:12:40 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 42 set refdiv: 2, fbdiv: 168, postdiv1: 7, postdiv2: 7, usr divider: 1
2020-05-03 04:12:41 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 50 set refdiv: 2, fbdiv: 168, postdiv1: 7, postdiv2: 6, usr divider: 1
2020-05-03 04:12:41 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 60 set refdiv: 2, fbdiv: 168, postdiv1: 7, postdiv2: 5, usr divider: 1
2020-05-03 04:12:41 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 75 set refdiv: 2, fbdiv: 168, postdiv1: 7, postdiv2: 4, usr divider: 1
2020-05-03 04:12:41 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 100 set refdiv: 2, fbdiv: 168, postdiv1: 7, postdiv2: 3, usr divider: 1
2020-05-03 04:12:41 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 150 set refdiv: 2, fbdiv: 168, postdiv1: 7, postdiv2: 2, usr divider: 1
2020-05-03 04:12:41 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 300 set refdiv: 2, fbdiv: 168, postdiv1: 7, postdiv2: 1, usr divider: 1
2020-05-03 04:12:41 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 350 set refdiv: 2, fbdiv: 168, postdiv1: 6, postdiv2: 1, usr divider: 1
2020-05-03 04:12:41 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 420 set refdiv: 2, fbdiv: 168, postdiv1: 5, postdiv2: 1, usr divider: 1
2020-05-03 04:12:41 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 525 set refdiv: 2, fbdiv: 168, postdiv1: 4, postdiv2: 1, usr divider: 1
2020-05-03 04:12:41 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 700 set refdiv: 2, fbdiv: 168, postdiv1: 3, postdiv2: 1, usr divider: 1
2020-05-03 04:12:42 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 41 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 7, usr divider: 1
2020-05-03 04:12:42 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 47 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 6, usr divider: 1
2020-05-03 04:12:42 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 57 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 5, usr divider: 1
2020-05-03 04:12:42 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 71 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 4, usr divider: 1
2020-05-03 04:12:42 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 95 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 3, usr divider: 1
2020-05-03 04:12:42 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 143 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 2, usr divider: 1
2020-05-03 04:12:42 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 287 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 1, usr divider: 1
2020-05-03 04:12:42 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 335 set refdiv: 2, fbdiv: 161, postdiv1: 6, postdiv2: 1, usr divider: 1
2020-05-03 04:12:42 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 402 set refdiv: 2, fbdiv: 161, postdiv1: 5, postdiv2: 1, usr divider: 1
2020-05-03 04:12:43 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 503 set refdiv: 2, fbdiv: 161, postdiv1: 4, postdiv2: 1, usr divider: 1
2020-05-03 04:12:43 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 670 set refdiv: 2, fbdiv: 161, postdiv1: 3, postdiv2: 1, usr divider: 1
2020-05-03 04:12:43 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 41 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 7, usr divider: 1
2020-05-03 04:12:43 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 47 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 6, usr divider: 1
2020-05-03 04:12:43 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 57 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 5, usr divider: 1
2020-05-03 04:12:43 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 71 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 4, usr divider: 1
2020-05-03 04:12:43 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 95 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 3, usr divider: 1
2020-05-03 04:12:43 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 143 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 2, usr divider: 1
2020-05-03 04:12:43 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 287 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 1, usr divider: 1
2020-05-03 04:12:43 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 335 set refdiv: 2, fbdiv: 161, postdiv1: 6, postdiv2: 1, usr divider: 1
2020-05-03 04:12:44 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 402 set refdiv: 2, fbdiv: 161, postdiv1: 5, postdiv2: 1, usr divider: 1
2020-05-03 04:12:44 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 503 set refdiv: 2, fbdiv: 161, postdiv1: 4, postdiv2: 1, usr divider: 1
2020-05-03 04:12:44 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 670 set refdiv: 2, fbdiv: 161, postdiv1: 3, postdiv2: 1, usr divider: 1
2020-05-03 04:12:44 driver-btm-api.c:612:set_timeout: freq 700 final timeout=168
2020-05-03 04:12:44 power_api.c:146:set_higher_voltage: higher_voltage = 18.000000
2020-05-03 04:12:44 power_api.c:428:slowly_set_iic_power_to_higher_voltage: slowly setting to voltage: 18.00 ...
2020-05-03 04:13:08 power_api.c:124:check_voltage_multi: retry time: 0
2020-05-03 04:13:10 power_api.c:86:get_average_voltage: chain[0], voltage is: 18.118095
2020-05-03 04:13:12 power_api.c:86:get_average_voltage: chain[1], voltage is: 18.081357
2020-05-03 04:13:14 power_api.c:86:get_average_voltage: chain[2], voltage is: 18.197695
2020-05-03 04:13:14 power_api.c:97:get_average_voltage: aveage voltage is: 18.132383
2020-05-03 04:13:14 frequency.c:540:get_current_min_freq: current min freq 670
2020-05-03 04:13:14 driver-btm-api.c:1660:check_clock_counter: freq 670 clock_counter_limit 85
2020-05-03 04:13:14 thread.c:799:create_check_system_status_thread: create thread
2020-05-03 04:13:15 driver-btm-api.c:2113:bitmain_soc_init: Init done!
2020-05-03 04:13:15 driver-btm-api.c:201:set_miner_status: STATUS_INIT
2020-05-03 04:13:19 driver-btm-api.c:201:set_miner_status: STATUS_OKAY
2020-05-03 04:13:24 driver-btm-api.c:1293:dhash_chip_send_job: Version num 4
2020-05-03 04:13:28 thread.c:382:check_working_voltage: current PCB min temperature is 43
2020-05-03 04:13:28 thread.c:383:check_working_voltage: current voltage is 18.00V, recovery to 17.10V
2020-05-03 04:13:28 power_api.c:397:slowly_set_iic_power_to_working_voltage: slowly setting to voltage: 17.10 ...
2020-05-03 04:14:00 power_api.c:124:check_voltage_multi: retry time: 0
2020-05-03 04:14:04 power_api.c:86:get_average_voltage: chain[0], voltage is: 17.187392
2020-05-03 04:14:07 power_api.c:86:get_average_voltage: chain[1], voltage is: 17.162900
2020-05-03 04:14:10 power_api.c:86:get_average_voltage: chain[2], voltage is: 17.285361
2020-05-03 04:14:10 power_api.c:97:get_average_voltage: aveage voltage is: 17.211885
2020-05-03 04:19:09 thread.c:422:is_zero_nonce_happened: chain_nonce[0] = 17787
2020-05-03 04:19:09 thread.c:422:is_zero_nonce_happened: chain_nonce[1] = 16839
2020-05-03 04:19:09 thread.c:422:is_zero_nonce_happened: chain_nonce[2] = 14466
2020-05-03 04:43:05 driver-btm-api.c:201:set_miner_status: WARN_NET_LOST
2020-05-03 04:44:11 thread.c:204:calc_hashrate_avg: avg rate is 38861.96 in 30 mins
2020-05-03 04:44:11 temperature.c:450:temp_statistics_show: pcb temp 43~56 chip temp 64~80
2020-05-03 04:44:11 thread.c:285:check_hashrate: latest avg rate < 0.98......
2020-05-03 04:44:11 thread.c:286:check_hashrate: current PCB min temperature 43
2020-05-03 04:44:11 thread.c:287:check_hashrate: current voltage is 17.10V, working voltage is 17.10V
2020-05-03 04:44:11 thread.c:318:check_hashrate: high temp, increase voltage 0.1V/0.2V to 17.20V
2020-05-03 04:44:11 driver-btm-api.c:2124:bitmain_reopen_core: reopen_core start!
2020-05-03 04:44:17 driver-btm-api.c:1067:init_miner_version: miner ID : 8042750618c0885c
2020-05-03 04:44:17 driver-btm-api.c:1073:init_miner_version: FPGA Version = 0xB013
2020-05-03 04:44:18 chain = 0, mode = 0, load_done = false.
2020-05-03 04:44:18 chain = 1, mode = 0, load_done = false.
2020-05-03 04:44:18 chain = 2, mode = 0, load_done = false.
2020-05-03 04:44:19 eeprom.c:425:check_pattern_test_level: invalid pattern test result. ignore
2020-05-03 04:44:19 chain = 0, mode = 0, load_done = false.
2020-05-03 04:44:19 chain = 1, mode = 0, load_done = false.
2020-05-03 04:44:19 chain = 2, mode = 0, load_done = false.
2020-05-03 04:44:20 chain = 0, mode = 0, load_done = false.
2020-05-03 04:44:20 chain = 1, mode = 0, load_done = false.
2020-05-03 04:44:20 chain = 2, mode = 0, load_done = false.
2020-05-03 04:44:21 eeprom.c:425:check_pattern_test_level: invalid pattern test result. ignore
2020-05-03 04:44:21 chain = 0, mode = 0, load_done = false.
2020-05-03 04:44:21 chain = 1, mode = 0, load_done = false.
2020-05-03 04:44:21 chain = 2, mode = 0, load_done = false.
2020-05-03 04:44:22 chain = 0, mode = 0, load_done = false.
2020-05-03 04:44:22 chain = 1, mode = 0, load_done = false.
2020-05-03 04:44:22 chain = 2, mode = 0, load_done = false.
2020-05-03 04:44:23 eeprom.c:425:check_pattern_test_level: invalid pattern test result. ignore
2020-05-03 04:44:23 driver-btm-api.c:705:get_product_id: product_id[0] = 1
2020-05-03 04:44:23 driver-btm-api.c:705:get_product_id: product_id[1] = 1
2020-05-03 04:44:23 driver-btm-api.c:705:get_product_id: product_id[2] = 1
2020-05-03 04:44:23 driver-btm-api.c:1633:get_ccdly_opt: ccdly_opt[0] = 1
2020-05-03 04:44:23 driver-btm-api.c:1633:get_ccdly_opt: ccdly_opt[1] = 1
2020-05-03 04:44:23 driver-btm-api.c:1633:get_ccdly_opt: ccdly_opt[2] = 1
2020-05-03 04:44:23 driver-btm-api.c:1877:bitmain_board_init: g_ccdly_opt = 1
2020-05-03 04:44:23 driver-btm-api.c:644:_set_project_type: project:2
2020-05-03 04:44:23 driver-btm-api.c:674:_set_project_type: Project type: Antminer T17
2020-05-03 04:44:23 driver-btm-api.c:685:dump_pcb_bom_version: Chain [0] PCB Version: 0x0100
2020-05-03 04:44:23 driver-btm-api.c:686:dump_pcb_bom_version: Chain [0] BOM Version: 0x0100
2020-05-03 04:44:23 driver-btm-api.c:685:dump_pcb_bom_version: Chain [1] PCB Version: 0x0100
2020-05-03 04:44:23 driver-btm-api.c:686:dump_pcb_bom_version: Chain [1] BOM Version: 0x0100
2020-05-03 04:44:23 driver-btm-api.c:685:dump_pcb_bom_version: Chain [2] PCB Version: 0x0100
2020-05-03 04:44:23 driver-btm-api.c:686:dump_pcb_bom_version: Chain [2] BOM Version: 0x0100
2020-05-03 04:44:25 driver-btm-api.c:1897:bitmain_board_init: Fan check passed.
2020-05-03 04:44:25 register.c:283:get_register: !!! reg crc error
2020-05-03 04:44:27 board.c:36:jump_and_app_check_restore_pic: chain[0] PIC jump to app
2020-05-03 04:44:33 board.c:40:jump_and_app_check_restore_pic: Check chain[0] PIC fw version=0xb9
2020-05-03 04:44:36 board.c:36:jump_and_app_check_restore_pic: chain[1] PIC jump to app
2020-05-03 04:44:41 board.c:40:jump_and_app_check_restore_pic: Check chain[1] PIC fw version=0xb9
2020-05-03 04:44:43 board.c:36:jump_and_app_check_restore_pic: chain[2] PIC jump to app
2020-05-03 04:44:46 board.c:40:jump_and_app_check_restore_pic: Check chain[2] PIC fw version=0xb9
2020-05-03 04:44:46 power_api.c:55:power_init: power init ...
2020-05-03 04:44:46 driver-btm-api.c:1907:bitmain_board_init: Enter 30s sleep to make sure power release finish.
2020-05-03 04:45:18 power_api.c:232:set_iic_power_to_highest_voltage: setting to voltage: 17.00 ...
2020-05-03 04:45:20 power_api.c:124:check_voltage_multi: retry time: 0
2020-05-03 04:45:22 power_api.c:86:get_average_voltage: chain[0], voltage is: 17.230254
2020-05-03 04:45:25 power_api.c:86:get_average_voltage: chain[1], voltage is: 17.126162
2020-05-03 04:45:28 power_api.c:86:get_average_voltage: chain[2], voltage is: 17.211885
2020-05-03 04:45:28 power_api.c:97:get_average_voltage: aveage voltage is: 17.189433
2020-05-03 04:45:28 power_api.c:182:set_iic_power_by_voltage: now set voltage to : 17.000000
2020-05-03 04:45:28 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[0]: chip baud = 115200, chip_divider = 26
2020-05-03 04:45:28 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[1]: chip baud = 115200, chip_divider = 26
2020-05-03 04:45:28 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[2]: chip baud = 115200, chip_divider = 26
2020-05-03 04:45:28 uart.c:80:set_baud: set fpga_baud = 115200, fpga_divider = 26
2020-05-03 04:45:38 driver-btm-api.c:1010:check_asic_number_with_power_on: Chain[0]: find 30 asic, times 0
2020-05-03 04:45:48 driver-btm-api.c:1010:check_asic_number_with_power_on: Chain[1]: find 30 asic, times 0
2020-05-03 04:45:58 driver-btm-api.c:1010:check_asic_number_with_power_on: Chain[2]: find 30 asic, times 0
2020-05-03 04:46:01 driver-btm-api.c:348:set_order_clock: chain[0]: set order clock, stragegy 3 clock_en=0x1
2020-05-03 04:46:01 driver-btm-api.c:348:set_order_clock: chain[1]: set order clock, stragegy 3 clock_en=0x1
2020-05-03 04:46:02 driver-btm-api.c:348:set_order_clock: chain[2]: set order clock, stragegy 3 clock_en=0x1
2020-05-03 04:46:02 driver-hash-chip.c:490:set_clock_delay_control: core_data = 0xb4
2020-05-03 04:46:02 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[0]: chip baud = 3000000, chip_divider = 0
2020-05-03 04:46:02 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[1]: chip baud = 3000000, chip_divider = 0
2020-05-03 04:46:02 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[2]: chip baud = 3000000, chip_divider = 0
2020-05-03 04:46:02 uart.c:80:set_baud: set fpga_baud = 3000000, fpga_divider = 0
2020-05-03 04:46:02 driver-btm-api.c:1660:check_clock_counter: freq 50 clock_counter_limit 6
2020-05-03 04:46:02 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[0]: chip baud = 115200, chip_divider = 26
2020-05-03 04:46:02 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[1]: chip baud = 115200, chip_divider = 26
2020-05-03 04:46:02 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[2]: chip baud = 115200, chip_divider = 26
2020-05-03 04:46:02 uart.c:80:set_baud: set fpga_baud = 115200, fpga_divider = 26
2020-05-03 04:46:03 voltage[0] = 1710
2020-05-03 04:46:03 voltage[1] = 1710
2020-05-03 04:46:03 voltage[2] = 1710
2020-05-03 04:46:03 power_api.c:140:set_working_voltage: working_voltage = 17.100000
2020-05-03 04:46:04 temperature.c:282:calibrate_temp_sensor_one_chain: Temperature sensor calibration: chain 0 success.
2020-05-03 04:46:05 temperature.c:282:calibrate_temp_sensor_one_chain: Temperature sensor calibration: chain 1 success.
2020-05-03 04:46:07 temperature.c:282:calibrate_temp_sensor_one_chain: Temperature sensor calibration: chain 2 success.
2020-05-03 04:46:07 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[0]: chip baud = 6000000, chip_divider = 7
2020-05-03 04:46:07 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[1]: chip baud = 6000000, chip_divider = 7
2020-05-03 04:46:07 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[2]: chip baud = 6000000, chip_divider = 7
2020-05-03 04:46:07 uart.c:80:set_baud: set fpga_baud = 6000000, fpga_divider = 3
2020-05-03 04:46:08 driver-btm-api.c:248:check_bringup_temp: Bring up temperature is 21
2020-05-03 04:46:08 driver-btm-api.c:581:calculate_timeout: dev->timeout = 392
2020-05-03 04:46:08 power_api.c:379:slowly_set_iic_power_to_custom_voltage: slowly setting to voltage: 18.00 ...
2020-05-03 04:46:41 power_api.c:124:check_voltage_multi: retry time: 0
2020-05-03 04:46:43 power_api.c:86:get_average_voltage: chain[0], voltage is: 18.142588
2020-05-03 04:46:44 power_api.c:86:get_average_voltage: chain[1], voltage is: 18.130342
2020-05-03 04:46:48 power_api.c:86:get_average_voltage: chain[2], voltage is: 18.258926
2020-05-03 04:46:48 power_api.c:97:get_average_voltage: aveage voltage is: 18.177285
2020-05-03 04:46:48 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 42 set refdiv: 2, fbdiv: 168, postdiv1: 7, postdiv2: 7, usr divider: 1
2020-05-03 04:46:48 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 50 set refdiv: 2, fbdiv: 168, postdiv1: 7, postdiv2: 6, usr divider: 1
2020-05-03 04:46:48 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 60 set refdiv: 2, fbdiv: 168, postdiv1: 7, postdiv2: 5, usr divider: 1
2020-05-03 04:46:48 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 75 set refdiv: 2, fbdiv: 168, postdiv1: 7, postdiv2: 4, usr divider: 1
2020-05-03 04:46:48 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 100 set refdiv: 2, fbdiv: 168, postdiv1: 7, postdiv2: 3, usr divider: 1
2020-05-03 04:46:48 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 150 set refdiv: 2, fbdiv: 168, postdiv1: 7, postdiv2: 2, usr divider: 1
2020-05-03 04:46:48 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 300 set refdiv: 2, fbdiv: 168, postdiv1: 7, postdiv2: 1, usr divider: 1
2020-05-03 04:46:48 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 350 set refdiv: 2, fbdiv: 168, postdiv1: 6, postdiv2: 1, usr divider: 1
2020-05-03 04:46:48 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 420 set refdiv: 2, fbdiv: 168, postdiv1: 5, postdiv2: 1, usr divider: 1
2020-05-03 04:46:49 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 525 set refdiv: 2, fbdiv: 168, postdiv1: 4, postdiv2: 1, usr divider: 1
2020-05-03 04:46:49 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 700 set refdiv: 2, fbdiv: 168, postdiv1: 3, postdiv2: 1, usr divider: 1
2020-05-03 04:46:49 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 41 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 7, usr divider: 1
2020-05-03 04:46:49 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 47 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 6, usr divider: 1
2020-05-03 04:46:49 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 57 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 5, usr divider: 1
2020-05-03 04:46:49 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 71 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 4, usr divider: 1
2020-05-03 04:46:49 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 95 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 3, usr divider: 1
2020-05-03 04:46:49 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 143 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 2, usr divider: 1
2020-05-03 04:46:49 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 287 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 1, usr divider: 1
2020-05-03 04:46:49 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 335 set refdiv: 2, fbdiv: 161, postdiv1: 6, postdiv2: 1, usr divider: 1
2020-05-03 04:46:50 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 402 set refdiv: 2, fbdiv: 161, postdiv1: 5, postdiv2: 1, usr divider: 1
2020-05-03 04:46:50 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 503 set refdiv: 2, fbdiv: 161, postdiv1: 4, postdiv2: 1, usr divider: 1
2020-05-03 04:46:50 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 670 set refdiv: 2, fbdiv: 161, postdiv1: 3, postdiv2: 1, usr divider: 1
2020-05-03 04:46:50 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 41 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 7, usr divider: 1
2020-05-03 04:46:50 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 47 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 6, usr divider: 1
2020-05-03 04:46:50 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 57 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 5, usr divider: 1
2020-05-03 04:46:50 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 71 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 4, usr divider: 1
2020-05-03 04:46:50 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 95 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 3, usr divider: 1
2020-05-03 04:46:50 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 143 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 2, usr divider: 1
2020-05-03 04:46:50 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 287 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 1, usr divider: 1
2020-05-03 04:46:51 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 335 set refdiv: 2, fbdiv: 161, postdiv1: 6, postdiv2: 1, usr divider: 1
2020-05-03 04:46:51 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 402 set refdiv: 2, fbdiv: 161, postdiv1: 5, postdiv2: 1, usr divider: 1
2020-05-03 04:46:51 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 503 set refdiv: 2, fbdiv: 161, postdiv1: 4, postdiv2: 1, usr divider: 1
2020-05-03 04:46:51 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 670 set refdiv: 2, fbdiv: 161, postdiv1: 3, postdiv2: 1, usr divider: 1
2020-05-03 04:46:51 driver-btm-api.c:612:set_timeout: freq 700 final timeout=168
2020-05-03 04:46:51 power_api.c:397:slowly_set_iic_power_to_working_voltage: slowly setting to voltage: 17.10 ...
2020-05-03 04:47:24 power_api.c:124:check_voltage_multi: retry time: 0
2020-05-03 04:47:26 power_api.c:86:get_average_voltage: chain[0], voltage is: 17.181269
2020-05-03 04:47:28 power_api.c:86:get_average_voltage: chain[1], voltage is: 17.156777
2020-05-03 04:47:29 power_api.c:86:get_average_voltage: chain[2], voltage is: 17.279238
2020-05-03 04:47:29 power_api.c:97:get_average_voltage: aveage voltage is: 17.205762
2020-05-03 04:47:29 driver-btm-api.c:1293:dhash_chip_send_job: Version num 1
2020-05-03 04:47:29 driver-btm-api.c:1293:dhash_chip_send_job: Version num 4
2020-05-03 04:47:30 driver-btm-api.c:2186:bitmain_reopen_core: reopen_core done!
2020-05-03 04:47:30 power_api.c:379:slowly_set_iic_power_to_custom_voltage: slowly setting to voltage: 17.20 ...
2020-05-03 04:47:57 power_api.c:124:check_voltage_multi: retry time: 0
2020-05-03 04:47:59 power_api.c:86:get_average_voltage: chain[0], voltage is: 17.279238
2020-05-03 04:48:01 power_api.c:86:get_average_voltage: chain[1], voltage is: 17.266992
2020-05-03 04:48:03 power_api.c:86:get_average_voltage: chain[2], voltage is: 17.377207
2020-05-03 04:48:03 power_api.c:97:get_average_voltage: aveage voltage is: 17.307812
2020-05-03 04:48:03 power_api.c:140:set_working_voltage: working_voltage = 17.200001
2020-05-03 04:49:02 driver-btm-api.c:201:set_miner_status: STATUS_OKAY
2020-05-03 04:53:02 thread.c:422:is_zero_nonce_happened: chain_nonce[0] = 111804
2020-05-03 04:53:02 thread.c:422:is_zero_nonce_happened: chain_nonce[1] = 106763
2020-05-03 04:53:02 thread.c:422:is_zero_nonce_happened: chain_nonce[2] = 91522
2020-05-03 05:18:02 thread.c:204:calc_hashrate_avg: avg rate is 39414.58 in 30 mins
2020-05-03 05:18:02 temperature.c:450:temp_statistics_show: pcb temp 44~57 chip temp 65~80
2020-05-03 05:48:03 thread.c:204:calc_hashrate_avg: avg rate is 39042.75 in 30 mins
2020-05-03 05:48:03 temperature.c:450:temp_statistics_show: pcb temp 44~57 chip temp 65~80
2020-05-03 05:48:03 thread.c:285:check_hashrate: latest avg rate < 0.98......
2020-05-03 05:48:03 thread.c:286:check_hashrate: current PCB min temperature 44
2020-05-03 05:48:03 thread.c:287:check_hashrate: current voltage is 17.20V, working voltage is 17.20V
2020-05-03 05:48:03 thread.c:312:check_hashrate: high temp, voltage has already increased 0.1V/0.2V
2020-05-03 06:18:04 thread.c:204:calc_hashrate_avg: avg rate is 39262.43 in 30 mins
2020-05-03 06:18:04 temperature.c:450:temp_statistics_show: pcb temp 44~57 chip temp 65~80
2020-05-03 06:48:06 thread.c:204:calc_hashrate_avg: avg rate is 39010.80 in 30 mins
2020-05-03 06:48:06 temperature.c:450:temp_statistics_show: pcb temp 44~57 chip temp 65~80
2020-05-03 06:48:06 thread.c:285:check_hashrate: latest avg rate < 0.98......
2020-05-03 06:48:06 thread.c:286:check_hashrate: current PCB min temperature 44
2020-05-03 06:48:06 thread.c:287:check_hashrate: current voltage is 17.20V, working voltage is 17.20V
2020-05-03 06:48:06 thread.c:312:check_hashrate: high temp, voltage has already increased 0.1V/0.2V
** POST TO LONG - Status post just like above and below showing "current PCB min temperature" at 45 **
2020-05-03 13:18:22 thread.c:204:calc_hashrate_avg: avg rate is 39077.63 in 30 mins
2020-05-03 13:18:22 temperature.c:450:temp_statistics_show: pcb temp 45~57 chip temp 66~80
2020-05-03 13:18:22 thread.c:285:check_hashrate: latest avg rate < 0.98......
2020-05-03 13:18:22 thread.c:286:check_hashrate: current PCB min temperature 45
2020-05-03 13:18:22 thread.c:287:check_hashrate: current voltage is 17.20V, working voltage is 17.20V
2020-05-03 13:18:22 thread.c:312:check_hashrate: high temp, voltage has already increased 0.1V/0.2V
2020-05-03 13:48:24 thread.c:204:calc_hashrate_avg: avg rate is 38996.33 in 30 mins
2020-05-03 13:48:24 temperature.c:450:temp_statistics_show: pcb temp 38~56 chip temp 59~79
2020-05-03 13:48:24 thread.c:285:check_hashrate: latest avg rate < 0.98......
2020-05-03 13:48:24 thread.c:286:check_hashrate: current PCB min temperature 38
2020-05-03 13:48:24 thread.c:287:check_hashrate: current voltage is 17.20V, working voltage is 17.20V
2020-05-03 13:48:24 thread.c:312:check_hashrate: high temp, voltage has already increased 0.1V/0.2V
2020-05-03 14:18:25 thread.c:204:calc_hashrate_avg: avg rate is 39111.03 in 30 mins
2020-05-03 14:18:25 temperature.c:450:temp_statistics_show: pcb temp 38~56 chip temp 59~80
2020-05-03 14:18:25 thread.c:285:check_hashrate: latest avg rate < 0.98......
2020-05-03 14:18:25 thread.c:286:check_hashrate: current PCB min temperature 38
2020-05-03 14:18:25 thread.c:287:check_hashrate: current voltage is 17.20V, working voltage is 17.20V
2020-05-03 14:18:25 thread.c:312:check_hashrate: high temp, voltage has already increased 0.1V/0.2V
2020-05-03 14:48:26 thread.c:204:calc_hashrate_avg: avg rate is 38897.26 in 30 mins
2020-05-03 14:48:26 temperature.c:450:temp_statistics_show: pcb temp 37~55 chip temp 58~79
2020-05-03 14:48:26 thread.c:285:check_hashrate: latest avg rate < 0.98......
2020-05-03 14:48:26 thread.c:286:check_hashrate: current PCB min temperature 37
2020-05-03 14:48:26 thread.c:287:check_hashrate: current voltage is 17.20V, working voltage is 17.20V
2020-05-03 14:48:26 thread.c:312:check_hashrate: high temp, voltage has already increased 0.1V/0.2V
2020-05-03 15:18:28 thread.c:204:calc_hashrate_avg: avg rate is 39043.82 in 30 mins
2020-05-03 15:18:28 temperature.c:450:temp_statistics_show: pcb temp 38~56 chip temp 59~80
2020-05-03 15:18:28 thread.c:285:check_hashrate: latest avg rate < 0.98......
2020-05-03 15:18:28 thread.c:286:check_hashrate: current PCB min temperature 38
2020-05-03 15:18:28 thread.c:287:check_hashrate: current voltage is 17.20V, working voltage is 17.20V
2020-05-03 15:18:28 thread.c:312:check_hashrate: high temp, voltage has already increased 0.1V/0.2V
2020-05-03 15:48:29 thread.c:204:calc_hashrate_avg: avg rate is 39100.51 in 30 mins
2020-05-03 15:48:29 temperature.c:450:temp_statistics_show: pcb temp 39~56 chip temp 59~80
2020-05-03 15:48:29 thread.c:285:check_hashrate: latest avg rate < 0.98......
2020-05-03 15:48:29 thread.c:286:check_hashrate: current PCB min temperature 39
2020-05-03 15:48:29 thread.c:287:check_hashrate: current voltage is 17.20V, working voltage is 17.20V
2020-05-03 15:48:29 thread.c:312:check_hashrate: high temp, voltage has already increased 0.1V/0.2V
2020-05-03 16:05:48 driver-btm-api.c:201:set_miner_status: WARN_NET_LOST
2020-05-03 16:06:23 driver-btm-api.c:1293:dhash_chip_send_job: Version num 1
2020-05-03 16:06:55 driver-btm-api.c:1293:dhash_chip_send_job: Version num 4
2020-05-03 16:06:55 driver-btm-api.c:201:set_miner_status: STATUS_OKAY
** POST is too long - Again same as above and below more status posts showing "current PCB min temperature" from 40 to 42 **
2020-05-03 23:48:49 thread.c:204:calc_hashrate_avg: avg rate is 39154.78 in 30 mins
2020-05-03 23:48:49 temperature.c:450:temp_statistics_show: pcb temp 40~56 chip temp 62~80
2020-05-03 23:48:49 thread.c:285:check_hashrate: latest avg rate < 0.98......
2020-05-03 23:48:49 thread.c:286:check_hashrate: current PCB min temperature 40
2020-05-03 23:48:49 thread.c:287:check_hashrate: current voltage is 17.20V, working voltage is 17.20V
2020-05-03 23:48:49 thread.c:312:check_hashrate: high temp, voltage has already increased 0.1V/0.2V
2020-05-04 00:18:51 thread.c:204:calc_hashrate_avg: avg rate is 38955.13 in 30 mins
2020-05-04 00:18:51 temperature.c:450:temp_statistics_show: pcb temp 37~55 chip temp 59~80
2020-05-04 00:18:51 thread.c:285:check_hashrate: latest avg rate < 0.98......
2020-05-04 00:18:51 thread.c:286:check_hashrate: current PCB min temperature 37
2020-05-04 00:18:51 thread.c:287:check_hashrate: current voltage is 17.20V, working voltage is 17.20V
2020-05-04 00:18:51 thread.c:312:check_hashrate: high temp, voltage has already increased 0.1V/0.2V
2020-05-04 00:48:52 thread.c:204:calc_hashrate_avg: avg rate is 38934.22 in 30 mins
2020-05-04 00:48:52 temperature.c:450:temp_statistics_show: pcb temp 36~53 chip temp 58~78
2020-05-04 00:48:52 thread.c:285:check_hashrate: latest avg rate < 0.98......
2020-05-04 00:48:52 thread.c:286:check_hashrate: current PCB min temperature 36
2020-05-04 00:48:52 thread.c:287:check_hashrate: current voltage is 17.20V, working voltage is 17.20V
2020-05-04 00:48:52 thread.c:312:check_hashrate: high temp, voltage has already increased 0.1V/0.2V
** Log was too long for forum posting rules - Just a repeat of the same with "current PCD min temperature 41 to 44 **
2020-05-04 15:19:29 thread.c:204:calc_hashrate_avg: avg rate is 38970.55 in 30 mins
2020-05-04 15:19:29 temperature.c:450:temp_statistics_show: pcb temp 44~57 chip temp 65~80
2020-05-04 15:19:29 thread.c:285:check_hashrate: latest avg rate < 0.98......
2020-05-04 15:19:29 thread.c:286:check_hashrate: current PCB min temperature 44
2020-05-04 15:19:29 thread.c:287:check_hashrate: current voltage is 17.20V, working voltage is 17.20V
2020-05-04 15:19:29 thread.c:312:check_hashrate: high temp, voltage has already increased 0.1V/0.2V
2020-05-04 15:49:31 thread.c:204:calc_hashrate_avg: avg rate is 39149.93 in 30 mins
2020-05-04 15:49:31 temperature.c:450:temp_statistics_show: pcb temp 37~56 chip temp 57~79
2020-05-04 15:49:31 thread.c:285:check_hashrate: latest avg rate < 0.98......
2020-05-04 15:49:31 thread.c:286:check_hashrate: current PCB min temperature 37
2020-05-04 15:49:31 thread.c:287:check_hashrate: current voltage is 17.20V, working voltage is 17.20V
2020-05-04 15:49:31 thread.c:312:check_hashrate: high temp, voltage has already increased 0.1V/0.2V
2020-05-04 16:19:32 thread.c:204:calc_hashrate_avg: avg rate is 38912.71 in 30 mins
2020-05-04 16:19:32 temperature.c:450:temp_statistics_show: pcb temp 36~53 chip temp 58~78
2020-05-04 16:19:32 thread.c:285:check_hashrate: latest avg rate < 0.98......
2020-05-04 16:19:32 thread.c:286:check_hashrate: current PCB min temperature 36
2020-05-04 16:19:32 thread.c:287:check_hashrate: current voltage is 17.20V, working voltage is 17.20V
2020-05-04 16:19:32 thread.c:312:check_hashrate: high temp, voltage has already increased 0.1V/0.2V
2020-05-04 16:49:33 thread.c:204:calc_hashrate_avg: avg rate is 39069.31 in 30 mins
2020-05-04 16:49:33 temperature.c:450:temp_statistics_show: pcb temp 37~54 chip temp 58~79
2020-05-04 16:49:33 thread.c:285:check_hashrate: latest avg rate < 0.98......
2020-05-04 16:49:33 thread.c:286:check_hashrate: current PCB min temperature 37
2020-05-04 16:49:33 thread.c:287:check_hashrate: current voltage is 17.20V, working voltage is 17.20V
2020-05-04 16:49:33 thread.c:312:check_hashrate: high temp, voltage has already increased 0.1V/0.2V
2020-05-04 17:19:35 thread.c:204:calc_hashrate_avg: avg rate is 39310.65 in 30 mins
2020-05-04 17:19:35 temperature.c:450:temp_statistics_show: pcb temp 36~53 chip temp 58~77
2020-05-04 17:49:36 thread.c:204:calc_hashrate_avg: avg rate is 38951.43 in 30 mins
2020-05-04 17:49:36 temperature.c:450:temp_statistics_show: pcb temp 36~53 chip temp 58~77
2020-05-04 17:49:36 thread.c:285:check_hashrate: latest avg rate < 0.98......
2020-05-04 17:49:36 thread.c:286:check_hashrate: current PCB min temperature 36
2020-05-04 17:49:36 thread.c:287:check_hashrate: current voltage is 17.20V, working voltage is 17.20V
2020-05-04 17:49:36 thread.c:312:check_hashrate: high temp, voltage has already increased 0.1V/0.2V
2020-05-04 18:05:32 driver-btm-api.c:201:set_miner_status: WARN_NET_LOST
2020-05-04 18:06:43 driver-btm-api.c:1293:dhash_chip_send_job: Version num 1
2020-05-04 18:06:53 driver-btm-api.c:1293:dhash_chip_send_job: Version num 4
2020-05-04 18:06:53 driver-btm-api.c:201:set_miner_status: STATUS_OKAY
2020-05-04 18:19:37 thread.c:204:calc_hashrate_avg: avg rate is 39049.05 in 30 mins
2020-05-04 18:19:37 temperature.c:450:temp_statistics_show: pcb temp 36~52 chip temp 57~77
2020-05-04 18:19:37 thread.c:285:check_hashrate: latest avg rate < 0.98......
2020-05-04 18:19:37 thread.c:286:check_hashrate: current PCB min temperature 36
2020-05-04 18:19:37 thread.c:287:check_hashrate: current voltage is 17.20V, working voltage is 17.20V
2020-05-04 18:19:37 thread.c:312:check_hashrate: high temp, voltage has already increased 0.1V/0.2V
2020-05-04 18:49:38 thread.c:204:calc_hashrate_avg: avg rate is 39058.82 in 30 mins
2020-05-04 18:49:38 temperature.c:450:temp_statistics_show: pcb temp 34~51 chip temp 56~75
2020-05-04 18:49:38 thread.c:285:check_hashrate: latest avg rate < 0.98......
2020-05-04 18:49:38 thread.c:286:check_hashrate: current PCB min temperature 34
2020-05-04 18:49:38 thread.c:287:check_hashrate: current voltage is 17.20V, working voltage is 17.20V
2020-05-04 18:49:38 thread.c:312:check_hashrate: high temp, voltage has already increased 0.1V/0.2V
2020-05-04 19:19:40 thread.c:204:calc_hashrate_avg: avg rate is 39027.68 in 30 mins
2020-05-04 19:19:40 temperature.c:450:temp_statistics_show: pcb temp 34~51 chip temp 56~75
2020-05-04 19:19:40 thread.c:285:check_hashrate: latest avg rate < 0.98......
2020-05-04 19:19:40 thread.c:286:check_hashrate: current PCB min temperature 34
2020-05-04 19:19:40 thread.c:287:check_hashrate: current voltage is 17.20V, working voltage is 17.20V
2020-05-04 19:19:40 thread.c:312:check_hashrate: high temp, voltage has already increased 0.1V/0.2V
Miner Status Screen: https://drive.google.com/file/d/1q5JcXDxunZAHhtlFYfMf1FYZA6HPgRrc/view?usp=sharing Jacob
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: mikeywith on May 05, 2020, 01:43:04 AM
Mikey, I'll take you up and can you show me how to change the fan speed to 100%? Can you do it on Stock firmware?
Jacob
Try to type my full user name, that way I get notified about it here (http://loyce.club/notifications/2033515.html), if not it will take me sometime to notice your post. You don't have to remove any wires, I made a simple guide on how to set a fixed speed for the fans, read about it here (https://bitcointalk.org/index.php?topic=5202112.0). [...]
Have you tried a different PSU for this miner?
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: mysticbitcoin on May 05, 2020, 06:50:33 PM
Mikeywith, Thats funny that you mention it. That is the conclusion that I'm coming. To the other T17 run at a lower voltage around 16.9 and have no issues and in fact have a higher average Hashrate. I don't have any extra PSU. I'll take one off one of the other good T17's and put it on this one. BTW, where is a good place to order a APW9 PSU, I'm in Canada. Jacob
Mikeywith, Thanks for that reference post on the setting the fan speed in the Miner Settings Page, so easy without picking the pin out of the fan connectors. There quite a few settings that they have hidden. Anyways, the results are in the same message comes regardless the amount of cooling. I don't want to run the fans a whole 24hrs when the same message still shows. I will try the different PSU. Kernel Logs before Fan 100% setting Reboot: [Deleted Boot Header of Log as its the same as it always has been, due to Forum Posting Maximum Length]
2020-05-03 04:49:02 driver-btm-api.c:201:set_miner_status: STATUS_OKAY
2020-05-03 04:53:02 thread.c:422:is_zero_nonce_happened: chain_nonce[0] = 111804
2020-05-03 04:53:02 thread.c:422:is_zero_nonce_happened: chain_nonce[1] = 106763
2020-05-03 04:53:02 thread.c:422:is_zero_nonce_happened: chain_nonce[2] = 91522
2020-05-03 05:18:02 thread.c:204:calc_hashrate_avg: avg rate is 39414.58 in 30 mins
2020-05-03 05:18:02 temperature.c:450:temp_statistics_show: pcb temp 44~57 chip temp 65~80
2020-05-03 05:48:03 thread.c:204:calc_hashrate_avg: avg rate is 39042.75 in 30 mins
2020-05-03 05:48:03 temperature.c:450:temp_statistics_show: pcb temp 44~57 chip temp 65~80
2020-05-03 05:48:03 thread.c:285:check_hashrate: latest avg rate < 0.98......
2020-05-03 05:48:03 thread.c:286:check_hashrate: current PCB min temperature 44
2020-05-03 05:48:03 thread.c:287:check_hashrate: current voltage is 17.20V, working voltage is 17.20V
2020-05-03 05:48:03 thread.c:312:check_hashrate: high temp, voltage has already increased 0.1V/0.2V
2020-05-03 06:18:04 thread.c:204:calc_hashrate_avg: avg rate is 39262.43 in 30 mins
2020-05-03 06:18:04 temperature.c:450:temp_statistics_show: pcb temp 44~57 chip temp 65~80
[Due to Forum Post limitation deleted - Same as above and below 10 iterations of the same of "current PCB min temperature" 44 to 45]
2020-05-03 13:18:22 thread.c:204:calc_hashrate_avg: avg rate is 39077.63 in 30 mins
2020-05-03 13:18:22 temperature.c:450:temp_statistics_show: pcb temp 45~57 chip temp 66~80
2020-05-03 13:18:22 thread.c:285:check_hashrate: latest avg rate < 0.98......
2020-05-03 13:18:22 thread.c:286:check_hashrate: current PCB min temperature 45
2020-05-03 13:18:22 thread.c:287:check_hashrate: current voltage is 17.20V, working voltage is 17.20V
2020-05-03 13:18:22 thread.c:312:check_hashrate: high temp, voltage has already increased 0.1V/0.2V
2020-05-03 13:48:24 thread.c:204:calc_hashrate_avg: avg rate is 38996.33 in 30 mins
2020-05-03 13:48:24 temperature.c:450:temp_statistics_show: pcb temp 38~56 chip temp 59~79
2020-05-03 13:48:24 thread.c:285:check_hashrate: latest avg rate < 0.98......
2020-05-03 13:48:24 thread.c:286:check_hashrate: current PCB min temperature 38
2020-05-03 13:48:24 thread.c:287:check_hashrate: current voltage is 17.20V, working voltage is 17.20V
2020-05-03 13:48:24 thread.c:312:check_hashrate: high temp, voltage has already increased 0.1V/0.2V
2020-05-03 14:18:25 thread.c:204:calc_hashrate_avg: avg rate is 39111.03 in 30 mins
2020-05-03 14:18:25 temperature.c:450:temp_statistics_show: pcb temp 38~56 chip temp 59~80
2020-05-03 14:18:25 thread.c:285:check_hashrate: latest avg rate < 0.98......
2020-05-03 14:18:25 thread.c:286:check_hashrate: current PCB min temperature 38
2020-05-03 14:18:25 thread.c:287:check_hashrate: current voltage is 17.20V, working voltage is 17.20V
2020-05-03 14:18:25 thread.c:312:check_hashrate: high temp, voltage has already increased 0.1V/0.2V
2020-05-03 14:48:26 thread.c:204:calc_hashrate_avg: avg rate is 38897.26 in 30 mins
2020-05-03 14:48:26 temperature.c:450:temp_statistics_show: pcb temp 37~55 chip temp 58~79
2020-05-03 14:48:26 thread.c:285:check_hashrate: latest avg rate < 0.98......
2020-05-03 14:48:26 thread.c:286:check_hashrate: current PCB min temperature 37
2020-05-03 14:48:26 thread.c:287:check_hashrate: current voltage is 17.20V, working voltage is 17.20V
2020-05-03 14:48:26 thread.c:312:check_hashrate: high temp, voltage has already increased 0.1V/0.2V
2020-05-03 15:18:28 thread.c:204:calc_hashrate_avg: avg rate is 39043.82 in 30 mins
2020-05-03 15:18:28 temperature.c:450:temp_statistics_show: pcb temp 38~56 chip temp 59~80
2020-05-03 15:18:28 thread.c:285:check_hashrate: latest avg rate < 0.98......
2020-05-03 15:18:28 thread.c:286:check_hashrate: current PCB min temperature 38
2020-05-03 15:18:28 thread.c:287:check_hashrate: current voltage is 17.20V, working voltage is 17.20V
2020-05-03 15:18:28 thread.c:312:check_hashrate: high temp, voltage has already increased 0.1V/0.2V
2020-05-03 15:48:29 thread.c:204:calc_hashrate_avg: avg rate is 39100.51 in 30 mins
2020-05-03 15:48:29 temperature.c:450:temp_statistics_show: pcb temp 39~56 chip temp 59~80
2020-05-03 15:48:29 thread.c:285:check_hashrate: latest avg rate < 0.98......
2020-05-03 15:48:29 thread.c:286:check_hashrate: current PCB min temperature 39
2020-05-03 15:48:29 thread.c:287:check_hashrate: current voltage is 17.20V, working voltage is 17.20V
2020-05-03 15:48:29 thread.c:312:check_hashrate: high temp, voltage has already increased 0.1V/0.2V
2020-05-03 16:05:48 driver-btm-api.c:201:set_miner_status: WARN_NET_LOST
2020-05-03 16:06:23 driver-btm-api.c:1293:dhash_chip_send_job: Version num 1
2020-05-03 16:06:55 driver-btm-api.c:1293:dhash_chip_send_job: Version num 4
2020-05-03 16:06:55 driver-btm-api.c:201:set_miner_status: STATUS_OKAY
[Due to Forum Post limitation deleted - Same as above and below 12 iterations of the same of "current PCB min temperature" 39 to 41]
2020-05-03 23:48:49 thread.c:204:calc_hashrate_avg: avg rate is 39154.78 in 30 mins
2020-05-03 23:48:49 temperature.c:450:temp_statistics_show: pcb temp 40~56 chip temp 62~80
2020-05-03 23:48:49 thread.c:285:check_hashrate: latest avg rate < 0.98......
2020-05-03 23:48:49 thread.c:286:check_hashrate: current PCB min temperature 40
2020-05-03 23:48:49 thread.c:287:check_hashrate: current voltage is 17.20V, working voltage is 17.20V
2020-05-03 23:48:49 thread.c:312:check_hashrate: high temp, voltage has already increased 0.1V/0.2V
2020-05-04 00:18:51 thread.c:204:calc_hashrate_avg: avg rate is 38955.13 in 30 mins
2020-05-04 00:18:51 temperature.c:450:temp_statistics_show: pcb temp 37~55 chip temp 59~80
2020-05-04 00:18:51 thread.c:285:check_hashrate: latest avg rate < 0.98......
2020-05-04 00:18:51 thread.c:286:check_hashrate: current PCB min temperature 37
2020-05-04 00:18:51 thread.c:287:check_hashrate: current voltage is 17.20V, working voltage is 17.20V
2020-05-04 00:18:51 thread.c:312:check_hashrate: high temp, voltage has already increased 0.1V/0.2V
2020-05-04 00:48:52 thread.c:204:calc_hashrate_avg: avg rate is 38934.22 in 30 mins
2020-05-04 00:48:52 temperature.c:450:temp_statistics_show: pcb temp 36~53 chip temp 58~78
2020-05-04 00:48:52 thread.c:285:check_hashrate: latest avg rate < 0.98......
2020-05-04 00:48:52 thread.c:286:check_hashrate: current PCB min temperature 36
2020-05-04 00:48:52 thread.c:287:check_hashrate: current voltage is 17.20V, working voltage is 17.20V
2020-05-04 00:48:52 thread.c:312:check_hashrate: high temp, voltage has already increased 0.1V/0.2V
2020-05-04 01:18:53 thread.c:204:calc_hashrate_avg: avg rate is 39152.60 in 30 mins
2020-05-04 01:18:53 temperature.c:450:temp_statistics_show: pcb temp 41~56 chip temp 62~80
2020-05-04 01:18:53 thread.c:285:check_hashrate: latest avg rate < 0.98......
2020-05-04 01:18:53 thread.c:286:check_hashrate: current PCB min temperature 41
2020-05-04 01:18:53 thread.c:287:check_hashrate: current voltage is 17.20V, working voltage is 17.20V
2020-05-04 01:18:53 thread.c:312:check_hashrate: high temp, voltage has already increased 0.1V/0.2V
2020-05-04 01:48:55 thread.c:204:calc_hashrate_avg: avg rate is 39297.96 in 30 mins
2020-05-04 01:48:55 temperature.c:450:temp_statistics_show: pcb temp 41~56 chip temp 62~80
[Due to Forum Post limitation deleted - Same as above and below 22 iterations of the same of "current PCB min temperature" 42 to 44]
2020-05-04 15:19:29 thread.c:204:calc_hashrate_avg: avg rate is 38970.55 in 30 mins
2020-05-04 15:19:29 temperature.c:450:temp_statistics_show: pcb temp 44~57 chip temp 65~80
2020-05-04 15:19:29 thread.c:285:check_hashrate: latest avg rate < 0.98......
2020-05-04 15:19:29 thread.c:286:check_hashrate: current PCB min temperature 44
2020-05-04 15:19:29 thread.c:287:check_hashrate: current voltage is 17.20V, working voltage is 17.20V
2020-05-04 15:19:29 thread.c:312:check_hashrate: high temp, voltage has already increased 0.1V/0.2V
2020-05-04 15:49:31 thread.c:204:calc_hashrate_avg: avg rate is 39149.93 in 30 mins
2020-05-04 15:49:31 temperature.c:450:temp_statistics_show: pcb temp 37~56 chip temp 57~79
2020-05-04 15:49:31 thread.c:285:check_hashrate: latest avg rate < 0.98......
2020-05-04 15:49:31 thread.c:286:check_hashrate: current PCB min temperature 37
2020-05-04 15:49:31 thread.c:287:check_hashrate: current voltage is 17.20V, working voltage is 17.20V
2020-05-04 15:49:31 thread.c:312:check_hashrate: high temp, voltage has already increased 0.1V/0.2V
2020-05-04 16:19:32 thread.c:204:calc_hashrate_avg: avg rate is 38912.71 in 30 mins
2020-05-04 16:19:32 temperature.c:450:temp_statistics_show: pcb temp 36~53 chip temp 58~78
2020-05-04 16:19:32 thread.c:285:check_hashrate: latest avg rate < 0.98......
2020-05-04 16:19:32 thread.c:286:check_hashrate: current PCB min temperature 36
2020-05-04 16:19:32 thread.c:287:check_hashrate: current voltage is 17.20V, working voltage is 17.20V
2020-05-04 16:19:32 thread.c:312:check_hashrate: high temp, voltage has already increased 0.1V/0.2V
2020-05-04 16:49:33 thread.c:204:calc_hashrate_avg: avg rate is 39069.31 in 30 mins
2020-05-04 16:49:33 temperature.c:450:temp_statistics_show: pcb temp 37~54 chip temp 58~79
2020-05-04 16:49:33 thread.c:285:check_hashrate: latest avg rate < 0.98......
2020-05-04 16:49:33 thread.c:286:check_hashrate: current PCB min temperature 37
2020-05-04 16:49:33 thread.c:287:check_hashrate: current voltage is 17.20V, working voltage is 17.20V
2020-05-04 16:49:33 thread.c:312:check_hashrate: high temp, voltage has already increased 0.1V/0.2V
2020-05-04 17:19:35 thread.c:204:calc_hashrate_avg: avg rate is 39310.65 in 30 mins
2020-05-04 17:19:35 temperature.c:450:temp_statistics_show: pcb temp 36~53 chip temp 58~77
2020-05-04 17:49:36 thread.c:204:calc_hashrate_avg: avg rate is 38951.43 in 30 mins
2020-05-04 17:49:36 temperature.c:450:temp_statistics_show: pcb temp 36~53 chip temp 58~77
2020-05-04 17:49:36 thread.c:285:check_hashrate: latest avg rate < 0.98......
2020-05-04 17:49:36 thread.c:286:check_hashrate: current PCB min temperature 36
2020-05-04 17:49:36 thread.c:287:check_hashrate: current voltage is 17.20V, working voltage is 17.20V
2020-05-04 17:49:36 thread.c:312:check_hashrate: high temp, voltage has already increased 0.1V/0.2V
2020-05-04 18:05:32 driver-btm-api.c:201:set_miner_status: WARN_NET_LOST
2020-05-04 18:06:43 driver-btm-api.c:1293:dhash_chip_send_job: Version num 1
2020-05-04 18:06:53 driver-btm-api.c:1293:dhash_chip_send_job: Version num 4
2020-05-04 18:06:53 driver-btm-api.c:201:set_miner_status: STATUS_OKAY
2020-05-04 18:19:37 thread.c:204:calc_hashrate_avg: avg rate is 39049.05 in 30 mins
2020-05-04 18:19:37 temperature.c:450:temp_statistics_show: pcb temp 36~52 chip temp 57~77
2020-05-04 18:19:37 thread.c:285:check_hashrate: latest avg rate < 0.98......
2020-05-04 18:19:37 thread.c:286:check_hashrate: current PCB min temperature 36
2020-05-04 18:19:37 thread.c:287:check_hashrate: current voltage is 17.20V, working voltage is 17.20V
2020-05-04 18:19:37 thread.c:312:check_hashrate: high temp, voltage has already increased 0.1V/0.2V
2020-05-04 18:49:38 thread.c:204:calc_hashrate_avg: avg rate is 39058.82 in 30 mins
2020-05-04 18:49:38 temperature.c:450:temp_statistics_show: pcb temp 34~51 chip temp 56~75
2020-05-04 18:49:38 thread.c:285:check_hashrate: latest avg rate < 0.98......
2020-05-04 18:49:38 thread.c:286:check_hashrate: current PCB min temperature 34
2020-05-04 18:49:38 thread.c:287:check_hashrate: current voltage is 17.20V, working voltage is 17.20V
2020-05-04 18:49:38 thread.c:312:check_hashrate: high temp, voltage has already increased 0.1V/0.2V
2020-05-04 19:19:40 thread.c:204:calc_hashrate_avg: avg rate is 39027.68 in 30 mins
2020-05-04 19:19:40 temperature.c:450:temp_statistics_show: pcb temp 34~51 chip temp 56~75
2020-05-04 19:19:40 thread.c:285:check_hashrate: latest avg rate < 0.98......
2020-05-04 19:19:40 thread.c:286:check_hashrate: current PCB min temperature 34
2020-05-04 19:19:40 thread.c:287:check_hashrate: current voltage is 17.20V, working voltage is 17.20V
2020-05-04 19:19:40 thread.c:312:check_hashrate: high temp, voltage has already increased 0.1V/0.2V
2020-05-04 19:49:41 thread.c:204:calc_hashrate_avg: avg rate is 39114.57 in 30 mins
2020-05-04 19:49:41 temperature.c:450:temp_statistics_show: pcb temp 34~50 chip temp 56~75
2020-05-04 19:49:41 thread.c:285:check_hashrate: latest avg rate < 0.98......
2020-05-04 19:49:41 thread.c:286:check_hashrate: current PCB min temperature 34
2020-05-04 19:49:41 thread.c:287:check_hashrate: current voltage is 17.20V, working voltage is 17.20V
2020-05-04 19:49:41 thread.c:312:check_hashrate: high temp, voltage has already increased 0.1V/0.2V
2020-05-04 20:05:02 driver-btm-api.c:201:set_miner_status: WARN_NET_LOST
2020-05-04 20:05:44 driver-btm-api.c:1293:dhash_chip_send_job: Version num 1
2020-05-04 20:06:07 driver-btm-api.c:1293:dhash_chip_send_job: Version num 4
2020-05-04 20:06:07 driver-btm-api.c:201:set_miner_status: STATUS_OKAY
2020-05-04 20:19:42 thread.c:204:calc_hashrate_avg: avg rate is 38422.16 in 30 mins
2020-05-04 20:19:42 temperature.c:450:temp_statistics_show: pcb temp 35~52 chip temp 56~77
2020-05-04 20:19:42 thread.c:285:check_hashrate: latest avg rate < 0.98......
2020-05-04 20:19:42 thread.c:286:check_hashrate: current PCB min temperature 35
2020-05-04 20:19:42 thread.c:287:check_hashrate: current voltage is 17.20V, working voltage is 17.20V
2020-05-04 20:19:42 thread.c:312:check_hashrate: high temp, voltage has already increased 0.1V/0.2V
2020-05-04 20:49:44 thread.c:204:calc_hashrate_avg: avg rate is 38984.30 in 30 mins
2020-05-04 20:49:44 temperature.c:450:temp_statistics_show: pcb temp 39~56 chip temp 60~80
2020-05-04 20:49:44 thread.c:285:check_hashrate: latest avg rate < 0.98......
2020-05-04 20:49:44 thread.c:286:check_hashrate: current PCB min temperature 39
2020-05-04 20:49:44 thread.c:287:check_hashrate: current voltage is 17.20V, working voltage is 17.20V
2020-05-04 20:49:44 thread.c:312:check_hashrate: high temp, voltage has already increased 0.1V/0.2V
[Due to Forum Post limitation deleted - Same as above and below 24 iterations of the same of "current PCB min temperature" 40 to 44]
2020-05-05 16:20:34 thread.c:204:calc_hashrate_avg: avg rate is 39062.38 in 30 mins
2020-05-05 16:20:34 temperature.c:450:temp_statistics_show: pcb temp 38~55 chip temp 60~80
2020-05-05 16:20:34 thread.c:285:check_hashrate: latest avg rate < 0.98......
2020-05-05 16:20:34 thread.c:286:check_hashrate: current PCB min temperature 38
2020-05-05 16:20:34 thread.c:287:check_hashrate: current voltage is 17.20V, working voltage is 17.20V
2020-05-05 16:20:34 thread.c:312:check_hashrate: high temp, voltage has already increased 0.1V/0.2V
Kernel Log after Fan 100%: Booting Linux on physical CPU 0x0
Linux version 4.6.0-xilinx-gff8137b-dirty (lzq@armdev2) (gcc version 4.8.3 20140320 (prerelease) (Sourcery CodeBench Lite 2014.05-23) ) #25 SMP PREEMPT Fri Nov 23 15:30:52 CST 2018
CPU: ARMv7 Processor [413fc090] revision 0 (ARMv7), cr=18c5387d
CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
Machine model: Xilinx Zynq
cma: Reserved 16 MiB at 0x0e000000
Memory policy: Data cache writealloc
On node 0 totalpages: 61440
free_area_init_node: node 0, pgdat c0b39280, node_mem_map cde10000
Normal zone: 480 pages used for memmap
Normal zone: 0 pages reserved
Normal zone: 61440 pages, LIFO batch:15
percpu: Embedded 12 pages/cpu @cddf1000 s19776 r8192 d21184 u49152
pcpu-alloc: s19776 r8192 d21184 u49152 alloc=12*4096
pcpu-alloc: [0] 0 [0] 1
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 60960
Kernel command line: mem=240M console=ttyPS0,115200 ramdisk_size=33554432 root=/dev/ram rw earlyprintk
PID hash table entries: 1024 (order: 0, 4096 bytes)
Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
Memory: 203756K/245760K available (6345K kernel code, 231K rwdata, 1896K rodata, 1024K init, 223K bss, 25620K reserved, 16384K cma-reserved, 0K highmem)
Virtual kernel memory layout:
vector : 0xffff0000 - 0xffff1000 ( 4 kB)
fixmap : 0xffc00000 - 0xfff00000 (3072 kB)
vmalloc : 0xcf800000 - 0xff800000 ( 768 MB)
lowmem : 0xc0000000 - 0xcf000000 ( 240 MB)
pkmap : 0xbfe00000 - 0xc0000000 ( 2 MB)
modules : 0xbf000000 - 0xbfe00000 ( 14 MB)
.text : 0xc0008000 - 0xc090c424 (9234 kB)
.init : 0xc0a00000 - 0xc0b00000 (1024 kB)
.data : 0xc0b00000 - 0xc0b39fe0 ( 232 kB)
.bss : 0xc0b39fe0 - 0xc0b71c28 ( 224 kB)
Preemptible hierarchical RCU implementation.
Build-time adjustment of leaf fanout to 32.
RCU restricting CPUs from NR_CPUS=4 to nr_cpu_ids=2.
RCU: Adjusting geometry for rcu_fanout_leaf=32, nr_cpu_ids=2
NR_IRQS:16 nr_irqs:16 16
efuse mapped to cf800000
ps7-slcr mapped to cf802000
L2C: platform modifies aux control register: 0x72360000 -> 0x72760000
L2C: DT/platform modifies aux control register: 0x72360000 -> 0x72760000
L2C-310 erratum 769419 enabled
L2C-310 enabling early BRESP for Cortex-A9
L2C-310 full line of zeros enabled for Cortex-A9
L2C-310 ID prefetch enabled, offset 1 lines
L2C-310 dynamic clock gating enabled, standby mode enabled
L2C-310 cache controller enabled, 8 ways, 512 kB
L2C-310: CACHE_ID 0x410000c8, AUX_CTRL 0x76760001
zynq_clock_init: clkc starts at cf802100
Zynq clock init
sched_clock: 64 bits at 333MHz, resolution 3ns, wraps every 4398046511103ns
clocksource: arm_global_timer: mask: 0xffffffffffffffff max_cycles: 0x4ce07af025, max_idle_ns: 440795209040 ns
Switching to timer-based delay loop, resolution 3ns
clocksource: ttc_clocksource: mask: 0xffff max_cycles: 0xffff, max_idle_ns: 537538477 ns
ps7-ttc #0 at cf80a000, irq=18
Console: colour dummy device 80x30
Calibrating delay loop (skipped), value calculated using timer frequency.. 666.66 BogoMIPS (lpj=3333333)
pid_max: default: 32768 minimum: 301
Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
CPU: Testing write buffer coherency: ok
CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
Setting up static identity map for 0x100000 - 0x100058
CPU1: failed to boot: -1
Brought up 1 CPUs
SMP: Total of 1 processors activated (666.66 BogoMIPS).
CPU: All CPU(s) started in SVC mode.
devtmpfs: initialized
VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4
clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
pinctrl core: initialized pinctrl subsystem
NET: Registered protocol family 16
DMA: preallocated 256 KiB pool for atomic coherent allocations
cpuidle: using governor menu
hw-breakpoint: found 5 (+1 reserved) breakpoint and 1 watchpoint registers.
hw-breakpoint: maximum watchpoint size is 4 bytes.
zynq-ocm f800c000.ps7-ocmc: ZYNQ OCM pool: 256 KiB @ 0xcf880000
vgaarb: loaded
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
media: Linux media interface: v0.10
Linux video capture interface: v2.00
pps_core: LinuxPPS API ver. 1 registered
pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
PTP clock support registered
EDAC MC: Ver: 3.0.0
Advanced Linux Sound Architecture Driver Initialized.
clocksource: Switched to clocksource arm_global_timer
NET: Registered protocol family 2
TCP established hash table entries: 2048 (order: 1, 8192 bytes)
TCP bind hash table entries: 2048 (order: 2, 16384 bytes)
TCP: Hash tables configured (established 2048 bind 2048)
UDP hash table entries: 256 (order: 1, 8192 bytes)
UDP-Lite hash table entries: 256 (order: 1, 8192 bytes)
NET: Registered protocol family 1
RPC: Registered named UNIX socket transport module.
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
PCI: CLS 0 bytes, default 64
Trying to unpack rootfs image as initramfs...
rootfs image is not initramfs (no cpio magic); looks like an initrd
Freeing initrd memory: 12580K (cceb8000 - cdb01000)
hw perfevents: enabled with armv7_cortex_a9 PMU driver, 7 counters available
futex hash table entries: 512 (order: 3, 32768 bytes)
workingset: timestamp_bits=28 max_order=16 bucket_order=0
jffs2: version 2.2. (NAND) (SUMMARY) © 2001-2006 Red Hat, Inc.
io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered (default)
dma-pl330 f8003000.ps7-dma: Loaded driver for PL330 DMAC-241330
dma-pl330 f8003000.ps7-dma: DBUFF-128x8bytes Num_Chans-8 Num_Peri-4 Num_Events-16
e0000000.serial: ttyPS0 at MMIO 0xe0000000 (irq = 158, base_baud = 6249999) is a xuartps
console [ttyPS0] enabled
xdevcfg f8007000.ps7-dev-cfg: ioremap 0xf8007000 to cf86e000
[drm] Initialized drm 1.1.0 20060810
brd: module loaded
loop: module loaded
CAN device driver interface
gpiod_set_value: invalid GPIO
libphy: MACB_mii_bus: probed
macb e000b000.ethernet eth0: Cadence GEM rev 0x00020118 at 0xe000b000 irq 31 (00:0a:35:00:00:00)
Generic PHY e000b000.etherne:00: attached PHY driver [Generic PHY] (mii_bus:phy_addr=e000b000.etherne:00, irq=-1)
e1000e: Intel(R) PRO/1000 Network Driver - 3.2.6-k
e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
ehci-pci: EHCI PCI platform driver
usbcore: registered new interface driver usb-storage
mousedev: PS/2 mouse device common for all mice
i2c /dev entries driver
Xilinx Zynq CpuIdle Driver started
sdhci: Secure Digital Host Controller Interface driver
sdhci: Copyright(c) Pierre Ossman
sdhci-pltfm: SDHCI platform and OF driver helper
mmc0: SDHCI controller on e0100000.ps7-sdio [e0100000.ps7-sdio] using ADMA
ledtrig-cpu: registered to indicate activity on CPUs
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
nand: device found, Manufacturer ID: 0x2c, Chip ID: 0xda
nand: Micron MT29F2G08ABAGAWP
nand: 256 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 128
nand: WARNING: pl35x-nand: the ECC used on your system is too weak compared to the one required by the NAND chip
Bad block table found at page 131008, version 0x01
Bad block table found at page 130944, version 0x01
6 ofpart partitions found on MTD device pl35x-nand
Creating 6 MTD partitions on "pl35x-nand":
0x000000000000-0x000002800000 : "BOOT.bin-env-dts-kernel"
0x000002800000-0x000004800000 : "ramfs"
0x000004800000-0x000005000000 : "configs"
0x000005000000-0x000006000000 : "reserve"
0x000006000000-0x000008000000 : "ramfs-bak"
0x000008000000-0x000010000000 : "reserve1"
NET: Registered protocol family 10
sit: IPv6 over IPv4 tunneling driver
NET: Registered protocol family 17
can: controller area network core (rev 20120528 abi 9)
NET: Registered protocol family 29
can: raw protocol (rev 20120528)
can: broadcast manager protocol (rev 20120528 t)
can: netlink gateway (rev 20130117) max_hops=1
zynq_pm_ioremap: no compatible node found for 'xlnx,zynq-ddrc-a05'
zynq_pm_late_init: Unable to map DDRC IO memory.
Registering SWP/SWPB emulation handler
hctosys: unable to open rtc device (rtc0)
ALSA device list:
No soundcards found.
RAMDISK: gzip image found at block 0
EXT4-fs (ram0): couldn't mount as ext3 due to feature incompatibilities
EXT4-fs (ram0): mounted filesystem without journal. Opts: (null)
VFS: Mounted root (ext4 filesystem) on device 1:0.
devtmpfs: mounted
Freeing unused kernel memory: 1024K (c0a00000 - c0b00000)
EXT4-fs (ram0): re-mounted. Opts: block_validity,delalloc,barrier,user_xattr
random: dd urandom read with 0 bits of entropy available
ubi0: attaching mtd2
ubi0: scanning is finished
ubi0: attached mtd2 (name "configs", size 8 MiB)
ubi0: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
ubi0: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
ubi0: VID header offset: 2048 (aligned 2048), data offset: 4096
ubi0: good PEBs: 64, bad PEBs: 0, corrupted PEBs: 0
ubi0: user volume: 1, internal volumes: 1, max. volumes count: 128
ubi0: max/mean erase counter: 6/2, WL threshold: 4096, image sequence number: 4244297529
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 01559AD8-7B6A-42E6-A3FE-EDF3659527A9, 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: 1052/340, WL threshold: 4096, image sequence number: 4185749592
ubi1: available PEBs: 0, total reserved PEBs: 1020, PEBs reserved for bad PEB handling: 36
ubi1: background thread "ubi_bgt1d" started, PID 720
UBIFS (ubi1:0): background thread "ubifs_bgt1_0" started, PID 723
UBIFS (ubi1:0): recovery needed
UBIFS (ubi1:0): recovery completed
UBIFS (ubi1:0): UBIFS: mounted UBI device 1, volume 0, name "reserve1"
UBIFS (ubi1:0): LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
UBIFS (ubi1:0): FS size: 123039744 bytes (117 MiB, 969 LEBs), journal size 6221824 bytes (5 MiB, 49 LEBs)
UBIFS (ubi1:0): reserved for root: 4952683 bytes (4836 KiB)
UBIFS (ubi1:0): media format: w4/r0 (latest is w4/r0), UUID 4829CF2C-7435-4146-B2FD-0826AAE8443A, small LPT model
IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
macb e000b000.ethernet eth0: unable to generate target frequency: 25000000 Hz
macb e000b000.ethernet eth0: link up (100/Full)
IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
In axi fpga driver!
request_mem_region OK!
AXI fpga dev virtual address is 0xcfb38000
*base_vir_addr = 0xab013
In fpga mem driver!
request_mem_region OK!
fpga mem virtual address is 0xd2000000
random: nonblocking pool is initialized
2020-05-05 16:30:15 driver-btm-api.c:631:init_freq_mode: This is scan-user version
2020-05-05 16:30:15 driver-btm-api.c:1994:bitmain_soc_init: opt_multi_version = 1
2020-05-05 16:30:15 driver-btm-api.c:1995:bitmain_soc_init: opt_bitmain_ab = 1
2020-05-05 16:30:15 driver-btm-api.c:1996:bitmain_soc_init: opt_bitmain_work_mode = 0
2020-05-05 16:30:15 driver-btm-api.c:1997:bitmain_soc_init: Miner compile time: Tue Dec 24 16:13:07 CST 2019 type: Antminer T17
2020-05-05 16:30:15 driver-btm-api.c:1998:bitmain_soc_init: commit version: e93a09b 2019-12-24 16:03:45, build by: lol 2019-12-24 16:19:49
2020-05-05 16:30:15 driver-btm-api.c:1810:show_sn: no SN got, please write SN to /nvdata/sn
2020-05-05 16:30:15 driver-btm-api.c:1135:miner_device_init: Detect 256MB control board of XILINX
2020-05-05 16:30:15 driver-btm-api.c:1083:init_fan_parameter: fan_eft : 1 fan_pwm : 100
2020-05-05 16:30:15 thread.c:789:create_read_nonce_reg_thread: create thread
2020-05-05 16:30:21 driver-btm-api.c:1067:init_miner_version: miner ID : 8042750618c0885c
2020-05-05 16:30:21 driver-btm-api.c:1073:init_miner_version: FPGA Version = 0xB013
2020-05-05 16:30:23 eeprom.c:425:check_pattern_test_level: invalid pattern test result. ignore
2020-05-05 16:30:25 eeprom.c:425:check_pattern_test_level: invalid pattern test result. ignore
2020-05-05 16:30:27 eeprom.c:425:check_pattern_test_level: invalid pattern test result. ignore
2020-05-05 16:30:27 driver-btm-api.c:705:get_product_id: product_id[0] = 1
2020-05-05 16:30:27 driver-btm-api.c:705:get_product_id: product_id[1] = 1
2020-05-05 16:30:27 driver-btm-api.c:705:get_product_id: product_id[2] = 1
2020-05-05 16:30:27 driver-btm-api.c:1633:get_ccdly_opt: ccdly_opt[0] = 1
2020-05-05 16:30:27 driver-btm-api.c:1633:get_ccdly_opt: ccdly_opt[1] = 1
2020-05-05 16:30:27 driver-btm-api.c:1633:get_ccdly_opt: ccdly_opt[2] = 1
2020-05-05 16:30:27 driver-btm-api.c:1877:bitmain_board_init: g_ccdly_opt = 1
2020-05-05 16:30:27 driver-btm-api.c:644:_set_project_type: project:2
2020-05-05 16:30:27 driver-btm-api.c:674:_set_project_type: Project type: Antminer T17
2020-05-05 16:30:27 driver-btm-api.c:685:dump_pcb_bom_version: Chain [0] PCB Version: 0x0100
2020-05-05 16:30:27 driver-btm-api.c:686:dump_pcb_bom_version: Chain [0] BOM Version: 0x0100
2020-05-05 16:30:27 driver-btm-api.c:685:dump_pcb_bom_version: Chain [1] PCB Version: 0x0100
2020-05-05 16:30:27 driver-btm-api.c:686:dump_pcb_bom_version: Chain [1] BOM Version: 0x0100
2020-05-05 16:30:27 driver-btm-api.c:685:dump_pcb_bom_version: Chain [2] PCB Version: 0x0100
2020-05-05 16:30:27 driver-btm-api.c:686:dump_pcb_bom_version: Chain [2] BOM Version: 0x0100
2020-05-05 16:30:29 driver-btm-api.c:1897:bitmain_board_init: Fan check passed.
2020-05-05 16:30:29 register.c:283:get_register: !!! reg crc error
2020-05-05 16:30:31 board.c:36:jump_and_app_check_restore_pic: chain[0] PIC jump to app
2020-05-05 16:30:34 board.c:40:jump_and_app_check_restore_pic: Check chain[0] PIC fw version=0xb9
2020-05-05 16:30:36 board.c:36:jump_and_app_check_restore_pic: chain[1] PIC jump to app
2020-05-05 16:30:39 board.c:40:jump_and_app_check_restore_pic: Check chain[1] PIC fw version=0xb9
2020-05-05 16:30:41 board.c:36:jump_and_app_check_restore_pic: chain[2] PIC jump to app
2020-05-05 16:30:45 board.c:40:jump_and_app_check_restore_pic: Check chain[2] PIC fw version=0xb9
2020-05-05 16:30:45 thread.c:784:create_pic_heart_beat_thread: create thread
2020-05-05 16:30:45 power_api.c:55:power_init: power init ...
2020-05-05 16:30:45 driver-btm-api.c:1907:bitmain_board_init: Enter 30s sleep to make sure power release finish.
2020-05-05 16:31:17 power_api.c:232:set_iic_power_to_highest_voltage: setting to voltage: 17.00 ...
2020-05-05 16:31:22 power_api.c:124:check_voltage_multi: retry time: 0
2020-05-05 16:31:24 power_api.c:86:get_average_voltage: chain[0], voltage is: 17.107793
2020-05-05 16:31:26 power_api.c:86:get_average_voltage: chain[1], voltage is: 17.113916
2020-05-05 16:31:28 power_api.c:86:get_average_voltage: chain[2], voltage is: 17.211885
2020-05-05 16:31:28 power_api.c:97:get_average_voltage: aveage voltage is: 17.144531
2020-05-05 16:31:28 power_api.c:182:set_iic_power_by_voltage: now set voltage to : 17.000000
2020-05-05 16:31:28 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[0]: chip baud = 115200, chip_divider = 26
2020-05-05 16:31:28 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[1]: chip baud = 115200, chip_divider = 26
2020-05-05 16:31:28 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[2]: chip baud = 115200, chip_divider = 26
2020-05-05 16:31:28 uart.c:80:set_baud: set fpga_baud = 115200, fpga_divider = 26
2020-05-05 16:31:39 driver-btm-api.c:1010:check_asic_number_with_power_on: Chain[0]: find 29 asic, times 0
2020-05-05 16:31:49 driver-btm-api.c:1010:check_asic_number_with_power_on: Chain[0]: find 30 asic, times 1
2020-05-05 16:31:59 driver-btm-api.c:1010:check_asic_number_with_power_on: Chain[1]: find 30 asic, times 0
2020-05-05 16:32:09 driver-btm-api.c:1010:check_asic_number_with_power_on: Chain[2]: find 30 asic, times 0
2020-05-05 16:32:13 driver-btm-api.c:348:set_order_clock: chain[0]: set order clock, stragegy 3 clock_en=0x1
2020-05-05 16:32:13 driver-btm-api.c:348:set_order_clock: chain[1]: set order clock, stragegy 3 clock_en=0x1
2020-05-05 16:32:13 driver-btm-api.c:348:set_order_clock: chain[2]: set order clock, stragegy 3 clock_en=0x1
2020-05-05 16:32:13 driver-hash-chip.c:490:set_clock_delay_control: core_data = 0xb4
2020-05-05 16:32:13 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[0]: chip baud = 3000000, chip_divider = 0
2020-05-05 16:32:13 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[1]: chip baud = 3000000, chip_divider = 0
2020-05-05 16:32:13 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[2]: chip baud = 3000000, chip_divider = 0
2020-05-05 16:32:13 uart.c:80:set_baud: set fpga_baud = 3000000, fpga_divider = 0
2020-05-05 16:32:13 driver-btm-api.c:1660:check_clock_counter: freq 50 clock_counter_limit 6
2020-05-05 16:32:14 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[0]: chip baud = 115200, chip_divider = 26
2020-05-05 16:32:14 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[1]: chip baud = 115200, chip_divider = 26
2020-05-05 16:32:14 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[2]: chip baud = 115200, chip_divider = 26
2020-05-05 16:32:14 uart.c:80:set_baud: set fpga_baud = 115200, fpga_divider = 26
2020-05-05 16:32:14 voltage[0] = 1710
2020-05-05 16:32:14 voltage[1] = 1710
2020-05-05 16:32:14 voltage[2] = 1710
2020-05-05 16:32:14 power_api.c:140:set_working_voltage: working_voltage = 17.100000
2020-05-05 16:32:15 temperature.c:282:calibrate_temp_sensor_one_chain: Temperature sensor calibration: chain 0 success.
2020-05-05 16:32:17 temperature.c:282:calibrate_temp_sensor_one_chain: Temperature sensor calibration: chain 1 success.
2020-05-05 16:32:18 temperature.c:282:calibrate_temp_sensor_one_chain: Temperature sensor calibration: chain 2 success.
2020-05-05 16:32:18 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[0]: chip baud = 6000000, chip_divider = 7
2020-05-05 16:32:18 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[1]: chip baud = 6000000, chip_divider = 7
2020-05-05 16:32:18 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[2]: chip baud = 6000000, chip_divider = 7
2020-05-05 16:32:18 uart.c:80:set_baud: set fpga_baud = 6000000, fpga_divider = 3
2020-05-05 16:32:20 driver-btm-api.c:248:check_bringup_temp: Bring up temperature is 13
2020-05-05 16:32:20 thread.c:804:create_check_miner_status_thread: create thread
2020-05-05 16:32:20 thread.c:794:create_set_miner_status_thread: create thread
2020-05-05 16:32:20 driver-btm-api.c:581:calculate_timeout: dev->timeout = 392
2020-05-05 16:32:20 thread.c:779:create_temperature_monitor_thread: create thread
2020-05-05 16:32:20 freq_tuning.c:154:freq_tuning_get_max_freq: Max freq of tuning is 760
2020-05-05 16:32:20 power_api.c:379:slowly_set_iic_power_to_custom_voltage: slowly setting to voltage: 18.00 ...
2020-05-05 16:32:58 power_api.c:124:check_voltage_multi: retry time: 0
2020-05-05 16:32:59 power_api.c:86:get_average_voltage: chain[0], voltage is: 18.142588
2020-05-05 16:33:01 power_api.c:86:get_average_voltage: chain[1], voltage is: 18.124219
2020-05-05 16:33:03 power_api.c:86:get_average_voltage: chain[2], voltage is: 18.246679
2020-05-05 16:33:03 power_api.c:97:get_average_voltage: aveage voltage is: 18.171162
2020-05-05 16:33:03 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 42 set refdiv: 2, fbdiv: 168, postdiv1: 7, postdiv2: 7, usr divider: 1
2020-05-05 16:33:03 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 50 set refdiv: 2, fbdiv: 168, postdiv1: 7, postdiv2: 6, usr divider: 1
2020-05-05 16:33:03 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 60 set refdiv: 2, fbdiv: 168, postdiv1: 7, postdiv2: 5, usr divider: 1
2020-05-05 16:33:03 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 75 set refdiv: 2, fbdiv: 168, postdiv1: 7, postdiv2: 4, usr divider: 1
2020-05-05 16:33:03 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 100 set refdiv: 2, fbdiv: 168, postdiv1: 7, postdiv2: 3, usr divider: 1
2020-05-05 16:33:03 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 150 set refdiv: 2, fbdiv: 168, postdiv1: 7, postdiv2: 2, usr divider: 1
2020-05-05 16:33:04 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 300 set refdiv: 2, fbdiv: 168, postdiv1: 7, postdiv2: 1, usr divider: 1
2020-05-05 16:33:04 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 350 set refdiv: 2, fbdiv: 168, postdiv1: 6, postdiv2: 1, usr divider: 1
2020-05-05 16:33:04 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 420 set refdiv: 2, fbdiv: 168, postdiv1: 5, postdiv2: 1, usr divider: 1
2020-05-05 16:33:04 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 525 set refdiv: 2, fbdiv: 168, postdiv1: 4, postdiv2: 1, usr divider: 1
2020-05-05 16:33:04 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 700 set refdiv: 2, fbdiv: 168, postdiv1: 3, postdiv2: 1, usr divider: 1
2020-05-05 16:33:04 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 41 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 7, usr divider: 1
2020-05-05 16:33:04 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 47 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 6, usr divider: 1
2020-05-05 16:33:04 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 57 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 5, usr divider: 1
2020-05-05 16:33:04 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 71 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 4, usr divider: 1
2020-05-05 16:33:04 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 95 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 3, usr divider: 1
2020-05-05 16:33:05 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 143 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 2, usr divider: 1
2020-05-05 16:33:05 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 287 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 1, usr divider: 1
2020-05-05 16:33:05 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 335 set refdiv: 2, fbdiv: 161, postdiv1: 6, postdiv2: 1, usr divider: 1
2020-05-05 16:33:05 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 402 set refdiv: 2, fbdiv: 161, postdiv1: 5, postdiv2: 1, usr divider: 1
2020-05-05 16:33:05 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 503 set refdiv: 2, fbdiv: 161, postdiv1: 4, postdiv2: 1, usr divider: 1
2020-05-05 16:33:05 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 670 set refdiv: 2, fbdiv: 161, postdiv1: 3, postdiv2: 1, usr divider: 1
2020-05-05 16:33:05 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 41 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 7, usr divider: 1
2020-05-05 16:33:05 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 47 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 6, usr divider: 1
2020-05-05 16:33:05 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 57 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 5, usr divider: 1
2020-05-05 16:33:05 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 71 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 4, usr divider: 1
2020-05-05 16:33:06 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 95 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 3, usr divider: 1
2020-05-05 16:33:06 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 143 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 2, usr divider: 1
2020-05-05 16:33:06 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 287 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 1, usr divider: 1
2020-05-05 16:33:06 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 335 set refdiv: 2, fbdiv: 161, postdiv1: 6, postdiv2: 1, usr divider: 1
2020-05-05 16:33:06 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 402 set refdiv: 2, fbdiv: 161, postdiv1: 5, postdiv2: 1, usr divider: 1
2020-05-05 16:33:06 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 503 set refdiv: 2, fbdiv: 161, postdiv1: 4, postdiv2: 1, usr divider: 1
2020-05-05 16:33:06 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 670 set refdiv: 2, fbdiv: 161, postdiv1: 3, postdiv2: 1, usr divider: 1
2020-05-05 16:33:06 driver-btm-api.c:612:set_timeout: freq 700 final timeout=168
2020-05-05 16:33:06 power_api.c:146:set_higher_voltage: higher_voltage = 18.000000
2020-05-05 16:33:06 power_api.c:428:slowly_set_iic_power_to_higher_voltage: slowly setting to voltage: 18.00 ...
2020-05-05 16:33:31 power_api.c:124:check_voltage_multi: retry time: 0
2020-05-05 16:33:32 power_api.c:86:get_average_voltage: chain[0], voltage is: 18.118095
2020-05-05 16:33:34 power_api.c:86:get_average_voltage: chain[1], voltage is: 18.105849
2020-05-05 16:33:36 power_api.c:86:get_average_voltage: chain[2], voltage is: 18.197695
2020-05-05 16:33:36 power_api.c:97:get_average_voltage: aveage voltage is: 18.140547
2020-05-05 16:33:36 frequency.c:540:get_current_min_freq: current min freq 670
2020-05-05 16:33:36 driver-btm-api.c:1660:check_clock_counter: freq 670 clock_counter_limit 85
2020-05-05 16:33:37 thread.c:799:create_check_system_status_thread: create thread
2020-05-05 16:33:38 driver-btm-api.c:2113:bitmain_soc_init: Init done!
2020-05-05 16:33:38 driver-btm-api.c:201:set_miner_status: STATUS_INIT
2020-05-05 16:33:43 driver-btm-api.c:201:set_miner_status: STATUS_OKAY
2020-05-05 16:33:52 driver-btm-api.c:1293:dhash_chip_send_job: Version num 4
2020-05-05 16:33:56 thread.c:382:check_working_voltage: current PCB min temperature is 28
2020-05-05 16:33:56 thread.c:383:check_working_voltage: current voltage is 18.00V, recovery to 17.10V
2020-05-05 16:33:56 power_api.c:397:slowly_set_iic_power_to_working_voltage: slowly setting to voltage: 17.10 ...
2020-05-05 16:34:30 power_api.c:124:check_voltage_multi: retry time: 0
2020-05-05 16:34:31 power_api.c:86:get_average_voltage: chain[0], voltage is: 17.181269
2020-05-05 16:34:33 power_api.c:86:get_average_voltage: chain[1], voltage is: 17.169023
2020-05-05 16:34:35 power_api.c:86:get_average_voltage: chain[2], voltage is: 17.291484
2020-05-05 16:34:35 power_api.c:97:get_average_voltage: aveage voltage is: 17.213926
2020-05-05 16:39:34 thread.c:422:is_zero_nonce_happened: chain_nonce[0] = 17583
2020-05-05 16:39:34 thread.c:422:is_zero_nonce_happened: chain_nonce[1] = 16756
2020-05-05 16:39:34 thread.c:422:is_zero_nonce_happened: chain_nonce[2] = 14440
2020-05-05 17:04:35 thread.c:204:calc_hashrate_avg: avg rate is 39214.98 in 30 mins
2020-05-05 17:04:35 temperature.c:450:temp_statistics_show: pcb temp 28~36 chip temp 48~58
2020-05-05 17:34:36 thread.c:204:calc_hashrate_avg: avg rate is 39180.69 in 30 mins
2020-05-05 17:34:36 temperature.c:450:temp_statistics_show: pcb temp 27~35 chip temp 47~58
2020-05-05 17:34:36 thread.c:285:check_hashrate: latest avg rate < 0.98......
2020-05-05 17:34:36 thread.c:286:check_hashrate: current PCB min temperature 27
2020-05-05 17:34:36 thread.c:287:check_hashrate: current voltage is 17.10V, working voltage is 17.10V
2020-05-05 17:34:36 thread.c:318:check_hashrate: high temp, increase voltage 0.1V/0.2V to 17.20V
2020-05-05 17:34:36 driver-btm-api.c:2124:bitmain_reopen_core: reopen_core start!
2020-05-05 17:34:44 driver-btm-api.c:1067:init_miner_version: miner ID : 8042750618c0885c
2020-05-05 17:34:44 driver-btm-api.c:1073:init_miner_version: FPGA Version = 0xB013
2020-05-05 17:34:45 chain = 0, mode = 0, load_done = false.
2020-05-05 17:34:45 chain = 1, mode = 0, load_done = false.
2020-05-05 17:34:45 chain = 2, mode = 0, load_done = false.
2020-05-05 17:34:46 chain = 0, mode = 0, load_done = false.
2020-05-05 17:34:46 chain = 1, mode = 0, load_done = false.
2020-05-05 17:34:46 chain = 2, mode = 0, load_done = false.
2020-05-05 17:34:46 eeprom.c:425:check_pattern_test_level: invalid pattern test result. ignore
2020-05-05 17:34:47 chain = 0, mode = 0, load_done = false.
2020-05-05 17:34:47 chain = 1, mode = 0, load_done = false.
2020-05-05 17:34:47 chain = 2, mode = 0, load_done = false.
2020-05-05 17:34:48 chain = 0, mode = 0, load_done = false.
2020-05-05 17:34:48 chain = 1, mode = 0, load_done = false.
2020-05-05 17:34:48 chain = 2, mode = 0, load_done = false.
2020-05-05 17:34:48 eeprom.c:425:check_pattern_test_level: invalid pattern test result. ignore
2020-05-05 17:34:49 chain = 0, mode = 0, load_done = false.
2020-05-05 17:34:49 chain = 1, mode = 0, load_done = false.
2020-05-05 17:34:49 chain = 2, mode = 0, load_done = false.
2020-05-05 17:34:49 eeprom.c:425:check_pattern_test_level: invalid pattern test result. ignore
2020-05-05 17:34:49 driver-btm-api.c:705:get_product_id: product_id[0] = 1
2020-05-05 17:34:49 driver-btm-api.c:705:get_product_id: product_id[1] = 1
2020-05-05 17:34:49 driver-btm-api.c:705:get_product_id: product_id[2] = 1
2020-05-05 17:34:49 driver-btm-api.c:1633:get_ccdly_opt: ccdly_opt[0] = 1
2020-05-05 17:34:49 driver-btm-api.c:1633:get_ccdly_opt: ccdly_opt[1] = 1
2020-05-05 17:34:49 driver-btm-api.c:1633:get_ccdly_opt: ccdly_opt[2] = 1
2020-05-05 17:34:49 driver-btm-api.c:1877:bitmain_board_init: g_ccdly_opt = 1
2020-05-05 17:34:49 driver-btm-api.c:644:_set_project_type: project:2
2020-05-05 17:34:49 driver-btm-api.c:674:_set_project_type: Project type: Antminer T17
2020-05-05 17:34:49 driver-btm-api.c:685:dump_pcb_bom_version: Chain [0] PCB Version: 0x0100
2020-05-05 17:34:49 driver-btm-api.c:686:dump_pcb_bom_version: Chain [0] BOM Version: 0x0100
2020-05-05 17:34:49 driver-btm-api.c:685:dump_pcb_bom_version: Chain [1] PCB Version: 0x0100
2020-05-05 17:34:49 driver-btm-api.c:686:dump_pcb_bom_version: Chain [1] BOM Version: 0x0100
2020-05-05 17:34:49 driver-btm-api.c:685:dump_pcb_bom_version: Chain [2] PCB Version: 0x0100
2020-05-05 17:34:49 driver-btm-api.c:686:dump_pcb_bom_version: Chain [2] BOM Version: 0x0100
2020-05-05 17:34:50 driver-btm-api.c:1897:bitmain_board_init: Fan check passed.
2020-05-05 17:34:50 register.c:283:get_register: !!! reg crc error
2020-05-05 17:34:52 board.c:36:jump_and_app_check_restore_pic: chain[0] PIC jump to app
2020-05-05 17:34:58 board.c:40:jump_and_app_check_restore_pic: Check chain[0] PIC fw version=0xb9
2020-05-05 17:35:02 board.c:36:jump_and_app_check_restore_pic: chain[1] PIC jump to app
2020-05-05 17:35:06 board.c:40:jump_and_app_check_restore_pic: Check chain[1] PIC fw version=0xb9
2020-05-05 17:35:08 board.c:36:jump_and_app_check_restore_pic: chain[2] PIC jump to app
2020-05-05 17:35:12 board.c:40:jump_and_app_check_restore_pic: Check chain[2] PIC fw version=0xb9
2020-05-05 17:35:12 power_api.c:55:power_init: power init ...
2020-05-05 17:35:12 driver-btm-api.c:1907:bitmain_board_init: Enter 30s sleep to make sure power release finish.
2020-05-05 17:35:44 power_api.c:232:set_iic_power_to_highest_voltage: setting to voltage: 17.00 ...
2020-05-05 17:35:45 power_api.c:124:check_voltage_multi: retry time: 0
2020-05-05 17:35:47 power_api.c:86:get_average_voltage: chain[0], voltage is: 17.199638
2020-05-05 17:35:50 power_api.c:86:get_average_voltage: chain[1], voltage is: 17.132285
2020-05-05 17:35:53 power_api.c:86:get_average_voltage: chain[2], voltage is: 17.224131
2020-05-05 17:35:53 power_api.c:97:get_average_voltage: aveage voltage is: 17.185351
2020-05-05 17:35:53 power_api.c:182:set_iic_power_by_voltage: now set voltage to : 17.000000
2020-05-05 17:35:53 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[0]: chip baud = 115200, chip_divider = 26
2020-05-05 17:35:53 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[1]: chip baud = 115200, chip_divider = 26
2020-05-05 17:35:53 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[2]: chip baud = 115200, chip_divider = 26
2020-05-05 17:35:53 uart.c:80:set_baud: set fpga_baud = 115200, fpga_divider = 26
2020-05-05 17:36:03 driver-btm-api.c:1010:check_asic_number_with_power_on: Chain[0]: find 29 asic, times 0
2020-05-05 17:36:13 driver-btm-api.c:1010:check_asic_number_with_power_on: Chain[0]: find 30 asic, times 1
2020-05-05 17:36:23 driver-btm-api.c:1010:check_asic_number_with_power_on: Chain[1]: find 30 asic, times 0
2020-05-05 17:36:34 driver-btm-api.c:1010:check_asic_number_with_power_on: Chain[2]: find 30 asic, times 0
2020-05-05 17:36:37 driver-btm-api.c:348:set_order_clock: chain[0]: set order clock, stragegy 3 clock_en=0x1
2020-05-05 17:36:37 driver-btm-api.c:348:set_order_clock: chain[1]: set order clock, stragegy 3 clock_en=0x1
2020-05-05 17:36:37 driver-btm-api.c:348:set_order_clock: chain[2]: set order clock, stragegy 3 clock_en=0x1
2020-05-05 17:36:38 driver-hash-chip.c:490:set_clock_delay_control: core_data = 0xb4
2020-05-05 17:36:38 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[0]: chip baud = 3000000, chip_divider = 0
2020-05-05 17:36:38 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[1]: chip baud = 3000000, chip_divider = 0
2020-05-05 17:36:38 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[2]: chip baud = 3000000, chip_divider = 0
2020-05-05 17:36:38 uart.c:80:set_baud: set fpga_baud = 3000000, fpga_divider = 0
2020-05-05 17:36:38 driver-btm-api.c:1660:check_clock_counter: freq 50 clock_counter_limit 6
2020-05-05 17:36:38 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[0]: chip baud = 115200, chip_divider = 26
2020-05-05 17:36:38 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[1]: chip baud = 115200, chip_divider = 26
2020-05-05 17:36:38 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[2]: chip baud = 115200, chip_divider = 26
2020-05-05 17:36:38 uart.c:80:set_baud: set fpga_baud = 115200, fpga_divider = 26
2020-05-05 17:36:38 voltage[0] = 1710
2020-05-05 17:36:38 voltage[1] = 1710
2020-05-05 17:36:38 voltage[2] = 1710
2020-05-05 17:36:38 power_api.c:140:set_working_voltage: working_voltage = 17.100000
2020-05-05 17:36:40 temperature.c:282:calibrate_temp_sensor_one_chain: Temperature sensor calibration: chain 0 success.
2020-05-05 17:36:41 temperature.c:282:calibrate_temp_sensor_one_chain: Temperature sensor calibration: chain 1 success.
2020-05-05 17:36:43 temperature.c:282:calibrate_temp_sensor_one_chain: Temperature sensor calibration: chain 2 success.
2020-05-05 17:36:43 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[0]: chip baud = 6000000, chip_divider = 7
2020-05-05 17:36:43 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[1]: chip baud = 6000000, chip_divider = 7
2020-05-05 17:36:43 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[2]: chip baud = 6000000, chip_divider = 7
2020-05-05 17:36:43 uart.c:80:set_baud: set fpga_baud = 6000000, fpga_divider = 3
2020-05-05 17:36:44 driver-btm-api.c:248:check_bringup_temp: Bring up temperature is 13
2020-05-05 17:36:44 driver-btm-api.c:581:calculate_timeout: dev->timeout = 392
2020-05-05 17:36:44 power_api.c:379:slowly_set_iic_power_to_custom_voltage: slowly setting to voltage: 18.00 ...
2020-05-05 17:37:17 power_api.c:124:check_voltage_multi: retry time: 0
2020-05-05 17:37:18 power_api.c:86:get_average_voltage: chain[0], voltage is: 18.136465
2020-05-05 17:37:20 power_api.c:86:get_average_voltage: chain[1], voltage is: 18.142588
2020-05-05 17:37:22 power_api.c:86:get_average_voltage: chain[2], voltage is: 18.265049
2020-05-05 17:37:22 power_api.c:97:get_average_voltage: aveage voltage is: 18.181367
2020-05-05 17:37:22 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 42 set refdiv: 2, fbdiv: 168, postdiv1: 7, postdiv2: 7, usr divider: 1
2020-05-05 17:37:22 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 50 set refdiv: 2, fbdiv: 168, postdiv1: 7, postdiv2: 6, usr divider: 1
2020-05-05 17:37:22 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 60 set refdiv: 2, fbdiv: 168, postdiv1: 7, postdiv2: 5, usr divider: 1
2020-05-05 17:37:22 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 75 set refdiv: 2, fbdiv: 168, postdiv1: 7, postdiv2: 4, usr divider: 1
2020-05-05 17:37:22 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 100 set refdiv: 2, fbdiv: 168, postdiv1: 7, postdiv2: 3, usr divider: 1
2020-05-05 17:37:23 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 150 set refdiv: 2, fbdiv: 168, postdiv1: 7, postdiv2: 2, usr divider: 1
2020-05-05 17:37:23 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 300 set refdiv: 2, fbdiv: 168, postdiv1: 7, postdiv2: 1, usr divider: 1
2020-05-05 17:37:23 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 350 set refdiv: 2, fbdiv: 168, postdiv1: 6, postdiv2: 1, usr divider: 1
2020-05-05 17:37:23 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 420 set refdiv: 2, fbdiv: 168, postdiv1: 5, postdiv2: 1, usr divider: 1
2020-05-05 17:37:23 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 525 set refdiv: 2, fbdiv: 168, postdiv1: 4, postdiv2: 1, usr divider: 1
2020-05-05 17:37:23 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 700 set refdiv: 2, fbdiv: 168, postdiv1: 3, postdiv2: 1, usr divider: 1
2020-05-05 17:37:23 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 41 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 7, usr divider: 1
2020-05-05 17:37:23 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 47 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 6, usr divider: 1
2020-05-05 17:37:23 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 57 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 5, usr divider: 1
2020-05-05 17:37:23 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 71 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 4, usr divider: 1
2020-05-05 17:37:24 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 95 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 3, usr divider: 1
2020-05-05 17:37:24 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 143 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 2, usr divider: 1
2020-05-05 17:37:24 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 287 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 1, usr divider: 1
2020-05-05 17:37:24 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 335 set refdiv: 2, fbdiv: 161, postdiv1: 6, postdiv2: 1, usr divider: 1
2020-05-05 17:37:24 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 402 set refdiv: 2, fbdiv: 161, postdiv1: 5, postdiv2: 1, usr divider: 1
2020-05-05 17:37:24 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 503 set refdiv: 2, fbdiv: 161, postdiv1: 4, postdiv2: 1, usr divider: 1
2020-05-05 17:37:24 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 670 set refdiv: 2, fbdiv: 161, postdiv1: 3, postdiv2: 1, usr divider: 1
2020-05-05 17:37:24 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 41 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 7, usr divider: 1
2020-05-05 17:37:24 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 47 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 6, usr divider: 1
2020-05-05 17:37:25 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 57 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 5, usr divider: 1
2020-05-05 17:37:25 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 71 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 4, usr divider: 1
2020-05-05 17:37:25 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 95 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 3, usr divider: 1
2020-05-05 17:37:25 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 143 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 2, usr divider: 1
2020-05-05 17:37:25 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 287 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 1, usr divider: 1
2020-05-05 17:37:25 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 335 set refdiv: 2, fbdiv: 161, postdiv1: 6, postdiv2: 1, usr divider: 1
2020-05-05 17:37:25 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 402 set refdiv: 2, fbdiv: 161, postdiv1: 5, postdiv2: 1, usr divider: 1
2020-05-05 17:37:25 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 503 set refdiv: 2, fbdiv: 161, postdiv1: 4, postdiv2: 1, usr divider: 1
2020-05-05 17:37:25 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 670 set refdiv: 2, fbdiv: 161, postdiv1: 3, postdiv2: 1, usr divider: 1
2020-05-05 17:37:25 driver-btm-api.c:612:set_timeout: freq 700 final timeout=168
2020-05-05 17:37:25 power_api.c:146:set_higher_voltage: higher_voltage = 18.000000
2020-05-05 17:37:25 power_api.c:428:slowly_set_iic_power_to_higher_voltage: slowly setting to voltage: 18.00 ...
2020-05-05 17:37:50 power_api.c:124:check_voltage_multi: retry time: 0
2020-05-05 17:37:52 power_api.c:86:get_average_voltage: chain[0], voltage is: 18.118095
2020-05-05 17:37:53 power_api.c:86:get_average_voltage: chain[1], voltage is: 18.105849
2020-05-05 17:37:55 power_api.c:86:get_average_voltage: chain[2], voltage is: 18.209941
2020-05-05 17:37:55 power_api.c:97:get_average_voltage: aveage voltage is: 18.144629
2020-05-05 17:37:56 driver-btm-api.c:2186:bitmain_reopen_core: reopen_core done!
2020-05-05 17:37:56 power_api.c:379:slowly_set_iic_power_to_custom_voltage: slowly setting to voltage: 17.20 ...
2020-05-05 17:38:36 power_api.c:124:check_voltage_multi: retry time: 0
2020-05-05 17:38:38 power_api.c:86:get_average_voltage: chain[0], voltage is: 17.273115
2020-05-05 17:38:39 power_api.c:86:get_average_voltage: chain[1], voltage is: 17.273115
2020-05-05 17:38:41 power_api.c:86:get_average_voltage: chain[2], voltage is: 17.377207
2020-05-05 17:38:41 power_api.c:97:get_average_voltage: aveage voltage is: 17.307812
2020-05-05 17:38:41 power_api.c:140:set_working_voltage: working_voltage = 17.200001
2020-05-05 17:43:40 thread.c:422:is_zero_nonce_happened: chain_nonce[0] = 205011
2020-05-05 17:43:40 thread.c:422:is_zero_nonce_happened: chain_nonce[1] = 196561
2020-05-05 17:43:40 thread.c:422:is_zero_nonce_happened: chain_nonce[2] = 166908
2020-05-05 18:08:41 thread.c:204:calc_hashrate_avg: avg rate is 39006.47 in 30 mins
2020-05-05 18:08:41 temperature.c:450:temp_statistics_show: pcb temp 29~37 chip temp 49~59
2020-05-05 18:08:41 thread.c:285:check_hashrate: latest avg rate < 0.98......
2020-05-05 18:08:41 thread.c:286:check_hashrate: current PCB min temperature 29
2020-05-05 18:08:41 thread.c:287:check_hashrate: current voltage is 17.20V, working voltage is 17.20V
2020-05-05 18:08:41 thread.c:312:check_hashrate: high temp, voltage has already increased 0.1V/0.2V
Miner Status Screen: https://drive.google.com/file/d/1fOkuB62Unp805chOktNVzAgIws75QC3o/view?usp=sharing Still shows: 2020-05-05 18:08:41 thread.c:312:check_hashrate: high temp, voltage has already increased 0.1V/0.2VJacob
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: mikeywith on May 05, 2020, 09:15:17 PM
Thats funny that you mention it. That is the conclusion that I'm coming.
After having read the kernel log again, I am almost sure it's a PSU issue, and thus increasing the fan speed won't really fix it, you could try to clean the PSU but I suggest replacing it with a working one just to see if it works, don't jump into conclusions and waste money buying a new PSU until it's confirmed. As for where can you buy those PSUs in Canada, I can't help you with that sadly, I live a few thousand miles away ;D, but IIRC Steamtyme (https://bitcointalk.org/index.php?action=profile;u=1112531) is in Canada and he has been involved in mining for long, maybe he knows of good sources there.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: mysticbitcoin on May 05, 2020, 09:32:54 PM
Mikeywith, Update. Just when thing were pointing to a PSU likely issue. I got this that just happened. Still away from the farm, so didn't do the PSU switch yet. Kernel Log: Booting Linux on physical CPU 0x0
Linux version 4.6.0-xilinx-gff8137b-dirty (lzq@armdev2) (gcc version 4.8.3 20140320 (prerelease) (Sourcery CodeBench Lite 2014.05-23) ) #25 SMP PREEMPT Fri Nov 23 15:30:52 CST 2018
CPU: ARMv7 Processor [413fc090] revision 0 (ARMv7), cr=18c5387d
CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
Machine model: Xilinx Zynq
cma: Reserved 16 MiB at 0x0e000000
Memory policy: Data cache writealloc
On node 0 totalpages: 61440
free_area_init_node: node 0, pgdat c0b39280, node_mem_map cde10000
Normal zone: 480 pages used for memmap
Normal zone: 0 pages reserved
Normal zone: 61440 pages, LIFO batch:15
percpu: Embedded 12 pages/cpu @cddf1000 s19776 r8192 d21184 u49152
pcpu-alloc: s19776 r8192 d21184 u49152 alloc=12*4096
pcpu-alloc: [0] 0 [0] 1
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 60960
Kernel command line: mem=240M console=ttyPS0,115200 ramdisk_size=33554432 root=/dev/ram rw earlyprintk
PID hash table entries: 1024 (order: 0, 4096 bytes)
Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
Memory: 203756K/245760K available (6345K kernel code, 231K rwdata, 1896K rodata, 1024K init, 223K bss, 25620K reserved, 16384K cma-reserved, 0K highmem)
Virtual kernel memory layout:
vector : 0xffff0000 - 0xffff1000 ( 4 kB)
fixmap : 0xffc00000 - 0xfff00000 (3072 kB)
vmalloc : 0xcf800000 - 0xff800000 ( 768 MB)
lowmem : 0xc0000000 - 0xcf000000 ( 240 MB)
pkmap : 0xbfe00000 - 0xc0000000 ( 2 MB)
modules : 0xbf000000 - 0xbfe00000 ( 14 MB)
.text : 0xc0008000 - 0xc090c424 (9234 kB)
.init : 0xc0a00000 - 0xc0b00000 (1024 kB)
.data : 0xc0b00000 - 0xc0b39fe0 ( 232 kB)
.bss : 0xc0b39fe0 - 0xc0b71c28 ( 224 kB)
Preemptible hierarchical RCU implementation.
Build-time adjustment of leaf fanout to 32.
RCU restricting CPUs from NR_CPUS=4 to nr_cpu_ids=2.
RCU: Adjusting geometry for rcu_fanout_leaf=32, nr_cpu_ids=2
NR_IRQS:16 nr_irqs:16 16
efuse mapped to cf800000
ps7-slcr mapped to cf802000
L2C: platform modifies aux control register: 0x72360000 -> 0x72760000
L2C: DT/platform modifies aux control register: 0x72360000 -> 0x72760000
L2C-310 erratum 769419 enabled
L2C-310 enabling early BRESP for Cortex-A9
L2C-310 full line of zeros enabled for Cortex-A9
L2C-310 ID prefetch enabled, offset 1 lines
L2C-310 dynamic clock gating enabled, standby mode enabled
L2C-310 cache controller enabled, 8 ways, 512 kB
L2C-310: CACHE_ID 0x410000c8, AUX_CTRL 0x76760001
zynq_clock_init: clkc starts at cf802100
Zynq clock init
sched_clock: 64 bits at 333MHz, resolution 3ns, wraps every 4398046511103ns
clocksource: arm_global_timer: mask: 0xffffffffffffffff max_cycles: 0x4ce07af025, max_idle_ns: 440795209040 ns
Switching to timer-based delay loop, resolution 3ns
clocksource: ttc_clocksource: mask: 0xffff max_cycles: 0xffff, max_idle_ns: 537538477 ns
ps7-ttc #0 at cf80a000, irq=18
Console: colour dummy device 80x30
Calibrating delay loop (skipped), value calculated using timer frequency.. 666.66 BogoMIPS (lpj=3333333)
pid_max: default: 32768 minimum: 301
Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
CPU: Testing write buffer coherency: ok
CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
Setting up static identity map for 0x100000 - 0x100058
CPU1: failed to boot: -1
Brought up 1 CPUs
SMP: Total of 1 processors activated (666.66 BogoMIPS).
CPU: All CPU(s) started in SVC mode.
devtmpfs: initialized
VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4
clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
pinctrl core: initialized pinctrl subsystem
NET: Registered protocol family 16
DMA: preallocated 256 KiB pool for atomic coherent allocations
cpuidle: using governor menu
hw-breakpoint: found 5 (+1 reserved) breakpoint and 1 watchpoint registers.
hw-breakpoint: maximum watchpoint size is 4 bytes.
zynq-ocm f800c000.ps7-ocmc: ZYNQ OCM pool: 256 KiB @ 0xcf880000
vgaarb: loaded
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
media: Linux media interface: v0.10
Linux video capture interface: v2.00
pps_core: LinuxPPS API ver. 1 registered
pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
PTP clock support registered
EDAC MC: Ver: 3.0.0
Advanced Linux Sound Architecture Driver Initialized.
clocksource: Switched to clocksource arm_global_timer
NET: Registered protocol family 2
TCP established hash table entries: 2048 (order: 1, 8192 bytes)
TCP bind hash table entries: 2048 (order: 2, 16384 bytes)
TCP: Hash tables configured (established 2048 bind 2048)
UDP hash table entries: 256 (order: 1, 8192 bytes)
UDP-Lite hash table entries: 256 (order: 1, 8192 bytes)
NET: Registered protocol family 1
RPC: Registered named UNIX socket transport module.
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
PCI: CLS 0 bytes, default 64
Trying to unpack rootfs image as initramfs...
rootfs image is not initramfs (no cpio magic); looks like an initrd
Freeing initrd memory: 12580K (cceb8000 - cdb01000)
hw perfevents: enabled with armv7_cortex_a9 PMU driver, 7 counters available
futex hash table entries: 512 (order: 3, 32768 bytes)
workingset: timestamp_bits=28 max_order=16 bucket_order=0
jffs2: version 2.2. (NAND) (SUMMARY) © 2001-2006 Red Hat, Inc.
io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered (default)
dma-pl330 f8003000.ps7-dma: Loaded driver for PL330 DMAC-241330
dma-pl330 f8003000.ps7-dma: DBUFF-128x8bytes Num_Chans-8 Num_Peri-4 Num_Events-16
e0000000.serial: ttyPS0 at MMIO 0xe0000000 (irq = 158, base_baud = 6249999) is a xuartps
console [ttyPS0] enabled
xdevcfg f8007000.ps7-dev-cfg: ioremap 0xf8007000 to cf86e000
[drm] Initialized drm 1.1.0 20060810
brd: module loaded
loop: module loaded
CAN device driver interface
gpiod_set_value: invalid GPIO
libphy: MACB_mii_bus: probed
macb e000b000.ethernet eth0: Cadence GEM rev 0x00020118 at 0xe000b000 irq 31 (00:0a:35:00:00:00)
Generic PHY e000b000.etherne:00: attached PHY driver [Generic PHY] (mii_bus:phy_addr=e000b000.etherne:00, irq=-1)
e1000e: Intel(R) PRO/1000 Network Driver - 3.2.6-k
e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
ehci-pci: EHCI PCI platform driver
usbcore: registered new interface driver usb-storage
mousedev: PS/2 mouse device common for all mice
i2c /dev entries driver
Xilinx Zynq CpuIdle Driver started
sdhci: Secure Digital Host Controller Interface driver
sdhci: Copyright(c) Pierre Ossman
sdhci-pltfm: SDHCI platform and OF driver helper
mmc0: SDHCI controller on e0100000.ps7-sdio [e0100000.ps7-sdio] using ADMA
ledtrig-cpu: registered to indicate activity on CPUs
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
nand: device found, Manufacturer ID: 0x2c, Chip ID: 0xda
nand: Micron MT29F2G08ABAGAWP
nand: 256 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 128
nand: WARNING: pl35x-nand: the ECC used on your system is too weak compared to the one required by the NAND chip
Bad block table found at page 131008, version 0x01
Bad block table found at page 130944, version 0x01
6 ofpart partitions found on MTD device pl35x-nand
Creating 6 MTD partitions on "pl35x-nand":
0x000000000000-0x000002800000 : "BOOT.bin-env-dts-kernel"
0x000002800000-0x000004800000 : "ramfs"
0x000004800000-0x000005000000 : "configs"
0x000005000000-0x000006000000 : "reserve"
0x000006000000-0x000008000000 : "ramfs-bak"
0x000008000000-0x000010000000 : "reserve1"
NET: Registered protocol family 10
sit: IPv6 over IPv4 tunneling driver
NET: Registered protocol family 17
can: controller area network core (rev 20120528 abi 9)
NET: Registered protocol family 29
can: raw protocol (rev 20120528)
can: broadcast manager protocol (rev 20120528 t)
can: netlink gateway (rev 20130117) max_hops=1
zynq_pm_ioremap: no compatible node found for 'xlnx,zynq-ddrc-a05'
zynq_pm_late_init: Unable to map DDRC IO memory.
Registering SWP/SWPB emulation handler
hctosys: unable to open rtc device (rtc0)
ALSA device list:
No soundcards found.
RAMDISK: gzip image found at block 0
EXT4-fs (ram0): couldn't mount as ext3 due to feature incompatibilities
EXT4-fs (ram0): mounted filesystem without journal. Opts: (null)
VFS: Mounted root (ext4 filesystem) on device 1:0.
devtmpfs: mounted
Freeing unused kernel memory: 1024K (c0a00000 - c0b00000)
EXT4-fs (ram0): re-mounted. Opts: block_validity,delalloc,barrier,user_xattr
random: dd urandom read with 0 bits of entropy available
ubi0: attaching mtd2
ubi0: scanning is finished
ubi0: attached mtd2 (name "configs", size 8 MiB)
ubi0: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
ubi0: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
ubi0: VID header offset: 2048 (aligned 2048), data offset: 4096
ubi0: good PEBs: 64, bad PEBs: 0, corrupted PEBs: 0
ubi0: user volume: 1, internal volumes: 1, max. volumes count: 128
ubi0: max/mean erase counter: 6/2, WL threshold: 4096, image sequence number: 4244297529
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 01559AD8-7B6A-42E6-A3FE-EDF3659527A9, 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: 1052/340, WL threshold: 4096, image sequence number: 4185749592
ubi1: available PEBs: 0, total reserved PEBs: 1020, PEBs reserved for bad PEB handling: 36
ubi1: background thread "ubi_bgt1d" started, PID 720
UBIFS (ubi1:0): background thread "ubifs_bgt1_0" started, PID 723
UBIFS (ubi1:0): recovery needed
UBIFS (ubi1:0): recovery completed
UBIFS (ubi1:0): UBIFS: mounted UBI device 1, volume 0, name "reserve1"
UBIFS (ubi1:0): LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
UBIFS (ubi1:0): FS size: 123039744 bytes (117 MiB, 969 LEBs), journal size 6221824 bytes (5 MiB, 49 LEBs)
UBIFS (ubi1:0): reserved for root: 4952683 bytes (4836 KiB)
UBIFS (ubi1:0): media format: w4/r0 (latest is w4/r0), UUID 4829CF2C-7435-4146-B2FD-0826AAE8443A, small LPT model
IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
macb e000b000.ethernet eth0: unable to generate target frequency: 25000000 Hz
macb e000b000.ethernet eth0: link up (100/Full)
IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
In axi fpga driver!
request_mem_region OK!
AXI fpga dev virtual address is 0xcfb38000
*base_vir_addr = 0xab013
In fpga mem driver!
request_mem_region OK!
fpga mem virtual address is 0xd2000000
random: nonblocking pool is initialized
2020-05-05 18:52:38 driver-btm-api.c:631:init_freq_mode: This is scan-user version
2020-05-05 18:52:38 driver-btm-api.c:1994:bitmain_soc_init: opt_multi_version = 1
2020-05-05 18:52:38 driver-btm-api.c:1995:bitmain_soc_init: opt_bitmain_ab = 1
2020-05-05 18:52:38 driver-btm-api.c:1996:bitmain_soc_init: opt_bitmain_work_mode = 0
2020-05-05 18:52:38 driver-btm-api.c:1997:bitmain_soc_init: Miner compile time: Tue Dec 24 16:13:07 CST 2019 type: Antminer T17
2020-05-05 18:52:38 driver-btm-api.c:1998:bitmain_soc_init: commit version: e93a09b 2019-12-24 16:03:45, build by: lol 2019-12-24 16:19:49
2020-05-05 18:52:38 driver-btm-api.c:1810:show_sn: no SN got, please write SN to /nvdata/sn
2020-05-05 18:52:38 driver-btm-api.c:1135:miner_device_init: Detect 256MB control board of XILINX
2020-05-05 18:52:38 driver-btm-api.c:1083:init_fan_parameter: fan_eft : 0 fan_pwm : 0
2020-05-05 18:52:38 thread.c:789:create_read_nonce_reg_thread: create thread
2020-05-05 18:52:44 driver-btm-api.c:1067:init_miner_version: miner ID : 8042750618c0885c
2020-05-05 18:52:44 driver-btm-api.c:1073:init_miner_version: FPGA Version = 0xB013
2020-05-05 18:52:46 eeprom.c:425:check_pattern_test_level: invalid pattern test result. ignore
2020-05-05 18:52:47 eeprom.c:425:check_pattern_test_level: invalid pattern test result. ignore
2020-05-05 18:52:49 eeprom.c:425:check_pattern_test_level: invalid pattern test result. ignore
2020-05-05 18:52:49 driver-btm-api.c:705:get_product_id: product_id[0] = 1
2020-05-05 18:52:49 driver-btm-api.c:705:get_product_id: product_id[1] = 1
2020-05-05 18:52:49 driver-btm-api.c:705:get_product_id: product_id[2] = 1
2020-05-05 18:52:49 driver-btm-api.c:1633:get_ccdly_opt: ccdly_opt[0] = 1
2020-05-05 18:52:49 driver-btm-api.c:1633:get_ccdly_opt: ccdly_opt[1] = 1
2020-05-05 18:52:49 driver-btm-api.c:1633:get_ccdly_opt: ccdly_opt[2] = 1
2020-05-05 18:52:49 driver-btm-api.c:1877:bitmain_board_init: g_ccdly_opt = 1
2020-05-05 18:52:49 driver-btm-api.c:644:_set_project_type: project:2
2020-05-05 18:52:49 driver-btm-api.c:674:_set_project_type: Project type: Antminer T17
2020-05-05 18:52:49 driver-btm-api.c:685:dump_pcb_bom_version: Chain [0] PCB Version: 0x0100
2020-05-05 18:52:49 driver-btm-api.c:686:dump_pcb_bom_version: Chain [0] BOM Version: 0x0100
2020-05-05 18:52:49 driver-btm-api.c:685:dump_pcb_bom_version: Chain [1] PCB Version: 0x0100
2020-05-05 18:52:49 driver-btm-api.c:686:dump_pcb_bom_version: Chain [1] BOM Version: 0x0100
2020-05-05 18:52:49 driver-btm-api.c:685:dump_pcb_bom_version: Chain [2] PCB Version: 0x0100
2020-05-05 18:52:49 driver-btm-api.c:686:dump_pcb_bom_version: Chain [2] BOM Version: 0x0100
2020-05-05 18:52:50 driver-btm-api.c:1897:bitmain_board_init: Fan check passed.
2020-05-05 18:52:50 register.c:283:get_register: !!! reg crc error
2020-05-05 18:52:50 register.c:283:get_register: !!! reg crc error
2020-05-05 18:52:52 board.c:36:jump_and_app_check_restore_pic: chain[0] PIC jump to app
2020-05-05 18:52:55 board.c:40:jump_and_app_check_restore_pic: Check chain[0] PIC fw version=0xb9
2020-05-05 18:52:57 board.c:36:jump_and_app_check_restore_pic: chain[1] PIC jump to app
2020-05-05 18:53:01 board.c:40:jump_and_app_check_restore_pic: Check chain[1] PIC fw version=0xb9
2020-05-05 18:53:02 board.c:36:jump_and_app_check_restore_pic: chain[2] PIC jump to app
2020-05-05 18:53:06 board.c:40:jump_and_app_check_restore_pic: Check chain[2] PIC fw version=0xb9
2020-05-05 18:53:06 thread.c:784:create_pic_heart_beat_thread: create thread
2020-05-05 18:53:06 power_api.c:55:power_init: power init ...
2020-05-05 18:53:06 driver-btm-api.c:1907:bitmain_board_init: Enter 30s sleep to make sure power release finish.
2020-05-05 18:53:38 power_api.c:232:set_iic_power_to_highest_voltage: setting to voltage: 17.00 ...
2020-05-05 18:53:44 power_api.c:124:check_voltage_multi: retry time: 0
2020-05-05 18:53:45 power_api.c:86:get_average_voltage: chain[0], voltage is: 17.138408
2020-05-05 18:53:47 power_api.c:86:get_average_voltage: chain[1], voltage is: 17.120039
2020-05-05 18:53:49 power_api.c:86:get_average_voltage: chain[2], voltage is: 17.230254
2020-05-05 18:53:49 power_api.c:97:get_average_voltage: aveage voltage is: 17.162900
2020-05-05 18:53:49 power_api.c:182:set_iic_power_by_voltage: now set voltage to : 17.000000
2020-05-05 18:53:49 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[0]: chip baud = 115200, chip_divider = 26
2020-05-05 18:53:49 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[1]: chip baud = 115200, chip_divider = 26
2020-05-05 18:53:49 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[2]: chip baud = 115200, chip_divider = 26
2020-05-05 18:53:49 uart.c:80:set_baud: set fpga_baud = 115200, fpga_divider = 26
2020-05-05 18:54:00 driver-btm-api.c:1010:check_asic_number_with_power_on: Chain[0]: find 30 asic, times 0
2020-05-05 18:54:10 driver-btm-api.c:1010:check_asic_number_with_power_on: Chain[1]: find 30 asic, times 0
2020-05-05 18:54:21 driver-btm-api.c:1010:check_asic_number_with_power_on: Chain[2]: find 30 asic, times 0
2020-05-05 18:54:24 driver-btm-api.c:348:set_order_clock: chain[0]: set order clock, stragegy 3 clock_en=0x1
2020-05-05 18:54:24 driver-btm-api.c:348:set_order_clock: chain[1]: set order clock, stragegy 3 clock_en=0x1
2020-05-05 18:54:24 driver-btm-api.c:348:set_order_clock: chain[2]: set order clock, stragegy 3 clock_en=0x1
2020-05-05 18:54:25 driver-hash-chip.c:490:set_clock_delay_control: core_data = 0xb4
2020-05-05 18:54:25 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[0]: chip baud = 3000000, chip_divider = 0
2020-05-05 18:54:25 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[1]: chip baud = 3000000, chip_divider = 0
2020-05-05 18:54:25 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[2]: chip baud = 3000000, chip_divider = 0
2020-05-05 18:54:25 uart.c:80:set_baud: set fpga_baud = 3000000, fpga_divider = 0
2020-05-05 18:54:25 driver-btm-api.c:1660:check_clock_counter: freq 50 clock_counter_limit 6
2020-05-05 18:54:25 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[0]: chip baud = 115200, chip_divider = 26
2020-05-05 18:54:25 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[1]: chip baud = 115200, chip_divider = 26
2020-05-05 18:54:25 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[2]: chip baud = 115200, chip_divider = 26
2020-05-05 18:54:25 uart.c:80:set_baud: set fpga_baud = 115200, fpga_divider = 26
2020-05-05 18:54:25 voltage[0] = 1710
2020-05-05 18:54:25 voltage[1] = 1710
2020-05-05 18:54:25 voltage[2] = 1710
2020-05-05 18:54:25 power_api.c:140:set_working_voltage: working_voltage = 17.100000
2020-05-05 18:54:27 temperature.c:282:calibrate_temp_sensor_one_chain: Temperature sensor calibration: chain 0 success.
2020-05-05 18:54:28 temperature.c:282:calibrate_temp_sensor_one_chain: Temperature sensor calibration: chain 1 success.
2020-05-05 18:54:29 temperature.c:282:calibrate_temp_sensor_one_chain: Temperature sensor calibration: chain 2 success.
2020-05-05 18:54:29 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[0]: chip baud = 6000000, chip_divider = 7
2020-05-05 18:54:29 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[1]: chip baud = 6000000, chip_divider = 7
2020-05-05 18:54:29 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[2]: chip baud = 6000000, chip_divider = 7
2020-05-05 18:54:29 uart.c:80:set_baud: set fpga_baud = 6000000, fpga_divider = 3
2020-05-05 18:54:31 driver-btm-api.c:248:check_bringup_temp: Bring up temperature is 15
2020-05-05 18:54:31 thread.c:804:create_check_miner_status_thread: create thread
2020-05-05 18:54:31 thread.c:794:create_set_miner_status_thread: create thread
2020-05-05 18:54:31 driver-btm-api.c:581:calculate_timeout: dev->timeout = 392
2020-05-05 18:54:31 thread.c:779:create_temperature_monitor_thread: create thread
2020-05-05 18:54:31 freq_tuning.c:154:freq_tuning_get_max_freq: Max freq of tuning is 760
2020-05-05 18:54:31 power_api.c:379:slowly_set_iic_power_to_custom_voltage: slowly setting to voltage: 18.00 ...
2020-05-05 18:55:04 power_api.c:124:check_voltage_multi: retry time: 0
2020-05-05 18:55:05 power_api.c:86:get_average_voltage: chain[0], voltage is: 18.130342
2020-05-05 18:55:07 power_api.c:86:get_average_voltage: chain[1], voltage is: 18.118095
2020-05-05 18:55:09 power_api.c:86:get_average_voltage: chain[2], voltage is: 18.228310
2020-05-05 18:55:09 power_api.c:97:get_average_voltage: aveage voltage is: 18.158916
2020-05-05 18:55:09 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 42 set refdiv: 2, fbdiv: 168, postdiv1: 7, postdiv2: 7, usr divider: 1
2020-05-05 18:55:09 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 50 set refdiv: 2, fbdiv: 168, postdiv1: 7, postdiv2: 6, usr divider: 1
2020-05-05 18:55:09 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 60 set refdiv: 2, fbdiv: 168, postdiv1: 7, postdiv2: 5, usr divider: 1
2020-05-05 18:55:09 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 75 set refdiv: 2, fbdiv: 168, postdiv1: 7, postdiv2: 4, usr divider: 1
2020-05-05 18:55:09 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 100 set refdiv: 2, fbdiv: 168, postdiv1: 7, postdiv2: 3, usr divider: 1
2020-05-05 18:55:09 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 150 set refdiv: 2, fbdiv: 168, postdiv1: 7, postdiv2: 2, usr divider: 1
2020-05-05 18:55:10 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 300 set refdiv: 2, fbdiv: 168, postdiv1: 7, postdiv2: 1, usr divider: 1
2020-05-05 18:55:10 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 350 set refdiv: 2, fbdiv: 168, postdiv1: 6, postdiv2: 1, usr divider: 1
2020-05-05 18:55:10 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 420 set refdiv: 2, fbdiv: 168, postdiv1: 5, postdiv2: 1, usr divider: 1
2020-05-05 18:55:10 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 525 set refdiv: 2, fbdiv: 168, postdiv1: 4, postdiv2: 1, usr divider: 1
2020-05-05 18:55:10 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 700 set refdiv: 2, fbdiv: 168, postdiv1: 3, postdiv2: 1, usr divider: 1
2020-05-05 18:55:10 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 41 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 7, usr divider: 1
2020-05-05 18:55:10 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 47 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 6, usr divider: 1
2020-05-05 18:55:10 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 57 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 5, usr divider: 1
2020-05-05 18:55:10 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 71 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 4, usr divider: 1
2020-05-05 18:55:10 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 95 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 3, usr divider: 1
2020-05-05 18:55:11 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 143 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 2, usr divider: 1
2020-05-05 18:55:11 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 287 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 1, usr divider: 1
2020-05-05 18:55:11 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 335 set refdiv: 2, fbdiv: 161, postdiv1: 6, postdiv2: 1, usr divider: 1
2020-05-05 18:55:11 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 402 set refdiv: 2, fbdiv: 161, postdiv1: 5, postdiv2: 1, usr divider: 1
2020-05-05 18:55:11 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 503 set refdiv: 2, fbdiv: 161, postdiv1: 4, postdiv2: 1, usr divider: 1
2020-05-05 18:55:11 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 670 set refdiv: 2, fbdiv: 161, postdiv1: 3, postdiv2: 1, usr divider: 1
2020-05-05 18:55:11 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 41 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 7, usr divider: 1
2020-05-05 18:55:11 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 47 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 6, usr divider: 1
2020-05-05 18:55:11 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 57 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 5, usr divider: 1
2020-05-05 18:55:12 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 71 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 4, usr divider: 1
2020-05-05 18:55:12 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 95 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 3, usr divider: 1
2020-05-05 18:55:12 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 143 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 2, usr divider: 1
2020-05-05 18:55:12 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 287 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 1, usr divider: 1
2020-05-05 18:55:12 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 335 set refdiv: 2, fbdiv: 161, postdiv1: 6, postdiv2: 1, usr divider: 1
2020-05-05 18:55:12 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 402 set refdiv: 2, fbdiv: 161, postdiv1: 5, postdiv2: 1, usr divider: 1
2020-05-05 18:55:12 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 503 set refdiv: 2, fbdiv: 161, postdiv1: 4, postdiv2: 1, usr divider: 1
2020-05-05 18:55:12 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 670 set refdiv: 2, fbdiv: 161, postdiv1: 3, postdiv2: 1, usr divider: 1
2020-05-05 18:55:12 driver-btm-api.c:612:set_timeout: freq 700 final timeout=168
2020-05-05 18:55:12 power_api.c:146:set_higher_voltage: higher_voltage = 18.000000
2020-05-05 18:55:12 power_api.c:428:slowly_set_iic_power_to_higher_voltage: slowly setting to voltage: 18.00 ...
2020-05-05 18:55:37 power_api.c:124:check_voltage_multi: retry time: 0
2020-05-05 18:55:38 power_api.c:86:get_average_voltage: chain[0], voltage is: 18.124219
2020-05-05 18:55:40 power_api.c:86:get_average_voltage: chain[1], voltage is: 18.105849
2020-05-05 18:55:42 power_api.c:86:get_average_voltage: chain[2], voltage is: 18.209941
2020-05-05 18:55:42 power_api.c:97:get_average_voltage: aveage voltage is: 18.146670
2020-05-05 18:55:42 frequency.c:540:get_current_min_freq: current min freq 670
2020-05-05 18:55:42 driver-btm-api.c:1660:check_clock_counter: freq 670 clock_counter_limit 85
2020-05-05 18:55:43 thread.c:799:create_check_system_status_thread: create thread
2020-05-05 18:55:44 driver-btm-api.c:2113:bitmain_soc_init: Init done!
2020-05-05 18:55:44 driver-btm-api.c:201:set_miner_status: STATUS_INIT
2020-05-05 18:55:48 driver-btm-api.c:201:set_miner_status: STATUS_OKAY
2020-05-05 18:55:57 driver-btm-api.c:1293:dhash_chip_send_job: Version num 4
2020-05-05 18:56:01 thread.c:382:check_working_voltage: current PCB min temperature is 38
2020-05-05 18:56:01 thread.c:383:check_working_voltage: current voltage is 18.00V, recovery to 17.10V
2020-05-05 18:56:01 power_api.c:397:slowly_set_iic_power_to_working_voltage: slowly setting to voltage: 17.10 ...
2020-05-05 18:56:36 power_api.c:124:check_voltage_multi: retry time: 0
2020-05-05 18:56:37 power_api.c:86:get_average_voltage: chain[0], voltage is: 17.187392
2020-05-05 18:56:39 power_api.c:86:get_average_voltage: chain[1], voltage is: 17.169023
2020-05-05 18:56:41 power_api.c:86:get_average_voltage: chain[2], voltage is: 17.273115
2020-05-05 18:56:41 power_api.c:97:get_average_voltage: aveage voltage is: 17.209844
2020-05-05 19:01:40 thread.c:422:is_zero_nonce_happened: chain_nonce[0] = 17626
2020-05-05 19:01:40 thread.c:422:is_zero_nonce_happened: chain_nonce[1] = 16888
2020-05-05 19:01:40 thread.c:422:is_zero_nonce_happened: chain_nonce[2] = 14630
2020-05-05 19:26:41 thread.c:204:calc_hashrate_avg: avg rate is 39401.36 in 30 mins
2020-05-05 19:26:41 temperature.c:450:temp_statistics_show: pcb temp 39~56 chip temp 61~80
2020-05-05 19:56:42 thread.c:204:calc_hashrate_avg: avg rate is 39142.25 in 30 mins
2020-05-05 19:56:42 temperature.c:450:temp_statistics_show: pcb temp 41~56 chip temp 61~80
2020-05-05 19:56:42 thread.c:285:check_hashrate: latest avg rate < 0.98......
2020-05-05 19:56:42 thread.c:286:check_hashrate: current PCB min temperature 41
2020-05-05 19:56:42 thread.c:287:check_hashrate: current voltage is 17.10V, working voltage is 17.10V
2020-05-05 19:56:42 thread.c:318:check_hashrate: high temp, increase voltage 0.1V/0.2V to 17.20V
2020-05-05 19:56:42 driver-btm-api.c:2124:bitmain_reopen_core: reopen_core start!
2020-05-05 19:56:48 driver-btm-api.c:1067:init_miner_version: miner ID : 8042750618c0885c
2020-05-05 19:56:48 driver-btm-api.c:1073:init_miner_version: FPGA Version = 0xB013
2020-05-05 19:56:49 chain = 0, mode = 0, load_done = false.
2020-05-05 19:56:49 chain = 1, mode = 0, load_done = false.
2020-05-05 19:56:49 chain = 2, mode = 0, load_done = false.
2020-05-05 19:56:50 chain = 0, mode = 0, load_done = false.
2020-05-05 19:56:50 chain = 1, mode = 0, load_done = false.
2020-05-05 19:56:50 chain = 2, mode = 0, load_done = false.
2020-05-05 19:56:50 eeprom.c:425:check_pattern_test_level: invalid pattern test result. ignore
2020-05-05 19:56:51 chain = 0, mode = 0, load_done = false.
2020-05-05 19:56:51 chain = 1, mode = 0, load_done = false.
2020-05-05 19:56:51 chain = 2, mode = 0, load_done = false.
2020-05-05 19:56:52 chain = 0, mode = 0, load_done = false.
2020-05-05 19:56:52 chain = 1, mode = 0, load_done = false.
2020-05-05 19:56:52 chain = 2, mode = 0, load_done = false.
2020-05-05 19:56:52 eeprom.c:425:check_pattern_test_level: invalid pattern test result. ignore
2020-05-05 19:56:53 chain = 0, mode = 0, load_done = false.
2020-05-05 19:56:53 chain = 1, mode = 0, load_done = false.
2020-05-05 19:56:53 chain = 2, mode = 0, load_done = false.
2020-05-05 19:56:54 eeprom.c:425:check_pattern_test_level: invalid pattern test result. ignore
2020-05-05 19:56:54 driver-btm-api.c:705:get_product_id: product_id[0] = 1
2020-05-05 19:56:54 driver-btm-api.c:705:get_product_id: product_id[1] = 1
2020-05-05 19:56:54 driver-btm-api.c:705:get_product_id: product_id[2] = 1
2020-05-05 19:56:54 driver-btm-api.c:1633:get_ccdly_opt: ccdly_opt[0] = 1
2020-05-05 19:56:54 driver-btm-api.c:1633:get_ccdly_opt: ccdly_opt[1] = 1
2020-05-05 19:56:54 driver-btm-api.c:1633:get_ccdly_opt: ccdly_opt[2] = 1
2020-05-05 19:56:54 driver-btm-api.c:1877:bitmain_board_init: g_ccdly_opt = 1
2020-05-05 19:56:54 driver-btm-api.c:644:_set_project_type: project:2
2020-05-05 19:56:54 driver-btm-api.c:674:_set_project_type: Project type: Antminer T17
2020-05-05 19:56:54 driver-btm-api.c:685:dump_pcb_bom_version: Chain [0] PCB Version: 0x0100
2020-05-05 19:56:54 driver-btm-api.c:686:dump_pcb_bom_version: Chain [0] BOM Version: 0x0100
2020-05-05 19:56:54 driver-btm-api.c:685:dump_pcb_bom_version: Chain [1] PCB Version: 0x0100
2020-05-05 19:56:54 driver-btm-api.c:686:dump_pcb_bom_version: Chain [1] BOM Version: 0x0100
2020-05-05 19:56:54 driver-btm-api.c:685:dump_pcb_bom_version: Chain [2] PCB Version: 0x0100
2020-05-05 19:56:54 driver-btm-api.c:686:dump_pcb_bom_version: Chain [2] BOM Version: 0x0100
2020-05-05 19:56:57 driver-btm-api.c:1897:bitmain_board_init: Fan check passed.
2020-05-05 19:56:57 register.c:283:get_register: !!! reg crc error
2020-05-05 19:56:59 board.c:36:jump_and_app_check_restore_pic: chain[0] PIC jump to app
2020-05-05 19:57:05 board.c:40:jump_and_app_check_restore_pic: Check chain[0] PIC fw version=0xb9
2020-05-05 19:57:08 board.c:36:jump_and_app_check_restore_pic: chain[1] PIC jump to app
2020-05-05 19:57:13 board.c:40:jump_and_app_check_restore_pic: Check chain[1] PIC fw version=0xb9
2020-05-05 19:57:15 board.c:36:jump_and_app_check_restore_pic: chain[2] PIC jump to app
2020-05-05 19:57:18 board.c:40:jump_and_app_check_restore_pic: Check chain[2] PIC fw version=0xb9
2020-05-05 19:57:18 power_api.c:55:power_init: power init ...
2020-05-05 19:57:18 driver-btm-api.c:1907:bitmain_board_init: Enter 30s sleep to make sure power release finish.
2020-05-05 19:57:50 power_api.c:232:set_iic_power_to_highest_voltage: setting to voltage: 17.00 ...
2020-05-05 19:57:52 power_api.c:124:check_voltage_multi: retry time: 0
2020-05-05 19:57:54 power_api.c:86:get_average_voltage: chain[0], voltage is: 17.193515
2020-05-05 19:57:57 power_api.c:86:get_average_voltage: chain[1], voltage is: 17.113916
2020-05-05 19:58:00 power_api.c:86:get_average_voltage: chain[2], voltage is: 17.230254
2020-05-05 19:58:00 power_api.c:97:get_average_voltage: aveage voltage is: 17.179228
2020-05-05 19:58:00 power_api.c:182:set_iic_power_by_voltage: now set voltage to : 17.000000
2020-05-05 19:58:00 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[0]: chip baud = 115200, chip_divider = 26
2020-05-05 19:58:00 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[1]: chip baud = 115200, chip_divider = 26
2020-05-05 19:58:00 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[2]: chip baud = 115200, chip_divider = 26
2020-05-05 19:58:00 uart.c:80:set_baud: set fpga_baud = 115200, fpga_divider = 26
2020-05-05 19:58:10 driver-btm-api.c:1010:check_asic_number_with_power_on: Chain[0]: find 30 asic, times 0
2020-05-05 19:58:20 driver-btm-api.c:1010:check_asic_number_with_power_on: Chain[1]: find 30 asic, times 0
2020-05-05 19:58:30 driver-btm-api.c:1010:check_asic_number_with_power_on: Chain[2]: find 30 asic, times 0
2020-05-05 19:58:33 driver-btm-api.c:348:set_order_clock: chain[0]: set order clock, stragegy 3 clock_en=0x1
2020-05-05 19:58:33 driver-btm-api.c:348:set_order_clock: chain[1]: set order clock, stragegy 3 clock_en=0x1
2020-05-05 19:58:34 driver-btm-api.c:348:set_order_clock: chain[2]: set order clock, stragegy 3 clock_en=0x1
2020-05-05 19:58:34 driver-hash-chip.c:490:set_clock_delay_control: core_data = 0xb4
2020-05-05 19:58:34 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[0]: chip baud = 3000000, chip_divider = 0
2020-05-05 19:58:34 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[1]: chip baud = 3000000, chip_divider = 0
2020-05-05 19:58:34 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[2]: chip baud = 3000000, chip_divider = 0
2020-05-05 19:58:34 uart.c:80:set_baud: set fpga_baud = 3000000, fpga_divider = 0
2020-05-05 19:58:34 driver-btm-api.c:1660:check_clock_counter: freq 50 clock_counter_limit 6
2020-05-05 19:58:35 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[0]: chip baud = 115200, chip_divider = 26
2020-05-05 19:58:35 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[1]: chip baud = 115200, chip_divider = 26
2020-05-05 19:58:35 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[2]: chip baud = 115200, chip_divider = 26
2020-05-05 19:58:35 uart.c:80:set_baud: set fpga_baud = 115200, fpga_divider = 26
2020-05-05 19:58:35 voltage[0] = 1710
2020-05-05 19:58:35 voltage[1] = 1710
2020-05-05 19:58:35 voltage[2] = 1710
2020-05-05 19:58:35 power_api.c:140:set_working_voltage: working_voltage = 17.100000
2020-05-05 19:58:36 temperature.c:282:calibrate_temp_sensor_one_chain: Temperature sensor calibration: chain 0 success.
2020-05-05 19:58:37 temperature.c:282:calibrate_temp_sensor_one_chain: Temperature sensor calibration: chain 1 success.
2020-05-05 19:58:39 temperature.c:282:calibrate_temp_sensor_one_chain: Temperature sensor calibration: chain 2 success.
2020-05-05 19:58:39 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[0]: chip baud = 6000000, chip_divider = 7
2020-05-05 19:58:39 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[1]: chip baud = 6000000, chip_divider = 7
2020-05-05 19:58:39 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[2]: chip baud = 6000000, chip_divider = 7
2020-05-05 19:58:39 uart.c:80:set_baud: set fpga_baud = 6000000, fpga_divider = 3
2020-05-05 19:58:40 driver-btm-api.c:248:check_bringup_temp: Bring up temperature is 16
2020-05-05 19:58:40 driver-btm-api.c:581:calculate_timeout: dev->timeout = 392
2020-05-05 19:58:40 power_api.c:379:slowly_set_iic_power_to_custom_voltage: slowly setting to voltage: 18.00 ...
2020-05-05 19:59:13 power_api.c:124:check_voltage_multi: retry time: 0
2020-05-05 19:59:15 power_api.c:86:get_average_voltage: chain[0], voltage is: 18.142588
2020-05-05 19:59:16 power_api.c:86:get_average_voltage: chain[1], voltage is: 18.118095
2020-05-05 19:59:20 power_api.c:86:get_average_voltage: chain[2], voltage is: 18.234433
2020-05-05 19:59:20 power_api.c:97:get_average_voltage: aveage voltage is: 18.165039
2020-05-05 19:59:20 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 42 set refdiv: 2, fbdiv: 168, postdiv1: 7, postdiv2: 7, usr divider: 1
2020-05-05 19:59:20 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 50 set refdiv: 2, fbdiv: 168, postdiv1: 7, postdiv2: 6, usr divider: 1
2020-05-05 19:59:20 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 60 set refdiv: 2, fbdiv: 168, postdiv1: 7, postdiv2: 5, usr divider: 1
2020-05-05 19:59:20 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 75 set refdiv: 2, fbdiv: 168, postdiv1: 7, postdiv2: 4, usr divider: 1
2020-05-05 19:59:20 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 100 set refdiv: 2, fbdiv: 168, postdiv1: 7, postdiv2: 3, usr divider: 1
2020-05-05 19:59:20 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 150 set refdiv: 2, fbdiv: 168, postdiv1: 7, postdiv2: 2, usr divider: 1
2020-05-05 19:59:20 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 300 set refdiv: 2, fbdiv: 168, postdiv1: 7, postdiv2: 1, usr divider: 1
2020-05-05 19:59:20 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 350 set refdiv: 2, fbdiv: 168, postdiv1: 6, postdiv2: 1, usr divider: 1
2020-05-05 19:59:20 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 420 set refdiv: 2, fbdiv: 168, postdiv1: 5, postdiv2: 1, usr divider: 1
2020-05-05 19:59:21 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 525 set refdiv: 2, fbdiv: 168, postdiv1: 4, postdiv2: 1, usr divider: 1
2020-05-05 19:59:21 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 700 set refdiv: 2, fbdiv: 168, postdiv1: 3, postdiv2: 1, usr divider: 1
2020-05-05 19:59:21 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 41 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 7, usr divider: 1
2020-05-05 19:59:21 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 47 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 6, usr divider: 1
2020-05-05 19:59:21 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 57 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 5, usr divider: 1
2020-05-05 19:59:21 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 71 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 4, usr divider: 1
2020-05-05 19:59:21 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 95 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 3, usr divider: 1
2020-05-05 19:59:21 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 143 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 2, usr divider: 1
2020-05-05 19:59:21 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 287 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 1, usr divider: 1
2020-05-05 19:59:21 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 335 set refdiv: 2, fbdiv: 161, postdiv1: 6, postdiv2: 1, usr divider: 1
2020-05-05 19:59:22 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 402 set refdiv: 2, fbdiv: 161, postdiv1: 5, postdiv2: 1, usr divider: 1
2020-05-05 19:59:22 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 503 set refdiv: 2, fbdiv: 161, postdiv1: 4, postdiv2: 1, usr divider: 1
2020-05-05 19:59:22 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 670 set refdiv: 2, fbdiv: 161, postdiv1: 3, postdiv2: 1, usr divider: 1
2020-05-05 19:59:22 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 41 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 7, usr divider: 1
2020-05-05 19:59:22 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 47 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 6, usr divider: 1
2020-05-05 19:59:22 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 57 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 5, usr divider: 1
2020-05-05 19:59:22 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 71 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 4, usr divider: 1
2020-05-05 19:59:22 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 95 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 3, usr divider: 1
2020-05-05 19:59:22 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 143 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 2, usr divider: 1
2020-05-05 19:59:23 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 287 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 1, usr divider: 1
2020-05-05 19:59:23 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 335 set refdiv: 2, fbdiv: 161, postdiv1: 6, postdiv2: 1, usr divider: 1
2020-05-05 19:59:23 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 402 set refdiv: 2, fbdiv: 161, postdiv1: 5, postdiv2: 1, usr divider: 1
2020-05-05 19:59:23 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 503 set refdiv: 2, fbdiv: 161, postdiv1: 4, postdiv2: 1, usr divider: 1
2020-05-05 19:59:23 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 670 set refdiv: 2, fbdiv: 161, postdiv1: 3, postdiv2: 1, usr divider: 1
2020-05-05 19:59:23 driver-btm-api.c:612:set_timeout: freq 700 final timeout=168
2020-05-05 19:59:23 power_api.c:146:set_higher_voltage: higher_voltage = 18.000000
2020-05-05 19:59:23 power_api.c:428:slowly_set_iic_power_to_higher_voltage: slowly setting to voltage: 18.00 ...
2020-05-05 19:59:43 power_api.c:124:check_voltage_multi: retry time: 0
2020-05-05 19:59:45 power_api.c:86:get_average_voltage: chain[0], voltage is: 18.118095
2020-05-05 19:59:47 power_api.c:86:get_average_voltage: chain[1], voltage is: 18.105849
2020-05-05 19:59:49 power_api.c:86:get_average_voltage: chain[2], voltage is: 18.216064
2020-05-05 19:59:49 power_api.c:97:get_average_voltage: aveage voltage is: 18.146670
2020-05-05 19:59:49 driver-btm-api.c:2186:bitmain_reopen_core: reopen_core done!
2020-05-05 19:59:49 power_api.c:379:slowly_set_iic_power_to_custom_voltage: slowly setting to voltage: 17.20 ...
2020-05-05 20:00:29 power_api.c:124:check_voltage_multi: retry time: 0
2020-05-05 20:00:31 power_api.c:86:get_average_voltage: chain[0], voltage is: 17.273115
2020-05-05 20:00:33 power_api.c:86:get_average_voltage: chain[1], voltage is: 17.254746
2020-05-05 20:00:35 power_api.c:86:get_average_voltage: chain[2], voltage is: 17.377207
2020-05-05 20:00:35 power_api.c:97:get_average_voltage: aveage voltage is: 17.301689
2020-05-05 20:00:35 power_api.c:140:set_working_voltage: working_voltage = 17.200001
2020-05-05 20:01:34 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 0
2020-05-05 20:01:34 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 1
2020-05-05 20:01:39 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 1, chip = 168, reg = 28, got chain = 2, chip = 178, reg = 200
2020-05-05 20:01:39 register.c:290:get_register: !!! REG_TYPE = 1. 721833730
2020-05-05 20:05:34 thread.c:422:is_zero_nonce_happened: chain_nonce[0] = 205495
2020-05-05 20:05:34 thread.c:422:is_zero_nonce_happened: chain_nonce[1] = 196027
2020-05-05 20:05:34 thread.c:422:is_zero_nonce_happened: chain_nonce[2] = 163020
2020-05-05 20:30:35 thread.c:204:calc_hashrate_avg: avg rate is 33210.39 in 30 mins
2020-05-05 20:30:35 temperature.c:450:temp_statistics_show: pcb temp 41~55 chip temp 57~79
2020-05-05 20:30:35 thread.c:285:check_hashrate: latest avg rate < 0.98......
2020-05-05 20:30:35 thread.c:286:check_hashrate: current PCB min temperature 41
2020-05-05 20:30:35 thread.c:287:check_hashrate: current voltage is 17.20V, working voltage is 17.20V
2020-05-05 20:30:35 thread.c:312:check_hashrate: high temp, voltage has already increased 0.1V/0.2V
2020-05-05 21:00:36 thread.c:204:calc_hashrate_avg: avg rate is 32871.43 in 30 mins
2020-05-05 21:00:36 temperature.c:450:temp_statistics_show: pcb temp 41~56 chip temp 57~80
2020-05-05 21:00:36 thread.c:285:check_hashrate: latest avg rate < 0.98......
2020-05-05 21:00:36 thread.c:286:check_hashrate: current PCB min temperature 41
2020-05-05 21:00:36 thread.c:287:check_hashrate: current voltage is 17.20V, working voltage is 17.20V
2020-05-05 21:00:36 thread.c:312:check_hashrate: high temp, voltage has already increased 0.1V/0.2V
Miner Status Screen Shot: https://drive.google.com/file/d/1PT64Ob4JA5zpMqUrPiP2YSL-PBWEWON7/view?usp=sharing This is the part. Same Hashboard (Chain [2]) that was giving me grief and is inconsistent. Never got this message before, but now its running at ~40% Hash rate, this is the original symptom that my whole situation started out with. 2020-05-05 20:01:34 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 0
2020-05-05 20:01:34 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 1
2020-05-05 20:01:39 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 1, chip = 168, reg = 28, got chain = 2, chip = 178, reg = 200
2020-05-05 20:01:39 register.c:290:get_register: !!! REG_TYPE = 1. 721833730
Do you still think it is a PSU issue? I think it could be with all the Voltage changing that it is doing, but still it seems like temperature is the issue. Finally got some info in the Log that points to where on this particular hashboard is the issue?? What is the next step I should take? Jacob
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: mikeywith on May 05, 2020, 09:55:40 PM
Without being 100% sure the PSU is not causing the issue, all we can do is speculate, and since the miner does power up, it means the PSU isn't complelty dead, simply something is wrong with it, so it would work one time and fail at another, as for the temperature the kernel log shows
2020-05-05 21:00:36 temperature.c:450:temp_statistics_show: pcb temp 41~56 chip temp 57~80
Antminer T17 has a max pcb temp of 75, your gear is 20 degrees far from that, also suspecting the PSU being the underlying cause of all this, doesn't negate the fact that chain 2 might be "dying" and is causing all the issues, you could disconnect chain 2 to see if the miner acts differently, but the proper way of troubleshooting IMO is top to bottom, you start with the PSU, Control Board, Network Cable, Wiring and etc. and THEN dig deeper into each hashbarods, you might think that there is no difference between the two approaches, but there is, there is a chance that your PSU is not able to supply enough power to all 3 boards despite that fact that all 3 boards are good, so you remove chain 2, everything looks great and you think your PSU is fine and board is bad when the fact is the exact the opposite.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: Scorpyy on May 05, 2020, 10:06:19 PM
If you decide to go for RMA, on all the new models you MUST ship the WHOLE miner, you might get lucky enough to be asked to ship only the bad part such as a hash board
I asked them if i could send only the hash boards. Here is their response: "If the hashboard is sent separately, the whole machine can not be debugged. It is possible that the repaired hashboard can still not be used after being installed. The warranty will be lost if the hashboard is sent separately, If you accept this risk, you can send it separately"
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: mysticbitcoin on May 06, 2020, 05:27:20 PM
UPDATE: PSU has been changed to a known good one. The Hashboard in question is now totally out of commission. The Board is only showing 22 Chips responding, I tried re-seating the cable as well as trying other cable from another good T17 Antminer. I have to make sure that it is the board that originally I thought it to be (one closest to the PSU). But I am at a loss. At this stage the Logs are not showing any of the High Temp messages and the PSU being set +0.10V to 17.20V to compensate. That maybe because the Controller has disabled the Hashboard in question and it is not instigating the temp issue. So what should I do next. This T17 was from July 2019 and so out of warranty. I need some advice and direction, and I'm willing to go all the way to repair the board myself. Kernel Log: Booting Linux on physical CPU 0x0
Linux version 4.6.0-xilinx-gff8137b-dirty (lzq@armdev2) (gcc version 4.8.3 20140320 (prerelease) (Sourcery CodeBench Lite 2014.05-23) ) #25 SMP PREEMPT Fri Nov 23 15:30:52 CST 2018
CPU: ARMv7 Processor [413fc090] revision 0 (ARMv7), cr=18c5387d
CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
Machine model: Xilinx Zynq
cma: Reserved 16 MiB at 0x0e000000
Memory policy: Data cache writealloc
On node 0 totalpages: 61440
free_area_init_node: node 0, pgdat c0b39280, node_mem_map cde10000
Normal zone: 480 pages used for memmap
Normal zone: 0 pages reserved
Normal zone: 61440 pages, LIFO batch:15
percpu: Embedded 12 pages/cpu @cddf1000 s19776 r8192 d21184 u49152
pcpu-alloc: s19776 r8192 d21184 u49152 alloc=12*4096
pcpu-alloc: [0] 0 [0] 1
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 60960
Kernel command line: mem=240M console=ttyPS0,115200 ramdisk_size=33554432 root=/dev/ram rw earlyprintk
PID hash table entries: 1024 (order: 0, 4096 bytes)
Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
Memory: 203756K/245760K available (6345K kernel code, 231K rwdata, 1896K rodata, 1024K init, 223K bss, 25620K reserved, 16384K cma-reserved, 0K highmem)
Virtual kernel memory layout:
vector : 0xffff0000 - 0xffff1000 ( 4 kB)
fixmap : 0xffc00000 - 0xfff00000 (3072 kB)
vmalloc : 0xcf800000 - 0xff800000 ( 768 MB)
lowmem : 0xc0000000 - 0xcf000000 ( 240 MB)
pkmap : 0xbfe00000 - 0xc0000000 ( 2 MB)
modules : 0xbf000000 - 0xbfe00000 ( 14 MB)
.text : 0xc0008000 - 0xc090c424 (9234 kB)
.init : 0xc0a00000 - 0xc0b00000 (1024 kB)
.data : 0xc0b00000 - 0xc0b39fe0 ( 232 kB)
.bss : 0xc0b39fe0 - 0xc0b71c28 ( 224 kB)
Preemptible hierarchical RCU implementation.
Build-time adjustment of leaf fanout to 32.
RCU restricting CPUs from NR_CPUS=4 to nr_cpu_ids=2.
RCU: Adjusting geometry for rcu_fanout_leaf=32, nr_cpu_ids=2
NR_IRQS:16 nr_irqs:16 16
efuse mapped to cf800000
ps7-slcr mapped to cf802000
L2C: platform modifies aux control register: 0x72360000 -> 0x72760000
L2C: DT/platform modifies aux control register: 0x72360000 -> 0x72760000
L2C-310 erratum 769419 enabled
L2C-310 enabling early BRESP for Cortex-A9
L2C-310 full line of zeros enabled for Cortex-A9
L2C-310 ID prefetch enabled, offset 1 lines
L2C-310 dynamic clock gating enabled, standby mode enabled
L2C-310 cache controller enabled, 8 ways, 512 kB
L2C-310: CACHE_ID 0x410000c8, AUX_CTRL 0x76760001
zynq_clock_init: clkc starts at cf802100
Zynq clock init
sched_clock: 64 bits at 333MHz, resolution 3ns, wraps every 4398046511103ns
clocksource: arm_global_timer: mask: 0xffffffffffffffff max_cycles: 0x4ce07af025, max_idle_ns: 440795209040 ns
Switching to timer-based delay loop, resolution 3ns
clocksource: ttc_clocksource: mask: 0xffff max_cycles: 0xffff, max_idle_ns: 537538477 ns
ps7-ttc #0 at cf80a000, irq=18
Console: colour dummy device 80x30
Calibrating delay loop (skipped), value calculated using timer frequency.. 666.66 BogoMIPS (lpj=3333333)
pid_max: default: 32768 minimum: 301
Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
CPU: Testing write buffer coherency: ok
CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
Setting up static identity map for 0x100000 - 0x100058
CPU1: failed to boot: -1
Brought up 1 CPUs
SMP: Total of 1 processors activated (666.66 BogoMIPS).
CPU: All CPU(s) started in SVC mode.
devtmpfs: initialized
VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4
clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
pinctrl core: initialized pinctrl subsystem
NET: Registered protocol family 16
DMA: preallocated 256 KiB pool for atomic coherent allocations
cpuidle: using governor menu
hw-breakpoint: found 5 (+1 reserved) breakpoint and 1 watchpoint registers.
hw-breakpoint: maximum watchpoint size is 4 bytes.
zynq-ocm f800c000.ps7-ocmc: ZYNQ OCM pool: 256 KiB @ 0xcf880000
vgaarb: loaded
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
media: Linux media interface: v0.10
Linux video capture interface: v2.00
pps_core: LinuxPPS API ver. 1 registered
pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
PTP clock support registered
EDAC MC: Ver: 3.0.0
Advanced Linux Sound Architecture Driver Initialized.
clocksource: Switched to clocksource arm_global_timer
NET: Registered protocol family 2
TCP established hash table entries: 2048 (order: 1, 8192 bytes)
TCP bind hash table entries: 2048 (order: 2, 16384 bytes)
TCP: Hash tables configured (established 2048 bind 2048)
UDP hash table entries: 256 (order: 1, 8192 bytes)
UDP-Lite hash table entries: 256 (order: 1, 8192 bytes)
NET: Registered protocol family 1
RPC: Registered named UNIX socket transport module.
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
PCI: CLS 0 bytes, default 64
Trying to unpack rootfs image as initramfs...
rootfs image is not initramfs (no cpio magic); looks like an initrd
Freeing initrd memory: 12580K (cceb8000 - cdb01000)
hw perfevents: enabled with armv7_cortex_a9 PMU driver, 7 counters available
futex hash table entries: 512 (order: 3, 32768 bytes)
workingset: timestamp_bits=28 max_order=16 bucket_order=0
jffs2: version 2.2. (NAND) (SUMMARY) © 2001-2006 Red Hat, Inc.
io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered (default)
dma-pl330 f8003000.ps7-dma: Loaded driver for PL330 DMAC-241330
dma-pl330 f8003000.ps7-dma: DBUFF-128x8bytes Num_Chans-8 Num_Peri-4 Num_Events-16
e0000000.serial: ttyPS0 at MMIO 0xe0000000 (irq = 158, base_baud = 6249999) is a xuartps
console [ttyPS0] enabled
xdevcfg f8007000.ps7-dev-cfg: ioremap 0xf8007000 to cf86e000
[drm] Initialized drm 1.1.0 20060810
brd: module loaded
loop: module loaded
CAN device driver interface
gpiod_set_value: invalid GPIO
libphy: MACB_mii_bus: probed
macb e000b000.ethernet eth0: Cadence GEM rev 0x00020118 at 0xe000b000 irq 31 (00:0a:35:00:00:00)
Generic PHY e000b000.etherne:00: attached PHY driver [Generic PHY] (mii_bus:phy_addr=e000b000.etherne:00, irq=-1)
e1000e: Intel(R) PRO/1000 Network Driver - 3.2.6-k
e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
ehci-pci: EHCI PCI platform driver
usbcore: registered new interface driver usb-storage
mousedev: PS/2 mouse device common for all mice
i2c /dev entries driver
Xilinx Zynq CpuIdle Driver started
sdhci: Secure Digital Host Controller Interface driver
sdhci: Copyright(c) Pierre Ossman
sdhci-pltfm: SDHCI platform and OF driver helper
mmc0: SDHCI controller on e0100000.ps7-sdio [e0100000.ps7-sdio] using ADMA
ledtrig-cpu: registered to indicate activity on CPUs
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
nand: device found, Manufacturer ID: 0x2c, Chip ID: 0xda
nand: Micron MT29F2G08ABAGAWP
nand: 256 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 128
nand: WARNING: pl35x-nand: the ECC used on your system is too weak compared to the one required by the NAND chip
Bad block table found at page 131008, version 0x01
Bad block table found at page 130944, version 0x01
6 ofpart partitions found on MTD device pl35x-nand
Creating 6 MTD partitions on "pl35x-nand":
0x000000000000-0x000002800000 : "BOOT.bin-env-dts-kernel"
0x000002800000-0x000004800000 : "ramfs"
0x000004800000-0x000005000000 : "configs"
0x000005000000-0x000006000000 : "reserve"
0x000006000000-0x000008000000 : "ramfs-bak"
0x000008000000-0x000010000000 : "reserve1"
NET: Registered protocol family 10
sit: IPv6 over IPv4 tunneling driver
NET: Registered protocol family 17
can: controller area network core (rev 20120528 abi 9)
NET: Registered protocol family 29
can: raw protocol (rev 20120528)
can: broadcast manager protocol (rev 20120528 t)
can: netlink gateway (rev 20130117) max_hops=1
zynq_pm_ioremap: no compatible node found for 'xlnx,zynq-ddrc-a05'
zynq_pm_late_init: Unable to map DDRC IO memory.
Registering SWP/SWPB emulation handler
hctosys: unable to open rtc device (rtc0)
ALSA device list:
No soundcards found.
RAMDISK: gzip image found at block 0
EXT4-fs (ram0): couldn't mount as ext3 due to feature incompatibilities
EXT4-fs (ram0): mounted filesystem without journal. Opts: (null)
VFS: Mounted root (ext4 filesystem) on device 1:0.
devtmpfs: mounted
Freeing unused kernel memory: 1024K (c0a00000 - c0b00000)
EXT4-fs (ram0): re-mounted. Opts: block_validity,delalloc,barrier,user_xattr
random: dd urandom read with 0 bits of entropy available
ubi0: attaching mtd2
ubi0: scanning is finished
ubi0: attached mtd2 (name "configs", size 8 MiB)
ubi0: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
ubi0: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
ubi0: VID header offset: 2048 (aligned 2048), data offset: 4096
ubi0: good PEBs: 64, bad PEBs: 0, corrupted PEBs: 0
ubi0: user volume: 1, internal volumes: 1, max. volumes count: 128
ubi0: max/mean erase counter: 6/3, WL threshold: 4096, image sequence number: 4244297529
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 01559AD8-7B6A-42E6-A3FE-EDF3659527A9, 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: 1052/341, WL threshold: 4096, image sequence number: 4185749592
ubi1: available PEBs: 0, total reserved PEBs: 1020, PEBs reserved for bad PEB handling: 36
ubi1: background thread "ubi_bgt1d" started, PID 720
UBIFS (ubi1:0): background thread "ubifs_bgt1_0" started, PID 723
UBIFS (ubi1:0): recovery needed
UBIFS (ubi1:0): recovery completed
UBIFS (ubi1:0): UBIFS: mounted UBI device 1, volume 0, name "reserve1"
UBIFS (ubi1:0): LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
UBIFS (ubi1:0): FS size: 123039744 bytes (117 MiB, 969 LEBs), journal size 6221824 bytes (5 MiB, 49 LEBs)
UBIFS (ubi1:0): reserved for root: 4952683 bytes (4836 KiB)
UBIFS (ubi1:0): media format: w4/r0 (latest is w4/r0), UUID 4829CF2C-7435-4146-B2FD-0826AAE8443A, small LPT model
IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
macb e000b000.ethernet eth0: unable to generate target frequency: 25000000 Hz
macb e000b000.ethernet eth0: link up (100/Full)
IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
In axi fpga driver!
request_mem_region OK!
AXI fpga dev virtual address is 0xcfb38000
*base_vir_addr = 0xab013
In fpga mem driver!
request_mem_region OK!
fpga mem virtual address is 0xd2000000
random: nonblocking pool is initialized
2020-05-06 03:44:32 driver-btm-api.c:631:init_freq_mode: This is scan-user version
2020-05-06 03:44:32 driver-btm-api.c:1994:bitmain_soc_init: opt_multi_version = 1
2020-05-06 03:44:32 driver-btm-api.c:1995:bitmain_soc_init: opt_bitmain_ab = 1
2020-05-06 03:44:32 driver-btm-api.c:1996:bitmain_soc_init: opt_bitmain_work_mode = 0
2020-05-06 03:44:32 driver-btm-api.c:1997:bitmain_soc_init: Miner compile time: Tue Dec 24 16:13:07 CST 2019 type: Antminer T17
2020-05-06 03:44:32 driver-btm-api.c:1998:bitmain_soc_init: commit version: e93a09b 2019-12-24 16:03:45, build by: lol 2019-12-24 16:19:49
2020-05-06 03:44:32 driver-btm-api.c:1810:show_sn: no SN got, please write SN to /nvdata/sn
2020-05-06 03:44:32 driver-btm-api.c:1135:miner_device_init: Detect 256MB control board of XILINX
2020-05-06 03:44:32 driver-btm-api.c:1083:init_fan_parameter: fan_eft : 0 fan_pwm : 0
2020-05-06 03:44:32 thread.c:789:create_read_nonce_reg_thread: create thread
2020-05-06 03:44:38 driver-btm-api.c:1067:init_miner_version: miner ID : 8042750618c0885c
2020-05-06 03:44:38 driver-btm-api.c:1073:init_miner_version: FPGA Version = 0xB013
2020-05-06 03:44:40 eeprom.c:425:check_pattern_test_level: invalid pattern test result. ignore
2020-05-06 03:44:42 eeprom.c:425:check_pattern_test_level: invalid pattern test result. ignore
2020-05-06 03:44:44 eeprom.c:425:check_pattern_test_level: invalid pattern test result. ignore
2020-05-06 03:44:44 driver-btm-api.c:705:get_product_id: product_id[0] = 1
2020-05-06 03:44:44 driver-btm-api.c:705:get_product_id: product_id[1] = 1
2020-05-06 03:44:44 driver-btm-api.c:705:get_product_id: product_id[2] = 1
2020-05-06 03:44:44 driver-btm-api.c:1633:get_ccdly_opt: ccdly_opt[0] = 1
2020-05-06 03:44:44 driver-btm-api.c:1633:get_ccdly_opt: ccdly_opt[1] = 1
2020-05-06 03:44:44 driver-btm-api.c:1633:get_ccdly_opt: ccdly_opt[2] = 1
2020-05-06 03:44:44 driver-btm-api.c:1877:bitmain_board_init: g_ccdly_opt = 1
2020-05-06 03:44:44 driver-btm-api.c:644:_set_project_type: project:2
2020-05-06 03:44:44 driver-btm-api.c:674:_set_project_type: Project type: Antminer T17
2020-05-06 03:44:44 driver-btm-api.c:685:dump_pcb_bom_version: Chain [0] PCB Version: 0x0100
2020-05-06 03:44:44 driver-btm-api.c:686:dump_pcb_bom_version: Chain [0] BOM Version: 0x0100
2020-05-06 03:44:44 driver-btm-api.c:685:dump_pcb_bom_version: Chain [1] PCB Version: 0x0100
2020-05-06 03:44:44 driver-btm-api.c:686:dump_pcb_bom_version: Chain [1] BOM Version: 0x0100
2020-05-06 03:44:44 driver-btm-api.c:685:dump_pcb_bom_version: Chain [2] PCB Version: 0x0100
2020-05-06 03:44:44 driver-btm-api.c:686:dump_pcb_bom_version: Chain [2] BOM Version: 0x0100
2020-05-06 03:44:46 driver-btm-api.c:1897:bitmain_board_init: Fan check passed.
2020-05-06 03:44:47 board.c:36:jump_and_app_check_restore_pic: chain[0] PIC jump to app
2020-05-06 03:44:51 board.c:40:jump_and_app_check_restore_pic: Check chain[0] PIC fw version=0xb9
2020-05-06 03:44:53 board.c:36:jump_and_app_check_restore_pic: chain[1] PIC jump to app
2020-05-06 03:44:56 board.c:40:jump_and_app_check_restore_pic: Check chain[1] PIC fw version=0xb9
2020-05-06 03:44:58 board.c:36:jump_and_app_check_restore_pic: chain[2] PIC jump to app
2020-05-06 03:45:01 board.c:40:jump_and_app_check_restore_pic: Check chain[2] PIC fw version=0xb9
2020-05-06 03:45:01 thread.c:784:create_pic_heart_beat_thread: create thread
2020-05-06 03:45:01 power_api.c:55:power_init: power init ...
2020-05-06 03:45:01 driver-btm-api.c:1907:bitmain_board_init: Enter 30s sleep to make sure power release finish.
2020-05-06 03:45:01 power_api.c:46:power_off: init gpio907
2020-05-06 03:45:33 power_api.c:232:set_iic_power_to_highest_voltage: setting to voltage: 17.00 ...
2020-05-06 03:45:39 power_api.c:124:check_voltage_multi: retry time: 0
2020-05-06 03:45:41 power_api.c:86:get_average_voltage: chain[0], voltage is: 21.246972
2020-05-06 03:45:43 power_api.c:86:get_average_voltage: chain[1], voltage is: 20.573437
2020-05-06 03:45:44 power_api.c:86:get_average_voltage: chain[2], voltage is: 20.040732
2020-05-06 03:45:44 power_api.c:97:get_average_voltage: aveage voltage is: 20.620381
2020-05-06 03:45:44 power_api.c:110:check_voltage: target_vol = 17.00, actural_vol = 20.62, more than 1.0v diff.
2020-05-06 03:45:45 power_api.c:124:check_voltage_multi: retry time: 1
2020-05-06 03:45:47 power_api.c:86:get_average_voltage: chain[0], voltage is: 19.012060
2020-05-06 03:45:49 power_api.c:86:get_average_voltage: chain[1], voltage is: 18.405879
2020-05-06 03:45:52 power_api.c:86:get_average_voltage: chain[2], voltage is: 17.554775
2020-05-06 03:45:52 power_api.c:97:get_average_voltage: aveage voltage is: 18.324238
2020-05-06 03:45:52 power_api.c:110:check_voltage: target_vol = 17.00, actural_vol = 18.32, more than 1.0v diff.
2020-05-06 03:45:53 power_api.c:124:check_voltage_multi: retry time: 2
2020-05-06 03:45:55 power_api.c:86:get_average_voltage: chain[0], voltage is: 16.568965
2020-05-06 03:45:58 power_api.c:86:get_average_voltage: chain[1], voltage is: 15.681123
2020-05-06 03:46:00 power_api.c:86:get_average_voltage: chain[2], voltage is: 17.383330
2020-05-06 03:46:00 power_api.c:97:get_average_voltage: aveage voltage is: 16.544472
2020-05-06 03:46:00 power_api.c:182:set_iic_power_by_voltage: now set voltage to : 17.000000
2020-05-06 03:46:00 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[0]: chip baud = 115200, chip_divider = 26
2020-05-06 03:46:00 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[1]: chip baud = 115200, chip_divider = 26
2020-05-06 03:46:00 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[2]: chip baud = 115200, chip_divider = 26
2020-05-06 03:46:00 uart.c:80:set_baud: set fpga_baud = 115200, fpga_divider = 26
2020-05-06 03:46:10 driver-btm-api.c:1010:check_asic_number_with_power_on: Chain[0]: find 30 asic, times 0
2020-05-06 03:46:20 driver-btm-api.c:1010:check_asic_number_with_power_on: Chain[1]: find 30 asic, times 0
2020-05-06 03:46:31 driver-btm-api.c:1010:check_asic_number_with_power_on: Chain[2]: find 22 asic, times 0
2020-05-06 03:46:41 driver-btm-api.c:1010:check_asic_number_with_power_on: Chain[2]: find 22 asic, times 1
2020-05-06 03:46:51 driver-btm-api.c:1010:check_asic_number_with_power_on: Chain[2]: find 22 asic, times 2
2020-05-06 03:46:51 driver-btm-api.c:1037:check_asic_number: Chain 2 only find 22 asic, will power off hash board 2
2020-05-06 03:46:55 driver-btm-api.c:348:set_order_clock: chain[0]: set order clock, stragegy 3 clock_en=0x1
2020-05-06 03:46:55 driver-btm-api.c:348:set_order_clock: chain[1]: set order clock, stragegy 3 clock_en=0x1
2020-05-06 03:46:55 driver-hash-chip.c:490:set_clock_delay_control: core_data = 0xb4
2020-05-06 03:46:55 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[0]: chip baud = 3000000, chip_divider = 0
2020-05-06 03:46:55 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[1]: chip baud = 3000000, chip_divider = 0
2020-05-06 03:46:55 uart.c:80:set_baud: set fpga_baud = 3000000, fpga_divider = 0
2020-05-06 03:46:55 driver-btm-api.c:1660:check_clock_counter: freq 50 clock_counter_limit 6
2020-05-06 03:46:56 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[0]: chip baud = 115200, chip_divider = 26
2020-05-06 03:46:56 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[1]: chip baud = 115200, chip_divider = 26
2020-05-06 03:46:56 uart.c:80:set_baud: set fpga_baud = 115200, fpga_divider = 26
2020-05-06 03:46:56 voltage[0] = 1710
2020-05-06 03:46:56 voltage[1] = 1710
2020-05-06 03:46:56 power_api.c:140:set_working_voltage: working_voltage = 17.100000
2020-05-06 03:46:57 temperature.c:282:calibrate_temp_sensor_one_chain: Temperature sensor calibration: chain 0 success.
2020-05-06 03:46:59 temperature.c:282:calibrate_temp_sensor_one_chain: Temperature sensor calibration: chain 1 success.
2020-05-06 03:46:59 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[0]: chip baud = 6000000, chip_divider = 7
2020-05-06 03:46:59 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[1]: chip baud = 6000000, chip_divider = 7
2020-05-06 03:46:59 uart.c:80:set_baud: set fpga_baud = 6000000, fpga_divider = 3
2020-05-06 03:47:00 driver-btm-api.c:248:check_bringup_temp: Bring up temperature is 18
2020-05-06 03:47:00 thread.c:804:create_check_miner_status_thread: create thread
2020-05-06 03:47:00 thread.c:794:create_set_miner_status_thread: create thread
2020-05-06 03:47:00 driver-btm-api.c:581:calculate_timeout: dev->timeout = 392
2020-05-06 03:47:00 thread.c:779:create_temperature_monitor_thread: create thread
2020-05-06 03:47:00 freq_tuning.c:154:freq_tuning_get_max_freq: Max freq of tuning is 760
2020-05-06 03:47:00 power_api.c:379:slowly_set_iic_power_to_custom_voltage: slowly setting to voltage: 18.00 ...
2020-05-06 03:47:29 power_api.c:124:check_voltage_multi: retry time: 0
2020-05-06 03:47:30 power_api.c:86:get_average_voltage: chain[0], voltage is: 18.154834
2020-05-06 03:47:32 power_api.c:86:get_average_voltage: chain[1], voltage is: 18.142588
2020-05-06 03:47:32 power_api.c:97:get_average_voltage: aveage voltage is: 18.148711
2020-05-06 03:47:32 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 42 set refdiv: 2, fbdiv: 168, postdiv1: 7, postdiv2: 7, usr divider: 1
2020-05-06 03:47:32 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 50 set refdiv: 2, fbdiv: 168, postdiv1: 7, postdiv2: 6, usr divider: 1
2020-05-06 03:47:32 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 60 set refdiv: 2, fbdiv: 168, postdiv1: 7, postdiv2: 5, usr divider: 1
2020-05-06 03:47:32 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 75 set refdiv: 2, fbdiv: 168, postdiv1: 7, postdiv2: 4, usr divider: 1
2020-05-06 03:47:33 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 100 set refdiv: 2, fbdiv: 168, postdiv1: 7, postdiv2: 3, usr divider: 1
2020-05-06 03:47:33 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 150 set refdiv: 2, fbdiv: 168, postdiv1: 7, postdiv2: 2, usr divider: 1
2020-05-06 03:47:33 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 300 set refdiv: 2, fbdiv: 168, postdiv1: 7, postdiv2: 1, usr divider: 1
2020-05-06 03:47:33 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 350 set refdiv: 2, fbdiv: 168, postdiv1: 6, postdiv2: 1, usr divider: 1
2020-05-06 03:47:33 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 420 set refdiv: 2, fbdiv: 168, postdiv1: 5, postdiv2: 1, usr divider: 1
2020-05-06 03:47:33 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 525 set refdiv: 2, fbdiv: 168, postdiv1: 4, postdiv2: 1, usr divider: 1
2020-05-06 03:47:33 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 700 set refdiv: 2, fbdiv: 168, postdiv1: 3, postdiv2: 1, usr divider: 1
2020-05-06 03:47:33 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 41 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 7, usr divider: 1
2020-05-06 03:47:33 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 47 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 6, usr divider: 1
2020-05-06 03:47:34 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 57 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 5, usr divider: 1
2020-05-06 03:47:34 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 71 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 4, usr divider: 1
2020-05-06 03:47:34 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 95 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 3, usr divider: 1
2020-05-06 03:47:34 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 143 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 2, usr divider: 1
2020-05-06 03:47:34 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 287 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 1, usr divider: 1
2020-05-06 03:47:34 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 335 set refdiv: 2, fbdiv: 161, postdiv1: 6, postdiv2: 1, usr divider: 1
2020-05-06 03:47:34 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 402 set refdiv: 2, fbdiv: 161, postdiv1: 5, postdiv2: 1, usr divider: 1
2020-05-06 03:47:34 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 503 set refdiv: 2, fbdiv: 161, postdiv1: 4, postdiv2: 1, usr divider: 1
2020-05-06 03:47:34 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 670 set refdiv: 2, fbdiv: 161, postdiv1: 3, postdiv2: 1, usr divider: 1
2020-05-06 03:47:34 driver-btm-api.c:612:set_timeout: freq 700 final timeout=168
2020-05-06 03:47:34 power_api.c:146:set_higher_voltage: higher_voltage = 18.000000
2020-05-06 03:47:34 power_api.c:428:slowly_set_iic_power_to_higher_voltage: slowly setting to voltage: 18.00 ...
2020-05-06 03:47:56 power_api.c:124:check_voltage_multi: retry time: 0
2020-05-06 03:47:58 power_api.c:86:get_average_voltage: chain[0], voltage is: 18.167080
2020-05-06 03:47:59 power_api.c:86:get_average_voltage: chain[1], voltage is: 18.118095
2020-05-06 03:47:59 power_api.c:97:get_average_voltage: aveage voltage is: 18.142588
2020-05-06 03:47:59 frequency.c:540:get_current_min_freq: current min freq 670
2020-05-06 03:47:59 driver-btm-api.c:1660:check_clock_counter: freq 670 clock_counter_limit 85
2020-05-06 03:48:01 thread.c:799:create_check_system_status_thread: create thread
2020-05-06 03:48:01 driver-btm-api.c:2113:bitmain_soc_init: Init done!
2020-05-06 03:48:01 driver-btm-api.c:201:set_miner_status: STATUS_INIT
2020-05-06 03:48:06 driver-btm-api.c:201:set_miner_status: STATUS_OKAY
2020-05-06 03:48:11 driver-btm-api.c:1293:dhash_chip_send_job: Version num 4
2020-05-06 03:48:15 thread.c:382:check_working_voltage: current PCB min temperature is 42
2020-05-06 03:48:15 thread.c:383:check_working_voltage: current voltage is 18.00V, recovery to 17.10V
2020-05-06 03:48:15 power_api.c:397:slowly_set_iic_power_to_working_voltage: slowly setting to voltage: 17.10 ...
2020-05-06 03:48:44 power_api.c:124:check_voltage_multi: retry time: 0
2020-05-06 03:48:47 power_api.c:86:get_average_voltage: chain[0], voltage is: 17.242500
2020-05-06 03:48:50 power_api.c:86:get_average_voltage: chain[1], voltage is: 17.199638
2020-05-06 03:48:50 power_api.c:97:get_average_voltage: aveage voltage is: 17.221069
2020-05-06 03:53:50 thread.c:422:is_zero_nonce_happened: chain_nonce[0] = 17465
2020-05-06 03:53:50 thread.c:422:is_zero_nonce_happened: chain_nonce[1] = 16602
2020-05-06 04:18:50 thread.c:204:calc_hashrate_avg: avg rate is 27453.74 in 30 mins
2020-05-06 04:18:50 temperature.c:450:temp_statistics_show: pcb temp 42~56 chip temp 66~80
2020-05-06 04:48:51 thread.c:204:calc_hashrate_avg: avg rate is 27530.55 in 30 mins
2020-05-06 04:48:51 temperature.c:450:temp_statistics_show: pcb temp 43~56 chip temp 66~80
2020-05-06 05:18:52 thread.c:204:calc_hashrate_avg: avg rate is 27760.23 in 30 mins
2020-05-06 05:18:52 temperature.c:450:temp_statistics_show: pcb temp 43~56 chip temp 66~80
2020-05-06 05:48:53 thread.c:204:calc_hashrate_avg: avg rate is 27631.15 in 30 mins
2020-05-06 05:48:53 temperature.c:450:temp_statistics_show: pcb temp 43~56 chip temp 66~80
2020-05-06 06:18:54 thread.c:204:calc_hashrate_avg: avg rate is 27378.79 in 30 mins
2020-05-06 06:18:54 temperature.c:450:temp_statistics_show: pcb temp 43~56 chip temp 66~80
2020-05-06 06:48:55 thread.c:204:calc_hashrate_avg: avg rate is 27575.81 in 30 mins
2020-05-06 06:48:55 temperature.c:450:temp_statistics_show: pcb temp 44~57 chip temp 67~80
2020-05-06 07:18:56 thread.c:204:calc_hashrate_avg: avg rate is 27259.51 in 30 mins
2020-05-06 07:18:56 temperature.c:450:temp_statistics_show: pcb temp 44~57 chip temp 67~80
2020-05-06 07:48:57 thread.c:204:calc_hashrate_avg: avg rate is 27632.78 in 30 mins
2020-05-06 07:48:57 temperature.c:450:temp_statistics_show: pcb temp 44~57 chip temp 66~81
2020-05-06 08:18:58 thread.c:204:calc_hashrate_avg: avg rate is 27501.75 in 30 mins
2020-05-06 08:18:58 temperature.c:450:temp_statistics_show: pcb temp 44~56 chip temp 67~80
2020-05-06 08:48:59 thread.c:204:calc_hashrate_avg: avg rate is 27580.74 in 30 mins
2020-05-06 08:48:59 temperature.c:450:temp_statistics_show: pcb temp 44~56 chip temp 67~80
2020-05-06 09:19:00 thread.c:204:calc_hashrate_avg: avg rate is 27439.63 in 30 mins
2020-05-06 09:19:00 temperature.c:450:temp_statistics_show: pcb temp 44~56 chip temp 67~80
2020-05-06 09:49:01 thread.c:204:calc_hashrate_avg: avg rate is 27474.81 in 30 mins
2020-05-06 09:49:01 temperature.c:450:temp_statistics_show: pcb temp 44~56 chip temp 67~80
2020-05-06 10:19:02 thread.c:204:calc_hashrate_avg: avg rate is 27385.07 in 30 mins
2020-05-06 10:19:02 temperature.c:450:temp_statistics_show: pcb temp 44~56 chip temp 67~80
2020-05-06 10:49:03 thread.c:204:calc_hashrate_avg: avg rate is 27453.96 in 30 mins
2020-05-06 10:49:03 temperature.c:450:temp_statistics_show: pcb temp 44~57 chip temp 67~80
2020-05-06 11:19:04 thread.c:204:calc_hashrate_avg: avg rate is 27575.16 in 30 mins
2020-05-06 11:19:04 temperature.c:450:temp_statistics_show: pcb temp 45~56 chip temp 67~80
2020-05-06 11:49:05 thread.c:204:calc_hashrate_avg: avg rate is 27357.69 in 30 mins
2020-05-06 11:49:05 temperature.c:450:temp_statistics_show: pcb temp 45~56 chip temp 68~80
2020-05-06 12:19:05 thread.c:204:calc_hashrate_avg: avg rate is 27594.36 in 30 mins
2020-05-06 12:19:05 temperature.c:450:temp_statistics_show: pcb temp 44~56 chip temp 67~80
2020-05-06 12:49:06 thread.c:204:calc_hashrate_avg: avg rate is 27735.40 in 30 mins
2020-05-06 12:49:06 temperature.c:450:temp_statistics_show: pcb temp 44~56 chip temp 67~80
2020-05-06 13:19:07 thread.c:204:calc_hashrate_avg: avg rate is 27537.99 in 30 mins
2020-05-06 13:19:07 temperature.c:450:temp_statistics_show: pcb temp 44~56 chip temp 68~80
2020-05-06 13:49:08 thread.c:204:calc_hashrate_avg: avg rate is 27652.88 in 30 mins
2020-05-06 13:49:08 temperature.c:450:temp_statistics_show: pcb temp 45~56 chip temp 68~80
2020-05-06 14:19:09 thread.c:204:calc_hashrate_avg: avg rate is 27269.65 in 30 mins
2020-05-06 14:19:09 temperature.c:450:temp_statistics_show: pcb temp 45~57 chip temp 68~81
2020-05-06 14:49:10 thread.c:204:calc_hashrate_avg: avg rate is 27399.37 in 30 mins
2020-05-06 14:49:10 temperature.c:450:temp_statistics_show: pcb temp 45~57 chip temp 68~80
2020-05-06 15:19:11 thread.c:204:calc_hashrate_avg: avg rate is 27543.52 in 30 mins
2020-05-06 15:19:11 temperature.c:450:temp_statistics_show: pcb temp 45~56 chip temp 68~80
2020-05-06 15:49:12 thread.c:204:calc_hashrate_avg: avg rate is 27670.96 in 30 mins
2020-05-06 15:49:12 temperature.c:450:temp_statistics_show: pcb temp 44~56 chip temp 66~79
2020-05-06 16:19:13 thread.c:204:calc_hashrate_avg: avg rate is 27272.62 in 30 mins
2020-05-06 16:19:13 temperature.c:450:temp_statistics_show: pcb temp 41~56 chip temp 64~80
2020-05-06 16:49:14 thread.c:204:calc_hashrate_avg: avg rate is 27570.06 in 30 mins
2020-05-06 16:49:14 temperature.c:450:temp_statistics_show: pcb temp 42~56 chip temp 66~81
2020-05-06 17:19:15 thread.c:204:calc_hashrate_avg: avg rate is 27402.72 in 30 mins
2020-05-06 17:19:15 temperature.c:450:temp_statistics_show: pcb temp 42~56 chip temp 65~80
Miner Status Screen: https://drive.google.com/file/d/16g9lWAe2jJXcNo01baSYgOBN_od4_n2Z/view?usp=sharing Log Shows: 2020-05-06 03:46:31 driver-btm-api.c:1010:check_asic_number_with_power_on: Chain[2]: find 22 asic, times 0
2020-05-06 03:46:41 driver-btm-api.c:1010:check_asic_number_with_power_on: Chain[2]: find 22 asic, times 1
2020-05-06 03:46:51 driver-btm-api.c:1010:check_asic_number_with_power_on: Chain[2]: find 22 asic, times 2
2020-05-06 03:46:51 driver-btm-api.c:1037:check_asic_number: Chain 2 only find 22 asic, will power off hash board 2
Jacob
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: mysticbitcoin on May 06, 2020, 05:40:58 PM
I also have a complete coorespondence with Bitmain tech support, Jessica L. I can post it if you guys are interested. All they have done is given me a generic trouble shooting list and not answered any of my specific questions. Thanks for your consultation!
could you please try to exclude the issues by the below instructions
1.check the wires for the hashboard--pull them and re-plug them again, and also you can try to change the new wires
2.upgrade to the latest firmware
3. change the PSU to try it and reset the miner to the factory settings
4.flash the SD card program to recover the control board
the SD card program have be sent to you aby another email box, (also in your spam box)
instructions:
1 unzip the file we send to you
2After decompressing the card file, put all the below files into the card,
3 insert it into the card slot of the control board,
4 and power on the control board
5 after the red and green lights blinks 3 or more times you can remove the SD card , it is ok
Please let us know if you have additional questions or concerns. Jacob
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: Scorpyy on May 06, 2020, 10:29:56 PM
1 question to those who have sent units back to Bitmain for repair:
Can i switch the hash-boards from another machine? Both machines are at warranty, however one works with 2/3 and the other with 1/3 boards.
I am thinking to combine the non-working ones into the same unit and send them for repair. Do you think that this is possible? Can they even tell the difference?
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: philipma1957 on May 06, 2020, 10:38:24 PM
1 question to those who have sent units back to Bitmain for repair:
Can i switch the hash-boards from another machine? Both machines are at warranty, however one works with 2/3 and the other with 1/3 boards.
I am thinking to combine the non-working ones into the same unit and send them for repair. Do you think that this is possible?
Ask them first. Most likely they will say no. but you never know. boards used to have serial numbers so you need to ask them if it is okay.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: mikeywith on May 07, 2020, 12:46:24 AM
Can they even tell the difference?
They can, and by doing so, you will void the warranty according to their reply to your question, you could still ask them, you lose nothing. i think "If the hashboard is sent separately, the whole machine can not be debugged. It is possible that the repaired hashboard can still not be used after being installed. The warranty will be lost if the hashboard is sent separately, If you accept this risk, you can send it separately"
mysticbitcoin, the problem with that you did is that you changed two aspects at once, now the results may be very misleading, was the bad board causing the issue, or was it the psu? you removed the hashboard and replaced the PSU, the logs changed, in the end, the results are not satisfying, kindly put the bad hash board back and keep the new/working PSU.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: mysticbitcoin on May 07, 2020, 01:20:03 AM
Mikeywith, Sorry, to be clear, I did not remove the hashboard it just stopped working altogether. All I did was remove and reconnect the cable to that hashboard. It has been connected everytime. Just that it is not registering all chips now. When powered on. The only change was the PSU. I never powered the miner without a hashboard.
Jacob
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: mikeywith on May 07, 2020, 02:05:20 AM
Ok the last thing to try now would be using the old psu with the bad hashboard unplugged ( completely removed ) and there will be 2 outcomes 1 - The temp error disappears and the kernel log looks very different to the first time = psu is good but the board causes the errors sometimes. 2- Kernel log goes back to the unusal temp and voltage readings = psu is bad, the bad hash board made things even worse. And regardless of what happens, it is now safe to assume the hashboard is bad, maybe not completely dead but bad, the fact it shows 22 asics (if that doesn't change) it means either chip 22 or 23 is bad, after the psu swap you can put it back, perform a few restarts and see if it still shows exactly 22 chips, i will guide you on how to troubleshoot the bad chip and if you are willing to invest in some tools, i will tell you where to start with replacing the chips and where to buy them.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: mysticbitcoin on May 07, 2020, 03:33:33 PM
Mikeywith, Update, Here is the kernel log with the original PSU and the Hashboard (Chain[2]) unplugged. No odd messages. Looks just like when it was run with the other PSU. I will now plug it the Hashboard in question and see what the logs say and post results. Kernel Log: Booting Linux on physical CPU 0x0
Linux version 4.6.0-xilinx-gff8137b-dirty (lzq@armdev2) (gcc version 4.8.3 20140320 (prerelease) (Sourcery CodeBench Lite 2014.05-23) ) #25 SMP PREEMPT Fri Nov 23 15:30:52 CST 2018
CPU: ARMv7 Processor [413fc090] revision 0 (ARMv7), cr=18c5387d
CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
Machine model: Xilinx Zynq
cma: Reserved 16 MiB at 0x0e000000
Memory policy: Data cache writealloc
On node 0 totalpages: 61440
free_area_init_node: node 0, pgdat c0b39280, node_mem_map cde10000
Normal zone: 480 pages used for memmap
Normal zone: 0 pages reserved
Normal zone: 61440 pages, LIFO batch:15
percpu: Embedded 12 pages/cpu @cddf1000 s19776 r8192 d21184 u49152
pcpu-alloc: s19776 r8192 d21184 u49152 alloc=12*4096
pcpu-alloc: [0] 0 [0] 1
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 60960
Kernel command line: mem=240M console=ttyPS0,115200 ramdisk_size=33554432 root=/dev/ram rw earlyprintk
PID hash table entries: 1024 (order: 0, 4096 bytes)
Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
Memory: 203756K/245760K available (6345K kernel code, 231K rwdata, 1896K rodata, 1024K init, 223K bss, 25620K reserved, 16384K cma-reserved, 0K highmem)
Virtual kernel memory layout:
vector : 0xffff0000 - 0xffff1000 ( 4 kB)
fixmap : 0xffc00000 - 0xfff00000 (3072 kB)
vmalloc : 0xcf800000 - 0xff800000 ( 768 MB)
lowmem : 0xc0000000 - 0xcf000000 ( 240 MB)
pkmap : 0xbfe00000 - 0xc0000000 ( 2 MB)
modules : 0xbf000000 - 0xbfe00000 ( 14 MB)
.text : 0xc0008000 - 0xc090c424 (9234 kB)
.init : 0xc0a00000 - 0xc0b00000 (1024 kB)
.data : 0xc0b00000 - 0xc0b39fe0 ( 232 kB)
.bss : 0xc0b39fe0 - 0xc0b71c28 ( 224 kB)
Preemptible hierarchical RCU implementation.
Build-time adjustment of leaf fanout to 32.
RCU restricting CPUs from NR_CPUS=4 to nr_cpu_ids=2.
RCU: Adjusting geometry for rcu_fanout_leaf=32, nr_cpu_ids=2
NR_IRQS:16 nr_irqs:16 16
efuse mapped to cf800000
ps7-slcr mapped to cf802000
L2C: platform modifies aux control register: 0x72360000 -> 0x72760000
L2C: DT/platform modifies aux control register: 0x72360000 -> 0x72760000
L2C-310 erratum 769419 enabled
L2C-310 enabling early BRESP for Cortex-A9
L2C-310 full line of zeros enabled for Cortex-A9
L2C-310 ID prefetch enabled, offset 1 lines
L2C-310 dynamic clock gating enabled, standby mode enabled
L2C-310 cache controller enabled, 8 ways, 512 kB
L2C-310: CACHE_ID 0x410000c8, AUX_CTRL 0x76760001
zynq_clock_init: clkc starts at cf802100
Zynq clock init
sched_clock: 64 bits at 333MHz, resolution 3ns, wraps every 4398046511103ns
clocksource: arm_global_timer: mask: 0xffffffffffffffff max_cycles: 0x4ce07af025, max_idle_ns: 440795209040 ns
Switching to timer-based delay loop, resolution 3ns
clocksource: ttc_clocksource: mask: 0xffff max_cycles: 0xffff, max_idle_ns: 537538477 ns
ps7-ttc #0 at cf80a000, irq=18
Console: colour dummy device 80x30
Calibrating delay loop (skipped), value calculated using timer frequency.. 666.66 BogoMIPS (lpj=3333333)
pid_max: default: 32768 minimum: 301
Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
CPU: Testing write buffer coherency: ok
CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
Setting up static identity map for 0x100000 - 0x100058
CPU1: failed to boot: -1
Brought up 1 CPUs
SMP: Total of 1 processors activated (666.66 BogoMIPS).
CPU: All CPU(s) started in SVC mode.
devtmpfs: initialized
VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4
clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
pinctrl core: initialized pinctrl subsystem
NET: Registered protocol family 16
DMA: preallocated 256 KiB pool for atomic coherent allocations
cpuidle: using governor menu
hw-breakpoint: found 5 (+1 reserved) breakpoint and 1 watchpoint registers.
hw-breakpoint: maximum watchpoint size is 4 bytes.
zynq-ocm f800c000.ps7-ocmc: ZYNQ OCM pool: 256 KiB @ 0xcf880000
vgaarb: loaded
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
media: Linux media interface: v0.10
Linux video capture interface: v2.00
pps_core: LinuxPPS API ver. 1 registered
pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
PTP clock support registered
EDAC MC: Ver: 3.0.0
Advanced Linux Sound Architecture Driver Initialized.
clocksource: Switched to clocksource arm_global_timer
NET: Registered protocol family 2
TCP established hash table entries: 2048 (order: 1, 8192 bytes)
TCP bind hash table entries: 2048 (order: 2, 16384 bytes)
TCP: Hash tables configured (established 2048 bind 2048)
UDP hash table entries: 256 (order: 1, 8192 bytes)
UDP-Lite hash table entries: 256 (order: 1, 8192 bytes)
NET: Registered protocol family 1
RPC: Registered named UNIX socket transport module.
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
PCI: CLS 0 bytes, default 64
Trying to unpack rootfs image as initramfs...
rootfs image is not initramfs (no cpio magic); looks like an initrd
Freeing initrd memory: 12580K (cceb8000 - cdb01000)
hw perfevents: enabled with armv7_cortex_a9 PMU driver, 7 counters available
futex hash table entries: 512 (order: 3, 32768 bytes)
workingset: timestamp_bits=28 max_order=16 bucket_order=0
jffs2: version 2.2. (NAND) (SUMMARY) © 2001-2006 Red Hat, Inc.
io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered (default)
dma-pl330 f8003000.ps7-dma: Loaded driver for PL330 DMAC-241330
dma-pl330 f8003000.ps7-dma: DBUFF-128x8bytes Num_Chans-8 Num_Peri-4 Num_Events-16
e0000000.serial: ttyPS0 at MMIO 0xe0000000 (irq = 158, base_baud = 6249999) is a xuartps
console [ttyPS0] enabled
xdevcfg f8007000.ps7-dev-cfg: ioremap 0xf8007000 to cf86e000
[drm] Initialized drm 1.1.0 20060810
brd: module loaded
loop: module loaded
CAN device driver interface
gpiod_set_value: invalid GPIO
libphy: MACB_mii_bus: probed
macb e000b000.ethernet eth0: Cadence GEM rev 0x00020118 at 0xe000b000 irq 31 (00:0a:35:00:00:00)
Generic PHY e000b000.etherne:00: attached PHY driver [Generic PHY] (mii_bus:phy_addr=e000b000.etherne:00, irq=-1)
e1000e: Intel(R) PRO/1000 Network Driver - 3.2.6-k
e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
ehci-pci: EHCI PCI platform driver
usbcore: registered new interface driver usb-storage
mousedev: PS/2 mouse device common for all mice
i2c /dev entries driver
Xilinx Zynq CpuIdle Driver started
sdhci: Secure Digital Host Controller Interface driver
sdhci: Copyright(c) Pierre Ossman
sdhci-pltfm: SDHCI platform and OF driver helper
mmc0: SDHCI controller on e0100000.ps7-sdio [e0100000.ps7-sdio] using ADMA
ledtrig-cpu: registered to indicate activity on CPUs
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
nand: device found, Manufacturer ID: 0x2c, Chip ID: 0xda
nand: Micron MT29F2G08ABAGAWP
nand: 256 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 128
nand: WARNING: pl35x-nand: the ECC used on your system is too weak compared to the one required by the NAND chip
Bad block table found at page 131008, version 0x01
Bad block table found at page 130944, version 0x01
6 ofpart partitions found on MTD device pl35x-nand
Creating 6 MTD partitions on "pl35x-nand":
0x000000000000-0x000002800000 : "BOOT.bin-env-dts-kernel"
0x000002800000-0x000004800000 : "ramfs"
0x000004800000-0x000005000000 : "configs"
0x000005000000-0x000006000000 : "reserve"
0x000006000000-0x000008000000 : "ramfs-bak"
0x000008000000-0x000010000000 : "reserve1"
NET: Registered protocol family 10
sit: IPv6 over IPv4 tunneling driver
NET: Registered protocol family 17
can: controller area network core (rev 20120528 abi 9)
NET: Registered protocol family 29
can: raw protocol (rev 20120528)
can: broadcast manager protocol (rev 20120528 t)
can: netlink gateway (rev 20130117) max_hops=1
zynq_pm_ioremap: no compatible node found for 'xlnx,zynq-ddrc-a05'
zynq_pm_late_init: Unable to map DDRC IO memory.
Registering SWP/SWPB emulation handler
hctosys: unable to open rtc device (rtc0)
ALSA device list:
No soundcards found.
RAMDISK: gzip image found at block 0
EXT4-fs (ram0): couldn't mount as ext3 due to feature incompatibilities
EXT4-fs (ram0): mounted filesystem without journal. Opts: (null)
VFS: Mounted root (ext4 filesystem) on device 1:0.
devtmpfs: mounted
Freeing unused kernel memory: 1024K (c0a00000 - c0b00000)
EXT4-fs (ram0): re-mounted. Opts: block_validity,delalloc,barrier,user_xattr
random: dd urandom read with 0 bits of entropy available
ubi0: attaching mtd2
ubi0: scanning is finished
ubi0: attached mtd2 (name "configs", size 8 MiB)
ubi0: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
ubi0: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
ubi0: VID header offset: 2048 (aligned 2048), data offset: 4096
ubi0: good PEBs: 64, bad PEBs: 0, corrupted PEBs: 0
ubi0: user volume: 1, internal volumes: 1, max. volumes count: 128
ubi0: max/mean erase counter: 6/3, WL threshold: 4096, image sequence number: 4244297529
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 01559AD8-7B6A-42E6-A3FE-EDF3659527A9, 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: 1053/342, WL threshold: 4096, image sequence number: 4185749592
ubi1: available PEBs: 0, total reserved PEBs: 1020, PEBs reserved for bad PEB handling: 36
ubi1: background thread "ubi_bgt1d" started, PID 720
UBIFS (ubi1:0): background thread "ubifs_bgt1_0" started, PID 723
UBIFS (ubi1:0): recovery needed
UBIFS (ubi1:0): recovery completed
UBIFS (ubi1:0): UBIFS: mounted UBI device 1, volume 0, name "reserve1"
UBIFS (ubi1:0): LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
UBIFS (ubi1:0): FS size: 123039744 bytes (117 MiB, 969 LEBs), journal size 6221824 bytes (5 MiB, 49 LEBs)
UBIFS (ubi1:0): reserved for root: 4952683 bytes (4836 KiB)
UBIFS (ubi1:0): media format: w4/r0 (latest is w4/r0), UUID 4829CF2C-7435-4146-B2FD-0826AAE8443A, small LPT model
IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
macb e000b000.ethernet eth0: unable to generate target frequency: 25000000 Hz
macb e000b000.ethernet eth0: link up (100/Full)
IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
In axi fpga driver!
request_mem_region OK!
AXI fpga dev virtual address is 0xcfb38000
*base_vir_addr = 0xab013
In fpga mem driver!
request_mem_region OK!
fpga mem virtual address is 0xd2000000
random: nonblocking pool is initialized
2020-05-07 03:21:41 driver-btm-api.c:631:init_freq_mode: This is scan-user version
2020-05-07 03:21:41 driver-btm-api.c:1994:bitmain_soc_init: opt_multi_version = 1
2020-05-07 03:21:41 driver-btm-api.c:1995:bitmain_soc_init: opt_bitmain_ab = 1
2020-05-07 03:21:41 driver-btm-api.c:1996:bitmain_soc_init: opt_bitmain_work_mode = 0
2020-05-07 03:21:41 driver-btm-api.c:1997:bitmain_soc_init: Miner compile time: Tue Dec 24 16:13:07 CST 2019 type: Antminer T17
2020-05-07 03:21:41 driver-btm-api.c:1998:bitmain_soc_init: commit version: e93a09b 2019-12-24 16:03:45, build by: lol 2019-12-24 16:19:49
2020-05-07 03:21:41 driver-btm-api.c:1810:show_sn: no SN got, please write SN to /nvdata/sn
2020-05-07 03:21:41 driver-btm-api.c:1135:miner_device_init: Detect 256MB control board of XILINX
2020-05-07 03:21:41 driver-btm-api.c:1083:init_fan_parameter: fan_eft : 0 fan_pwm : 0
2020-05-07 03:21:41 thread.c:789:create_read_nonce_reg_thread: create thread
2020-05-07 03:21:47 driver-btm-api.c:1067:init_miner_version: miner ID : 8042750618c0885c
2020-05-07 03:21:47 driver-btm-api.c:1073:init_miner_version: FPGA Version = 0xB013
2020-05-07 03:21:49 eeprom.c:425:check_pattern_test_level: invalid pattern test result. ignore
2020-05-07 03:21:51 eeprom.c:425:check_pattern_test_level: invalid pattern test result. ignore
2020-05-07 03:21:51 driver-btm-api.c:705:get_product_id: product_id[0] = 1
2020-05-07 03:21:51 driver-btm-api.c:705:get_product_id: product_id[1] = 1
2020-05-07 03:21:51 driver-btm-api.c:1633:get_ccdly_opt: ccdly_opt[0] = 1
2020-05-07 03:21:51 driver-btm-api.c:1633:get_ccdly_opt: ccdly_opt[1] = 1
2020-05-07 03:21:51 driver-btm-api.c:1877:bitmain_board_init: g_ccdly_opt = 1
2020-05-07 03:21:51 driver-btm-api.c:644:_set_project_type: project:2
2020-05-07 03:21:51 driver-btm-api.c:674:_set_project_type: Project type: Antminer T17
2020-05-07 03:21:51 driver-btm-api.c:685:dump_pcb_bom_version: Chain [0] PCB Version: 0x0100
2020-05-07 03:21:51 driver-btm-api.c:686:dump_pcb_bom_version: Chain [0] BOM Version: 0x0100
2020-05-07 03:21:51 driver-btm-api.c:685:dump_pcb_bom_version: Chain [1] PCB Version: 0x0100
2020-05-07 03:21:51 driver-btm-api.c:686:dump_pcb_bom_version: Chain [1] BOM Version: 0x0100
2020-05-07 03:21:55 driver-btm-api.c:1897:bitmain_board_init: Fan check passed.
2020-05-07 03:21:57 board.c:36:jump_and_app_check_restore_pic: chain[0] PIC jump to app
2020-05-07 03:22:00 board.c:40:jump_and_app_check_restore_pic: Check chain[0] PIC fw version=0xb9
2020-05-07 03:22:02 board.c:36:jump_and_app_check_restore_pic: chain[1] PIC jump to app
2020-05-07 03:22:05 board.c:40:jump_and_app_check_restore_pic: Check chain[1] PIC fw version=0xb9
2020-05-07 03:22:05 thread.c:784:create_pic_heart_beat_thread: create thread
2020-05-07 03:22:05 power_api.c:55:power_init: power init ...
2020-05-07 03:22:05 driver-btm-api.c:1907:bitmain_board_init: Enter 30s sleep to make sure power release finish.
2020-05-07 03:22:05 power_api.c:46:power_off: init gpio907
2020-05-07 03:22:37 power_api.c:232:set_iic_power_to_highest_voltage: setting to voltage: 17.00 ...
2020-05-07 03:22:39 power_api.c:124:check_voltage_multi: retry time: 0
2020-05-07 03:22:41 power_api.c:86:get_average_voltage: chain[0], voltage is: 21.173496
2020-05-07 03:22:43 power_api.c:86:get_average_voltage: chain[1], voltage is: 20.420361
2020-05-07 03:22:43 power_api.c:97:get_average_voltage: aveage voltage is: 20.796928
2020-05-07 03:22:43 power_api.c:110:check_voltage: target_vol = 17.00, actural_vol = 20.80, more than 1.0v diff.
2020-05-07 03:22:44 power_api.c:124:check_voltage_multi: retry time: 1
2020-05-07 03:22:45 power_api.c:86:get_average_voltage: chain[0], voltage is: 19.416181
2020-05-07 03:22:47 power_api.c:86:get_average_voltage: chain[1], voltage is: 18.797754
2020-05-07 03:22:47 power_api.c:97:get_average_voltage: aveage voltage is: 19.106968
2020-05-07 03:22:47 power_api.c:110:check_voltage: target_vol = 17.00, actural_vol = 19.11, more than 1.0v diff.
2020-05-07 03:22:48 power_api.c:124:check_voltage_multi: retry time: 2
2020-05-07 03:22:50 power_api.c:86:get_average_voltage: chain[0], voltage is: 17.811943
2020-05-07 03:22:53 power_api.c:86:get_average_voltage: chain[1], voltage is: 16.868994
2020-05-07 03:22:53 power_api.c:97:get_average_voltage: aveage voltage is: 17.340469
2020-05-07 03:22:53 power_api.c:182:set_iic_power_by_voltage: now set voltage to : 17.000000
2020-05-07 03:22:53 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[0]: chip baud = 115200, chip_divider = 26
2020-05-07 03:22:53 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[1]: chip baud = 115200, chip_divider = 26
2020-05-07 03:22:54 uart.c:80:set_baud: set fpga_baud = 115200, fpga_divider = 26
2020-05-07 03:23:03 driver-btm-api.c:1010:check_asic_number_with_power_on: Chain[0]: find 30 asic, times 0
2020-05-07 03:23:13 driver-btm-api.c:1010:check_asic_number_with_power_on: Chain[1]: find 30 asic, times 0
2020-05-07 03:23:16 driver-btm-api.c:348:set_order_clock: chain[0]: set order clock, stragegy 3 clock_en=0x1
2020-05-07 03:23:16 driver-btm-api.c:348:set_order_clock: chain[1]: set order clock, stragegy 3 clock_en=0x1
2020-05-07 03:23:16 driver-hash-chip.c:490:set_clock_delay_control: core_data = 0xb4
2020-05-07 03:23:16 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[0]: chip baud = 3000000, chip_divider = 0
2020-05-07 03:23:16 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[1]: chip baud = 3000000, chip_divider = 0
2020-05-07 03:23:16 uart.c:80:set_baud: set fpga_baud = 3000000, fpga_divider = 0
2020-05-07 03:23:16 driver-btm-api.c:1660:check_clock_counter: freq 50 clock_counter_limit 6
2020-05-07 03:23:17 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[0]: chip baud = 115200, chip_divider = 26
2020-05-07 03:23:17 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[1]: chip baud = 115200, chip_divider = 26
2020-05-07 03:23:17 uart.c:80:set_baud: set fpga_baud = 115200, fpga_divider = 26
2020-05-07 03:23:17 voltage[0] = 1710
2020-05-07 03:23:17 voltage[1] = 1710
2020-05-07 03:23:17 power_api.c:140:set_working_voltage: working_voltage = 17.100000
2020-05-07 03:23:18 temperature.c:282:calibrate_temp_sensor_one_chain: Temperature sensor calibration: chain 0 success.
2020-05-07 03:23:19 temperature.c:282:calibrate_temp_sensor_one_chain: Temperature sensor calibration: chain 1 success.
2020-05-07 03:23:19 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[0]: chip baud = 6000000, chip_divider = 7
2020-05-07 03:23:19 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[1]: chip baud = 6000000, chip_divider = 7
2020-05-07 03:23:19 uart.c:80:set_baud: set fpga_baud = 6000000, fpga_divider = 3
2020-05-07 03:23:21 driver-btm-api.c:248:check_bringup_temp: Bring up temperature is 22
2020-05-07 03:23:21 thread.c:804:create_check_miner_status_thread: create thread
2020-05-07 03:23:21 thread.c:794:create_set_miner_status_thread: create thread
2020-05-07 03:23:21 driver-btm-api.c:581:calculate_timeout: dev->timeout = 392
2020-05-07 03:23:21 thread.c:779:create_temperature_monitor_thread: create thread
2020-05-07 03:23:21 freq_tuning.c:154:freq_tuning_get_max_freq: Max freq of tuning is 760
2020-05-07 03:23:21 power_api.c:379:slowly_set_iic_power_to_custom_voltage: slowly setting to voltage: 18.00 ...
2020-05-07 03:23:50 power_api.c:124:check_voltage_multi: retry time: 0
2020-05-07 03:23:51 power_api.c:86:get_average_voltage: chain[0], voltage is: 18.142588
2020-05-07 03:23:53 power_api.c:86:get_average_voltage: chain[1], voltage is: 18.118095
2020-05-07 03:23:53 power_api.c:97:get_average_voltage: aveage voltage is: 18.130342
2020-05-07 03:23:53 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 42 set refdiv: 2, fbdiv: 168, postdiv1: 7, postdiv2: 7, usr divider: 1
2020-05-07 03:23:53 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 50 set refdiv: 2, fbdiv: 168, postdiv1: 7, postdiv2: 6, usr divider: 1
2020-05-07 03:23:53 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 60 set refdiv: 2, fbdiv: 168, postdiv1: 7, postdiv2: 5, usr divider: 1
2020-05-07 03:23:53 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 75 set refdiv: 2, fbdiv: 168, postdiv1: 7, postdiv2: 4, usr divider: 1
2020-05-07 03:23:53 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 100 set refdiv: 2, fbdiv: 168, postdiv1: 7, postdiv2: 3, usr divider: 1
2020-05-07 03:23:54 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 150 set refdiv: 2, fbdiv: 168, postdiv1: 7, postdiv2: 2, usr divider: 1
2020-05-07 03:23:54 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 300 set refdiv: 2, fbdiv: 168, postdiv1: 7, postdiv2: 1, usr divider: 1
2020-05-07 03:23:54 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 350 set refdiv: 2, fbdiv: 168, postdiv1: 6, postdiv2: 1, usr divider: 1
2020-05-07 03:23:54 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 420 set refdiv: 2, fbdiv: 168, postdiv1: 5, postdiv2: 1, usr divider: 1
2020-05-07 03:23:54 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 525 set refdiv: 2, fbdiv: 168, postdiv1: 4, postdiv2: 1, usr divider: 1
2020-05-07 03:23:54 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 700 set refdiv: 2, fbdiv: 168, postdiv1: 3, postdiv2: 1, usr divider: 1
2020-05-07 03:23:54 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 41 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 7, usr divider: 1
2020-05-07 03:23:54 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 47 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 6, usr divider: 1
2020-05-07 03:23:54 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 57 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 5, usr divider: 1
2020-05-07 03:23:55 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 71 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 4, usr divider: 1
2020-05-07 03:23:55 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 95 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 3, usr divider: 1
2020-05-07 03:23:55 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 143 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 2, usr divider: 1
2020-05-07 03:23:55 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 287 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 1, usr divider: 1
2020-05-07 03:23:55 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 335 set refdiv: 2, fbdiv: 161, postdiv1: 6, postdiv2: 1, usr divider: 1
2020-05-07 03:23:55 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 402 set refdiv: 2, fbdiv: 161, postdiv1: 5, postdiv2: 1, usr divider: 1
2020-05-07 03:23:55 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 503 set refdiv: 2, fbdiv: 161, postdiv1: 4, postdiv2: 1, usr divider: 1
2020-05-07 03:23:55 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 670 set refdiv: 2, fbdiv: 161, postdiv1: 3, postdiv2: 1, usr divider: 1
2020-05-07 03:23:55 driver-btm-api.c:612:set_timeout: freq 700 final timeout=168
2020-05-07 03:23:55 power_api.c:397:slowly_set_iic_power_to_working_voltage: slowly setting to voltage: 17.10 ...
2020-05-07 03:24:24 power_api.c:124:check_voltage_multi: retry time: 0
2020-05-07 03:24:28 power_api.c:86:get_average_voltage: chain[0], voltage is: 17.211885
2020-05-07 03:24:31 power_api.c:86:get_average_voltage: chain[1], voltage is: 17.181269
2020-05-07 03:24:31 power_api.c:97:get_average_voltage: aveage voltage is: 17.196577
2020-05-07 03:24:31 frequency.c:540:get_current_min_freq: current min freq 670
2020-05-07 03:24:31 driver-btm-api.c:1660:check_clock_counter: freq 670 clock_counter_limit 85
2020-05-07 03:24:32 thread.c:799:create_check_system_status_thread: create thread
2020-05-07 03:24:33 driver-btm-api.c:2113:bitmain_soc_init: Init done!
2020-05-07 03:24:33 driver-btm-api.c:201:set_miner_status: STATUS_INIT
2020-05-07 03:24:38 driver-btm-api.c:201:set_miner_status: STATUS_OKAY
2020-05-07 03:24:47 driver-btm-api.c:1293:dhash_chip_send_job: Version num 4
2020-05-07 03:29:46 thread.c:422:is_zero_nonce_happened: chain_nonce[0] = 15323
2020-05-07 03:29:46 thread.c:422:is_zero_nonce_happened: chain_nonce[1] = 14616
2020-05-07 03:54:47 thread.c:204:calc_hashrate_avg: avg rate is 27676.36 in 29 mins
2020-05-07 03:54:47 temperature.c:450:temp_statistics_show: pcb temp 44~56 chip temp 67~80
2020-05-07 04:24:48 thread.c:204:calc_hashrate_avg: avg rate is 27736.35 in 30 mins
2020-05-07 04:24:48 temperature.c:450:temp_statistics_show: pcb temp 44~56 chip temp 67~80
2020-05-07 04:54:49 thread.c:204:calc_hashrate_avg: avg rate is 27372.68 in 30 mins
2020-05-07 04:54:49 temperature.c:450:temp_statistics_show: pcb temp 45~56 chip temp 67~80
2020-05-07 05:24:50 thread.c:204:calc_hashrate_avg: avg rate is 27682.71 in 30 mins
2020-05-07 05:24:50 temperature.c:450:temp_statistics_show: pcb temp 45~56 chip temp 67~80
2020-05-07 05:54:51 thread.c:204:calc_hashrate_avg: avg rate is 27730.27 in 30 mins
2020-05-07 05:54:51 temperature.c:450:temp_statistics_show: pcb temp 45~56 chip temp 67~80
2020-05-07 06:24:52 thread.c:204:calc_hashrate_avg: avg rate is 27587.18 in 30 mins
2020-05-07 06:24:52 temperature.c:450:temp_statistics_show: pcb temp 45~56 chip temp 67~80
2020-05-07 06:54:53 thread.c:204:calc_hashrate_avg: avg rate is 27575.03 in 30 mins
2020-05-07 06:54:53 temperature.c:450:temp_statistics_show: pcb temp 45~56 chip temp 68~80
2020-05-07 07:24:54 thread.c:204:calc_hashrate_avg: avg rate is 27445.78 in 30 mins
2020-05-07 07:24:54 temperature.c:450:temp_statistics_show: pcb temp 45~56 chip temp 67~80
2020-05-07 07:54:54 thread.c:204:calc_hashrate_avg: avg rate is 27814.17 in 30 mins
2020-05-07 07:54:54 temperature.c:450:temp_statistics_show: pcb temp 45~56 chip temp 68~80
2020-05-07 08:24:55 thread.c:204:calc_hashrate_avg: avg rate is 27621.68 in 30 mins
2020-05-07 08:24:55 temperature.c:450:temp_statistics_show: pcb temp 45~56 chip temp 68~80
2020-05-07 08:54:56 thread.c:204:calc_hashrate_avg: avg rate is 27537.58 in 30 mins
2020-05-07 08:54:56 temperature.c:450:temp_statistics_show: pcb temp 45~57 chip temp 68~80
2020-05-07 09:24:57 thread.c:204:calc_hashrate_avg: avg rate is 27614.20 in 30 mins
2020-05-07 09:24:57 temperature.c:450:temp_statistics_show: pcb temp 45~56 chip temp 68~80
2020-05-07 09:54:58 thread.c:204:calc_hashrate_avg: avg rate is 27766.82 in 30 mins
2020-05-07 09:54:58 temperature.c:450:temp_statistics_show: pcb temp 45~56 chip temp 68~80
2020-05-07 10:24:59 thread.c:204:calc_hashrate_avg: avg rate is 27521.63 in 30 mins
2020-05-07 10:24:59 temperature.c:450:temp_statistics_show: pcb temp 45~56 chip temp 68~80
2020-05-07 10:55:00 thread.c:204:calc_hashrate_avg: avg rate is 27584.10 in 30 mins
2020-05-07 10:55:00 temperature.c:450:temp_statistics_show: pcb temp 45~56 chip temp 68~80
2020-05-07 11:25:01 thread.c:204:calc_hashrate_avg: avg rate is 27534.69 in 30 mins
2020-05-07 11:25:01 temperature.c:450:temp_statistics_show: pcb temp 45~56 chip temp 68~80
2020-05-07 11:55:02 thread.c:204:calc_hashrate_avg: avg rate is 27889.86 in 30 mins
2020-05-07 11:55:02 temperature.c:450:temp_statistics_show: pcb temp 45~56 chip temp 68~81
2020-05-07 12:25:03 thread.c:204:calc_hashrate_avg: avg rate is 27751.13 in 30 mins
2020-05-07 12:25:03 temperature.c:450:temp_statistics_show: pcb temp 45~57 chip temp 68~81
2020-05-07 12:55:04 thread.c:204:calc_hashrate_avg: avg rate is 27353.70 in 30 mins
2020-05-07 12:55:04 temperature.c:450:temp_statistics_show: pcb temp 45~56 chip temp 68~80
2020-05-07 13:25:05 thread.c:204:calc_hashrate_avg: avg rate is 27620.71 in 30 mins
2020-05-07 13:25:05 temperature.c:450:temp_statistics_show: pcb temp 45~56 chip temp 68~80
2020-05-07 13:55:06 thread.c:204:calc_hashrate_avg: avg rate is 27397.21 in 30 mins
2020-05-07 13:55:06 temperature.c:450:temp_statistics_show: pcb temp 45~56 chip temp 68~80
2020-05-07 14:25:07 thread.c:204:calc_hashrate_avg: avg rate is 27671.73 in 30 mins
2020-05-07 14:25:07 temperature.c:450:temp_statistics_show: pcb temp 45~57 chip temp 68~80
2020-05-07 14:55:08 thread.c:204:calc_hashrate_avg: avg rate is 27487.33 in 30 mins
2020-05-07 14:55:08 temperature.c:450:temp_statistics_show: pcb temp 45~56 chip temp 68~80
2020-05-07 15:25:09 thread.c:204:calc_hashrate_avg: avg rate is 27426.67 in 30 mins
2020-05-07 15:25:09 temperature.c:450:temp_statistics_show: pcb temp 45~56 chip temp 68~80
Miner Status Screen: https://drive.google.com/file/d/1e3O_gmv7yX_vPT0KGWFxJLt0LzlWGNot/view?usp=sharing Jacob
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: mysticbitcoin on May 07, 2020, 04:50:29 PM
1. The Kernel Log does look pretty different. No bad messages regarding temperature and such. So it's pointing to the Hashboard. 2. Back to the Original/PSU and problem Hashboard plugged in. The Kernal Log looks to have some of the re-occuring error messages. Too soon to for temperature messages, will let it run and post later. Funny thing is the Hashboard now recognizes all 30 chips and is running. Hashboard (Chain[2]) is operating a little higher now at a hashrate 60% of normal. As always it is showing all "oooo"'s for the chip status when the board does run. Very Strange and inconsistent when it works and doesn't but the errors and symptoms are the same. Kernel Log: Booting Linux on physical CPU 0x0
Linux version 4.6.0-xilinx-gff8137b-dirty (lzq@armdev2) (gcc version 4.8.3 20140320 (prerelease) (Sourcery CodeBench Lite 2014.05-23) ) #25 SMP PREEMPT Fri Nov 23 15:30:52 CST 2018
CPU: ARMv7 Processor [413fc090] revision 0 (ARMv7), cr=18c5387d
CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
Machine model: Xilinx Zynq
cma: Reserved 16 MiB at 0x0e000000
Memory policy: Data cache writealloc
On node 0 totalpages: 61440
free_area_init_node: node 0, pgdat c0b39280, node_mem_map cde10000
Normal zone: 480 pages used for memmap
Normal zone: 0 pages reserved
Normal zone: 61440 pages, LIFO batch:15
percpu: Embedded 12 pages/cpu @cddf1000 s19776 r8192 d21184 u49152
pcpu-alloc: s19776 r8192 d21184 u49152 alloc=12*4096
pcpu-alloc: [0] 0 [0] 1
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 60960
Kernel command line: mem=240M console=ttyPS0,115200 ramdisk_size=33554432 root=/dev/ram rw earlyprintk
PID hash table entries: 1024 (order: 0, 4096 bytes)
Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
Memory: 203756K/245760K available (6345K kernel code, 231K rwdata, 1896K rodata, 1024K init, 223K bss, 25620K reserved, 16384K cma-reserved, 0K highmem)
Virtual kernel memory layout:
vector : 0xffff0000 - 0xffff1000 ( 4 kB)
fixmap : 0xffc00000 - 0xfff00000 (3072 kB)
vmalloc : 0xcf800000 - 0xff800000 ( 768 MB)
lowmem : 0xc0000000 - 0xcf000000 ( 240 MB)
pkmap : 0xbfe00000 - 0xc0000000 ( 2 MB)
modules : 0xbf000000 - 0xbfe00000 ( 14 MB)
.text : 0xc0008000 - 0xc090c424 (9234 kB)
.init : 0xc0a00000 - 0xc0b00000 (1024 kB)
.data : 0xc0b00000 - 0xc0b39fe0 ( 232 kB)
.bss : 0xc0b39fe0 - 0xc0b71c28 ( 224 kB)
Preemptible hierarchical RCU implementation.
Build-time adjustment of leaf fanout to 32.
RCU restricting CPUs from NR_CPUS=4 to nr_cpu_ids=2.
RCU: Adjusting geometry for rcu_fanout_leaf=32, nr_cpu_ids=2
NR_IRQS:16 nr_irqs:16 16
efuse mapped to cf800000
ps7-slcr mapped to cf802000
L2C: platform modifies aux control register: 0x72360000 -> 0x72760000
L2C: DT/platform modifies aux control register: 0x72360000 -> 0x72760000
L2C-310 erratum 769419 enabled
L2C-310 enabling early BRESP for Cortex-A9
L2C-310 full line of zeros enabled for Cortex-A9
L2C-310 ID prefetch enabled, offset 1 lines
L2C-310 dynamic clock gating enabled, standby mode enabled
L2C-310 cache controller enabled, 8 ways, 512 kB
L2C-310: CACHE_ID 0x410000c8, AUX_CTRL 0x76760001
zynq_clock_init: clkc starts at cf802100
Zynq clock init
sched_clock: 64 bits at 333MHz, resolution 3ns, wraps every 4398046511103ns
clocksource: arm_global_timer: mask: 0xffffffffffffffff max_cycles: 0x4ce07af025, max_idle_ns: 440795209040 ns
Switching to timer-based delay loop, resolution 3ns
clocksource: ttc_clocksource: mask: 0xffff max_cycles: 0xffff, max_idle_ns: 537538477 ns
ps7-ttc #0 at cf80a000, irq=18
Console: colour dummy device 80x30
Calibrating delay loop (skipped), value calculated using timer frequency.. 666.66 BogoMIPS (lpj=3333333)
pid_max: default: 32768 minimum: 301
Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
CPU: Testing write buffer coherency: ok
CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
Setting up static identity map for 0x100000 - 0x100058
CPU1: failed to boot: -1
Brought up 1 CPUs
SMP: Total of 1 processors activated (666.66 BogoMIPS).
CPU: All CPU(s) started in SVC mode.
devtmpfs: initialized
VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4
clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
pinctrl core: initialized pinctrl subsystem
NET: Registered protocol family 16
DMA: preallocated 256 KiB pool for atomic coherent allocations
cpuidle: using governor menu
hw-breakpoint: found 5 (+1 reserved) breakpoint and 1 watchpoint registers.
hw-breakpoint: maximum watchpoint size is 4 bytes.
zynq-ocm f800c000.ps7-ocmc: ZYNQ OCM pool: 256 KiB @ 0xcf880000
vgaarb: loaded
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
media: Linux media interface: v0.10
Linux video capture interface: v2.00
pps_core: LinuxPPS API ver. 1 registered
pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
PTP clock support registered
EDAC MC: Ver: 3.0.0
Advanced Linux Sound Architecture Driver Initialized.
clocksource: Switched to clocksource arm_global_timer
NET: Registered protocol family 2
TCP established hash table entries: 2048 (order: 1, 8192 bytes)
TCP bind hash table entries: 2048 (order: 2, 16384 bytes)
TCP: Hash tables configured (established 2048 bind 2048)
UDP hash table entries: 256 (order: 1, 8192 bytes)
UDP-Lite hash table entries: 256 (order: 1, 8192 bytes)
NET: Registered protocol family 1
RPC: Registered named UNIX socket transport module.
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
PCI: CLS 0 bytes, default 64
Trying to unpack rootfs image as initramfs...
rootfs image is not initramfs (no cpio magic); looks like an initrd
Freeing initrd memory: 12580K (cceb8000 - cdb01000)
hw perfevents: enabled with armv7_cortex_a9 PMU driver, 7 counters available
futex hash table entries: 512 (order: 3, 32768 bytes)
workingset: timestamp_bits=28 max_order=16 bucket_order=0
jffs2: version 2.2. (NAND) (SUMMARY) © 2001-2006 Red Hat, Inc.
io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered (default)
dma-pl330 f8003000.ps7-dma: Loaded driver for PL330 DMAC-241330
dma-pl330 f8003000.ps7-dma: DBUFF-128x8bytes Num_Chans-8 Num_Peri-4 Num_Events-16
e0000000.serial: ttyPS0 at MMIO 0xe0000000 (irq = 158, base_baud = 6249999) is a xuartps
console [ttyPS0] enabled
xdevcfg f8007000.ps7-dev-cfg: ioremap 0xf8007000 to cf86e000
[drm] Initialized drm 1.1.0 20060810
brd: module loaded
loop: module loaded
CAN device driver interface
gpiod_set_value: invalid GPIO
libphy: MACB_mii_bus: probed
macb e000b000.ethernet eth0: Cadence GEM rev 0x00020118 at 0xe000b000 irq 31 (00:0a:35:00:00:00)
Generic PHY e000b000.etherne:00: attached PHY driver [Generic PHY] (mii_bus:phy_addr=e000b000.etherne:00, irq=-1)
e1000e: Intel(R) PRO/1000 Network Driver - 3.2.6-k
e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
ehci-pci: EHCI PCI platform driver
usbcore: registered new interface driver usb-storage
mousedev: PS/2 mouse device common for all mice
i2c /dev entries driver
Xilinx Zynq CpuIdle Driver started
sdhci: Secure Digital Host Controller Interface driver
sdhci: Copyright(c) Pierre Ossman
sdhci-pltfm: SDHCI platform and OF driver helper
mmc0: SDHCI controller on e0100000.ps7-sdio [e0100000.ps7-sdio] using ADMA
ledtrig-cpu: registered to indicate activity on CPUs
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
nand: device found, Manufacturer ID: 0x2c, Chip ID: 0xda
nand: Micron MT29F2G08ABAGAWP
nand: 256 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 128
nand: WARNING: pl35x-nand: the ECC used on your system is too weak compared to the one required by the NAND chip
Bad block table found at page 131008, version 0x01
Bad block table found at page 130944, version 0x01
6 ofpart partitions found on MTD device pl35x-nand
Creating 6 MTD partitions on "pl35x-nand":
0x000000000000-0x000002800000 : "BOOT.bin-env-dts-kernel"
0x000002800000-0x000004800000 : "ramfs"
0x000004800000-0x000005000000 : "configs"
0x000005000000-0x000006000000 : "reserve"
0x000006000000-0x000008000000 : "ramfs-bak"
0x000008000000-0x000010000000 : "reserve1"
NET: Registered protocol family 10
sit: IPv6 over IPv4 tunneling driver
NET: Registered protocol family 17
can: controller area network core (rev 20120528 abi 9)
NET: Registered protocol family 29
can: raw protocol (rev 20120528)
can: broadcast manager protocol (rev 20120528 t)
can: netlink gateway (rev 20130117) max_hops=1
zynq_pm_ioremap: no compatible node found for 'xlnx,zynq-ddrc-a05'
zynq_pm_late_init: Unable to map DDRC IO memory.
Registering SWP/SWPB emulation handler
hctosys: unable to open rtc device (rtc0)
ALSA device list:
No soundcards found.
RAMDISK: gzip image found at block 0
EXT4-fs (ram0): couldn't mount as ext3 due to feature incompatibilities
EXT4-fs (ram0): mounted filesystem without journal. Opts: (null)
VFS: Mounted root (ext4 filesystem) on device 1:0.
devtmpfs: mounted
Freeing unused kernel memory: 1024K (c0a00000 - c0b00000)
EXT4-fs (ram0): re-mounted. Opts: block_validity,delalloc,barrier,user_xattr
random: dd urandom read with 0 bits of entropy available
ubi0: attaching mtd2
ubi0: scanning is finished
ubi0: attached mtd2 (name "configs", size 8 MiB)
ubi0: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
ubi0: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
ubi0: VID header offset: 2048 (aligned 2048), data offset: 4096
ubi0: good PEBs: 64, bad PEBs: 0, corrupted PEBs: 0
ubi0: user volume: 1, internal volumes: 1, max. volumes count: 128
ubi0: max/mean erase counter: 6/3, WL threshold: 4096, image sequence number: 4244297529
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 01559AD8-7B6A-42E6-A3FE-EDF3659527A9, 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: 1054/342, WL threshold: 4096, image sequence number: 4185749592
ubi1: available PEBs: 0, total reserved PEBs: 1020, PEBs reserved for bad PEB handling: 36
ubi1: background thread "ubi_bgt1d" started, PID 720
UBIFS (ubi1:0): background thread "ubifs_bgt1_0" started, PID 723
UBIFS (ubi1:0): recovery needed
UBIFS (ubi1:0): recovery completed
UBIFS (ubi1:0): UBIFS: mounted UBI device 1, volume 0, name "reserve1"
UBIFS (ubi1:0): LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
UBIFS (ubi1:0): FS size: 123039744 bytes (117 MiB, 969 LEBs), journal size 6221824 bytes (5 MiB, 49 LEBs)
UBIFS (ubi1:0): reserved for root: 4952683 bytes (4836 KiB)
UBIFS (ubi1:0): media format: w4/r0 (latest is w4/r0), UUID 4829CF2C-7435-4146-B2FD-0826AAE8443A, small LPT model
IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
macb e000b000.ethernet eth0: unable to generate target frequency: 25000000 Hz
macb e000b000.ethernet eth0: link up (100/Full)
IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
In axi fpga driver!
request_mem_region OK!
AXI fpga dev virtual address is 0xcfb38000
*base_vir_addr = 0xab013
In fpga mem driver!
request_mem_region OK!
fpga mem virtual address is 0xd2000000
random: nonblocking pool is initialized
2020-05-07 16:31:51 driver-btm-api.c:631:init_freq_mode: This is scan-user version
2020-05-07 16:31:51 driver-btm-api.c:1994:bitmain_soc_init: opt_multi_version = 1
2020-05-07 16:31:51 driver-btm-api.c:1995:bitmain_soc_init: opt_bitmain_ab = 1
2020-05-07 16:31:51 driver-btm-api.c:1996:bitmain_soc_init: opt_bitmain_work_mode = 0
2020-05-07 16:31:51 driver-btm-api.c:1997:bitmain_soc_init: Miner compile time: Tue Dec 24 16:13:07 CST 2019 type: Antminer T17
2020-05-07 16:31:51 driver-btm-api.c:1998:bitmain_soc_init: commit version: e93a09b 2019-12-24 16:03:45, build by: lol 2019-12-24 16:19:49
2020-05-07 16:31:51 driver-btm-api.c:1810:show_sn: no SN got, please write SN to /nvdata/sn
2020-05-07 16:31:51 driver-btm-api.c:1135:miner_device_init: Detect 256MB control board of XILINX
2020-05-07 16:31:51 driver-btm-api.c:1083:init_fan_parameter: fan_eft : 0 fan_pwm : 0
2020-05-07 16:31:51 thread.c:789:create_read_nonce_reg_thread: create thread
2020-05-07 16:31:57 driver-btm-api.c:1067:init_miner_version: miner ID : 8042750618c0885c
2020-05-07 16:31:57 driver-btm-api.c:1073:init_miner_version: FPGA Version = 0xB013
2020-05-07 16:31:58 eeprom.c:425:check_pattern_test_level: invalid pattern test result. ignore
2020-05-07 16:32:00 eeprom.c:425:check_pattern_test_level: invalid pattern test result. ignore
2020-05-07 16:32:02 eeprom.c:425:check_pattern_test_level: invalid pattern test result. ignore
2020-05-07 16:32:02 driver-btm-api.c:705:get_product_id: product_id[0] = 1
2020-05-07 16:32:02 driver-btm-api.c:705:get_product_id: product_id[1] = 1
2020-05-07 16:32:02 driver-btm-api.c:705:get_product_id: product_id[2] = 1
2020-05-07 16:32:02 driver-btm-api.c:1633:get_ccdly_opt: ccdly_opt[0] = 1
2020-05-07 16:32:02 driver-btm-api.c:1633:get_ccdly_opt: ccdly_opt[1] = 1
2020-05-07 16:32:02 driver-btm-api.c:1633:get_ccdly_opt: ccdly_opt[2] = 1
2020-05-07 16:32:02 driver-btm-api.c:1877:bitmain_board_init: g_ccdly_opt = 1
2020-05-07 16:32:02 driver-btm-api.c:644:_set_project_type: project:2
2020-05-07 16:32:02 driver-btm-api.c:674:_set_project_type: Project type: Antminer T17
2020-05-07 16:32:02 driver-btm-api.c:685:dump_pcb_bom_version: Chain [0] PCB Version: 0x0100
2020-05-07 16:32:02 driver-btm-api.c:686:dump_pcb_bom_version: Chain [0] BOM Version: 0x0100
2020-05-07 16:32:02 driver-btm-api.c:685:dump_pcb_bom_version: Chain [1] PCB Version: 0x0100
2020-05-07 16:32:02 driver-btm-api.c:686:dump_pcb_bom_version: Chain [1] BOM Version: 0x0100
2020-05-07 16:32:02 driver-btm-api.c:685:dump_pcb_bom_version: Chain [2] PCB Version: 0x0100
2020-05-07 16:32:02 driver-btm-api.c:686:dump_pcb_bom_version: Chain [2] BOM Version: 0x0100
2020-05-07 16:32:04 driver-btm-api.c:1897:bitmain_board_init: Fan check passed.
2020-05-07 16:32:04 register.c:283:get_register: !!! reg crc error
2020-05-07 16:32:06 board.c:36:jump_and_app_check_restore_pic: chain[0] PIC jump to app
2020-05-07 16:32:09 board.c:40:jump_and_app_check_restore_pic: Check chain[0] PIC fw version=0xb9
2020-05-07 16:32:11 board.c:36:jump_and_app_check_restore_pic: chain[1] PIC jump to app
2020-05-07 16:32:15 board.c:40:jump_and_app_check_restore_pic: Check chain[1] PIC fw version=0xb9
2020-05-07 16:32:16 board.c:36:jump_and_app_check_restore_pic: chain[2] PIC jump to app
2020-05-07 16:32:20 board.c:40:jump_and_app_check_restore_pic: Check chain[2] PIC fw version=0xb9
2020-05-07 16:32:20 thread.c:784:create_pic_heart_beat_thread: create thread
2020-05-07 16:32:20 power_api.c:55:power_init: power init ...
2020-05-07 16:32:20 driver-btm-api.c:1907:bitmain_board_init: Enter 30s sleep to make sure power release finish.
2020-05-07 16:32:52 power_api.c:232:set_iic_power_to_highest_voltage: setting to voltage: 17.00 ...
2020-05-07 16:32:57 power_api.c:124:check_voltage_multi: retry time: 0
2020-05-07 16:32:59 power_api.c:86:get_average_voltage: chain[0], voltage is: 17.928281
2020-05-07 16:33:01 power_api.c:86:get_average_voltage: chain[1], voltage is: 17.352715
2020-05-07 16:33:03 power_api.c:86:get_average_voltage: chain[2], voltage is: 17.211885
2020-05-07 16:33:03 power_api.c:97:get_average_voltage: aveage voltage is: 17.497627
2020-05-07 16:33:03 power_api.c:182:set_iic_power_by_voltage: now set voltage to : 17.000000
2020-05-07 16:33:03 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[0]: chip baud = 115200, chip_divider = 26
2020-05-07 16:33:03 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[1]: chip baud = 115200, chip_divider = 26
2020-05-07 16:33:03 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[2]: chip baud = 115200, chip_divider = 26
2020-05-07 16:33:03 uart.c:80:set_baud: set fpga_baud = 115200, fpga_divider = 26
2020-05-07 16:33:14 driver-btm-api.c:1010:check_asic_number_with_power_on: Chain[0]: find 30 asic, times 0
2020-05-07 16:33:24 driver-btm-api.c:1010:check_asic_number_with_power_on: Chain[1]: find 30 asic, times 0
2020-05-07 16:33:34 driver-btm-api.c:1010:check_asic_number_with_power_on: Chain[2]: find 30 asic, times 0
2020-05-07 16:33:38 driver-btm-api.c:348:set_order_clock: chain[0]: set order clock, stragegy 3 clock_en=0x1
2020-05-07 16:33:38 driver-btm-api.c:348:set_order_clock: chain[1]: set order clock, stragegy 3 clock_en=0x1
2020-05-07 16:33:38 driver-btm-api.c:348:set_order_clock: chain[2]: set order clock, stragegy 3 clock_en=0x1
2020-05-07 16:33:38 driver-hash-chip.c:490:set_clock_delay_control: core_data = 0xb4
2020-05-07 16:33:39 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[0]: chip baud = 3000000, chip_divider = 0
2020-05-07 16:33:39 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[1]: chip baud = 3000000, chip_divider = 0
2020-05-07 16:33:39 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[2]: chip baud = 3000000, chip_divider = 0
2020-05-07 16:33:39 uart.c:80:set_baud: set fpga_baud = 3000000, fpga_divider = 0
2020-05-07 16:33:39 driver-btm-api.c:1660:check_clock_counter: freq 50 clock_counter_limit 6
2020-05-07 16:33:39 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[0]: chip baud = 115200, chip_divider = 26
2020-05-07 16:33:39 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[1]: chip baud = 115200, chip_divider = 26
2020-05-07 16:33:39 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[2]: chip baud = 115200, chip_divider = 26
2020-05-07 16:33:39 uart.c:80:set_baud: set fpga_baud = 115200, fpga_divider = 26
2020-05-07 16:33:39 voltage[0] = 1710
2020-05-07 16:33:39 voltage[1] = 1710
2020-05-07 16:33:39 voltage[2] = 1710
2020-05-07 16:33:39 power_api.c:140:set_working_voltage: working_voltage = 17.100000
2020-05-07 16:33:41 temperature.c:282:calibrate_temp_sensor_one_chain: Temperature sensor calibration: chain 0 success.
2020-05-07 16:33:42 temperature.c:282:calibrate_temp_sensor_one_chain: Temperature sensor calibration: chain 1 success.
2020-05-07 16:33:43 temperature.c:282:calibrate_temp_sensor_one_chain: Temperature sensor calibration: chain 2 success.
2020-05-07 16:33:43 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[0]: chip baud = 6000000, chip_divider = 7
2020-05-07 16:33:43 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[1]: chip baud = 6000000, chip_divider = 7
2020-05-07 16:33:43 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[2]: chip baud = 6000000, chip_divider = 7
2020-05-07 16:33:43 uart.c:80:set_baud: set fpga_baud = 6000000, fpga_divider = 3
2020-05-07 16:33:45 driver-btm-api.c:248:check_bringup_temp: Bring up temperature is 17
2020-05-07 16:33:45 thread.c:804:create_check_miner_status_thread: create thread
2020-05-07 16:33:45 thread.c:794:create_set_miner_status_thread: create thread
2020-05-07 16:33:45 driver-btm-api.c:581:calculate_timeout: dev->timeout = 392
2020-05-07 16:33:45 thread.c:779:create_temperature_monitor_thread: create thread
2020-05-07 16:33:45 freq_tuning.c:154:freq_tuning_get_max_freq: Max freq of tuning is 760
2020-05-07 16:33:45 power_api.c:379:slowly_set_iic_power_to_custom_voltage: slowly setting to voltage: 18.00 ...
2020-05-07 16:34:17 power_api.c:124:check_voltage_multi: retry time: 0
2020-05-07 16:34:19 power_api.c:86:get_average_voltage: chain[0], voltage is: 18.142588
2020-05-07 16:34:21 power_api.c:86:get_average_voltage: chain[1], voltage is: 18.124219
2020-05-07 16:34:23 power_api.c:86:get_average_voltage: chain[2], voltage is: 18.234433
2020-05-07 16:34:23 power_api.c:97:get_average_voltage: aveage voltage is: 18.167080
2020-05-07 16:34:23 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 42 set refdiv: 2, fbdiv: 168, postdiv1: 7, postdiv2: 7, usr divider: 1
2020-05-07 16:34:23 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 50 set refdiv: 2, fbdiv: 168, postdiv1: 7, postdiv2: 6, usr divider: 1
2020-05-07 16:34:23 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 60 set refdiv: 2, fbdiv: 168, postdiv1: 7, postdiv2: 5, usr divider: 1
2020-05-07 16:34:23 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 75 set refdiv: 2, fbdiv: 168, postdiv1: 7, postdiv2: 4, usr divider: 1
2020-05-07 16:34:23 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 100 set refdiv: 2, fbdiv: 168, postdiv1: 7, postdiv2: 3, usr divider: 1
2020-05-07 16:34:23 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 150 set refdiv: 2, fbdiv: 168, postdiv1: 7, postdiv2: 2, usr divider: 1
2020-05-07 16:34:23 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 300 set refdiv: 2, fbdiv: 168, postdiv1: 7, postdiv2: 1, usr divider: 1
2020-05-07 16:34:24 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 350 set refdiv: 2, fbdiv: 168, postdiv1: 6, postdiv2: 1, usr divider: 1
2020-05-07 16:34:24 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 420 set refdiv: 2, fbdiv: 168, postdiv1: 5, postdiv2: 1, usr divider: 1
2020-05-07 16:34:24 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 525 set refdiv: 2, fbdiv: 168, postdiv1: 4, postdiv2: 1, usr divider: 1
2020-05-07 16:34:24 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 700 set refdiv: 2, fbdiv: 168, postdiv1: 3, postdiv2: 1, usr divider: 1
2020-05-07 16:34:24 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 41 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 7, usr divider: 1
2020-05-07 16:34:24 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 47 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 6, usr divider: 1
2020-05-07 16:34:24 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 57 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 5, usr divider: 1
2020-05-07 16:34:24 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 71 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 4, usr divider: 1
2020-05-07 16:34:24 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 95 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 3, usr divider: 1
2020-05-07 16:34:24 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 143 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 2, usr divider: 1
2020-05-07 16:34:25 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 287 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 1, usr divider: 1
2020-05-07 16:34:25 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 335 set refdiv: 2, fbdiv: 161, postdiv1: 6, postdiv2: 1, usr divider: 1
2020-05-07 16:34:25 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 402 set refdiv: 2, fbdiv: 161, postdiv1: 5, postdiv2: 1, usr divider: 1
2020-05-07 16:34:25 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 503 set refdiv: 2, fbdiv: 161, postdiv1: 4, postdiv2: 1, usr divider: 1
2020-05-07 16:34:25 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 670 set refdiv: 2, fbdiv: 161, postdiv1: 3, postdiv2: 1, usr divider: 1
2020-05-07 16:34:25 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 41 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 7, usr divider: 1
2020-05-07 16:34:25 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 47 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 6, usr divider: 1
2020-05-07 16:34:25 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 57 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 5, usr divider: 1
2020-05-07 16:34:25 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 71 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 4, usr divider: 1
2020-05-07 16:34:26 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 95 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 3, usr divider: 1
2020-05-07 16:34:26 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 143 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 2, usr divider: 1
2020-05-07 16:34:26 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 287 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 1, usr divider: 1
2020-05-07 16:34:26 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 335 set refdiv: 2, fbdiv: 161, postdiv1: 6, postdiv2: 1, usr divider: 1
2020-05-07 16:34:26 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 402 set refdiv: 2, fbdiv: 161, postdiv1: 5, postdiv2: 1, usr divider: 1
2020-05-07 16:34:26 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 503 set refdiv: 2, fbdiv: 161, postdiv1: 4, postdiv2: 1, usr divider: 1
2020-05-07 16:34:26 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 670 set refdiv: 2, fbdiv: 161, postdiv1: 3, postdiv2: 1, usr divider: 1
2020-05-07 16:34:26 driver-btm-api.c:612:set_timeout: freq 700 final timeout=168
2020-05-07 16:34:26 power_api.c:146:set_higher_voltage: higher_voltage = 18.000000
2020-05-07 16:34:26 power_api.c:428:slowly_set_iic_power_to_higher_voltage: slowly setting to voltage: 18.00 ...
2020-05-07 16:34:51 power_api.c:124:check_voltage_multi: retry time: 0
2020-05-07 16:34:52 power_api.c:86:get_average_voltage: chain[0], voltage is: 18.130342
2020-05-07 16:34:54 power_api.c:86:get_average_voltage: chain[1], voltage is: 18.099726
2020-05-07 16:34:56 power_api.c:86:get_average_voltage: chain[2], voltage is: 18.185449
2020-05-07 16:34:56 power_api.c:97:get_average_voltage: aveage voltage is: 18.138506
2020-05-07 16:34:56 frequency.c:540:get_current_min_freq: current min freq 670
2020-05-07 16:34:56 driver-btm-api.c:1660:check_clock_counter: freq 670 clock_counter_limit 85
2020-05-07 16:34:56 register.c:966:register_process_asic_response: Get another asic response: chain = 2, asic = 26
2020-05-07 16:34:56 register.c:1416:quick_dump_core_hash_clock_counter: bad clock counter. chain = 0, asic = 5, core = 1, found 1, clock counter 0x00000000
2020-05-07 16:34:56 driver-btm-api.c:2097:bitmain_soc_init: clock count check failed after retry, wait for hash rate protect later.
2020-05-07 16:34:56 thread.c:799:create_check_system_status_thread: create thread
2020-05-07 16:34:57 driver-btm-api.c:2113:bitmain_soc_init: Init done!
2020-05-07 16:34:57 driver-btm-api.c:201:set_miner_status: STATUS_INIT
2020-05-07 16:35:01 register.c:290:get_register: !!! REG_TYPE = 1. 1084936194
2020-05-07 16:35:02 register.c:290:get_register: !!! REG_TYPE = 1. 1090506754
2020-05-07 16:35:02 register.c:290:get_register: !!! REG_TYPE = 1. 1090506754
2020-05-07 16:35:02 driver-btm-api.c:201:set_miner_status: STATUS_OKAY
2020-05-07 16:35:07 driver-btm-api.c:1293:dhash_chip_send_job: Version num 4
2020-05-07 16:35:12 thread.c:382:check_working_voltage: current PCB min temperature is 41
2020-05-07 16:35:12 thread.c:383:check_working_voltage: current voltage is 18.00V, recovery to 17.10V
2020-05-07 16:35:12 power_api.c:397:slowly_set_iic_power_to_working_voltage: slowly setting to voltage: 17.10 ...
2020-05-07 16:35:50 power_api.c:124:check_voltage_multi: retry time: 0
2020-05-07 16:35:51 power_api.c:86:get_average_voltage: chain[0], voltage is: 17.187392
2020-05-07 16:35:53 power_api.c:86:get_average_voltage: chain[1], voltage is: 17.162900
2020-05-07 16:35:55 power_api.c:86:get_average_voltage: chain[2], voltage is: 17.279238
2020-05-07 16:35:55 power_api.c:97:get_average_voltage: aveage voltage is: 17.209844
Miner Status Screen: https://drive.google.com/file/d/1kXmiaOT-iP8L2mvQ9IGNY_JJVskctpEs/view?usp=sharing Again Error Messages to note that didn't show up when the Hashboard in question (Chain [2]) was plugged in: 2020-05-07 16:34:56 register.c:966:register_process_asic_response: Get another asic response: chain = 2, asic = 26
2020-05-07 16:34:56 register.c:1416:quick_dump_core_hash_clock_counter: bad clock counter. chain = 0, asic = 5, core = 1, found 1, clock counter 0x00000000
2020-05-07 16:34:56 driver-btm-api.c:2097:bitmain_soc_init: clock count check failed after retry, wait for hash rate protect later.
2020-05-07 16:35:01 register.c:290:get_register: !!! REG_TYPE = 1. 1084936194
2020-05-07 16:35:02 register.c:290:get_register: !!! REG_TYPE = 1. 1090506754
2020-05-07 16:35:02 register.c:290:get_register: !!! REG_TYPE = 1. 1090506754
Jacob
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: mikeywith on May 07, 2020, 10:35:40 PM
This, without a doubt, is a bad hashboard, and by the way, boards showing 0 ASICs or anything less than what it should show (In this case 30 Asics) it's pretty normal to show all ASICs at some point, either after a reboot or when you move the board, here is a fun fact, many S9s boards I attempted to fix showed all Asics when I put the board on the table in a horizontal way, where the chips are sitting on the table, the moment I place them back in the miner vertically "standing", the board starts to act, sometimes it does mine well for a few days/weeks and then collapses again, sometimes by applying some pressure on the heatsinks I got some hashboards to work.
What you can conclude from the above is that some heatsinks/chips don't have perfect contact with the body of the hash board, so when they are cold, they seem to stick and contact, the board works, but when it gets hot, the heatsink/chip lose contact and errors start to show, in some cases and for whatever reason, the heatsink/chip does stick by itself and never show any errors again, but in most cases, it's only a matter of time till either the heatsink falls off the hashboard simply give you the same error.
So now my guess is that some chips/heatsinks on the hashboards are not in good contact, this is a common problem, in fact if you read the report coming in from the Chinese miners, one of the most common problem is what you are having now. If you want to investigate even further, you can buy Fluke 15b + f15b + (https://www.zeusbtc.com/RepairDetails.asp?ID=99), you can find it on Amazon too, but since you are going to be using the repair guide (https://www.zeusbtc.com/NewsDetails.asp?ID=187) from zeusbtc, maybe it's a good idea to support them, but that's up to you of course, for now, you don't need the repair tools they sell, you can simply measure the resistance with the board unplugged, one or more chips will show some weird numbers, that will be a bad chip which needs replacement.
Replacing the chips is a whole different topic, but it's pretty doable if you have the tools, so if you plan on taking mining seriously and stacking more Bitmain gears, then it might be a good investment to buy all those tools, if not then just mine on with the board until it rest in peace.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: mysticbitcoin on May 08, 2020, 01:53:41 AM
Mikeywith, I'm fully committed and I would like to try to fix it myself. I don't mind supporting zeusbtc, does their platform work for the latest Bitmain products as well? I've used soldering equipment before and have the will do to hot air. Kernel Log: ** SAME AS Prior Post - Deleted due to Forum Posting Limits **
2020-05-07 16:40:54 thread.c:422:is_zero_nonce_happened: chain_nonce[0] = 17862
2020-05-07 16:40:54 thread.c:422:is_zero_nonce_happened: chain_nonce[1] = 16993
2020-05-07 16:40:54 thread.c:422:is_zero_nonce_happened: chain_nonce[2] = 9242
2020-05-07 16:40:54 thread.c:478:clear_zero_nonce_mark: 0 nonce protect succeed.
2020-05-07 17:05:55 thread.c:204:calc_hashrate_avg: avg rate is 34688.48 in 30 mins
2020-05-07 17:05:55 temperature.c:450:temp_statistics_show: pcb temp 40~56 chip temp 63~84
2020-05-07 17:05:55 thread.c:285:check_hashrate: latest avg rate < 0.98......
2020-05-07 17:05:55 thread.c:286:check_hashrate: current PCB min temperature 40
2020-05-07 17:05:55 thread.c:287:check_hashrate: current voltage is 17.10V, working voltage is 17.10V
2020-05-07 17:05:55 thread.c:318:check_hashrate: high temp, increase voltage 0.1V/0.2V to 17.20V
2020-05-07 17:05:55 driver-btm-api.c:2124:bitmain_reopen_core: reopen_core start!
2020-05-07 17:06:01 driver-btm-api.c:1067:init_miner_version: miner ID : 8042750618c0885c
2020-05-07 17:06:01 driver-btm-api.c:1073:init_miner_version: FPGA Version = 0xB013
2020-05-07 17:06:01 chain = 0, mode = 0, load_done = false.
2020-05-07 17:06:01 chain = 1, mode = 0, load_done = false.
2020-05-07 17:06:01 chain = 2, mode = 0, load_done = false.
2020-05-07 17:06:02 chain = 0, mode = 0, load_done = false.
2020-05-07 17:06:02 chain = 1, mode = 0, load_done = false.
2020-05-07 17:06:02 chain = 2, mode = 0, load_done = false.
2020-05-07 17:06:03 eeprom.c:425:check_pattern_test_level: invalid pattern test result. ignore
2020-05-07 17:06:03 chain = 0, mode = 0, load_done = false.
2020-05-07 17:06:03 chain = 1, mode = 0, load_done = false.
2020-05-07 17:06:03 chain = 2, mode = 0, load_done = false.
2020-05-07 17:06:04 chain = 0, mode = 0, load_done = false.
2020-05-07 17:06:04 chain = 1, mode = 0, load_done = false.
2020-05-07 17:06:04 chain = 2, mode = 0, load_done = false.
2020-05-07 17:06:05 eeprom.c:425:check_pattern_test_level: invalid pattern test result. ignore
2020-05-07 17:06:05 chain = 0, mode = 0, load_done = false.
2020-05-07 17:06:05 chain = 1, mode = 0, load_done = false.
2020-05-07 17:06:05 chain = 2, mode = 0, load_done = false.
2020-05-07 17:06:06 chain = 0, mode = 0, load_done = false.
2020-05-07 17:06:06 chain = 1, mode = 0, load_done = false.
2020-05-07 17:06:06 chain = 2, mode = 0, load_done = false.
2020-05-07 17:06:07 eeprom.c:425:check_pattern_test_level: invalid pattern test result. ignore
2020-05-07 17:06:07 driver-btm-api.c:705:get_product_id: product_id[0] = 1
2020-05-07 17:06:07 driver-btm-api.c:705:get_product_id: product_id[1] = 1
2020-05-07 17:06:07 driver-btm-api.c:705:get_product_id: product_id[2] = 1
2020-05-07 17:06:07 driver-btm-api.c:1633:get_ccdly_opt: ccdly_opt[0] = 1
2020-05-07 17:06:07 driver-btm-api.c:1633:get_ccdly_opt: ccdly_opt[1] = 1
2020-05-07 17:06:07 driver-btm-api.c:1633:get_ccdly_opt: ccdly_opt[2] = 1
2020-05-07 17:06:07 driver-btm-api.c:1877:bitmain_board_init: g_ccdly_opt = 1
2020-05-07 17:06:07 driver-btm-api.c:644:_set_project_type: project:2
2020-05-07 17:06:07 driver-btm-api.c:674:_set_project_type: Project type: Antminer T17
2020-05-07 17:06:07 driver-btm-api.c:685:dump_pcb_bom_version: Chain [0] PCB Version: 0x0100
2020-05-07 17:06:07 driver-btm-api.c:686:dump_pcb_bom_version: Chain [0] BOM Version: 0x0100
2020-05-07 17:06:07 driver-btm-api.c:685:dump_pcb_bom_version: Chain [1] PCB Version: 0x0100
2020-05-07 17:06:07 driver-btm-api.c:686:dump_pcb_bom_version: Chain [1] BOM Version: 0x0100
2020-05-07 17:06:07 driver-btm-api.c:685:dump_pcb_bom_version: Chain [2] PCB Version: 0x0100
2020-05-07 17:06:07 driver-btm-api.c:686:dump_pcb_bom_version: Chain [2] BOM Version: 0x0100
2020-05-07 17:06:09 driver-btm-api.c:1897:bitmain_board_init: Fan check passed.
2020-05-07 17:06:10 register.c:283:get_register: !!! reg crc error
2020-05-07 17:06:12 board.c:36:jump_and_app_check_restore_pic: chain[0] PIC jump to app
2020-05-07 17:06:15 board.c:40:jump_and_app_check_restore_pic: Check chain[0] PIC fw version=0xb9
2020-05-07 17:06:17 board.c:36:jump_and_app_check_restore_pic: chain[1] PIC jump to app
2020-05-07 17:06:21 board.c:40:jump_and_app_check_restore_pic: Check chain[1] PIC fw version=0xb9
2020-05-07 17:06:24 board.c:36:jump_and_app_check_restore_pic: chain[2] PIC jump to app
2020-05-07 17:06:30 board.c:40:jump_and_app_check_restore_pic: Check chain[2] PIC fw version=0xb9
2020-05-07 17:06:30 power_api.c:55:power_init: power init ...
2020-05-07 17:06:30 driver-btm-api.c:1907:bitmain_board_init: Enter 30s sleep to make sure power release finish.
2020-05-07 17:07:02 power_api.c:232:set_iic_power_to_highest_voltage: setting to voltage: 17.00 ...
2020-05-07 17:07:04 power_api.c:124:check_voltage_multi: retry time: 0
2020-05-07 17:07:05 power_api.c:86:get_average_voltage: chain[0], voltage is: 17.199638
2020-05-07 17:07:07 power_api.c:86:get_average_voltage: chain[1], voltage is: 17.107793
2020-05-07 17:07:09 power_api.c:86:get_average_voltage: chain[2], voltage is: 17.211885
2020-05-07 17:07:09 power_api.c:97:get_average_voltage: aveage voltage is: 17.173105
2020-05-07 17:07:09 power_api.c:182:set_iic_power_by_voltage: now set voltage to : 17.000000
2020-05-07 17:07:09 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[0]: chip baud = 115200, chip_divider = 26
2020-05-07 17:07:09 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[1]: chip baud = 115200, chip_divider = 26
2020-05-07 17:07:09 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[2]: chip baud = 115200, chip_divider = 26
2020-05-07 17:07:09 uart.c:80:set_baud: set fpga_baud = 115200, fpga_divider = 26
2020-05-07 17:07:19 driver-btm-api.c:1010:check_asic_number_with_power_on: Chain[0]: find 29 asic, times 0
2020-05-07 17:07:29 driver-btm-api.c:1010:check_asic_number_with_power_on: Chain[0]: find 30 asic, times 1
2020-05-07 17:07:39 driver-btm-api.c:1010:check_asic_number_with_power_on: Chain[1]: find 30 asic, times 0
2020-05-07 17:07:49 driver-btm-api.c:1010:check_asic_number_with_power_on: Chain[2]: find 30 asic, times 0
2020-05-07 17:07:53 driver-btm-api.c:348:set_order_clock: chain[0]: set order clock, stragegy 3 clock_en=0x1
2020-05-07 17:07:53 driver-btm-api.c:348:set_order_clock: chain[1]: set order clock, stragegy 3 clock_en=0x1
2020-05-07 17:07:53 driver-btm-api.c:348:set_order_clock: chain[2]: set order clock, stragegy 3 clock_en=0x1
2020-05-07 17:07:54 driver-hash-chip.c:490:set_clock_delay_control: core_data = 0xb4
2020-05-07 17:07:54 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[0]: chip baud = 3000000, chip_divider = 0
2020-05-07 17:07:54 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[1]: chip baud = 3000000, chip_divider = 0
2020-05-07 17:07:54 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[2]: chip baud = 3000000, chip_divider = 0
2020-05-07 17:07:54 uart.c:80:set_baud: set fpga_baud = 3000000, fpga_divider = 0
2020-05-07 17:07:54 driver-btm-api.c:1660:check_clock_counter: freq 50 clock_counter_limit 6
2020-05-07 17:07:54 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[0]: chip baud = 115200, chip_divider = 26
2020-05-07 17:07:54 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[1]: chip baud = 115200, chip_divider = 26
2020-05-07 17:07:54 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[2]: chip baud = 115200, chip_divider = 26
2020-05-07 17:07:54 uart.c:80:set_baud: set fpga_baud = 115200, fpga_divider = 26
2020-05-07 17:07:54 voltage[0] = 1710
2020-05-07 17:07:54 voltage[1] = 1710
2020-05-07 17:07:54 voltage[2] = 1710
2020-05-07 17:07:54 power_api.c:140:set_working_voltage: working_voltage = 17.100000
2020-05-07 17:07:56 temperature.c:282:calibrate_temp_sensor_one_chain: Temperature sensor calibration: chain 0 success.
2020-05-07 17:07:57 temperature.c:282:calibrate_temp_sensor_one_chain: Temperature sensor calibration: chain 1 success.
2020-05-07 17:07:58 temperature.c:282:calibrate_temp_sensor_one_chain: Temperature sensor calibration: chain 2 success.
2020-05-07 17:07:58 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[0]: chip baud = 6000000, chip_divider = 7
2020-05-07 17:07:58 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[1]: chip baud = 6000000, chip_divider = 7
2020-05-07 17:07:58 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[2]: chip baud = 6000000, chip_divider = 7
2020-05-07 17:07:58 uart.c:80:set_baud: set fpga_baud = 6000000, fpga_divider = 3
2020-05-07 17:08:00 driver-btm-api.c:248:check_bringup_temp: Bring up temperature is 18
2020-05-07 17:08:00 driver-btm-api.c:581:calculate_timeout: dev->timeout = 392
2020-05-07 17:08:00 power_api.c:379:slowly_set_iic_power_to_custom_voltage: slowly setting to voltage: 18.00 ...
2020-05-07 17:08:36 power_api.c:124:check_voltage_multi: retry time: 0
2020-05-07 17:08:38 power_api.c:86:get_average_voltage: chain[0], voltage is: 18.142588
2020-05-07 17:08:40 power_api.c:86:get_average_voltage: chain[1], voltage is: 18.118095
2020-05-07 17:08:41 power_api.c:86:get_average_voltage: chain[2], voltage is: 18.228310
2020-05-07 17:08:41 power_api.c:97:get_average_voltage: aveage voltage is: 18.162998
2020-05-07 17:08:41 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 42 set refdiv: 2, fbdiv: 168, postdiv1: 7, postdiv2: 7, usr divider: 1
2020-05-07 17:08:42 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 50 set refdiv: 2, fbdiv: 168, postdiv1: 7, postdiv2: 6, usr divider: 1
2020-05-07 17:08:42 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 60 set refdiv: 2, fbdiv: 168, postdiv1: 7, postdiv2: 5, usr divider: 1
2020-05-07 17:08:42 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 75 set refdiv: 2, fbdiv: 168, postdiv1: 7, postdiv2: 4, usr divider: 1
2020-05-07 17:08:42 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 100 set refdiv: 2, fbdiv: 168, postdiv1: 7, postdiv2: 3, usr divider: 1
2020-05-07 17:08:42 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 150 set refdiv: 2, fbdiv: 168, postdiv1: 7, postdiv2: 2, usr divider: 1
2020-05-07 17:08:42 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 300 set refdiv: 2, fbdiv: 168, postdiv1: 7, postdiv2: 1, usr divider: 1
2020-05-07 17:08:42 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 350 set refdiv: 2, fbdiv: 168, postdiv1: 6, postdiv2: 1, usr divider: 1
2020-05-07 17:08:42 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 420 set refdiv: 2, fbdiv: 168, postdiv1: 5, postdiv2: 1, usr divider: 1
2020-05-07 17:08:42 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 525 set refdiv: 2, fbdiv: 168, postdiv1: 4, postdiv2: 1, usr divider: 1
2020-05-07 17:08:42 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 700 set refdiv: 2, fbdiv: 168, postdiv1: 3, postdiv2: 1, usr divider: 1
2020-05-07 17:08:43 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 41 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 7, usr divider: 1
2020-05-07 17:08:43 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 47 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 6, usr divider: 1
2020-05-07 17:08:43 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 57 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 5, usr divider: 1
2020-05-07 17:08:43 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 71 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 4, usr divider: 1
2020-05-07 17:08:43 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 95 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 3, usr divider: 1
2020-05-07 17:08:43 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 143 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 2, usr divider: 1
2020-05-07 17:08:43 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 287 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 1, usr divider: 1
2020-05-07 17:08:43 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 335 set refdiv: 2, fbdiv: 161, postdiv1: 6, postdiv2: 1, usr divider: 1
2020-05-07 17:08:43 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 402 set refdiv: 2, fbdiv: 161, postdiv1: 5, postdiv2: 1, usr divider: 1
2020-05-07 17:08:43 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 503 set refdiv: 2, fbdiv: 161, postdiv1: 4, postdiv2: 1, usr divider: 1
2020-05-07 17:08:44 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 670 set refdiv: 2, fbdiv: 161, postdiv1: 3, postdiv2: 1, usr divider: 1
2020-05-07 17:08:44 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 41 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 7, usr divider: 1
2020-05-07 17:08:44 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 47 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 6, usr divider: 1
2020-05-07 17:08:44 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 57 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 5, usr divider: 1
2020-05-07 17:08:44 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 71 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 4, usr divider: 1
2020-05-07 17:08:44 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 95 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 3, usr divider: 1
2020-05-07 17:08:44 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 143 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 2, usr divider: 1
2020-05-07 17:08:44 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 287 set refdiv: 2, fbdiv: 161, postdiv1: 7, postdiv2: 1, usr divider: 1
2020-05-07 17:08:44 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 335 set refdiv: 2, fbdiv: 161, postdiv1: 6, postdiv2: 1, usr divider: 1
2020-05-07 17:08:45 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 402 set refdiv: 2, fbdiv: 161, postdiv1: 5, postdiv2: 1, usr divider: 1
2020-05-07 17:08:45 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 503 set refdiv: 2, fbdiv: 161, postdiv1: 4, postdiv2: 1, usr divider: 1
2020-05-07 17:08:45 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 670 set refdiv: 2, fbdiv: 161, postdiv1: 3, postdiv2: 1, usr divider: 1
2020-05-07 17:08:45 driver-btm-api.c:612:set_timeout: freq 700 final timeout=168
2020-05-07 17:08:45 power_api.c:146:set_higher_voltage: higher_voltage = 18.000000
2020-05-07 17:08:45 power_api.c:428:slowly_set_iic_power_to_higher_voltage: slowly setting to voltage: 18.00 ...
2020-05-07 17:09:09 power_api.c:124:check_voltage_multi: retry time: 0
2020-05-07 17:09:11 power_api.c:86:get_average_voltage: chain[0], voltage is: 18.111972
2020-05-07 17:09:13 power_api.c:86:get_average_voltage: chain[1], voltage is: 18.099726
2020-05-07 17:09:15 power_api.c:86:get_average_voltage: chain[2], voltage is: 18.209941
2020-05-07 17:09:15 power_api.c:97:get_average_voltage: aveage voltage is: 18.140547
2020-05-07 17:09:15 driver-btm-api.c:2186:bitmain_reopen_core: reopen_core done!
2020-05-07 17:09:15 power_api.c:379:slowly_set_iic_power_to_custom_voltage: slowly setting to voltage: 17.20 ...
2020-05-07 17:09:16 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 0
2020-05-07 17:09:16 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 2, chip = 184, reg = 28, got chain = 2, chip = 109, reg = 226
2020-05-07 17:09:17 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 1
2020-05-07 17:09:18 register.c:290:get_register: !!! REG_TYPE = 1. 718332418
2020-05-07 17:09:19 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 0
2020-05-07 17:09:20 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 1
2020-05-07 17:09:22 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 2, chip = 184, reg = 28, got chain = 2, chip = 230, reg = 1
2020-05-07 17:09:23 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 0
2020-05-07 17:09:23 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 1
2020-05-07 17:09:26 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 0
2020-05-07 17:09:26 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 1
2020-05-07 17:09:29 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 0
2020-05-07 17:09:29 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 1
2020-05-07 17:09:40 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 0
2020-05-07 17:09:40 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 1
2020-05-07 17:09:42 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 0
2020-05-07 17:09:42 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 1
2020-05-07 17:09:55 power_api.c:124:check_voltage_multi: retry time: 0
2020-05-07 17:09:56 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 0
2020-05-07 17:09:56 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 1
2020-05-07 17:09:57 power_api.c:86:get_average_voltage: chain[0], voltage is: 17.260869
2020-05-07 17:09:59 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 0
2020-05-07 17:09:59 register.c:290:get_register: !!! REG_TYPE = 1. 1634862082
2020-05-07 17:09:59 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 1
2020-05-07 17:09:59 power_api.c:86:get_average_voltage: chain[1], voltage is: 17.254746
2020-05-07 17:10:00 register.c:290:get_register: !!! REG_TYPE = 1. 962365698
2020-05-07 17:10:01 power_api.c:86:get_average_voltage: chain[2], voltage is: 17.358838
2020-05-07 17:10:01 power_api.c:97:get_average_voltage: aveage voltage is: 17.291484
2020-05-07 17:10:01 power_api.c:140:set_working_voltage: working_voltage = 17.200001
2020-05-07 17:10:01 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 2, chip = 184, reg = 28, got chain = 2, chip = 184, reg = 140
2020-05-07 17:10:02 register.c:290:get_register: !!! REG_TYPE = 1. 1219239938
2020-05-07 17:10:02 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 0
2020-05-07 17:10:02 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 1
2020-05-07 17:10:05 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 0
2020-05-07 17:10:05 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 1
2020-05-07 17:10:08 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 2, chip = 184, reg = 28, got chain = 2, chip = 0, reg = 34
2020-05-07 17:10:08 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 0
2020-05-07 17:10:08 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 1
2020-05-07 17:10:11 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 0
2020-05-07 17:10:11 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 1
2020-05-07 17:10:14 register.c:290:get_register: !!! REG_TYPE = 1. 1024805634
2020-05-07 17:10:14 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 0
2020-05-07 17:10:14 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 1
2020-05-07 17:10:17 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 0
2020-05-07 17:10:17 register.c:290:get_register: !!! REG_TYPE = 1. 2118170626
2020-05-07 17:10:17 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 1
2020-05-07 17:10:20 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 0
2020-05-07 17:10:20 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 2, chip = 184, reg = 28, got chain = 2, chip = 0, reg = 128
2020-05-07 17:10:20 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 1
2020-05-07 17:10:23 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 0
2020-05-07 17:10:24 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 1
2020-05-07 17:10:27 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 0
2020-05-07 17:10:27 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 1
2020-05-07 17:15:00 thread.c:422:is_zero_nonce_happened: chain_nonce[0] = 112336
2020-05-07 17:15:00 thread.c:422:is_zero_nonce_happened: chain_nonce[1] = 107640
2020-05-07 17:15:00 thread.c:422:is_zero_nonce_happened: chain_nonce[2] = 55208
2020-05-07 17:40:01 thread.c:204:calc_hashrate_avg: avg rate is 32945.16 in 30 mins
2020-05-07 17:40:01 temperature.c:450:temp_statistics_show: pcb temp 42~56 chip temp 61~80
2020-05-07 17:40:01 thread.c:285:check_hashrate: latest avg rate < 0.98......
2020-05-07 17:40:01 thread.c:286:check_hashrate: current PCB min temperature 42
2020-05-07 17:40:01 thread.c:287:check_hashrate: current voltage is 17.20V, working voltage is 17.20V
2020-05-07 17:40:01 thread.c:312:check_hashrate: high temp, voltage has already increased 0.1V/0.2V
** Deleted to meet Forum Posting Limit - Same as above but with temperature of 42 to 43 **
2020-05-07 19:45:47 register.c:290:get_register: !!! REG_TYPE = 1. 564257026
2020-05-07 19:45:50 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 0
2020-05-07 19:45:50 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 2, chip = 184, reg = 28, got chain = 2, chip = 144, reg = 131
2020-05-07 19:45:50 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 1
2020-05-07 19:45:53 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 0
2020-05-07 19:45:53 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 1
2020-05-07 19:45:56 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 0
2020-05-07 19:45:56 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 1
2020-05-07 19:45:58 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 0
2020-05-07 19:45:59 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 1
2020-05-07 19:46:01 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 0
2020-05-07 19:46:01 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 1
2020-05-07 19:46:04 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 0
2020-05-07 19:46:04 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 1
2020-05-07 19:46:07 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 0
2020-05-07 19:46:07 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 1
2020-05-07 19:46:09 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 0
2020-05-07 19:46:10 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 1
2020-05-07 19:46:12 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 2, chip = 184, reg = 28, got chain = 2, chip = 191, reg = 134
2020-05-07 19:46:12 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 2, chip = 184, reg = 28, got chain = 2, chip = 105, reg = 123
2020-05-07 19:46:12 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 0
2020-05-07 19:46:13 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 1
2020-05-07 19:46:15 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 0
2020-05-07 19:46:15 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 1
2020-05-07 19:46:18 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 0
2020-05-07 19:46:18 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 1
2020-05-07 19:46:21 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 0
2020-05-07 19:46:21 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 1
2020-05-07 19:46:23 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 2, chip = 184, reg = 28, got chain = 2, chip = 254, reg = 128
2020-05-07 19:46:23 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 0
2020-05-07 19:46:24 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 1
2020-05-07 19:46:26 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 0
2020-05-07 19:46:26 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 1
2020-05-07 19:46:29 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 2, chip = 184, reg = 28, got chain = 2, chip = 106, reg = 56
2020-05-07 19:46:29 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 0
2020-05-07 19:46:29 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 1
2020-05-07 19:46:32 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 0
2020-05-07 19:46:32 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 1
2020-05-07 19:46:34 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 0
2020-05-07 19:46:35 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 1
2020-05-07 19:46:37 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 2, chip = 184, reg = 28, got chain = 2, chip = 10, reg = 232
2020-05-07 19:46:37 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 0
2020-05-07 19:46:37 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 1
2020-05-07 19:46:40 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 0
2020-05-07 19:46:40 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 1
2020-05-07 19:46:43 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 0
2020-05-07 19:46:43 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 1
2020-05-07 19:46:45 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 0
2020-05-07 19:46:46 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 1
2020-05-07 19:46:48 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 2, chip = 184, reg = 28, got chain = 2, chip = 161, reg = 213
2020-05-07 19:46:48 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 0
2020-05-07 19:46:48 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 1
2020-05-07 19:46:51 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 0
2020-05-07 19:46:51 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 2, chip = 184, reg = 28, got chain = 2, chip = 38, reg = 65
2020-05-07 19:46:51 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 1
2020-05-07 19:46:54 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 0
2020-05-07 19:46:54 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 1
2020-05-07 19:46:57 register.c:290:get_register: !!! REG_TYPE = 1. 2146941442
2020-05-07 19:46:57 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 0
2020-05-07 19:46:57 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 1
2020-05-07 19:47:00 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 0
2020-05-07 19:47:00 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 2, chip = 184, reg = 28, got chain = 2, chip = 156, reg = 208
2020-05-07 19:47:00 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 1
2020-05-07 19:47:02 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 0
2020-05-07 19:47:02 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 1
2020-05-07 19:47:05 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 0
2020-05-07 19:47:05 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 2, chip = 184, reg = 28, got chain = 2, chip = 16, reg = 212
2020-05-07 19:47:05 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 1
2020-05-07 19:47:08 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 0
2020-05-07 19:47:08 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 1
2020-05-07 19:47:11 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 0
2020-05-07 19:47:11 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 1
2020-05-07 19:47:13 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 0
2020-05-07 19:47:14 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 1
2020-05-07 19:47:16 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 0
2020-05-07 19:47:16 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 1
2020-05-07 19:47:19 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 0
2020-05-07 19:47:19 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 1
2020-05-07 19:47:22 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 0
2020-05-07 19:47:22 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 1
2020-05-07 19:47:24 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 0
2020-05-07 19:47:24 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 1
2020-05-07 19:47:27 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 0
2020-05-07 19:47:27 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 2, chip = 184, reg = 28, got chain = 2, chip = 219, reg = 153
2020-05-07 19:47:27 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 1
2020-05-07 19:47:30 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 0
2020-05-07 19:47:30 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 2, chip = 184, reg = 28, got chain = 2, chip = 30, reg = 93
2020-05-07 19:47:30 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 1
2020-05-07 19:47:33 register.c:290:get_register: !!! REG_TYPE = 1. 1381375234
2020-05-07 19:47:33 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 0
2020-05-07 19:47:33 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 1
2020-05-07 19:47:35 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 2, chip = 184, reg = 28, got chain = 2, chip = 140, reg = 183
2020-05-07 19:47:35 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 0
2020-05-07 19:47:35 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 1
2020-05-07 19:47:38 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 0
2020-05-07 19:47:38 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 1
2020-05-07 19:47:41 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 2, chip = 184, reg = 28, got chain = 2, chip = 16, reg = 132
2020-05-07 19:47:41 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 0
2020-05-07 19:47:41 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 1
2020-05-07 19:47:43 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 0
2020-05-07 19:47:44 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 1
2020-05-07 19:47:46 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 2, chip = 184, reg = 28, got chain = 2, chip = 5, reg = 8
2020-05-07 19:47:46 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 0
2020-05-07 19:47:46 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 1
2020-05-07 19:47:49 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 0
2020-05-07 19:47:49 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 1
2020-05-07 19:47:52 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 0
2020-05-07 19:47:52 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 1
2020-05-07 19:47:54 register.c:290:get_register: !!! REG_TYPE = 1. 1090715650
2020-05-07 19:47:54 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 0
2020-05-07 19:47:54 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 1
2020-05-07 19:47:57 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 0
2020-05-07 19:47:57 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 1
2020-05-07 19:48:00 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 0
2020-05-07 19:48:00 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 1
2020-05-07 19:48:03 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 0
2020-05-07 19:48:03 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 1
2020-05-07 19:48:05 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 0
2020-05-07 19:48:05 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 1
2020-05-07 19:48:08 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 0
2020-05-07 19:48:08 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 1
2020-05-07 19:48:11 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 0
2020-05-07 19:48:11 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 1
2020-05-07 19:48:14 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 0
2020-05-07 19:48:14 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 2, chip = 184, reg = 28, got chain = 2, chip = 81, reg = 152
2020-05-07 19:48:14 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 1
2020-05-07 19:48:16 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 0
2020-05-07 19:48:16 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 1
2020-05-07 19:48:19 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 0
2020-05-07 19:48:19 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 2, chip = 184, reg = 28, got chain = 2, chip = 6, reg = 105
2020-05-07 19:48:19 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 1
2020-05-07 19:48:22 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 0
2020-05-07 19:48:22 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 1
2020-05-07 19:48:25 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 2, chip = 184, reg = 28, got chain = 2, chip = 0, reg = 0
2020-05-07 19:48:25 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 0
2020-05-07 19:48:25 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 2, chip = 184, reg = 28, got chain = 2, chip = 167, reg = 87
2020-05-07 19:48:25 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 1
2020-05-07 19:48:27 register.c:290:get_register: !!! REG_TYPE = 1. 1610716674
2020-05-07 19:48:27 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 0
2020-05-07 19:48:28 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 2, chip = 184, reg = 28, got chain = 2, chip = 176, reg = 245
2020-05-07 19:48:28 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 1
2020-05-07 19:48:30 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 2, chip = 184, reg = 28, got chain = 2, chip = 137, reg = 3
2020-05-07 19:48:30 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 0
2020-05-07 19:48:30 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 1
2020-05-07 19:48:33 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 0
2020-05-07 19:48:33 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 1
2020-05-07 19:48:36 register.c:290:get_register: !!! REG_TYPE = 1. 1811939330
2020-05-07 19:48:36 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 0
2020-05-07 19:48:36 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 1
2020-05-07 19:48:39 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 0
2020-05-07 19:48:39 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 1
2020-05-07 19:48:41 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 0
2020-05-07 19:48:41 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 1
2020-05-07 19:48:44 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 0
2020-05-07 19:48:44 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 1
2020-05-07 19:48:47 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 0
2020-05-07 19:48:47 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 1
2020-05-07 19:48:50 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 0
2020-05-07 19:48:50 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 1
2020-05-07 19:48:52 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 0
2020-05-07 19:48:53 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 1
2020-05-07 19:48:55 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 0
2020-05-07 19:48:55 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 1
2020-05-07 19:48:58 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 0
2020-05-07 19:48:58 register.c:290:get_register: !!! REG_TYPE = 1. 536901890
2020-05-07 19:48:58 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 1
2020-05-07 19:49:01 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 0
2020-05-07 19:49:01 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 1
2020-05-07 19:49:03 register.c:290:get_register: !!! REG_TYPE = 1. 1627249410
2020-05-07 19:49:04 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 0
2020-05-07 19:49:04 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 1
2020-05-07 19:49:06 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 0
2020-05-07 19:49:06 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 2, chip = 184, reg = 28, got chain = 2, chip = 216, reg = 28
2020-05-07 19:49:07 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 1
2020-05-07 19:49:09 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 2, chip = 184, reg = 28, got chain = 2, chip = 94, reg = 45
2020-05-07 19:49:09 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 0
2020-05-07 19:49:09 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 1
2020-05-07 19:49:12 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 0
2020-05-07 19:49:12 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 1
2020-05-07 19:49:14 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 0
2020-05-07 19:49:15 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 1
2020-05-07 19:49:17 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 0
2020-05-07 19:49:17 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 1
2020-05-07 19:49:20 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 2, chip = 184, reg = 28, got chain = 2, chip = 184, reg = 140
2020-05-07 19:49:20 register.c:290:get_register: !!! REG_TYPE = 1. 1179097602
2020-05-07 19:49:20 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 0
2020-05-07 19:49:20 register.c:290:get_register: !!! REG_TYPE = 1. 1996685314
2020-05-07 19:49:20 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 1
2020-05-07 19:49:23 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 0
2020-05-07 19:49:23 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 1
2020-05-07 19:49:26 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 0
2020-05-07 19:49:26 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 1
2020-05-07 19:49:28 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 0
2020-05-07 19:49:28 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 2, chip = 184, reg = 28, got chain = 2, chip = 184, reg = 140
2020-05-07 19:49:28 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 1
2020-05-07 19:49:31 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 0
2020-05-07 19:49:31 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 1
2020-05-07 19:49:34 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 0
2020-05-07 19:49:34 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 2, chip = 184, reg = 28, got chain = 2, chip = 64, reg = 255
2020-05-07 19:49:34 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 1
2020-05-07 19:49:37 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 0
2020-05-07 19:49:37 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 1
2020-05-07 19:49:39 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 0
2020-05-07 19:49:40 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 1
2020-05-07 19:49:42 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 0
2020-05-07 19:49:42 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 1
2020-05-07 19:49:45 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 0
2020-05-07 19:49:45 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 1
2020-05-07 19:49:48 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 0
2020-05-07 19:49:48 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 1
2020-05-07 19:49:51 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 0
2020-05-07 19:49:51 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 1
2020-05-07 19:49:53 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 0
2020-05-07 19:49:54 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 1
2020-05-07 19:49:56 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 0
2020-05-07 19:49:56 register.c:290:get_register: !!! REG_TYPE = 1. 914804994
2020-05-07 19:49:56 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 1
2020-05-07 19:49:59 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 0
2020-05-07 19:49:59 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 1
2020-05-07 19:50:02 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 0
2020-05-07 19:50:02 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 1
2020-05-07 19:50:05 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 2, chip = 184, reg = 28, got chain = 2, chip = 147, reg = 93
2020-05-07 19:50:05 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 2, chip = 184, reg = 28, got chain = 2, chip = 135, reg = 107
2020-05-07 19:50:05 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 0
2020-05-07 19:50:05 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 1
2020-05-07 19:50:08 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 0
2020-05-07 19:50:08 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 1
2020-05-07 19:50:10 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 0
2020-05-07 19:50:11 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 1
2020-05-07 19:50:13 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 0
2020-05-07 19:50:13 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 2, chip = 184, reg = 28, got chain = 2, chip = 125, reg = 216
2020-05-07 19:50:14 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 1
2020-05-07 19:50:16 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 2, chip = 184, reg = 28, got chain = 2, chip = 49, reg = 130
2020-05-07 19:50:16 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 0
2020-05-07 19:50:16 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 1
2020-05-07 19:50:19 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 0
2020-05-07 19:50:19 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 1
2020-05-07 19:50:22 register.c:290:get_register: !!! REG_TYPE = 1. 1879154946
2020-05-07 19:50:22 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 0
2020-05-07 19:50:22 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 2, chip = 184, reg = 28, got chain = 2, chip = 44, reg = 227
2020-05-07 19:50:22 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 2, chip = 184, reg = 28, got chain = 2, chip = 17, reg = 188
2020-05-07 19:50:22 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 2, chip = 184, reg = 28, got chain = 2, chip = 19, reg = 30
2020-05-07 19:50:22 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 1
2020-05-07 19:50:25 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 2, chip = 184, reg = 28, got chain = 2, chip = 25, reg = 131
2020-05-07 19:50:25 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 0
2020-05-07 19:50:25 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 2, chip = 184, reg = 28, got chain = 2, chip = 26, reg = 86
2020-05-07 19:50:25 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 1
2020-05-07 19:50:28 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 0
2020-05-07 19:50:28 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 1
2020-05-07 19:50:31 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 2, chip = 184, reg = 28, got chain = 2, chip = 144, reg = 1
2020-05-07 19:50:31 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 0
2020-05-07 19:50:31 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 1
2020-05-07 19:50:34 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 2, chip = 184, reg = 28, got chain = 2, chip = 167, reg = 56
2020-05-07 19:50:34 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 0
2020-05-07 19:50:34 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 1
2020-05-07 19:50:36 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 2, chip = 184, reg = 28, got chain = 2, chip = 4, reg = 180
2020-05-07 19:50:37 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 0
2020-05-07 19:50:37 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 1
2020-05-07 19:50:39 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 0
2020-05-07 19:50:40 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 1
2020-05-07 19:50:42 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 0
2020-05-07 19:50:42 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 1
2020-05-07 19:50:45 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 0
2020-05-07 19:50:45 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 2, chip = 184, reg = 28, got chain = 2, chip = 15, reg = 246
2020-05-07 19:50:45 register.c:290:get_register: !!! REG_TYPE = 1. 571650050
2020-05-07 19:50:45 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 1
2020-05-07 19:50:48 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 0
2020-05-07 19:50:48 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 1
2020-05-07 19:50:51 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 0
2020-05-07 19:50:51 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 1
2020-05-07 19:50:53 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 0
2020-05-07 19:50:54 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 2, chip = 184, reg = 28, got chain = 2, chip = 177, reg = 56
2020-05-07 19:50:54 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 1
2020-05-07 19:50:56 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 0
2020-05-07 19:50:56 register.c:290:get_register: !!! REG_TYPE = 1. 2069790466
2020-05-07 19:50:57 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 1
2020-05-07 19:50:59 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 0
2020-05-07 19:50:59 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 1
2020-05-07 19:51:02 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 0
2020-05-07 19:51:02 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 1
2020-05-07 19:51:05 register.c:290:get_register: !!! REG_TYPE = 1. 816255490
2020-05-07 19:51:05 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 0
2020-05-07 19:51:05 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 1
2020-05-07 19:51:07 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 0
2020-05-07 19:51:08 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 1
2020-05-07 19:51:10 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 0
2020-05-07 19:51:10 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 1
2020-05-07 19:51:13 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 0
2020-05-07 19:51:13 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 1
2020-05-07 19:51:16 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 0
2020-05-07 19:51:16 temperature.c:697:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 184, reg = 1
2020-05-07 20:10:07 thread.c:204:calc_hashrate_avg: avg rate is 32675.68 in 30 mins
2020-05-07 20:10:07 temperature.c:450:temp_statistics_show: pcb temp 42~56 chip temp 63~80
2020-05-07 20:10:07 thread.c:285:check_hashrate: latest avg rate < 0.98......
2020-05-07 20:10:07 thread.c:286:check_hashrate: current PCB min temperature 42
2020-05-07 20:10:07 thread.c:287:check_hashrate: current voltage is 17.20V, working voltage is 17.20V
2020-05-07 20:10:07 thread.c:312:check_hashrate: high temp, voltage has already increased 0.1V/0.2V
** DELETED due to Forum Posting Limit - Same as above and below but temperature 42 **
2020-05-07 23:10:15 thread.c:204:calc_hashrate_avg: avg rate is 32806.89 in 30 mins
2020-05-07 23:10:15 temperature.c:450:temp_statistics_show: pcb temp 41~56 chip temp 60~79
2020-05-07 23:10:15 thread.c:285:check_hashrate: latest avg rate < 0.98......
2020-05-07 23:10:15 thread.c:286:check_hashrate: current PCB min temperature 41
2020-05-07 23:10:15 thread.c:287:check_hashrate: current voltage is 17.20V, working voltage is 17.20V
2020-05-07 23:10:15 thread.c:312:check_hashrate: high temp, voltage has already increased 0.1V/0.2V
2020-05-07 23:10:15 thread.c:238:is_domain_unbalance: Domain unbalance happened!
2020-05-07 23:10:15 driver-btm-api.c:201:set_miner_status: ERROR_UNBALANCE
2020-05-07 23:10:15 driver-btm-api.c:155:stop_mining_and_reboot: stop mining: Unbalance happened, reboot!
2020-05-07 23:10:15 thread.c:850:cancel_check_miner_status_thread: cancel thread
2020-05-07 23:10:15 thread.c:824:cancel_temperature_monitor_thread: cancel thread
2020-05-07 23:10:15 thread.c:834:cancel_read_nonce_reg_thread: cancel thread
2020-05-07 23:10:15 driver-btm-api.c:128:killall_hashboard: ****power off hashboard****
2020-05-07 23:10:20 Assert fail!! driver-btm-api.c:160: reboot
Looks like I might have to replace a temperature sensor as well? Jacob
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: mikeywith on May 08, 2020, 10:04:07 PM
does their platform work for the latest Bitmain products as well?
Not sure what you mean by platform, if you are talking about the tools then you can browse their website, they have this tool (https://www.zeusbtc.com/RepairDetails.asp?ID=212) works for all Bitmain Sha256 miners from T9 all the way to the latest 17 series. I've used soldering equipment before and have the will do to hot air.
Here is a video tutorial for Antminer S9 https://www.youtube.com/watch?v=5WH7g61d90w&t=246s, fixing other versions will be nearly exactly the same, you will need the same tools, the only difference is that the chips models are different for certain miners, you can find all the tools in the video including the chips on their website or on aliexpress, the general tools can be found at any local shop near you, the chips and the fixture tools are special and only manufactured in China as far as I know. Looks like I might have to replace a temperature sensor as well?
Nop, you don't have to, the chances of all 4 sensors stop working are slim to nothing, this error happens because of a bad chip, you can refer to this topic (https://bitcointalk.org/index.php?topic=5244120.0) for more details regarding the temp sensors
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: PopoJeff on May 08, 2020, 11:20:55 PM
Well, thought I had my issue under control with the temp sensor error. After multiple reboots, I reloaded the firmware. It ran a bit and threw the error. Then ran almost a day before the error. Ran another 3 days before the next error today. Did a few reboots with no luck. S17+ 70 So, being new, I plan to send it back for repair. But the other thing thats getting me, that Ive never seen in any other miner is this error: 2020-05-03 00:25:10 register.c:306:get_register: !!! reg crc errorWhether it throws the temp sensor error or not..... I get that reg crc error. Ive searched and cant find what it means. It will appear in the log hundreds of times, one after another. I just did another reboot, this time pointing it at a new pool. Dont see the reg crc error, but still giving me the temp sensor error on one board. Edit: nope. Did another reboot an it came back. So the pool had nothing to do with it. Here's a little sampling: et_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: philipma1957 on May 08, 2020, 11:28:30 PM
mine with it till a week after 1/2 ing then send it in under warranty.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: PopoJeff on May 08, 2020, 11:31:05 PM
Thats kinda the plan. An extra 43TH is better than none. Miner was almost "free" with the account credit I had at Bitmain.
And with the power plan (described in another post somewhere) that I have..... my price per kWh decreases with the extra power use. Adding this miner dropped me from approx 7.2c to 6.8c.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: mikeywith on May 09, 2020, 01:51:57 AM
I think this particulate error: 2020-05-08 23:24:57 register.c:306:get_register: !!! reg crc error
Has to do with your internet connection or the pool itself, but since you tried a different pool then maybe a network problem, can you try to use DHCP settings and just to be safe, use a different ethernet cable. Depending on how many gears you have, maybe overclocking them a bit will get your rate back to 6.8c ? also how long do you have for the warranty to be over? if not too long, maybe just void the warranty and send only the bad hashboard to Bitmain.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: PopoJeff on May 09, 2020, 02:25:04 AM
I'm at work now, I'll look into the network aspect tomorrow.
This unit is brand new. Arrived 7 days ago.
And, 3 of my 5 units are still under warranty. So I'm only running factory firmware/settings while still covered. So no overclocking for me. Also, I'm better with electrical than electronic, so I'm not comfortable messing with computer settings and programs I don't understand. #OPP (Old People Problems). BetaMax VCR was the height of my technical knowledge.
Edit:
So I swapped out the Ethernet cable, using a cable known to be working fine with another unit. Then had another thought..... I initially assigned this unit a worker name for the pool that I had previously used for an old unit which I have since sold. Dont know if that could cause confusion with the pool. Assigned it a completely new worker name not previously used.
Rebooted and so far we're ok. We'll see for how long. No crc reg error yet. It also read all the boards temp sensors correctly this time.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: mikeywith on May 10, 2020, 05:21:17 AM
Then had another thought..... I initially assigned this unit a worker name for the pool that I had previously used for an old unit which I have since sold. Dont know if that could cause confusion with the pool.
Depending on how the pool itself deals with these settings, it might cause the issue, but as far as I know, having two machines with the exact worker name online at the same time causes no problem, but it's possible that the worker had expired on the pool and no longer considered valid and thus the pool refuses it, this is why I like to use CKsolo pool as a second or third pool option since it requires no registration whatsoever, to me it's the most consistent pool, if it doesn't work, I rule out the pool problem. Anyway, if the reg "crc error error" shows up again, it is still safe to assume that it's a connection issue, maybe your router/isp blocks the pool after a certain amount of packets if it shows up again, use DHCP settings on the miner, if it fails, use a public DNS like 8.8.8.8 and at last, try a different router.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: PopoJeff on May 10, 2020, 12:06:18 PM
Thanks so much for your help and sharing of knowledge. Log looks good so far:
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: 203444K/245760K available (6345K kernel code, 231K rwdata, 1896K rodata, 1024K init, 223K bss, 25932K reserved, 16384K cma-reserved, 0K highmem)
Virtual kernel memory layout:
vector : 0xffff0000 - 0xffff1000 ( 4 kB)
fixmap : 0xffc00000 - 0xfff00000 (3072 kB)
vmalloc : 0xcf800000 - 0xff800000 ( 768 MB)
lowmem : 0xc0000000 - 0xcf000000 ( 240 MB)
pkmap : 0xbfe00000 - 0xc0000000 ( 2 MB)
modules : 0xbf000000 - 0xbfe00000 ( 14 MB)
.text : 0xc0008000 - 0xc090c424 (9234 kB)
.init : 0xc0a00000 - 0xc0b00000 (1024 kB)
.data : 0xc0b00000 - 0xc0b39fe0 ( 232 kB)
.bss : 0xc0b39fe0 - 0xc0b71c28 ( 224 kB)
Preemptible hierarchical RCU implementation.
Build-time adjustment of leaf fanout to 32.
RCU restricting CPUs from NR_CPUS=4 to nr_cpu_ids=2.
RCU: Adjusting geometry for rcu_fanout_leaf=32, nr_cpu_ids=2
NR_IRQS:16 nr_irqs:16 16
efuse mapped to cf800000
ps7-slcr mapped to cf802000
L2C: platform modifies aux control register: 0x72360000 -> 0x72760000
L2C: DT/platform modifies aux control register: 0x72360000 -> 0x72760000
L2C-310 erratum 769419 enabled
L2C-310 enabling early BRESP for Cortex-A9
L2C-310 full line of zeros enabled for Cortex-A9
L2C-310 ID prefetch enabled, offset 1 lines
L2C-310 dynamic clock gating enabled, standby mode enabled
L2C-310 cache controller enabled, 8 ways, 512 kB
L2C-310: CACHE_ID 0x410000c8, AUX_CTRL 0x76760001
zynq_clock_init: clkc starts at cf802100
Zynq clock init
sched_clock: 64 bits at 333MHz, resolution 3ns, wraps every 4398046511103ns
clocksource: arm_global_timer: mask: 0xffffffffffffffff max_cycles: 0x4ce07af025, max_idle_ns: 440795209040 ns
Switching to timer-based delay loop, resolution 3ns
clocksource: ttc_clocksource: mask: 0xffff max_cycles: 0xffff, max_idle_ns: 537538477 ns
ps7-ttc #0 at cf80a000, irq=18
Console: colour dummy device 80x30
Calibrating delay loop (skipped), value calculated using timer frequency.. 666.66 BogoMIPS (lpj=3333333)
pid_max: default: 32768 minimum: 301
Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
CPU: Testing write buffer coherency: ok
CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
Setting up static identity map for 0x100000 - 0x100058
CPU1: failed to boot: -1
Brought up 1 CPUs
SMP: Total of 1 processors activated (666.66 BogoMIPS).
CPU: All CPU(s) started in SVC mode.
devtmpfs: initialized
VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4
clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
pinctrl core: initialized pinctrl subsystem
NET: Registered protocol family 16
DMA: preallocated 256 KiB pool for atomic coherent allocations
cpuidle: using governor menu
hw-breakpoint: found 5 (+1 reserved) breakpoint and 1 watchpoint registers.
hw-breakpoint: maximum watchpoint size is 4 bytes.
zynq-ocm f800c000.ps7-ocmc: ZYNQ OCM pool: 256 KiB @ 0xcf880000
vgaarb: loaded
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
media: Linux media interface: v0.10
Linux video capture interface: v2.00
pps_core: LinuxPPS API ver. 1 registered
pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
PTP clock support registered
EDAC MC: Ver: 3.0.0
Advanced Linux Sound Architecture Driver Initialized.
clocksource: Switched to clocksource arm_global_timer
NET: Registered protocol family 2
TCP established hash table entries: 2048 (order: 1, 8192 bytes)
TCP bind hash table entries: 2048 (order: 2, 16384 bytes)
TCP: Hash tables configured (established 2048 bind 2048)
UDP hash table entries: 256 (order: 1, 8192 bytes)
UDP-Lite hash table entries: 256 (order: 1, 8192 bytes)
NET: Registered protocol family 1
RPC: Registered named UNIX socket transport module.
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
PCI: CLS 0 bytes, default 64
Trying to unpack rootfs image as initramfs...
rootfs image is not initramfs (no cpio magic); looks like an initrd
Freeing initrd memory: 12892K (cce6a000 - cdb01000)
hw perfevents: enabled with armv7_cortex_a9 PMU driver, 7 counters available
futex hash table entries: 512 (order: 3, 32768 bytes)
workingset: timestamp_bits=28 max_order=16 bucket_order=0
jffs2: version 2.2. (NAND) (SUMMARY) © 2001-2006 Red Hat, Inc.
io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered (default)
dma-pl330 f8003000.ps7-dma: Loaded driver for PL330 DMAC-241330
dma-pl330 f8003000.ps7-dma: DBUFF-128x8bytes Num_Chans-8 Num_Peri-4 Num_Events-16
e0000000.serial: ttyPS0 at MMIO 0xe0000000 (irq = 158, base_baud = 6249999) is a xuartps
console [ttyPS0] enabled
xdevcfg f8007000.ps7-dev-cfg: ioremap 0xf8007000 to cf86e000
[drm] Initialized drm 1.1.0 20060810
brd: module loaded
loop: module loaded
CAN device driver interface
gpiod_set_value: invalid GPIO
libphy: MACB_mii_bus: probed
macb e000b000.ethernet eth0: Cadence GEM rev 0x00020118 at 0xe000b000 irq 31 (00:0a:35:00:00:00)
Generic PHY e000b000.etherne:00: attached PHY driver [Generic PHY] (mii_bus:phy_addr=e000b000.etherne:00, irq=-1)
e1000e: Intel(R) PRO/1000 Network Driver - 3.2.6-k
e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
ehci-pci: EHCI PCI platform driver
usbcore: registered new interface driver usb-storage
mousedev: PS/2 mouse device common for all mice
i2c /dev entries driver
Xilinx Zynq CpuIdle Driver started
sdhci: Secure Digital Host Controller Interface driver
sdhci: Copyright(c) Pierre Ossman
sdhci-pltfm: SDHCI platform and OF driver helper
mmc0: SDHCI controller on e0100000.ps7-sdio [e0100000.ps7-sdio] using ADMA
ledtrig-cpu: registered to indicate activity on CPUs
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
nand: device found, Manufacturer ID: 0x2c, Chip ID: 0xda
nand: Micron MT29F2G08ABAGAWP
nand: 256 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 128
nand: WARNING: pl35x-nand: the ECC used on your system is too weak compared to the one required by the NAND chip
Bad block table found at page 131008, version 0x01
Bad block table found at page 130944, version 0x01
6 ofpart partitions found on MTD device pl35x-nand
Creating 6 MTD partitions on "pl35x-nand":
0x000000000000-0x000002800000 : "BOOT.bin-env-dts-kernel"
0x000002800000-0x000004800000 : "ramfs"
0x000004800000-0x000005000000 : "configs"
0x000005000000-0x000006000000 : "reserve"
0x000006000000-0x000008000000 : "ramfs-bak"
0x000008000000-0x000010000000 : "reserve1"
NET: Registered protocol family 10
sit: IPv6 over IPv4 tunneling driver
NET: Registered protocol family 17
can: controller area network core (rev 20120528 abi 9)
NET: Registered protocol family 29
can: raw protocol (rev 20120528)
can: broadcast manager protocol (rev 20120528 t)
can: netlink gateway (rev 20130117) max_hops=1
zynq_pm_ioremap: no compatible node found for 'xlnx,zynq-ddrc-a05'
zynq_pm_late_init: Unable to map DDRC IO memory.
Registering SWP/SWPB emulation handler
hctosys: unable to open rtc device (rtc0)
ALSA device list:
No soundcards found.
RAMDISK: gzip image found at block 0
EXT4-fs (ram0): couldn't mount as ext3 due to feature incompatibilities
EXT4-fs (ram0): mounted filesystem without journal. Opts: (null)
VFS: Mounted root (ext4 filesystem) on device 1:0.
devtmpfs: mounted
Freeing unused kernel memory: 1024K (c0a00000 - c0b00000)
EXT4-fs (ram0): re-mounted. Opts: block_validity,delalloc,barrier,user_xattr
random: dd urandom read with 0 bits of entropy available
ubi0: attaching mtd2
ubi0: scanning is finished
ubi0: attached mtd2 (name "configs", size 8 MiB)
ubi0: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
ubi0: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
ubi0: VID header offset: 2048 (aligned 2048), data offset: 4096
ubi0: good PEBs: 64, bad PEBs: 0, corrupted PEBs: 0
ubi0: user volume: 1, internal volumes: 1, max. volumes count: 128
ubi0: max/mean erase counter: 8/3, WL threshold: 4096, image sequence number: 237714726
ubi0: available PEBs: 0, total reserved PEBs: 64, PEBs reserved for bad PEB handling: 40
ubi0: background thread "ubi_bgt0d" started, PID 708
UBIFS (ubi0:0): background thread "ubifs_bgt0_0" started, PID 711
UBIFS (ubi0:0): UBIFS: mounted UBI device 0, volume 0, name "configs"
UBIFS (ubi0:0): LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
UBIFS (ubi0:0): FS size: 1396736 bytes (1 MiB, 11 LEBs), journal size 888833 bytes (0 MiB, 5 LEBs)
UBIFS (ubi0:0): reserved for root: 65970 bytes (64 KiB)
UBIFS (ubi0:0): media format: w4/r0 (latest is w4/r0), UUID FF09433B-E002-4C29-97EC-6220DDC4BB36, 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: 31/15, WL threshold: 4096, image sequence number: 3265111179
ubi1: available PEBs: 0, total reserved PEBs: 1020, PEBs reserved for bad PEB handling: 36
ubi1: background thread "ubi_bgt1d" started, PID 720
UBIFS (ubi1:0): background thread "ubifs_bgt1_0" started, PID 723
UBIFS (ubi1:0): UBIFS: mounted UBI device 1, volume 0, name "reserve1"
UBIFS (ubi1:0): LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
UBIFS (ubi1:0): FS size: 123039744 bytes (117 MiB, 969 LEBs), journal size 6221824 bytes (5 MiB, 49 LEBs)
UBIFS (ubi1:0): reserved for root: 4952683 bytes (4836 KiB)
UBIFS (ubi1:0): media format: w4/r0 (latest is w4/r0), UUID 1AF6F1E1-61F0-462C-AE44-C7D9596CF7E2, 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 = 0xb023
In fpga mem driver!
request_mem_region OK!
fpga mem virtual address is 0xd2000000
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
random: nonblocking pool is initialized
macb e000b000.ethernet eth0: link down
macb e000b000.ethernet eth0: unable to generate target frequency: 25000000 Hz
macb e000b000.ethernet eth0: link up (100/Full)
2020-05-09 22:33:00 driver-btm-api.c:741:init_freq_mode: This is scan-user version
2020-05-09 22:33:00 driver-btm-api.c:2413:bitmain_soc_init: opt_multi_version = 1
2020-05-09 22:33:00 driver-btm-api.c:2414:bitmain_soc_init: opt_bitmain_ab = 1
2020-05-09 22:33:00 driver-btm-api.c:2415:bitmain_soc_init: opt_bitmain_work_mode = 0
2020-05-09 22:33:00 driver-btm-api.c:2416:bitmain_soc_init: Miner compile time: Tue Apr 7 14:11:08 CST 2020 type: Antminer S17+
2020-05-09 22:33:00 driver-btm-api.c:2417:bitmain_soc_init: commit version: 0fa7066 2020-04-06 22:14:32, build by: lol 2020-04-07 14:17:53
2020-05-09 22:33:00 driver-btm-api.c:2045:show_sn: len:16, 8108ed0c2b10481c
2020-05-09 22:33:00 driver-btm-api.c:2423:bitmain_soc_init: show sn return 1
2020-05-09 22:33:00 driver-btm-api.c:2065:handle_sn_for_factory_mode: show sn return 1
2020-05-09 22:33:00 driver-btm-api.c:2103:handle_sn_for_factory_mode: read sn success, 8108ed0c2b10481c
2020-05-09 22:33:00 fan.c:279:front_fan_power_on: Note: front fan is power on!
2020-05-09 22:33:00 fan.c:291:rear_fan_power_on: Note: rear fan is power on!
2020-05-09 22:33:00 driver-btm-api.c:1276:miner_device_init: Detect 256MB control board of XILINX
2020-05-09 22:33:00 driver-btm-api.c:1217:init_fan_parameter: fan_eft : 0 fan_pwm : 0
2020-05-09 22:33:06 driver-btm-api.c:1201:init_miner_version: miner ID : 8108ed0c2b10481c
2020-05-09 22:33:06 driver-btm-api.c:1207:init_miner_version: FPGA Version = 0xB023
2020-05-09 22:33:12 driver-btm-api.c:799:get_product_id: product_id[0] = 0
2020-05-09 22:33:12 driver-btm-api.c:799:get_product_id: product_id[1] = 0
2020-05-09 22:33:12 driver-btm-api.c:799:get_product_id: product_id[2] = 0
2020-05-09 22:33:12 driver-btm-api.c:2196:update_conf_by_power_feedback: Power feedback is disabled
2020-05-09 22:33:12 driver-btm-api.c:2200:update_conf_by_power_feedback: get_calibration_voltage, vol:1970.
2020-05-09 22:33:12 frequency.c:1366:adjust_higer_max_vol_table: adjust_higer_max_vol_table, adjust_vol = 0
2020-05-09 22:33:12 thread.c:1066:create_read_nonce_reg_thread: create thread
2020-05-09 22:33:18 driver-btm-api.c:1201:init_miner_version: miner ID : 8108ed0c2b10481c
2020-05-09 22:33:18 driver-btm-api.c:1207:init_miner_version: FPGA Version = 0xB023
2020-05-09 22:33:23 driver-btm-api.c:799:get_product_id: product_id[0] = 0
2020-05-09 22:33:23 driver-btm-api.c:799:get_product_id: product_id[1] = 0
2020-05-09 22:33:23 driver-btm-api.c:799:get_product_id: product_id[2] = 0
2020-05-09 22:33:23 driver-btm-api.c:754:_set_project_type: project:0
2020-05-09 22:33:23 driver-btm-api.c:775:_set_project_type: Project type: Antminer S17+
2020-05-09 22:33:23 driver-btm-api.c:786:dump_pcb_bom_version: Chain [0] PCB Version: 0x0100
2020-05-09 22:33:23 driver-btm-api.c:787:dump_pcb_bom_version: Chain [0] BOM Version: 0x0100
2020-05-09 22:33:23 driver-btm-api.c:786:dump_pcb_bom_version: Chain [1] PCB Version: 0x0100
2020-05-09 22:33:23 driver-btm-api.c:787:dump_pcb_bom_version: Chain [1] BOM Version: 0x0100
2020-05-09 22:33:23 driver-btm-api.c:786:dump_pcb_bom_version: Chain [2] PCB Version: 0x0100
2020-05-09 22:33:23 driver-btm-api.c:787:dump_pcb_bom_version: Chain [2] BOM Version: 0x0100
2020-05-09 22:33:23 driver-btm-api.c:2334:bitmain_board_init: Fan check passed.
2020-05-09 22:33:24 board.c:36:jump_and_app_check_restore_pic: chain[0] PIC jump to app
2020-05-09 22:33:26 board.c:40:jump_and_app_check_restore_pic: Check chain[0] PIC fw version=0x88
2020-05-09 22:33:27 board.c:36:jump_and_app_check_restore_pic: chain[1] PIC jump to app
2020-05-09 22:33:29 board.c:40:jump_and_app_check_restore_pic: Check chain[1] PIC fw version=0x88
2020-05-09 22:33:30 board.c:36:jump_and_app_check_restore_pic: chain[2] PIC jump to app
2020-05-09 22:33:32 board.c:40:jump_and_app_check_restore_pic: Check chain[2] PIC fw version=0x88
2020-05-09 22:33:32 thread.c:1061:create_pic_heart_beat_thread: create thread
2020-05-09 22:33:32 power_api.c:213:power_init: Power init:
2020-05-09 22:33:32 power_api.c:214:power_init: current_voltage_raw = 0
2020-05-09 22:33:32 power_api.c:215:power_init: highest_voltage_raw = 2100
2020-05-09 22:33:32 power_api.c:216:power_init: working_voltage_raw = 1950
2020-05-09 22:33:32 power_api.c:217:power_init: higher_voltage_raw = 2040
2020-05-09 22:33:32 power_api.c:218:power_init: check_asic_voltage_raw = 2100
2020-05-09 22:33:32 driver-btm-api.c:2344:bitmain_board_init: Enter 30s sleep to make sure power release finish.
2020-05-09 22:34:04 power_api.c:324:set_to_highest_voltage_by_steps: Set to voltage raw 2100, step by step.
2020-05-09 22:34:30 power_api.c:85:check_voltage_multi: retry time: 0
2020-05-09 22:34:31 power_api.c:40:_get_avg_voltage: chain = 0, voltage = 21.078507
2020-05-09 22:34:32 power_api.c:40:_get_avg_voltage: chain = 1, voltage = 21.151866
2020-05-09 22:34:33 power_api.c:40:_get_avg_voltage: chain = 2, voltage = 21.124679
2020-05-09 22:34:33 power_api.c:53:_get_avg_voltage: average_voltage = 21.118350
2020-05-09 22:34:33 power_api.c:71:check_voltage: target_vol = 21.00, actural_vol = 21.12, check voltage passed.
2020-05-09 22:34:33 uart.c:72:set_baud: set fpga_baud to 115200
2020-05-09 22:34:44 driver-btm-api.c:1096:check_asic_number_with_power_on: Chain[0]: find 65 asic, times 0
2020-05-09 22:34:56 driver-btm-api.c:1096:check_asic_number_with_power_on: Chain[1]: find 65 asic, times 0
2020-05-09 22:35:07 driver-btm-api.c:1096:check_asic_number_with_power_on: Chain[2]: find 65 asic, times 0
2020-05-09 22:35:15 driver-hash-chip.c:266:set_uart_relay: set uart relay to 0x330003
2020-05-09 22:35:15 driver-btm-api.c:397:set_order_clock: chain[0]: set order clock, stragegy 3
2020-05-09 22:35:15 driver-btm-api.c:397:set_order_clock: chain[1]: set order clock, stragegy 3
2020-05-09 22:35:15 driver-btm-api.c:397:set_order_clock: chain[2]: set order clock, stragegy 3
2020-05-09 22:35:16 driver-hash-chip.c:502:set_clock_delay_control: core_data = 0x34
2020-05-09 22:35:16 driver-btm-api.c:1854:check_clock_counter: freq 50 clock_counter_limit 6
2020-05-09 22:35:16 voltage[0] = 1960
2020-05-09 22:35:16 voltage[1] = 1960
2020-05-09 22:35:16 voltage[2] = 1960
2020-05-09 22:35:16 power_api.c:226:set_working_voltage_raw: working_voltage_raw = 1960
2020-05-09 22:35:17 temperature.c:340:calibrate_temp_sensor_one_chain: chain 0 temp sensor NCT218
2020-05-09 22:35:19 temperature.c:340:calibrate_temp_sensor_one_chain: chain 1 temp sensor NCT218
2020-05-09 22:35:20 temperature.c:340:calibrate_temp_sensor_one_chain: chain 2 temp sensor NCT218
2020-05-09 22:35:20 uart.c:72:set_baud: set fpga_baud to 12000000
2020-05-09 22:35:21 driver-btm-api.c:264:check_bringup_temp: Bring up temperature is 24
2020-05-09 22:35:21 thread.c:1081:create_check_miner_status_thread: create thread
2020-05-09 22:35:21 thread.c:1071:create_show_miner_status_thread: create thread
2020-05-09 22:35:21 thread.c:1051:create_temperature_monitor_thread: create thread
2020-05-09 22:35:21 freq_tuning.c:183:freq_tuning_get_max_freq: Max freq of tuning is 650
2020-05-09 22:35:21 driver-btm-api.c:1727:send_null_work: [DEBUG] Send null work.
2020-05-09 22:35:21 thread.c:1041:create_asic_status_monitor_thread: create thread
2020-05-09 22:35:21 frequency.c:1019:inc_freq_with_fixed_vco: chain = 255, freq = 510, is_higher_voltage = true
2020-05-09 22:35:41 frequency.c:1061:inc_freq_with_fixed_step: chain = 0, freq_start = 510, freq_end = 530, freq_step = 5, is_higher_voltage = true
2020-05-09 22:35:45 power_api.c:352:set_to_voltage_by_steps: Set to voltage raw 2090, step by step.
2020-05-09 22:35:47 power_api.c:85:check_voltage_multi: retry time: 0
2020-05-09 22:35:48 power_api.c:40:_get_avg_voltage: chain = 0, voltage = 20.907335
2020-05-09 22:35:49 power_api.c:40:_get_avg_voltage: chain = 1, voltage = 20.929306
2020-05-09 22:35:50 power_api.c:40:_get_avg_voltage: chain = 2, voltage = 20.902438
2020-05-09 22:35:50 power_api.c:53:_get_avg_voltage: average_voltage = 20.913027
2020-05-09 22:35:50 power_api.c:71:check_voltage: target_vol = 20.90, actural_vol = 20.91, check voltage passed.
2020-05-09 22:35:54 frequency.c:1061:inc_freq_with_fixed_step: chain = 2, freq_start = 510, freq_end = 530, freq_step = 5, is_higher_voltage = true
2020-05-09 22:36:02 frequency.c:1061:inc_freq_with_fixed_step: chain = 0, freq_start = 530, freq_end = 540, freq_step = 5, is_higher_voltage = true
2020-05-09 22:36:06 power_api.c:352:set_to_voltage_by_steps: Set to voltage raw 2080, step by step.
2020-05-09 22:36:08 power_api.c:85:check_voltage_multi: retry time: 0
2020-05-09 22:36:10 power_api.c:40:_get_avg_voltage: chain = 0, voltage = 20.760617
2020-05-09 22:36:11 power_api.c:40:_get_avg_voltage: chain = 1, voltage = 20.831620
2020-05-09 22:36:12 power_api.c:40:_get_avg_voltage: chain = 2, voltage = 20.780487
2020-05-09 22:36:12 power_api.c:53:_get_avg_voltage: average_voltage = 20.790908
2020-05-09 22:36:12 power_api.c:71:check_voltage: target_vol = 20.80, actural_vol = 20.79, check voltage passed.
2020-05-09 22:36:12 frequency.c:1090:inc_asic_diff_freq_by_steps: chain = 0, start = 540, freq_step = 5
2020-05-09 22:36:19 frequency.c:1090:inc_asic_diff_freq_by_steps: chain = 1, start = 510, freq_step = 5
2020-05-09 22:36:24 frequency.c:1090:inc_asic_diff_freq_by_steps: chain = 2, start = 530, freq_step = 5
2020-05-09 22:36:30 driver-btm-api.c:727:set_timeout: freq = 590, percent = 90, hcn = 44236, timeout = 74
2020-05-09 22:36:30 power_api.c:310:set_to_working_voltage_by_steps: Set to voltage raw 1960, step by step.
2020-05-09 22:36:35 power_api.c:85:check_voltage_multi: retry time: 0
2020-05-09 22:36:36 power_api.c:40:_get_avg_voltage: chain = 0, voltage = 19.586872
2020-05-09 22:36:37 power_api.c:40:_get_avg_voltage: chain = 1, voltage = 19.659384
2020-05-09 22:36:38 power_api.c:40:_get_avg_voltage: chain = 2, voltage = 19.610540
2020-05-09 22:36:38 power_api.c:53:_get_avg_voltage: average_voltage = 19.618932
2020-05-09 22:36:38 power_api.c:71:check_voltage: target_vol = 19.60, actural_vol = 19.62, check voltage passed.
2020-05-09 22:36:38 thread.c:1076:create_check_system_status_thread: create thread
2020-05-09 22:36:39 driver-btm-api.c:2577:bitmain_soc_init: Init done!
2020-05-09 22:36:39 driver-btm-api.c:216:set_miner_status: STATUS_INIT
2020-05-09 22:36:43 driver-btm-api.c:216:set_miner_status: STATUS_OKAY
2020-05-09 22:36:44 frequency.c:205:get_ideal_hash_rate_GH: ideal_hash_rate = 70780
2020-05-09 22:36:44 frequency.c:223:get_sale_hash_rate_GH: sale_hash_rate = 70000
2020-05-09 22:36:48 driver-btm-api.c:1458:dhash_chip_send_job: Version num 4.
2020-05-09 22:36:48 driver-btm-api.c:1606:dhash_chip_send_job: stime.tv_sec 1589063808, block_ntime 1589063797
2020-05-09 23:06:49 thread.c:257:calc_hashrate_avg: avg rate is 72269.23 in 30 mins
2020-05-09 23:06:49 temperature.c:516:temp_statistics_show: pcb temp 39~63 chip temp 57~79
2020-05-09 23:36:51 thread.c:257:calc_hashrate_avg: avg rate is 72034.49 in 30 mins
2020-05-09 23:36:51 temperature.c:516:temp_statistics_show: pcb temp 39~63 chip temp 56~79
2020-05-10 00:06:53 thread.c:257:calc_hashrate_avg: avg rate is 72525.06 in 30 mins
2020-05-10 00:06:53 temperature.c:516:temp_statistics_show: pcb temp 39~63 chip temp 57~79
2020-05-10 00:36:55 thread.c:257:calc_hashrate_avg: avg rate is 72206.55 in 30 mins
2020-05-10 00:36:55 temperature.c:516:temp_statistics_show: pcb temp 40~64 chip temp 57~79
2020-05-10 01:06:57 thread.c:257:calc_hashrate_avg: avg rate is 72373.74 in 30 mins
2020-05-10 01:06:57 temperature.c:516:temp_statistics_show: pcb temp 40~64 chip temp 58~80
2020-05-10 01:36:59 thread.c:257:calc_hashrate_avg: avg rate is 72084.52 in 30 mins
2020-05-10 01:36:59 temperature.c:516:temp_statistics_show: pcb temp 40~63 chip temp 58~79
2020-05-10 02:07:01 thread.c:257:calc_hashrate_avg: avg rate is 72276.11 in 30 mins
2020-05-10 02:07:01 temperature.c:516:temp_statistics_show: pcb temp 39~63 chip temp 57~79
2020-05-10 02:37:03 thread.c:257:calc_hashrate_avg: avg rate is 72427.43 in 30 mins
2020-05-10 02:37:03 temperature.c:516:temp_statistics_show: pcb temp 39~64 chip temp 57~79
2020-05-10 03:07:05 thread.c:257:calc_hashrate_avg: avg rate is 72172.38 in 30 mins
2020-05-10 03:07:05 temperature.c:516:temp_statistics_show: pcb temp 39~64 chip temp 57~80
2020-05-10 03:37:07 thread.c:257:calc_hashrate_avg: avg rate is 72237.06 in 30 mins
2020-05-10 03:37:07 temperature.c:516:temp_statistics_show: pcb temp 39~64 chip temp 57~80
2020-05-10 04:07:09 thread.c:257:calc_hashrate_avg: avg rate is 72478.07 in 30 mins
2020-05-10 04:07:09 temperature.c:516:temp_statistics_show: pcb temp 40~64 chip temp 58~80
2020-05-10 04:37:11 thread.c:257:calc_hashrate_avg: avg rate is 72410.35 in 30 mins
2020-05-10 04:37:11 temperature.c:516:temp_statistics_show: pcb temp 39~63 chip temp 57~80
2020-05-10 05:07:13 thread.c:257:calc_hashrate_avg: avg rate is 72040.27 in 30 mins
2020-05-10 05:07:13 temperature.c:516:temp_statistics_show: pcb temp 39~64 chip temp 57~80
2020-05-10 05:37:16 thread.c:257:calc_hashrate_avg: avg rate is 72515.90 in 30 mins
2020-05-10 05:37:16 temperature.c:516:temp_statistics_show: pcb temp 40~64 chip temp 58~80
2020-05-10 06:07:17 thread.c:257:calc_hashrate_avg: avg rate is 72201.67 in 30 mins
2020-05-10 06:07:17 temperature.c:516:temp_statistics_show: pcb temp 39~63 chip temp 58~79
2020-05-10 06:37:20 thread.c:257:calc_hashrate_avg: avg rate is 72211.43 in 30 mins
2020-05-10 06:37:20 temperature.c:516:temp_statistics_show: pcb temp 39~63 chip temp 58~79
2020-05-10 07:07:22 thread.c:257:calc_hashrate_avg: avg rate is 72297.47 in 30 mins
2020-05-10 07:07:22 temperature.c:516:temp_statistics_show: pcb temp 40~63 chip temp 58~80
2020-05-10 07:37:24 thread.c:257:calc_hashrate_avg: avg rate is 72406.68 in 30 mins
2020-05-10 07:37:24 temperature.c:516:temp_statistics_show: pcb temp 40~65 chip temp 58~80
2020-05-10 08:07:26 thread.c:257:calc_hashrate_avg: avg rate is 72187.64 in 30 mins
2020-05-10 08:07:26 temperature.c:516:temp_statistics_show: pcb temp 39~64 chip temp 58~79
2020-05-10 08:37:28 thread.c:257:calc_hashrate_avg: avg rate is 72241.33 in 30 mins
2020-05-10 08:37:28 temperature.c:516:temp_statistics_show: pcb temp 39~64 chip temp 58~80
2020-05-10 09:07:30 thread.c:257:calc_hashrate_avg: avg rate is 72516.51 in 30 mins
2020-05-10 09:07:30 temperature.c:516:temp_statistics_show: pcb temp 40~63 chip temp 58~80
2020-05-10 09:37:32 thread.c:257:calc_hashrate_avg: avg rate is 72341.40 in 30 mins
2020-05-10 09:37:32 temperature.c:516:temp_statistics_show: pcb temp 40~63 chip temp 57~80
2020-05-10 10:07:34 thread.c:257:calc_hashrate_avg: avg rate is 72287.09 in 30 mins
2020-05-10 10:07:34 temperature.c:516:temp_statistics_show: pcb temp 40~64 chip temp 58~79
2020-05-10 10:37:36 thread.c:257:calc_hashrate_avg: avg rate is 72598.28 in 30 mins
2020-05-10 10:37:36 temperature.c:516:temp_statistics_show: pcb temp 40~64 chip temp 57~80
2020-05-10 11:07:38 thread.c:257:calc_hashrate_avg: avg rate is 72505.53 in 30 mins
2020-05-10 11:07:38 temperature.c:516:temp_statistics_show: pcb temp 39~64 chip temp 58~80
2020-05-10 11:37:40 thread.c:257:calc_hashrate_avg: avg rate is 72204.11 in 30 mins
2020-05-10 11:37:40 temperature.c:516:temp_statistics_show: pcb temp 40~64 chip temp 58~80
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: Scorpyy on May 11, 2020, 07:51:39 AM
Does anyone know can Bitmain tell if firmware was changed in the past if i revert it to original one?
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: favebook on May 11, 2020, 04:45:36 PM
Does anyone know can Bitmain tell if firmware was changed in the past if i revert it to original one?
AFAIK, no. I had a machine which pooped 2 hashboards (on original BITMAIN firmware) and I tried custom one just to see if voltage change or frequency change would bring it alive (worked fine for some time), and then I decided to RMA it. Just returned to original firmware and they repaired it w/o questions. It was in warranty.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: foncho86 on May 16, 2020, 11:11:55 PM
I have one T17e, one card burned out the chips heatsinks came away made short-circuit, so I have two boards left, One is dead tells me 0 Asics. And the other one must to be placed at a warm place in order to startup and work, because a normal cold start-up doesn't come to live. Do you know what I should do to fix that in order to cold start my miner normaly.. not needed to warm it up to start it..??? the problem that the board gives to me when it cold start is 0,then 4 then 6 Asics and ERROR_TEMP_LOST.. should I change the temp sensor..?? or should I remove all the heatsinks and clean it.. and put the heatsinks again? in order to heat the board over a faulty contact on the board?
Thanks for any help in advance..!!!
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: Scorpyy on May 17, 2020, 06:24:04 AM
If you can find new sensors and know how to replace them you can try that. If machine is still under warranty i would suggest you to just return it for repair.
Switching to Asic.to or Awesome miner firmware can help a little in some cases. By upclocking the boards, the machine runs on higher temp which causes less temp sensor errors. Also you can set miner to automatically reboot after board drops.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: mikeywith on May 18, 2020, 12:09:47 AM
should I change the temp sensor..
Don't do that, it's very very highly unlikely that changing the sensor will fix anything, the board that shows 0 aasic probably has a losen heatsink or a faulty chip somewhere, if you think the cold start up is causing the issue then use a custom firmware, i think they have an option of warming up the chips that could help. ?? or should I remove all the heatsinks and clean it.. and put the heatsinks again?
NO!! , removing a heatsink is not something you can easily do, you need a few tools, let alone removing all of them, you will need a few days to do that and then that might not fix the issue.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: foncho86 on May 19, 2020, 12:19:28 AM
Found the other board has a faulty chip, when I was cleaining it.. the chip falled down with the heatsink.. I would get a good chip from the burned board and trying to resolder.. I have a heat gun... and flux.. and all the equipment to repair it...
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: mikeywith on May 19, 2020, 01:41:28 AM
Found the other board has a faulty chip, when I was cleaining it.. the chip falled down with the heatsink.
probably has a losen heatsink or a faulty chip somewhere
See that was an easy guess, in fact the T17e has a failure rate of 30%, the majority of that 30 % is the exact problem you have, so for everyone else reading this (probably in the near future) whenever you get a board showing 0 asic or temp-sensor issues, know that most of the time it's a chip/heatsink issue. The good thing is that the chip you going to remove will have pre-tin solder on it, so you only need to heat it and you don't need any tin-tool for that, you can refer to this video (https://www.youtube.com/watch?v=5WH7g61d90w&t=160s)to get a better idea on how to replace the chip,
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: Spooky123 on May 19, 2020, 02:48:59 AM
If anybody has a S17 Pro hashboard that is burnt and can't warranty it, I am looking for one for core value. Just send me a PM. Thanks.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: Scorpyy on May 19, 2020, 12:31:55 PM
[...]
So chip / heatsink issue on most of units, and yet Bitmain claims if heatsink is loose or chip is burned that warranty for that board is voided, so sad.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: favebook on May 19, 2020, 02:19:23 PM
So chip / heatsink issue on most of units, and yet Bitmain claims if heatsink is loose or chip is burned that warranty for that board is voided, so sad.
AFAIK that website wasn't changed since era of S9's. For T/S17 gear they know they fk-ed up and are replacing whole units without any real questions. For my S17 Pro (out of warranty) "repair" cost me $60 which is less than 40% of what I paid for shipping, so I was happy. But for bigger farms, I guess they do not even ask and just replace it with new unit for free.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: PopoJeff on May 19, 2020, 11:43:35 PM
Thanks so much for your help and sharing of knowledge.
Log looks good so far...
Well, ran flawlessly since the above post.... 9 days. Then the whole thing dropped out today. That reg crc error returned, and the failure to read temp sensor error came back too. Looking to figure out the return process this week.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: mikeywith on May 20, 2020, 12:16:18 AM
So chip / heatsink issue on most of units, and yet Bitmain claims if heatsink is loose or chip is burned that warranty for that board is voided, so sad.
Are you sure about this? assuming you haven't disassembled the miner the warranty is still valid no? I honestly never understood their warranty program, when I read how they offered to send technicians to the mining farms in china to fix their faulty 17 series and how was Jihan wu "begging those miners to give Bitmain a second chance with the S19" it looks like and for obvious reasons, the way they treat large farms is way different than how they treat the average joe like ourselves, I don't want to keep repeating this but I hope this serves a lesson to avoid the 17 series, and not buy any 19 series mining gear until reports show that they have a reasonably low RMA/failure rate. Today one of my friends lost the last working chain on his S17, it would show 0 Asics, sometimes more, it became unstable and useless, he bought that gear for 4k back then, most certainly way too far from ROIing on that gear.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: PopoJeff on May 22, 2020, 09:32:04 AM
Well, ran flawlessly since the above post.... 9 days. Then the whole thing dropped out today. That reg crc error returned, and the failure to read temp sensor error came back too.
Looking to figure out the return process this week.
Contacted Bitmain customer service and created a repair ticket to claim DOA since I'm still within my 30day window. But CA repair facility is closed due to CoronaVirus govt lockdown. Customer service asked me to ship it to the HONG KONG location. I responded asking for alternatives, as my shipping to CA is ~ $100, and to Hong Kong is ~$400-500. I'd rather wait for CA to reopen, than spend 4-5x shipping cost.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: mikeywith on May 22, 2020, 11:19:45 PM
I responded asking for alternatives, as my shipping to CA is ~ $100, and to Hong Kong is ~$400-500. I'd rather wait for CA to reopen, than spend 4-5x shipping cost.
$400-500 + the time wasted from sending it to receiving it back will probably cause you to lose more than you will ever mine with that gear, they do have an address in Netherlands, I presume it would be cheaper and faster to ship it there, you need to ask them if you can send it there (obviously after checking the shipping price to that location), here is a list of all their repair (https://support.bitmain.com/hc/en-us/articles/220138027-Global-repair-site-delivery-addresses) sites.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: PopoJeff on May 23, 2020, 12:01:14 PM
I responded to customer service email, advising that I was not concerned with speed of repair/replacement, and asked if I could delay the return until CA is re-opened. Received a response that we could do just that, file a temporary repair ticket for CA, and update/renew as needed until CA reopened.
My business aspect is unique, in that this miner was bought almost completely with previous credit. I spent less than $200 total, including shipping and tariff. Plan was to bring in an almost free 70th unit, and sell the 50th unit, effectively getting paid to swap out and increase by 20th. But not doing that til I get a good unit.
So I unplug this thing on Wednesday to not waste power. Spend 2 days of emailing, and figure out I'm in a holding pattern. I plugged it back in Friday to fiddle with it again, and its running perfectly again with no errors almost 24hrs now. That tells me theres nothing wrong on my end network wise, if the errors come and go randomly.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: The_binary_Observer on May 26, 2020, 05:53:23 AM
Hello, I have been reading every single answer to this interesting post. This is because I have also been framed by Bitmain with those S17+ antminers. I have some background in electronics and analyzing those intermittent failures that these miners have just got me a little confused, specially during a time that I checked control boards and data cables by disconnecting back and forth. At times the miner was full throttle mining just to drop after few hours. That in electronics is called a "cold soldering". Although there are not visible cold solderings I discovered that the soldering material that is being used on this S17 have 2 problems.
First, high amount of lead and low proportion of tin, and of course zero silver in the soldering material. This can be observed under the microscope used to soldering circuit boards. All of the solderings showed a greyish mate color and no shinning finish.
Second, below normal temperature of the soldering material, also leaves traces, specially on the hashing board chips. Also analyzed under the microscope there are traces that look like an sponge along with tiny cracks surrounding the chip's area at the surface of the hashing board.
So, this takes me into the conclusion that somebody at Bitmain's is trying to cut ends and by doing this they have compromised 50% of the S17, T17 series. The use of soldering with high percentage of plumb just tells me that they are throwing the cheapest crap they have to solder the components on those miners. Also they are trying to reduce electricity costs by not heating well enough the soldering material melted at the trays and this is specially true because the soldering material with higher proportion-ratio of lead instead of tin and silver takes colder temperatures to melt.
So taking all this into consideration I really recommend to all of those that are willing to throw the money into shipping costs, customs fees and no mining income, just don't do it because Bitmain still uses the same bad quality materials to fix it.
Since that soldering material is all over the hashing and controller boards is just a matter of time chips keep coming off the boards, the only and costly solution is to desoldering them all and soldering back with a good quality soldering flux, other than that those miners will keep failing over and over.
Basically most of the S17 series are doomed.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: mikeywith on May 26, 2020, 08:03:26 AM
Since that soldering material is all over the hashing and controller boards is just a matter of time chips keep coming off the boards, the only and costly solution is to desoldering them all and soldering back with a good quality soldering flux, other than that those miners will keep failing over and over.
Basically most of the S17 series are doomed.
You have just explained 'scientifically' what I have been trying to tell everyone for months, dude we need more people like you around. So, since the soldering melts at fairly low temp, will under-clocling these miners give any improvement in the lifespan of that tin before chips start falling? Or should someone just overclock the heck out of them because they will melt either way? Or leave them at stock? Also what soldering flux do you suggest to use? A product link from Amazon will be great.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: favebook on May 26, 2020, 12:51:25 PM
I have some background in electronics and analyzing those intermittent failures that these miners have just got me a little confused, specially during a time that I checked control boards and data cables by disconnecting back and forth.
At times the miner was full throttle mining just to drop after few hours. That in electronics is called a "cold soldering". Although there are not visible cold solderings I discovered that the soldering material that is being used on this S17 have 2 problems.
First, high amount of lead and low proportion of tin, and of course zero silver in the soldering material. This can be observed under the microscope used to soldering circuit boards. All of the solderings showed a greyish mate color and no shinning finish.
Second, below normal temperature of the soldering material, also leaves traces, specially on the hashing board chips. Also analyzed under the microscope there are traces that look like an sponge along with tiny cracks surrounding the chip's area at the surface of the hashing board.
What mikeywith said... We need more people like you, seriously! Would you mind setting up a ticket and telling them all of this? You might get a refund or some coupon or even a job offer there :D
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: The_binary_Observer on May 27, 2020, 01:36:22 PM
My friend mikeywith, I really appreciate your good words, thanks. About your question of keep it stock or overclocking, I rather underclocking them cut the blue wire from the fans and place the miner in a horizontal position instead of vertical so the chips on the boards also stay in horizontal position and that might help to keep them from falling easily. Also I observed that the base plate where the fans are attached are not completely open to the airflow as those in the S9. Those plates have metal fins forming squares in front of the fans and let me tell you those fins cause a disruption and some blockage of the airflow into de miner. In the past I did some experiment placing a simple air filter in front of the intake fans on S9, after few minutes of operation the miner's temperature raised exponentially in relation with a no air filter condition. Based on that, I suspect that any obstruction of the air flow, no matter how small is can cause the temperature on the miner to raise abnormally high and relatively quick. The solution to this is to cut those stupid square fins that are in the fan base plate and leave them as those that come with the S9. Just keep the outer frame of the plate which is in reality where the plate and fans attach to the aluminum body of the miner. About your question of which soldering paste to use, the BEST choice all over the board hands down is Kester TSF-6522. it can be bought on electronic specialty stores such as Digikey. This compound is specially good since is a tacky and NO CLEAN class which is very important. Due to the limited space between the hashing chips is absolutely necessary to leave no trace of soldering material around and within the chip that is about to be soldered. Here is the link: https://www.digikey.com/products/en/soldering-desoldering-rework-products/flux-flux-remover/266 I hope this have helped many people around to understand what is really going on with this miners and to suggest to those that are willing to fix by themselves their miners to do it. Instead to spend the money by sending your machine, as Bitmain expects to do it, to Hong Kong, I rather buy the chips, the hot air soldering machine and soldering compound and do it myself. Yet, if you feel you are not able to do such a job find an electronic technician that have hot air soldering skills and ask to do the job, you can supply the hashing chips and the soldering paste. To all good friends in this community I tell you guys WE ALL are on our own on this and if I were a lawyer I will be filling for a class action lawsuit against Bitmain. By the time and in the best of our interests let's find out how to solve our miners problems by ourselves so we can be back in business in a safe and low cost manner. Best regards.
... Would you mind setting up a ticket and telling them all of this? You might get a refund or some coupon or even a job offer there :D
Friend Favebook, I already did and I'm really sick of "copy and paste" answers by someone called Jessica L. who is in charge of technical department.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: favebook on May 27, 2020, 05:18:34 PM
About your question of keep it stock or overclocking, I rather underclocking them cut the blue wire from the fans and place the miner in a horizontal position instead of vertical so the chips on the boards also stay in horizontal position and that might help to keep them from falling easily.
Are you sure about the horizontal positioning? By some laws of physics and my basic understanding of it, while miner is in vertical position, all heatsinks have the same sag and gravity is pulling them downwards at angle of 90°. And that may not be perfect, but I think it is best to stay in that position since if you put the miner horizontally, half of heatsinks are in perfect position (gravity is pulling them towards chips and that would make them almost impossible to fall off), but half of them are in worst position as they are pulled downwards (away from chips) at angle of 180° and that would make them (by some raw and stupid calculation) 50% more likely to fall off than in vertical position. Please, do correct me if I am wrong in any way! Friend Favebook, I already did and I'm really sick of "copy and paste" answers by someone called Jessica L. who is in charge of technical department.
Yeah, I understand you... I hate those answers too.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: jbillk on May 27, 2020, 06:43:52 PM
I have a S17 with 3 dead hashboards that gradually dropped out. No warranty, no good-will. For sure its the solder breaking on the chips, tried everything.
This is not recommended, but as a last ditch effort tried to re-flow the hash boards by heating to 385 Deg f for 10 min. Haven't had success. I've heard of people bringing motherboards and GPUs back to life using this technique. Theory is the heat melts and reconnects the broken solder joint.
Maybe something to try before you throw your board in the trash. Not sure if anybody else has tried this with any degree of success.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: Pendrak on May 27, 2020, 07:26:55 PM
All S17 T17 series need a change of FANS, those that come are the worst wining shitty fans i haver use, all bitmain equipment this days come with those fans, they move almost nothing air, if you have DELTA or other good brand (2.6 amp) just change the 2 back FANS.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: The_binary_Observer on May 27, 2020, 08:54:24 PM
Are you sure about the horizontal positioning? By some laws of physics and my basic understanding of it, while miner is in vertical position, all heatsinks have the same sag and gravity is pulling them downwards at angle of 90°. And that may not be perfect, but I think it is best to stay in that position since if you put the miner horizontally, half of heatsinks are in perfect position (gravity is pulling them towards chips and that would make them almost impossible to fall off), but half of them are in worst position as they are pulled downwards (away from chips) at angle of 180° and that would make them (by some raw and stupid calculation) 50% more likely to fall off than in vertical position.
I understand what you are talking about, you are referring to the chips that are on the other side of the hashing boards, the small ones with small heatsink. However, what I am doing is putting upwards the chips with the long heatsink which are the ones that creates most of the heat and thus are prone to fall off the board due to this high temperature. The ones on the opposite side have a small heatsink which tells me they develop less heat. I am testing this position on several miners and see what happens.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: favebook on May 28, 2020, 03:06:09 AM
I understand what you are talking about, you are referring to the chips that are on the other side of the hashing boards, the small ones with small heatsink. However, what I am doing is putting upwards the chips with the long heatsink which are the ones that creates most of the heat and thus are prone to fall off the board due to this high temperature. The ones on the opposite side have a small heatsink which tells me they develop less heat. I am testing this position on several miners and see what happens.
That seems smart. Will test too!
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: The_binary_Observer on May 28, 2020, 04:08:46 PM
I have a S17 with 3 dead hashboards that gradually dropped out. No warranty, no good-will. For sure its the solder breaking on the chips, tried everything.
This is not recommended, but as a last ditch effort tried to re-flow the hash boards by heating to 385 Deg f for 10 min. Haven't had success. I've heard of people bringing motherboards and GPUs back to life using this technique. Theory is the heat melts and reconnects the broken solder joint.
Maybe something to try before you throw your board in the trash. Not sure if anybody else has tried this with any degree of success.
Jbillk, don't throw them to the garbage, find someone near you that have soldering skills using hot air guns, buy yourself a good soldering paste and bring one hashing board and ask the tech resold the chips and most of the components on the hashing board. here is a top notch soldering paste https://www.digikey.com/products/en/soldering-desoldering-rework-products/flux-flux-remover/266
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: mikeywith on May 28, 2020, 09:41:21 PM
you are referring to the chips that are on the other side of the hashing boards, the small ones with small heatsink.
favebook brought up a very good point, just for everybody's information, the heatsinks that usually fall are the once that are directly on top of the chips ( the bigger ones), if you take out 2 heatsinks placed in the opposite direction of one another, one will have the asic chip below it, another will be "empty", however, without totally negating the effect of positioning the miner in a horizontal position, it's safe to assume that unless you can do it easily [1] it's really not worth the effort, there isn't much you can do about these heatsinks until they fall, sadly. [1]- if you use spilt-room design as I do and you have already made a whole to fit the miner vertically, going horizontal is a lot of effort, which IMO not worth it given the little advantages you get from this, but if it's a matter of simply repositioning the miner in 30-60 seconds, go ahead, you lose nothing. This is not recommended, but as a last ditch effort tried to re-flow the hash boards by heating to 385 Deg f for 10 min.
Had to go from f to c (apparently what 99% of human beings use ;D) and it turns out to be 196 c, please DON"T do that, the chips and most other components will most likely rest in peace when they are put in that temp for 10 mins, your method could have probably fixed the soldering problem but created a far greater issue. I suggest to simply apply some pressure on the heatsinks see which one falls, try to soldier it or do as The_binary_Observer suggested.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: danieleither on June 01, 2020, 10:47:58 PM
Recently purchased 2 x S17+ 70TH, April batch but delivered in May due to delays at Customs. Both machines worked fine initially, then dropped a hashboard. One machine after just 1 hour and the 2nd unit after approx. 2.5 hours, very disappointing :( Spent several days back and forth with Bitmain support doing everything they asked but to no avail and now both units have been shipped back for repair.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: mikeywith on June 02, 2020, 07:23:13 AM
Sorry to hear your story, although by now I am not surprised to read such stories, in fact, I'd be surprised hearing the opposite about these crappy gears Bitmain makes.
Did the support bots at bitmain give you any troubleshooting aside from the
"Sir please reset the mine and flash the latest firmware" or "Sir this is the recovery files put on sd and flash, use this guide"?
I am sure that members here provide a million times better troubleshooting than bitmain's support, did they tell you about the cheap soldering they use? I can bet the house that the 2 boards that failed had a loose heatsink/chip on them, just like 99% of other issues happen, so another month or so of delay, only to get the same unit you ordered a long time ago, by the time you start hashing - all those S19s/M30s have been plugged in, well good luck with that.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: o_solo_miner on June 02, 2020, 09:29:24 AM
I have some background in electronics and analyzing those intermittent failures that these miners have just got me a little confused, specially during a time that I checked control boards and data cables by disconnecting back and forth. At times the miner was full throttle mining just to drop after few hours. That in electronics is called a "cold soldering". Although there are not visible cold solderings I discovered that the soldering material that is being used on this S17 have 2 problems.
First, high amount of lead and low proportion of tin, and of course zero silver in the soldering material. This can be observed under the microscope used to soldering circuit boards. All of the solderings showed a greyish mate color and no shinning finish.
Just to let you know, the greyish finish comes basicly from lead free solder. All Manufactors are forced to use leadfree from 1996 on for consumer products. You may test it using a handheld analyzer (in production used to check material prior production). That you expirience cold joints is a old problem also on S5 and S3. To repair that, I use no clean flux paste around the affected chip then a heatplate on the underside of the board (regulatet to 100° c) and warm the pcb up for arround 3 min. before I am using a regulated hotair (360°c) on top to melt the joint and reestablish connection. 99% this method works. 1% the chip was realy dead before that action. In conclusion I can say that bitmain did not got their reflow process in control, and no qa off corse.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: Pendrak on June 03, 2020, 04:42:26 AM
All you do is a reflow, make sense if the board is new, if the equipment is old a reballing is needed.
The lead-free solders melt at higher temperatures of about 217°C/422°F compared to 183°C/361°F for the lead-based option, if you can use lead paste/ball is better.
The problem with Lead-free solders is that make micro-fracture occurs in the solder joints, this is a know problem with the consoles (XBOX and PS), reballing with lead balls make then working perfectly, no more cold joints and micro-fracture.
Lead free solder is an abomination for circuits, help the environment but kill circuits especially the ones that work with high temperature.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: o_solo_miner on June 03, 2020, 07:06:35 AM
Well, this is not valid for all electronics.
Bitmain asics comes as qfn package not bga, that means that the coating of the chip is paladium. Everything in chip manufacture is oriented to lead-free now.
Depending on what kind of solder paste (activator chemicals) was used, a mix with other lead paste (acid chemicals as activator) may result in a good joint, but degrading of the influence of the different chemicals mixed now over the time. The heat of the board, the vibration from the fans, and a not homogen temp over the pcb result in warping the joints (microfracture).
The problem of the miner is to look overall, so the pcb design and the material used is also an issue. Given the condition of in wich the pcb has to operate, this is not an easy (quick) task. But time to market is the main concern at bitmain. Anyway we have to live with it, as we got only the option not to buy.
PS: If bitmain can offer you a new S9 for 63$ now and still make some money, I do not think that they are realy designing the miners up to quality or a long life.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: jbillk on June 03, 2020, 04:37:39 PM
Jbillk, don't throw them to the garbage, find someone near you that have soldering skills using hot air guns, buy yourself a good soldering paste and bring one hashing board and ask the tech resold the chips and most of the components on the hashing board.
here is a top notch soldering paste
https://www.digikey.com/products/en/soldering-desoldering-rework-products/flux-flux-remover/266
Problem is that all the boards look ok, it would be like finding a needle in a haystack finding the bad chips. The log shows 0 chips detected on all 3 boards, so i have no idea witch ones need to be re-soldered. I also tried blasting the boards with hot air gun, no results. Not sure if reflow oven at higher temperature will work (already tried 10 min @ 200 deg c). Really have nothing to lose, i'm just experimenting at this point.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: mikeywith on June 04, 2020, 07:23:07 AM
PS: If bitmain can offer you a new S9 for 63$ now and still make some money, I do not think that they are realy designing the miners up to quality or a long life.
This makes sense, but what I don't seem to understand is the reason why all gears made by Bitmain in 2019 onwards have the same issue, it's not just the 17 series, even the S9k had the same issue of heatsinks/chips falling off the hash boards, I am not sure if you saw my thread (https://bitcointalk.org/index.php?topic=5218440.msg53631697#msg53631697) regarding the s9k, now I don't know enough about electrics but it seems like bitmain aren't using any type of solder but rather they inherit the postage stamp method of using a bit of saliva to stick them ;D, I would understand if the heatsinks fall due to over-heating them - that means the quality of the paste they use is bad, but for chips to fall off due to shipping and handling is terrible, I would like to get a an explanation on that.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: o_solo_miner on June 04, 2020, 05:44:34 PM
I will take a look at your S9 topic, if chips fall off during transport, that means that the reflow was to low in temp or the belt speed was to fast (if the temp profile in the oven was ok). POOR QA!
The best way to repair the faulty board (and produce the board) would be to use a vapor phase instead of the reflow. But that is to pricy for them and to slow. The heatsink is glued, the S1 was a proper way to do a heatsink, but again, to pricy for BM.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: philipma1957 on June 04, 2020, 05:55:23 PM
Yeah. the box is well packed. the foam is good quality. but the force generated with a 6 foot drop is quite a bit.
and if you drop the box flat on the bottom there will be no apparent damage to the box or the miner inside.
But every heat sink will be subject to a g-force from the drop then stop.
to make it more wrong is that if the gear is in a really cold spot ie during wintertime the gear is allowed to travel in 0c or 32f or lower transport bays.
So now the glue/heatsink past is hard stiff and brittle so now drop it 6 feet and the box has no damage the unit looks fine . I could guarantee that multiple glue/paste/epoxy heatsink joints now have micro damage . Same as solder joints.
Would love to demo that test. As you know it happens.
edit To be clear 0c or 32f makes the heatsink to chip joint a bit more brittle and easier to crack then it would be at 20c or 68f
And of course at -20c or -4f it would be a bit stiffer and even more brittle.
So if the fedex/dhl/ups truck drops off a unit on your porch in the winter time it is very likely the chip to heatsink seal if cracked was cracked right at your door step.
Here in NJ I have received hundreds of pieces of gear from China and sometimes the guys drop the gear off when I am not home.
Even if the guy drops it 3-4 feet to the step in the dead of winter it is not good for the heatsinks.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: mikeywith on June 05, 2020, 04:38:40 PM
And of course at -20c or -4f it would be a bit stiffer and even more brittle.
So if the fedex/dhl/ups truck drops off a unit on your porch in the winter time it is very likely the chip to heatsink seal if cracked was cracked right at your door step.
Even if the guy drops it 3-4 feet to the step in the dead of winter it is not good for the heatsinks.
I believe it has little to do with the outside temp when the miner is not running, also bad handling of packages doesn't seem to be the reason why those chips on my S9ks fell, I had a lot of them shipped, some for me and a lot for clients, they all arrived at the same time with the same environmental conditions, a few had heatsinks fall right out of the box, some did mine for a few days, some for a few weeks, some are still good to this point but overall terrible, so my guess is that alongside with the terrible quality of their solder paste, those S9ks don't go through a quality process, so depending heavily on your luck, you might receive a bricked gear as I did.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: favebook on June 05, 2020, 07:01:24 PM
Well... Considering their price, QC is probably not worth it for Bitmain to do on S9ks. It has been noticable over years that their QC is becoming worse (or even worse, it could be that it hasn't changed at all even though technology changed a lot and that can be a big problem too).
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: mikeywith on June 05, 2020, 09:57:47 PM
Well... Considering their price, QC is probably not worth it for Bitmain to do on S9ks. It has been noticable over years that their QC is becoming worse (or even worse, it could be that it hasn't changed at all even though technology changed a lot and that can be a big problem too).
Just for the record, I paid $263.00 for those crappy S9ks, they weren't at $60 like now, so really nearly $300 for that gear doesn't give bitmain the excuse to send them with fallen chips and heatsinks, in fact, the QS measure should be same on all gears, cheap gears cost less to manufacture, which is why they can afford to sell them for so cheap, but QS is a different story, around the same period of time I bought S9js for $276, and they are a trillion times better, those S9js were probably stored from previous years batches, and given that all the new gears S9 or not have the same issue of chips/heatsinks falling, it shows that something went wrong in their QS department, something which all the S19s buyers should keep in mind, although Jihan Wu promised that the S19s will be robust after he admitted the 17 series were crappy, he, of course, puts the blame on Micree Zhan. Ironically I tend to believe Jihan this time, not because I think he is honest by any means, but the S19s are their last chance, so it's very likely that everything about S19 is going to be a lot better in terms of quality, I am just not willing to take the risk until it's confirmed.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: The_binary_Observer on June 09, 2020, 03:11:50 AM
Well after pushing and pushing at every known e-mail address at Bitmain I finally got in contact with somebody on a high rank at service dept. He confirmed what I have been suspecting about the quality of soldering is very likely the root of the problems on all S17 series, even on prior from S series as S9K and all the way thru S17. I got in touch with him via whatsapp here is the conversation: https://ibb.co/LdPzMyc
So, being that said, all my dear friends is useless and futile send you S17 to Bitmain even under warranty because is very likely that as soon as you receive them back other chips will come off, so learn how to solder using soldering paste and flux with hot air solder. Other than that, find yourself a local electronic tech near you to avoid and expose the miner to shipping "kick handling" even if shipped to Bitmain's Service Center in the USA.
Hope this clears out all theories about this equipment since the root cause of failure have been revealed.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: mikeywith on June 09, 2020, 09:01:15 PM
This guy knows a lot more than those bots who usually reply to most of us, but the logic behind his explanation is plain stupid, saying "The advantage is that easy is easy to disassemble" is like saying "We made this car with a strong engine but we hang it using a zip-tie so you can remove it whenever you need", so if that guy is not lying, he is simply stupid, simply because how often do you need to disassemble those chips? almost NEVER, how often do you need them to stick and not drop? ALWAYS!
The only advantage I can think of is that low-temperature solder paste cost way less than high-temperature solder paste, making thousands of gears, it means soldering millions of chips, 100,000 miners with 30 chips each, using a cheaper paste saves you hypnotically 1.1 cents per chip or 1$ per miner, that's a $100,000, you make 200,000 miners, you save twice as much, this assumes $1 cost reduction per miner which of course is just a random number that could potentially be a lot higher.
If there is really any advantage (related to the subject) aside from cost reduction for low-temp paste vs high-temp paste, I would like to know about it.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: The_binary_Observer on June 09, 2020, 11:13:26 PM
Mikeywith, what really disturbed me is the part the guy says, "Because new miners rarely have such problems in China, it is likely that they have been injured during transportation"
So how do they transport the miners within Mainland China? By teletransportation as in Star Trek? Scotty beam up the miners to Shinchong farm? Nahhh they ship them the same way the do to other parts of the world.
So thinking about the way that people operates, cheating and lying all the time, I have come into a conclusion that Bitmain have two assembly lines, one for their own farms and customers within China, the other for the rest of the world which is low quality and compensates the extra costs invested into the "domestic production assembly line".
Moreover, they don't want more competition so they take your hard earned money, send you a crappy machine and in 3 months max you are out of the business either because you ran out of money or you are not willing to spend more in some other brand of equipment and in the top of that you have no working miners either.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: favebook on June 10, 2020, 01:45:57 AM
Mikeywith, what really disturbed me is the part the guy says, "Because new miners rarely have such problems in China, it is likely that they have been injured during transportation"
So how do they transport the miners within Mainland China? By teletransportation as in Star Trek? Scotty beam up the miners to Shinchong farm? Nahhh they ship them the same way the do to other parts of the world.
So thinking about the way that people operates, cheating and lying all the time, I have come into a conclusion that Bitmain have two assembly lines, one for their own farms and customers within China, the other for the rest of the world which is low quality and compensates the extra costs invested into the "domestic production assembly line".
Moreover, they don't want more competition so they take your hard earned money, send you a crappy machine and in 3 months max you are out of the business either because you ran out of money or you are not willing to spend more in some other brand of equipment and in the top of that you have no working miners either.
Come to think of it. That could be true (Bolded Italic). I am a small sample but all the gear I ordered via friend in China is working even OC-ed after year and more. And only units I had problem with were shipped from Bitmain directly to Europe.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: mikeywith on June 10, 2020, 10:49:26 AM
Mikeywith, what really disturbed me is the part the guy says, "Because new miners rarely have such problems in China, it is likely that they have been injured during transportation"
That is another lie, a while ago i linked an article which was likely translated from a Chinese one, that talked about Chinese miners complain about the exact same problem we all have 'heatsinks/chips falling apart', apparently the mining whales in China have some private WeChat groups, and that's where Jihan Wu hangs around, Jihan Wu begged the Chinese miners to give bitmain another chance with the S19 after admitting the 17 series had some major quality issues, those reports came from CHINA from CHINESE miners, so saying "new miners rarely have such problems in china is a straight out lie" unless he thinks that 30% or higher failure rate is considered "rare". This, of course, does not negate the fact that the Chinese miners get a special pass, Jihan Wu never apologized or begged us, he probably never bothers about the forum, or other non-Chinese groups on telegram and Facebook, but when the Chinese miners complain he listens, heck he even offered to send them staff on site to have the faulty 17 series fixed at NO cost.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: akagi82 on June 12, 2020, 05:21:56 AM
I also have a complete coorespondence with Bitmain tech support, Jessica L. I can post it if you guys are interested. All they have done is given me a generic trouble shooting list and not answered any of my specific questions...
This is pretty normal... such a waste of time.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: danieleither on June 15, 2020, 12:07:51 AM
Recently purchased 2 x S17+ 70TH, April batch but delivered in May due to delays at Customs. Both machines worked fine initially, then dropped a hashboard. One machine after just 1 hour and the 2nd unit after approx. 2.5 hours, very disappointing :( Spent several days back and forth with Bitmain support doing everything they asked but to no avail and now both units have been shipped back for repair.
Since I posted this a short while back, I feel it is only fair to post an update since the response from Bitmain has been reasonably impressive. After a few days of initial troubleshooting (back and forth communication with Bitmain where they asked me to try various things to fix the problem), they asked me to send the units to their repair centre in Europe. I know from following the tracking number that the faulty units arrived at the repair centre on Wednesday 3rd June. On Thursday 4th June I received a notification from Fedex of 2 brand new replacement units being shipped from China, which duly arrived here on Tuesday 9th June. They would have been here Monday 8th if it wasn't for a delay in customs. The replacement units are working perfectly. Whilst it's not good that I received two faulty units initially, in their credit they have replaced them very quickly and with no complications.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: philipma1957 on June 15, 2020, 01:40:48 AM
That was pretty good service on their part. Thank you for the follow up info.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: mikeywith on June 16, 2020, 12:58:32 AM
That was pretty good service on their part.
How was that a pretty good service? ;D, did they refund the shipping fees he paid to send those faulty hash boards to Europe? did they compensate him for the days of mining he lost? ya "pretty good" is a bit of a broad word, but for Bitmain to do it, I guess it's outstanding because we are not used to that kind of "okay service". With that being said, and despite that not being the best thing one would expect after paying a fortune for mining gear, I consider danieleither to be a lucky client who got VIP treatment, your chances of receiving the same thing are not so high. danieleither, glad you got your gears to run with all three boards, wish you luck with them.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: favebook on June 16, 2020, 01:30:25 AM
How was that a pretty good service? ;D, did they refund the shipping fees he paid to send those faulty hash boards to Europe? did they compensate him for the days of mining he lost? ya "pretty good" is a bit of a broad word, but for Bitmain to do it, I guess it's outstanding because we are not used to that kind of "okay service".
With that being said, and despite that not being the best thing one would expect after paying a fortune for mining gear, I consider danieleither to be a lucky client who got VIP treatment, your chances of receiving the same thing are not so high.
danieleither, glad you got your gears to run with all three boards, wish you luck with them.
I fully agree with you (bolded part). But I do not think that danieleither got a VIP treatment as I had the same treatment (twice for same unit) from Bitmain. But do not get me wrong, I do not think that is the best they could've done, but it was AWESOME comparing to what they have been doing over last few years.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: mikeywith on June 16, 2020, 02:41:18 AM
Well, let's call it a terrible choice of words on my behalf ;D. As far as I know, they hardly allow you to send the hashboard separately, and they will ask you to ship the whole machine, a few weeks ago someone complained about the same thing somewhere in this board, so it doesn't seem like they will always give you the option of sending the bad board while keeping the other working boards to reduce the loss, is it now okay to disassemble the miner without voiding the warranty? or is it a VIP thing? ;D
I don't claim to be an expert in this warranty process, I probably know the least about it among you guys, given the circumstances and the shipping cost to the nearest repair center, to me it has almost always been best to try to
1- Claim a coupon from them.
2- Fix the board by myself.
3- Throw them away (https://bitcointalk.org/index.php?topic=5254616.0).
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: favebook on June 16, 2020, 02:42:35 PM
[...]
Either I am reading it wrong or you know something I do not, but I think he sent a both machines that were faulty. Since I posted this a short while back, I feel it is only fair to post an update since the response from Bitmain has been reasonably impressive.
After a few days of initial troubleshooting (back and forth communication with Bitmain where they asked me to try various things to fix the problem), they asked me to send the units to their repair centre in Europe. I know from following the tracking number that the faulty units arrived at the repair centre on Wednesday 3rd June. On Thursday 4th June I received a notification from Fedex of 2 brand new replacement units being shipped from China, which duly arrived here on Tuesday 9th June. They would have been here Monday 8th if it wasn't for a delay in customs.
The replacement units are working perfectly. Whilst it's not good that I received two faulty units initially, in their credit they have replaced them very quickly and with no complications.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: Guinsanity on June 16, 2020, 03:59:44 PM
I wtb a couple of psu fans for my t17, two of then are not working
w40s12bmd5 from nidec
12vdc 0.64a
https://www.nidec.com/en/product/search/category/B101/M111/S100/NCJ-W40S12BMD5-5/
Anyone knows where to buy?
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: mikeywith on June 16, 2020, 04:44:08 PM
[...]
Ok my bad I thought he only sent the bad boards, this means he didn't get any special treatment, in fact I got a better deal on the faulty control board of my S17+ Despite them sending me this https://i.ibb.co/XXtCGcn/Return.png (https://i.ibb.co/XXtCGcn/Return.png) I insisted on sending only the control board and not the whole unit because I already had another control board to replace the bad one and I didn't want the gear to stop mining, and after a ton of "polite" arguments with them, I managed to get them to accept my request. They asked me to create a repair ticket to HongKong but send it to the Netherlands since it was the cheapest to send to from where the miner was located, once it was delivered I guess in 2-3 days they sent me an email with the tracking number for a control board from China at their expense, and then they refused to pay me for the shipping to the Netherlands but after being consistent - I managed to get a coupon from them. ;D With that being said, I still think they treat us terribly by sending us dead machines in the first place. [...]
You can get it on aliexpress for $12 https://www.aliexpress.com/item/32825983768.html or if you are in the U.S you can check with scott (https://bitcointalk.org/index.php?action=profile;u=1449095) if he doesn't have them he would probably be able to tell you where you can find them, make sure you get another spare those fans are not the best quality one can get and they eventually you will lose another fan.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: Scorpyy on June 17, 2020, 12:51:58 AM
Wait, you can actually get a coupon because you had to cover shipping expenses to their service location? ;D I haven't read that info anywhere.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: philipma1957 on June 17, 2020, 05:08:34 AM
I wtb a couple of psu fans for my t17, two of then are not working
w40s12bmd5 from nidec
12vdc 0.64a
https://www.nidec.com/en/product/search/category/B101/M111/S100/NCJ-W40S12BMD5-5/
Anyone knows where to buy?
delta makes one that should work it is 40x40x28. same size. it is .81 amp which is close to your spec. it is four pin. ebay item 283157645798 even if you dont order it from that seller you can look for part number.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: mikeywith on June 17, 2020, 11:59:01 AM
Wait, you can actually get a coupon because you had to cover shipping expenses to their service location? ;D I haven't read that info anywhere.
You can, if you know how to negotiate, in fact, i asked for 1- A new control board 2- A compensation for my shipping fee 3- A compensation for the downtime caused by their irresponsible actions. I got 1 and for 2 I got a coupon, and nothing for number 3. You see in reality when you pay for a brand new mining gear and it arrives broken, they should be responsible for all 3 points, but because of lack of competition and people not demanding their rights - Bitmain can keep treating their clients like shit. I have bought hundreds and hundreds of gears directly from their website, some are mine and some are for clients, maybe I get slightly better treatment than those who bought only 10 or 20 gears, but this doesn't stop anyone from demanding their rights from Bitmain, in the end, all you lose is a few emails back and forth.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: Scorpyy on June 17, 2020, 06:41:49 PM
Wait was it a DOA ( dead on arrival ) ? Or did they work for some-time?
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: mikeywith on June 17, 2020, 07:09:35 PM
It's complicated, so bear with me, the machine was DOA, I replaced the control board and the gear was hashing away, before changing the control board I sent them an email describing the issue hoping they would give me the recovery files to fix it, but no luck with the recovery, so I stopped talking to them and simply went along with replacing the control board (took a while for me to get the replacement), and I was busy then, so I didn't bother about it. Later on, in March I was like hey, I think Bitmain owe me a control board, so I sent them an email demanding all three points above, and this was their first reply Mar 5, 18:20 CST
Dear *************
Thanks for your consultation!
why did you not ship it back in Feb we found you consult with us in Feb if you send back to us at that time it will meet the DOA
We checked your miner did not belong to the DOA now, due to you did not create the repair ticket and send it back to us in time which we have advised you before
4. Please ship back them within 30 days from Order Ship out date, otherwise the devices cannot be treated as DOA.
we checked your SN which is exceed 30 days warranty
and for the DOA the 30 days is calculated from shipping date to creating repair ticket date ,but you still not created the repair ticket in our system
So to them and according to their rules, it was not DOA, so they wanted me to bear all costs, apparently, I didn't give a flying **** about that and went on with my daily negotiations, a few emails back and forth resulted in a new control board shipped from China and a coupon to compensate the shipping cost to the Netherlands. If it was considered DOA (me creating the repair ticket within 30 days from when they shipped it out) would they compensate the shipping cost without having to send Jessica a few emails? As I explained above, I don't know much about their warranty and DOA stuff, not even sure if what I got was a good deal or should I have asked for more?
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: Biodom on June 19, 2020, 01:34:40 AM
Hello, I have been reading every single answer to this interesting post. This is because I have also been framed by Bitmain with those S17+ antminers. I have some background in electronics and analyzing those intermittent failures that these miners have just got me a little confused, specially during a time that I checked control boards and data cables by disconnecting back and forth. At times the miner was full throttle mining just to drop after few hours. That in electronics is called a "cold soldering". Although there are not visible cold solderings I discovered that the soldering material that is being used on this S17 have 2 problems.
First, high amount of lead and low proportion of tin, and of course zero silver in the soldering material. This can be observed under the microscope used to soldering circuit boards. All of the solderings showed a greyish mate color and no shinning finish.
Second, below normal temperature of the soldering material, also leaves traces, specially on the hashing board chips. Also analyzed under the microscope there are traces that look like an sponge along with tiny cracks surrounding the chip's area at the surface of the hashing board.
So, this takes me into the conclusion that somebody at Bitmain's is trying to cut ends and by doing this they have compromised 50% of the S17, T17 series. The use of soldering with high percentage of plumb just tells me that they are throwing the cheapest crap they have to solder the components on those miners. Also they are trying to reduce electricity costs by not heating well enough the soldering material melted at the trays and this is specially true because the soldering material with higher proportion-ratio of lead instead of tin and silver takes colder temperatures to melt.
So taking all this into consideration I really recommend to all of those that are willing to throw the money into shipping costs, customs fees and no mining income, just don't do it because Bitmain still uses the same bad quality materials to fix it.
Since that soldering material is all over the hashing and controller boards is just a matter of time chips keep coming off the boards, the only and costly solution is to desoldering them all and soldering back with a good quality soldering flux, other than that those miners will keep failing over and over.
Basically most of the S17 series are doomed.
Since S9 had a pretty good reliability/longevity (on average), I wonder what is the cause of the apparently shoddy work done on these machines?
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: philipma1957 on June 19, 2020, 01:52:27 AM
Well the s9. had a lot of bad batches say 4 to 11 way back say. sept 2016.
It came out in April 2016. batches 1,2,3 were decent. Then a drop off.
but in feb 2017 on they got their shit together. They put out a lot of s9's they worked for 2 years or more.
The s15 and t15 came and gone quick under a year
The s17 and t17 lasted a year- 14 months . say April 2019 to June 2020
Now the s19 are out.
So no time spent on bettering the gear has been spent.
Also. I am willing to bet that. a ton of s17 gear was burnt due to too much over clock.
But that is another guess.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: Scorpyy on June 30, 2020, 01:38:46 PM
Here is the update on my situation.
T17e ordered, worked for 6-7 months. Dropped a board recently - out of warranty - will try to resolder chips as explained in this thread once i gather all knowledge and material.
2x T17+ - dropped almost all boards after 2 months of operation, sent to Netherlands for repair, shortly after we received info that replacement units have been sent out from China.
After 20 days of trouble with customs, we finally managed to get them in our possession. Customs inspected units and concluded that it were used ones and not new ones and asked for statement that we are importing operational units and not scrap (importing scrap is against the law). Both units were really dirty on 1 side, like it was stored in some warehouse for 3 years, i haven't inspected the inside but fans appeared to be clean. Its not just regular dust you can wipe it out, this appeared like it was glued to the miner. You could scratch it out only. Bitmain sent out replacement units within 2 days of receiving ours, and units arrived in our country in less then 2 days via DHL, so that was fast, but our customs delayed it a lot. Also one thing to notice is that Bitmain extended our warranty period for 18 days.
Shipping didn't cost us very much. I think total will be 80$ for shipping, and about 62$ for customs (for both units total). But the trouble we went trough has no price. Since we ordered as company we needed to provide a total of 12-17 documents ( statements, invoices, confirmations etc etc ) regarding export and import.
So, i was aware that Bitmain sent out same crappy gear and that it is just a matter of time before same issue re-occurs. I plugged in both miners. Both worked fine but then...
After 5 minutes = 1 miner dropped a board.
After 4 hours of mining = the other miner dropped 2 boards.
So conclusion is, replacement units were DOA, One miner works with 1 board, the other one works with 2 boards ( for now ). Both miners have exact same issue ( temp sensors ). I have contacted Bitmain and they told me to try and replace firmware ;D and if that didn't work they suggested me to send them again for repair but this time they will provide me with coupons for shipping fees. I don't mind sending the units back again for repair, but whats the point if we are going to bounce back-and forward this shitty gear until warranty expires.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: favebook on June 30, 2020, 03:07:02 PM
Both units were really dirty on 1 side, like it was stored in some warehouse for 3 years, i haven't inspected the inside but fans appeared to be clean. Its not just regular dust you can wipe it out, this appeared like it was glued to the miner. You could scratch it out only. Bitmain sent out replacement units within 2 days of receiving ours, and units arrived in our country in less then 2 days via DHL, so that was fast, but our customs delayed it a lot. Also one thing to notice is that Bitmain extended our warranty period for 18 days.
If in addition to your statement, the miner was oily or dirt had oily/wet look to it. You can be damn sure they used it in immersion (either Bitmain (for testing or otherwise) or some other customer which returned it for repair). Shipping didn't cost us very much. I think total will be 80$ for shipping, and about 62$ for customs (for both units total). But the trouble we went trough has no price. Since we ordered as company we needed to provide a total of 12-17 documents ( statements, invoices, confirmations etc etc ) regarding export and import.
So, i was aware that Bitmain sent out same crappy gear and that it is just a matter of time before same issue re-occurs. I plugged in both miners. Both worked fine but then...
After 5 minutes = 1 miner dropped a board.
After 4 hours of mining = the other miner dropped 2 boards.
So conclusion is, replacement units were DOA, One miner works with 1 board, the other one works with 2 boards ( for now ). Both miners have exact same issue ( temp sensors ). I have contacted Bitmain and they told me to try and replace firmware ;D and if that didn't work they suggested me to send them again for repair but this time they will provide me with coupons for shipping fees. I don't mind sending the units back again for repair, but whats the point if we are going to bounce back-and forward this shitty gear until warranty expires.
At this point (as you are a company ordering from other company), I'd politely ask for a big check of compensation for all the troubles (if they give you coupons, fight that as they are mostly useless unless you plan on supporting(buying from) them (which I wouldn't do if I had gone through all that) or ask to trade your DOA and broken machines for one of their new miners (if that works for you). If politeness does not work, you could threaten them with a legal action for sending broken machines as "new ones" and then failing to repair them, but that is totally up to you and I do not know how would that benefit you as you will probably lose a lot of time if you actually go through with it. But a little threat could work out in your favour if politeness does not as I previously stated. But it's always POLITENESS>threat. Also do not be afraid to politely tell them that even those units that are out of warranty need to be fixed. I paid only 40 USD or something silly like that for my S17 PRO (that broke twice in a span of 9 months). First repair was in warranty and was free ("only" 2 dead boards here) and second one was like 2-3 months out of INITIAL warranty (day when I got my first unit and not it's replacement) and as I said, I paid something silly while all three boards were dead (physically there was nothing wrong with them (I personally took them out, inspected them and filmed them from both sides and sent videos to Bitmain Support)). But they kept dropping at initialization 95% of the time. Also I should note that I tried with different control board but that did not fix or change the problem in any way. Only the PSU was untested as I didn't have a different one at that time.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: Scorpyy on June 30, 2020, 03:24:00 PM
you could threaten them with a legal action for sending broken machines as "new ones" and then failing to repair them,
I can't as terms from Bitmain say: 1.6 “Replacement Product” or “replacement product” means the Product of the same type or specifications provided to replace the defective Product or Product of the same brand with hash rates no less than that of the defective Product. Replacement Product may not be a new Product. The warranty period of the Replacement Product will be the remaining warranty period of the original Product calculated from the date of dispatch of the original Product, except when the warranty is voided in accordance with the terms and conditions of this Policy. https://service.bitmain.com/support/terms As for the state of miners, they are not oily, they are dusty. I can show pictures if anyone is interested. Regarding the first one T17e that dropped 1 board out of warranty - i think im gonna wait for it to drop more boards. But as i said whats the point in repairing if they are sending same crap back. I have made 2 proposals to Bitmain so far: 1) We send you DOA units, you replace with new series once available ( we can pay difference in value ) 2) We send or keep DOA units, you provide with coupons for new series once available. We expect coupon not to be below 60-70% of what we payed for 3 units, T17e 2x T17+. This seem fair and logical instead of sending crappy gear back and forward. Also we are risking our company to get fined for up to 10.000 USD because importing scrap equipment is against the law.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: favebook on June 30, 2020, 08:47:13 PM
Bad choice of words and word order on my side. What I meant is that they sent you NEW ones (ones you bought), and they were either DOA or broken in few days/weeks after NORMAL use (if that is the case, and I would assume it is). And about their so called "replacement product", they should work and not be DOA either, so that is another point you could make.
1) works much better for you imho
2) really bad idea if they give you 10% or 30% coupons. If they give you 50%+ coupons, that might be good for you.
*by % I do not mean % of what you spent, but rather the rule of coupon where you can use it to deduct only up to % of your new order*
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: Scorpyy on July 02, 2020, 05:03:19 PM
Ok so i decided to re-solder chips, however instead of going for every single chip i want to start with one that is already faulty. Does anyone know a way i can determine which one is it if there are no visible damages on the board? I want to gather all required information before i dissamble the miner.
@The_binary_Observer we need your expertise on this one.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: The_binary_Observer on July 03, 2020, 12:59:20 AM
Hello good friend Scorpyy, to begin with visual inspection is paramount. The most probably is that you will find at at least 1 chip falling off the hashing board, although I'm shure there is going to be more than one. The thing here is to touch, press and shake every heat sink on the hashing boards in order find those that are almost loose but not enough to fall by gravity. Most of the time if there is a complete hashing board not showing, if that is the case, chip number 1 and chip number 65 should be checked.
This is because the way the hashboards are designed, the chips circuitry works in series so if the first or the last chip of the chain fails the whole chain fails.
Some people say that if the temperature sensors on the hashing board fail the controller board does not activates that hashing board, the thing is that if there is 1 out of 4 temperature sensor working the controller stills start that hashing board and is very unlikely that all 4 temperature sensors fail all together.
Now, if you want to take this to the next level in order to be absolutely and completely sure about which component is causing the failure on your miner then you have to buy an special diagnostic device called universal test fixture that connects in series between the miner and a laptop or pc, from there you can start to determine what is exactly causing the hashing board not to start.
Depending of how many hashing boards you expect to repair and assuming that you are going to use the universal test fixture device along with a top quality soldering paste, soldering flux and hot air solder you may be spending around $400 dollars. However, I put you this way, there is a place in the U.S. that claims they repair S17 series hashing boards, they charge for EVERY hashboard repair service $350, plus shipping.
If you send at least 1 complete miner to Bitmain in Hong Kong you may be end paying $150 or $200 on shipping costs plus customs fees when they send back a new crappy miner which is not guaranteed to be 100% free of failure within the next 15 days of first start. However, if there is more than one complete miner to be shipped to Bitmain then do the math between buying the repair/diagnostic equipment or paying either 3rd party repair or shipping/customs costs to and from Hong Kong, you may be ending paying more than $400 and if your miner or miners fail again you are ready to fix them right away on the spot.
Also, I have found that the S17 series are shipped from Bitmain overclocked and that is one of the reasons they fail so much. All S17 use the same hashing chips, what makes them different is the clock speed and the number of chips on hashing boards. I have been running some testings with this S17 and S9 and I have been able to reach consistent and almost zero HW errors overclocking to 100 Th on S17+ and 20 Th on S9. Don't ask how I do reached those numbers because there is time and money invested on those tests that I am not willing to share. All I can tell is that if the above instructions, specially re-soldering the chips, are followed higher overclocking speeds can be safely achieved. By saying this I am really suspicious about the S19 series and their so called 110 Th. From my perspective it seems those S19's are nothing more than the same S17 with maybe couple of more chips per hashing board with an aggressive overclocking. Only time will tell if I'm wrong or not, I can't wait to see massive failure claims about those S19 in the coming weeks.
To end this post my advice to everyone ...save, your time, your money, your mental health and your soul STAY AWAY FROM BITMAIN PRODUCTS.
PS: Buy Kester soldering paste and soldering flux. Some people here maybe thinking... "this person works for Kester and that is why is recommending it" I don't work for that company but in my years of experience Kester soldering products have proven to be highly reliable.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: mileys1990 on July 03, 2020, 07:17:57 AM
I did order a new one and it ships whiting 20 days so i might end up with at least a month of an expensive gear sitting there doing pretty nothing but loses value. mobdro (https://get-mobdro.com)
tubemate (https://get-tubemate.com)
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: The_binary_Observer on July 03, 2020, 12:29:09 PM
I wish you the best of luck with that my dear friend.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: danieleither on July 04, 2020, 03:17:31 PM
I've recently taken delivery, and installed the following:
12 x T17+ 58T
24 x S17e 60T
These were all installed 1 week ago, and much to my surprise - all 36 units are working perfectly so far (they've been running 7 days). I was expecting at least a few to be DOA or drop hashboards within a few hours. Of course I realise that they can still fail, but anyone that understands the 'bathtub curve' will know that if a new piece of equipment is going to fail, it is most likely to do so very shortly after powering up (e.g. within a few hours).
It is of course early days, but it's a good sign that perhaps they have made improvements with the manufacturing / soldering process? These units are all from the Shenzhen factory.
It would be interesting to hear from some S19 owners about reliability so far, DOA units etc?
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: philipma1957 on July 04, 2020, 03:22:07 PM
I've recently taken delivery, and installed the following:
12 x T17+ 58T
24 x S17e 60T
These were all installed 1 week ago, and much to my surprise - all 36 units are working perfectly so far (they've been running 7 days). I was expecting at least a few to be DOA or drop hashboards within a few hours. Of course I realise that they can still fail, but anyone that understands the 'bathtub curve' will know that if a new piece of equipment is going to fail, it is most likely to do so very shortly after powering up (e.g. within a few hours).
It is of course early days, but it's a good sign that perhaps they have made improvements with the manufacturing / soldering process? These units are all from the Shenzhen factory.
It would be interesting to hear from some S19 owners about reliability so far, DOA units etc?
A lot depends on room temperatures. What is the hosting room at 25c or more?
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: Scorpyy on July 04, 2020, 04:50:36 PM
but anyone that understands the 'bathtub curve' will know that if a new piece of equipment is going to fail, it is most likely to do so very shortly after powering up (e.g. within a few hours).
My brand new units: 2 T17+ died within 2 months. 1 T17e died within 6 months. And as for the environmental temperatures it all happened during the winter so no worries on that side. I wish you good luck with those honestly.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: danieleither on July 04, 2020, 04:51:01 PM
Hard to say as I've gone for a passive cooling approach with this setup. Each miner has a double fan-duct on the rear, connected to 150mm ducting (approx 0.5m lengths) which in turn exhausts the hot air directly to the outside. The intake air temperature will be dependent on the air temperature outside, since there are large air vents on the intake side (drawing air from outside). Outside temperature has ranged from 10deg to 25deg over the past week. There is a small build-up of heat from the psu's which circulates back through the miners, and depending on wind conditions - it's possible some of the heated exhaust air may get drawn back into the miners from outside. https://i.imgur.com/SJyJsgk.jpg (https://i.imgur.com/SJyJsgk.jpg) https://i.imgur.com/9rKBov7.jpg (https://i.imgur.com/9rKBov7.jpg) https://i.imgur.com/WQNzOWo.jpg (https://i.imgur.com/WQNzOWo.jpg) https://i.imgur.com/5UjIPnB.jpg (https://i.imgur.com/5UjIPnB.jpg)
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: The_binary_Observer on July 04, 2020, 07:18:58 PM
It would be interesting to hear from some S19 owners about reliability so far, DOA units etc?
Tell you something, my parts supplier for bitmain miners just sent me a message last night related to the Universal Test Fixture software... They are working on an update to attend the new S19. So, what this tells me is that S19's are about to be the same story of the deceiving S17 series. Also. I am willing to bet that. a ton of s17 gear was burnt due to too much over clock.
You are absolutely correct !!!They were shipped overclocked straight out from Bitmain. Among the several tests I have been performing the last 10 months with those S17 series I have discovered that they are overclocked for several reasons but I am going to mention a couple of them. 1- The HW error factor is unusually higher than average, if there are no problems with the internet connection the next cause for this to happen is aggressive overclocking 2- The working temperature factor of the miner is too high even on controlled environment ( 23 degrees celsius ) or winter time, plus the fan speed is also too high 90% of the time.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: mikeywith on July 06, 2020, 09:57:08 PM
My brand new units:
2 T17+ died within 2 months.
1 T17e died within 6 months.
While I don't personally own many of those T17 series but you are not alone, EVERY single person I know that has those gears have had a very high failure rate, the only exception so far is S17pro, there is something special about those gears, maybe they are way underclocked and that's the reason why the solder paste is still holding well. my parts supplier for bitmain miners just sent me a message last night related to the Universal Test Fixture software... They are working on an update to attend the new S19. So, what this tells me is that S19's are about to be the same story of the deceiving S17 series.
Let me guess, was it Kevin from www.zeusbtc.com? if he tells you that the S19 are as terrible as the 17 series I would believe him without a single doubt, but the fact that they are developing a tool/firmware to fix those gears doesn't really indicate anything bad about them, the proof is, the first fixture tool they made was for S9 and we all know how robust those gears were. I hope that nobody is expecting Japanese or German standards from Bitmain whereby nothing will go wrong at all, I will be happy with something that is as good as S9, although I highly doubt I will ever touch Bitmain gears ever again.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: The_binary_Observer on July 08, 2020, 12:47:23 AM
mikeywith, from my personal point of view as you said about S9, those are the best miners from Bitmain and that tool was released after the S9 was first released. However, taking into consideration the connections this provider may have and more specifically inside Bitmain, the only fact that they are developing a software update to cover something that hasn't even hit the markets yet, thus nobody should know how those series will perform, it tells me they know something about it or may have a beforehand information and want to be ready when that happens, specially the Chinese.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: mikeywith on July 08, 2020, 02:21:20 PM
FYI S19s have been in the market for quite sometime, enough time to start building a fixture tool or any other related projects , i don't confirm or deny the theory you just stated, in fact, i tend to agree to it, i know the Chinese get special treatment from bitmain, i just don't know how special that can be, with that being said i am by no means trying to defend the quality of these 19 series.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: danieleither on July 19, 2020, 12:49:36 AM
Could somebody advise the correct fan type for 17 series power supplies or post a link? I have some faulty fans on my T17+ which I need to replace. They're out of warranty so I'll do it myself.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: philipma1957 on July 19, 2020, 12:47:28 PM
Could somebody advise the correct fan type for 17 series power supplies or post a link? I have some faulty fans on my T17+ which I need to replace. They're out of warranty so I'll do it myself.
this is good https://shop.bitmain.com/product/detail?pid=000201910151107519921qKMCqzJ06A8 buy extra and buy these https://shop.bitmain.com/product/detail?pid=00020200612174640197fvX6QXWM06AB
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: mikeywith on July 19, 2020, 05:55:18 PM
Phill those are 12cm fans for the miner itself, he is looking for Apw9' fans those small once 4cm square, can be found here https://m.tr.aliexpress.com/item/4000204047398.html
Where are you located? I will try to find a supplier in your area.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: philipma1957 on July 19, 2020, 06:28:40 PM
Missed that thanks.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: danieleither on July 19, 2020, 08:21:13 PM
Thank you - that's all the info I need, I can source it here or an equivalent :)
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: Guinsanity on July 20, 2020, 04:21:09 PM
What you guys think about this
https://www.aliexpress.com/item/4000112386858.html
For a complete noob into electronics and so, this is a good course? theres a placa that i can found free material teaching how to reapair asics and psus?
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: philipma1957 on July 20, 2020, 04:42:28 PM
You need more than courses.
You will need tools 🧰.
You will need meters.
You will need a work station 🚉
In a clean room.
A lot of repair is desoldering of asics then soldering them back correctly.
Do you have good eyesight?
It helps to be able to do good close up work.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: Guinsanity on July 20, 2020, 05:02:30 PM
I can have all of this, i have a good environment and a separated clean space in my farm, its just to know where to start and what to buy and so on.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: mikeywith on July 21, 2020, 06:34:01 AM
I can have all of this, i have a good environment and a separated clean space in my farm, its just to know where to start and what to buy and so on.
Obviosully I don't know what is inside the paid that course, my guess is that there is nothing worth buying in there, you can find free tutorials both videos and written format in https://www.zeusbtc.com/ the list of tools can be easily known by watching one of their videos fixing a miner, it's mainly 1- The fixture tool 2- A multimeter ( some specific models) 3- Heatgun 4- Solder paste Those are off the top of my head, watch the videos and write down all the tools they use.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: BitMaxz on July 21, 2020, 11:47:05 PM
It doesn't need this course if he knows the basic things about Electronics and I think the other guide inside the course I think is how to flash the miner with SD card and how to upgrade the miner through web GUI. He will need some repair kit for repairing like this image below. https://i.imgur.com/IPPybo4.png (https://i.imgur.com/IPPybo4.png) For hardware related issues and SD card for software and fixture tool for diagnosing or finding the hashboard issue.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: Guinsanity on July 22, 2020, 01:50:29 PM
The tool to check chip problems is the same for s9/s17 and so on?
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: mikeywith on July 22, 2020, 02:29:28 PM
[...]
This kit contains a few unneccessery stuff like Antistatic mat, gloves and even the DC power supply isn't needed here, he could use the miner's PSU, if he would open a repair shop he could probably invest in all those tools, but to simply fix your own miners and perhabs some of your friends', then my suggestion is to watch the repair videos and write down a list of the things they use. Also if you are planning on buying the test fixture tool, I suggest you wait for a while, the latest one they have now is for the 17 series and S9/T9, and I am sure pretty soon they will make one for the 19 series, you might need that later on when you buy S19/S19pro/T19 gears, it would be cheaper to buy it once than having to buy it again when the time comes.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: amirheavy666 on July 30, 2020, 09:12:58 PM
Try using Asic.to firmware and undervolt or overvolt it a bit. That seemed to be a fix in most instances. Also, if that does not work, try lower frequency with higher voltage.
Dear favebook, please advise how try lower frequncey with higher voltage .. i have two t17+, it works with 3 chains without problem for only 3 days and after that one chip for each T17+ have 0 instead of 44. so with try lower frequency with higher voltage it have been solved ? how do this thing? please guide ....thanks.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: favebook on July 30, 2020, 11:03:18 PM
First you have to install asic.to firmware (join Telegram group if you need help or read original thread - it has good tutorial): https://bitcointalk.org/index.php?topic=5208500.0.
Then you can choose one of presets (OC/DC) or you can manually type what frequency and voltage you want.
Keep in mind that this firmware is free but it has fee of 3% afaik.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: Scorpyy on September 09, 2020, 10:35:06 AM
Bitmain is sending me DOA units from repair all the time. And now one unit is 2nd DOA. Really not fair from their side, i am paying all shipping and everything so we can bounce back and forward scrap units. And their coupons mean nothing at this point as not only that they dont have anything else for sale but it is questionable that i will even consider ordering anything from them again.
Does anyone know any e-mail / website for local authorities in China who can assist in here? Cause if they can't fix it, i want a refund.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: The_binary_Observer on September 09, 2020, 06:38:55 PM
What makes you think that there is a slight chance you can even be taken into consideration by chinese authorities? You are dealing with a comunist regime who participates in every aspect of local and national economy and business. The comunist party owns every company in China even bitmain which is highly profitable in every aspect of the chinese economy and energy industry. Not even in your wildest dreams any action against bitmain will go thru using the Chinese authorities. However, in the USA there is a legal figure called "Class Suit Action" and in this particular case it perfectly fits what it was created for.
All what is needed is several of us all together to file a legal suit against bitmain in the USA for wrongful and deceiving selling practices by selling and distributing defective merchandise and offering no warranty in the USA.
Bitmain is registered in the USA as a company so if there is a substantial number of people filling for a class suit action we may, at least, receive a full refund even if some time have passed.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: Scorpyy on September 09, 2020, 08:51:11 PM
Well nothing much really, but at this point i have nothing to lose. Returned them 2 units, 2 units came back. Both died within few hours. Again sent them 1 of them, i decided to keep one that works somehow with 2 boards, and the last one came in also malfunctioning ( works with 1 board ). I still can send it back for repair once again but whats the point? They will always send scrap back and that is obvious. I can also include some international authorities, i mean they can't just get away with this that easily by producing and selling scrap.
I just need some agencies, local or international. But the thing is i know that they can always say that they sent out a working replacement and that it died during transport and we can't do anything about it. If they wanted to find a solution they would, but they don't want. Its much cheaper for them to pretend that they are fixing units until the end of the warranty period.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: mikeywith on September 09, 2020, 09:39:52 PM
Bitmain is sending me DOA units from repair all the time. And now one unit is 2nd DOA. Really not fair from their side, i am paying all shipping and everything so we can bounce back and forward scrap units. And their coupons mean nothing at this point as not only that they dont have anything else for sale but it is questionable that i will even consider ordering anything from them again.
It shouldn't be just "questionable" at this point, it should be "certain". I have totally lost faith in Bitmain since last year, since the day they started using terrible thermal paste/solder and low-quality PSUs, I encountered a huge loss and 90% of the miners I bought from Bitmain except for S9/S9i/S9j have either lost a board or two, got a toasted PSU, arrived with fallen heatsinks, they are complete trash and everyone who doesn't plan on losing money on purpose should AVOID Bitmain for now and probably months/years to come. Does anyone know any e-mail / website for local authorities in China who can assist in here? Cause if they can't fix it, i want a refund.
I wouldn't take this route, I suggest you stay consistent in your communications with them, send them as many Emails as needed, be patient and polite and request a FULL refund at first, and then slowly settle down for less, negotiating with Bitmain is like negotiating with a hawker, it's nothing like the other professional multi-billion enterprises, so you need to use a different way of communicating and if you are persistent and consistent you will at least manage to get some refund in the end.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: Scorpyy on September 15, 2020, 10:30:16 AM
Man i wish i could bring any good news but i submitted all documentation, was polite, sent tons of e-mails, told them that we had 3k+ usd in expenses due to fail equipment and 300+ USD in expenses due to DOA returned units.
And you know what their response was?
"we double checked with our leader we can apply for 23USD coupon for you " IS THIS A JOKE?
And then guess what, they doubled it:
"sorry what we can max compensate is 50 usd "
This has to be a joke? Jessica L. is bored and she-s joking with me.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: NotFuzzyWarm on September 15, 2020, 01:01:28 PM
Nope, not joking. That ^^ kind of stunts is why I stopped using BM gear years ago. Much prefer MicroBT (Whatsminers) and Canaan (Avalons). MicroBT are more efficient but the Avalons are better built.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: Scorpyy on September 15, 2020, 02:20:42 PM
you will at least manage to get some refund in the end.
When you said some refund i wasn't thinking about value equal to 2 large pizza-s and a coca cola. And the value is in COUPON. Not only that they don't have anything for sale for months but also why would i even consider buying from them again.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: philipma1957 on September 15, 2020, 03:51:23 PM
you must be persistent
be patient
be professional
be persuasive
be polite.
tell them that 50usd is far too small.
ask for 1000usd in btc to an address for a refund
you are in for 3300 and have two working boards.
you should get 2200 usd
but are willing to take 1000usd.
point to this thread. tell them they have given much larger amounts to other customers.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: mikeywith on September 16, 2020, 10:49:20 AM
Oh boy, a $50 coupon to make up for $3300 loss is nuts, i was not expecting them to send you a full refund, not even a half but most certainly not a $50 coupons.
It seems like they have gone broke or lost a ton of money during the past a few months, but you stay on it, stay persistent don't give up just yet.
Tell them you will go to court for this if they don't refund you some serious amount.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: PopoJeff on September 18, 2020, 09:55:15 PM
Rather than wait for Bitmain repair location to open post-covid to fix my DOA claim, I just sold my unit on eBay.
The S17+ 70 I got cost me less than $200 after applying Bitmain credit. It arrived with one dead board.
I got $650 for it on eBay.
And bought a S17+73 from a friend for $650.
All in all..... it was much better than dealing with Bitmain
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: wndsnb on October 06, 2020, 02:58:47 PM
I've had 2 out of 7 S17 Pros that came from Malaysia go down. One was RMAed to the CA site months ago ... still waiting for updates. The other one I just picked up from my host to try to fix myself. My host did all they could do and had no luck.
Interestingly, I have 10 S17s and 3 S17pros that came from China at a host in Canada and not a single one has gone down. Wondering if quality control at the Malaysia plant is not so good...
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: mikeywith on October 06, 2020, 05:18:42 PM
As far as I know, Bitmain doesn't make any mining gears in Malaysia, it's probably just a sorting hub to reduce import/tax costs for countries that aren't so friendly with goods coming in directly from China, what happened to you was probably nothing but a bad luck with one of the batches, Someone said that the recent batches are slightly better build as far as the thermal/glue is is concerned, which does make sense.
Please keep us updated with your attempt to fix this broken S17 pro, if possible, describe the issues you are facing just in case someone had the same problem and they could help you fix it.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: NotFuzzyWarm on October 06, 2020, 05:29:30 PM
As far as I know, Bitmain doesn't make any mining gears in Malaysia, it's probably just a sorting hub to reduce import/tax costs for countries that aren't so friendly with goods coming in directly from China, Incorrect. The Trump Tax tariff and ones from a few other countries forbid that by using Country of Origin as the deciding factor. That means where the miners are assembled so BM does have at least 1 assembly plant in Malaysia that does at least final assembly of them using parts made in China. Given the quality issues they may also stuff the hash boards there...
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: mikeywith on October 06, 2020, 08:00:38 PM
I stand corrected then, I confrimed from a Malaysian source that Bitmain does indeed assemble some of it's miners in Malaysia, still "assembly" is quite a broad word as in we don't know to which level of assembly they go to.
I still think the quality isn't very different because 90% of the issues that all of these 17 series gears have in common is the thermal paste/solder, whereby the whole chip fall down or just the heatsink drops (both lead to a none-working hash board) I highly doubt soldering the chips nor glueing the heatsinks on them is done in Malaysia, it's more likely that they receive ready to use hash boards, control boards, PSUs and a bunch of screws and all they do is put them all together, and just by doing so, you can't really harm the hash boars unless you intentionally do it, and even then, you need a lot of time and effort.
on the other hand, if the assembly goes to a much lower level like soldering the chips and all, then the difference in quality will vary greatly, however, all the 17 series gears I ordered came from China, and the quality is terrible overall, so I still believe it's a matter of luck after all.
I shall confirm what does actually happen in the warehouse of Malaysia in a few days, will keep you updated.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: philipma1957 on October 06, 2020, 08:15:43 PM
Maybe you don't let us know. Since you never know who is reading this.
My partner buysolar got a 700 import tax bill today. I am hoping I don't get any bills for the gear I purchased last fall.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: mikeywith on October 06, 2020, 10:46:51 PM
I don't think that is confidential information, assembling thousands of miners isn't something you can keep a secret, unless specified otherwise by my source then i will not reveal the information.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: wndsnb on October 06, 2020, 11:16:31 PM
Yeah, this miner even has a label saying it was made in Malaysia. https://i.imgur.com/dPPCwsG.png (https://i.imgur.com/dPPCwsG.png) My host reported that some heatsinks had fallen off. They put them back on but it still did not come back up completely, reporting 0 asics on two of the hashboards and some temperature sensor issues. Just hooked it up last night and it came up just fine ran for about 30 minutes and then died. So already better than what my host was reporting. Maybe the bumping around/vibration from the 8 hours of being in my car on the drive home did it some good. After it died, I updated it to the latest firmware and started it back up before going to bed. It was still running when I got up this morning. It's reasonably cool here so fans are running around 50%. I'm going to figure out a way to limit cooling to stress test it before I declare it fixed. Here's the log where it ran for 30 min then went dead: Booting Linux on physical CPU 0x0
Linux version 4.6.0-xilinx-gff8137b-dirty (lzq@armdev2) (gcc version 4.8.3 20140320 (prerelease) (Sourcery CodeBench Lite 2014.05-23) ) #25 SMP PREEMPT Fri Nov 23 15:30:52 CST 2018
CPU: ARMv7 Processor [413fc090] revision 0 (ARMv7), cr=18c5387d
CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
Machine model: Xilinx Zynq
cma: Reserved 16 MiB at 0x0e000000
Memory policy: Data cache writealloc
On node 0 totalpages: 61440
free_area_init_node: node 0, pgdat c0b39280, node_mem_map cde10000
Normal zone: 480 pages used for memmap
Normal zone: 0 pages reserved
Normal zone: 61440 pages, LIFO batch:15
percpu: Embedded 12 pages/cpu @cddf1000 s19776 r8192 d21184 u49152
pcpu-alloc: s19776 r8192 d21184 u49152 alloc=12*4096
pcpu-alloc: [0] 0 [0] 1
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 60960
Kernel command line: mem=240M console=ttyPS0,115200 ramdisk_size=33554432 root=/dev/ram rw earlyprintk
PID hash table entries: 1024 (order: 0, 4096 bytes)
Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
Memory: 190264K/245760K available (6345K kernel code, 231K rwdata, 1896K rodata, 1024K init, 223K bss, 39112K reserved, 16384K cma-reserved, 0K highmem)
Virtual kernel memory layout:
vector : 0xffff0000 - 0xffff1000 ( 4 kB)
fixmap : 0xffc00000 - 0xfff00000 (3072 kB)
vmalloc : 0xcf800000 - 0xff800000 ( 768 MB)
lowmem : 0xc0000000 - 0xcf000000 ( 240 MB)
pkmap : 0xbfe00000 - 0xc0000000 ( 2 MB)
modules : 0xbf000000 - 0xbfe00000 ( 14 MB)
.text : 0xc0008000 - 0xc090c424 (9234 kB)
.init : 0xc0a00000 - 0xc0b00000 (1024 kB)
.data : 0xc0b00000 - 0xc0b39fe0 ( 232 kB)
.bss : 0xc0b39fe0 - 0xc0b71c28 ( 224 kB)
Preemptible hierarchical RCU implementation.
Build-time adjustment of leaf fanout to 32.
RCU restricting CPUs from NR_CPUS=4 to nr_cpu_ids=2.
RCU: Adjusting geometry for rcu_fanout_leaf=32, nr_cpu_ids=2
NR_IRQS:16 nr_irqs:16 16
efuse mapped to cf800000
ps7-slcr mapped to cf802000
L2C: platform modifies aux control register: 0x72360000 -> 0x72760000
L2C: DT/platform modifies aux control register: 0x72360000 -> 0x72760000
L2C-310 erratum 769419 enabled
L2C-310 enabling early BRESP for Cortex-A9
L2C-310 full line of zeros enabled for Cortex-A9
L2C-310 ID prefetch enabled, offset 1 lines
L2C-310 dynamic clock gating enabled, standby mode enabled
L2C-310 cache controller enabled, 8 ways, 512 kB
L2C-310: CACHE_ID 0x410000c8, AUX_CTRL 0x76760001
zynq_clock_init: clkc starts at cf802100
Zynq clock init
sched_clock: 64 bits at 333MHz, resolution 3ns, wraps every 4398046511103ns
clocksource: arm_global_timer: mask: 0xffffffffffffffff max_cycles: 0x4ce07af025, max_idle_ns: 440795209040 ns
Switching to timer-based delay loop, resolution 3ns
clocksource: ttc_clocksource: mask: 0xffff max_cycles: 0xffff, max_idle_ns: 537538477 ns
ps7-ttc #0 at cf80a000, irq=18
Console: colour dummy device 80x30
Calibrating delay loop (skipped), value calculated using timer frequency.. 666.66 BogoMIPS (lpj=3333333)
pid_max: default: 32768 minimum: 301
Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
CPU: Testing write buffer coherency: ok
CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
Setting up static identity map for 0x100000 - 0x100058
CPU1: failed to boot: -1
Brought up 1 CPUs
SMP: Total of 1 processors activated (666.66 BogoMIPS).
CPU: All CPU(s) started in SVC mode.
devtmpfs: initialized
VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4
clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
pinctrl core: initialized pinctrl subsystem
NET: Registered protocol family 16
DMA: preallocated 256 KiB pool for atomic coherent allocations
cpuidle: using governor menu
hw-breakpoint: found 5 (+1 reserved) breakpoint and 1 watchpoint registers.
hw-breakpoint: maximum watchpoint size is 4 bytes.
zynq-ocm f800c000.ps7-ocmc: ZYNQ OCM pool: 256 KiB @ 0xcf880000
vgaarb: loaded
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
media: Linux media interface: v0.10
Linux video capture interface: v2.00
pps_core: LinuxPPS API ver. 1 registered
pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
PTP clock support registered
EDAC MC: Ver: 3.0.0
Advanced Linux Sound Architecture Driver Initialized.
clocksource: Switched to clocksource arm_global_timer
NET: Registered protocol family 2
TCP established hash table entries: 2048 (order: 1, 8192 bytes)
TCP bind hash table entries: 2048 (order: 2, 16384 bytes)
TCP: Hash tables configured (established 2048 bind 2048)
UDP hash table entries: 256 (order: 1, 8192 bytes)
UDP-Lite hash table entries: 256 (order: 1, 8192 bytes)
NET: Registered protocol family 1
RPC: Registered named UNIX socket transport module.
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
PCI: CLS 0 bytes, default 64
Trying to unpack rootfs image as initramfs...
rootfs image is not initramfs (no cpio magic); looks like an initrd
Freeing initrd memory: 26072K (cc18b000 - cdb01000)
hw perfevents: enabled with armv7_cortex_a9 PMU driver, 7 counters available
futex hash table entries: 512 (order: 3, 32768 bytes)
workingset: timestamp_bits=28 max_order=16 bucket_order=0
jffs2: version 2.2. (NAND) (SUMMARY) © 2001-2006 Red Hat, Inc.
io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered (default)
dma-pl330 f8003000.ps7-dma: Loaded driver for PL330 DMAC-241330
dma-pl330 f8003000.ps7-dma: DBUFF-128x8bytes Num_Chans-8 Num_Peri-4 Num_Events-16
e0000000.serial: ttyPS0 at MMIO 0xe0000000 (irq = 158, base_baud = 6249999) is a xuartps
console [ttyPS0] enabled
xdevcfg f8007000.ps7-dev-cfg: ioremap 0xf8007000 to cf86e000
[drm] Initialized drm 1.1.0 20060810
brd: module loaded
loop: module loaded
CAN device driver interface
gpiod_set_value: invalid GPIO
libphy: MACB_mii_bus: probed
macb e000b000.ethernet eth0: Cadence GEM rev 0x00020118 at 0xe000b000 irq 31 (00:0a:35:00:00:00)
Generic PHY e000b000.etherne:00: attached PHY driver [Generic PHY] (mii_bus:phy_addr=e000b000.etherne:00, irq=-1)
e1000e: Intel(R) PRO/1000 Network Driver - 3.2.6-k
e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
ehci-pci: EHCI PCI platform driver
usbcore: registered new interface driver usb-storage
mousedev: PS/2 mouse device common for all mice
i2c /dev entries driver
Xilinx Zynq CpuIdle Driver started
sdhci: Secure Digital Host Controller Interface driver
sdhci: Copyright(c) Pierre Ossman
sdhci-pltfm: SDHCI platform and OF driver helper
mmc0: SDHCI controller on e0100000.ps7-sdio [e0100000.ps7-sdio] using ADMA
ledtrig-cpu: registered to indicate activity on CPUs
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
nand: device found, Manufacturer ID: 0x2c, Chip ID: 0xda
nand: Micron MT29F2G08ABAGAWP
nand: 256 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 128
nand: WARNING: pl35x-nand: the ECC used on your system is too weak compared to the one required by the NAND chip
Bad block table found at page 131008, version 0x01
Bad block table found at page 130944, version 0x01
6 ofpart partitions found on MTD device pl35x-nand
Creating 6 MTD partitions on "pl35x-nand":
0x000000000000-0x000002800000 : "BOOT.bin-env-dts-kernel"
0x000002800000-0x000004800000 : "ramfs"
0x000004800000-0x000005000000 : "configs"
0x000005000000-0x000006000000 : "reserve"
0x000006000000-0x000008000000 : "ramfs-bak"
0x000008000000-0x000010000000 : "reserve1"
NET: Registered protocol family 10
sit: IPv6 over IPv4 tunneling driver
NET: Registered protocol family 17
can: controller area network core (rev 20120528 abi 9)
NET: Registered protocol family 29
can: raw protocol (rev 20120528)
can: broadcast manager protocol (rev 20120528 t)
can: netlink gateway (rev 20130117) max_hops=1
zynq_pm_ioremap: no compatible node found for 'xlnx,zynq-ddrc-a05'
zynq_pm_late_init: Unable to map DDRC IO memory.
Registering SWP/SWPB emulation handler
hctosys: unable to open rtc device (rtc0)
ALSA device list:
No soundcards found.
RAMDISK: gzip image found at block 0
EXT4-fs (ram0): couldn't mount as ext3 due to feature incompatibilities
EXT4-fs (ram0): mounted filesystem without journal. Opts: (null)
VFS: Mounted root (ext4 filesystem) on device 1:0.
devtmpfs: mounted
Freeing unused kernel memory: 1024K (c0a00000 - c0b00000)
EXT4-fs (ram0): re-mounted. Opts: block_validity,delalloc,barrier,user_xattr
random: dd urandom read with 0 bits of entropy available
ubi0: attaching mtd2
ubi0: scanning is finished
ubi0: attached mtd2 (name "configs", size 8 MiB)
ubi0: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
ubi0: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
ubi0: VID header offset: 2048 (aligned 2048), data offset: 4096
ubi0: good PEBs: 64, bad PEBs: 0, corrupted PEBs: 0
ubi0: user volume: 1, internal volumes: 1, max. volumes count: 128
ubi0: max/mean erase counter: 2/1, WL threshold: 4096, image sequence number: 1099087952
ubi0: available PEBs: 0, total reserved PEBs: 64, PEBs reserved for bad PEB handling: 40
ubi0: background thread "ubi_bgt0d" started, PID 708
UBIFS (ubi0:0): background thread "ubifs_bgt0_0" started, PID 711
UBIFS (ubi0:0): recovery needed
UBIFS (ubi0:0): recovery completed
UBIFS (ubi0:0): UBIFS: mounted UBI device 0, volume 0, name "configs"
UBIFS (ubi0:0): LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
UBIFS (ubi0:0): FS size: 1396736 bytes (1 MiB, 11 LEBs), journal size 888833 bytes (0 MiB, 5 LEBs)
UBIFS (ubi0:0): reserved for root: 65970 bytes (64 KiB)
UBIFS (ubi0:0): media format: w4/r0 (latest is w4/r0), UUID CD1BC056-7E24-4E3E-BCAF-EAA178A77B8B, small LPT model
ubi1: attaching mtd5
ubi1: scanning is finished
ubi1: attached mtd5 (name "reserve1", size 128 MiB)
ubi1: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
ubi1: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
ubi1: VID header offset: 2048 (aligned 2048), data offset: 4096
ubi1: good PEBs: 1020, bad PEBs: 4, corrupted PEBs: 0
ubi1: user volume: 1, internal volumes: 1, max. volumes count: 128
ubi1: max/mean erase counter: 972/211, WL threshold: 4096, image sequence number: 4185749592
ubi1: available PEBs: 0, total reserved PEBs: 1020, PEBs reserved for bad PEB handling: 36
ubi1: background thread "ubi_bgt1d" started, PID 720
UBIFS (ubi1:0): background thread "ubifs_bgt1_0" started, PID 723
UBIFS (ubi1:0): recovery needed
UBIFS (ubi1:0): recovery completed
UBIFS (ubi1:0): UBIFS: mounted UBI device 1, volume 0, name "reserve1"
UBIFS (ubi1:0): LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
UBIFS (ubi1:0): FS size: 123039744 bytes (117 MiB, 969 LEBs), journal size 6221824 bytes (5 MiB, 49 LEBs)
UBIFS (ubi1:0): reserved for root: 4952683 bytes (4836 KiB)
UBIFS (ubi1:0): media format: w4/r0 (latest is w4/r0), UUID 4829CF2C-7435-4146-B2FD-0826AAE8443A, small LPT model
IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
macb e000b000.ethernet eth0: unable to generate target frequency: 25000000 Hz
macb e000b000.ethernet eth0: link up (100/Full)
IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
In axi fpga driver!
request_mem_region OK!
AXI fpga dev virtual address is 0xcfb38000
*base_vir_addr = 0xab011
In fpga mem driver!
request_mem_region OK!
fpga mem virtual address is 0xd2000000
random: nonblocking pool is initialized
2020-10-06 00:22:35 driver-btm-api.c:773:init_freq_mode: This is scan-user version
2020-10-06 00:22:35 driver-btm-api.c:1891:bitmain_soc_init: opt_multi_version = 1
2020-10-06 00:22:35 driver-btm-api.c:1892:bitmain_soc_init: opt_bitmain_ab = 1
2020-10-06 00:22:35 driver-btm-api.c:1893:bitmain_soc_init: opt_bitmain_work_mode = 1
2020-10-06 00:22:35 driver-btm-api.c:1894:bitmain_soc_init: Miner compile time: Mon May 27 10:57:13 CST 2019 type: Antminer S17 Pro
2020-10-06 00:22:35 driver-btm-api.c:1895:bitmain_soc_init: commit version: c0bb7cc 2019-05-23 10:59:44, build by: lol 2019-05-27 11:08:02
2020-10-06 00:22:35 driver-btm-api.c:1778:show_sn: no SN got, please write SN to /nvdata/sn
2020-10-06 00:22:35 driver-btm-api.c:1251:miner_device_init: Detect 256MB control board of XILINX
2020-10-06 00:22:35 driver-btm-api.c:1199:init_fan_parameter: fan_eft : 0 fan_pwm : 0
2020-10-06 00:22:35 thread.c:627:create_read_nonce_reg_thread: create thread
2020-10-06 00:22:41 driver-btm-api.c:1183:init_miner_version: miner ID : 800a1dce57408854
2020-10-06 00:22:41 driver-btm-api.c:1189:init_miner_version: FPGA Version = 0xB011
2020-10-06 00:22:47 driver-btm-api.c:835:get_product_id: product_id[0] = 0
2020-10-06 00:22:47 driver-btm-api.c:835:get_product_id: product_id[1] = 0
2020-10-06 00:22:47 driver-btm-api.c:835:get_product_id: product_id[2] = 0
2020-10-06 00:22:47 driver-btm-api.c:786:_set_project_type: project:0
2020-10-06 00:22:47 driver-btm-api.c:811:_set_project_type: Project type: Antminer S17 Pro
2020-10-06 00:22:47 driver-btm-api.c:822:dump_pcb_bom_version: Chain [0] PCB Version: 0x0101
2020-10-06 00:22:47 driver-btm-api.c:823:dump_pcb_bom_version: Chain [0] BOM Version: 0x0103
2020-10-06 00:22:47 driver-btm-api.c:822:dump_pcb_bom_version: Chain [1] PCB Version: 0x0101
2020-10-06 00:22:47 driver-btm-api.c:823:dump_pcb_bom_version: Chain [1] BOM Version: 0x0103
2020-10-06 00:22:47 driver-btm-api.c:822:dump_pcb_bom_version: Chain [2] PCB Version: 0x0101
2020-10-06 00:22:47 driver-btm-api.c:823:dump_pcb_bom_version: Chain [2] BOM Version: 0x0103
2020-10-06 00:22:48 driver-btm-api.c:1841:bitmain_board_init: Fan check passed.
2020-10-06 00:22:50 board.c:36:jump_and_app_check_restore_pic: chain[0] PIC jump to app
2020-10-06 00:22:53 board.c:40:jump_and_app_check_restore_pic: Check chain[0] PIC fw version=0xb9
2020-10-06 00:22:55 board.c:36:jump_and_app_check_restore_pic: chain[1] PIC jump to app
2020-10-06 00:22:58 board.c:40:jump_and_app_check_restore_pic: Check chain[1] PIC fw version=0xb9
2020-10-06 00:23:00 board.c:36:jump_and_app_check_restore_pic: chain[2] PIC jump to app
2020-10-06 00:23:03 board.c:40:jump_and_app_check_restore_pic: Check chain[2] PIC fw version=0xb9
2020-10-06 00:23:03 thread.c:622:create_pic_heart_beat_thread: create thread
2020-10-06 00:23:03 power_api.c:55:power_init: power init ...
2020-10-06 00:23:03 driver-btm-api.c:1851:bitmain_board_init: Enter 30s sleep to make sure power release finish.
2020-10-06 00:23:35 power_api.c:164:set_iic_power_to_highest_voltage: setting to voltage: 21.00 ...
2020-10-06 00:23:41 power_api.c:113:set_iic_power_by_voltage: now setting voltage to : 21.000000
2020-10-06 00:23:53 driver-btm-api.c:1126:check_asic_number_with_power_on: Chain[0]: find 48 asic, times 0
2020-10-06 00:24:05 driver-btm-api.c:1126:check_asic_number_with_power_on: Chain[1]: find 48 asic, times 0
2020-10-06 00:24:17 driver-btm-api.c:1126:check_asic_number_with_power_on: Chain[2]: find 48 asic, times 0
2020-10-06 00:24:17 driver-btm-api.c:336:set_order_clock: chain[0]: set order clock, stragegy 3
2020-10-06 00:24:17 driver-btm-api.c:336:set_order_clock: chain[1]: set order clock, stragegy 3
2020-10-06 00:24:17 driver-btm-api.c:336:set_order_clock: chain[2]: set order clock, stragegy 3
2020-10-06 00:24:22 driver-hash-chip.c:453:set_clock_delay_control: core_data = 0x34
2020-10-06 00:24:22 voltage[0] = 1800
2020-10-06 00:24:22 voltage[1] = 1800
2020-10-06 00:24:22 voltage[2] = 1800
2020-10-06 00:24:22 power_api.c:76:set_working_voltage: working_voltage = 18.000000
2020-10-06 00:24:24 temperature.c:267:calibrate_temp_sensor_one_chain: Temperature sensor calibration: chain 0 success.
2020-10-06 00:24:25 temperature.c:267:calibrate_temp_sensor_one_chain: Temperature sensor calibration: chain 1 success.
2020-10-06 00:24:26 temperature.c:267:calibrate_temp_sensor_one_chain: Temperature sensor calibration: chain 2 success.
2020-10-06 00:24:26 driver-hash-chip.c:229:dhash_chip_set_baud_v2: chain[0]: chip baud = 6000000, chip_divider = 7
2020-10-06 00:24:26 driver-hash-chip.c:229:dhash_chip_set_baud_v2: chain[1]: chip baud = 6000000, chip_divider = 7
2020-10-06 00:24:26 driver-hash-chip.c:229:dhash_chip_set_baud_v2: chain[2]: chip baud = 6000000, chip_divider = 7
2020-10-06 00:24:26 uart.c:80:set_baud: set fpga_baud = 6000000, fpga_divider = 3
2020-10-06 00:24:28 driver-btm-api.c:236:check_bringup_temp: Bring up temperature is 25
2020-10-06 00:24:28 thread.c:642:create_check_miner_status_thread: create thread
2020-10-06 00:24:28 thread.c:632:create_set_miner_status_thread: create thread
2020-10-06 00:24:28 driver-btm-api.c:723:calculate_timeout: dev->timeout = 245
2020-10-06 00:24:28 freq_tuning.c:173:freq_tuning_get_max_freq: Max freq of tuning is 690
2020-10-06 00:24:28 frequency.c:484:increase_freq_by_frequency_list_slowly: Increase freq slowly for all chain to 565
2020-10-06 00:24:28 frequency.c:341:auto_adaption_high_voltage_increase_frequency: auto adaption increase frequency from 50.000000 to 500.000000 @20.80V.
2020-10-06 00:24:28 frequency.c:342:auto_adaption_high_voltage_increase_frequency: index 0 2
2020-10-06 00:24:28 power_api.c:344:slowly_set_iic_power_to_custom_voltage: slowly setting to voltage: 20.80 ...
2020-10-06 00:24:52 power_api.c:219:get_average_voltage: chain[0], voltage is: 21.149004
2020-10-06 00:24:54 power_api.c:219:get_average_voltage: chain[1], voltage is: 21.179619
2020-10-06 00:24:57 power_api.c:219:get_average_voltage: chain[2], voltage is: 21.057158
2020-10-06 00:24:57 power_api.c:229:get_average_voltage: average voltage is: 21.128593
2020-10-06 00:24:57 driver-btm-api.c:657:increase_freq_slowly: init_freq = 50.00, final_freq = 500.00, freq_step = 5.00, chain = 255
2020-10-06 00:26:28 frequency.c:341:auto_adaption_high_voltage_increase_frequency: auto adaption increase frequency from 500.000000 to 550.000000 @20.30V.
2020-10-06 00:26:28 frequency.c:342:auto_adaption_high_voltage_increase_frequency: index 1 2
2020-10-06 00:26:28 power_api.c:344:slowly_set_iic_power_to_custom_voltage: slowly setting to voltage: 20.30 ...
2020-10-06 00:27:07 power_api.c:219:get_average_voltage: chain[0], voltage is: 20.683652
2020-10-06 00:27:09 power_api.c:219:get_average_voltage: chain[1], voltage is: 20.708144
2020-10-06 00:27:11 power_api.c:219:get_average_voltage: chain[2], voltage is: 20.604052
2020-10-06 00:27:11 power_api.c:229:get_average_voltage: average voltage is: 20.665283
2020-10-06 00:27:11 driver-btm-api.c:657:increase_freq_slowly: init_freq = 500.00, final_freq = 550.00, freq_step = 5.00, chain = 255
2020-10-06 00:27:21 frequency.c:341:auto_adaption_high_voltage_increase_frequency: auto adaption increase frequency from 550.000000 to 565.000000 @19.60V.
2020-10-06 00:27:21 frequency.c:342:auto_adaption_high_voltage_increase_frequency: index 2 2
2020-10-06 00:27:21 power_api.c:344:slowly_set_iic_power_to_custom_voltage: slowly setting to voltage: 19.60 ...
2020-10-06 00:27:56 power_api.c:219:get_average_voltage: chain[0], voltage is: 19.942763
2020-10-06 00:27:57 power_api.c:219:get_average_voltage: chain[1], voltage is: 19.961133
2020-10-06 00:27:59 power_api.c:219:get_average_voltage: chain[2], voltage is: 19.875410
2020-10-06 00:27:59 power_api.c:229:get_average_voltage: average voltage is: 19.926435
2020-10-06 00:27:59 driver-btm-api.c:657:increase_freq_slowly: init_freq = 550.00, final_freq = 565.00, freq_step = 5.00, chain = 255
2020-10-06 00:28:02 frequency.c:491:increase_freq_by_frequency_list_slowly: Increase freq slowly for chain 2 to 580
2020-10-06 00:28:02 frequency.c:341:auto_adaption_high_voltage_increase_frequency: auto adaption increase frequency from 565.000000 to 580.000000 @19.60V.
2020-10-06 00:28:02 frequency.c:342:auto_adaption_high_voltage_increase_frequency: index 2 2
2020-10-06 00:28:02 driver-btm-api.c:657:increase_freq_slowly: init_freq = 565.00, final_freq = 580.00, freq_step = 5.00, chain = 2
2020-10-06 00:28:05 frequency.c:499:increase_freq_by_frequency_list_slowly: Increase diff freq slowly for chain 2 to maximum 620
2020-10-06 00:28:05 power_api.c:344:slowly_set_iic_power_to_custom_voltage: slowly setting to voltage: 19.30 ...
2020-10-06 00:28:33 power_api.c:219:get_average_voltage: chain[0], voltage is: 19.667226
2020-10-06 00:28:36 power_api.c:219:get_average_voltage: chain[1], voltage is: 19.679472
2020-10-06 00:28:39 power_api.c:219:get_average_voltage: chain[2], voltage is: 19.605996
2020-10-06 00:28:39 power_api.c:229:get_average_voltage: average voltage is: 19.650898
2020-10-06 00:28:44 driver-btm-api.c:754:set_timeout: freq 620 final timeout=118
2020-10-06 00:28:44 power_api.c:362:slowly_set_iic_power_to_working_voltage: slowly setting to voltage: 18.00 ...
2020-10-06 00:29:31 power_api.c:219:get_average_voltage: chain[0], voltage is: 18.307910
2020-10-06 00:29:33 power_api.c:219:get_average_voltage: chain[1], voltage is: 18.326279
2020-10-06 00:29:34 power_api.c:219:get_average_voltage: chain[2], voltage is: 18.265049
2020-10-06 00:29:34 power_api.c:229:get_average_voltage: average voltage is: 18.299746
2020-10-06 00:29:34 thread.c:617:create_temperature_monitor_thread: create thread
2020-10-06 00:29:34 thread.c:637:create_check_system_status_thread: create thread
2020-10-06 00:29:35 driver-btm-api.c:1988:bitmain_soc_init: Init done!
2020-10-06 00:29:35 driver-btm-api.c:194:set_miner_status: STATUS_INIT
2020-10-06 00:29:41 driver-btm-api.c:194:set_miner_status: STATUS_OKAY
2020-10-06 00:29:45 driver-btm-api.c:1423:dhash_chip_send_job: Verion num 4
2020-10-06 00:59:47 thread.c:164:calc_hashrate_avg: avg rate is 52382.95 in 30 mins
2020-10-06 00:59:47 temperature.c:435:temp_statistics_show: pcb temp 35~62 chip temp 46~80
2020-10-06 00:59:47 thread.c:245:check_hashrate: latest avg rate < 0.98......
2020-10-06 00:59:47 thread.c:246:check_hashrate: current PCB min temperature 35
2020-10-06 00:59:47 thread.c:247:check_hashrate: current voltage is 18.00V, working voltage is 18.00V
2020-10-06 00:59:47 thread.c:278:check_hashrate: high temp, increase voltage 0.1V/0.2V to 18.10V
2020-10-06 00:59:47 driver-btm-api.c:1999:bitmain_reopen_core: reopen_core start!
2020-10-06 00:59:54 driver-btm-api.c:1183:init_miner_version: miner ID : 800a1dce57408854
2020-10-06 00:59:54 driver-btm-api.c:1189:init_miner_version: FPGA Version = 0xB011
2020-10-06 00:59:55 chain = 0, mode = 1, load_done = false.
2020-10-06 00:59:55 chain = 1, mode = 1, load_done = false.
2020-10-06 00:59:55 chain = 2, mode = 1, load_done = false.
2020-10-06 00:59:56 chain = 0, mode = 1, load_done = false.
2020-10-06 00:59:56 chain = 1, mode = 1, load_done = false.
2020-10-06 00:59:56 chain = 2, mode = 1, load_done = false.
2020-10-06 00:59:57 chain = 0, mode = 1, load_done = false.
2020-10-06 00:59:57 chain = 1, mode = 1, load_done = false.
2020-10-06 00:59:57 chain = 2, mode = 1, load_done = false.
2020-10-06 00:59:58 chain = 0, mode = 1, load_done = false.
2020-10-06 00:59:58 chain = 1, mode = 1, load_done = false.
2020-10-06 00:59:58 chain = 2, mode = 1, load_done = false.
2020-10-06 00:59:59 chain = 0, mode = 1, load_done = false.
2020-10-06 00:59:59 chain = 1, mode = 1, load_done = false.
2020-10-06 00:59:59 chain = 2, mode = 1, load_done = false.
2020-10-06 00:59:59 driver-btm-api.c:835:get_product_id: product_id[0] = 0
2020-10-06 00:59:59 driver-btm-api.c:835:get_product_id: product_id[1] = 0
2020-10-06 00:59:59 driver-btm-api.c:835:get_product_id: product_id[2] = 0
2020-10-06 00:59:59 driver-btm-api.c:786:_set_project_type: project:0
2020-10-06 00:59:59 driver-btm-api.c:811:_set_project_type: Project type: Antminer S17 Pro
2020-10-06 00:59:59 driver-btm-api.c:822:dump_pcb_bom_version: Chain [0] PCB Version: 0x0101
2020-10-06 00:59:59 driver-btm-api.c:823:dump_pcb_bom_version: Chain [0] BOM Version: 0x0103
2020-10-06 00:59:59 driver-btm-api.c:822:dump_pcb_bom_version: Chain [1] PCB Version: 0x0101
2020-10-06 00:59:59 driver-btm-api.c:823:dump_pcb_bom_version: Chain [1] BOM Version: 0x0103
2020-10-06 00:59:59 driver-btm-api.c:822:dump_pcb_bom_version: Chain [2] PCB Version: 0x0101
2020-10-06 00:59:59 driver-btm-api.c:823:dump_pcb_bom_version: Chain [2] BOM Version: 0x0103
2020-10-06 01:00:00 driver-btm-api.c:1841:bitmain_board_init: Fan check passed.
2020-10-06 01:00:03 board.c:36:jump_and_app_check_restore_pic: chain[0] PIC jump to app
2020-10-06 01:00:08 board.c:40:jump_and_app_check_restore_pic: Check chain[0] PIC fw version=0xb9
2020-10-06 01:00:10 board.c:36:jump_and_app_check_restore_pic: chain[1] PIC jump to app
2020-10-06 01:00:13 board.c:40:jump_and_app_check_restore_pic: Check chain[1] PIC fw version=0xb9
2020-10-06 01:00:13 register.c:282:get_register: !!! reg crc error
2020-10-06 01:00:15 board.c:36:jump_and_app_check_restore_pic: chain[2] PIC jump to app
edit: I checked last night and didn't see any markings on the hashboards indicating where they were made. I wonder what the actual rules are for what US customs calls made in China. If all they have to do is send hashboards separate from the main body to Malaysia and have them just plug them together to bypass the tariff, I'd think all of the other manufacturers would have jumped on that to try to capture more of the US market, and Bitmain would have made it easier to order from Malaysia instead of only offering it to larger customers. Turns out my host has about 25 dead S17 pros, not sure what % of his total that is. We've struck a deal so I'm going to attempt to fix his dead miners, I'll update the thread on what I find.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: NotFuzzyWarm on October 07, 2020, 02:18:25 PM
I wonder what the actual rules are for what US customs calls made in China. If all they have to do is send hashboards separate from the main body to Malaysia and have them just plug them together to bypass the tariff, I'd think all of the other manufacturers would have jumped on that...
Not positive but am pretty sure it takes more than sending a plug-together kit of parts to get around the tariffs hence my guess about the boards being stuffed in Malaysia as well PSU's being made there as well. Someone needs to check the Customs category breakdown on them.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: mikeywith on October 07, 2020, 05:57:36 PM
It's reasonably cool here so fans are running around 50%. I'm going to figure out a way to limit cooling to stress test it before I declare it fixed.
Limit the fans speed to 10-20% by following this guide (https://bitcointalk.org/index.php?topic=5202112.0), this used to work on all previous firmware versions but I am not sure about the latest firmware, however, I think it's likely going to work just fine. By the way, upgrading to the latest firmware means you are now stuck with it forever, I hope you were aware of this before actually doing it.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: wndsnb on October 07, 2020, 07:54:31 PM
...
Thanks! I just put the miner in a box, cut an intake and exhaust hole, and then slowly covered up the intake until I got the temperatures up. But your way is way better obviously ... I tried it on this miner with the latest firmware and it does still work. While testing that out, I changed the setting multiple times and ran into an issue where the miner did not come up after applying changes to the configuration page. I saw this once before and figured it was just a fluke, but it happened again. Comes back up with a reboot though, so not much of an issue.
Booting Linux on physical CPU 0x0
Linux version 4.6.0-xilinx-gff8137b-dirty (lzq@armdev2) (gcc version 4.8.3 20140320 (prerelease) (Sourcery CodeBench Lite 2014.05-23) ) #25 SMP PREEMPT Fri Nov 23 15:30:52 CST 2018
CPU: ARMv7 Processor [413fc090] revision 0 (ARMv7), cr=18c5387d
CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
Machine model: Xilinx Zynq
cma: Reserved 16 MiB at 0x0e000000
Memory policy: Data cache writealloc
On node 0 totalpages: 61440
free_area_init_node: node 0, pgdat c0b39280, node_mem_map cde10000
Normal zone: 480 pages used for memmap
Normal zone: 0 pages reserved
Normal zone: 61440 pages, LIFO batch:15
percpu: Embedded 12 pages/cpu @cddf1000 s19776 r8192 d21184 u49152
pcpu-alloc: s19776 r8192 d21184 u49152 alloc=12*4096
pcpu-alloc: [0] 0 [0] 1
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 60960
Kernel command line: mem=240M console=ttyPS0,115200 ramdisk_size=33554432 root=/dev/ram rw earlyprintk
PID hash table entries: 1024 (order: 0, 4096 bytes)
Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
Memory: 203608K/245760K available (6345K kernel code, 231K rwdata, 1896K rodata, 1024K init, 223K bss, 25768K reserved, 16384K cma-reserved, 0K highmem)
Virtual kernel memory layout:
vector : 0xffff0000 - 0xffff1000 ( 4 kB)
fixmap : 0xffc00000 - 0xfff00000 (3072 kB)
vmalloc : 0xcf800000 - 0xff800000 ( 768 MB)
lowmem : 0xc0000000 - 0xcf000000 ( 240 MB)
pkmap : 0xbfe00000 - 0xc0000000 ( 2 MB)
modules : 0xbf000000 - 0xbfe00000 ( 14 MB)
.text : 0xc0008000 - 0xc090c424 (9234 kB)
.init : 0xc0a00000 - 0xc0b00000 (1024 kB)
.data : 0xc0b00000 - 0xc0b39fe0 ( 232 kB)
.bss : 0xc0b39fe0 - 0xc0b71c28 ( 224 kB)
Preemptible hierarchical RCU implementation.
Build-time adjustment of leaf fanout to 32.
RCU restricting CPUs from NR_CPUS=4 to nr_cpu_ids=2.
RCU: Adjusting geometry for rcu_fanout_leaf=32, nr_cpu_ids=2
NR_IRQS:16 nr_irqs:16 16
efuse mapped to cf800000
ps7-slcr mapped to cf802000
L2C: platform modifies aux control register: 0x72360000 -> 0x72760000
L2C: DT/platform modifies aux control register: 0x72360000 -> 0x72760000
L2C-310 erratum 769419 enabled
L2C-310 enabling early BRESP for Cortex-A9
L2C-310 full line of zeros enabled for Cortex-A9
L2C-310 ID prefetch enabled, offset 1 lines
L2C-310 dynamic clock gating enabled, standby mode enabled
L2C-310 cache controller enabled, 8 ways, 512 kB
L2C-310: CACHE_ID 0x410000c8, AUX_CTRL 0x76760001
zynq_clock_init: clkc starts at cf802100
Zynq clock init
sched_clock: 64 bits at 333MHz, resolution 3ns, wraps every 4398046511103ns
clocksource: arm_global_timer: mask: 0xffffffffffffffff max_cycles: 0x4ce07af025, max_idle_ns: 440795209040 ns
Switching to timer-based delay loop, resolution 3ns
clocksource: ttc_clocksource: mask: 0xffff max_cycles: 0xffff, max_idle_ns: 537538477 ns
ps7-ttc #0 at cf80a000, irq=18
Console: colour dummy device 80x30
Calibrating delay loop (skipped), value calculated using timer frequency.. 666.66 BogoMIPS (lpj=3333333)
pid_max: default: 32768 minimum: 301
Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
CPU: Testing write buffer coherency: ok
CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
Setting up static identity map for 0x100000 - 0x100058
CPU1: failed to boot: -1
Brought up 1 CPUs
SMP: Total of 1 processors activated (666.66 BogoMIPS).
CPU: All CPU(s) started in SVC mode.
devtmpfs: initialized
VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4
clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
pinctrl core: initialized pinctrl subsystem
NET: Registered protocol family 16
DMA: preallocated 256 KiB pool for atomic coherent allocations
cpuidle: using governor menu
hw-breakpoint: found 5 (+1 reserved) breakpoint and 1 watchpoint registers.
hw-breakpoint: maximum watchpoint size is 4 bytes.
zynq-ocm f800c000.ps7-ocmc: ZYNQ OCM pool: 256 KiB @ 0xcf880000
vgaarb: loaded
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
media: Linux media interface: v0.10
Linux video capture interface: v2.00
pps_core: LinuxPPS API ver. 1 registered
pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
PTP clock support registered
EDAC MC: Ver: 3.0.0
Advanced Linux Sound Architecture Driver Initialized.
clocksource: Switched to clocksource arm_global_timer
NET: Registered protocol family 2
TCP established hash table entries: 2048 (order: 1, 8192 bytes)
TCP bind hash table entries: 2048 (order: 2, 16384 bytes)
TCP: Hash tables configured (established 2048 bind 2048)
UDP hash table entries: 256 (order: 1, 8192 bytes)
UDP-Lite hash table entries: 256 (order: 1, 8192 bytes)
NET: Registered protocol family 1
RPC: Registered named UNIX socket transport module.
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
PCI: CLS 0 bytes, default 64
Trying to unpack rootfs image as initramfs...
rootfs image is not initramfs (no cpio magic); looks like an initrd
Freeing initrd memory: 12728K (cce93000 - cdb01000)
hw perfevents: enabled with armv7_cortex_a9 PMU driver, 7 counters available
futex hash table entries: 512 (order: 3, 32768 bytes)
workingset: timestamp_bits=28 max_order=16 bucket_order=0
jffs2: version 2.2. (NAND) (SUMMARY) © 2001-2006 Red Hat, Inc.
io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered (default)
dma-pl330 f8003000.ps7-dma: Loaded driver for PL330 DMAC-241330
dma-pl330 f8003000.ps7-dma: DBUFF-128x8bytes Num_Chans-8 Num_Peri-4 Num_Events-16
e0000000.serial: ttyPS0 at MMIO 0xe0000000 (irq = 158, base_baud = 6249999) is a xuartps
console [ttyPS0] enabled
xdevcfg f8007000.ps7-dev-cfg: ioremap 0xf8007000 to cf86e000
[drm] Initialized drm 1.1.0 20060810
brd: module loaded
loop: module loaded
CAN device driver interface
gpiod_set_value: invalid GPIO
libphy: MACB_mii_bus: probed
macb e000b000.ethernet eth0: Cadence GEM rev 0x00020118 at 0xe000b000 irq 31 (00:0a:35:00:00:00)
Generic PHY e000b000.etherne:00: attached PHY driver [Generic PHY] (mii_bus:phy_addr=e000b000.etherne:00, irq=-1)
e1000e: Intel(R) PRO/1000 Network Driver - 3.2.6-k
e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
ehci-pci: EHCI PCI platform driver
usbcore: registered new interface driver usb-storage
mousedev: PS/2 mouse device common for all mice
i2c /dev entries driver
Xilinx Zynq CpuIdle Driver started
sdhci: Secure Digital Host Controller Interface driver
sdhci: Copyright(c) Pierre Ossman
sdhci-pltfm: SDHCI platform and OF driver helper
mmc0: SDHCI controller on e0100000.ps7-sdio [e0100000.ps7-sdio] using ADMA
ledtrig-cpu: registered to indicate activity on CPUs
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
nand: device found, Manufacturer ID: 0x2c, Chip ID: 0xda
nand: Micron MT29F2G08ABAGAWP
nand: 256 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 128
nand: WARNING: pl35x-nand: the ECC used on your system is too weak compared to the one required by the NAND chip
Bad block table found at page 131008, version 0x01
Bad block table found at page 130944, version 0x01
6 ofpart partitions found on MTD device pl35x-nand
Creating 6 MTD partitions on "pl35x-nand":
0x000000000000-0x000002800000 : "BOOT.bin-env-dts-kernel"
0x000002800000-0x000004800000 : "ramfs"
0x000004800000-0x000005000000 : "configs"
0x000005000000-0x000006000000 : "reserve"
0x000006000000-0x000008000000 : "ramfs-bak"
0x000008000000-0x000010000000 : "reserve1"
NET: Registered protocol family 10
sit: IPv6 over IPv4 tunneling driver
NET: Registered protocol family 17
can: controller area network core (rev 20120528 abi 9)
NET: Registered protocol family 29
can: raw protocol (rev 20120528)
can: broadcast manager protocol (rev 20120528 t)
can: netlink gateway (rev 20130117) max_hops=1
zynq_pm_ioremap: no compatible node found for 'xlnx,zynq-ddrc-a05'
zynq_pm_late_init: Unable to map DDRC IO memory.
Registering SWP/SWPB emulation handler
hctosys: unable to open rtc device (rtc0)
ALSA device list:
No soundcards found.
RAMDISK: gzip image found at block 0
EXT4-fs (ram0): couldn't mount as ext3 due to feature incompatibilities
EXT4-fs (ram0): mounted filesystem without journal. Opts: (null)
VFS: Mounted root (ext4 filesystem) on device 1:0.
devtmpfs: mounted
Freeing unused kernel memory: 1024K (c0a00000 - c0b00000)
EXT4-fs (ram0): re-mounted. Opts: block_validity,delalloc,barrier,user_xattr
random: dd urandom read with 0 bits of entropy available
ubi0: attaching mtd2
ubi0: scanning is finished
ubi0: attached mtd2 (name "configs", size 8 MiB)
ubi0: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
ubi0: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
ubi0: VID header offset: 2048 (aligned 2048), data offset: 4096
ubi0: good PEBs: 64, bad PEBs: 0, corrupted PEBs: 0
ubi0: user volume: 1, internal volumes: 1, max. volumes count: 128
ubi0: max/mean erase counter: 3/1, WL threshold: 4096, image sequence number: 1099087952
ubi0: available PEBs: 0, total reserved PEBs: 64, PEBs reserved for bad PEB handling: 40
ubi0: background thread "ubi_bgt0d" started, PID 708
UBIFS (ubi0:0): background thread "ubifs_bgt0_0" started, PID 711
UBIFS (ubi0:0): UBIFS: mounted UBI device 0, volume 0, name "configs"
UBIFS (ubi0:0): LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
UBIFS (ubi0:0): FS size: 1396736 bytes (1 MiB, 11 LEBs), journal size 888833 bytes (0 MiB, 5 LEBs)
UBIFS (ubi0:0): reserved for root: 65970 bytes (64 KiB)
UBIFS (ubi0:0): media format: w4/r0 (latest is w4/r0), UUID CD1BC056-7E24-4E3E-BCAF-EAA178A77B8B, small LPT model
ubi1: attaching mtd5
ubi1: scanning is finished
ubi1: attached mtd5 (name "reserve1", size 128 MiB)
ubi1: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
ubi1: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
ubi1: VID header offset: 2048 (aligned 2048), data offset: 4096
ubi1: good PEBs: 1020, bad PEBs: 4, corrupted PEBs: 0
ubi1: user volume: 1, internal volumes: 1, max. volumes count: 128
ubi1: max/mean erase counter: 974/212, WL threshold: 4096, image sequence number: 4185749592
ubi1: available PEBs: 0, total reserved PEBs: 1020, PEBs reserved for bad PEB handling: 36
ubi1: background thread "ubi_bgt1d" started, PID 720
UBIFS (ubi1:0): background thread "ubifs_bgt1_0" started, PID 723
UBIFS (ubi1:0): UBIFS: mounted UBI device 1, volume 0, name "reserve1"
UBIFS (ubi1:0): LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
UBIFS (ubi1:0): FS size: 123039744 bytes (117 MiB, 969 LEBs), journal size 6221824 bytes (5 MiB, 49 LEBs)
UBIFS (ubi1:0): reserved for root: 4952683 bytes (4836 KiB)
UBIFS (ubi1:0): media format: w4/r0 (latest is w4/r0), UUID 4829CF2C-7435-4146-B2FD-0826AAE8443A, small LPT model
IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
macb e000b000.ethernet eth0: unable to generate target frequency: 25000000 Hz
macb e000b000.ethernet eth0: link up (100/Full)
IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
In axi fpga driver!
request_mem_region OK!
AXI fpga dev virtual address is 0xcfb38000
*base_vir_addr = 0xab013
In fpga mem driver!
request_mem_region OK!
fpga mem virtual address is 0xd2000000
random: nonblocking pool is initialized
Oct 7 19:00:19 (none) local0.info bmminer: (null) 0: invalid nonce - HW error
Oct 7 19:00:19 (none) local0.info bmminer: (null) 0: invalid nonce - HW error
Oct 7 19:00:19 (none) local0.info bmminer: (null) 0: invalid nonce - HW error
Oct 7 19:00:19 (none) local0.info bmminer: (null) 0: invalid nonce - HW error
Oct 7 19:00:19 (none) local0.info bmminer: (null) 0: invalid nonce - HW error
Oct 7 19:00:19 (none) local0.info bmminer: (null) 0: invalid nonce - HW error
Oct 7 19:00:19 (none) local0.info bmminer: (null) 0: invalid nonce - HW error
Oct 7 19:00:19 (none) local0.info bmminer: (null) 0: invalid nonce - HW error
Oct 7 19:00:19 (none) local0.info bmminer: (null) 0: invalid nonce - HW error
Oct 7 19:00:19 (none) local0.info bmminer: (null) 0: invalid nonce - HW error
Oct 7 19:00:19 (none) local0.info bmminer: (null) 0: invalid nonce - HW error
Oct 7 19:00:19 (none) local0.info bmminer: (null) 0: invalid nonce - HW error
Oct 7 19:00:19 (none) local0.info bmminer: (null) 0: invalid nonce - HW error
Oct 7 19:00:19 (none) local0.info bmminer: (null) 0: invalid nonce - HW error
Oct 7 19:00:19 (none) local0.info bmminer: (null) 0: invalid nonce - HW error
Oct 7 19:00:19 (none) local0.info bmminer: (null) 0: invalid nonce - HW error
Oct 7 19:00:19 (none) local0.info bmminer: (null) 0: invalid nonce - HW error
Oct 7 19:00:19 (none) local0.info bmminer: (null) 0: invalid nonce - HW error
Oct 7 19:00:19 (none) local0.info bmminer: (null) 0: invalid nonce - HW error
Oct 7 19:00:19 (none) local0.info bmminer: (null) 0: invalid nonce - HW error
Oct 7 19:00:19 (none) local0.info bmminer: (null) 0: invalid nonce - HW error
Oct 7 19:00:19 (none) local0.info bmminer: (null) 0: invalid nonce - HW error
Oct 7 19:00:19 (none) local0.info bmminer: (null) 0: invalid nonce - HW error
Oct 7 19:00:19 (none) local0.info bmminer: (null) 0: invalid nonce - HW error
Oct 7 19:00:19 (none) local0.info bmminer: (null) 0: invalid nonce - HW error
Oct 7 19:00:19 (none) local0.info bmminer: (null) 0: invalid nonce - HW error
Oct 7 19:00:19 (none) local0.info bmminer: (null) 0: invalid nonce - HW error
Oct 7 19:00:19 (none) local0.info bmminer: (null) 0: invalid nonce - HW error
Oct 7 19:00:19 (none) local0.info bmminer: (null) 0: invalid nonce - HW error
Oct 7 19:00:19 (none) local0.info bmminer: (null) 0: invalid nonce - HW error
Oct 7 19:00:19 (none) local0.info bmminer: (null) 0: invalid nonce - HW error
Oct 7 19:00:19 (none) local0.info bmminer: (null) 0: invalid nonce - HW error
Oct 7 19:00:19 (none) local0.info bmminer: (null) 0: invalid nonce - HW error
Oct 7 19:00:19 (none) local0.info bmminer: (null) 0: invalid nonce - HW error
Oct 7 19:00:19 (none) local0.info bmminer: (null) 0: invalid nonce - HW error
Oct 7 19:00:19 (none) local0.info bmminer: (null) 0: invalid nonce - HW error
Oct 7 19:00:19 (none) local0.info bmminer: (null) 0: invalid nonce - HW error
Oct 7 19:00:19 (none) local0.info bmminer: (null) 0: invalid nonce - HW error
Oct 7 19:00:19 (none) local0.info bmminer: (null) 0: invalid nonce - HW error
Oct 7 19:00:19 (none) local0.info bmminer: (null) 0: invalid nonce - HW error
Oct 7 19:00:19 (none) local0.info bmminer: (null) 0: invalid nonce - HW error
[deleted]
Oct 7 19:00:30 (none) local0.info bmminer: (null) 0: invalid nonce - HW error
Oct 7 19:00:30 (none) local0.info bmminer: (null) 0: invalid nonce - HW error
Oct 7 19:00:30 (none) local0.info bmminer: (null) 0: invalid nonce - HW error
Oct 7 19:00:30 (none) local0.info bmminer: (null) 0: invalid nonce - HW error
2020-10-07 18:53:36 driver-btm-api.c:542:init_freq_mode: This is scan-user version
2020-10-07 18:53:36 driver-btm-api.c:1877:bitmain_soc_init: opt_multi_version = 1
2020-10-07 18:53:36 driver-btm-api.c:1878:bitmain_soc_init: opt_bitmain_ab = 1
2020-10-07 18:53:36 driver-btm-api.c:1879:bitmain_soc_init: opt_bitmain_work_mode = 0
2020-10-07 18:53:36 driver-btm-api.c:1880:bitmain_soc_init: Miner compile time: Mon Apr 27 13:25:08 CST 2020 type: Antminer S17 Pro
2020-10-07 18:53:36 driver-btm-api.c:1881:bitmain_soc_init: commit version: d22f356 2020-04-24 18:30:49, build by: lol 2020-04-27 13:31:45
2020-10-07 18:53:36 driver-btm-api.c:1691:show_sn: no SN got, please write SN to /nvdata/sn
2020-10-07 18:53:36 driver-btm-api.c:1040:miner_device_init: Detect 256MB control board of XILINX
2020-10-07 18:53:36 driver-btm-api.c:988:init_fan_parameter: fan_eft : 1 fan_pwm : 30
2020-10-07 18:53:36 thread.c:783:create_read_nonce_reg_thread: create thread
2020-10-07 18:53:42 driver-btm-api.c:972:init_miner_version: miner ID : 800a1dce57408854
2020-10-07 18:53:42 driver-btm-api.c:978:init_miner_version: FPGA Version = 0xB013
2020-10-07 18:53:47 driver-btm-api.c:616:get_product_id: product_id[0] = 0
2020-10-07 18:53:47 driver-btm-api.c:616:get_product_id: product_id[1] = 0
2020-10-07 18:53:47 driver-btm-api.c:616:get_product_id: product_id[2] = 0
2020-10-07 18:53:47 driver-btm-api.c:560:_set_project_type: project:0
2020-10-07 18:53:47 driver-btm-api.c:585:_set_project_type: Project type: Antminer S17 Pro
2020-10-07 18:53:47 driver-btm-api.c:596:dump_pcb_bom_version: Chain [0] PCB Version: 0x0101
2020-10-07 18:53:47 driver-btm-api.c:597:dump_pcb_bom_version: Chain [0] BOM Version: 0x0103
2020-10-07 18:53:47 driver-btm-api.c:596:dump_pcb_bom_version: Chain [1] PCB Version: 0x0101
2020-10-07 18:53:47 driver-btm-api.c:597:dump_pcb_bom_version: Chain [1] BOM Version: 0x0103
2020-10-07 18:53:47 driver-btm-api.c:596:dump_pcb_bom_version: Chain [2] PCB Version: 0x0101
2020-10-07 18:53:47 driver-btm-api.c:597:dump_pcb_bom_version: Chain [2] BOM Version: 0x0103
2020-10-07 18:53:48 driver-btm-api.c:1802:bitmain_board_init: Fan check passed.
2020-10-07 18:53:49 board.c:36:jump_and_app_check_restore_pic: chain[0] PIC jump to app
2020-10-07 18:53:51 board.c:40:jump_and_app_check_restore_pic: Check chain[0] PIC fw version=0xb9
2020-10-07 18:53:53 board.c:36:jump_and_app_check_restore_pic: chain[1] PIC jump to app
2020-10-07 18:53:55 board.c:40:jump_and_app_check_restore_pic: Check chain[1] PIC fw version=0xb9
2020-10-07 18:53:56 board.c:36:jump_and_app_check_restore_pic: chain[2] PIC jump to app
2020-10-07 18:53:58 board.c:40:jump_and_app_check_restore_pic: Check chain[2] PIC fw version=0xb9
2020-10-07 18:53:58 thread.c:778:create_pic_heart_beat_thread: create thread
2020-10-07 18:53:58 power_api.c:207:power_init: Power init:
2020-10-07 18:53:58 power_api.c:208:power_init: current_voltage_raw = 0
2020-10-07 18:53:58 power_api.c:209:power_init: highest_voltage_raw = 2100
2020-10-07 18:53:58 power_api.c:210:power_init: working_voltage_raw = 1830
2020-10-07 18:53:58 power_api.c:211:power_init: higher_voltage_raw = 1950
2020-10-07 18:53:58 driver-btm-api.c:1812:bitmain_board_init: Enter 30s sleep to make sure power release finish.
2020-10-07 18:54:30 power_api.c:251:set_to_highest_voltage: Set to voltage raw 2100, one step.
2020-10-07 18:54:32 power_api.c:87:check_voltage_multi: retry time: 0
2020-10-07 18:54:33 power_api.c:37:_get_avg_voltage: chain = 0, voltage = 21.369433
2020-10-07 18:54:34 power_api.c:37:_get_avg_voltage: chain = 1, voltage = 21.424541
2020-10-07 18:54:35 power_api.c:37:_get_avg_voltage: chain = 2, voltage = 21.289834
2020-10-07 18:54:35 power_api.c:50:_get_avg_voltage: average_voltage = 21.361269
2020-10-07 18:54:35 power_api.c:68:check_voltage: target_vol = 21.00, actural_vol = 21.36, check voltage passed.
2020-10-07 18:54:35 uart.c:71:set_baud: set fpga_baud to 115200
2020-10-07 18:54:46 driver-btm-api.c:915:check_asic_number_with_power_on: Chain[0]: find 48 asic, times 0
2020-10-07 18:54:57 driver-btm-api.c:915:check_asic_number_with_power_on: Chain[1]: find 48 asic, times 0
2020-10-07 18:55:08 driver-btm-api.c:915:check_asic_number_with_power_on: Chain[2]: find 48 asic, times 0
2020-10-07 18:55:13 driver-btm-api.c:345:set_order_clock: chain[0]: set order clock, stragegy 3
2020-10-07 18:55:14 driver-btm-api.c:345:set_order_clock: chain[1]: set order clock, stragegy 3
2020-10-07 18:55:14 driver-btm-api.c:345:set_order_clock: chain[2]: set order clock, stragegy 3
2020-10-07 18:55:14 driver-hash-chip.c:502:set_clock_delay_control: core_data = 0x34
2020-10-07 18:55:14 uart.c:71:set_baud: set fpga_baud to 3000000
2020-10-07 18:55:14 driver-btm-api.c:1574:check_clock_counter: freq 50 clock_counter_limit 6
2020-10-07 18:55:16 uart.c:71:set_baud: set fpga_baud to 115200
2020-10-07 18:55:16 voltage[0] = 1700
2020-10-07 18:55:16 voltage[1] = 1700
2020-10-07 18:55:16 voltage[2] = 1700
2020-10-07 18:55:16 power_api.c:219:set_working_voltage_raw: working_voltage_raw = 1700
2020-10-07 18:55:17 temperature.c:281:calibrate_temp_sensor_one_chain: Temperature sensor calibration: chain 0 success.
2020-10-07 18:55:19 temperature.c:281:calibrate_temp_sensor_one_chain: Temperature sensor calibration: chain 1 success.
2020-10-07 18:55:20 temperature.c:281:calibrate_temp_sensor_one_chain: Temperature sensor calibration: chain 2 success.
2020-10-07 18:55:20 uart.c:71:set_baud: set fpga_baud to 6000000
2020-10-07 18:55:22 driver-btm-api.c:245:check_bringup_temp: Bring up temperature is 31
2020-10-07 18:55:22 thread.c:798:create_check_miner_status_thread: create thread
2020-10-07 18:55:22 thread.c:788:create_set_miner_status_thread: create thread
2020-10-07 18:55:22 thread.c:773:create_temperature_monitor_thread: create thread
2020-10-07 18:55:22 frequency.c:749:inc_freq_with_fixed_vco: chain = 255, freq = 425, is_higher_voltage = true
2020-10-07 18:55:22 power_api.c:287:set_to_voltage_by_steps: Set to voltage raw 2020, step by step.
2020-10-07 18:55:40 power_api.c:87:check_voltage_multi: retry time: 0
2020-10-07 18:55:41 power_api.c:37:_get_avg_voltage: chain = 0, voltage = 20.530576
2020-10-07 18:55:42 power_api.c:37:_get_avg_voltage: chain = 1, voltage = 20.573437
2020-10-07 18:55:43 power_api.c:37:_get_avg_voltage: chain = 2, voltage = 20.469345
2020-10-07 18:55:43 power_api.c:50:_get_avg_voltage: average_voltage = 20.524453
2020-10-07 18:55:43 power_api.c:68:check_voltage: target_vol = 20.20, actural_vol = 20.52, check voltage passed.
2020-10-07 18:56:15 frequency.c:801:inc_freq_with_fixed_step: chain = 0, freq_start = 425, freq_end = 425, freq_step = 5, is_higher_voltage = true
2020-10-07 18:56:15 frequency.c:801:inc_freq_with_fixed_step: chain = 1, freq_start = 425, freq_end = 425, freq_step = 5, is_higher_voltage = true
2020-10-07 18:56:15 frequency.c:801:inc_freq_with_fixed_step: chain = 2, freq_start = 425, freq_end = 425, freq_step = 5, is_higher_voltage = true
2020-10-07 18:56:15 frequency.c:801:inc_freq_with_fixed_step: chain = 2, freq_start = 425, freq_end = 450, freq_step = 5, is_higher_voltage = true
2020-10-07 18:56:17 power_api.c:287:set_to_voltage_by_steps: Set to voltage raw 1920, step by step.
2020-10-07 18:56:33 power_api.c:87:check_voltage_multi: retry time: 0
2020-10-07 18:56:34 power_api.c:37:_get_avg_voltage: chain = 0, voltage = 19.514150
2020-10-07 18:56:35 power_api.c:37:_get_avg_voltage: chain = 1, voltage = 19.544765
2020-10-07 18:56:36 power_api.c:37:_get_avg_voltage: chain = 2, voltage = 19.471289
2020-10-07 18:56:36 power_api.c:50:_get_avg_voltage: average_voltage = 19.510068
2020-10-07 18:56:36 power_api.c:68:check_voltage: target_vol = 19.20, actural_vol = 19.51, check voltage passed.
2020-10-07 18:56:36 frequency.c:618:inc_asic_diff_freq_by_steps: chain = 0, start = 425, freq_step = 5
2020-10-07 18:56:40 frequency.c:618:inc_asic_diff_freq_by_steps: chain = 1, start = 425, freq_step = 5
2020-10-07 18:56:43 frequency.c:618:inc_asic_diff_freq_by_steps: chain = 2, start = 450, freq_step = 5
2020-10-07 18:56:50 driver-btm-api.c:528:set_timeout: freq = 510, percent = 90, hcn = 73728, timeout = 144
2020-10-07 18:56:50 power_api.c:269:set_to_working_voltage_by_steps: Set to voltage raw 1700, step by step.
2020-10-07 18:57:11 power_api.c:87:check_voltage_multi: retry time: 0
2020-10-07 18:57:12 power_api.c:37:_get_avg_voltage: chain = 0, voltage = 17.273115
2020-10-07 18:57:13 power_api.c:37:_get_avg_voltage: chain = 1, voltage = 17.291484
2020-10-07 18:57:14 power_api.c:37:_get_avg_voltage: chain = 2, voltage = 17.211885
2020-10-07 18:57:14 power_api.c:50:_get_avg_voltage: average_voltage = 17.258828
2020-10-07 18:57:14 power_api.c:68:check_voltage: target_vol = 17.00, actural_vol = 17.26, check voltage passed.
2020-10-07 18:57:14 thread.c:793:create_check_system_status_thread: create thread
2020-10-07 18:57:15 driver-btm-api.c:1988:bitmain_soc_init: Init done!
2020-10-07 18:57:15 driver-btm-api.c:198:set_miner_status: STATUS_INIT
2020-10-07 18:57:20 driver-btm-api.c:198:set_miner_status: STATUS_OKAY
2020-10-07 18:57:21 frequency.c:216:get_ideal_hash_rate_GH: ideal_hash_rate = 44486
2020-10-07 18:57:21 frequency.c:236:get_sale_hash_rate_GH: sale_hash_rate = 44000
2020-10-07 18:57:24 driver-btm-api.c:1199:dhash_chip_send_job: Version num 4
2020-10-07 18:57:33 register.c:313:get_register: !!! REG_TYPE = 1. 842137602
2020-10-07 18:57:33 register.c:313:get_register: !!! REG_TYPE = 1. 607911938
2020-10-07 18:57:33 register.c:313:get_register: !!! REG_TYPE = 1. 776667138
2020-10-07 18:57:33 register.c:313:get_register: !!! REG_TYPE = 1. 877985794
2020-10-07 18:57:33 register.c:313:get_register: !!! REG_TYPE = 1. 962199554
2020-10-07 18:57:33 register.c:313:get_register: !!! REG_TYPE = 1. 996409346
2020-10-07 18:57:33 register.c:313:get_register: !!! REG_TYPE = 1. 778960898
2020-10-07 18:57:33 register.c:313:get_register: !!! REG_TYPE = 1. 1014169602
2020-10-07 18:57:33 register.c:313:get_register: !!! REG_TYPE = 1. 712835074
2020-10-07 18:57:33 register.c:313:get_register: !!! REG_TYPE = 1. 830930946
2020-10-07 18:57:33 register.c:313:get_register: !!! REG_TYPE = 1. 1066139650
2020-10-07 18:57:33 register.c:313:get_register: !!! REG_TYPE = 1. 764477442
2020-10-07 18:57:33 register.c:313:get_register: !!! REG_TYPE = 1. 647364610
2020-10-07 18:57:33 register.c:313:get_register: !!! REG_TYPE = 1. 580911106
2020-10-07 18:57:33 register.c:313:get_register: !!! REG_TYPE = 1. 983891970
2020-10-07 18:57:33 register.c:313:get_register: !!! REG_TYPE = 1. 799997954
2020-10-07 18:57:33 register.c:313:get_register: !!! REG_TYPE = 1. 867762178
[deleted]
2020-10-07 18:57:35 register.c:313:get_register: !!! REG_TYPE = 1. 835518466
2020-10-07 18:57:35 register.c:313:get_register: !!! REG_TYPE = 1. 669384706
2020-10-07 18:57:35 register.c:313:get_register: !!! REG_TYPE = 1. 867762178
2020-10-07 18:57:35 register.c:313:get_register: !!! REG_TYPE = 1. 669384706
2020-10-07 18:57:35 register.c:313:get_register: !!! REG_TYPE = 1. 974389250
2020-10-07 18:57:35 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 0, chip = 55, reg = 0
2020-10-07 18:57:35 register.c:313:get_register: !!! REG_TYPE = 1. 607911938
2020-10-07 18:57:35 register.c:313:get_register: !!! REG_TYPE = 1. 776667138
2020-10-07 18:57:35 register.c:313:get_register: !!! REG_TYPE = 1. 877985794
2020-10-07 18:57:35 register.c:313:get_register: !!! REG_TYPE = 1. 962199554
[deleted]
2020-10-07 18:57:35 register.c:313:get_register: !!! REG_TYPE = 1. 799997954
2020-10-07 18:57:35 register.c:313:get_register: !!! REG_TYPE = 1. 867762178
2020-10-07 18:57:35 register.c:313:get_register: !!! REG_TYPE = 1. 669384706
2020-10-07 18:57:35 register.c:313:get_register: !!! REG_TYPE = 1. 1429907970
2020-10-07 18:57:35 register.c:313:get_register: !!! REG_TYPE = 1. 607911938
2020-10-07 18:57:35 register.c:313:get_register: !!! REG_TYPE = 1. 877985794
2020-10-07 18:57:35 register.c:313:get_register: !!! REG_TYPE = 1. 647364610
2020-10-07 18:57:35 register.c:313:get_register: !!! REG_TYPE = 1. 983891970
2020-10-07 18:57:35 register.c:313:get_register: !!! REG_TYPE = 1. 799997954
2020-10-07 18:57:35 register.c:313:get_register: !!! REG_TYPE = 1. 867762178
2020-10-07 18:57:35 register.c:313:get_register: !!! REG_TYPE = 1. 951975938
2020-10-07 18:57:35 register.c:313:get_register: !!! REG_TYPE = 1. 835518466
2020-10-07 18:57:35 register.c:313:get_register: !!! REG_TYPE = 1. 669384706
2020-10-07 18:57:35 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 55, reg = 28, got chain = 2, chip = 170, reg = 85
2020-10-07 18:57:35 register.c:313:get_register: !!! REG_TYPE = 1. 842137602
2020-10-07 18:57:35 register.c:313:get_register: !!! REG_TYPE = 1. 607911938
2020-10-07 18:57:35 register.c:313:get_register: !!! REG_TYPE = 1. 776667138
2020-10-07 18:57:35 register.c:313:get_register: !!! REG_TYPE = 1. 877985794
2020-10-07 18:57:35 register.c:313:get_register: !!! REG_TYPE = 1. 996409346
[deleted]
2020-10-07 18:57:37 register.c:313:get_register: !!! REG_TYPE = 1. 669384706
2020-10-07 18:57:37 register.c:313:get_register: !!! REG_TYPE = 1. 830930946
2020-10-07 18:57:37 register.c:313:get_register: !!! REG_TYPE = 1. 669384706
2020-10-07 18:57:38 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 40, reg = 28, got chain = 0, chip = 55, reg = 28
2020-10-07 18:57:38 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 40, reg = 28, got chain = 0, chip = 55, reg = 28
2020-10-07 18:57:38 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 40, reg = 28, got chain = 0, chip = 55, reg = 28
2020-10-07 18:57:38 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 40, reg = 28, got chain = 0, chip = 55, reg = 28
2020-10-07 18:57:38 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 40, reg = 28, got chain = 0, chip = 55, reg = 28
2020-10-07 18:57:38 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 40, reg = 28, got chain = 0, chip = 55, reg = 28
2020-10-07 18:57:38 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 40, reg = 28, got chain = 0, chip = 55, reg = 28
2020-10-07 18:57:38 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 40, reg = 28, got chain = 0, chip = 55, reg = 28
2020-10-07 18:57:38 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 40, reg = 28, got chain = 0, chip = 55, reg = 28
2020-10-07 18:57:38 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 40, reg = 28, got chain = 0, chip = 55, reg = 28
2020-10-07 18:57:38 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 40, reg = 28, got chain = 0, chip = 55, reg = 28
2020-10-07 18:57:38 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 40, reg = 28, got chain = 0, chip = 55, reg = 28
2020-10-07 18:57:38 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 40, reg = 28, got chain = 0, chip = 55, reg = 28
2020-10-07 18:57:38 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 40, reg = 28, got chain = 0, chip = 55, reg = 28
2020-10-07 18:57:38 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 40, reg = 28, got chain = 0, chip = 55, reg = 28
[deleted]
2020-10-07 18:57:39 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 40, reg = 28, got chain = 0, chip = 55, reg = 28
2020-10-07 18:57:39 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 40, reg = 28, got chain = 0, chip = 55, reg = 28
2020-10-07 18:57:39 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 40, reg = 28, got chain = 0, chip = 55, reg = 28
2020-10-07 18:57:39 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 40, reg = 28, got chain = 0, chip = 55, reg = 28
2020-10-07 18:57:39 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 40, reg = 28, got chain = 0, chip = 55, reg = 28
2020-10-07 18:57:39 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 40, reg = 28, got chain = 0, chip = 55, reg = 28
2020-10-07 18:57:39 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 1, chip = 40, reg = 1
2020-10-07 18:57:39 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 180, reg = 28, got chain = 0, chip = 55, reg = 28
2020-10-07 18:57:39 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 180, reg = 28, got chain = 0, chip = 55, reg = 28
2020-10-07 18:57:39 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 180, reg = 28, got chain = 0, chip = 55, reg = 28
[deleted]
2020-10-07 18:57:39 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 180, reg = 28, got chain = 0, chip = 55, reg = 28
2020-10-07 18:57:39 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 180, reg = 28, got chain = 0, chip = 55, reg = 28
2020-10-07 18:57:39 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 180, reg = 28, got chain = 0, chip = 55, reg = 28
2020-10-07 18:57:39 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 180, reg = 28, got chain = 0, chip = 55, reg = 28
2020-10-07 18:57:39 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 2, chip = 180, reg = 0
2020-10-07 18:57:39 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 180, reg = 28, got chain = 0, chip = 55, reg = 28
2020-10-07 18:57:39 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 180, reg = 28, got chain = 0, chip = 55, reg = 28
2020-10-07 18:57:39 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 180, reg = 28, got chain = 0, chip = 55, reg = 28
[deleted]
2020-10-07 18:57:41 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 180, reg = 28, got chain = 0, chip = 40, reg = 28
2020-10-07 18:57:41 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 180, reg = 28, got chain = 0, chip = 40, reg = 28
2020-10-07 18:57:41 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 180, reg = 28, got chain = 0, chip = 40, reg = 28
2020-10-07 18:57:41 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 2, chip = 180, reg = 1
2020-10-07 18:57:41 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 195, reg = 28, got chain = 0, chip = 40, reg = 28
2020-10-07 18:57:41 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 195, reg = 28, got chain = 0, chip = 40, reg = 28
2020-10-07 18:57:41 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 195, reg = 28, got chain = 0, chip = 40, reg = 28
2020-10-07 18:57:41 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 195, reg = 28, got chain = 0, chip = 40, reg = 28
2020-10-07 18:57:41 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 195, reg = 28, got chain = 0, chip = 40, reg = 28
2020-10-07 18:57:41 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 195, reg = 28, got chain = 0, chip = 40, reg = 28
2020-10-07 18:57:41 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 195, reg = 28, got chain = 0, chip = 40, reg = 28
2020-10-07 18:57:41 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 195, reg = 28, got chain = 0, chip = 40, reg = 28
2020-10-07 18:57:41 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 195, reg = 28, got chain = 0, chip = 40, reg = 28
2020-10-07 18:57:41 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 195, reg = 28, got chain = 0, chip = 40, reg = 28
2020-10-07 18:57:41 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 195, reg = 28, got chain = 0, chip = 40, reg = 28
2020-10-07 18:57:41 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 195, reg = 28, got chain = 0, chip = 40, reg = 28
2020-10-07 18:57:41 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 195, reg = 28, got chain = 0, chip = 40, reg = 28
2020-10-07 18:57:41 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 195, reg = 28, got chain = 0, chip = 40, reg = 28
2020-10-07 18:57:41 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 195, reg = 28, got chain = 0, chip = 40, reg = 28
2020-10-07 18:57:41 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 195, reg = 28, got chain = 0, chip = 40, reg = 28
2020-10-07 18:57:41 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 195, reg = 28, got chain = 0, chip = 40, reg = 28
2020-10-07 18:57:41 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 195, reg = 28, got chain = 0, chip = 40, reg = 28
2020-10-07 18:57:41 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 195, reg = 28, got chain = 0, chip = 40, reg = 28
2020-10-07 18:57:41 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 195, reg = 28, got chain = 0, chip = 40, reg = 28
2020-10-07 18:57:41 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 195, reg = 28, got chain = 0, chip = 40, reg = 28
2020-10-07 18:57:41 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 195, reg = 28, got chain = 0, chip = 40, reg = 28
2020-10-07 18:57:41 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 195, reg = 28, got chain = 0, chip = 40, reg = 28
2020-10-07 18:57:41 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 3, chip = 195, reg = 0
2020-10-07 18:57:41 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 195, reg = 28, got chain = 0, chip = 40, reg = 28
2020-10-07 18:57:41 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 195, reg = 28, got chain = 0, chip = 40, reg = 28
2020-10-07 18:57:42 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 195, reg = 28, got chain = 0, chip = 40, reg = 28
2020-10-07 18:57:42 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 195, reg = 28, got chain = 0, chip = 40, reg = 28
2020-10-07 18:57:42 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 195, reg = 28, got chain = 0, chip = 40, reg = 28
2020-10-07 18:57:42 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 195, reg = 28, got chain = 0, chip = 40, reg = 28
2020-10-07 18:57:42 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 195, reg = 28, got chain = 0, chip = 40, reg = 28
2020-10-07 18:57:42 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 195, reg = 28, got chain = 0, chip = 40, reg = 28
2020-10-07 18:57:42 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 195, reg = 28, got chain = 0, chip = 40, reg = 28
2020-10-07 18:57:42 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 195, reg = 28, got chain = 0, chip = 40, reg = 28
2020-10-07 18:57:42 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 195, reg = 28, got chain = 0, chip = 40, reg = 28
2020-10-07 18:57:42 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 195, reg = 28, got chain = 0, chip = 40, reg = 28
2020-10-07 18:57:42 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 195, reg = 28, got chain = 0, chip = 180, reg = 28
2020-10-07 18:57:42 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 195, reg = 28, got chain = 0, chip = 180, reg = 28
2020-10-07 18:57:42 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 195, reg = 28, got chain = 0, chip = 180, reg = 28
2020-10-07 18:57:42 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 195, reg = 28, got chain = 0, chip = 180, reg = 28
2020-10-07 18:57:42 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 195, reg = 28, got chain = 0, chip = 180, reg = 28
2020-10-07 18:57:42 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 195, reg = 28, got chain = 0, chip = 180, reg = 28
2020-10-07 18:57:42 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 195, reg = 28, got chain = 0, chip = 180, reg = 28
2020-10-07 18:57:42 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 195, reg = 28, got chain = 0, chip = 180, reg = 28
2020-10-07 18:57:42 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 195, reg = 28, got chain = 0, chip = 180, reg = 28
2020-10-07 18:57:42 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 195, reg = 28, got chain = 0, chip = 180, reg = 28
2020-10-07 18:57:42 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 195, reg = 28, got chain = 0, chip = 180, reg = 28
2020-10-07 18:57:42 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 195, reg = 28, got chain = 0, chip = 180, reg = 28
2020-10-07 18:57:42 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 195, reg = 28, got chain = 0, chip = 180, reg = 28
2020-10-07 18:57:42 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 195, reg = 28, got chain = 0, chip = 180, reg = 28
2020-10-07 18:57:42 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 195, reg = 28, got chain = 0, chip = 180, reg = 28
2020-10-07 18:57:42 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 195, reg = 28, got chain = 0, chip = 180, reg = 28
2020-10-07 18:57:42 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 195, reg = 28, got chain = 0, chip = 180, reg = 28
2020-10-07 18:57:42 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 195, reg = 28, got chain = 0, chip = 180, reg = 28
2020-10-07 18:57:42 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 195, reg = 28, got chain = 0, chip = 180, reg = 28
2020-10-07 18:57:42 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 195, reg = 28, got chain = 0, chip = 180, reg = 28
2020-10-07 18:57:42 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 195, reg = 28, got chain = 0, chip = 180, reg = 28
2020-10-07 18:57:42 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 195, reg = 28, got chain = 0, chip = 180, reg = 28
2020-10-07 18:57:42 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 195, reg = 28, got chain = 0, chip = 180, reg = 28
2020-10-07 18:57:42 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 195, reg = 28, got chain = 0, chip = 180, reg = 28
2020-10-07 18:57:42 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 195, reg = 28, got chain = 0, chip = 180, reg = 28
2020-10-07 18:57:42 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 195, reg = 28, got chain = 0, chip = 180, reg = 28
2020-10-07 18:57:43 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 195, reg = 28, got chain = 0, chip = 180, reg = 28
2020-10-07 18:57:43 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 195, reg = 28, got chain = 0, chip = 180, reg = 28
2020-10-07 18:57:43 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 195, reg = 28, got chain = 0, chip = 180, reg = 28
2020-10-07 18:57:43 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 195, reg = 28, got chain = 0, chip = 180, reg = 28
2020-10-07 18:57:43 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 195, reg = 28, got chain = 0, chip = 180, reg = 28
2020-10-07 18:57:43 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 195, reg = 28, got chain = 0, chip = 180, reg = 28
2020-10-07 18:57:43 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 195, reg = 28, got chain = 0, chip = 180, reg = 28
2020-10-07 18:57:43 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 195, reg = 28, got chain = 0, chip = 180, reg = 28
2020-10-07 18:57:43 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 195, reg = 28, got chain = 0, chip = 180, reg = 28
2020-10-07 18:57:43 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 195, reg = 28, got chain = 0, chip = 180, reg = 28
2020-10-07 18:57:43 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 195, reg = 28, got chain = 0, chip = 180, reg = 28
2020-10-07 18:57:43 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 195, reg = 28, got chain = 0, chip = 180, reg = 28
2020-10-07 18:57:43 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 195, reg = 28, got chain = 0, chip = 180, reg = 28
2020-10-07 18:57:43 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 195, reg = 28, got chain = 0, chip = 180, reg = 28
2020-10-07 18:57:43 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 0, chip = 195, reg = 28, got chain = 0, chip = 180, reg = 28
2020-10-07 18:57:43 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 3, chip = 195, reg = 1
2020-10-07 18:57:43 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 1, chip = 55, reg = 28, got chain = 0, chip = 180, reg = 28
2020-10-07 18:57:43 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 1, chip = 55, reg = 28, got chain = 0, chip = 180, reg = 28
2020-10-07 18:57:43 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 1, chip = 55, reg = 28, got chain = 0, chip = 180, reg = 28
2020-10-07 18:57:43 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 1, chip = 55, reg = 28, got chain = 0, chip = 180, reg = 28
2020-10-07 18:57:43 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 1, chip = 55, reg = 28, got chain = 0, chip = 180, reg = 28
2020-10-07 18:57:43 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 1, chip = 55, reg = 28, got chain = 0, chip = 180, reg = 28
2020-10-07 18:57:43 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 1, chip = 55, reg = 28, got chain = 0, chip = 180, reg = 28
2020-10-07 18:57:43 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 1, chip = 55, reg = 28, got chain = 0, chip = 180, reg = 28
2020-10-07 18:57:43 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 1, chip = 55, reg = 28, got chain = 0, chip = 180, reg = 28
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: mikeywith on October 07, 2020, 10:51:16 PM
I tried it on this miner with the latest firmware and it does still work.
Would be great if you could mention that in the thread so that others know it works on the latest firmware as well. While testing that out, I changed the setting multiple times and ran into an issue where the miner did not come up after applying changes to the configuration page. I saw this once before and figured it was just a fluke, but it happened again. Comes back up with a reboot though, so not much of an issue.
Actually, this could be much of an issue, or at least, it will eventually be ( sorry to let you know), but if you follow the kernel closely, you will see these 4 lines. 2020-10-07 18:57:35 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 0, chip = 55, reg = 0 2020-10-07 18:57:39 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 1, chip = 40, reg = 1 2020-10-07 18:57:39 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 2, chip = 180, reg = 0 2020-10-07 18:57:43 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 3, chip = 195, reg = 1 I think your Chain 0 has a bad contact, nothing is wrong with all 4 temp sensors (0,1,2,3), this is a loose chip/heat sink, it hasn't exactly fallen, but it isn't 100% in contact, what usually happens when you see all 4 senors down is that the hash board will work at times, fail to work on another, sometimes it works for a whole week and then goes down, a reboot may fix it, you may need to reboot it 2-3 times, then it works for an hour and drops, the whole miner reboots, eventually and after x period of time (x is purely based on your luck) it will stop hashing and you will have to remove it from the miner for the other two boards to work uninterrupted. To anyone else, I would advise against the attempt of fixing it, but since you said you are planning to fix your host's hash boards, then this chian 0 could be a great start to practice, you will need to figure out which chip is loose, remove it and then solder it back.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: wndsnb on October 07, 2020, 11:28:38 PM
When this happens all of the chains have the same error though, this would lead me to believe that the issue would be not be specific to a single hashboard. Also, I have power cycled and rebooted many times and never saw this issue. It only seems to happen when I update settings and click the "save&apply". 2020-10-07 18:57:35 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 0, chip = 55, reg = 0
2020-10-07 18:57:37 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 1, chip = 40, reg = 0
2020-10-07 18:57:41 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 2, chip = 180, reg = 1
2020-10-07 18:57:43 temperature.c:695:get_temp_info: read temp sensor failed: chain = 0, sensor = 3, chip = 195, reg = 1
2020-10-07 18:57:44 temperature.c:695:get_temp_info: read temp sensor failed: chain = 1, sensor = 0, chip = 55, reg = 0
2020-10-07 18:57:46 temperature.c:695:get_temp_info: read temp sensor failed: chain = 1, sensor = 1, chip = 40, reg = 0
2020-10-07 18:57:48 temperature.c:695:get_temp_info: read temp sensor failed: chain = 1, sensor = 2, chip = 180, reg = 0
2020-10-07 18:57:50 temperature.c:695:get_temp_info: read temp sensor failed: chain = 1, sensor = 3, chip = 195, reg = 0
2020-10-07 18:57:52 temperature.c:695:get_temp_info: read temp sensor failed: chain = 2, sensor = 0, chip = 55, reg = 0
2020-10-07 18:57:54 temperature.c:695:get_temp_info: read temp sensor failed: chain = 2, sensor = 1, chip = 40, reg = 0
2020-10-07 18:57:56 temperature.c:695:get_temp_info: read temp sensor failed: chain = 2, sensor = 2, chip = 180, reg = 0
2020-10-07 18:57:58 temperature.c:695:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 195, reg = 0
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: mikeywith on October 08, 2020, 01:18:28 AM
When this happens all of the chains have the same error though, this would lead me to believe that the issue would be not be specific to a single hashboard. Also, I have power cycled and rebooted many times and never saw this issue. It only seems to happen when I update settings and click the "save&apply".
Is that specific to just this latest firmware? I never had an issue when hitting save and apply, it actually seems like it performs a full reboot when that happens, but since I have not used the latest firmware so I can't really tell, I can only assume it's some sort of a bug, but if a complete reboot solves the problem then I shouldn't worry about it. By the way, thanks for sharing all of this information, only a few people here do, the majority would disappear the moment their miners start hashing away. ;D
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: wndsnb on October 08, 2020, 12:08:01 PM
Is that specific to just this latest firmware?
It is possible, but I didn't do much testing on the miner before I updated the firmware so no way to know. I'll report back if I see it in any of my hosts miners with older firmware. This one is headed back to my host today or tomorrow.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: mikeywith on October 09, 2020, 05:27:18 PM
It is possible, but I didn't do much testing on the miner before I updated the firmware so no way to know. I'll report back if I see it in any of my hosts miners with older firmware. This one is headed back to my host today or tomorrow.
I have tested this on S17 pro running "Wed Dec 25 09:47:07 CST 2019" firmware and when I hit "Save&Apply" the miner performs a full reboot and starts with this line the kernel log Booting Linux on physical CPU 0x0
So I think it's safe to assume that is pretty much just a glitch in the latest firmware.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: wndsnb on October 11, 2020, 01:11:52 PM
So I think it's safe to assume that is pretty much just a glitch in the latest firmware.
That's what it seemed like to me. If not I'll know soon enough, the miner should arrive back at my host on Monday. Another related note, my host let me know that Bitmain finally sent a replacement S17 pro for the one he RMA'ed for me to the California repair center over 4 months ago.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: philipma1957 on October 11, 2020, 01:15:02 PM
so 120 days no machine. or 120 x 50 = 6000 x 0.08 = 480 usd - power cost
that is a low estimate as 0.08 usd is a low number average for 1 th of mining for the last 4 months
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: Moeter81 on October 11, 2020, 06:35:51 PM
Hello everybody,
First of all, I apologize for my bad english.
I have a small farm myself, with S9 and S17 + miners.
I ordered two S17 + 73s directly from Bitmain, one of which had a defective one after a short time and I sent it back and received a new one, this one was a replacement device and didn't work from the start, so I have it again sent back. Then Bitmain sent me a new one, it works until now.
In the meantime, another S17 + 73 has stopped working, also this one, I sent in again and received a new one.
The S17 + 76 have been running without any problems so far.
Currently, an S17 + 67 can only find one chain. Unfortunately, this device is no longer guaranteed.
I've already tried a few things (firmware change), unfortunately without success.
Maybe, with your help, can I get the device working again?
Greetings from Germany
Moeter
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: favebook on October 11, 2020, 06:57:04 PM
Hello, I am sad to greet you into this great forum with bad news.
You have been more than unlucky and your only choice is now to RMA that unit again. If you wish, you can fight (discreetly and professionally) over emails with Bitmain to try to get refund for your miner or maybe to get a discount for newer S19/S19Pro.
Using custom firmware with underclock might help it read some hashboards but that is not a hard fix.
Your problem is 99% loose heatsinks.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: Moeter81 on October 11, 2020, 08:01:17 PM
This is one of the kernel logs: Booting Linux on physical CPU 0x0
Linux version 4.6.0-xilinx-gff8137b-dirty (lzq@armdev2) (gcc version 4.8.3 20140320 (prerelease) (Sourcery CodeBench Lite 2014.05-23) ) #25 SMP PREEMPT Fri Nov 23 15:30:52 CST 2018
CPU: ARMv7 Processor [413fc090] revision 0 (ARMv7), cr=18c5387d
CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
Machine model: Xilinx Zynq
cma: Reserved 16 MiB at 0x0e000000
Memory policy: Data cache writealloc
On node 0 totalpages: 61440
free_area_init_node: node 0, pgdat c0b39280, node_mem_map cde10000
Normal zone: 480 pages used for memmap
Normal zone: 0 pages reserved
Normal zone: 61440 pages, LIFO batch:15
percpu: Embedded 12 pages/cpu @cddf1000 s19776 r8192 d21184 u49152
pcpu-alloc: s19776 r8192 d21184 u49152 alloc=12*4096
pcpu-alloc: [0] 0 [0] 1
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 60960
Kernel command line: mem=240M console=ttyPS0,115200 ramdisk_size=33554432 root=/dev/ram rw earlyprintk
PID hash table entries: 1024 (order: 0, 4096 bytes)
Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
Memory: 203432K/245760K available (6345K kernel code, 231K rwdata, 1896K rodata, 1024K init, 223K bss, 25944K reserved, 16384K cma-reserved, 0K highmem)
Virtual kernel memory layout:
vector : 0xffff0000 - 0xffff1000 ( 4 kB)
fixmap : 0xffc00000 - 0xfff00000 (3072 kB)
vmalloc : 0xcf800000 - 0xff800000 ( 768 MB)
lowmem : 0xc0000000 - 0xcf000000 ( 240 MB)
pkmap : 0xbfe00000 - 0xc0000000 ( 2 MB)
modules : 0xbf000000 - 0xbfe00000 ( 14 MB)
.text : 0xc0008000 - 0xc090c424 (9234 kB)
.init : 0xc0a00000 - 0xc0b00000 (1024 kB)
.data : 0xc0b00000 - 0xc0b39fe0 ( 232 kB)
.bss : 0xc0b39fe0 - 0xc0b71c28 ( 224 kB)
Preemptible hierarchical RCU implementation.
Build-time adjustment of leaf fanout to 32.
RCU restricting CPUs from NR_CPUS=4 to nr_cpu_ids=2.
RCU: Adjusting geometry for rcu_fanout_leaf=32, nr_cpu_ids=2
NR_IRQS:16 nr_irqs:16 16
efuse mapped to cf800000
ps7-slcr mapped to cf802000
L2C: platform modifies aux control register: 0x72360000 -> 0x72760000
L2C: DT/platform modifies aux control register: 0x72360000 -> 0x72760000
L2C-310 erratum 769419 enabled
L2C-310 enabling early BRESP for Cortex-A9
L2C-310 full line of zeros enabled for Cortex-A9
L2C-310 ID prefetch enabled, offset 1 lines
L2C-310 dynamic clock gating enabled, standby mode enabled
L2C-310 cache controller enabled, 8 ways, 512 kB
L2C-310: CACHE_ID 0x410000c8, AUX_CTRL 0x76760001
zynq_clock_init: clkc starts at cf802100
Zynq clock init
sched_clock: 64 bits at 333MHz, resolution 3ns, wraps every 4398046511103ns
clocksource: arm_global_timer: mask: 0xffffffffffffffff max_cycles: 0x4ce07af025, max_idle_ns: 440795209040 ns
Switching to timer-based delay loop, resolution 3ns
clocksource: ttc_clocksource: mask: 0xffff max_cycles: 0xffff, max_idle_ns: 537538477 ns
ps7-ttc #0 at cf80a000, irq=18
Console: colour dummy device 80x30
Calibrating delay loop (skipped), value calculated using timer frequency.. 666.66 BogoMIPS (lpj=3333333)
pid_max: default: 32768 minimum: 301
Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
CPU: Testing write buffer coherency: ok
CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
Setting up static identity map for 0x100000 - 0x100058
CPU1: failed to boot: -1
Brought up 1 CPUs
SMP: Total of 1 processors activated (666.66 BogoMIPS).
CPU: All CPU(s) started in SVC mode.
devtmpfs: initialized
VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4
clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
pinctrl core: initialized pinctrl subsystem
NET: Registered protocol family 16
DMA: preallocated 256 KiB pool for atomic coherent allocations
cpuidle: using governor menu
hw-breakpoint: found 5 (+1 reserved) breakpoint and 1 watchpoint registers.
hw-breakpoint: maximum watchpoint size is 4 bytes.
zynq-ocm f800c000.ps7-ocmc: ZYNQ OCM pool: 256 KiB @ 0xcf880000
vgaarb: loaded
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
media: Linux media interface: v0.10
Linux video capture interface: v2.00
pps_core: LinuxPPS API ver. 1 registered
pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
PTP clock support registered
EDAC MC: Ver: 3.0.0
Advanced Linux Sound Architecture Driver Initialized.
clocksource: Switched to clocksource arm_global_timer
NET: Registered protocol family 2
TCP established hash table entries: 2048 (order: 1, 8192 bytes)
TCP bind hash table entries: 2048 (order: 2, 16384 bytes)
TCP: Hash tables configured (established 2048 bind 2048)
UDP hash table entries: 256 (order: 1, 8192 bytes)
UDP-Lite hash table entries: 256 (order: 1, 8192 bytes)
NET: Registered protocol family 1
RPC: Registered named UNIX socket transport module.
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
PCI: CLS 0 bytes, default 64
Trying to unpack rootfs image as initramfs...
rootfs image is not initramfs (no cpio magic); looks like an initrd
Freeing initrd memory: 12904K (cce67000 - cdb01000)
hw perfevents: enabled with armv7_cortex_a9 PMU driver, 7 counters available
futex hash table entries: 512 (order: 3, 32768 bytes)
workingset: timestamp_bits=28 max_order=16 bucket_order=0
jffs2: version 2.2. (NAND) (SUMMARY) © 2001-2006 Red Hat, Inc.
io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered (default)
dma-pl330 f8003000.ps7-dma: Loaded driver for PL330 DMAC-241330
dma-pl330 f8003000.ps7-dma: DBUFF-128x8bytes Num_Chans-8 Num_Peri-4 Num_Events-16
e0000000.serial: ttyPS0 at MMIO 0xe0000000 (irq = 158, base_baud = 6249999) is a xuartps
console [ttyPS0] enabled
xdevcfg f8007000.ps7-dev-cfg: ioremap 0xf8007000 to cf86e000
[drm] Initialized drm 1.1.0 20060810
brd: module loaded
loop: module loaded
CAN device driver interface
gpiod_set_value: invalid GPIO
libphy: MACB_mii_bus: probed
macb e000b000.ethernet eth0: Cadence GEM rev 0x00020118 at 0xe000b000 irq 31 (00:0a:35:00:00:00)
Generic PHY e000b000.etherne:00: attached PHY driver [Generic PHY] (mii_bus:phy_addr=e000b000.etherne:00, irq=-1)
e1000e: Intel(R) PRO/1000 Network Driver - 3.2.6-k
e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
ehci-pci: EHCI PCI platform driver
usbcore: registered new interface driver usb-storage
mousedev: PS/2 mouse device common for all mice
i2c /dev entries driver
Xilinx Zynq CpuIdle Driver started
sdhci: Secure Digital Host Controller Interface driver
sdhci: Copyright(c) Pierre Ossman
sdhci-pltfm: SDHCI platform and OF driver helper
mmc0: SDHCI controller on e0100000.ps7-sdio [e0100000.ps7-sdio] using ADMA
ledtrig-cpu: registered to indicate activity on CPUs
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
nand: device found, Manufacturer ID: 0x2c, Chip ID: 0xda
nand: Micron MT29F2G08ABAGAWP
nand: 256 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 128
nand: WARNING: pl35x-nand: the ECC used on your system is too weak compared to the one required by the NAND chip
Bad block table found at page 131008, version 0x01
Bad block table found at page 130944, version 0x01
6 ofpart partitions found on MTD device pl35x-nand
Creating 6 MTD partitions on "pl35x-nand":
0x000000000000-0x000002800000 : "BOOT.bin-env-dts-kernel"
0x000002800000-0x000004800000 : "ramfs"
0x000004800000-0x000005000000 : "configs"
0x000005000000-0x000006000000 : "reserve"
0x000006000000-0x000008000000 : "ramfs-bak"
0x000008000000-0x000010000000 : "reserve1"
NET: Registered protocol family 10
sit: IPv6 over IPv4 tunneling driver
NET: Registered protocol family 17
can: controller area network core (rev 20120528 abi 9)
NET: Registered protocol family 29
can: raw protocol (rev 20120528)
can: broadcast manager protocol (rev 20120528 t)
can: netlink gateway (rev 20130117) max_hops=1
zynq_pm_ioremap: no compatible node found for 'xlnx,zynq-ddrc-a05'
zynq_pm_late_init: Unable to map DDRC IO memory.
Registering SWP/SWPB emulation handler
hctosys: unable to open rtc device (rtc0)
ALSA device list:
No soundcards found.
RAMDISK: gzip image found at block 0
EXT4-fs (ram0): couldn't mount as ext3 due to feature incompatibilities
EXT4-fs (ram0): mounted filesystem without journal. Opts: (null)
VFS: Mounted root (ext4 filesystem) on device 1:0.
devtmpfs: mounted
Freeing unused kernel memory: 1024K (c0a00000 - c0b00000)
EXT4-fs (ram0): re-mounted. Opts: block_validity,delalloc,barrier,user_xattr
random: dd urandom read with 0 bits of entropy available
ubi0: attaching mtd2
ubi0: scanning is finished
ubi0: attached mtd2 (name "configs", size 8 MiB)
ubi0: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
ubi0: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
ubi0: VID header offset: 2048 (aligned 2048), data offset: 4096
ubi0: good PEBs: 64, bad PEBs: 0, corrupted PEBs: 0
ubi0: user volume: 1, internal volumes: 1, max. volumes count: 128
ubi0: max/mean erase counter: 20/9, WL threshold: 4096, image sequence number: 237714726
ubi0: available PEBs: 0, total reserved PEBs: 64, PEBs reserved for bad PEB handling: 40
ubi0: background thread "ubi_bgt0d" started, PID 708
UBIFS (ubi0:0): background thread "ubifs_bgt0_0" started, PID 711
UBIFS (ubi0:0): UBIFS: mounted UBI device 0, volume 0, name "configs"
UBIFS (ubi0:0): LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
UBIFS (ubi0:0): FS size: 1396736 bytes (1 MiB, 11 LEBs), journal size 888833 bytes (0 MiB, 5 LEBs)
UBIFS (ubi0:0): reserved for root: 65970 bytes (64 KiB)
UBIFS (ubi0:0): media format: w4/r0 (latest is w4/r0), UUID FF09433B-E002-4C29-97EC-6220DDC4BB36, 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: 3361/788, WL threshold: 4096, image sequence number: 3265111179
ubi1: available PEBs: 0, total reserved PEBs: 1020, PEBs reserved for bad PEB handling: 36
ubi1: background thread "ubi_bgt1d" started, PID 720
UBIFS (ubi1:0): background thread "ubifs_bgt1_0" started, PID 723
UBIFS (ubi1:0): UBIFS: mounted UBI device 1, volume 0, name "reserve1"
UBIFS (ubi1:0): LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
UBIFS (ubi1:0): FS size: 123039744 bytes (117 MiB, 969 LEBs), journal size 6221824 bytes (5 MiB, 49 LEBs)
UBIFS (ubi1:0): reserved for root: 4952683 bytes (4836 KiB)
UBIFS (ubi1:0): media format: w4/r0 (latest is w4/r0), UUID 1AF6F1E1-61F0-462C-AE44-C7D9596CF7E2, 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 = 0xb023
In fpga mem driver!
request_mem_region OK!
fpga mem virtual address is 0xd2000000
random: nonblocking pool is initialized
2020-10-11 05:55:51 driver-btm-api.c:779:init_freq_mode: This is scan-user version
2020-10-11 05:55:51 driver-btm-api.c:2451:bitmain_soc_init: opt_multi_version = 1
2020-10-11 05:55:51 driver-btm-api.c:2452:bitmain_soc_init: opt_bitmain_ab = 1
2020-10-11 05:55:51 driver-btm-api.c:2453:bitmain_soc_init: opt_bitmain_work_mode = 0
2020-10-11 05:55:51 driver-btm-api.c:2454:bitmain_soc_init: Miner compile time: Tue Jun 2 10:31:07 CST 2020 type: Antminer S17+
2020-10-11 05:55:51 driver-btm-api.c:2455:bitmain_soc_init: commit version: 1ca50a5 2020-06-01 18:51:22, build by: lol 2020-06-02 10:37:21
2020-10-11 05:55:51 driver-btm-api.c:2083:show_sn: len:16, 8048ed0c2b104814
2020-10-11 05:55:51 driver-btm-api.c:2461:bitmain_soc_init: show sn return 1
2020-10-11 05:55:51 driver-btm-api.c:2103:handle_sn_for_factory_mode: show sn return 1
2020-10-11 05:55:51 driver-btm-api.c:2141:handle_sn_for_factory_mode: read sn success, 8048ed0c2b104814
2020-10-11 05:55:51 fan.c:284:front_fan_power_on: Note: front fan is power on!
2020-10-11 05:55:51 fan.c:296:rear_fan_power_on: Note: rear fan is power on!
2020-10-11 05:55:51 driver-btm-api.c:1314:miner_device_init: Detect 256MB control board of XILINX
2020-10-11 05:55:51 driver-btm-api.c:1255:init_fan_parameter: fan_eft : 0 fan_pwm : 0
2020-10-11 05:55:57 driver-btm-api.c:1239:init_miner_version: miner ID : 8048ed0c2b104814
2020-10-11 05:55:57 driver-btm-api.c:1245:init_miner_version: FPGA Version = 0xB023
2020-10-11 05:55:57 chain = 0, mode = 0, load_done = false.
2020-10-11 05:55:57 chain = 1, mode = 0, load_done = false.
2020-10-11 05:55:57 chain = 2, mode = 0, load_done = false.
2020-10-11 05:55:57 chain = 0, load_done = false
2020-10-11 05:55:57 chain = 1, load_done = false
2020-10-11 05:55:57 chain = 2, load_done = false
2020-10-11 05:56:02 chain = 0, mode = 0, load_done = false.
2020-10-11 05:56:02 chain = 1, mode = 0, load_done = false.
2020-10-11 05:56:02 chain = 2, mode = 0, load_done = false.
2020-10-11 05:56:02 chain = 0, load_done = false
2020-10-11 05:56:02 chain = 1, load_done = false
2020-10-11 05:56:02 chain = 2, load_done = false
2020-10-11 05:56:02 driver-btm-api.c:837:get_product_id: product_id[0] = 0
2020-10-11 05:56:02 driver-btm-api.c:837:get_product_id: product_id[1] = 0
2020-10-11 05:56:02 driver-btm-api.c:837:get_product_id: product_id[2] = 0
2020-10-11 05:56:02 driver-btm-api.c:2234:update_conf_by_power_feedback: Power feedback is disabled
2020-10-11 05:56:02 driver-btm-api.c:2202:get_calibration_voltage: calibration voltage flag is error data.
2020-10-11 05:56:02 driver-btm-api.c:2268:update_conf_by_power_feedback: Note: no calibration voltage, default diff = 0
2020-10-11 05:56:02 frequency.c:1457:adjust_higer_max_vol_table: adjust_higer_max_vol_table, adjust_vol = 0
2020-10-11 05:56:02 thread.c:1363:create_read_nonce_reg_thread: create thread
2020-10-11 05:56:07 frequency.c:205:get_ideal_hash_rate_GH: ideal_hash_rate = 67628
2020-10-11 05:56:08 driver-btm-api.c:1239:init_miner_version: miner ID : 8048ed0c2b104814
2020-10-11 05:56:08 driver-btm-api.c:1245:init_miner_version: FPGA Version = 0xB023
2020-10-11 05:56:12 chain = 0, load_done = false
2020-10-11 05:56:12 chain = 1, load_done = false
2020-10-11 05:56:12 chain = 2, load_done = false
2020-10-11 05:56:14 driver-btm-api.c:837:get_product_id: product_id[0] = 0
2020-10-11 05:56:14 driver-btm-api.c:837:get_product_id: product_id[1] = 0
2020-10-11 05:56:14 driver-btm-api.c:837:get_product_id: product_id[2] = 0
2020-10-11 05:56:14 driver-btm-api.c:792:_set_project_type: project:0
2020-10-11 05:56:14 driver-btm-api.c:813:_set_project_type: Project type: Antminer S17+
2020-10-11 05:56:14 driver-btm-api.c:824:dump_pcb_bom_version: Chain [0] PCB Version: 0x0100
2020-10-11 05:56:14 driver-btm-api.c:825:dump_pcb_bom_version: Chain [0] BOM Version: 0x0100
2020-10-11 05:56:14 driver-btm-api.c:824:dump_pcb_bom_version: Chain [1] PCB Version: 0x0100
2020-10-11 05:56:14 driver-btm-api.c:825:dump_pcb_bom_version: Chain [1] BOM Version: 0x0100
2020-10-11 05:56:14 driver-btm-api.c:824:dump_pcb_bom_version: Chain [2] PCB Version: 0x0100
2020-10-11 05:56:14 driver-btm-api.c:825:dump_pcb_bom_version: Chain [2] BOM Version: 0x0100
2020-10-11 05:56:16 driver-btm-api.c:2372:bitmain_board_init: Fan check passed.
2020-10-11 05:56:17 board.c:36:jump_and_app_check_restore_pic: chain[0] PIC jump to app
2020-10-11 05:56:19 board.c:40:jump_and_app_check_restore_pic: Check chain[0] PIC fw version=0x88
2020-10-11 05:56:20 board.c:36:jump_and_app_check_restore_pic: chain[1] PIC jump to app
2020-10-11 05:56:22 board.c:40:jump_and_app_check_restore_pic: Check chain[1] PIC fw version=0x88
2020-10-11 05:56:23 board.c:36:jump_and_app_check_restore_pic: chain[2] PIC jump to app
2020-10-11 05:56:25 board.c:40:jump_and_app_check_restore_pic: Check chain[2] PIC fw version=0x88
2020-10-11 05:56:25 thread.c:1358:create_pic_heart_beat_thread: create thread
2020-10-11 05:56:25 power_api.c:213:power_init: Power init:
2020-10-11 05:56:25 power_api.c:214:power_init: current_voltage_raw = 0
2020-10-11 05:56:25 power_api.c:215:power_init: highest_voltage_raw = 2100
2020-10-11 05:56:25 power_api.c:216:power_init: working_voltage_raw = 1950
2020-10-11 05:56:25 power_api.c:217:power_init: higher_voltage_raw = 2040
2020-10-11 05:56:25 power_api.c:218:power_init: check_asic_voltage_raw = 2100
2020-10-11 05:56:25 driver-btm-api.c:2382:bitmain_board_init: Enter 30s sleep to make sure power release finish.
2020-10-11 05:56:25 power_api.c:186:power_off: init gpio907
2020-10-11 05:56:57 power_api.c:324:set_to_highest_voltage_by_steps: Set to voltage raw 2100, step by step.
2020-10-11 05:57:23 power_api.c:85:check_voltage_multi: retry time: 0
2020-10-11 05:57:24 power_api.c:40:_get_avg_voltage: chain = 0, voltage = 21.108418
2020-10-11 05:57:25 power_api.c:40:_get_avg_voltage: chain = 1, voltage = 21.006361
2020-10-11 05:57:26 power_api.c:40:_get_avg_voltage: chain = 2, voltage = 21.132653
2020-10-11 05:57:26 power_api.c:53:_get_avg_voltage: average_voltage = 21.082477
2020-10-11 05:57:26 power_api.c:71:check_voltage: target_vol = 21.00, actural_vol = 21.08, check voltage passed.
2020-10-11 05:57:26 uart.c:72:set_baud: set fpga_baud to 115200
2020-10-11 05:57:37 driver-btm-api.c:1134:check_asic_number_with_power_on: Chain[0]: find 8 asic, times 0
2020-10-11 05:57:48 driver-btm-api.c:1134:check_asic_number_with_power_on: Chain[0]: find 8 asic, times 1
2020-10-11 05:57:59 driver-btm-api.c:1134:check_asic_number_with_power_on: Chain[0]: find 8 asic, times 2
2020-10-11 05:57:59 power_api.c:380:modify_check_asic_voltage: check_asic_voltage_raw = 2100
chain 0, IO_DRIVE_STRENGTH_CONFIGURATION reg = 0x f1fffff
2020-10-11 05:58:08 driver-btm-api.c:1157:check_asic_number_with_power_on: Chain[0]: find 8 asic, times 3
2020-10-11 05:58:08 power_api.c:380:modify_check_asic_voltage: check_asic_voltage_raw = 2050
2020-10-11 05:58:08 power_api.c:364:set_to_check_asic_voltage_by_steps: Set to voltage raw 2050, step by step.
2020-10-11 05:58:12 power_api.c:85:check_voltage_multi: retry time: 0
2020-10-11 05:58:13 power_api.c:40:_get_avg_voltage: chain = 0, voltage = 20.547073
2020-10-11 05:58:14 power_api.c:40:_get_avg_voltage: chain = 1, voltage = 20.474554
2020-10-11 05:58:15 power_api.c:40:_get_avg_voltage: chain = 2, voltage = 20.599489
2020-10-11 05:58:15 power_api.c:53:_get_avg_voltage: average_voltage = 20.540372
2020-10-11 05:58:15 power_api.c:71:check_voltage: target_vol = 20.50, actural_vol = 20.54, check voltage passed.
chain 0, IO_DRIVE_STRENGTH_CONFIGURATION reg = 0x f1fffff
2020-10-11 05:58:24 driver-btm-api.c:1157:check_asic_number_with_power_on: Chain[0]: find 8 asic, times 4
2020-10-11 05:58:24 power_api.c:380:modify_check_asic_voltage: check_asic_voltage_raw = 2000
2020-10-11 05:58:24 power_api.c:364:set_to_check_asic_voltage_by_steps: Set to voltage raw 2000, step by step.
2020-10-11 05:58:28 power_api.c:85:check_voltage_multi: retry time: 0
2020-10-11 05:58:29 power_api.c:40:_get_avg_voltage: chain = 0, voltage = 20.063613
2020-10-11 05:58:30 power_api.c:40:_get_avg_voltage: chain = 1, voltage = 20.040765
2020-10-11 05:58:31 power_api.c:40:_get_avg_voltage: chain = 2, voltage = 20.114796
2020-10-11 05:58:31 power_api.c:53:_get_avg_voltage: average_voltage = 20.073058
2020-10-11 05:58:31 power_api.c:71:check_voltage: target_vol = 20.00, actural_vol = 20.07, check voltage passed.
chain 0, IO_DRIVE_STRENGTH_CONFIGURATION reg = 0x f1fffff
2020-10-11 05:58:40 driver-btm-api.c:1157:check_asic_number_with_power_on: Chain[0]: find 8 asic, times 5
2020-10-11 05:58:40 power_api.c:380:modify_check_asic_voltage: check_asic_voltage_raw = 2100
2020-10-11 05:58:40 power_api.c:364:set_to_check_asic_voltage_by_steps: Set to voltage raw 2100, step by step.
2020-10-11 05:58:45 power_api.c:85:check_voltage_multi: retry time: 0
2020-10-11 05:58:46 power_api.c:40:_get_avg_voltage: chain = 0, voltage = 21.030534
2020-10-11 05:58:47 power_api.c:40:_get_avg_voltage: chain = 1, voltage = 20.982188
2020-10-11 05:58:48 power_api.c:40:_get_avg_voltage: chain = 2, voltage = 21.084183
2020-10-11 05:58:48 power_api.c:53:_get_avg_voltage: average_voltage = 21.032302
2020-10-11 05:58:48 power_api.c:71:check_voltage: target_vol = 21.00, actural_vol = 21.03, check voltage passed.
2020-10-11 05:58:48 driver-btm-api.c:1193:check_asic_number: Chain 0 only find 8 asic, will power off hash board 0
2020-10-11 05:58:50 driver-btm-api.c:1195:check_asic_number: Chain 0 voltage: an0 = 2.816129, an2 2.806452, an6 2.532258.
2020-10-11 05:58:52 frequency.c:205:get_ideal_hash_rate_GH: ideal_hash_rate = 44631
2020-10-11 05:59:02 driver-btm-api.c:1134:check_asic_number_with_power_on: Chain[1]: find 65 asic, times 0
2020-10-11 05:59:12 driver-btm-api.c:1134:check_asic_number_with_power_on: Chain[2]: find 0 asic, times 0
2020-10-11 05:59:23 driver-btm-api.c:1134:check_asic_number_with_power_on: Chain[2]: find 0 asic, times 1
2020-10-11 05:59:34 driver-btm-api.c:1134:check_asic_number_with_power_on: Chain[2]: find 0 asic, times 2
2020-10-11 05:59:34 power_api.c:380:modify_check_asic_voltage: check_asic_voltage_raw = 2100
chain 2, IO_DRIVE_STRENGTH_CONFIGURATION reg = 0x f1fffff
2020-10-11 05:59:42 driver-btm-api.c:1157:check_asic_number_with_power_on: Chain[2]: find 0 asic, times 3
2020-10-11 05:59:42 power_api.c:380:modify_check_asic_voltage: check_asic_voltage_raw = 2050
2020-10-11 05:59:42 power_api.c:364:set_to_check_asic_voltage_by_steps: Set to voltage raw 2050, step by step.
2020-10-11 05:59:46 power_api.c:85:check_voltage_multi: retry time: 0
2020-10-11 05:59:47 power_api.c:40:_get_avg_voltage: chain = 1, voltage = 20.474554
2020-10-11 05:59:48 power_api.c:40:_get_avg_voltage: chain = 2, voltage = 20.547073
2020-10-11 05:59:48 power_api.c:53:_get_avg_voltage: average_voltage = 20.510814
2020-10-11 05:59:48 power_api.c:71:check_voltage: target_vol = 20.50, actural_vol = 20.51, check voltage passed.
chain 2, IO_DRIVE_STRENGTH_CONFIGURATION reg = 0x f1fffff
2020-10-11 05:59:57 driver-btm-api.c:1157:check_asic_number_with_power_on: Chain[2]: find 0 asic, times 4
2020-10-11 05:59:57 power_api.c:380:modify_check_asic_voltage: check_asic_voltage_raw = 2000
2020-10-11 05:59:57 power_api.c:364:set_to_check_asic_voltage_by_steps: Set to voltage raw 2000, step by step.
2020-10-11 06:00:00 power_api.c:85:check_voltage_multi: retry time: 0
2020-10-11 06:00:01 power_api.c:40:_get_avg_voltage: chain = 1, voltage = 19.991094
2020-10-11 06:00:02 power_api.c:40:_get_avg_voltage: chain = 2, voltage = 20.089173
2020-10-11 06:00:02 power_api.c:53:_get_avg_voltage: average_voltage = 20.040133
2020-10-11 06:00:02 power_api.c:71:check_voltage: target_vol = 20.00, actural_vol = 20.04, check voltage passed.
chain 2, IO_DRIVE_STRENGTH_CONFIGURATION reg = 0x f1fffff
2020-10-11 06:00:11 driver-btm-api.c:1157:check_asic_number_with_power_on: Chain[2]: find 0 asic, times 5
2020-10-11 06:00:11 power_api.c:380:modify_check_asic_voltage: check_asic_voltage_raw = 2100
2020-10-11 06:00:11 power_api.c:364:set_to_check_asic_voltage_by_steps: Set to voltage raw 2100, step by step.
2020-10-11 06:00:16 power_api.c:85:check_voltage_multi: retry time: 0
2020-10-11 06:00:17 power_api.c:40:_get_avg_voltage: chain = 1, voltage = 20.982188
2020-10-11 06:00:18 power_api.c:40:_get_avg_voltage: chain = 2, voltage = 21.057326
2020-10-11 06:00:18 power_api.c:53:_get_avg_voltage: average_voltage = 21.019757
2020-10-11 06:00:18 power_api.c:71:check_voltage: target_vol = 21.00, actural_vol = 21.02, check voltage passed.
2020-10-11 06:00:18 driver-btm-api.c:1193:check_asic_number: Chain 2 only find 0 asic, will power off hash board 2
2020-10-11 06:00:19 driver-btm-api.c:1195:check_asic_number: Chain 2 voltage: an0 = 2.816129, an2 2.809677, an6 2.535484.
2020-10-11 06:00:23 frequency.c:205:get_ideal_hash_rate_GH: ideal_hash_rate = 22571
2020-10-11 06:00:23 driver-hash-chip.c:266:set_uart_relay: set uart relay to 0x330003
2020-10-11 06:00:23 driver-btm-api.c:435:set_order_clock: chain[1]: set order clock, stragegy 3
2020-10-11 06:00:23 driver-hash-chip.c:502:set_clock_delay_control: core_data = 0x34
2020-10-11 06:00:23 driver-btm-api.c:1892:check_clock_counter: freq 50 clock_counter_limit 6
2020-10-11 06:00:24 voltage[1] = 1980
2020-10-11 06:00:24 power_api.c:226:set_working_voltage_raw: working_voltage_raw = 1980
2020-10-11 06:00:25 temperature.c:340:calibrate_temp_sensor_one_chain: chain 1 temp sensor NCT218
2020-10-11 06:00:25 uart.c:72:set_baud: set fpga_baud to 12000000
2020-10-11 06:00:25 driver-btm-api.c:293:check_bringup_temp: Bring up temperature is 17
2020-10-11 06:00:25 thread.c:1378:create_check_miner_status_thread: create thread
2020-10-11 06:00:25 thread.c:1368:create_show_miner_status_thread: create thread
2020-10-11 06:00:25 thread.c:1348:create_temperature_monitor_thread: create thread
2020-10-11 06:00:25 frequency.c:514:check_bringup_temp_dec_freq: dec freq = 0 when bringup temp = 17 dec_freq_index=0
2020-10-11 06:00:25 freq_tuning.c:183:freq_tuning_get_max_freq: Max freq of tuning is 650
2020-10-11 06:00:25 driver-btm-api.c:1765:send_null_work: [DEBUG] Send null work.
2020-10-11 06:00:25 thread.c:1338:create_asic_status_monitor_thread: create thread
2020-10-11 06:00:25 frequency.c:1110:inc_freq_with_fixed_vco: chain = 255, freq = 530, is_higher_voltage = true
2020-10-11 06:00:27 frequency.c:205:get_ideal_hash_rate_GH: ideal_hash_rate = 22571
2020-10-11 06:01:47 power_api.c:352:set_to_voltage_by_steps: Set to voltage raw 2090, step by step.
2020-10-11 06:01:48 power_api.c:85:check_voltage_multi: retry time: 0
2020-10-11 06:01:49 power_api.c:40:_get_avg_voltage: chain = 1, voltage = 20.834816
2020-10-11 06:01:49 power_api.c:53:_get_avg_voltage: average_voltage = 20.834816
2020-10-11 06:01:49 power_api.c:71:check_voltage: target_vol = 20.90, actural_vol = 20.83, check voltage passed.
2020-10-11 06:02:53 power_api.c:352:set_to_voltage_by_steps: Set to voltage raw 2080, step by step.
2020-10-11 06:02:55 power_api.c:85:check_voltage_multi: retry time: 0
2020-10-11 06:02:56 power_api.c:40:_get_avg_voltage: chain = 1, voltage = 20.740457
2020-10-11 06:02:56 power_api.c:53:_get_avg_voltage: average_voltage = 20.740457
2020-10-11 06:02:56 power_api.c:71:check_voltage: target_vol = 20.80, actural_vol = 20.74, check voltage passed.
2020-10-11 06:03:37 power_api.c:352:set_to_voltage_by_steps: Set to voltage raw 2060, step by step.
2020-10-11 06:03:38 power_api.c:85:check_voltage_multi: retry time: 0
2020-10-11 06:03:39 power_api.c:40:_get_avg_voltage: chain = 1, voltage = 20.547073
2020-10-11 06:03:39 power_api.c:53:_get_avg_voltage: average_voltage = 20.547073
2020-10-11 06:03:39 power_api.c:71:check_voltage: target_vol = 20.60, actural_vol = 20.55, check voltage passed.
2020-10-11 06:05:40 driver-btm-api.c:765:set_timeout: freq = 530, percent = 90, hcn = 44236, timeout = 83
2020-10-11 06:05:40 frequency.c:1429:check_initial_temperature_status: need to set higer voltage,vol_higher:2080,vol_limit:2100
2020-10-11 06:05:40 power_api.c:232:set_higher_voltage_raw: higher_voltage_raw = 2080
2020-10-11 06:05:40 power_api.c:338:set_to_higher_voltage_by_steps: Set to voltage raw 2080, step by step.
2020-10-11 06:05:42 power_api.c:85:check_voltage_multi: retry time: 0
2020-10-11 06:05:43 power_api.c:40:_get_avg_voltage: chain = 1, voltage = 20.716284
2020-10-11 06:05:43 power_api.c:53:_get_avg_voltage: average_voltage = 20.716284
2020-10-11 06:05:43 power_api.c:71:check_voltage: target_vol = 20.80, actural_vol = 20.72, check voltage passed.
2020-10-11 06:05:43 thread.c:1373:create_check_system_status_thread: create thread
2020-10-11 06:05:44 driver-btm-api.c:2618:bitmain_soc_init: Init done!
2020-10-11 06:05:44 driver-btm-api.c:222:set_miner_status: STATUS_INIT
2020-10-11 06:05:48 driver-btm-api.c:222:set_miner_status: STATUS_OKAY
2020-10-11 06:05:49 frequency.c:223:get_sale_hash_rate_GH: sale_hash_rate = 22000
2020-10-11 06:05:53 driver-btm-api.c:1496:dhash_chip_send_job: Version num 4.
2020-10-11 06:05:53 driver-btm-api.c:1644:dhash_chip_send_job: stime.tv_sec 1602396353, block_ntime 1602396335
2020-10-11 06:15:57 thread.c:506:check_working_voltage: current PCB min temperature is 39
2020-10-11 06:15:57 thread.c:507:check_working_voltage: current voltage is 2080, recovery to 1980
2020-10-11 06:15:57 power_api.c:310:set_to_working_voltage_by_steps: Set to voltage raw 1980, step by step.
2020-10-11 06:16:02 power_api.c:85:check_voltage_multi: retry time: 0
2020-10-11 06:16:03 power_api.c:40:_get_avg_voltage: chain = 1, voltage = 19.797709
2020-10-11 06:16:03 power_api.c:53:_get_avg_voltage: average_voltage = 19.797709
2020-10-11 06:16:03 power_api.c:71:check_voltage: target_vol = 19.80, actural_vol = 19.80, check voltage passed.
2020-10-11 06:46:03 thread.c:259:calc_hashrate_avg: avg rate is 22863.91 in 40 mins
2020-10-11 06:46:03 temperature.c:516:temp_statistics_show: pcb temp 40~68 chip temp 57~80
2020-10-11 07:16:04 thread.c:259:calc_hashrate_avg: avg rate is 23045.18 in 30 mins
2020-10-11 07:16:04 temperature.c:516:temp_statistics_show: pcb temp 40~68 chip temp 58~79
2020-10-11 07:46:05 thread.c:259:calc_hashrate_avg: avg rate is 22974.36 in 30 mins
2020-10-11 07:46:05 temperature.c:516:temp_statistics_show: pcb temp 39~68 chip temp 57~79
2020-10-11 08:16:06 thread.c:259:calc_hashrate_avg: avg rate is 23042.13 in 30 mins
2020-10-11 08:16:06 temperature.c:516:temp_statistics_show: pcb temp 39~68 chip temp 57~80
2020-10-11 08:46:07 thread.c:259:calc_hashrate_avg: avg rate is 22973.14 in 30 mins
2020-10-11 08:46:07 temperature.c:516:temp_statistics_show: pcb temp 40~68 chip temp 58~79
2020-10-11 09:16:08 thread.c:259:calc_hashrate_avg: avg rate is 22989.62 in 30 mins
2020-10-11 09:16:08 temperature.c:516:temp_statistics_show: pcb temp 39~68 chip temp 57~80
2020-10-11 09:46:09 thread.c:259:calc_hashrate_avg: avg rate is 22909.55 in 30 mins
2020-10-11 09:46:09 temperature.c:516:temp_statistics_show: pcb temp 41~68 chip temp 59~80
2020-10-11 10:16:09 thread.c:259:calc_hashrate_avg: avg rate is 23078.76 in 30 mins
2020-10-11 10:16:09 temperature.c:516:temp_statistics_show: pcb temp 40~68 chip temp 58~79
2020-10-11 10:46:10 thread.c:259:calc_hashrate_avg: avg rate is 22991.45 in 30 mins
2020-10-11 10:46:10 temperature.c:516:temp_statistics_show: pcb temp 41~68 chip temp 59~79
2020-10-11 11:16:11 thread.c:259:calc_hashrate_avg: avg rate is 22983.52 in 30 mins
2020-10-11 11:16:11 temperature.c:516:temp_statistics_show: pcb temp 41~69 chip temp 58~80
2020-10-11 11:46:12 thread.c:259:calc_hashrate_avg: avg rate is 22957.27 in 30 mins
2020-10-11 11:46:12 temperature.c:516:temp_statistics_show: pcb temp 42~69 chip temp 60~80
2020-10-11 12:16:13 thread.c:259:calc_hashrate_avg: avg rate is 23120.88 in 30 mins
2020-10-11 12:16:13 temperature.c:516:temp_statistics_show: pcb temp 43~69 chip temp 62~80
2020-10-11 12:46:14 thread.c:259:calc_hashrate_avg: avg rate is 22852.87 in 30 mins
2020-10-11 12:46:14 temperature.c:516:temp_statistics_show: pcb temp 42~68 chip temp 59~79
2020-10-11 13:16:15 thread.c:259:calc_hashrate_avg: avg rate is 22971.92 in 30 mins
2020-10-11 13:16:15 temperature.c:516:temp_statistics_show: pcb temp 43~69 chip temp 61~80
2020-10-11 13:46:16 thread.c:259:calc_hashrate_avg: avg rate is 23115.40 in 30 mins
2020-10-11 13:46:16 temperature.c:516:temp_statistics_show: pcb temp 43~68 chip temp 61~79
2020-10-11 14:16:17 thread.c:259:calc_hashrate_avg: avg rate is 22786.94 in 30 mins
2020-10-11 14:16:17 temperature.c:516:temp_statistics_show: pcb temp 43~68 chip temp 61~79
2020-10-11 14:46:17 thread.c:259:calc_hashrate_avg: avg rate is 23122.71 in 30 mins
2020-10-11 14:46:17 temperature.c:516:temp_statistics_show: pcb temp 43~68 chip temp 61~79
2020-10-11 15:16:18 thread.c:259:calc_hashrate_avg: avg rate is 22621.49 in 30 mins
2020-10-11 15:16:18 temperature.c:516:temp_statistics_show: pcb temp 43~68 chip temp 62~80
2020-10-11 15:46:19 thread.c:259:calc_hashrate_avg: avg rate is 22967.64 in 30 mins
2020-10-11 15:46:19 temperature.c:516:temp_statistics_show: pcb temp 42~67 chip temp 60~79
2020-10-11 16:16:20 thread.c:259:calc_hashrate_avg: avg rate is 23059.83 in 30 mins
2020-10-11 16:16:20 temperature.c:516:temp_statistics_show: pcb temp 42~68 chip temp 60~79
2020-10-11 16:46:21 thread.c:259:calc_hashrate_avg: avg rate is 22704.52 in 30 mins
2020-10-11 16:46:21 temperature.c:516:temp_statistics_show: pcb temp 43~68 chip temp 60~79
2020-10-11 17:13:12 driver-btm-api.c:222:set_miner_status: WARN_NET_LOST
2020-10-11 17:13:49 driver-btm-api.c:1496:dhash_chip_send_job: Version num 1.
2020-10-11 17:14:07 driver-btm-api.c:1496:dhash_chip_send_job: Version num 4.
2020-10-11 17:14:08 driver-btm-api.c:222:set_miner_status: STATUS_OKAY
2020-10-11 17:16:22 thread.c:259:calc_hashrate_avg: avg rate is 22981.69 in 30 mins
2020-10-11 17:16:22 temperature.c:516:temp_statistics_show: pcb temp 42~68 chip temp 60~79
2020-10-11 17:46:23 thread.c:259:calc_hashrate_avg: avg rate is 23023.77 in 30 mins
2020-10-11 17:46:23 temperature.c:516:temp_statistics_show: pcb temp 43~68 chip temp 62~79
2020-10-11 17:56:41 driver-btm-api.c:1496:dhash_chip_send_job: Version num 1.
2020-10-11 17:57:12 driver-btm-api.c:1496:dhash_chip_send_job: Version num 4.
2020-10-11 18:03:49 driver-btm-api.c:1496:dhash_chip_send_job: Version num 1.
2020-10-11 18:04:12 driver-btm-api.c:222:set_miner_status: WARN_NET_LOST
2020-10-11 18:04:21 driver-btm-api.c:1496:dhash_chip_send_job: Version num 4.
2020-10-11 18:04:21 driver-btm-api.c:222:set_miner_status: STATUS_OKAY
2020-10-11 18:16:24 thread.c:259:calc_hashrate_avg: avg rate is 22183.76 in 30 mins
2020-10-11 18:16:24 temperature.c:516:temp_statistics_show: pcb temp 42~68 chip temp 61~80
2020-10-11 18:46:24 thread.c:259:calc_hashrate_avg: avg rate is 23026.25 in 30 mins
2020-10-11 18:46:24 temperature.c:516:temp_statistics_show: pcb temp 42~68 chip temp 60~79
2020-10-11 19:16:25 thread.c:259:calc_hashrate_avg: avg rate is 22998.17 in 30 mins
2020-10-11 19:16:25 temperature.c:516:temp_statistics_show: pcb temp 42~68 chip temp 59~79
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: Moeter81 on October 11, 2020, 08:29:55 PM
Booting Linux on physical CPU 0x0
Linux version 4.6.0-xilinx-gff8137b-dirty (lzq@armdev2) (gcc version 4.8.3 20140320 (prerelease) (Sourcery CodeBench Lite 2014.05-23) ) #25 SMP PREEMPT Fri Nov 23 15:30:52 CST 2018
CPU: ARMv7 Processor [413fc090] revision 0 (ARMv7), cr=18c5387d
CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
Machine model: Xilinx Zynq
cma: Reserved 16 MiB at 0x0e000000
Memory policy: Data cache writealloc
On node 0 totalpages: 61440
free_area_init_node: node 0, pgdat c0b39280, node_mem_map cde10000
Normal zone: 480 pages used for memmap
Normal zone: 0 pages reserved
Normal zone: 61440 pages, LIFO batch:15
percpu: Embedded 12 pages/cpu @cddf1000 s19776 r8192 d21184 u49152
pcpu-alloc: s19776 r8192 d21184 u49152 alloc=12*4096
pcpu-alloc: [0] 0 [0] 1
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 60960
Kernel command line: mem=240M console=ttyPS0,115200 ramdisk_size=33554432 root=/dev/ram rw earlyprintk
PID hash table entries: 1024 (order: 0, 4096 bytes)
Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
Memory: 203432K/245760K available (6345K kernel code, 231K rwdata, 1896K rodata, 1024K init, 223K bss, 25944K reserved, 16384K cma-reserved, 0K highmem)
Virtual kernel memory layout:
vector : 0xffff0000 - 0xffff1000 ( 4 kB)
fixmap : 0xffc00000 - 0xfff00000 (3072 kB)
vmalloc : 0xcf800000 - 0xff800000 ( 768 MB)
lowmem : 0xc0000000 - 0xcf000000 ( 240 MB)
pkmap : 0xbfe00000 - 0xc0000000 ( 2 MB)
modules : 0xbf000000 - 0xbfe00000 ( 14 MB)
.text : 0xc0008000 - 0xc090c424 (9234 kB)
.init : 0xc0a00000 - 0xc0b00000 (1024 kB)
.data : 0xc0b00000 - 0xc0b39fe0 ( 232 kB)
.bss : 0xc0b39fe0 - 0xc0b71c28 ( 224 kB)
Preemptible hierarchical RCU implementation.
Build-time adjustment of leaf fanout to 32.
RCU restricting CPUs from NR_CPUS=4 to nr_cpu_ids=2.
RCU: Adjusting geometry for rcu_fanout_leaf=32, nr_cpu_ids=2
NR_IRQS:16 nr_irqs:16 16
efuse mapped to cf800000
ps7-slcr mapped to cf802000
L2C: platform modifies aux control register: 0x72360000 -> 0x72760000
L2C: DT/platform modifies aux control register: 0x72360000 -> 0x72760000
L2C-310 erratum 769419 enabled
L2C-310 enabling early BRESP for Cortex-A9
L2C-310 full line of zeros enabled for Cortex-A9
L2C-310 ID prefetch enabled, offset 1 lines
L2C-310 dynamic clock gating enabled, standby mode enabled
L2C-310 cache controller enabled, 8 ways, 512 kB
L2C-310: CACHE_ID 0x410000c8, AUX_CTRL 0x76760001
zynq_clock_init: clkc starts at cf802100
Zynq clock init
sched_clock: 64 bits at 333MHz, resolution 3ns, wraps every 4398046511103ns
clocksource: arm_global_timer: mask: 0xffffffffffffffff max_cycles: 0x4ce07af025, max_idle_ns: 440795209040 ns
Switching to timer-based delay loop, resolution 3ns
clocksource: ttc_clocksource: mask: 0xffff max_cycles: 0xffff, max_idle_ns: 537538477 ns
ps7-ttc #0 at cf80a000, irq=18
Console: colour dummy device 80x30
Calibrating delay loop (skipped), value calculated using timer frequency.. 666.66 BogoMIPS (lpj=3333333)
pid_max: default: 32768 minimum: 301
Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
CPU: Testing write buffer coherency: ok
CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
Setting up static identity map for 0x100000 - 0x100058
CPU1: failed to boot: -1
Brought up 1 CPUs
SMP: Total of 1 processors activated (666.66 BogoMIPS).
CPU: All CPU(s) started in SVC mode.
devtmpfs: initialized
VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4
clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
pinctrl core: initialized pinctrl subsystem
NET: Registered protocol family 16
DMA: preallocated 256 KiB pool for atomic coherent allocations
cpuidle: using governor menu
hw-breakpoint: found 5 (+1 reserved) breakpoint and 1 watchpoint registers.
hw-breakpoint: maximum watchpoint size is 4 bytes.
zynq-ocm f800c000.ps7-ocmc: ZYNQ OCM pool: 256 KiB @ 0xcf880000
vgaarb: loaded
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
media: Linux media interface: v0.10
Linux video capture interface: v2.00
pps_core: LinuxPPS API ver. 1 registered
pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
PTP clock support registered
EDAC MC: Ver: 3.0.0
Advanced Linux Sound Architecture Driver Initialized.
clocksource: Switched to clocksource arm_global_timer
NET: Registered protocol family 2
TCP established hash table entries: 2048 (order: 1, 8192 bytes)
TCP bind hash table entries: 2048 (order: 2, 16384 bytes)
TCP: Hash tables configured (established 2048 bind 2048)
UDP hash table entries: 256 (order: 1, 8192 bytes)
UDP-Lite hash table entries: 256 (order: 1, 8192 bytes)
NET: Registered protocol family 1
RPC: Registered named UNIX socket transport module.
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
PCI: CLS 0 bytes, default 64
Trying to unpack rootfs image as initramfs...
rootfs image is not initramfs (no cpio magic); looks like an initrd
Freeing initrd memory: 12904K (cce67000 - cdb01000)
hw perfevents: enabled with armv7_cortex_a9 PMU driver, 7 counters available
futex hash table entries: 512 (order: 3, 32768 bytes)
workingset: timestamp_bits=28 max_order=16 bucket_order=0
jffs2: version 2.2. (NAND) (SUMMARY) © 2001-2006 Red Hat, Inc.
io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered (default)
dma-pl330 f8003000.ps7-dma: Loaded driver for PL330 DMAC-241330
dma-pl330 f8003000.ps7-dma: DBUFF-128x8bytes Num_Chans-8 Num_Peri-4 Num_Events-16
e0000000.serial: ttyPS0 at MMIO 0xe0000000 (irq = 158, base_baud = 6249999) is a xuartps
console [ttyPS0] enabled
xdevcfg f8007000.ps7-dev-cfg: ioremap 0xf8007000 to cf86e000
[drm] Initialized drm 1.1.0 20060810
brd: module loaded
loop: module loaded
CAN device driver interface
gpiod_set_value: invalid GPIO
libphy: MACB_mii_bus: probed
macb e000b000.ethernet eth0: Cadence GEM rev 0x00020118 at 0xe000b000 irq 31 (00:0a:35:00:00:00)
Generic PHY e000b000.etherne:00: attached PHY driver [Generic PHY] (mii_bus:phy_addr=e000b000.etherne:00, irq=-1)
e1000e: Intel(R) PRO/1000 Network Driver - 3.2.6-k
e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
ehci-pci: EHCI PCI platform driver
usbcore: registered new interface driver usb-storage
mousedev: PS/2 mouse device common for all mice
i2c /dev entries driver
Xilinx Zynq CpuIdle Driver started
sdhci: Secure Digital Host Controller Interface driver
sdhci: Copyright(c) Pierre Ossman
sdhci-pltfm: SDHCI platform and OF driver helper
mmc0: SDHCI controller on e0100000.ps7-sdio [e0100000.ps7-sdio] using ADMA
ledtrig-cpu: registered to indicate activity on CPUs
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
nand: device found, Manufacturer ID: 0x2c, Chip ID: 0xda
nand: Micron MT29F2G08ABAGAWP
nand: 256 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 128
nand: WARNING: pl35x-nand: the ECC used on your system is too weak compared to the one required by the NAND chip
Bad block table found at page 131008, version 0x01
Bad block table found at page 130944, version 0x01
6 ofpart partitions found on MTD device pl35x-nand
Creating 6 MTD partitions on "pl35x-nand":
0x000000000000-0x000002800000 : "BOOT.bin-env-dts-kernel"
0x000002800000-0x000004800000 : "ramfs"
0x000004800000-0x000005000000 : "configs"
0x000005000000-0x000006000000 : "reserve"
0x000006000000-0x000008000000 : "ramfs-bak"
0x000008000000-0x000010000000 : "reserve1"
NET: Registered protocol family 10
sit: IPv6 over IPv4 tunneling driver
NET: Registered protocol family 17
can: controller area network core (rev 20120528 abi 9)
NET: Registered protocol family 29
can: raw protocol (rev 20120528)
can: broadcast manager protocol (rev 20120528 t)
can: netlink gateway (rev 20130117) max_hops=1
zynq_pm_ioremap: no compatible node found for 'xlnx,zynq-ddrc-a05'
zynq_pm_late_init: Unable to map DDRC IO memory.
Registering SWP/SWPB emulation handler
hctosys: unable to open rtc device (rtc0)
ALSA device list:
No soundcards found.
RAMDISK: gzip image found at block 0
EXT4-fs (ram0): couldn't mount as ext3 due to feature incompatibilities
EXT4-fs (ram0): mounted filesystem without journal. Opts: (null)
VFS: Mounted root (ext4 filesystem) on device 1:0.
devtmpfs: mounted
Freeing unused kernel memory: 1024K (c0a00000 - c0b00000)
EXT4-fs (ram0): re-mounted. Opts: block_validity,delalloc,barrier,user_xattr
random: dd urandom read with 0 bits of entropy available
ubi0: attaching mtd2
ubi0: scanning is finished
ubi0: attached mtd2 (name "configs", size 8 MiB)
ubi0: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
ubi0: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
ubi0: VID header offset: 2048 (aligned 2048), data offset: 4096
ubi0: good PEBs: 64, bad PEBs: 0, corrupted PEBs: 0
ubi0: user volume: 1, internal volumes: 1, max. volumes count: 128
ubi0: max/mean erase counter: 20/9, WL threshold: 4096, image sequence number: 237714726
ubi0: available PEBs: 0, total reserved PEBs: 64, PEBs reserved for bad PEB handling: 40
ubi0: background thread "ubi_bgt0d" started, PID 708
UBIFS (ubi0:0): background thread "ubifs_bgt0_0" started, PID 711
UBIFS (ubi0:0): UBIFS: mounted UBI device 0, volume 0, name "configs"
UBIFS (ubi0:0): LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
UBIFS (ubi0:0): FS size: 1396736 bytes (1 MiB, 11 LEBs), journal size 888833 bytes (0 MiB, 5 LEBs)
UBIFS (ubi0:0): reserved for root: 65970 bytes (64 KiB)
UBIFS (ubi0:0): media format: w4/r0 (latest is w4/r0), UUID FF09433B-E002-4C29-97EC-6220DDC4BB36, 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: 3361/788, WL threshold: 4096, image sequence number: 3265111179
ubi1: available PEBs: 0, total reserved PEBs: 1020, PEBs reserved for bad PEB handling: 36
ubi1: background thread "ubi_bgt1d" started, PID 720
UBIFS (ubi1:0): background thread "ubifs_bgt1_0" started, PID 723
UBIFS (ubi1:0): UBIFS: mounted UBI device 1, volume 0, name "reserve1"
UBIFS (ubi1:0): LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
UBIFS (ubi1:0): FS size: 123039744 bytes (117 MiB, 969 LEBs), journal size 6221824 bytes (5 MiB, 49 LEBs)
UBIFS (ubi1:0): reserved for root: 4952683 bytes (4836 KiB)
UBIFS (ubi1:0): media format: w4/r0 (latest is w4/r0), UUID 1AF6F1E1-61F0-462C-AE44-C7D9596CF7E2, 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 = 0xb023
In fpga mem driver!
request_mem_region OK!
fpga mem virtual address is 0xd2000000
random: nonblocking pool is initialized
2020-10-10 17:01:16 driver-btm-api.c:779:init_freq_mode: This is scan-user version
2020-10-10 17:01:16 driver-btm-api.c:2451:bitmain_soc_init: opt_multi_version = 1
2020-10-10 17:01:16 driver-btm-api.c:2452:bitmain_soc_init: opt_bitmain_ab = 1
2020-10-10 17:01:16 driver-btm-api.c:2453:bitmain_soc_init: opt_bitmain_work_mode = 0
2020-10-10 17:01:16 driver-btm-api.c:2454:bitmain_soc_init: Miner compile time: Tue Jun 2 10:31:07 CST 2020 type: Antminer S17+
2020-10-10 17:01:16 driver-btm-api.c:2455:bitmain_soc_init: commit version: 1ca50a5 2020-06-01 18:51:22, build by: lol 2020-06-02 10:37:21
2020-10-10 17:01:16 driver-btm-api.c:2083:show_sn: len:16, 8048ed0c2b104814
2020-10-10 17:01:16 driver-btm-api.c:2461:bitmain_soc_init: show sn return 1
2020-10-10 17:01:16 driver-btm-api.c:2103:handle_sn_for_factory_mode: show sn return 1
2020-10-10 17:01:16 driver-btm-api.c:2141:handle_sn_for_factory_mode: read sn success, 8048ed0c2b104814
2020-10-10 17:01:16 fan.c:284:front_fan_power_on: Note: front fan is power on!
2020-10-10 17:01:16 fan.c:296:rear_fan_power_on: Note: rear fan is power on!
2020-10-10 17:01:16 driver-btm-api.c:1314:miner_device_init: Detect 256MB control board of XILINX
2020-10-10 17:01:16 driver-btm-api.c:1255:init_fan_parameter: fan_eft : 0 fan_pwm : 0
2020-10-10 17:01:22 driver-btm-api.c:1239:init_miner_version: miner ID : 8048ed0c2b104814
2020-10-10 17:01:22 driver-btm-api.c:1245:init_miner_version: FPGA Version = 0xB023
2020-10-10 17:01:24 chain = 0, mode = 0, load_done = false.
2020-10-10 17:01:24 chain = 1, mode = 0, load_done = false.
2020-10-10 17:01:24 chain = 2, mode = 0, load_done = false.
2020-10-10 17:01:24 chain = 0, load_done = false
2020-10-10 17:01:24 chain = 1, load_done = false
2020-10-10 17:01:24 chain = 2, load_done = false
2020-10-10 17:01:26 chain = 0, mode = 0, load_done = false.
2020-10-10 17:01:26 chain = 1, mode = 0, load_done = false.
2020-10-10 17:01:26 chain = 2, mode = 0, load_done = false.
2020-10-10 17:01:26 chain = 0, load_done = false
2020-10-10 17:01:26 chain = 1, load_done = false
2020-10-10 17:01:26 chain = 2, load_done = false
2020-10-10 17:01:27 driver-btm-api.c:837:get_product_id: product_id[0] = 0
2020-10-10 17:01:27 driver-btm-api.c:837:get_product_id: product_id[1] = 0
2020-10-10 17:01:27 driver-btm-api.c:837:get_product_id: product_id[2] = 0
2020-10-10 17:01:27 driver-btm-api.c:2234:update_conf_by_power_feedback: Power feedback is disabled
2020-10-10 17:01:27 driver-btm-api.c:2202:get_calibration_voltage: calibration voltage flag is error data.
2020-10-10 17:01:27 driver-btm-api.c:2268:update_conf_by_power_feedback: Note: no calibration voltage, default diff = 0
2020-10-10 17:01:27 frequency.c:1457:adjust_higer_max_vol_table: adjust_higer_max_vol_table, adjust_vol = 0
2020-10-10 17:01:27 thread.c:1363:create_read_nonce_reg_thread: create thread
2020-10-10 17:01:28 frequency.c:205:get_ideal_hash_rate_GH: ideal_hash_rate = 67628
2020-10-10 17:01:33 driver-btm-api.c:1239:init_miner_version: miner ID : 8048ed0c2b104814
2020-10-10 17:01:33 driver-btm-api.c:1245:init_miner_version: FPGA Version = 0xB023
2020-10-10 17:01:33 chain = 0, load_done = false
2020-10-10 17:01:33 chain = 1, load_done = false
2020-10-10 17:01:33 chain = 2, load_done = false
2020-10-10 17:01:36 chain = 0, load_done = false
2020-10-10 17:01:36 chain = 1, load_done = false
2020-10-10 17:01:36 chain = 2, load_done = false
2020-10-10 17:01:39 driver-btm-api.c:837:get_product_id: product_id[0] = 0
2020-10-10 17:01:39 driver-btm-api.c:837:get_product_id: product_id[1] = 0
2020-10-10 17:01:39 driver-btm-api.c:837:get_product_id: product_id[2] = 0
2020-10-10 17:01:39 driver-btm-api.c:792:_set_project_type: project:0
2020-10-10 17:01:39 driver-btm-api.c:813:_set_project_type: Project type: Antminer S17+
2020-10-10 17:01:39 driver-btm-api.c:824:dump_pcb_bom_version: Chain [0] PCB Version: 0x0100
2020-10-10 17:01:39 driver-btm-api.c:825:dump_pcb_bom_version: Chain [0] BOM Version: 0x0100
2020-10-10 17:01:39 driver-btm-api.c:824:dump_pcb_bom_version: Chain [1] PCB Version: 0x0100
2020-10-10 17:01:39 driver-btm-api.c:825:dump_pcb_bom_version: Chain [1] BOM Version: 0x0100
2020-10-10 17:01:39 driver-btm-api.c:824:dump_pcb_bom_version: Chain [2] PCB Version: 0x0100
2020-10-10 17:01:39 driver-btm-api.c:825:dump_pcb_bom_version: Chain [2] BOM Version: 0x0100
2020-10-10 17:01:41 driver-btm-api.c:2372:bitmain_board_init: Fan check passed.
2020-10-10 17:01:42 board.c:36:jump_and_app_check_restore_pic: chain[0] PIC jump to app
2020-10-10 17:01:44 board.c:40:jump_and_app_check_restore_pic: Check chain[0] PIC fw version=0x88
2020-10-10 17:01:45 board.c:36:jump_and_app_check_restore_pic: chain[1] PIC jump to app
2020-10-10 17:01:47 board.c:40:jump_and_app_check_restore_pic: Check chain[1] PIC fw version=0x88
2020-10-10 17:01:48 board.c:36:jump_and_app_check_restore_pic: chain[2] PIC jump to app
2020-10-10 17:01:50 board.c:40:jump_and_app_check_restore_pic: Check chain[2] PIC fw version=0x88
2020-10-10 17:01:50 thread.c:1358:create_pic_heart_beat_thread: create thread
2020-10-10 17:01:50 power_api.c:213:power_init: Power init:
2020-10-10 17:01:50 power_api.c:214:power_init: current_voltage_raw = 0
2020-10-10 17:01:50 power_api.c:215:power_init: highest_voltage_raw = 2100
2020-10-10 17:01:50 power_api.c:216:power_init: working_voltage_raw = 1950
2020-10-10 17:01:50 power_api.c:217:power_init: higher_voltage_raw = 2040
2020-10-10 17:01:50 power_api.c:218:power_init: check_asic_voltage_raw = 2100
2020-10-10 17:01:50 driver-btm-api.c:2382:bitmain_board_init: Enter 30s sleep to make sure power release finish.
2020-10-10 17:02:22 power_api.c:324:set_to_highest_voltage_by_steps: Set to voltage raw 2100, step by step.
2020-10-10 17:02:48 power_api.c:85:check_voltage_multi: retry time: 0
2020-10-10 17:02:49 power_api.c:40:_get_avg_voltage: chain = 0, voltage = 21.108418
2020-10-10 17:02:50 power_api.c:40:_get_avg_voltage: chain = 1, voltage = 21.006361
2020-10-10 17:02:51 power_api.c:40:_get_avg_voltage: chain = 2, voltage = 21.132653
2020-10-10 17:02:51 power_api.c:53:_get_avg_voltage: average_voltage = 21.082477
2020-10-10 17:02:51 power_api.c:71:check_voltage: target_vol = 21.00, actural_vol = 21.08, check voltage passed.
2020-10-10 17:02:51 uart.c:72:set_baud: set fpga_baud to 115200
2020-10-10 17:03:02 driver-btm-api.c:1134:check_asic_number_with_power_on: Chain[0]: find 0 asic, times 0
2020-10-10 17:03:13 driver-btm-api.c:1134:check_asic_number_with_power_on: Chain[0]: find 0 asic, times 1
2020-10-10 17:03:24 driver-btm-api.c:1134:check_asic_number_with_power_on: Chain[0]: find 0 asic, times 2
2020-10-10 17:03:24 power_api.c:380:modify_check_asic_voltage: check_asic_voltage_raw = 2100
chain 0, IO_DRIVE_STRENGTH_CONFIGURATION reg = 0x f1fffff
2020-10-10 17:03:32 driver-btm-api.c:1157:check_asic_number_with_power_on: Chain[0]: find 0 asic, times 3
2020-10-10 17:03:32 power_api.c:380:modify_check_asic_voltage: check_asic_voltage_raw = 2050
2020-10-10 17:03:32 power_api.c:364:set_to_check_asic_voltage_by_steps: Set to voltage raw 2050, step by step.
2020-10-10 17:03:36 power_api.c:85:check_voltage_multi: retry time: 0
2020-10-10 17:03:38 power_api.c:40:_get_avg_voltage: chain = 0, voltage = 20.573249
2020-10-10 17:03:39 power_api.c:40:_get_avg_voltage: chain = 1, voltage = 20.524841
2020-10-10 17:03:40 power_api.c:40:_get_avg_voltage: chain = 2, voltage = 20.623724
2020-10-10 17:03:40 power_api.c:53:_get_avg_voltage: average_voltage = 20.573938
2020-10-10 17:03:40 power_api.c:71:check_voltage: target_vol = 20.50, actural_vol = 20.57, check voltage passed.
chain 0, IO_DRIVE_STRENGTH_CONFIGURATION reg = 0x f1fffff
2020-10-10 17:03:49 driver-btm-api.c:1157:check_asic_number_with_power_on: Chain[0]: find 0 asic, times 4
2020-10-10 17:03:49 power_api.c:380:modify_check_asic_voltage: check_asic_voltage_raw = 2000
2020-10-10 17:03:49 power_api.c:364:set_to_check_asic_voltage_by_steps: Set to voltage raw 2000, step by step.
2020-10-10 17:03:52 power_api.c:85:check_voltage_multi: retry time: 0
2020-10-10 17:03:53 power_api.c:40:_get_avg_voltage: chain = 0, voltage = 20.063613
2020-10-10 17:03:54 power_api.c:40:_get_avg_voltage: chain = 1, voltage = 20.015267
2020-10-10 17:03:55 power_api.c:40:_get_avg_voltage: chain = 2, voltage = 20.114796
2020-10-10 17:03:55 power_api.c:53:_get_avg_voltage: average_voltage = 20.064558
2020-10-10 17:03:55 power_api.c:71:check_voltage: target_vol = 20.00, actural_vol = 20.06, check voltage passed.
chain 0, IO_DRIVE_STRENGTH_CONFIGURATION reg = 0x f1fffff
2020-10-10 17:04:04 driver-btm-api.c:1157:check_asic_number_with_power_on: Chain[0]: find 0 asic, times 5
2020-10-10 17:04:04 power_api.c:380:modify_check_asic_voltage: check_asic_voltage_raw = 2100
2020-10-10 17:04:04 power_api.c:364:set_to_check_asic_voltage_by_steps: Set to voltage raw 2100, step by step.
2020-10-10 17:04:09 power_api.c:85:check_voltage_multi: retry time: 0
2020-10-10 17:04:10 power_api.c:40:_get_avg_voltage: chain = 0, voltage = 21.054707
2020-10-10 17:04:11 power_api.c:40:_get_avg_voltage: chain = 1, voltage = 21.008918
2020-10-10 17:04:12 power_api.c:40:_get_avg_voltage: chain = 2, voltage = 21.108418
2020-10-10 17:04:12 power_api.c:53:_get_avg_voltage: average_voltage = 21.057348
2020-10-10 17:04:12 power_api.c:71:check_voltage: target_vol = 21.00, actural_vol = 21.06, check voltage passed.
2020-10-10 17:04:12 driver-btm-api.c:1193:check_asic_number: Chain 0 only find 0 asic, will power off hash board 0
2020-10-10 17:04:13 driver-btm-api.c:1195:check_asic_number: Chain 0 voltage: an0 = 2.816129, an2 2.809677, an6 2.535484.
2020-10-10 17:04:17 frequency.c:205:get_ideal_hash_rate_GH: ideal_hash_rate = 44631
2020-10-10 17:04:25 driver-btm-api.c:1134:check_asic_number_with_power_on: Chain[1]: find 65 asic, times 0
2020-10-10 17:04:36 driver-btm-api.c:1134:check_asic_number_with_power_on: Chain[2]: find 0 asic, times 0
2020-10-10 17:04:47 driver-btm-api.c:1134:check_asic_number_with_power_on: Chain[2]: find 0 asic, times 1
2020-10-10 17:04:57 driver-btm-api.c:1134:check_asic_number_with_power_on: Chain[2]: find 0 asic, times 2
2020-10-10 17:04:57 power_api.c:380:modify_check_asic_voltage: check_asic_voltage_raw = 2100
chain 2, IO_DRIVE_STRENGTH_CONFIGURATION reg = 0x f1fffff
2020-10-10 17:05:06 driver-btm-api.c:1157:check_asic_number_with_power_on: Chain[2]: find 0 asic, times 3
2020-10-10 17:05:06 power_api.c:380:modify_check_asic_voltage: check_asic_voltage_raw = 2050
2020-10-10 17:05:06 power_api.c:364:set_to_check_asic_voltage_by_steps: Set to voltage raw 2050, step by step.
2020-10-10 17:05:09 power_api.c:85:check_voltage_multi: retry time: 0
2020-10-10 17:05:10 power_api.c:40:_get_avg_voltage: chain = 1, voltage = 20.472681
2020-10-10 17:05:12 power_api.c:40:_get_avg_voltage: chain = 2, voltage = 20.547073
2020-10-10 17:05:12 power_api.c:53:_get_avg_voltage: average_voltage = 20.509877
2020-10-10 17:05:12 power_api.c:71:check_voltage: target_vol = 20.50, actural_vol = 20.51, check voltage passed.
chain 2, IO_DRIVE_STRENGTH_CONFIGURATION reg = 0x f1fffff
2020-10-10 17:05:20 driver-btm-api.c:1157:check_asic_number_with_power_on: Chain[2]: find 0 asic, times 4
2020-10-10 17:05:20 power_api.c:380:modify_check_asic_voltage: check_asic_voltage_raw = 2000
2020-10-10 17:05:20 power_api.c:364:set_to_check_asic_voltage_by_steps: Set to voltage raw 2000, step by step.
2020-10-10 17:05:24 power_api.c:85:check_voltage_multi: retry time: 0
2020-10-10 17:05:25 power_api.c:40:_get_avg_voltage: chain = 1, voltage = 20.015267
2020-10-10 17:05:26 power_api.c:40:_get_avg_voltage: chain = 2, voltage = 20.063613
2020-10-10 17:05:26 power_api.c:53:_get_avg_voltage: average_voltage = 20.039440
2020-10-10 17:05:26 power_api.c:71:check_voltage: target_vol = 20.00, actural_vol = 20.04, check voltage passed.
chain 2, IO_DRIVE_STRENGTH_CONFIGURATION reg = 0x f1fffff
2020-10-10 17:05:34 driver-btm-api.c:1157:check_asic_number_with_power_on: Chain[2]: find 0 asic, times 5
2020-10-10 17:05:34 power_api.c:380:modify_check_asic_voltage: check_asic_voltage_raw = 2100
2020-10-10 17:05:34 power_api.c:364:set_to_check_asic_voltage_by_steps: Set to voltage raw 2100, step by step.
2020-10-10 17:05:40 power_api.c:85:check_voltage_multi: retry time: 0
2020-10-10 17:05:41 power_api.c:40:_get_avg_voltage: chain = 1, voltage = 20.955528
2020-10-10 17:05:42 power_api.c:40:_get_avg_voltage: chain = 2, voltage = 21.081529
2020-10-10 17:05:42 power_api.c:53:_get_avg_voltage: average_voltage = 21.018529
2020-10-10 17:05:42 power_api.c:71:check_voltage: target_vol = 21.00, actural_vol = 21.02, check voltage passed.
2020-10-10 17:05:42 driver-btm-api.c:1193:check_asic_number: Chain 2 only find 0 asic, will power off hash board 2
2020-10-10 17:05:43 driver-btm-api.c:1195:check_asic_number: Chain 2 voltage: an0 = 2.816129, an2 2.806452, an6 2.532258.
2020-10-10 17:05:45 frequency.c:205:get_ideal_hash_rate_GH: ideal_hash_rate = 22571
2020-10-10 17:05:47 driver-hash-chip.c:266:set_uart_relay: set uart relay to 0x330003
2020-10-10 17:05:47 driver-btm-api.c:435:set_order_clock: chain[1]: set order clock, stragegy 3
2020-10-10 17:05:47 driver-hash-chip.c:502:set_clock_delay_control: core_data = 0x34
2020-10-10 17:05:47 driver-btm-api.c:1892:check_clock_counter: freq 50 clock_counter_limit 6
2020-10-10 17:05:47 voltage[1] = 1980
2020-10-10 17:05:47 power_api.c:226:set_working_voltage_raw: working_voltage_raw = 1980
2020-10-10 17:05:48 temperature.c:340:calibrate_temp_sensor_one_chain: chain 1 temp sensor NCT218
2020-10-10 17:05:48 uart.c:72:set_baud: set fpga_baud to 12000000
2020-10-10 17:05:49 driver-btm-api.c:293:check_bringup_temp: Bring up temperature is 21
2020-10-10 17:05:49 thread.c:1378:create_check_miner_status_thread: create thread
2020-10-10 17:05:49 thread.c:1368:create_show_miner_status_thread: create thread
2020-10-10 17:05:49 thread.c:1348:create_temperature_monitor_thread: create thread
2020-10-10 17:05:49 frequency.c:514:check_bringup_temp_dec_freq: dec freq = 0 when bringup temp = 21 dec_freq_index=0
2020-10-10 17:05:49 freq_tuning.c:183:freq_tuning_get_max_freq: Max freq of tuning is 650
2020-10-10 17:05:49 driver-btm-api.c:1765:send_null_work: [DEBUG] Send null work.
2020-10-10 17:05:49 thread.c:1338:create_asic_status_monitor_thread: create thread
2020-10-10 17:05:49 frequency.c:1110:inc_freq_with_fixed_vco: chain = 255, freq = 530, is_higher_voltage = true
2020-10-10 17:05:51 frequency.c:205:get_ideal_hash_rate_GH: ideal_hash_rate = 22571
2020-10-10 17:08:14 power_api.c:352:set_to_voltage_by_steps: Set to voltage raw 2090, step by step.
2020-10-10 17:08:16 power_api.c:85:check_voltage_multi: retry time: 0
2020-10-10 17:08:17 power_api.c:40:_get_avg_voltage: chain = 1, voltage = 20.810674
2020-10-10 17:08:17 power_api.c:53:_get_avg_voltage: average_voltage = 20.810674
2020-10-10 17:08:17 power_api.c:71:check_voltage: target_vol = 20.90, actural_vol = 20.81, check voltage passed.
2020-10-10 17:10:58 driver-btm-api.c:765:set_timeout: freq = 530, percent = 90, hcn = 44236, timeout = 83
2020-10-10 17:10:58 power_api.c:310:set_to_working_voltage_by_steps: Set to voltage raw 1980, step by step.
2020-10-10 17:11:03 power_api.c:85:check_voltage_multi: retry time: 0
2020-10-10 17:11:05 power_api.c:40:_get_avg_voltage: chain = 1, voltage = 19.797709
2020-10-10 17:11:05 power_api.c:53:_get_avg_voltage: average_voltage = 19.797709
2020-10-10 17:11:05 power_api.c:71:check_voltage: target_vol = 19.80, actural_vol = 19.80, check voltage passed.
2020-10-10 17:11:05 thread.c:1373:create_check_system_status_thread: create thread
2020-10-10 17:11:05 driver-btm-api.c:2618:bitmain_soc_init: Init done!
2020-10-10 17:11:05 driver-btm-api.c:222:set_miner_status: STATUS_INIT
2020-10-10 17:11:10 driver-btm-api.c:222:set_miner_status: STATUS_OKAY
2020-10-10 17:11:11 frequency.c:223:get_sale_hash_rate_GH: sale_hash_rate = 22000
2020-10-10 17:11:15 driver-btm-api.c:1496:dhash_chip_send_job: Version num 4.
2020-10-10 17:11:15 driver-btm-api.c:1644:dhash_chip_send_job: stime.tv_sec 1602349875, block_ntime 1602349869
2020-10-10 17:17:02 temperature.c:843:get_temp_info: read temp sensor failed: chain = 1, sensor = 3, chip = 50, reg = 0
2020-10-10 17:17:03 temperature.c:843:get_temp_info: read temp sensor failed: chain = 1, sensor = 3, chip = 50, reg = 1
2020-10-10 17:17:03 thread.c:1265:asic_status_monitor_thread: ERROR: chain 1 get hashrate_reg_counter 0, require 65, failed times 1
2020-10-10 17:17:04 temperature.c:843:get_temp_info: read temp sensor failed: chain = 1, sensor = 2, chip = 54, reg = 0
2020-10-10 17:17:04 thread.c:1293:asic_status_monitor_thread: chain 1 can't get enough hashrate reg val for 0 times.
2020-10-10 17:17:05 temperature.c:843:get_temp_info: read temp sensor failed: chain = 1, sensor = 2, chip = 54, reg = 1
2020-10-10 17:17:05 thread.c:1273:asic_status_monitor_thread: ERROR: chain 1 get hashrate_reg_counter 48, require 65, failed times 1: ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo oooxx xxxxx xxxxx xxxxx
2020-10-10 17:17:05 temperature.c:843:get_temp_info: read temp sensor failed: chain = 1, sensor = 3, chip = 50, reg = 0
2020-10-10 17:17:05 temperature.c:843:get_temp_info: read temp sensor failed: chain = 1, sensor = 3, chip = 50, reg = 1
2020-10-10 17:17:06 thread.c:1293:asic_status_monitor_thread: chain 1 can't get enough hashrate reg val for 1 times.
2020-10-10 17:17:07 thread.c:1273:asic_status_monitor_thread: ERROR: chain 1 get hashrate_reg_counter 48, require 65, failed times 1: ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo oooxx xxxxx xxxxx xxxxx
2020-10-10 17:17:07 temperature.c:843:get_temp_info: read temp sensor failed: chain = 1, sensor = 2, chip = 54, reg = 0
2020-10-10 17:17:07 temperature.c:843:get_temp_info: read temp sensor failed: chain = 1, sensor = 2, chip = 54, reg = 1
2020-10-10 17:17:08 temperature.c:843:get_temp_info: read temp sensor failed: chain = 1, sensor = 3, chip = 50, reg = 0
2020-10-10 17:17:08 temperature.c:843:get_temp_info: read temp sensor failed: chain = 1, sensor = 3, chip = 50, reg = 1
2020-10-10 17:17:08 thread.c:1293:asic_status_monitor_thread: chain 1 can't get enough hashrate reg val for 2 times.
2020-10-10 17:17:09 thread.c:1273:asic_status_monitor_thread: ERROR: chain 1 get hashrate_reg_counter 48, require 65, failed times 1: ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo oooxx xxxxx xxxxx xxxxx
2020-10-10 17:17:09 temperature.c:843:get_temp_info: read temp sensor failed: chain = 1, sensor = 2, chip = 54, reg = 0
2020-10-10 17:17:10 temperature.c:843:get_temp_info: read temp sensor failed: chain = 1, sensor = 2, chip = 54, reg = 1
2020-10-10 17:17:10 temperature.c:843:get_temp_info: read temp sensor failed: chain = 1, sensor = 3, chip = 50, reg = 0
2020-10-10 17:17:10 thread.c:1293:asic_status_monitor_thread: chain 1 can't get enough hashrate reg val for 3 times.
2020-10-10 17:17:11 temperature.c:843:get_temp_info: read temp sensor failed: chain = 1, sensor = 3, chip = 50, reg = 1
2020-10-10 17:17:11 thread.c:1273:asic_status_monitor_thread: ERROR: chain 1 get hashrate_reg_counter 48, require 65, failed times 1: ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo oooxx xxxxx xxxxx xxxxx
2020-10-10 17:17:12 temperature.c:843:get_temp_info: read temp sensor failed: chain = 1, sensor = 2, chip = 54, reg = 0
2020-10-10 17:17:12 thread.c:1293:asic_status_monitor_thread: chain 1 can't get enough hashrate reg val for 4 times.
2020-10-10 17:17:13 temperature.c:843:get_temp_info: read temp sensor failed: chain = 1, sensor = 2, chip = 54, reg = 1
2020-10-10 17:17:13 thread.c:1273:asic_status_monitor_thread: ERROR: chain 1 get hashrate_reg_counter 48, require 65, failed times 1: ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo oooxx xxxxx xxxxx xxxxx
2020-10-10 17:17:13 temperature.c:843:get_temp_info: read temp sensor failed: chain = 1, sensor = 3, chip = 50, reg = 0
2020-10-10 17:17:13 temperature.c:843:get_temp_info: read temp sensor failed: chain = 1, sensor = 3, chip = 50, reg = 1
2020-10-10 17:17:14 thread.c:1293:asic_status_monitor_thread: chain 1 can't get enough hashrate reg val for 5 times.
2020-10-10 17:17:15 thread.c:1273:asic_status_monitor_thread: ERROR: chain 1 get hashrate_reg_counter 48, require 65, failed times 1: ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo oooxx xxxxx xxxxx xxxxx
2020-10-10 17:17:15 temperature.c:843:get_temp_info: read temp sensor failed: chain = 1, sensor = 2, chip = 54, reg = 0
2020-10-10 17:17:15 temperature.c:843:get_temp_info: read temp sensor failed: chain = 1, sensor = 2, chip = 54, reg = 1
2020-10-10 17:17:15 temperature.c:843:get_temp_info: read temp sensor failed: chain = 1, sensor = 3, chip = 50, reg = 0
2020-10-10 17:17:16 temperature.c:843:get_temp_info: read temp sensor failed: chain = 1, sensor = 3, chip = 50, reg = 1
2020-10-10 17:17:16 thread.c:1293:asic_status_monitor_thread: chain 1 can't get enough hashrate reg val for 6 times.
2020-10-10 17:17:17 thread.c:1273:asic_status_monitor_thread: ERROR: chain 1 get hashrate_reg_counter 48, require 65, failed times 1: ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo oooxx xxxxx xxxxx xxxxx
2020-10-10 17:17:17 temperature.c:843:get_temp_info: read temp sensor failed: chain = 1, sensor = 2, chip = 54, reg = 0
2020-10-10 17:17:18 temperature.c:843:get_temp_info: read temp sensor failed: chain = 1, sensor = 2, chip = 54, reg = 1
2020-10-10 17:17:18 temperature.c:843:get_temp_info: read temp sensor failed: chain = 1, sensor = 3, chip = 50, reg = 0
2020-10-10 17:17:18 thread.c:1293:asic_status_monitor_thread: chain 1 can't get enough hashrate reg val for 7 times.
2020-10-10 17:17:18 temperature.c:843:get_temp_info: read temp sensor failed: chain = 1, sensor = 3, chip = 50, reg = 1
2020-10-10 17:17:19 thread.c:1273:asic_status_monitor_thread: ERROR: chain 1 get hashrate_reg_counter 48, require 65, failed times 1: ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo oooxx xxxxx xxxxx xxxxx
2020-10-10 17:17:20 temperature.c:843:get_temp_info: read temp sensor failed: chain = 1, sensor = 2, chip = 54, reg = 0
2020-10-10 17:17:20 thread.c:1293:asic_status_monitor_thread: chain 1 can't get enough hashrate reg val for 8 times.
2020-10-10 17:17:20 temperature.c:843:get_temp_info: read temp sensor failed: chain = 1, sensor = 2, chip = 54, reg = 1
2020-10-10 17:17:21 thread.c:1273:asic_status_monitor_thread: ERROR: chain 1 get hashrate_reg_counter 48, require 65, failed times 1: ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo oooxx xxxxx xxxxx xxxxx
2020-10-10 17:17:21 temperature.c:843:get_temp_info: read temp sensor failed: chain = 1, sensor = 3, chip = 50, reg = 0
2020-10-10 17:17:21 temperature.c:843:get_temp_info: read temp sensor failed: chain = 1, sensor = 3, chip = 50, reg = 1
2020-10-10 17:17:22 thread.c:1293:asic_status_monitor_thread: chain 1 can't get enough hashrate reg val for 9 times.
2020-10-10 17:17:23 thread.c:1273:asic_status_monitor_thread: ERROR: chain 1 get hashrate_reg_counter 48, require 65, failed times 1: ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo oooxx xxxxx xxxxx xxxxx
2020-10-10 17:17:23 temperature.c:843:get_temp_info: read temp sensor failed: chain = 1, sensor = 2, chip = 54, reg = 0
2020-10-10 17:17:23 temperature.c:843:get_temp_info: read temp sensor failed: chain = 1, sensor = 2, chip = 54, reg = 1
2020-10-10 17:17:23 temperature.c:843:get_temp_info: read temp sensor failed: chain = 1, sensor = 3, chip = 50, reg = 0
2020-10-10 17:17:24 temperature.c:843:get_temp_info: read temp sensor failed: chain = 1, sensor = 3, chip = 50, reg = 1
2020-10-10 17:17:24 thread.c:1293:asic_status_monitor_thread: chain 1 can't get enough hashrate reg val for 10 times.
2020-10-10 17:17:25 thread.c:1273:asic_status_monitor_thread: ERROR: chain 1 get hashrate_reg_counter 48, require 65, failed times 1: ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo oooxx xxxxx xxxxx xxxxx
2020-10-10 17:17:25 temperature.c:843:get_temp_info: read temp sensor failed: chain = 1, sensor = 2, chip = 54, reg = 0
2020-10-10 17:17:26 temperature.c:843:get_temp_info: read temp sensor failed: chain = 1, sensor = 2, chip = 54, reg = 1
2020-10-10 17:17:26 temperature.c:843:get_temp_info: read temp sensor failed: chain = 1, sensor = 3, chip = 50, reg = 0
2020-10-10 17:17:26 thread.c:1293:asic_status_monitor_thread: chain 1 can't get enough hashrate reg val for 11 times.
2020-10-10 17:17:26 temperature.c:843:get_temp_info: read temp sensor failed: chain = 1, sensor = 3, chip = 50, reg = 1
2020-10-10 17:17:27 thread.c:1273:asic_status_monitor_thread: ERROR: chain 1 get hashrate_reg_counter 48, require 65, failed times 1: ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo oooxx xxxxx xxxxx xxxxx
2020-10-10 17:17:28 temperature.c:843:get_temp_info: read temp sensor failed: chain = 1, sensor = 2, chip = 54, reg = 0
2020-10-10 17:17:28 thread.c:1293:asic_status_monitor_thread: chain 1 can't get enough hashrate reg val for 12 times.
2020-10-10 17:17:28 temperature.c:843:get_temp_info: read temp sensor failed: chain = 1, sensor = 2, chip = 54, reg = 1
2020-10-10 17:17:29 temperature.c:843:get_temp_info: read temp sensor failed: chain = 1, sensor = 3, chip = 50, reg = 0
2020-10-10 17:17:29 thread.c:1273:asic_status_monitor_thread: ERROR: chain 1 get hashrate_reg_counter 48, require 65, failed times 1: ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo oooxx xxxxx xxxxx xxxxx
2020-10-10 17:17:29 temperature.c:843:get_temp_info: read temp sensor failed: chain = 1, sensor = 3, chip = 50, reg = 1
2020-10-10 17:17:30 thread.c:1293:asic_status_monitor_thread: chain 1 can't get enough hashrate reg val for 13 times.
2020-10-10 17:17:31 temperature.c:843:get_temp_info: read temp sensor failed: chain = 1, sensor = 2, chip = 54, reg = 0
2020-10-10 17:17:31 thread.c:1273:asic_status_monitor_thread: ERROR: chain 1 get hashrate_reg_counter 48, require 65, failed times 1: ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo oooxx xxxxx xxxxx xxxxx
2020-10-10 17:17:31 temperature.c:843:get_temp_info: read temp sensor failed: chain = 1, sensor = 2, chip = 54, reg = 1
2020-10-10 17:17:31 temperature.c:843:get_temp_info: read temp sensor failed: chain = 1, sensor = 3, chip = 50, reg = 0
2020-10-10 17:17:32 temperature.c:843:get_temp_info: read temp sensor failed: chain = 1, sensor = 3, chip = 50, reg = 1
2020-10-10 17:17:32 thread.c:1293:asic_status_monitor_thread: chain 1 can't get enough hashrate reg val for 14 times.
2020-10-10 17:17:33 thread.c:1273:asic_status_monitor_thread: ERROR: chain 1 get hashrate_reg_counter 48, require 65, failed times 1: ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo oooxx xxxxx xxxxx xxxxx
2020-10-10 17:17:33 temperature.c:843:get_temp_info: read temp sensor failed: chain = 1, sensor = 2, chip = 54, reg = 0
2020-10-10 17:17:34 temperature.c:843:get_temp_info: read temp sensor failed: chain = 1, sensor = 2, chip = 54, reg = 1
2020-10-10 17:17:34 temperature.c:843:get_temp_info: read temp sensor failed: chain = 1, sensor = 3, chip = 50, reg = 0
2020-10-10 17:17:34 temperature.c:843:get_temp_info: read temp sensor failed: chain = 1, sensor = 3, chip = 50, reg = 1
2020-10-10 17:17:34 thread.c:1293:asic_status_monitor_thread: chain 1 can't get enough hashrate reg val for 15 times.
2020-10-10 17:17:35 thread.c:1273:asic_status_monitor_thread: ERROR: chain 1 get hashrate_reg_counter 48, require 65, failed times 1: ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo oooxx xxxxx xxxxx xxxxx
2020-10-10 17:17:36 temperature.c:843:get_temp_info: read temp sensor failed: chain = 1, sensor = 2, chip = 54, reg = 0
2020-10-10 17:17:36 temperature.c:843:get_temp_info: read temp sensor failed: chain = 1, sensor = 2, chip = 54, reg = 1
2020-10-10 17:17:36 thread.c:1293:asic_status_monitor_thread: chain 1 can't get enough hashrate reg val for 16 times.
2020-10-10 17:17:37 temperature.c:843:get_temp_info: read temp sensor failed: chain = 1, sensor = 3, chip = 50, reg = 0
2020-10-10 17:17:37 thread.c:1273:asic_status_monitor_thread: ERROR: chain 1 get hashrate_reg_counter 48, require 65, failed times 1: ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo oooxx xxxxx xxxxx xxxxx
2020-10-10 17:17:37 temperature.c:843:get_temp_info: read temp sensor failed: chain = 1, sensor = 3, chip = 50, reg = 1
2020-10-10 17:17:38 thread.c:1293:asic_status_monitor_thread: chain 1 can't get enough hashrate reg val for 17 times.
2020-10-10 17:17:38 temperature.c:843:get_temp_info: read temp sensor failed: chain = 1, sensor = 2, chip = 54, reg = 0
2020-10-10 17:17:39 thread.c:1273:asic_status_monitor_thread: ERROR: chain 1 get hashrate_reg_counter 48, require 65, failed times 1: ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo oooxx xxxxx xxxxx xxxxx
2020-10-10 17:17:39 temperature.c:843:get_temp_info: read temp sensor failed: chain = 1, sensor = 2, chip = 54, reg = 1
2020-10-10 17:17:39 temperature.c:843:get_temp_info: read temp sensor failed: chain = 1, sensor = 3, chip = 50, reg = 0
2020-10-10 17:17:40 temperature.c:843:get_temp_info: read temp sensor failed: chain = 1, sensor = 3, chip = 50, reg = 1
2020-10-10 17:17:40 thread.c:1293:asic_status_monitor_thread: chain 1 can't get enough hashrate reg val for 18 times.
2020-10-10 17:17:41 thread.c:1273:asic_status_monitor_thread: ERROR: chain 1 get hashrate_reg_counter 48, require 65, failed times 1: ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo oooxx xxxxx xxxxx xxxxx
2020-10-10 17:17:41 temperature.c:843:get_temp_info: read temp sensor failed: chain = 1, sensor = 2, chip = 54, reg = 0
2020-10-10 17:17:41 temperature.c:843:get_temp_info: read temp sensor failed: chain = 1, sensor = 2, chip = 54, reg = 1
2020-10-10 17:17:42 temperature.c:843:get_temp_info: read temp sensor failed: chain = 1, sensor = 3, chip = 50, reg = 0
2020-10-10 17:17:42 temperature.c:843:get_temp_info: read temp sensor failed: chain = 1, sensor = 3, chip = 50, reg = 1
2020-10-10 17:17:42 thread.c:1293:asic_status_monitor_thread: chain 1 can't get enough hashrate reg val for 19 times.
2020-10-10 17:17:43 thread.c:1273:asic_status_monitor_thread: ERROR: chain 1 get hashrate_reg_counter 48, require 65, failed times 1: ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo oooxx xxxxx xxxxx xxxxx
2020-10-10 17:17:44 temperature.c:843:get_temp_info: read temp sensor failed: chain = 1, sensor = 2, chip = 54, reg = 0
2020-10-10 17:17:44 temperature.c:843:get_temp_info: read temp sensor failed: chain = 1, sensor = 2, chip = 54, reg = 1
2020-10-10 17:17:44 thread.c:1293:asic_status_monitor_thread: chain 1 can't get enough hashrate reg val for 20 times.
2020-10-10 17:17:44 temperature.c:843:get_temp_info: read temp sensor failed: chain = 1, sensor = 3, chip = 50, reg = 0
2020-10-10 17:17:45 thread.c:1273:asic_status_monitor_thread: ERROR: chain 1 get hashrate_reg_counter 48, require 65, failed times 1: ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo oooxx xxxxx xxxxx xxxxx
2020-10-10 17:17:45 temperature.c:843:get_temp_info: read temp sensor failed: chain = 1, sensor = 3, chip = 50, reg = 1
2020-10-10 17:17:46 thread.c:1293:asic_status_monitor_thread: chain 1 can't get enough hashrate reg val for 21 times.
2020-10-10 17:17:46 temperature.c:843:get_temp_info: read temp sensor failed: chain = 1, sensor = 2, chip = 54, reg = 0
2020-10-10 17:17:47 thread.c:1273:asic_status_monitor_thread: ERROR: chain 1 get hashrate_reg_counter 48, require 65, failed times 1: ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo oooxx xxxxx xxxxx xxxxx
2020-10-10 17:17:47 temperature.c:843:get_temp_info: read temp sensor failed: chain = 1, sensor = 2, chip = 54, reg = 1
2020-10-10 17:17:47 temperature.c:843:get_temp_info: read temp sensor failed: chain = 1, sensor = 3, chip = 50, reg = 0
2020-10-10 17:17:47 temperature.c:843:get_temp_info: read temp sensor failed: chain = 1, sensor = 3, chip = 50, reg = 1
2020-10-10 17:17:48 thread.c:1293:asic_status_monitor_thread: chain 1 can't get enough hashrate reg val for 22 times.
2020-10-10 17:17:49 thread.c:1273:asic_status_monitor_thread: ERROR: chain 1 get hashrate_reg_counter 48, require 65, failed times 1: ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo oooxx xxxxx xxxxx xxxxx
2020-10-10 17:17:49 temperature.c:843:get_temp_info: read temp sensor failed: chain = 1, sensor = 2, chip = 54, reg = 0
2020-10-10 17:17:49 temperature.c:843:get_temp_info: read temp sensor failed: chain = 1, sensor = 2, chip = 54, reg = 1
2020-10-10 17:17:50 temperature.c:843:get_temp_info: read temp sensor failed: chain = 1, sensor = 3, chip = 50, reg = 0
2020-10-10 17:17:50 temperature.c:843:get_temp_info: read temp sensor failed: chain = 1, sensor = 3, chip = 50, reg = 1
2020-10-10 17:17:50 thread.c:1293:asic_status_monitor_thread: chain 1 can't get enough hashrate reg val for 23 times.
2020-10-10 17:17:51 thread.c:1273:asic_status_monitor_thread: ERROR: chain 1 get hashrate_reg_counter 48, require 65, failed times 1: ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo oooxx xxxxx xxxxx xxxxx
2020-10-10 17:17:52 temperature.c:843:get_temp_info: read temp sensor failed: chain = 1, sensor = 2, chip = 54, reg = 0
2020-10-10 17:17:52 temperature.c:843:get_temp_info: read temp sensor failed: chain = 1, sensor = 2, chip = 54, reg = 1
2020-10-10 17:17:52 thread.c:1293:asic_status_monitor_thread: chain 1 can't get enough hashrate reg val for 24 times.
2020-10-10 17:17:52 temperature.c:843:get_temp_info: read temp sensor failed: chain = 1, sensor = 3, chip = 50, reg = 0
2020-10-10 17:17:53 temperature.c:843:get_temp_info: read temp sensor failed: chain = 1, sensor = 3, chip = 50, reg = 1
2020-10-10 17:17:53 thread.c:1273:asic_status_monitor_thread: ERROR: chain 1 get hashrate_reg_counter 48, require 65, failed times 1: ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo oooxx xxxxx xxxxx xxxxx
2020-10-10 17:17:54 temperature.c:843:get_temp_info: read temp sensor failed: chain = 1, sensor = 2, chip = 54, reg = 0
2020-10-10 17:17:54 thread.c:1293:asic_status_monitor_thread: chain 1 can't get enough hashrate reg val for 25 times.
2020-10-10 17:17:55 temperature.c:843:get_temp_info: read temp sensor failed: chain = 1, sensor = 2, chip = 54, reg = 1
2020-10-10 17:17:55 thread.c:1273:asic_status_monitor_thread: ERROR: chain 1 get hashrate_reg_counter 48, require 65, failed times 1: ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo oooxx xxxxx xxxxx xxxxx
2020-10-10 17:17:55 temperature.c:843:get_temp_info: read temp sensor failed: chain = 1, sensor = 3, chip = 50, reg = 0
2020-10-10 17:17:55 temperature.c:843:get_temp_info: read temp sensor failed: chain = 1, sensor = 3, chip = 50, reg = 1
2020-10-10 17:17:56 thread.c:1293:asic_status_monitor_thread: chain 1 can't get enough hashrate reg val for 26 times.
2020-10-10 17:17:57 thread.c:1273:asic_status_monitor_thread: ERROR: chain 1 get hashrate_reg_counter 48, require 65, failed times 1: ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo oooxx xxxxx xxxxx xxxxx
2020-10-10 17:17:57 temperature.c:843:get_temp_info: read temp sensor failed: chain = 1, sensor = 2, chip = 54, reg = 0
2020-10-10 17:17:57 temperature.c:843:get_temp_info: read temp sensor failed: chain = 1, sensor = 2, chip = 54, reg = 1
2020-10-10 17:17:58 temperature.c:843:get_temp_info: read temp sensor failed: chain = 1, sensor = 3, chip = 50, reg = 0
2020-10-10 17:17:58 temperature.c:843:get_temp_info: read temp sensor failed: chain = 1, sensor = 3, chip = 50, reg = 1
2020-10-10 17:17:58 thread.c:1293:asic_status_monitor_thread: chain 1 can't get enough hashrate reg val for 27 times.
2020-10-10 17:17:59 thread.c:1273:asic_status_monitor_thread: ERROR: chain 1 get hashrate_reg_counter 48, require 65, failed times 1: ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo oooxx xxxxx xxxxx xxxxx
2020-10-10 17:18:00 temperature.c:843:get_temp_info: read temp sensor failed: chain = 1, sensor = 2, chip = 54, reg = 0
2020-10-10 17:18:00 temperature.c:843:get_temp_info: read temp sensor failed: chain = 1, sensor = 2, chip = 54, reg = 1
2020-10-10 17:18:00 temperature.c:843:get_temp_info: read temp sensor failed: chain = 1, sensor = 3, chip = 50, reg = 0
2020-10-10 17:18:00 thread.c:1293:asic_status_monitor_thread: chain 1 can't get enough hashrate reg val for 28 times.
2020-10-10 17:18:01 temperature.c:843:get_temp_info: read temp sensor failed: chain = 1, sensor = 3, chip = 50, reg = 1
2020-10-10 17:18:01 thread.c:1273:asic_status_monitor_thread: ERROR: chain 1 get hashrate_reg_counter 48, require 65, failed times 1: ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo oooxx xxxxx xxxxx xxxxx
2020-10-10 17:18:02 temperature.c:843:get_temp_info: read temp sensor failed: chain = 1, sensor = 2, chip = 54, reg = 0
2020-10-10 17:18:02 thread.c:1293:asic_status_monitor_thread: chain 1 can't get enough hashrate reg val for 29 times.
2020-10-10 17:18:02 thread.c:1297:asic_status_monitor_thread: chain 1 can't get enough hashrate reg val for 30 times, power off.
2020-10-10 17:18:03 temperature.c:843:get_temp_info: read temp sensor failed: chain = 1, sensor = 2, chip = 54, reg = 1
2020-10-10 17:18:03 temperature.c:843:get_temp_info: read temp sensor failed: chain = 1, sensor = 3, chip = 50, reg = 0
2020-10-10 17:18:03 temperature.c:843:get_temp_info: read temp sensor failed: chain = 1, sensor = 3, chip = 50, reg = 1
2020-10-10 17:18:03 driver-btm-api.c:222:set_miner_status: ERROR_ASIC_LOSS
2020-10-10 17:18:03 driver-btm-api.c:156:stop_mining: stop mining: all chains meet asic loss.
2020-10-10 17:18:03 thread.c:1419:cancel_check_miner_status_thread: cancel thread
2020-10-10 17:18:03 thread.c:1388:cancel_temperature_monitor_thread: cancel thread
2020-10-10 17:18:03 thread.c:1414:cancel_check_system_status_thread: cancel thread
2020-10-10 17:18:03 thread.c:1403:cancel_read_nonce_reg_thread: cancel thread
2020-10-10 17:18:03 driver-btm-api.c:141:killall_hashboard: ****power off hashboard****
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: mikeywith on October 11, 2020, 10:06:43 PM
This is the important part of the kernel log 2020-10-10 17:04:04 driver-btm-api.c:1157:check_asic_number_with_power_on: Chain[0]: find 0 asic, times 5 2020-10-10 17:05:34 driver-btm-api.c:1157:check_asic_number_with_power_on: Chain[2]: find 0 asic, times 5 These two lines suggest that these two hash boards are dead, that's most likely due to the fact that some heatsinks lost contact to the chip due to bad quality of the thermal paste bitmain used on these 17 series.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: Moeter81 on October 12, 2020, 03:35:41 AM
It started with one chain not working, then another, and then another, so it wasn't always the same chain, so I thought there might be another problem.
I took off both fans to clean them, but couldn't see any loose heat sinks.
wouldn't it be possible to re-solder the chips (heat sinks)?
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: mikeywith on October 13, 2020, 09:17:48 PM
It started with one chain not working, then another, and then another, so it wasn't always the same chain, so I thought there might be another problem.
Could you explain more? Do you mean sometimes Chain 0 and 1 work fine while Chain 2 doesn't, and then the next day Chain 0 doesn't work while Chain 1 and 2 work just fine? If that is the case then this could be a power related issue, I will tell you how to troubleshoot it if that is what you mean, but if you mean that all 3 boards failed at different times then the previous analysis still stands. I took off both fans to clean them, but couldn't see any loose heat sinks.
wouldn't it be possible to re-solder the chips (heat sinks)?
Most of the time the heatsinks are not loose enough to fall, so you can't really see them, they are just not in a perfect contact with the chip, sometimes the heatsink is fine but the chip itself is loose from the board, there isn't much you can inspect with your bare eyes, a simple shake would reveal if a heatsink has fallen. As for fixing these heatsinks and chips, it really isn't that simple, we discussed that in several topics before just search the forum, and you will find all the information you need.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: Moeter81 on October 14, 2020, 04:45:42 PM
now he has given up completely. But first he finds 2 chains and then again not. all very strange.
Booting Linux on physical CPU 0x0
Linux version 4.6.0-xilinx-gff8137b-dirty (lzq@armdev2) (gcc version 4.8.3 20140320 (prerelease) (Sourcery CodeBench Lite 2014.05-23) ) #25 SMP PREEMPT Fri Nov 23 15:30:52 CST 2018
CPU: ARMv7 Processor [413fc090] revision 0 (ARMv7), cr=18c5387d
CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
Machine model: Xilinx Zynq
cma: Reserved 16 MiB at 0x0e000000
Memory policy: Data cache writealloc
On node 0 totalpages: 61440
free_area_init_node: node 0, pgdat c0b39280, node_mem_map cde10000
Normal zone: 480 pages used for memmap
Normal zone: 0 pages reserved
Normal zone: 61440 pages, LIFO batch:15
percpu: Embedded 12 pages/cpu @cddf1000 s19776 r8192 d21184 u49152
pcpu-alloc: s19776 r8192 d21184 u49152 alloc=12*4096
pcpu-alloc: [0] 0 [0] 1
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 60960
Kernel command line: mem=240M console=ttyPS0,115200 ramdisk_size=33554432 root=/dev/ram rw earlyprintk
PID hash table entries: 1024 (order: 0, 4096 bytes)
Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
Memory: 203432K/245760K available (6345K kernel code, 231K rwdata, 1896K rodata, 1024K init, 223K bss, 25944K reserved, 16384K cma-reserved, 0K highmem)
Virtual kernel memory layout:
vector : 0xffff0000 - 0xffff1000 ( 4 kB)
fixmap : 0xffc00000 - 0xfff00000 (3072 kB)
vmalloc : 0xcf800000 - 0xff800000 ( 768 MB)
lowmem : 0xc0000000 - 0xcf000000 ( 240 MB)
pkmap : 0xbfe00000 - 0xc0000000 ( 2 MB)
modules : 0xbf000000 - 0xbfe00000 ( 14 MB)
.text : 0xc0008000 - 0xc090c424 (9234 kB)
.init : 0xc0a00000 - 0xc0b00000 (1024 kB)
.data : 0xc0b00000 - 0xc0b39fe0 ( 232 kB)
.bss : 0xc0b39fe0 - 0xc0b71c28 ( 224 kB)
Preemptible hierarchical RCU implementation.
Build-time adjustment of leaf fanout to 32.
RCU restricting CPUs from NR_CPUS=4 to nr_cpu_ids=2.
RCU: Adjusting geometry for rcu_fanout_leaf=32, nr_cpu_ids=2
NR_IRQS:16 nr_irqs:16 16
efuse mapped to cf800000
ps7-slcr mapped to cf802000
L2C: platform modifies aux control register: 0x72360000 -> 0x72760000
L2C: DT/platform modifies aux control register: 0x72360000 -> 0x72760000
L2C-310 erratum 769419 enabled
L2C-310 enabling early BRESP for Cortex-A9
L2C-310 full line of zeros enabled for Cortex-A9
L2C-310 ID prefetch enabled, offset 1 lines
L2C-310 dynamic clock gating enabled, standby mode enabled
L2C-310 cache controller enabled, 8 ways, 512 kB
L2C-310: CACHE_ID 0x410000c8, AUX_CTRL 0x76760001
zynq_clock_init: clkc starts at cf802100
Zynq clock init
sched_clock: 64 bits at 333MHz, resolution 3ns, wraps every 4398046511103ns
clocksource: arm_global_timer: mask: 0xffffffffffffffff max_cycles: 0x4ce07af025, max_idle_ns: 440795209040 ns
Switching to timer-based delay loop, resolution 3ns
clocksource: ttc_clocksource: mask: 0xffff max_cycles: 0xffff, max_idle_ns: 537538477 ns
ps7-ttc #0 at cf80a000, irq=18
Console: colour dummy device 80x30
Calibrating delay loop (skipped), value calculated using timer frequency.. 666.66 BogoMIPS (lpj=3333333)
pid_max: default: 32768 minimum: 301
Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
CPU: Testing write buffer coherency: ok
CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
Setting up static identity map for 0x100000 - 0x100058
CPU1: failed to boot: -1
Brought up 1 CPUs
SMP: Total of 1 processors activated (666.66 BogoMIPS).
CPU: All CPU(s) started in SVC mode.
devtmpfs: initialized
VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4
clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
pinctrl core: initialized pinctrl subsystem
NET: Registered protocol family 16
DMA: preallocated 256 KiB pool for atomic coherent allocations
cpuidle: using governor menu
hw-breakpoint: found 5 (+1 reserved) breakpoint and 1 watchpoint registers.
hw-breakpoint: maximum watchpoint size is 4 bytes.
zynq-ocm f800c000.ps7-ocmc: ZYNQ OCM pool: 256 KiB @ 0xcf880000
vgaarb: loaded
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
media: Linux media interface: v0.10
Linux video capture interface: v2.00
pps_core: LinuxPPS API ver. 1 registered
pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
PTP clock support registered
EDAC MC: Ver: 3.0.0
Advanced Linux Sound Architecture Driver Initialized.
clocksource: Switched to clocksource arm_global_timer
NET: Registered protocol family 2
TCP established hash table entries: 2048 (order: 1, 8192 bytes)
TCP bind hash table entries: 2048 (order: 2, 16384 bytes)
TCP: Hash tables configured (established 2048 bind 2048)
UDP hash table entries: 256 (order: 1, 8192 bytes)
UDP-Lite hash table entries: 256 (order: 1, 8192 bytes)
NET: Registered protocol family 1
RPC: Registered named UNIX socket transport module.
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
PCI: CLS 0 bytes, default 64
Trying to unpack rootfs image as initramfs...
rootfs image is not initramfs (no cpio magic); looks like an initrd
Freeing initrd memory: 12904K (cce67000 - cdb01000)
hw perfevents: enabled with armv7_cortex_a9 PMU driver, 7 counters available
futex hash table entries: 512 (order: 3, 32768 bytes)
workingset: timestamp_bits=28 max_order=16 bucket_order=0
jffs2: version 2.2. (NAND) (SUMMARY) © 2001-2006 Red Hat, Inc.
io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered (default)
dma-pl330 f8003000.ps7-dma: Loaded driver for PL330 DMAC-241330
dma-pl330 f8003000.ps7-dma: DBUFF-128x8bytes Num_Chans-8 Num_Peri-4 Num_Events-16
e0000000.serial: ttyPS0 at MMIO 0xe0000000 (irq = 158, base_baud = 6249999) is a xuartps
console [ttyPS0] enabled
xdevcfg f8007000.ps7-dev-cfg: ioremap 0xf8007000 to cf86e000
[drm] Initialized drm 1.1.0 20060810
brd: module loaded
loop: module loaded
CAN device driver interface
gpiod_set_value: invalid GPIO
libphy: MACB_mii_bus: probed
macb e000b000.ethernet eth0: Cadence GEM rev 0x00020118 at 0xe000b000 irq 31 (00:0a:35:00:00:00)
Generic PHY e000b000.etherne:00: attached PHY driver [Generic PHY] (mii_bus:phy_addr=e000b000.etherne:00, irq=-1)
e1000e: Intel(R) PRO/1000 Network Driver - 3.2.6-k
e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
ehci-pci: EHCI PCI platform driver
usbcore: registered new interface driver usb-storage
mousedev: PS/2 mouse device common for all mice
i2c /dev entries driver
Xilinx Zynq CpuIdle Driver started
sdhci: Secure Digital Host Controller Interface driver
sdhci: Copyright(c) Pierre Ossman
sdhci-pltfm: SDHCI platform and OF driver helper
mmc0: SDHCI controller on e0100000.ps7-sdio [e0100000.ps7-sdio] using ADMA
ledtrig-cpu: registered to indicate activity on CPUs
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
nand: device found, Manufacturer ID: 0x2c, Chip ID: 0xda
nand: Micron MT29F2G08ABAGAWP
nand: 256 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 128
nand: WARNING: pl35x-nand: the ECC used on your system is too weak compared to the one required by the NAND chip
Bad block table found at page 131008, version 0x01
Bad block table found at page 130944, version 0x01
6 ofpart partitions found on MTD device pl35x-nand
Creating 6 MTD partitions on "pl35x-nand":
0x000000000000-0x000002800000 : "BOOT.bin-env-dts-kernel"
0x000002800000-0x000004800000 : "ramfs"
0x000004800000-0x000005000000 : "configs"
0x000005000000-0x000006000000 : "reserve"
0x000006000000-0x000008000000 : "ramfs-bak"
0x000008000000-0x000010000000 : "reserve1"
NET: Registered protocol family 10
sit: IPv6 over IPv4 tunneling driver
NET: Registered protocol family 17
can: controller area network core (rev 20120528 abi 9)
NET: Registered protocol family 29
can: raw protocol (rev 20120528)
can: broadcast manager protocol (rev 20120528 t)
can: netlink gateway (rev 20130117) max_hops=1
zynq_pm_ioremap: no compatible node found for 'xlnx,zynq-ddrc-a05'
zynq_pm_late_init: Unable to map DDRC IO memory.
Registering SWP/SWPB emulation handler
hctosys: unable to open rtc device (rtc0)
ALSA device list:
No soundcards found.
RAMDISK: gzip image found at block 0
EXT4-fs (ram0): couldn't mount as ext3 due to feature incompatibilities
EXT4-fs (ram0): mounted filesystem without journal. Opts: (null)
VFS: Mounted root (ext4 filesystem) on device 1:0.
devtmpfs: mounted
Freeing unused kernel memory: 1024K (c0a00000 - c0b00000)
EXT4-fs (ram0): re-mounted. Opts: block_validity,delalloc,barrier,user_xattr
random: dd urandom read with 0 bits of entropy available
ubi0: attaching mtd2
ubi0: scanning is finished
ubi0: attached mtd2 (name "configs", size 8 MiB)
ubi0: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
ubi0: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
ubi0: VID header offset: 2048 (aligned 2048), data offset: 4096
ubi0: good PEBs: 64, bad PEBs: 0, corrupted PEBs: 0
ubi0: user volume: 1, internal volumes: 1, max. volumes count: 128
ubi0: max/mean erase counter: 20/9, WL threshold: 4096, image sequence number: 237714726
ubi0: available PEBs: 0, total reserved PEBs: 64, PEBs reserved for bad PEB handling: 40
ubi0: background thread "ubi_bgt0d" started, PID 708
UBIFS (ubi0:0): background thread "ubifs_bgt0_0" started, PID 711
UBIFS (ubi0:0): UBIFS: mounted UBI device 0, volume 0, name "configs"
UBIFS (ubi0:0): LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
UBIFS (ubi0:0): FS size: 1396736 bytes (1 MiB, 11 LEBs), journal size 888833 bytes (0 MiB, 5 LEBs)
UBIFS (ubi0:0): reserved for root: 65970 bytes (64 KiB)
UBIFS (ubi0:0): media format: w4/r0 (latest is w4/r0), UUID FF09433B-E002-4C29-97EC-6220DDC4BB36, 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: 3361/790, WL threshold: 4096, image sequence number: 3265111179
ubi1: available PEBs: 0, total reserved PEBs: 1020, PEBs reserved for bad PEB handling: 36
ubi1: background thread "ubi_bgt1d" started, PID 720
UBIFS (ubi1:0): background thread "ubifs_bgt1_0" started, PID 723
UBIFS (ubi1:0): UBIFS: mounted UBI device 1, volume 0, name "reserve1"
UBIFS (ubi1:0): LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
UBIFS (ubi1:0): FS size: 123039744 bytes (117 MiB, 969 LEBs), journal size 6221824 bytes (5 MiB, 49 LEBs)
UBIFS (ubi1:0): reserved for root: 4952683 bytes (4836 KiB)
UBIFS (ubi1:0): media format: w4/r0 (latest is w4/r0), UUID 1AF6F1E1-61F0-462C-AE44-C7D9596CF7E2, 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 = 0xb023
In fpga mem driver!
request_mem_region OK!
fpga mem virtual address is 0xd2000000
random: nonblocking pool is initialized
2020-10-14 16:33:07 driver-btm-api.c:779:init_freq_mode: This is scan-user version
2020-10-14 16:33:07 driver-btm-api.c:2451:bitmain_soc_init: opt_multi_version = 1
2020-10-14 16:33:07 driver-btm-api.c:2452:bitmain_soc_init: opt_bitmain_ab = 1
2020-10-14 16:33:07 driver-btm-api.c:2453:bitmain_soc_init: opt_bitmain_work_mode = 0
2020-10-14 16:33:07 driver-btm-api.c:2454:bitmain_soc_init: Miner compile time: Tue Jun 2 10:31:07 CST 2020 type: Antminer S17+
2020-10-14 16:33:07 driver-btm-api.c:2455:bitmain_soc_init: commit version: 1ca50a5 2020-06-01 18:51:22, build by: lol 2020-06-02 10:37:21
2020-10-14 16:33:07 driver-btm-api.c:2083:show_sn: len:16, 8048ed0c2b104814
2020-10-14 16:33:07 driver-btm-api.c:2461:bitmain_soc_init: show sn return 1
2020-10-14 16:33:07 driver-btm-api.c:2103:handle_sn_for_factory_mode: show sn return 1
2020-10-14 16:33:07 driver-btm-api.c:2141:handle_sn_for_factory_mode: read sn success, 8048ed0c2b104814
2020-10-14 16:33:07 fan.c:284:front_fan_power_on: Note: front fan is power on!
2020-10-14 16:33:07 fan.c:296:rear_fan_power_on: Note: rear fan is power on!
2020-10-14 16:33:07 driver-btm-api.c:1314:miner_device_init: Detect 256MB control board of XILINX
2020-10-14 16:33:07 driver-btm-api.c:1255:init_fan_parameter: fan_eft : 0 fan_pwm : 0
2020-10-14 16:33:13 driver-btm-api.c:1239:init_miner_version: miner ID : 8048ed0c2b104814
2020-10-14 16:33:13 driver-btm-api.c:1245:init_miner_version: FPGA Version = 0xB023
2020-10-14 16:33:14 chain = 0, mode = 0, load_done = false.
2020-10-14 16:33:14 chain = 1, mode = 0, load_done = false.
2020-10-14 16:33:14 chain = 2, mode = 0, load_done = false.
2020-10-14 16:33:14 chain = 0, load_done = false
2020-10-14 16:33:14 chain = 1, load_done = false
2020-10-14 16:33:14 chain = 2, load_done = false
2020-10-14 16:33:18 driver-btm-api.c:837:get_product_id: product_id[0] = 0
2020-10-14 16:33:18 driver-btm-api.c:837:get_product_id: product_id[1] = 0
2020-10-14 16:33:18 driver-btm-api.c:837:get_product_id: product_id[2] = 0
2020-10-14 16:33:18 driver-btm-api.c:2234:update_conf_by_power_feedback: Power feedback is disabled
2020-10-14 16:33:18 driver-btm-api.c:2202:get_calibration_voltage: calibration voltage flag is error data.
2020-10-14 16:33:18 driver-btm-api.c:2268:update_conf_by_power_feedback: Note: no calibration voltage, default diff = 0
2020-10-14 16:33:18 frequency.c:1457:adjust_higer_max_vol_table: adjust_higer_max_vol_table, adjust_vol = 0
2020-10-14 16:33:18 thread.c:1363:create_read_nonce_reg_thread: create thread
2020-10-14 16:33:19 frequency.c:205:get_ideal_hash_rate_GH: ideal_hash_rate = 67628
2020-10-14 16:33:24 driver-btm-api.c:1239:init_miner_version: miner ID : 8048ed0c2b104814
2020-10-14 16:33:24 driver-btm-api.c:1245:init_miner_version: FPGA Version = 0xB023
2020-10-14 16:33:29 chain = 0, load_done = false
2020-10-14 16:33:29 chain = 1, load_done = false
2020-10-14 16:33:29 chain = 2, load_done = false
2020-10-14 16:33:30 driver-btm-api.c:837:get_product_id: product_id[0] = 0
2020-10-14 16:33:30 driver-btm-api.c:837:get_product_id: product_id[1] = 0
2020-10-14 16:33:30 driver-btm-api.c:837:get_product_id: product_id[2] = 0
2020-10-14 16:33:30 driver-btm-api.c:792:_set_project_type: project:0
2020-10-14 16:33:30 driver-btm-api.c:813:_set_project_type: Project type: Antminer S17+
2020-10-14 16:33:30 driver-btm-api.c:824:dump_pcb_bom_version: Chain [0] PCB Version: 0x0100
2020-10-14 16:33:30 driver-btm-api.c:825:dump_pcb_bom_version: Chain [0] BOM Version: 0x0100
2020-10-14 16:33:30 driver-btm-api.c:824:dump_pcb_bom_version: Chain [1] PCB Version: 0x0100
2020-10-14 16:33:30 driver-btm-api.c:825:dump_pcb_bom_version: Chain [1] BOM Version: 0x0100
2020-10-14 16:33:30 driver-btm-api.c:824:dump_pcb_bom_version: Chain [2] PCB Version: 0x0100
2020-10-14 16:33:30 driver-btm-api.c:825:dump_pcb_bom_version: Chain [2] BOM Version: 0x0100
2020-10-14 16:33:32 driver-btm-api.c:2372:bitmain_board_init: Fan check passed.
2020-10-14 16:33:33 board.c:36:jump_and_app_check_restore_pic: chain[0] PIC jump to app
2020-10-14 16:33:35 board.c:40:jump_and_app_check_restore_pic: Check chain[0] PIC fw version=0x88
2020-10-14 16:33:36 board.c:36:jump_and_app_check_restore_pic: chain[1] PIC jump to app
2020-10-14 16:33:38 board.c:40:jump_and_app_check_restore_pic: Check chain[1] PIC fw version=0x88
2020-10-14 16:33:39 board.c:36:jump_and_app_check_restore_pic: chain[2] PIC jump to app
2020-10-14 16:33:41 board.c:40:jump_and_app_check_restore_pic: Check chain[2] PIC fw version=0x88
2020-10-14 16:33:41 thread.c:1358:create_pic_heart_beat_thread: create thread
2020-10-14 16:33:41 power_api.c:213:power_init: Power init:
2020-10-14 16:33:41 power_api.c:214:power_init: current_voltage_raw = 0
2020-10-14 16:33:41 power_api.c:215:power_init: highest_voltage_raw = 2100
2020-10-14 16:33:41 power_api.c:216:power_init: working_voltage_raw = 1950
2020-10-14 16:33:41 power_api.c:217:power_init: higher_voltage_raw = 2040
2020-10-14 16:33:41 power_api.c:218:power_init: check_asic_voltage_raw = 2100
2020-10-14 16:33:41 driver-btm-api.c:2382:bitmain_board_init: Enter 30s sleep to make sure power release finish.
2020-10-14 16:34:13 power_api.c:324:set_to_highest_voltage_by_steps: Set to voltage raw 2100, step by step.
2020-10-14 16:34:39 power_api.c:85:check_voltage_multi: retry time: 0
2020-10-14 16:34:40 power_api.c:40:_get_avg_voltage: chain = 0, voltage = 21.108418
2020-10-14 16:34:41 power_api.c:40:_get_avg_voltage: chain = 1, voltage = 21.006361
2020-10-14 16:34:42 power_api.c:40:_get_avg_voltage: chain = 2, voltage = 21.108418
2020-10-14 16:34:42 power_api.c:53:_get_avg_voltage: average_voltage = 21.074399
2020-10-14 16:34:42 power_api.c:71:check_voltage: target_vol = 21.00, actural_vol = 21.07, check voltage passed.
2020-10-14 16:34:42 uart.c:72:set_baud: set fpga_baud to 115200
2020-10-14 16:34:53 driver-btm-api.c:1134:check_asic_number_with_power_on: Chain[0]: find 65 asic, times 0
2020-10-14 16:35:04 driver-btm-api.c:1134:check_asic_number_with_power_on: Chain[1]: find 65 asic, times 0
2020-10-14 16:35:15 driver-btm-api.c:1134:check_asic_number_with_power_on: Chain[2]: find 0 asic, times 0
2020-10-14 16:35:26 driver-btm-api.c:1134:check_asic_number_with_power_on: Chain[2]: find 0 asic, times 1
2020-10-14 16:35:36 driver-btm-api.c:1134:check_asic_number_with_power_on: Chain[2]: find 0 asic, times 2
2020-10-14 16:35:36 power_api.c:380:modify_check_asic_voltage: check_asic_voltage_raw = 2100
chain 2, IO_DRIVE_STRENGTH_CONFIGURATION reg = 0x f1fffff
2020-10-14 16:35:45 driver-btm-api.c:1157:check_asic_number_with_power_on: Chain[2]: find 0 asic, times 3
2020-10-14 16:35:45 power_api.c:380:modify_check_asic_voltage: check_asic_voltage_raw = 2050
2020-10-14 16:35:45 power_api.c:364:set_to_check_asic_voltage_by_steps: Set to voltage raw 2050, step by step.
2020-10-14 16:35:48 power_api.c:85:check_voltage_multi: retry time: 0
2020-10-14 16:35:50 power_api.c:40:_get_avg_voltage: chain = 0, voltage = 20.547073
2020-10-14 16:35:51 power_api.c:40:_get_avg_voltage: chain = 1, voltage = 20.448539
2020-10-14 16:35:52 power_api.c:40:_get_avg_voltage: chain = 2, voltage = 20.573249
2020-10-14 16:35:52 power_api.c:53:_get_avg_voltage: average_voltage = 20.522954
2020-10-14 16:35:52 power_api.c:71:check_voltage: target_vol = 20.50, actural_vol = 20.52, check voltage passed.
chain 2, IO_DRIVE_STRENGTH_CONFIGURATION reg = 0x f1fffff
2020-10-14 16:36:01 driver-btm-api.c:1157:check_asic_number_with_power_on: Chain[2]: find 0 asic, times 4
2020-10-14 16:36:01 power_api.c:380:modify_check_asic_voltage: check_asic_voltage_raw = 2000
2020-10-14 16:36:01 power_api.c:364:set_to_check_asic_voltage_by_steps: Set to voltage raw 2000, step by step.
2020-10-14 16:36:04 power_api.c:85:check_voltage_multi: retry time: 0
2020-10-14 16:36:05 power_api.c:40:_get_avg_voltage: chain = 0, voltage = 20.063613
2020-10-14 16:36:06 power_api.c:40:_get_avg_voltage: chain = 1, voltage = 19.991094
2020-10-14 16:36:07 power_api.c:40:_get_avg_voltage: chain = 2, voltage = 20.063613
2020-10-14 16:36:07 power_api.c:53:_get_avg_voltage: average_voltage = 20.039440
2020-10-14 16:36:07 power_api.c:71:check_voltage: target_vol = 20.00, actural_vol = 20.04, check voltage passed.
chain 2, IO_DRIVE_STRENGTH_CONFIGURATION reg = 0x f1fffff
2020-10-14 16:36:16 driver-btm-api.c:1157:check_asic_number_with_power_on: Chain[2]: find 0 asic, times 5
2020-10-14 16:36:16 power_api.c:380:modify_check_asic_voltage: check_asic_voltage_raw = 2100
2020-10-14 16:36:16 power_api.c:364:set_to_check_asic_voltage_by_steps: Set to voltage raw 2100, step by step.
2020-10-14 16:36:21 power_api.c:85:check_voltage_multi: retry time: 0
2020-10-14 16:36:23 power_api.c:40:_get_avg_voltage: chain = 0, voltage = 21.057326
2020-10-14 16:36:24 power_api.c:40:_get_avg_voltage: chain = 1, voltage = 20.982188
2020-10-14 16:36:25 power_api.c:40:_get_avg_voltage: chain = 2, voltage = 21.030534
2020-10-14 16:36:25 power_api.c:53:_get_avg_voltage: average_voltage = 21.023349
2020-10-14 16:36:25 power_api.c:71:check_voltage: target_vol = 21.00, actural_vol = 21.02, check voltage passed.
2020-10-14 16:36:25 driver-btm-api.c:1193:check_asic_number: Chain 2 only find 0 asic, will power off hash board 2
2020-10-14 16:36:26 driver-btm-api.c:1195:check_asic_number: Chain 2 voltage: an0 = 2.816129, an2 2.809677, an6 2.532258.
2020-10-14 16:36:29 frequency.c:205:get_ideal_hash_rate_GH: ideal_hash_rate = 45568
2020-10-14 16:36:33 driver-hash-chip.c:266:set_uart_relay: set uart relay to 0x330003
2020-10-14 16:36:33 driver-btm-api.c:435:set_order_clock: chain[0]: set order clock, stragegy 3
2020-10-14 16:36:33 driver-btm-api.c:435:set_order_clock: chain[1]: set order clock, stragegy 3
2020-10-14 16:36:33 driver-hash-chip.c:502:set_clock_delay_control: core_data = 0x34
2020-10-14 16:36:33 driver-btm-api.c:1892:check_clock_counter: freq 50 clock_counter_limit 6
2020-10-14 16:36:34 voltage[0] = 1980
2020-10-14 16:36:34 voltage[1] = 1980
2020-10-14 16:36:34 power_api.c:226:set_working_voltage_raw: working_voltage_raw = 1980
2020-10-14 16:36:35 temperature.c:340:calibrate_temp_sensor_one_chain: chain 0 temp sensor NCT218
2020-10-14 16:36:36 temperature.c:340:calibrate_temp_sensor_one_chain: chain 1 temp sensor NCT218
2020-10-14 16:36:36 uart.c:72:set_baud: set fpga_baud to 12000000
2020-10-14 16:36:37 driver-btm-api.c:293:check_bringup_temp: Bring up temperature is 21
2020-10-14 16:36:37 thread.c:1378:create_check_miner_status_thread: create thread
2020-10-14 16:36:37 thread.c:1368:create_show_miner_status_thread: create thread
2020-10-14 16:36:37 thread.c:1348:create_temperature_monitor_thread: create thread
2020-10-14 16:36:37 frequency.c:514:check_bringup_temp_dec_freq: dec freq = 0 when bringup temp = 21 dec_freq_index=0
2020-10-14 16:36:37 freq_tuning.c:183:freq_tuning_get_max_freq: Max freq of tuning is 650
2020-10-14 16:36:37 driver-btm-api.c:1765:send_null_work: [DEBUG] Send null work.
2020-10-14 16:36:37 thread.c:1338:create_asic_status_monitor_thread: create thread
2020-10-14 16:36:37 frequency.c:1110:inc_freq_with_fixed_vco: chain = 255, freq = 530, is_higher_voltage = true
2020-10-14 16:36:38 frequency.c:205:get_ideal_hash_rate_GH: ideal_hash_rate = 45568
2020-10-14 16:37:37 temperature.c:843:get_temp_info: read temp sensor failed: chain = 1, sensor = 3, chip = 50, reg = 0
2020-10-14 16:37:37 thread.c:1273:asic_status_monitor_thread: ERROR: chain 1 get hashrate_reg_counter 40, require 65, failed times 1: ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo xxxxx xxxxx xxxxx xxxxx xxxxx
2020-10-14 16:37:37 temperature.c:843:get_temp_info: read temp sensor failed: chain = 1, sensor = 3, chip = 50, reg = 1
2020-10-14 16:37:39 thread.c:1293:asic_status_monitor_thread: chain 1 can't get enough hashrate reg val for 0 times.
2020-10-14 16:37:39 thread.c:1273:asic_status_monitor_thread: ERROR: chain 1 get hashrate_reg_counter 40, require 65, failed times 1: ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo xxxxx xxxxx xxxxx xxxxx xxxxx
2020-10-14 16:37:39 temperature.c:843:get_temp_info: read temp sensor failed: chain = 1, sensor = 2, chip = 54, reg = 0
2020-10-14 16:37:39 temperature.c:843:get_temp_info: read temp sensor failed: chain = 1, sensor = 2, chip = 54, reg = 1
2020-10-14 16:37:40 temperature.c:843:get_temp_info: read temp sensor failed: chain = 1, sensor = 3, chip = 50, reg = 0
2020-10-14 16:37:40 temperature.c:843:get_temp_info: read temp sensor failed: chain = 1, sensor = 3, chip = 50, reg = 1
2020-10-14 16:37:41 thread.c:1293:asic_status_monitor_thread: chain 1 can't get enough hashrate reg val for 1 times.
2020-10-14 16:37:41 thread.c:1273:asic_status_monitor_thread: ERROR: chain 1 get hashrate_reg_counter 40, require 65, failed times 1: ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo xxxxx xxxxx xxxxx xxxxx xxxxx
2020-10-14 16:37:42 temperature.c:843:get_temp_info: read temp sensor failed: chain = 1, sensor = 2, chip = 54, reg = 0
2020-10-14 16:37:42 temperature.c:843:get_temp_info: read temp sensor failed: chain = 1, sensor = 2, chip = 54, reg = 1
2020-10-14 16:37:43 thread.c:1293:asic_status_monitor_thread: chain 1 can't get enough hashrate reg val for 2 times.
2020-10-14 16:37:43 temperature.c:843:get_temp_info: read temp sensor failed: chain = 1, sensor = 3, chip = 50, reg = 0
2020-10-14 16:37:43 thread.c:1273:asic_status_monitor_thread: ERROR: chain 1 get hashrate_reg_counter 40, require 65, failed times 1: ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo xxxxx xxxxx xxxxx xxxxx xxxxx
2020-10-14 16:37:43 temperature.c:843:get_temp_info: read temp sensor failed: chain = 1, sensor = 3, chip = 50, reg = 1
2020-10-14 16:37:45 thread.c:1293:asic_status_monitor_thread: chain 1 can't get enough hashrate reg val for 3 times.
2020-10-14 16:37:45 thread.c:1273:asic_status_monitor_thread: ERROR: chain 1 get hashrate_reg_counter 40, require 65, failed times 1: ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo xxxxx xxxxx xxxxx xxxxx xxxxx
2020-10-14 16:37:45 temperature.c:843:get_temp_info: read temp sensor failed: chain = 1, sensor = 2, chip = 54, reg = 0
2020-10-14 16:37:45 temperature.c:843:get_temp_info: read temp sensor failed: chain = 1, sensor = 2, chip = 54, reg = 1
2020-10-14 16:37:46 temperature.c:843:get_temp_info: read temp sensor failed: chain = 1, sensor = 3, chip = 50, reg = 0
2020-10-14 16:37:46 temperature.c:843:get_temp_info: read temp sensor failed: chain = 1, sensor = 3, chip = 50, reg = 1
2020-10-14 16:37:47 thread.c:1293:asic_status_monitor_thread: chain 1 can't get enough hashrate reg val for 4 times.
2020-10-14 16:37:47 thread.c:1297:asic_status_monitor_thread: chain 1 can't get enough hashrate reg val for 5 times, power off.
2020-10-14 16:37:49 frequency.c:205:get_ideal_hash_rate_GH: ideal_hash_rate = 22997
2020-10-14 16:39:02 power_api.c:352:set_to_voltage_by_steps: Set to voltage raw 2090, step by step.
2020-10-14 16:39:04 power_api.c:85:check_voltage_multi: retry time: 0
2020-10-14 16:39:05 power_api.c:40:_get_avg_voltage: chain = 0, voltage = 20.909669
2020-10-14 16:39:05 power_api.c:53:_get_avg_voltage: average_voltage = 20.909669
2020-10-14 16:39:05 power_api.c:71:check_voltage: target_vol = 20.90, actural_vol = 20.91, check voltage passed.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: mikeywith on October 15, 2020, 08:05:58 PM
It is normal for these Antminers to act strange, I still think your issue is a loose heatsink that sometimes works and sometimes doesn't, however, what you described in your last post could also mean that your PSU is faulty, usually, when the temp-sensor issue appears on a single hash board, it means that particular board is bad, but when it happens on all chains then there is a good chance that the PSU is going bad and it can't supply enough power to all boards.
To troubleshoot this you would try with a another PSU, and then remove two hash boards and keep only one at a time, start by keeping chain 0 and then chain 1 and lastly chain 2, by doing this you will confirm whether you have good working hash boards and just need a new PSU or your PSU is fine but the boards are dead.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: Moeter81 on October 17, 2020, 06:36:30 AM
I'll swap the power supplies and then report whether it worked.
thanks for the help.
greeting
Moeter
I've swapped the power supplies. But the problem is the same. I also removed all 3 boards and checked them visually, but I couldn't find any abnormalities. I could still try to swap the control board, but I think that doesn't help either. What else can I do useful with the miner?
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: favebook on October 17, 2020, 09:11:09 AM
I've swapped the power supplies. But the problem is the same.
I also removed all 3 boards and checked them visually, but I couldn't find any abnormalities.
I could still try to swap the control board, but I think that doesn't help either.
What else can I do useful with the miner?
Sadly, your only viable choice would be RMA. Control board is rarely the problem, you ruled out PSU which I already doubted would be the problem as I had similar problem. The problem lies within the hashboards, and there is not much you can do.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: mikeywith on October 17, 2020, 11:49:58 PM
[...]
I gave you merit for reporting back since a few people actually do that, so I just want you to know that your follow-up is appreciated. As for your problem, I sadly don't have much more to add to Favebook's comment, if returning the gear isn't an option, then all you left with is attempting to fix those boards, try applying some pressure on all the heatsinks, set the miner in a horizontal position, chances are slim to nothing but you lose nothing, whenever this happens to me, I say to myself "Hey, look at the bright side, I have a spare PSU and a control board". :D
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: wndsnb on October 19, 2020, 06:08:35 PM
Well, my S17 pro is back at the host but only going ~12 hours or so before requiring a reboot. I let it go 48 hours straight and then stress tested it by restricting cooling at home without any issues. Guessing the power at my host is a lot noisier than at my home and maybe that is pushing the marginal chips over the edge. Might have to come up with a way to inject noise into my power to replicate that at home.
So looks like I'm going to get this one back and take another crack at it.
If the major issue with these is just poorly attached heatsinks, I might have a way to quickly find them. I'm going to try heating each hashboard on a rework preheater (like this one (https://www.hakko.com/english/products/hakko_fr870b.html)) and use a thermal imager to look for heat sinks that rise in temperature slower than the rest. Might be able to find them just by feeling them with my fingertips, but the thermal imager will be able to very quickly detect even small differences.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: NotFuzzyWarm on October 19, 2020, 06:23:28 PM
Guessing the power at my host is a lot noisier than at my home and maybe that is pushing the marginal chips over the edge. Might have to come up with a way to inject noise into my power to replicate that at home...
Only way to SAFELY do that which I know of is by using a programmable AC power source such as these. https://www.chromausa.com/instruments/ac-power-sources/ or their older versions https://www.chromausa.com/product/programmable-ac-power-source-6400/. Und they are pricey.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: wndsnb on October 19, 2020, 06:51:47 PM
Hmm ... maybe I can convince my boss we need one at my work.
Here's a used 3KVA one on Ebay for $2650: https://www.ebay.com/itm/Agilent-HP-6814A-AC-Power-Source-Analyzer-300Vrms-3000VA/333455613990.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: NotFuzzyWarm on October 19, 2020, 07:20:25 PM
Do be aware that those and the ones from Chroma only provide variable voltage and frequency. For simulating 'dirty' power you need an impulse tester. NIST has a good paper on that (https://www.nist.gov/document/impulsetesterspdf) that includes schematics for DIY folks :D
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: danieleither on October 19, 2020, 07:35:52 PM
Perhaps I should not talk it up... but so far I have been very lucky with my Bitmain purchases.
I'm running:
21 x S19 95T
24 x S17e 60T
18 x T17+ 58T
2 x S17+ 70T
1 x S17+ 67T
All purchased between April and July 2020.
The 2 x S17+ 70T both failed within hours of running, I sent them back to Bitmain and they replaced within a few days - other than this no problems at all.
Also have 24 x Whatsminer M31S+ 82T, had one hashboard fail which was replaced under warranty.
I wonder if climate and humidity, or nature of setup have anything to do with some of the other failures here?
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: philipma1957 on October 19, 2020, 07:42:54 PM
Could be.
All my air is profiteered before it enters the cold aisle. < fuck spell check pre-filtered not profiteered
I don't over clock much (some s17pro's do turbo)
I suspect that clocking the s17pro past 65th = early death
I also suspect many clock over the safe limit.
My only poor 17 gear is 2x t17e and 2x t17+ all of which work well when down clocked.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: wndsnb on October 19, 2020, 08:00:51 PM
Do be aware that those and the ones from Chroma only provide variable voltage and frequency. For simulating 'dirty' power you need an impulse tester. NIST has a good paper on that (https://www.nist.gov/document/impulsetesterspdf) that includes schematics for DIY folks :D
The 6814A does say in its datasheet that it has programmable distortion, but it does that just by clipping the sinewave. It's probably just easier to drive the 5 hours to my host to test it out there anyway, gonna be hard to simulate a few thousand switching power supplies. Maybe I'll bring my oscilloscope next time I go and see what it actually looks like. Or maybe I'll just send them a filter to try.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: mikeywith on October 19, 2020, 08:50:46 PM
Guessing the power at my host is a lot noisier than at my home and maybe that is pushing the marginal chips over the edge. Might have to come up with a way to inject noise into my power to replicate that at home...
I don't know much about electricity, but if noise is the issue, won't that affect only the PSU itself and not the DC power that gets delivered to the hash boards? if I am wrong (very likely) then please correct me. Anyway, I think that the miner started to act funny because it was moved and driven for a few hours, my guess is that if you try it again at home, it will have the same problem. I'm going to try heating each hashboard on a rework preheater (like this one (https://www.hakko.com/english/products/hakko_fr870b.html)) and use a thermal imager to look for heat sinks that rise in temperature slower than the rest.
Sounds like a good idea to troubleshoot that, not sure if that will actually work if you are thinking about fixing a lot of miners it might be worth investing some $$ in buying the fixture tools from https://www.zeusbtc.com/Repair.asp.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: wndsnb on October 19, 2020, 09:17:46 PM
Noise on the input can lead to noise on the output.
I was thinking the same thing about being shaken around when the miner powered up for me immediately when I got it home. Maybe the trip back to my house will fix it again... hmm ... maybe I'll ask my host to whack it with a hammer a few times....
I also have a test fixture on order, but it may not detect an intermittent problem like this.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: danieleither on October 19, 2020, 09:18:36 PM
[...]
Oh, one other thing - my voltage here is superb. Usually around 245v, never seen it drop below 240v.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: mikeywith on October 20, 2020, 02:25:06 AM
Noise on the input can lead to noise on the output.
This makes sense. ... whack it with a hammer a few times.
Sounds like an easy fix ;D, this can also boost its hashrate. I also have a test fixture on order, but it may not detect an intermittent problem like this.
The tool shows you at which chip the signal was intersepted, the firmware that comes with it doesn't shut-down the hashboard even if a heatsink or a chip is loose, I think it will do what you need it to do, meanwhile, you can contact them on thier telegram/whatsapp to see what kind of issues does that tool fix and how does it actually work.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: Moeter81 on October 27, 2020, 04:59:23 AM
Has anyone experienced what a Bitmain repair costs?
If I add the verand, is it better to simply order 3 new hashboards?
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: favebook on October 27, 2020, 11:09:07 AM
Has anyone experienced what a Bitmain repair costs?
If I add the verand, is it better to simply order 3 new hashboards?
I did, I've posted it in multiple threads by now. My S17 Pro was RMA-ed twice, once in warranty period and once outside of it. Hashboards were dying both time. It cost me 60$ for repair and around 300$ for shipping from Serbia to Netherlands. Sometimes it's not just hashboards so it's hard to fix. But if you have good offer for hashboards, I'd try buying them.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: wndsnb on October 27, 2020, 01:14:08 PM
Depends a lot on how much you can get hashboards for. Just took a quick look on ebay and the only S17 hashboards I see are $390 each and come from China. Better off trying to find a used working S17. Kind of surprised there aren't more dead or partially working T17/S17s on ebay with all the reports of QC issues. Maybe they are all waiting their turn at Bitmain repair centers... I sent my S17 pro to the California center in May and I still don't have it back, although I got a notification that a replacement is on its way a few weeks ago.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: wndsnb on October 28, 2020, 01:08:19 PM
Started work on the 1st S17 from my host. 2 hashboards showing 0 chips. Turns out both of them have heatsinks that are misaligned enough to short to the adjacent row. https://i.imgur.com/fmRtdr5.png?1 (https://i.imgur.com/fmRtdr5.png) After moving this heatsink back into position, this board comes up and identifies all chips, but the test fixture is showing a couple of bad chips so it looks like I'll need to replace a few. The 2nd board is still not coming up after moving heatsinks back into position. Looks like an issue with the pic microcontroller on the board not enabling power so I ordered a pic ISD (pickit 4 (https://www.microchip.com/Developmenttools/ProductDetails/PG164140)) to investigate that further. Hoping that Bitmain did not set the read protection on the pic flash so I can read out the firmware to be able to program a replacement chip if necessary, but I'm thinking chances of that are close to 0. If not, it looks like zeusbtc sells a download for pic firmware for all Bitmain's miners. Also, just another thing I noticed with both these hashboards was that there were insect wings (looked like moth wings) blocking a few of the input side of the heatsinks. Could be what caused some chips to overheat enough for the heatsinks to slip. The solder holding the heatsinks on is low-temperature solder, so it will melt at under 150deg C.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: mikeywith on October 28, 2020, 02:22:14 PM
Your post is so good, I spent all my left merit on it. ;D Started work on the 1st S17 from my host. 2 hashboards showing 0 chips. Turns out both of them have heatsinks that are misaligned enough to short to the adjacent row.
After moving this heatsink back into position, this board comes up and identifies all chips, but the test fixture is showing a couple of bad chips so it looks like I'll need to replace a few.
Make sure you measure the voltage/resistance of the potential bad chips before replacing them, I have a reference for the voltage/resistance range but only for S9, so you will have to ask ZeusBtc for the reference, you do need the reference so if they don't have it, then get them from another working board, keep in mind that different regions of chips have different normal range, hard to tell which is which unless you can compare it against something else. Also, just another thing I noticed with both these hashboards was that there were insect wings (looked like moth wings) blocking a few of the input side of the heatsinks. Could be what caused some chips to overheat enough for the heatsinks to slip.
Not sure about the wings, but the majority of the boards I had on these 17 series gears were clean as brand new, on the other hand, some boards were pretty dirty and were hashing without an issue, these miners are badly built and that's all about it, even if the heatsink was blocked from dirt, it should be able to handle the max-safety-temp and the miner would shut-down before temps are higher than what that paste/solder can handle, but that isn't the case (sadly). Please keep us updated.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: Vezza on October 29, 2020, 11:29:57 AM
Hello, I just got a T17+ and it arrived with a damaged chip/sink and it won’t read the other chips. Any suggestions what I should do and if there is anyone that could help me change it?
Would it be smart to glue it with thermo adhesive cpu past in the mean time until i can change it? Would that help in any means?
Thank you.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: wndsnb on October 29, 2020, 12:19:42 PM
Would it be smart to glue it with thermo adhesive cpu past in the mean time until i can change it? Would that help in any means?
Heatsinks on these miners are not attached using adhesive. Instead, the heatsinks are soldered directly to the top of the chips with low-temperature melting point solder (138 deg C). Using thermal adhesive to attach the heat sink to the chip may work, but it might be extremely difficult or impossible to remove it once it's on. Zeusbtc has listings for independent repair centers on their website you could try contacting (bottom of this page https://www.zeusbtc.com/Repair.asp).
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: Vezza on October 29, 2020, 01:39:26 PM
Got ya thanks! I’ve sent them an email to.
Could anyone help me make a minimum requirement list for equipment needed for changing chips on boards. Would like to start trying it out since I a ton of s9 dead boards. Would prefer with equipment from Europe. Thank you!
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: wndsnb on October 29, 2020, 02:44:13 PM
S9s are a tough one at current difficulty and price... most likely better off tossing the broken ones and buying used replacements. I think you can get them for under $50 at this point. But if you want to start repairing other miners practicing on S9s is a good way to start.
At a minimum, you'll need a multimeter, adjustable heat gun, soldering iron, solder wick, solder wire, solder paste, tinning stencil. A test jig is very useful.
Best place to start is probably just doing an internet search for miner repair videos.
Also, let us know what the repair places tell you. Interested to know what they charge.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: favebook on October 29, 2020, 04:14:18 PM
Changing PSU did not help. A single board that sometimes had 0 chips instantly started hashing, while other two were not hashing like on old PSU but after a single restart it disappeared as well. 0 out of 65 chips read on all boards.
PSU that I put in now was new (ordered from Bitmain) and was tested on working unit, which means that it is not a problem. Control board cannot be the problem as I have tested it on working unit as well. Data cables I am yet to test but I doubt they are the problem.
I will quote this message in THIS THREAD (https://bitcointalk.org/index.php?topic=5217949.0) as that is where it might help people. I will provide pictures of a single hashboard which I think started the chain reaction of all boards going down.
Here are three photos of hashboard that first started making problems: https://imgur.com/a/ZhxhMsO Here is why I think this board is the reason my old PSU and other two hashboards are dead as well: https://i.imgur.com/Gjo7jud.jpg (https://i.imgur.com/Gjo7jud.jpg) My assumption is that it bricked the PSU which caused other hashboards to not work as well. I would like input from others about this assumption. Discoloration on one of chips (in middle of picture) means that it probably burnt. How or why I am not sure. What that one does I am also not sure. It's name is "copper_26". I'd appreciate if someone more tech-savy with Antminers could tell us what that chip is used for and why might it have burned? I am used to seeing heatsinks shorting hashboards or falling off, but I've never seen this chip get burned.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: wndsnb on October 29, 2020, 04:59:56 PM
My assumption is that it bricked the PSU which caused other hashboards to not work as well. I would like input from others about this assumption.
Discoloration on one of chips (in middle of picture) means that it probably burnt. How or why I am not sure. What that one does I am also not sure. It's name is "copper_26". I'd appreciate if someone more tech-savy with Antminers could tell us what that chip is used for and why might it have burned?
I don't think those are chips, I think it is literally just a piece of copper. Possibly used to increase the current capacity of the signal. Can't really tell from your photo if it is just oxidation or scorch marks.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: mikeywith on October 29, 2020, 05:11:52 PM
I think Wndsnb is correct, this doesn't seem anything like a chip or even a diode, it's just a 10*3mm piece of copper connected to "copper 27" as shown in the image: https://i.imgur.com/vd4UBDh.png (https://i.imgur.com/vd4UBDh.png) Here is the repair manual from Zeusbtc for S17+ https://drive.google.com/uc?id=1TfNMnpEFxEGMHbTr3lmy2-9Ry7XzlgP2&export=download , it has all the pinouts and details about how that hashboard actually works, perhabs someone who understands electronics well enough can help you further (I think NotfuzzyWarm is your guy). I am also interested to know what happened here, that piece does indeed look burnt/shorted, maybe too much current passed in there?
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: NotFuzzyWarm on October 29, 2020, 07:32:50 PM
I don't think those are chips, I think it is literally just a piece of copper. Possibly used to increase the current capacity of the signal. Can't really tell from your photo if it is just oxidation or scorch marks.
That is my guess as well - they are simply thick copper busbars soldered onto the power planes in the PCB in that area and are used to increase the current capacity of the power planes. The fact that they are located around where power comes in reinforces that idea. Only way to tell would be to check the resistance between some of them - if they are all soldered to the same power planes it should be very close to zero. While that suspect bar looks funky, to me it does not suggest overheating - more like simple oxidation and/or bad plating. Either way it should not affect their function and cause problems. Tip when checking low resistances: First press the meter probes together to establish the resistance of the meter leads. Most of the time it will be around 0.1 ohms. If the meter has a zeroing function, use it otherwise just subtract the meter lead resistance from what you measure across the bars to get the true value.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: favebook on October 29, 2020, 10:44:43 PM
I'll try to get better picture tomorrow, but it does look like a scorch mark to me. During the next week, I might bring it to my local electrician to check it. He might be able to tell me more. But until then, I am opening a RMA ticket to see if Netherlands repair shop has opened and when can I send it for repair. EDIT: I've made a "good" picture of copper plate in case and I am almost certain that it is not oxidation, but I will have to check with professional. I tried scratching it off with my nail but it doesn't budge. Ignore the discoloration on copper plates around the one in middle of picture. Does are due to light bouncing in weird ways as well as compression of google photos. Also, that brownish substance around copper is only dirt. There are no signs of scorch marks on PCB. https://i.imgur.com/Nqud3ee.jpg (https://i.imgur.com/Nqud3ee.jpg) Second not so good image (but it does show uncompressed color of copper plate) is here: https://imgur.com/a/cyzvv2k
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: wndsnb on October 31, 2020, 03:34:32 PM
Looks to me like just oxidation or staining, probably happened during the reflow during assembly or in a cleaning process after.
I think that copper plate is connected to the positive rail of the PSU input, it is there just to increase the current capacity of the connection between the + input and the FETs used to switch the main power to the asics on the board. The FETs are the 4 8-pin chips just below the copper piece (Q1, Q2, Q5, and Q6 in the schematic mikeywith posted). Those are pretty beefy FETs, but they would have gone up in smoke long before a bare copper plate would have heated up to the point of discoloration.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: favebook on October 31, 2020, 08:43:21 PM
You might be right, I could be very wrong. If you are right, then that would mean that there is a different problem and my initial thought was totally wrong. PSU might still have caused initial droppage of chips and I am nowhere near closer to narrowing down what is bad. I will just RMA it and let Bitmain decide what they did wrong.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: wndsnb on November 02, 2020, 02:44:08 PM
The 2nd board is still not coming up after moving heatsinks back into position. Looks like an issue with the pic microcontroller on the board not enabling power so I ordered a pic ISD (pickit 4 (https://www.microchip.com/Developmenttools/ProductDetails/PG164140)) to investigate that further. Hoping that Bitmain did not set the read protection on the pic flash so I can read out the firmware to be able to program a replacement chip if necessary, but I'm thinking chances of that are close to 0. If not, it looks like zeusbtc sells a download for pic firmware for all Bitmain's miners.
Well, the problem with this board was not the pic microcontroller. Turns out I was just not looking for its enable signal at the right time. The test jig I have only runs the board for about 1.5 seconds when it doesn't detect any ASICs, and I was measuring the pic outputs after the board had already powered down. I was able to connect to the pic with the pickit4 and read the pic firmware out of a known good board and use it to verify the firmware in the bad board. So it does not look like there is a need to buy a download... a little sketchy that Zuesbtc is trying to sell it when you can read it yourself with the tools needed to program the chip. I haven't actually programmed a chip with the firmware I read out, so maybe there is some issue with doing that that I'm not seeing. Or maybe some boards do have the read protection bit set and I got lucky.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: favebook on November 02, 2020, 04:24:14 PM
After careful and thorough examination of hashboards, I have found in addition to oxidised copper plate (thank you wndsnb for clarifying that), there was a heatsink which was misaligned in comparison to others see pictures below: https://i.imgur.com/CU4SHOd.jpg (https://i.imgur.com/CU4SHOd.jpg) https://i.imgur.com/ARddUCl.jpg (https://i.imgur.com/ARddUCl.jpg) Note that they were touching at top most part but with a gentle push of finger I made space between them in order to test if the hashboard will power on, but it was futile attempt. The bottom part of loose heatsink is around 0.2mm away from nearby one, but as top part was touching, there was probably a shortage there. Moving on, after the futile attempt at "fixing" it, I gently pushed the heatsink in case with my middle finger and this was the result: https://i.imgur.com/8Nayhat.jpg (https://i.imgur.com/8Nayhat.jpg) May that hashboard rest in peace. Now, I was thinking about 2 other hashboards that were working fine during the hottest day of summer (35C+ ambient) but as soon as ambient temperature dropped below 5C (few weeks ago) they started reading 0 out of 65 chips or 12 out of 65 chips (it warried from time to time). I figured maybe it had something to do with Thermodynamics law of expansion and contraction in hot and cold time respectively. So I took my Z11 (which is underclocked for better efficiency and therefore doesn't produce that much heat anyway) and placed it in front of my S17+ intake (picture below). And I was astonished by result. After first boot, both hashboards found all 65 out of 65 chips and started hashing away instantly. https://i.imgur.com/E9zXvyE.jpg (https://i.imgur.com/E9zXvyE.jpg) To further secure my unit to hash as much as possible and as long as possible, I updated to newest firmware which seems to fix the exact problem I have but I was unaware of this before I tested the method I noted above. 1. Enhance the working stability of the miner under special conditions (e.g. a certain range of low or high ambient temperature environment).
I hope this helps someone in future.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: wndsnb on November 02, 2020, 04:48:20 PM
Moving on, after the futile attempt at "fixing" it, I gently pushed the heatsink in case with my middle finger and this was the result:
https://i.imgur.com/8Nayhat.jpg
May that hashboard rest in peace.
That may not actually be as bad as it might look. If the solder snapped without taking part of the chip with it, then re-attaching the heatsink with a heat gun might fix it (probably very slim chance though). I think all of the shiny solder on the chip in your photo was not in contact with the heatsink, the part that snapped when you pushed on it would be the small dull section in the top left of the chip. Since only a small portion of the heatsink was actually making contact, it would have been overheating, so this would have probably caused issues and lines up with other suggestions that poorly attached heatsinks are a major problem with these miners. So maybe, if the chip didn't already overheat to the point of failure, just re-attaching the heatsink might do it.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: favebook on November 02, 2020, 05:46:31 PM
I have never done soldering before and the only experience with heat gun that I have was bending hard-line tubbing. I wouldn't dare to do that yet, I might buy broken S9s to learn how to do it on them but I would rather RMA this unit right now.
I could provide you a better and zoomed in pictures of chip and heatsink.
Solder snapped with heatsink for sure, the only thing that I could see on bottom of the heatsink was name (or part of it) of the chip, which might or might not indicate that it took a part of chip as well.
That chip group did have a problem with overheating now that you mention it, but never above 90C, it was usually in mid 80s and during winter in low 70s.
It is one of the last chips on the board if I remember right.
During my initial testing when I didn't even open the unit, that hashboard would at least pop up in voltage check. But now after loose heatsink it doesn't even show up in Kernel Log which is normal but it might mean that it is possible to save it, but as I said, I am not up to that challenge.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: NotFuzzyWarm on November 02, 2020, 06:29:52 PM
So instead of soldering, use a good epoxy thermal adhesive to reattach the heat sink... Assuming the chip itself was not damaged, should work just fine.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: favebook on November 02, 2020, 07:05:35 PM
So instead of soldering, use a good epoxy thermal adhesive to reattach the heat sink... Assuming the chip itself was not damaged, should work just fine.
Would you recommend any specific one? Preferable purchasable in Europe?
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: NotFuzzyWarm on November 02, 2020, 07:25:47 PM
Do a search for Arctic Silver or Arctic Alumina on your fav site. Key point is that it be a thermal epoxy so it holds the heat sink in place and is NOT just a thermal paste. Thermal pastes and stick-on thermal pads will not rigidly bond so things can move.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: favebook on November 02, 2020, 09:13:23 PM
Sadly there are no Arctic Silver or Alumina in my country. There are only epoxy resins in my country and they are used for something totally different. Looks like I will have to pull cords to get it from Germany/Italy or I will have to order from Amazon.
Thank you for your help tho. I will try it before RMA-ing the unit.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: mikeywith on November 03, 2020, 12:15:28 PM
Would you recommend any specific one? Preferable purchasable in Europe?
Read my topic (https://bitcointalk.org/index.php?topic=5264179.msg54858181#msg54858181), I had gone through a similar problem, I ended up ordering Arctic silver form this link https://www.amazon.com/dp/B0087X7262 for $17, now the price has gone up to $37 which is way too much, actually even $17 is a lot for 7g, if shipping from China is an option and doesn't take forever, then get the black glue from a place like ZeusBtc https://www.zeusbtc.com/RepairDetails.asp?ID=86, you can actually find it cheaper on Aliexpress (not sure if it's the same quality). If you end up ordering the "black glue" make sure whatever forwarder you use will be able to get it to you within 10 days, the guys at Zeusbtc told me that it can't be stored out of the fridge for more than 10 days.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: wndsnb on November 03, 2020, 02:58:19 PM
If using thermal adhesive, be aware that most some of them are electrically conductive. Be careful not to let any drip over the side of the chip which may short out circuits on the board.
edit: just looked up arctic silver and it looks like that one does not conduct.
edit #2: ... looks like NotFuzzyWarm beat me to it
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: NotFuzzyWarm on November 03, 2020, 03:20:06 PM
If using thermal adhesive, be aware that most of them are electrically conductive. Be careful not to let any drip over the side of the chip which may short out circuits on the board.
^^ Not necessarily. The Arctic Silver brand specifically state they are electrically non-conductive though do have a small capacitance value. Just make sure whatever you get states that it is electrically non-conductive. When using any thermal compound that is conductive one trick often done is to simply apply a thin line of RTV (silicone glue for electronics) over the IC pins to keep the thermal epoxy from touching them.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: wndsnb on November 09, 2020, 02:36:19 PM
I'm finding that the hashboard I'm troubleshooting that had 5 heatsinks shifted and shorting adjacent rows also has shifted chips. And on top of that, it looks like too much solder was used when the heatsinks were originally attached and some of it has migrated down and is now shorting pins on some of the chips. Looking like I'm going to have to take off more than half the heatsinks before I can get this one back up. https://i.imgur.com/wRc851d.png (https://i.imgur.com/wRc851d.png) Here's a thermal image of the board where you can see some of shifted chips in the upper left corner. Not really necessary, but a cool toy to play with. That is where all the shifted heat sinks were as well. This was taken when the test fixture was just querying the chips status to get an asic count, so no hashing yet. The photo is cool, but in this case, it was also easy enough to find those by just feeling the board. https://i.imgur.com/Xfu6L0M.png (https://i.imgur.com/Xfu6L0M.png)
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: Pendrak on November 10, 2020, 09:15:46 PM
What thermal paste they use for attach those heatsink?
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: wndsnb on November 10, 2020, 09:21:13 PM
They are attached with solder. This is what I am using: https://www.chipquik.com/store/product_info.php?products_id=470007
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: NotFuzzyWarm on November 10, 2020, 09:35:03 PM
As wndsnb said it is NOT thermal paste. Thermal paste does not mechanically bond things (heat sinks) to chips - it only fills gaps/voids between surfaces and relies on clips or other means to hold things together. Same applies to self-sticking thermal pads. Either solder or a thermal epoxy adhesive MUST be used or the heat sinks will eventually fall off.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: mikeywith on November 10, 2020, 10:20:27 PM
Thermal cooling adhesive like the one from Arctic (https://www.amazon.com/Arctic-Silver-Premium-Adhesive-ASTA-7G/dp/B0087X7262?th=1) will do the job as well, the cheapest would be the "black glue" from China, I am not sure if that's more of solder or thermal adhesive, but it works, and it's dirt cheap, I tried to look for an alternative in the local market but with no luck, I am not even sure how do people here go about fixing heatsinks of other electronic equipment or maybe I didn't know what "material" I should be asking for since the words "solder/adhesive" didn't ring the bell, they would show me thermal paste used for CPUs and be like "this should work". :-\
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: Vezza on November 11, 2020, 09:30:26 PM
nand: WARNING: pl35x-nand: the ECC used on your system is too weak compared to the one required by the NAND chip Does anyone know why I get this thing up?
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: Breeze on November 13, 2020, 03:10:16 PM
Hi guys
Which hashboard is hashboard 1 (chain 0)?
Closes to the PSU for example.
Maybe @mikeywith can help me? ;D
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: favebook on November 13, 2020, 04:43:30 PM
Hi guys
Which hashboard is hashboard 1 (chain 0)?
Closes to the PSU for example.
Maybe @mikeywith can help me? ;D
Physical location does not matter. Check data connection cables. IIRC order is: 0 3 1 2 They are marked on control board, you will have no trouble finding this out by yourself. If you have troubles, then send a picture of control board, and I will circle it for you.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: Breeze on November 13, 2020, 04:52:19 PM
Now when i checked carefully with a flashlight, i saw J1, J2 and J3 on the control board. That should be it? Thanks.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: favebook on November 13, 2020, 05:12:04 PM
Depends on what unit we are talking about. J1, J2 and J3 were used on old S9 model as far as I know. I didn't see them on any of S/T 17 miners.
Can you provide more info about your unit and your problem?
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: mikeywith on November 13, 2020, 05:46:39 PM
Usually, the label on the control board will be represented in the kernel log, in case that is not the case, then the ordering is ascending, so your chain 0 will be J1, the labels are quite visible on the control board, you just need to follow the ribbon cable to see which hash board goes to which socket.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: Breeze on November 13, 2020, 06:02:43 PM
Depends on what unit we are talking about. J1, J2 and J3 were used on old S9 model as far as I know. I didn't see them on any of S/T 17 miners.
Can you provide more info about your unit and your problem?
S17 Pro. It's very hard to see on S17 control board. You can see J1, then you have to look with a flashlight between the tight cable connection to see J2 and J3. Chain 0 dropped out. Tried all the tricks on this thread to get it working. So decided to open it up and take a look on my heatsinks. Usually, the label on the control board will be represented in the kernel log, in case that is not the case, then the ordering is ascending, so your chain 0 will be J1, the labels are quite visible on the control board, you just need to follow the ribbon cable to see which hash board goes to which socket.
Thanks. Wanted it to clarify it.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: CryptoLLC on November 22, 2020, 09:41:05 PM
Turns out my host has about 25 dead S17 pros, not sure what % of his total that is. We've struck a deal so I'm going to attempt to fix his dead miners, I'll update the thread on what I find.
Did you figure out a way to find the bad chip? I have about 20 boards from S17+ 73th and all the boards have error temp sensor and then they show 0 asic found. I dont know how to find the bad chip? Which chip do I need to check the solder on?
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: wndsnb on November 22, 2020, 10:16:16 PM
This is a good place to start: https://www.zeusbtc.com/NewsDetails.asp?ID=182
There is a download link on the page for the full repair manual, but it is in Chinese. You can load it into google translate to get a somewhat understandable translation.
If you want to try to fix them yourself, then you'll need a test fixture, a multimeter, adjustable heat gun, soldiering iron, ...etc. An oscilloscope is also helpful. I wouldn't recommend it unless you already have a background in electronics and have some experience doing surface mount rework.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: CryptoLLC on November 22, 2020, 10:29:46 PM
I have this error for all my bad boards. I have 20+ bad boards. S17+ 73th.
read temp sensor failed
After some time the board shows 0 asic found.
After doing a lot of research the problems seems to be bad contact between the heat sink and the chip.
So my question is how do I find that bad contact? I tryed tapping on the heatsinks lightly to see if any heat sinks will come off. I tryed banging the board lightly to get some heat sinks to come off. But all the heat sinks are still on. I have all the tools to fix the problem. Solder, heat gun, tin, watt meter, oscilloscope, psu, extra chips and so on. I just dont know which chip is at fault. What are the ways to find that bad connection? Thank you.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: mikeywith on November 22, 2020, 11:17:49 PM
I have all the tools to fix the problem. Solder, heat gun, tin, watt meter, oscilloscope, psu, extra chips and so on. I just dont know which chip is at fault. What are the ways to find that bad connection? Thank you.
You will need a fixture tool like this one (https://www.zeusbtc.com/RepairDetails.asp?ID=212), what does tool does is tell you where was the signal interrupted, and then to double-check you could measure the voltage and/or resistance of that chip, keep in mind that in the event of all 3 hash boards throwing that temp-sensor error then the problem is most likely a bad PSU.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: CryptoLLC on November 22, 2020, 11:50:43 PM
I have that test fixture. It tells me that all temp sensors are bad. Also Im testing one board at a time. Im using a brand new psu for testing. How do I test the voltage and resistance of the chip? Also where do I start at? Chip 1 or somewhere else. I have no idea what chip to start at since none of the heat sinks came loose. Is there a quick way to test each chip? Im 100% the problem has to be that a heat sink is not fully on. All I need is to find it and I have all the tools to re seat it back on.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: wndsnb on November 23, 2020, 12:24:23 AM
Can you post the log from the test fixture run showing the bad temp sensors?
If the issue is only a poorly connected heat sink, then it would only fail when the chip overheats. Going to be hard to find that.
You might try feeling the temperature of the individual heat sinks right after it fails to see if a heatsink is warmer or cooler than the rest.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: CryptoLLC on November 23, 2020, 12:30:49 AM
Here here is the log from the test fixture.
http://servervideos.hopto.org/error.jpg (http://servervideos.hopto.org/error.jpg)
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: mikeywith on November 23, 2020, 05:20:14 PM
Here here is the log from the test fixture.
http://servervideos.hopto.org/error.jpg (http://servervideos.hopto.org/error.jpg)
I am not familiar with the fixture tool but looks like it is telling you that chip no 50 is bad, no? Anyway you should contact zeusbtc and ask for the voltage reference range, each domain (group of chips) has its own normal voltage values, you just need a volt-meter and the reference table.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: CryptoLLC on November 23, 2020, 08:46:50 PM
Another question I have is on some of my other boards when I take off a heat sink there seems to be very little solder on the heat sink. Looks like at manufacturing they did not apply enough solder. I want to add more solder to the heat sink and put it back on the chip. What do I use for this? Also how do I do this? I have low temp solder paste but is there a procedure to add more solder to the heat sink? Maybe some flux or some other chemical? I tried adding flux and then put some low temp solder paste but it does not stick to the heat sink edges where the solder is missing. The solder paste just melts off and connected to the solder that is already there. It does not stick to the heat sink edges where the solder is missing. How can I make it stick? Thank you.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: mikeywith on November 23, 2020, 09:39:57 PM
You can use something like https://www.amazon.com/Arctic-Silver-Premium-Adhesive-ASTA-7G/dp/B0087X7262, or use the black glue (https://www.zeusbtc.com/RepairDetails.asp?ID=86) from the same website you got the tool, adding more solder to the existing isn't a good idea, you should clean the chip's surface and then start fresh, ensure that the amount of solder paste is equally even across the whole chip.
Watch this video https://youtu.be/5WH7g61d90w, it's helpful.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: CryptoLLC on November 23, 2020, 09:49:50 PM
So you put the thermal solder on the chip? Do I need to put anything on the heat sink such as flux or something else?
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: mikeywith on November 23, 2020, 11:01:35 PM
I am not really an expert in this field, but why would you use flux? it's not like you are soldering the chip on the hash board, maybe you could use flux to clean the heatsink before gluing it on the chip but I don't think you need to put anything else besides the thermal adhesive, by the way, here is a slightly different way of doing it > https://www.youtube.com/watch?v=378FPjkHQJc.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: CryptoLLC on November 24, 2020, 04:44:23 AM
I wouldnt want to use any permeneatny adhesive. Im looking to apply solder. What solder do you know I can use for this that can be taken off and on. Also I have a whole bunch of boards that have the same exact errors when I run the test fixture. All the asic are found but I still get a temp sensor error. 1970-01-01 00:00:52 main.c:45:main: Ready for test
1970-01-01 00:00:59 single_board_test.c:2336:get_eeprom_info: get EEPROM info success!
1970-01-01 00:00:59 single_board_test.c:2585:single_board_test: g_test_level 7, pattern_test_time 1
1970-01-01 00:00:59 single_board_test.c:2375:do_single_board_test: Begin test
1970-01-01 00:00:59 fan.c:276:front_fan_power_on: Note: front fan is power on!
1970-01-01 00:00:59 fan.c:288:rear_fan_power_on: Note: rear fan is power on!
1970-01-01 00:00:59 driver-btm-api.c:1165:miner_device_init: Detect 256MB control board of XILINX
1970-01-01 00:00:59 driver-btm-api.c:1106:init_fan_parameter: fan_eft : 0 fan_pwm : 0
1970-01-01 00:01:05 driver-btm-api.c:1090:init_miner_version: miner ID : 805445801c20881c
1970-01-01 00:01:05 driver-btm-api.c:1096:init_miner_version: FPGA Version = 0xB031
1970-01-01 00:01:06 board.c:36:jump_and_app_check_restore_pic: chain[0] PIC jump to app
1970-01-01 00:01:08 board.c:40:jump_and_app_check_restore_pic: Check chain[0] PIC fw version=0x88
1970-01-01 00:01:08 thread.c:807:create_pic_heart_beat_thread: create thread
1970-01-01 00:01:12 power_api.c:228:set_higher_voltage_raw: higher_voltage_raw = 2100
1970-01-01 00:01:12 power_api.c:278:set_to_higher_voltage: Set to voltage raw 2100, one step.
1970-01-01 00:01:14 power_api.c:85:check_voltage_multi: retry time: 0
1970-01-01 00:01:15 power_api.c:40:_get_avg_voltage: chain = 0, voltage = 20.926828
1970-01-01 00:01:15 power_api.c:53:_get_avg_voltage: average_voltage = 20.926828
1970-01-01 00:01:15 power_api.c:71:check_voltage: target_vol = 21.00, actural_vol = 20.93, check voltage passed.
1970-01-01 00:01:15 uart.c:71:set_baud: set fpga_baud to 115200
1970-01-01 00:01:15 driver-hash-chip.c:245:dhash_chip_set_baud_v2: chain[0]: chip baud = 115200, chip_divider = 26
1970-01-01 00:01:26 driver-btm-api.c:1030:check_asic_number_with_power_on: Chain[0]: find 65 asic, times 0
1970-01-01 00:01:29 driver-hash-chip.c:266:set_uart_relay: set uart relay to 0x330003
1970-01-01 00:01:29 driver-btm-api.c:363:set_order_clock: chain[0]: set order clock, stragegy 3
1970-01-01 00:01:29 driver-hash-chip.c:502:set_clock_delay_control: core_data = 0x34
1970-01-01 00:01:29 driver-hash-chip.c:502:set_clock_delay_control: core_data = 0x34
1970-01-01 00:01:29 driver-hash-chip.c:517:set_clock_delay_control: singe chain mode
1970-01-01 00:01:30 temperature.c:320:calibrate_temp_sensor_one_chain: chain 0 temp sensor NCT218
1970-01-01 00:01:31 temperature.c:488:temp_statistics_show: pcb temp 17~20 chip temp 18~20
1970-01-01 00:01:31 uart.c:71:set_baud: set fpga_baud to 12000000
1970-01-01 00:01:31 driver-hash-chip.c:245:dhash_chip_set_baud_v2: chain[0]: chip baud = 12000000, chip_divider = 3
1970-01-01 00:01:31 temperature.c:488:temp_statistics_show: pcb temp 18~19 chip temp 19~21
1970-01-01 00:01:31 power_api.c:222:set_working_voltage_raw: working_voltage_raw = 1950
1970-01-01 00:01:31 frequency.c:808:inc_freq_with_fixed_vco: chain = 255, freq = 625, is_higher_voltage = true
1970-01-01 00:01:42 power_api.c:348:set_to_voltage_by_steps: Set to voltage raw 2070, step by step.
1970-01-01 00:01:44 power_api.c:85:check_voltage_multi: retry time: 0
1970-01-01 00:01:45 power_api.c:40:_get_avg_voltage: chain = 0, voltage = 20.217949
1970-01-01 00:01:45 power_api.c:53:_get_avg_voltage: average_voltage = 20.217949
1970-01-01 00:01:45 power_api.c:71:check_voltage: target_vol = 20.70, actural_vol = 20.22, check voltage passed.
1970-01-01 00:01:45 driver-btm-api.c:666:set_timeout: freq = 625, percent = 10, hcn = 4915, timeout = 7
1970-01-01 00:01:45 power_api.c:306:set_to_working_voltage_by_steps: Set to voltage raw 1950, step by step.
1970-01-01 00:01:50 power_api.c:85:check_voltage_multi: retry time: 0
1970-01-01 00:01:52 power_api.c:40:_get_avg_voltage: chain = 0, voltage = 19.097436
1970-01-01 00:01:52 power_api.c:53:_get_avg_voltage: average_voltage = 19.097436
1970-01-01 00:01:52 power_api.c:71:check_voltage: target_vol = 19.50, actural_vol = 19.10, check voltage passed.
1970-01-01 00:01:52 register.c:185:read_asic_reg_with_addr: read asic reg timeout: expect chain = 0, chip = 14, reg = 28
1970-01-01 00:01:52 register.c:185:read_asic_reg_with_addr: read asic reg timeout: expect chain = 0, chip = 14, reg = 28
1970-01-01 00:01:52 register.c:185:read_asic_reg_with_addr: read asic reg timeout: expect chain = 0, chip = 14, reg = 28
1970-01-01 00:01:52 register.c:185:read_asic_reg_with_addr: read asic reg timeout: expect chain = 0, chip = 14, reg = 28
1970-01-01 00:01:52 register.c:185:read_asic_reg_with_addr: read asic reg timeout: expect chain = 0, chip = 14, reg = 28
1970-01-01 00:01:52 register.c:185:read_asic_reg_with_addr: read asic reg timeout: expect chain = 0, chip = 14, reg = 28
1970-01-01 00:01:52 register.c:185:read_asic_reg_with_addr: read asic reg timeout: expect chain = 0, chip = 14, reg = 28
1970-01-01 00:01:52 register.c:185:read_asic_reg_with_addr: read asic reg timeout: expect chain = 0, chip = 14, reg = 28
1970-01-01 00:01:52 temperature.c:744:get_temp_info: read temp sensor failed: chain = 0, sensor = 0, chip = 14, reg = 0
1970-01-01 00:01:52 register.c:185:read_asic_reg_with_addr: read asic reg timeout: expect chain = 0, chip = 14, reg = 28
1970-01-01 00:01:52 register.c:185:read_asic_reg_with_addr: read asic reg timeout: expect chain = 0, chip = 14, reg = 28
1970-01-01 00:01:52 register.c:185:read_asic_reg_with_addr: read asic reg timeout: expect chain = 0, chip = 14, reg = 28
1970-01-01 00:01:52 register.c:185:read_asic_reg_with_addr: read asic reg timeout: expect chain = 0, chip = 14, reg = 28
1970-01-01 00:01:52 register.c:185:read_asic_reg_with_addr: read asic reg timeout: expect chain = 0, chip = 14, reg = 28
1970-01-01 00:01:52 register.c:185:read_asic_reg_with_addr: read asic reg timeout: expect chain = 0, chip = 14, reg = 28
1970-01-01 00:01:52 register.c:185:read_asic_reg_with_addr: read asic reg timeout: expect chain = 0, chip = 14, reg = 28
1970-01-01 00:01:52 register.c:185:read_asic_reg_with_addr: read asic reg timeout: expect chain = 0, chip = 14, reg = 28
1970-01-01 00:01:52 register.c:185:read_asic_reg_with_addr: read asic reg timeout: expect chain = 0, chip = 14, reg = 28
1970-01-01 00:01:52 register.c:185:read_asic_reg_with_addr: read asic reg timeout: expect chain = 0, chip = 14, reg = 28
1970-01-01 00:01:52 register.c:185:read_asic_reg_with_addr: read asic reg timeout: expect chain = 0, chip = 14, reg = 28
1970-01-01 00:01:52 register.c:185:read_asic_reg_with_addr: read asic reg timeout: expect chain = 0, chip = 14, reg = 28
1970-01-01 00:01:53 register.c:185:read_asic_reg_with_addr: read asic reg timeout: expect chain = 0, chip = 14, reg = 28
1970-01-01 00:01:53 register.c:185:read_asic_reg_with_addr: read asic reg timeout: expect chain = 0, chip = 14, reg = 28
1970-01-01 00:01:53 register.c:185:read_asic_reg_with_addr: read asic reg timeout: expect chain = 0, chip = 14, reg = 28
1970-01-01 00:01:53 register.c:185:read_asic_reg_with_addr: read asic reg timeout: expect chain = 0, chip = 14, reg = 28
1970-01-01 00:01:53 temperature.c:744:get_temp_info: read temp sensor failed: chain = 0, sensor = 0, chip = 14, reg = 1
1970-01-01 00:01:53 register.c:185:read_asic_reg_with_addr: read asic reg timeout: expect chain = 0, chip = 10, reg = 28
1970-01-01 00:01:53 register.c:185:read_asic_reg_with_addr: read asic reg timeout: expect chain = 0, chip = 10, reg = 28
1970-01-01 00:01:53 register.c:185:read_asic_reg_with_addr: read asic reg timeout: expect chain = 0, chip = 10, reg = 28
1970-01-01 00:01:53 register.c:185:read_asic_reg_with_addr: read asic reg timeout: expect chain = 0, chip = 10, reg = 28
1970-01-01 00:01:53 register.c:185:read_asic_reg_with_addr: read asic reg timeout: expect chain = 0, chip = 10, reg = 28
1970-01-01 00:01:53 register.c:185:read_asic_reg_with_addr: read asic reg timeout: expect chain = 0, chip = 10, reg = 28
1970-01-01 00:01:53 register.c:185:read_asic_reg_with_addr: read asic reg timeout: expect chain = 0, chip = 10, reg = 28
1970-01-01 00:01:53 register.c:185:read_asic_reg_with_addr: read asic reg timeout: expect chain = 0, chip = 10, reg = 28
1970-01-01 00:01:53 temperature.c:744:get_temp_info: read temp sensor failed: chain = 0, sensor = 1, chip = 10, reg = 0
1970-01-01 00:01:53 register.c:185:read_asic_reg_with_addr: read asic reg timeout: expect chain = 0, chip = 10, reg = 28
1970-01-01 00:01:53 register.c:185:read_asic_reg_with_addr: read asic reg timeout: expect chain = 0, chip = 10, reg = 28
1970-01-01 00:01:53 register.c:185:read_asic_reg_with_addr: read asic reg timeout: expect chain = 0, chip = 10, reg = 28
1970-01-01 00:01:53 register.c:185:read_asic_reg_with_addr: read asic reg timeout: expect chain = 0, chip = 10, reg = 28
1970-01-01 00:01:53 register.c:185:read_asic_reg_with_addr: read asic reg timeout: expect chain = 0, chip = 10, reg = 28
1970-01-01 00:01:53 register.c:185:read_asic_reg_with_addr: read asic reg timeout: expect chain = 0, chip = 10, reg = 28
1970-01-01 00:01:53 register.c:185:read_asic_reg_with_addr: read asic reg timeout: expect chain = 0, chip = 10, reg = 28
1970-01-01 00:01:53 register.c:185:read_asic_reg_with_addr: read asic reg timeout: expect chain = 0, chip = 10, reg = 28
1970-01-01 00:01:53 register.c:185:read_asic_reg_with_addr: read asic reg timeout: expect chain = 0, chip = 10, reg = 28
1970-01-01 00:01:53 register.c:185:read_asic_reg_with_addr: read asic reg timeout: expect chain = 0, chip = 10, reg = 28
1970-01-01 00:01:53 register.c:185:read_asic_reg_with_addr: read asic reg timeout: expect chain = 0, chip = 10, reg = 28
1970-01-01 00:01:54 register.c:185:read_asic_reg_with_addr: read asic reg timeout: expect chain = 0, chip = 10, reg = 28
1970-01-01 00:01:54 register.c:185:read_asic_reg_with_addr: read asic reg timeout: expect chain = 0, chip = 10, reg = 28
1970-01-01 00:01:54 register.c:185:read_asic_reg_with_addr: read asic reg timeout: expect chain = 0, chip = 10, reg = 28
1970-01-01 00:01:54 register.c:185:read_asic_reg_with_addr: read asic reg timeout: expect chain = 0, chip = 10, reg = 28
1970-01-01 00:01:54 register.c:185:read_asic_reg_with_addr: read asic reg timeout: expect chain = 0, chip = 10, reg = 28
1970-01-01 00:01:54 temperature.c:744:get_temp_info: read temp sensor failed: chain = 0, sensor = 1, chip = 10, reg = 1
1970-01-01 00:01:54 register.c:185:read_asic_reg_with_addr: read asic reg timeout: expect chain = 0, chip = 54, reg = 28
1970-01-01 00:01:54 register.c:185:read_asic_reg_with_addr: read asic reg timeout: expect chain = 0, chip = 54, reg = 28
1970-01-01 00:01:54 register.c:185:read_asic_reg_with_addr: read asic reg timeout: expect chain = 0, chip = 54, reg = 28
1970-01-01 00:01:54 register.c:185:read_asic_reg_with_addr: read asic reg timeout: expect chain = 0, chip = 54, reg = 28
1970-01-01 00:01:54 register.c:185:read_asic_reg_with_addr: read asic reg timeout: expect chain = 0, chip = 54, reg = 28
1970-01-01 00:01:54 register.c:185:read_asic_reg_with_addr: read asic reg timeout: expect chain = 0, chip = 54, reg = 28
1970-01-01 00:01:54 register.c:185:read_asic_reg_with_addr: read asic reg timeout: expect chain = 0, chip = 54, reg = 28
1970-01-01 00:01:54 register.c:185:read_asic_reg_with_addr: read asic reg timeout: expect chain = 0, chip = 54, reg = 28
1970-01-01 00:01:54 temperature.c:744:get_temp_info: read temp sensor failed: chain = 0, sensor = 2, chip = 54, reg = 0
1970-01-01 00:01:54 register.c:185:read_asic_reg_with_addr: read asic reg timeout: expect chain = 0, chip = 54, reg = 28
1970-01-01 00:01:54 register.c:185:read_asic_reg_with_addr: read asic reg timeout: expect chain = 0, chip = 54, reg = 28
1970-01-01 00:01:54 register.c:185:read_asic_reg_with_addr: read asic reg timeout: expect chain = 0, chip = 54, reg = 28
1970-01-01 00:01:54 register.c:185:read_asic_reg_with_addr: read asic reg timeout: expect chain = 0, chip = 54, reg = 28
1970-01-01 00:01:54 register.c:185:read_asic_reg_with_addr: read asic reg timeout: expect chain = 0, chip = 54, reg = 28
1970-01-01 00:01:54 register.c:185:read_asic_reg_with_addr: read asic reg timeout: expect chain = 0, chip = 54, reg = 28
1970-01-01 00:01:54 register.c:185:read_asic_reg_with_addr: read asic reg timeout: expect chain = 0, chip = 54, reg = 28
1970-01-01 00:01:54 register.c:185:read_asic_reg_with_addr: read asic reg timeout: expect chain = 0, chip = 54, reg = 28
1970-01-01 00:01:54 register.c:185:read_asic_reg_with_addr: read asic reg timeout: expect chain = 0, chip = 54, reg = 28
1970-01-01 00:01:55 register.c:185:read_asic_reg_with_addr: read asic reg timeout: expect chain = 0, chip = 54, reg = 28
1970-01-01 00:01:55 register.c:185:read_asic_reg_with_addr: read asic reg timeout: expect chain = 0, chip = 54, reg = 28
1970-01-01 00:01:55 register.c:185:read_asic_reg_with_addr: read asic reg timeout: expect chain = 0, chip = 54, reg = 28
1970-01-01 00:01:55 register.c:185:read_asic_reg_with_addr: read asic reg timeout: expect chain = 0, chip = 54, reg = 28
1970-01-01 00:01:55 register.c:185:read_asic_reg_with_addr: read asic reg timeout: expect chain = 0, chip = 54, reg = 28
1970-01-01 00:01:55 register.c:185:read_asic_reg_with_addr: read asic reg timeout: expect chain = 0, chip = 54, reg = 28
1970-01-01 00:01:55 register.c:185:read_asic_reg_with_addr: read asic reg timeout: expect chain = 0, chip = 54, reg = 28
1970-01-01 00:01:55 temperature.c:744:get_temp_info: read temp sensor failed: chain = 0, sensor = 2, chip = 54, reg = 1
1970-01-01 00:01:55 register.c:185:read_asic_reg_with_addr: read asic reg timeout: expect chain = 0, chip = 50, reg = 28
1970-01-01 00:01:55 register.c:185:read_asic_reg_with_addr: read asic reg timeout: expect chain = 0, chip = 50, reg = 28
1970-01-01 00:01:55 register.c:185:read_asic_reg_with_addr: read asic reg timeout: expect chain = 0, chip = 50, reg = 28
1970-01-01 00:01:55 register.c:185:read_asic_reg_with_addr: read asic reg timeout: expect chain = 0, chip = 50, reg = 28
1970-01-01 00:01:55 register.c:185:read_asic_reg_with_addr: read asic reg timeout: expect chain = 0, chip = 50, reg = 28
1970-01-01 00:01:55 register.c:185:read_asic_reg_with_addr: read asic reg timeout: expect chain = 0, chip = 50, reg = 28
1970-01-01 00:01:55 register.c:185:read_asic_reg_with_addr: read asic reg timeout: expect chain = 0, chip = 50, reg = 28
1970-01-01 00:01:55 register.c:185:read_asic_reg_with_addr: read asic reg timeout: expect chain = 0, chip = 50, reg = 28
1970-01-01 00:01:55 temperature.c:744:get_temp_info: read temp sensor failed: chain = 0, sensor = 3, chip = 50, reg = 0
1970-01-01 00:01:55 register.c:185:read_asic_reg_with_addr: read asic reg timeout: expect chain = 0, chip = 50, reg = 28
1970-01-01 00:01:55 register.c:185:read_asic_reg_with_addr: read asic reg timeout: expect chain = 0, chip = 50, reg = 28
1970-01-01 00:01:55 register.c:185:read_asic_reg_with_addr: read asic reg timeout: expect chain = 0, chip = 50, reg = 28
1970-01-01 00:01:55 register.c:185:read_asic_reg_with_addr: read asic reg timeout: expect chain = 0, chip = 50, reg = 28
1970-01-01 00:01:55 register.c:185:read_asic_reg_with_addr: read asic reg timeout: expect chain = 0, chip = 50, reg = 28
1970-01-01 00:01:55 register.c:185:read_asic_reg_with_addr: read asic reg timeout: expect chain = 0, chip = 50, reg = 28
1970-01-01 00:01:55 register.c:185:read_asic_reg_with_addr: read asic reg timeout: expect chain = 0, chip = 50, reg = 28
1970-01-01 00:01:55 register.c:185:read_asic_reg_with_addr: read asic reg timeout: expect chain = 0, chip = 50, reg = 28
1970-01-01 00:01:56 register.c:185:read_asic_reg_with_addr: read asic reg timeout: expect chain = 0, chip = 50, reg = 28
1970-01-01 00:01:56 register.c:185:read_asic_reg_with_addr: read asic reg timeout: expect chain = 0, chip = 50, reg = 28
1970-01-01 00:01:56 register.c:185:read_asic_reg_with_addr: read asic reg timeout: expect chain = 0, chip = 50, reg = 28
1970-01-01 00:01:56 register.c:185:read_asic_reg_with_addr: read asic reg timeout: expect chain = 0, chip = 50, reg = 28
1970-01-01 00:01:56 register.c:185:read_asic_reg_with_addr: read asic reg timeout: expect chain = 0, chip = 50, reg = 28
1970-01-01 00:01:56 register.c:185:read_asic_reg_with_addr: read asic reg timeout: expect chain = 0, chip = 50, reg = 28
1970-01-01 00:01:56 register.c:185:read_asic_reg_with_addr: read asic reg timeout: expect chain = 0, chip = 50, reg = 28
1970-01-01 00:01:56 register.c:185:read_asic_reg_with_addr: read asic reg timeout: expect chain = 0, chip = 50, reg = 28
1970-01-01 00:01:56 temperature.c:744:get_temp_info: read temp sensor failed: chain = 0, sensor = 3, chip = 50, reg = 1
1970-01-01 00:01:56 single_board_test.c:1659:wait_warm_up: temper sensor bad
I have this same exact error for over 10 boards. Also the the error states chip 50, 54, 10, 14 as being bad chips but I get this same exact error on many boards. Cant all have the same exact chips with the same exact error. What could this be? My boards are in 100% perfect condition and all the sudden stopped working one day. Showed temp sensor errors and then stopped working completely. Running this test fixture is showing temo sensor is bad but that cant be either. Something is wrong and I dont know how to find the problem. Please advise. Thank you.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: mikeywith on November 24, 2020, 10:06:31 AM
Nothing is permanent, that arctic adhesive won't hold against a hammer or a heat gun direct to that heatsink, the same thing applies to any other solder you might use. What matters in your kernel log is only these 4 lines: 1970-01-01 00:01:52 temperature.c:744:get_temp_info: read temp sensor failed: chain = 0, sensor = 0, chip = 14, reg = 0
1970-01-01 00:01:54 temperature.c:744:get_temp_info: read temp sensor failed: chain = 0, sensor = 1, chip = 10, reg = 1
1970-01-01 00:01:54 temperature.c:744:get_temp_info: read temp sensor failed: chain = 0, sensor = 2, chip = 54, reg = 0
1970-01-01 00:01:55 temperature.c:744:get_temp_info: read temp sensor failed: chain = 0, sensor = 3, chip = 50, reg = 0
The kernel log can be a bit confusing, it isn't saying that those 4 chips are bad, it's only trying to tell you that the temp sensor next to those 4 chips is bad, each board has temp sensors located near the chips mentioned 10,14,50 and 54 something like this: https://support.bitmain.com/hc/user_images/KOxgKWB0nf0QDY_1EADsng.jpeg (https://support.bitmain.com/hc/user_images/KOxgKWB0nf0QDY_1EADsng.jpeg) But this isn't even accurate either, because it's unlikely that 4 temp sensors would die, and the real actual cause must be one of two. 1- If all temp sensors across 3 hash boards (total of 12 temp sensors) show "failed" then the problem is the PSU 2- If one hash boards temp sensors show "failed" then one or more heatsink/chip isn't in 100% contact and needs replacement, and more often than not the first chip (chip 0) is the bad one notice that, the PSU theory still stands even if 1 hash board is having a hard time reading the temp sensor, it's hard to explain but take it as is.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: CryptoLLC on November 24, 2020, 08:23:56 PM
I spent all night playing with the boards. So here is a some what of a fix. The fixture is not accurate at all. I put these same boards into my miner and put asic.to or bitmain firmware on it and ran it as is. I worked!!! It looks like the test fixture is showing that temp sensors are bad but that's not true. They are good. I would double check the chips to have their volts in order. Such as clock and RO, also check the rest as well but clock and ro are good way to find a bad chip. Anyway I found some chips that have solder balls next to it. Remove those balls. Once the chips all have good volts run asic.to firmware and it should work. The test fixture is lying. lol. Dont believe it. I fixed 6 boards last night once I stopped believing the test fixture. They are sill working as of this morning. I will update you when I fix more boards.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: mikeywith on November 24, 2020, 11:38:31 PM
I wouldn't say the fixture is lying, it is doing its job, which can't be perfect all the time, I suppose the solder balls you found around the chip came from "overdosing" by bitmain staff/robots, after being put under heat that extra solder has to go somewhere when it goes outside of where it has to be it will short the hash board, it probably does something to the component that reads the temp-sensor and that could explain why both the fixture tool and the miner kernel log mention the temp-sensor when sensors are actually good, and since temp-sensors are essentials the miner won't start thinking that all 4 sensors are bad, these are some terrible quality gears.
I am glad you managed to fix some of the hash boards, it would have been a lot better if you could take some photos, also share how did you manage to remove that solder without damaging anything else.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: CryptoLLC on November 25, 2020, 07:52:56 AM
I will share all the info soon. I have a youtube channel. I will post a link soon.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: mikxxy on November 25, 2020, 02:18:15 PM
An AntminerT17+ been running perfect for some months suddenly and after some power cuts, did not restart. Flashed it with Awesom FW and getting this in kernel log, is all boards dead or just the hashboard? Thanks Mike. [2020/11/25 14:09:25] INFO: Power ON
[2020/11/25 14:09:27] INFO: Starting FPGA queue
[2020/11/25 14:09:27] INFO: Initializing hash boards
[2020/11/25 14:09:27] INFO: chain[2] - Initializing
[2020/11/25 14:09:27] INFO: chain[1] - Initializing
[2020/11/25 14:09:27] INFO: chain[0] - Initializing
[2020/11/25 14:09:43] WARN: chain[2] - 44 of 65 chips detected
[2020/11/25 14:09:46] WARN: chain[1] - 44 of 65 chips detected
[2020/11/25 14:09:49] WARN: chain[0] - 44 of 65 chips detected
[2020/11/25 14:09:54] WARN: chain[2] - 44 of 65 chips detected
[2020/11/25 14:09:57] WARN: chain[1] - 44 of 65 chips detected
[2020/11/25 14:10:00] WARN: chain[0] - 44 of 65 chips detected
[2020/11/25 14:10:06] WARN: chain[2] - 44 of 65 chips detected
[2020/11/25 14:10:06] ERROR: driver-btm-chain.c:488 chain[2] - Failed to detect ASIC chips
[2020/11/25 14:10:06] INFO: chain[2] - Shutting down the chain
[2020/11/25 14:10:06] ERROR: driver-btm-base.c:356 chain[2] - Initialization failed
[2020/11/25 14:10:09] WARN: chain[1] - 44 of 65 chips detected
[2020/11/25 14:10:09] ERROR: driver-btm-chain.c:488 chain[1] - Failed to detect ASIC chips
[2020/11/25 14:10:09] INFO: chain[1] - Shutting down the chain
[2020/11/25 14:10:09] ERROR: driver-btm-base.c:356 chain[1] - Initialization failed
[2020/11/25 14:10:12] WARN: chain[0] - 44 of 65 chips detected
[2020/11/25 14:10:12] ERROR: driver-btm-chain.c:488 chain[0] - Failed to detect ASIC chips
[2020/11/25 14:10:12] INFO: chain[0] - Shutting down the chain
[2020/11/25 14:10:12] ERROR: driver-btm-base.c:356 chain[0] - Initialization failed
[2020/11/25 14:10:12] ERROR: driver-btm-base.c:2154 Failed to initialize hash boards
[2020/11/25 14:10:12] INFO: Shutting down the miner
[2020/11/25 14:10:12] INFO: Stopping FPGA queue
[2020/11/25 14:10:12] INFO: chain[0] - Shutting down the chain
[2020/11/25 14:10:12] INFO: chain[1] - Shutting down the chain
[2020/11/25 14:10:12] INFO: chain[2] - Shutting down the chain
[2020/11/25 14:10:12] INFO: Power OFF
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: favebook on November 25, 2020, 02:55:26 PM
This is a new one, I've never seen any unit drop all hashboards at exact same chip (44).
Have you tried custom firmware or newest firmware from Bitmain? Could you try changing PSU? Could you try disconnecting one of the boards and running 1 or 2 hashboards only?
Please use [code/code] for logs.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: mikeywith on November 25, 2020, 03:13:33 PM
Please use the code function to post kernel logs, it's really annoying and hurts the eyes. :(, use something like this [2020/11/25 14:09:43] WARN: chain[2] - 44 of 65 chips detected
[2020/11/25 14:09:46] WARN: chain[1] - 44 of 65 chips detected
[2020/11/25 14:09:49] WARN: chain[0] - 44 of 65 chips detected What the kernel log suggests is that all 3 hashboards have only 44 asics, which means the signal at chip 45 gets interrupted, it is unlikely that all 3 hash boards will have the exact same problem, so my guess is your PSU got a problem, can you test the miner with another working PSU?
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: mikxxy on November 25, 2020, 06:19:52 PM
Sorry about the annoyance with code format :-[but im still a newbie :D, seems as a plausible explanation, as the the power cut only involed one of the two powercords. icould try with a psu from a T17 APW9 would that be sufficient for the test of the faulty T17+ APW9+? Upgraded to latest Bitmain orginal FW, and now flashed the awesom SD 2.03.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: mikeywith on November 25, 2020, 07:10:59 PM
Can you confirm that all 3 fans on the PSU spin just fine? icould try with a psu from a T17 40 Th would that be sufficient for the test of the faulty T17+ 58th?
NO, don't do that, the T17+ uses APW9+ while the T17 uses APW9 EMC, I am not the right person to ask when it comes to electricity but my guess is that the APW9+ could damage your T17. Upgraded to latest Bitmain orginal FW, and now flashed the awesom SD 2.03.
Are you getting different results?
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: mikxxy on November 25, 2020, 08:41:58 PM
Jup, all 3 spinn when powerd by both cords. Regarding PSU its way around, APW9 instead of the plus version, for testing. the miner stopped rigth after i powered back one of the cords due to the powercut, red led came upp instead of the green in end of power cycle, so that seems indicate a total sudden loss of function, rather then a progressive problem?. Seems to be a new design of the top cover, no 4 screws holding top down, this one have screws on the sides and something looking as a "button" on backside, how do i unmount the topcover on this miner?
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: CryptoLLC on November 25, 2020, 08:52:31 PM
Watch this video on solder balls, 0 asic or when hash board only detects 44 chips or 22 chips and so on.
https://www.youtube.com/watch?v=mqd-AEpcJTw (https://www.youtube.com/watch?v=mqd-AEpcJTw)
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: mikeywith on November 25, 2020, 11:26:39 PM
Seems to be a new design of the top cover, no 4 screws holding top down, this one have screws on the sides and something looking as a "button" on backside, how do i unmount the topcover on this miner?
I don't have a miner with such a cover, but I think this video will be helpful > https://www.youtube.com/watch?v=czBf5E2lYDk&t=1s Watch this video on solder balls, 0 asic or when hash board only detects 44 chips or 22 chips and so on.
That is a great video, I did hit the like on it, I have a few things to add 1- When there is a short-circuit caused by anything whether it's excessive solder or a heatsink that dropped and shorting other chips, 99% of the time you will get 0 asic and not 44, 22, and the other weird combinations. 2- You talked about buying the black glue from China, it's indeed a good product and extremely cheap, but that product has to be stored in the fridge, it can't be at room temperature for more than 10 days, and with the pandemic and the slow worldwide shipping it could take more than 10 days so make sure you check with the courier or get another alternative from the local store. 3- The problems you talked about are very common in all 17 series with no exception, so it's probably worth mentioning. Also, I would change the video title to " Chain[]: find 0 asic Antminer" as this will most likely be the most common keyword people would use.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: mikxxy on November 25, 2020, 11:45:07 PM
Thanks :D It was indeed a button to press for takning the top cover off, never seen this one. I dissassembled the miner and all the hashboards look fine no lose heatsinks. im leaning towards psu, as it happend simutaniusly.I conclude that theres power to the boards and fans, but its not powering up hashboards. Should be a separate power circuit for the boards. I have another, a T17 that lost one (occasionly one more), but controler detects the faulty board, some data as voltage is shown, and also a asic count before powering it off
ill disassemble the psu to check if theres any visual damage, dont know anything about testpoints or so, would appreciate any suggestions for where to search.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: mikeywith on November 26, 2020, 01:58:55 AM
Should be a separate power circuit for the boards.
There are indeed two different circuits and this is so confusing to most people, they see the LEDs turn on and they think it's a confirmation that the PSU is in perfect shape which sadly isn't really the case. I have another, a T17 that lost one (occasionly one more), but controler detects the faulty board, some data as voltage is shown
If I understood you correctly, you have another working T17 PSU (APW9) that is powering a single hash board, and sometimes two, and we know you "most likely" have a dead PSU and 3 working hash boards, wouldn't it be wise to take the working PSU and instal it on the "potentially" working 3 hash boards? ill disassemble the psu to check if theres any visual damage, dont know anything about testpoints or so, would appreciate any suggestions for where to search.
We milked this topic quite a bit, but long story short these PSUs were not really meant to be fixed, it's not that it's impossible to fix them, but once you open it you will get the point, to me, anything except for a simple fan change on those PSU isn't working looking into, and I doubt you will find many resources regarding the subject, so if you are not an expert in this field, chances are you should be looking for a PSU replacement.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: wndsnb on November 26, 2020, 04:10:39 PM
So you put the thermal solder on the chip? Do I need to put anything on the heat sink such as flux or something else?
This video shows a method of cleaning up and applying solder to attach the heat sinks: https://youtu.be/F6L9hCQ4OhY A bit of tacky flux can help to get the solder to flow and adhere to the chip surface. Flux plus solder wick is used to clean up excess solder. This is the solder paste, flux, and solder wick I use and have had good results with: https://www.chipquik.com/store/product_info.php?products_id=310001 https://www.chipquik.com/store/product_info.php?products_id=470006 https://www.chipquik.com/store/product_info.php?products_id=640003
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: mikxxy on November 27, 2020, 10:01:12 AM
Now i changed the PSU took it from a working T17+. Same problem persists . Inotice this message in Awesom miner [2020/11/27 07:56:00] INFO: Auto-tuning
[2020/11/27 07:55:58] INFO: eFUSE protection is active
[2020/11/27 07:54:49] INFO: Auto-tuning
[2020/11/27 07:54:47] INFO: eFUSE protection is active
[2020/11/27 07:53:24] INFO: Auto-tuning
[2020/11/27 07:53:17] INFO: eFUSE protection is active
JES, problem identified! The culprit is the control board, looks normal, there seems to be some problem in or out coming signals to the net,it does not identify itself on a IP scanner. changed inbetween the healthy one an d the bad one, so no problem with the hashboards. Awesom was inndicating 44 of 66, wich is wrong as there is only 44 chips on each board. Bitmain has produced several models of the T17+ this particular one has 58Th, so the Awesom FW got confused. Regardind the control board it may just be something with RJ45 connector, but i think its easier to just get a replacement board? I open up another one, a T17 it had actually a heatsink off! there is some videos in Russian language, about fixing this, but i semm not to understand if the chip is replaced or resolderd? i should be burnt shortly after heatsink falling off, while in mining mode? Isnt there a way to just "short" the bad chip out and thus restoring integrety of the chain?
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: mikeywith on November 27, 2020, 04:17:27 PM
JES, problem identified! The culprit is the control board......but i think its easier to just get a replacement board?
That is good news, it's very unlikely for a control board to toast, which is also why it would make sense if you found some very cheap control board, bitmain store (https://shop.bitmain.com/product/parts#Control%20Board) is out of stock, so you need to get it from elsewhere, are you located in the U.S? I open up another one, a T17 it had actually a heatsink off! there is some videos in Russian language, about fixing this, but i semm not to understand if the chip is replaced or resolderd? i should be burnt shortly after heatsink falling off, while in mining mode?
If the chip is bad then it needs replacement, but most of the time if the chip is toasted the heatsink won't fall, if the heatsink is off that hashboard is likely going to stop mining before the chip is burned, so usually, a heatsink that is off just needs resoldering. Isnt there a way to just "short" the bad chip out and thus restoring integrety of the chain?
None that I am aware off, but let's see what the other guys have to say although I doubt such a fix is possible.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: mikxxy on November 27, 2020, 09:12:36 PM
i'm located within the EU, whats confusing as said is the T17+ and none with different amount of chips on each board, 44 and 64?, should they need a designatet FW depending on asic count on each hash bord? Awesom issued two different FW's 1.00 and 2.0.3? Ill try the first one on the faulty card, may be it will run?
Yes rigth, the T17 with a poped heatsink present it self at initial phase of power cycling, 000000 and then it wanish from the Gui, so i migth be alive, lets see what will happen as i glue i back then.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: mikeywith on November 27, 2020, 09:59:14 PM
whats confusing as said is the T17+ and none with different amount of chips on each board, 44 and 64?, should they need a designatet FW depending on asic count on each hash bord? Awesom issued two different FW's 1.00 and 2.0.3? Ill try the first one on the faulty card, may be it will run?
That is strange, I don't think the firmware knows the number of chips i.e it isn't hard coded into it, it probably gets the information from the hash board itself, the reasoning behind my point is that using the same control board and the same firmware you can run different hashboards, for an example if you take S17 hash boards and put them in your S17 pro they will work just fine despite having different asic count. But with that being said you should reach out to Patrike (https://bitcointalk.org/index.php?action=profile;u=211077) and explain the issue to him.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: mikxxy on November 27, 2020, 11:27:22 PM
Yes im with you,. when i try run the bad controler in the second maschine it behaves exactly as in the previous setting, by not beeing able to detect correct asic valuse but in addition, now also giving error of not detecting any fans, even though the are spinning accordingly to pre setting of 30% (awesom FW), could it be affected by any virus in any of processors? A leds onboard are behaving as expected, boot sequenceas as it should, then it tries to initialize the hash bords iindefinitely. So what could by wrong with this controller? Regarding the poped heat sink can it just be glued on and then reinforced by glueing the top of the heatsink to those in vicinity? By joggling the controller back and forth, i started to catch on Awesom, detecting asic chains but the first one, also it warns if try to raise freq some steps above 500Mhz N: chain[0] - Failed to reset pic (attempt = 2), resp: 0x90 0x90
[2020/11/27 23:45:34] WARN: chain[0] - Failed to reset pic (attempt = 3), resp: 0x90 0x90
[2020/11/27 23:45:35] WARN: chain[0] - Failed to start pic app (attempt = 1), resp: 0x01 0x01
[2020/11/27 23:45:36] WARN: chain[0] - Failed to start pic app (attempt = 2), resp: 0x01 0x01
[2020/11/27 23:45:36] WARN: chain[0] - Failed to start pic app (attempt = 3), resp: 0x01 0x01
[2020/11/27 23:45:38] WARN: chain[0] - Failed to reset pic (attempt = 1), resp: 0x01 0x01
[2020/11/27 23:45:39] WARN: chain[0] - Failed to reset pic (attempt = 2), resp: 0x01 0x01
[2020/11/27 23:45:41] INFO: chain[2] - 44 chips detected
[2020/11/27 23:45:41] WARN: chain[0] - Failed to reset pic (attempt = 3), resp: 0x01 0x01
[2020/11/27 23:45:41] WARN: chain[0] - Failed to start pic app (attempt = 1), resp: 0x01 0x01
[2020/11/27 23:45:42] WARN: chain[0] - Failed to start pic app (attempt = 2), resp: 0x01 0x01
[2020/11/27 23:45:42] WARN: chain[0] - Failed to start pic app (attempt = 3), resp: 0x01 0x01
[2020/11/27 23:45:43] INFO: chain[1] - 44 chips detected
[2020/11/27 23:45:44] WARN: chain[0] - Failed to reset pic (attempt = 1), resp: 0x01 0x01
[2020/11/27 23:45:46] WARN: chain[0] - Failed to reset pic (attempt = 2), resp: 0x01 0x01
[2020/11/27 23:45:47] WARN: chain[0] - Failed to reset pic (attempt = 3), resp: 0x01 0x01
[2020/11/27 23:45:48] WARN: chain[0] - Failed to start pic app (attempt = 1), resp: 0x01 0x01
[2020/11/27 23:39:24] INFO: Initializing
[2020/11/27 23:39:22] INFO: eFUSE protection is active
[2020/11/27 23:39:00] INFO: Initializing
[2020/11/27 23:38:58] INFO: eFUSE protection is active
[2020/11/27 23:38:34] INFO: Initializing
[2020/11/27 23:38:34] INFO: Pool connection FAILED. Check INTERNET, POOL URL or WORKER
[2020/11/27 23:38:32] INFO: eFUSE protection is active
[2020/11/27 23:38:00] INFO: Mining
[2020/11/27 23:36:38] INFO: Initializing
[2020/11/27 23:36:36] INFO: eFUSE protection is active
[2020/11/27 23:36:30] INFO: Initializing
[2020/11/27 23:36:28] INFO: eFUSE protection is active
[2020/11/27 23:35:59] INFO: Initializing
[2020/11/27 23:35:59] INFO: Pool connection FAILED. Check INTERNET,
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: mikeywith on November 28, 2020, 12:25:08 AM
So what could by wrong with this controller?
When a control board is bad, you would expect all kind of weird problems, and honestly, things now are becoming confusing and hard to follow ???, can you just not test the bad control board so we all can focus on the good one? i'm located within the EU...
That is unfortunate, I don't know of any trusted suppliers there, but should you need one I think you should contact one of these guys (in no particular order) - favebook (https://bitcointalk.org/index.php?action=profile;u=2290678) - thierry4wd (https://bitcointalk.org/index.php?action=profile;u=1656984) - o_solo_miner (https://bitcointalk.org/index.php?action=profile;u=395806) There might be others, but those are off the top of my hand for a list of EU based miners that can be trusted. Regarding the poped heat sink can it just be glued on and then reinforced by glueing the top of the heatsink to those in vicinity?
More explanation is needed, I don't seem to understand why exactly are you planning on doing. [2020/11/27 23:38:58] INFO: eFUSE protection is active
This line is very strange, I did text Marc (Asic.to) on telegram, let's see what he knows, it seems like a power-related issue, are you sure the PSU you using is APW9+ and the input voltage is 200-240v? Also, it shows this Pool connection FAILED. Check INTERNET, POOL URL or WORKER
Are you sure your pool settings are in place? is Asicboost is activated make sure the pool is AB compatible if this log comes from the bad control board and all this info can be misleading.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: mikxxy on November 28, 2020, 02:08:08 AM
Alrigth i see what mean.. i hava tendency to go down into the Rabbit holes when something from my point of view ocours, yes and things may get out of contex and thus causing confusion. So im sorry for any incoinvience caused.
i have no outher means to test of the bad card by any other means than trail and error. with the apprieciated help from you guys. All the equipment mentioned, has been running att smal miningpark for at least 6 mounths , and all the settings are also the origional against Poolin. So all the odd behavior described herein emmenate from known and reliable mining conditions. The Antminer T17+ is out of stock and those few contrilers that find their way to Ebay, are very expensive. //Mixy----------------------------------------------------------
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: mikeywith on November 28, 2020, 03:47:07 AM
Take it easy, we all have lost many gears, the failure rate on these 17 series is much more than you can imagine, I would have been more than happy if I got 6 months of all my 17 series gears, so you are not in the worst situation one can be.
Recap:
1- I assume the T17 is done with and you are going to try and solder the heatsinks?
2- You have 2*T17+ , one is fine another one has a bad control board, when you try them on a working control board you get the errors you posted in the last post? is that the case or am I missing something?
If I am on the right track, you should know that mixing hash boards from different miners will cause many issues, so while you are trying to fix all this please keep track of the different hash boards and to which control board they belong.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: favebook on November 28, 2020, 04:26:05 AM
[...]
Sadly, as of 2020 I cannot seem to find any reliable resellers here in Europe for parts. I had to order anything I need from Bitmain when they had it in stock and from some resellers I found on random websites and in random telegram chats. Shipping anything was more expensive than the parts I was ordering. It was NOT worth it. Any broken hardware that I have right now will be RMA-ed as that is the best cost-effective move I can do right now. Others might know more or have better luck, but this is my experience. For example, I have Innosilicon T2TZ with burnt PSU and fully operational hashboards (tested on other unit). Ordering new PSU would cost 110 USD and shipping for it would be 130 USD. While I bought the whole unit (used at that time) for 500 euro. [...]
eFuse line seems to be normal thing during auto-tune and sometimes during reboot of miner. I've noticed on a lot of different WORKING units which were running Vnish firmware. As for pool connection failed, I'd advise to try different network as yours might be blocking some ports like devfee pool ones and that would make the unit stop mining (I've experienced this first hand with my home network on thierry4wd's firmware, even though the unit works fine on the network which I use for miners only). If that is not the case, then mikey's advice to check pool settings and asicboost should be the things to look at.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: mikeywith on November 28, 2020, 05:26:35 AM
Sadly, as of 2020 I cannot seem to find any reliable resellers here in Europe for parts.
I think Zeusbtc have a branch in Poland, not sure if it's just a workshop where they only repair your miners or they actually do sell stuff, it might be worth looking into it, perhaps you or mikxxy should get in touch with them, if you don't get an answer I'll reach out to someone from Zeusbtc.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: mikxxy on November 28, 2020, 12:18:10 PM
Status is now 1-T17 about to solder the poped heat sink, the other 2 cards seem to work ok! But before it used to drop another board after been mining for a wihle. So there migth be another bad soldered Heat sink missbehaving when heating up a bit, standing i the farm?. Been knocking around with a pen, I ordered a fixture, so we will see.
2-T17+ the original 'dead one', is now working fine, after it received' a working control board
3- T17+ (the control board donor) Seem to have 2 boards working ok, and the third one not startng due to problem with pic processor. i'll will try to change around hash board cables to isolate problem. The control board came from the 'dead' T17+, so i migth have some issues. It came up with a connection error last night, so i'll check if it remains.
Update: After identifying a bad ribbon cable the other T17+ also works fully, the connection issue was becuase of some instability caused by the faulty hashboard connection!
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: favebook on November 28, 2020, 05:31:40 PM
I think Zeusbtc have a branch in Poland, not sure if it's just a workshop where they only repair your miners or they actually do sell stuff, it might be worth looking into it, perhaps you or mikxxy should get in touch with them, if you don't get an answer I'll reach out to someone from Zeusbtc.
I'd wager that it's only repair shop in Poland, as their website sells everything over WhatsApp orders and they seem to have their warehouse in China (Hong Kong?). If you have someone from Poland branch, feel free to give me his contact or ask him if they have any warehouses in Europe. Otherwise, I will try to contact their support to see if I can get in contact with someone from Poland.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: mikeywith on November 28, 2020, 07:40:33 PM
But before it used to drop another board after been mining for a wihle. So there migth be another bad soldered Heat sink missbehaving when heating up
Yes, that is exactly the cause, one or more heatsink are not glued perfectly, sometimes they will contact and read and sometimes they don't, I have a few boards that behave this way, just mine with it until it longer functions, the bad heatsink will eventually fall off or at least becomes so loose that you can identify it with your bare eyes/hands. I will try to contact their support to see if I can get in contact with someone from Poland.
go to this page > https://www.zeusbtc.com/Repair.asp, scroll down and you will see a list of some cities/countries, looks like you have to keep your contact information and they should contact you. The site also mentions Attention: The miner repair points shown on the map below are independent individuals. This site only offers a free display. Please contact the maintenance point for specific matters. If there is any dispute, please resolve it by negotiation. Any consequences will not be related to this site. So it doesn't seem like they are a branch of Zuesbtc, but I can only assume that Zeusbtc must have done at least a basic check on these guys to confirm their integrity, some of them might have got some training in China from Zeusbtc, I tend to think that they can be trusted, but I would still. deal with caution
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: mikxxy on November 28, 2020, 08:25:05 PM
Regarding Antminer spares. https://www.antminerdistribution.com/ is EU based and reliable (bougth a miner back in 2019), more expensive then most of asian sites, but if you do your purchase trough a company they will deduct the VAT. They have both miners and spares availble, mostly on request though. I dont know if tare afiliated with Bitmain, or not.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: favebook on November 28, 2020, 10:55:02 PM
Regarding Antminer spares. https://www.antminerdistribution.com/ is EU based and reliable (bougth a miner back in 2019), more expensive then most of asian sites, but if you do your purchase trough a company they will deduct the VAT. They have both miners and spares availble, mostly on request though. I dont know if tare afiliated with Bitmain, or not.
Would you care to provide proof of payment or some sort of proof that you successfully bought miners from them? They are not affiliated with Bitmain and they always seemed like a scam to me. Sometimes they had better prices than Bitmain themselves. [...]
I'll check with them, they might have something I need.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: mikeywith on November 28, 2020, 11:24:51 PM
I dont know if tare afiliated with Bitmain, or not.
They are not, also their website looks scammy but the prices seem legit and more to the upside than the opposite. Seems like mining in EU is dying, if not already dead (power cost-related issue for the most part), and not so many Europeans discuss suppliers, EU tax, and all the stuff that are related to EU, unlike how the U.S folks here do, maybe one of you should start a topic dedicated to EU miners so you all can share resources, news and anything else that you might find useful, there are probably at least 5-6 EU based miners around this board.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: mikxxy on November 29, 2020, 10:17:59 AM
Ok i'll find something. Another reliable shop is Prominerz in Switzerland. I bougth some miners there to in 2019, i donnu their ability in spares, maybe on reguest as service?
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: mikeywith on November 29, 2020, 09:10:39 PM
Ok i'll find something. Another reliable shop is Prominerz in Switzerland. I bougth some miners there to in 2019, i donnu their ability in spares, maybe on reguest as service?
You lose nothing if you contact them, it's just doesn't line up perfectly, Switzerland and mining don't seem to blend well, I mean who on earth would start a mining business in that expensive country? were prices near the reasonable back in 2019 when you bought the gears? I think what you should look for is a supplier in Eastern Europe, mining there is a thing and probably the supplier's option is much better on that side of the continent.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: mikxxy on November 30, 2020, 12:03:08 AM
I agree that Switcherland is a odd place for a Crypto miner outlet, but on the other hand crypto have no borders no time zones. Back then it was one of the few reliable outlets in Europe. They mainly profited on antminer customers, that either missed out on ordering or got to few from Bitmains batches,and saw crypto prices surge. I think prices then was like 25% higher compared to Bitmain, but i was able to buy excl. VAT. got some z11 there. From my point of veiw, ordering, paying in advance, from a Swiss company, on wich i could get info on the net and so on, contra an Asian company (ex Bitmain) was no brainer.
But idont agree on that eastern europe, should be a more reliable and/or convient, chances to be scammed is in my opion higher in east EU. In general (not crypto bussinessin particular) It still carries a shady reputation from the past. Corruption is higher (maybee not everyone will agree with but lif its out of topic i'll remove it) But on the other han eastern europe is expirienced regarding crypto, land got a larger crypto community then in west, mainly becuase of the historical mistrust towards gowerments, insitutions and banks. In some west Eu countries, like Sweden, knowledge about crypto, in mainstream population is almost non existing.
Sorry for massive of typos, but tired lika dog, becuase of a rough day, tuning all the miners to a maximum. Unfortianly i went one step to high in the auto tunning, and in the end i blow the main fuses, 4x80amps, supplying the farm, then i just threw in the towel and went home.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: mikeywith on November 30, 2020, 02:43:57 AM
But idont agree on that eastern europe, should be a more reliable and/or convient...
Just to be crystal clear here, my main objective was related to price and availability only, I assumed because east Europe has more mining operation then mining-related stuff would be cheaper and easier to find, but as far as integrity, or lack thereof, I am sure you know much better than I do. ... tuning all the miners to a maximum. Unfortianly i went one step to high in the auto tunning, and in the end i blow the main fuses...
1 - PLEASE don't overclock these gears, they are very very sensitive, they barely run for long enough at stock settings, overclocking them is extremely risky. 2 - The fact that some overclocking was enough to blow those fuses, you might actually be pushing them the max anyway, the same thing would have happened if you had a sudden drop in voltage and your gears needed to draw more amps, so be careful.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: mikxxy on December 01, 2020, 01:56:08 AM
[...]
I dont now if anyone noticed the "freezer trick" in this video posted above, https://youtu.be/F6L9hCQ4OhY ,I had some parts of it tranlated by i russian speking friend, and it turned that some hashboard problems can be detected by freezing the board, and there after run it. I took the hash board board (0) from the T17, that droped off or didn't start, that on irregular bases, (in awesom showing ...4 of 30 asic...) and put it in the freezer for a couple of hours, and it felt stable there after, now on day 2, been minning normal and also starts normal on multible power cycles. I dont know the exact mechanism for this phenomena, as the dude couldn't explain to well, but as its known that bad quality of solder composition/flux, migth be affected by prolonged heat exposure, resulting in bad solder joints due to crystallic changes in the solderit self. The process of freezing migth some how mediate some transformation the solder. Let see how long this fix will hold... Worth trying on such boards. To the other board [1] i attached the heat sink with thermal glue but to no awail, still showing (..24 of 30 ASICS..) freezing did not help on this one.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: mikeywith on December 04, 2020, 06:49:30 PM
So how is the frozen hashboard doing now? I know the freezing trick works on weakening the adhesive and make the heatsink easier to remove, not exactly sure how it would help to make it stick harder!! I would love to hear more from other members, NFW and wndsnb can perhaps shed some light on the subject.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: wndsnb on December 04, 2020, 07:14:14 PM
Well ... Can't argue with results but I doubt it will be a very permanent fix. I'm also curious if it is still running.
My only guess would be that the issue was a bad solder joint and the thermal cycle expansion/contraction moved the bad connection enough to make contact. Or maybe the residual flux that may be keeping some stray solder balls in place that leaked out during heatsink application gets brittle enough to flake off when cold.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: Moeter81 on December 05, 2020, 05:40:38 AM
I sent my defective S17 + 67 to Bitmain for repair on October 29th (out of warranty). After several inquiries about the status of my order, I received an email from Bitmain yesterday: Dear customer
Miner type & Quantity:1
Antminer S17+ (67T)
Due to the impact of the Covid-19 , our overseas warehouses( HK，CA, Netherlands) have stopped shipments. Due to the temporary shutdown of the warehouses, we cannot get the machines from the warehouse.
In order to be able to solve this problem in a timely manner and minimize customer losses, we provide you with the following solutions. Please check it out. If you can accept this solution, we will be grateful.
Thank you for your understanding and strong support.
1. We will apply for equal coupon compensation for you based on the current market value of the second hands miners; the coupon value is 1127usd
2. If your product is out of warranty, scrapped, or mixed, we regret that we cannot directly return it for you, and we can only apply for coupon compensation for you based on the marketing price minus the repair quotation that needs to be paid;
3. Coupons can be used to purchase all products of our official website www.bitmain.com , which can be deducted 10% of the total order amount and have a one-year warranty;
4. We can also help you contact the buyer, and sell the coupons in your hand at 90% of the coupon price, so that you can get the corresponding USD or BTC;
5. This is buyout coupons, will not ship the products back to customer.
Thank you again for your strong support to our company, and hope to receive your reply.
Unfortunately, that was not the solution that I would have expected! after paying 50 € for shipping and 30 $ to Bitmain for the estimate. Now I don't know what to do. and I wonder if the S19 I have ordered will arrive.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: wndsnb on December 05, 2020, 03:24:50 PM
[...]
Wow ... so they want to keep your property and won't even compensate you in real $, but 10% max coupons instead! Unreal. The things people/companies/governments are doing using the COVID excuse are just awful.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: mikeywith on December 05, 2020, 05:53:49 PM
1. We will apply for equal coupon compensation for you based on the current market value of the second hands miners; the coupon value is 1127usd
They are lying to you, used S17+ go for above $1500, for $1127 you can only get S17-56th. 4. We can also help you contact the buyer, and sell the coupons in your hand at 90% of the coupon price, so that you can get the corresponding USD or BTC;
Point number 4 is really funny, they want to persuade you to sell them the miner at a much cheaper rate, nobody is going to pay 90%, they will be that "buyer" so (1127-30$)*0.9 = $987.3, also expect a 5-10% less with an excuse of bitcoin price is lower on the exchange they use. :-\ Sorry that this is happening to you man, Bitmain is indeed a terrible company to deal with. :-[
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: HagssFIN on December 06, 2020, 08:37:37 AM
Bitmain doesn't really shame on their dirty ways of making money for the owners! >:(
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: mikeywith on December 06, 2020, 01:38:18 PM
Bitmain doesn't really shame on their dirty ways of making money for the owners! >:(
Indeed, I think they trapped him into sending his gear by quoting him an estimate of $30 to fix his S17+, what kind of a fix would bitmain put their staff on for $30 :-\, anyway, people should look for alternative ways to fix their gears, check zeusbtc or ask other forum members about workshops that are specialized in mining, phill knows a few in the U.S he perhaps should make a dedicated topic in regards to that.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: wndsnb on December 06, 2020, 05:32:40 PM
Found the post where phil recommends a repair place. Not sure if those prices are up to date, the web site currently says $150/$250 for basic/advanced repair. I'm in NC. Can I send you my PSUs to test? Or can you send me a working one and I'll pay for shipping?
We have a repair guy we use that is located in NC. Give me 5 minutes to find the link. He has been a godsend with psu replacement. I used https://hmtech.co/ (919) 283-2715 they do repair m20s they sold me a m20s psu a p21 they also have bitmain parts and repairs. Tell them philipma1957 of bitcointalk linked you. I get zero money for this. But I like that they know I send them people. He has to be close to you as it is the same state. He has helped 4 or 5 of us with psu replacements. yeah they seem to have really dropped in their service . I won't be using them to get a m30s. I used https://hmtech.co/ (919) 283-2715 they do repair m20s they sold me a m20s psu a p21 ASIC Repair : Basic / Advanced
Bitmain
$300 / $400
S17 & T17
Whatsminer
$300 / $400
M20s & M21S
Innosilicon
$300 / $400
T3 series
ASIC PSU's
Innosilicon T3 series PSU
$200
New
Whatspower P21 PSU
$200
New
Innosilicon T2 double fan series & T3 PSU
$200
New
good luck.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: mikeywith on December 08, 2020, 12:27:14 AM
Thanks for finding the post, I started this topic (https://bitcointalk.org/index.php?topic=5297994.0) to help the mining community locate repair services nearby, since sending gears back to China isn't working as it should, I believe this thread would be very helpful, I hope that we all band together to grow the list in that topic.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: mikxxy on December 08, 2020, 08:48:19 PM
So how is the frozen hashboard doing now? I know the freezing trick works on weakening the adhesive and make the heatsink easier to remove, not exactly sure how it would help to make it stick harder!! I would love to hear more from other members, NFW and wndsnb can perhaps shed some light on the subject.
Yes it's still stable since i started it, even though i OC it a little to kompensate for the dead card. Chain# ASIC# Frequency(avg) Voltage Consumption (W) GH/S(ideal) GH/S(RT) Errors(HW) Temp(PCB) Temp(Chip) ASIC status
1 24 0 15.8 15 0.00 0.00 0 0-0-0-0 0-0-0-0 Failed to detect ASIC chips
2 30 750 15.8 684 15,120.00 14,789.48 1 54-59-52-57 76-82-76-79 ooo ooo ooo ooo ooo ooo ooo ooo ooo ooo
3 30 750 15.8 684 15,120.00 15,022.88 2 52-56-51-55 75-78-73-75 ooo ooo ooo ooo ooo ooo ooo ooo ooo ooo
Total 84 750 1383 30,240.00 29,812.36 3 going to try to fix the dead card once i get the board fixture, but i thnk it will require a lot of expirience and gear to rework the ASIC chip. Anyone that did this operation with good outcome? By the way is miners.eu a trusted vendor?
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: mikeywith on December 08, 2020, 09:19:06 PM
Yes it's still stable since i started it, even though i OC it a little to kompensate for the dead card.
That is good news, temps look good too, I will try the trick soon, I will need to go the farm to pick up all the dead 17 series, I have a lot of them, since the trick is cheap and easy it's worth the try. By the way is miners.eu a trusted vendor?
Nop, they are likely scammers, there are a few accusations against them in this thread (https://bitcointalk.org/index.php?topic=5279533.0), also their Trustpilot reviews aren't great, see one thing to notice about Trustpilot is that positive reviews can be faked easily because they require no proof, while negatives require verifications such as emails, screenshots and all that, the seller can dispute against your negative feedback and have it deleted, so negative feedback outweighs a 100 positive once. Here is one recent feedback: You wont get any items from them
I paid my order 8 weeks ago, product should be "in stock, shipped in 5 days" no product, no refund so far.
Chat on their website mysteriously closes after you have made your payment. No answer to phone and to email rarely, telling to wait more.
I have made police report of them.
They reply in 10 min when it's on their favor, 2-4weeks when yours.
They offered to pay me to get my previous review off so I did but ofc they didn't paid so its here again.
They will threat you with lawsuit for sure if you share your negative experience.
Nobody knows or trusts John, but the fact that his verified negative feedback is still there simply means that the accused party failed to prove that John is lying, which means they have indeed scammed him.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: mikxxy on December 08, 2020, 10:18:02 PM
I'm thinking most conviinient is to freeze the whole miner:) and pick up used freezer cheap on the way???:)
miners.eu have good prices on etherum miners, much better than Prominerz, which seem to "trusted" pricing policy by up to 20% compared to miners.eu. It seems there some talking regarding "negative elements" making it hard to distinguish inbetween the vendors, scamers i.e unhappy buyers, competitors trying to miscredit each other as scammers. Whats your opion on that? Is asicminervalue.com to be a trusted as non afiliated party? They have markings "trusted" on some vendors (obviously based on some simple algortim, but still they are risking to discredit thier trademark if they are deviating with their "Trusted" marks to much. Just my 2 cents.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: favebook on December 09, 2020, 02:30:53 AM
Is asicminervalue.com to be a trusted as non afiliated party? They have markings "trusted" on some vendors (obviously based on some simple algortim, but still they are risking to discredit thier trademark if they are deviating with their "Trusted" marks to much.
Just my 2 cents
Read FAQ from time to time. It might be fruitful for you: All vendor listed are legit?
We try to check vendors to provide the safest links possible, but we cannot guarantee any of them.
You must be aware that all external links are out of our control, and one store may be safe for some users and give one bad experience to another.
All labels and risk estimates are given "as is" based on our experience and feedback from the community.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: Moeter81 on December 09, 2020, 05:53:12 AM
I phoned Dominic Alders (Miners.eu) 2 weeks ago. I asked him which miners he could deliver from the warehouse immediately. His answer was that you don't have any miners in stock. (according to the website, some devices are shown as available). All miners, but could be delivered between 7-14 days.
My order was executed and paid for on November 17th, 2020. Unfortunately I haven't received a miner yet and communication is difficult. I hope it will turn out well, I will report.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: mtnrotary on December 12, 2020, 08:52:26 PM
Hi all, I've read through some of this thread and am amazed to see the number of errors people have had with their s17's.
I'm in a similar boat however not so familiar so was after some help in trying to determine what to do next. Long story short, 3 of my miners are hosted in Canada. The mining company elected to transfer the miners across the country and within days of arriving at the new site all three died.
I have access to the serial numbers and kernal logs but trying to figure out what to post to help determine the issue? The problem is complicated by the fact the mining company is being rather unhelpful, and I'm on the other side of the world to Canada.
Anyway, any assistance would be greatly appreciated :)
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: wndsnb on December 12, 2020, 09:26:26 PM
A good start would be to post the kernel logs.
Are they not hashing at all, or hashing and then shutting down after a period of time?
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: Moeter81 on December 14, 2020, 05:47:12 AM
https://bitcointalk.org/index.php?topic=5279533.0 (https://bitcointalk.org/index.php?topic=5279533.0)
here, I have completed my report about Miners.eu.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: Costar79 on December 20, 2020, 05:18:01 AM
Hi all, I bought two second hand s17+ from coinminingcentral of the 140 Th i was hoping to get out of these two machines i am only getting 50 to 80. All kinds of problems, the common ones, temp sensors hash boards going off line all that jazz. The first machine, the better one starts up at with all three chains running and the after a couple of hours gets a temp sensor error and then shuts that board off. 70Th down to 50Th then seems to stay like that until i reboot the machine and then the board starts up again back to 70Th YAAAY for a couple of hours again and boops back offline! The second machine seems to have only one board that functions correctly, ill leave the log here so someone can make sense of whats happening. 2020-12-20 03:47:35 driver-btm-api.c:1239:init_miner_version: miner ID : 80781c864e10481c
2020-12-20 03:47:35 driver-btm-api.c:1245:init_miner_version: FPGA Version = 0xB023
2020-12-20 03:47:40 driver-btm-api.c:837:get_product_id: product_id[0] = 0
2020-12-20 03:47:40 driver-btm-api.c:837:get_product_id: product_id[1] = 0
2020-12-20 03:47:40 driver-btm-api.c:837:get_product_id: product_id[2] = 0
2020-12-20 03:47:40 driver-btm-api.c:792:_set_project_type: project:0
2020-12-20 03:47:40 driver-btm-api.c:813:_set_project_type: Project type: Antminer S17+
2020-12-20 03:47:40 driver-btm-api.c:824:dump_pcb_bom_version: Chain [0] PCB Version: 0x0100
2020-12-20 03:47:40 driver-btm-api.c:825:dump_pcb_bom_version: Chain [0] BOM Version: 0x0100
2020-12-20 03:47:40 driver-btm-api.c:824:dump_pcb_bom_version: Chain [1] PCB Version: 0x0100
2020-12-20 03:47:40 driver-btm-api.c:825:dump_pcb_bom_version: Chain [1] BOM Version: 0x0100
2020-12-20 03:47:40 driver-btm-api.c:824:dump_pcb_bom_version: Chain [2] PCB Version: 0x0100
2020-12-20 03:47:40 driver-btm-api.c:825:dump_pcb_bom_version: Chain [2] BOM Version: 0x0100
2020-12-20 03:47:42 driver-btm-api.c:2372:bitmain_board_init: Fan check passed.
2020-12-20 03:47:43 board.c:36:jump_and_app_check_restore_pic: chain[0] PIC jump to app
2020-12-20 03:47:46 board.c:40:jump_and_app_check_restore_pic: Check chain[0] PIC fw version=0x88
2020-12-20 03:47:47 board.c:36:jump_and_app_check_restore_pic: chain[1] PIC jump to app
2020-12-20 03:47:49 board.c:40:jump_and_app_check_restore_pic: Check chain[1] PIC fw version=0x88
2020-12-20 03:47:50 board.c:36:jump_and_app_check_restore_pic: chain[2] PIC jump to app
2020-12-20 03:47:52 board.c:40:jump_and_app_check_restore_pic: Check chain[2] PIC fw version=0x88
2020-12-20 03:47:52 thread.c:1358:create_pic_heart_beat_thread: create thread
2020-12-20 03:47:52 power_api.c:213:power_init: Power init:
2020-12-20 03:47:52 power_api.c:214:power_init: current_voltage_raw = 0
2020-12-20 03:47:52 power_api.c:215:power_init: highest_voltage_raw = 2100
2020-12-20 03:47:52 power_api.c:216:power_init: working_voltage_raw = 1950
2020-12-20 03:47:52 power_api.c:217:power_init: higher_voltage_raw = 2040
2020-12-20 03:47:52 power_api.c:218:power_init: check_asic_voltage_raw = 2100
2020-12-20 03:47:52 driver-btm-api.c:2382:bitmain_board_init: Enter 30s sleep to make sure power release finish.
2020-12-20 03:47:52 power_api.c:186:power_off: init gpio907
2020-12-20 03:48:24 power_api.c:324:set_to_highest_voltage_by_steps: Set to voltage raw 2100, step by step.
2020-12-20 03:48:50 power_api.c:85:check_voltage_multi: retry time: 0
2020-12-20 03:48:51 power_api.c:40:_get_avg_voltage: chain = 0, voltage = 20.970549
2020-12-20 03:48:52 power_api.c:40:_get_avg_voltage: chain = 1, voltage = 20.924359
2020-12-20 03:48:53 power_api.c:40:_get_avg_voltage: chain = 2, voltage = 20.897566
2020-12-20 03:48:53 power_api.c:53:_get_avg_voltage: average_voltage = 20.930825
2020-12-20 03:48:53 power_api.c:71:check_voltage: target_vol = 21.00, actural_vol = 20.93, check voltage passed.
2020-12-20 03:48:53 uart.c:72:set_baud: set fpga_baud to 115200
2020-12-20 03:49:04 driver-btm-api.c:1134:check_asic_number_with_power_on: Chain[0]: find 65 asic, times 0
2020-12-20 03:49:15 driver-btm-api.c:1134:check_asic_number_with_power_on: Chain[1]: find 50 asic, times 0
2020-12-20 03:49:26 driver-btm-api.c:1134:check_asic_number_with_power_on: Chain[1]: find 50 asic, times 1
2020-12-20 03:49:37 driver-btm-api.c:1134:check_asic_number_with_power_on: Chain[1]: find 50 asic, times 2
2020-12-20 03:49:37 power_api.c:380:modify_check_asic_voltage: check_asic_voltage_raw = 2100
chain 1, IO_DRIVE_STRENGTH_CONFIGURATION reg = 0x f1fffff
2020-12-20 03:49:46 driver-btm-api.c:1157:check_asic_number_with_power_on: Chain[1]: find 50 asic, times 3
2020-12-20 03:49:46 power_api.c:380:modify_check_asic_voltage: check_asic_voltage_raw = 2050
2020-12-20 03:49:46 power_api.c:364:set_to_check_asic_voltage_by_steps: Set to voltage raw 2050, step by step.
2020-12-20 03:49:49 power_api.c:85:check_voltage_multi: retry time: 0
2020-12-20 03:49:52 power_api.c:40:_get_avg_voltage: chain = 0, voltage = 20.433504
2020-12-20 03:49:53 power_api.c:40:_get_avg_voltage: chain = 1, voltage = 20.411010
2020-12-20 03:49:54 power_api.c:40:_get_avg_voltage: chain = 2, voltage = 20.386683
2020-12-20 03:49:54 power_api.c:53:_get_avg_voltage: average_voltage = 20.410399
2020-12-20 03:49:54 power_api.c:71:check_voltage: target_vol = 20.50, actural_vol = 20.41, check voltage passed.
chain 1, IO_DRIVE_STRENGTH_CONFIGURATION reg = 0x f1fffff
2020-12-20 03:50:03 driver-btm-api.c:1157:check_asic_number_with_power_on: Chain[1]: find 50 asic, times 4
2020-12-20 03:50:03 power_api.c:380:modify_check_asic_voltage: check_asic_voltage_raw = 2000
2020-12-20 03:50:03 power_api.c:364:set_to_check_asic_voltage_by_steps: Set to voltage raw 2000, step by step.
2020-12-20 03:50:06 power_api.c:85:check_voltage_multi: retry time: 0
2020-12-20 03:50:08 power_api.c:40:_get_avg_voltage: chain = 0, voltage = 19.947570
2020-12-20 03:50:09 power_api.c:40:_get_avg_voltage: chain = 1, voltage = 19.924455
2020-12-20 03:50:10 power_api.c:40:_get_avg_voltage: chain = 2, voltage = 19.900127
2020-12-20 03:50:10 power_api.c:53:_get_avg_voltage: average_voltage = 19.924051
2020-12-20 03:50:10 power_api.c:71:check_voltage: target_vol = 20.00, actural_vol = 19.92, check voltage passed.
chain 1, IO_DRIVE_STRENGTH_CONFIGURATION reg = 0x f1fffff
2020-12-20 03:50:19 driver-btm-api.c:1157:check_asic_number_with_power_on: Chain[1]: find 50 asic, times 5
2020-12-20 03:50:19 power_api.c:380:modify_check_asic_voltage: check_asic_voltage_raw = 2100
2020-12-20 03:50:19 power_api.c:364:set_to_check_asic_voltage_by_steps: Set to voltage raw 2100, step by step.
2020-12-20 03:50:24 power_api.c:85:check_voltage_multi: retry time: 0
2020-12-20 03:50:26 power_api.c:40:_get_avg_voltage: chain = 0, voltage = 20.892719
2020-12-20 03:50:27 power_api.c:40:_get_avg_voltage: chain = 1, voltage = 20.897566
2020-12-20 03:50:28 power_api.c:40:_get_avg_voltage: chain = 2, voltage = 20.873238
2020-12-20 03:50:28 power_api.c:53:_get_avg_voltage: average_voltage = 20.887841
2020-12-20 03:50:28 power_api.c:71:check_voltage: target_vol = 21.00, actural_vol = 20.89, check voltage passed.
2020-12-20 03:50:28 driver-btm-api.c:1193:check_asic_number: Chain 1 only find 50 asic, will power off hash board 1
2020-12-20 03:50:29 driver-btm-api.c:1195:check_asic_number: Chain 1 voltage: an0 = 2.770968, an2 2.770968, an6 2.519355.
2020-12-20 03:50:41 driver-btm-api.c:1134:check_asic_number_with_power_on: Chain[2]: find 65 asic, times 0
2020-12-20 03:50:46 driver-hash-chip.c:266:set_uart_relay: set uart relay to 0x330003
2020-12-20 03:50:46 driver-btm-api.c:435:set_order_clock: chain[0]: set order clock, stragegy 3
2020-12-20 03:50:47 driver-btm-api.c:435:set_order_clock: chain[2]: set order clock, stragegy 3
2020-12-20 03:50:47 driver-hash-chip.c:502:set_clock_delay_control: core_data = 0x34
2020-12-20 03:50:47 driver-btm-api.c:1892:check_clock_counter: freq 50 clock_counter_limit 6
2020-12-20 03:50:47 voltage[0] = 1960
2020-12-20 03:50:47 voltage[2] = 1960
2020-12-20 03:50:47 power_api.c:226:set_working_voltage_raw: working_voltage_raw = 1960
2020-12-20 03:50:49 temperature.c:340:calibrate_temp_sensor_one_chain: chain 0 temp sensor NCT218
2020-12-20 03:50:50 temperature.c:340:calibrate_temp_sensor_one_chain: chain 2 temp sensor NCT218
2020-12-20 03:50:50 uart.c:72:set_baud: set fpga_baud to 12000000
2020-12-20 03:50:51 driver-btm-api.c:293:check_bringup_temp: Bring up temperature is 23
2020-12-20 03:50:51 thread.c:1378:create_check_miner_status_thread: create thread
2020-12-20 03:50:51 thread.c:1368:create_show_miner_status_thread: create thread
2020-12-20 03:50:51 thread.c:1348:create_temperature_monitor_thread: create thread
2020-12-20 03:50:51 frequency.c:514:check_bringup_temp_dec_freq: dec freq = 0 when bringup temp = 23 dec_freq_index=0
2020-12-20 03:50:51 freq_tuning.c:183:freq_tuning_get_max_freq: Max freq of tuning is 650
2020-12-20 03:50:51 driver-btm-api.c:1765:send_null_work: [DEBUG] Send null work.
2020-12-20 03:50:51 thread.c:1338:create_asic_status_monitor_thread: create thread
2020-12-20 03:50:51 frequency.c:1110:inc_freq_with_fixed_vco: chain = 255, freq = 515, is_higher_voltage = true
2020-12-20 03:51:41 power_api.c:352:set_to_voltage_by_steps: Set to voltage raw 2090, step by step.
2020-12-20 03:51:43 power_api.c:85:check_voltage_multi: retry time: 0
2020-12-20 03:51:45 power_api.c:40:_get_avg_voltage: chain = 0, voltage = 20.797954
2020-12-20 03:51:46 power_api.c:40:_get_avg_voltage: chain = 2, voltage = 20.700767
2020-12-20 03:51:46 power_api.c:53:_get_avg_voltage: average_voltage = 20.749361
2020-12-20 03:51:46 power_api.c:71:check_voltage: target_vol = 20.90, actural_vol = 20.75, check voltage passed.
2020-12-20 03:55:20 thread.c:1273:asic_status_monitor_thread: ERROR: chain 0 get hashrate_reg_counter 55, require 65, failed times 1: ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo xxxxx xxxxx
2020-12-20 03:55:21 thread.c:1293:asic_status_monitor_thread: chain 0 can't get enough hashrate reg val for 0 times.
2020-12-20 03:55:22 thread.c:1273:asic_status_monitor_thread: ERROR: chain 0 get hashrate_reg_counter 55, require 65, failed times 1: ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo xxxxx xxxxx
2020-12-20 03:55:23 thread.c:1293:asic_status_monitor_thread: chain 0 can't get enough hashrate reg val for 1 times.
2020-12-20 03:55:24 thread.c:1273:asic_status_monitor_thread: ERROR: chain 0 get hashrate_reg_counter 55, require 65, failed times 1: ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo xxxxx xxxxx
2020-12-20 03:55:25 thread.c:1293:asic_status_monitor_thread: chain 0 can't get enough hashrate reg val for 2 times.
2020-12-20 03:55:26 thread.c:1273:asic_status_monitor_thread: ERROR: chain 0 get hashrate_reg_counter 55, require 65, failed times 1: ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo xxxxx xxxxx
2020-12-20 03:55:26 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 2, chip = 150, reg = 28, got chain = 0, chip = 0, reg = 1
2020-12-20 03:55:27 register.c:313:get_register: !!! REG_TYPE = 1. 704673792
2020-12-20 03:55:27 thread.c:1293:asic_status_monitor_thread: chain 0 can't get enough hashrate reg val for 3 times.
2020-12-20 03:55:28 thread.c:1273:asic_status_monitor_thread: ERROR: chain 0 get hashrate_reg_counter 56, require 65, failed times 1: ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo xxxox xxxxx
2020-12-20 03:55:29 thread.c:1293:asic_status_monitor_thread: chain 0 can't get enough hashrate reg val for 4 times.
2020-12-20 03:55:29 thread.c:1297:asic_status_monitor_thread: chain 0 can't get enough hashrate reg val for 5 times, power off.
2020-12-20 03:55:30 temperature.c:843:get_temp_info: read temp sensor failed: chain = 0, sensor = 3, chip = 50, reg = 1
2020-12-20 03:56:02 power_api.c:352:set_to_voltage_by_steps: Set to voltage raw 2060, step by step.
2020-12-20 03:56:04 power_api.c:85:check_voltage_multi: retry time: 0
2020-12-20 03:56:05 power_api.c:40:_get_avg_voltage: chain = 2, voltage = 20.384910
2020-12-20 03:56:05 power_api.c:53:_get_avg_voltage: average_voltage = 20.384910
2020-12-20 03:56:05 power_api.c:71:check_voltage: target_vol = 20.60, actural_vol = 20.38, check voltage passed.
2020-12-20 03:56:05 frequency.c:1181:inc_asic_diff_freq_by_steps: chain = 2, start = 515, freq_step = 5
2020-12-20 03:56:09 driver-btm-api.c:765:set_timeout: freq = 545, percent = 90, hcn = 44236, timeout = 81
2020-12-20 03:56:09 power_api.c:310:set_to_working_voltage_by_steps: Set to voltage raw 1960, step by step.
2020-12-20 03:56:14 power_api.c:85:check_voltage_multi: retry time: 0
2020-12-20 03:56:15 power_api.c:40:_get_avg_voltage: chain = 2, voltage = 19.413043
2020-12-20 03:56:15 power_api.c:53:_get_avg_voltage: average_voltage = 19.413043
2020-12-20 03:56:15 power_api.c:71:check_voltage: target_vol = 19.60, actural_vol = 19.41, check voltage passed.
2020-12-20 03:56:15 thread.c:1373:create_check_system_status_thread: create thread
2020-12-20 03:56:16 driver-btm-api.c:2618:bitmain_soc_init: Init done!
2020-12-20 03:56:16 driver-btm-api.c:222:set_miner_status: STATUS_INIT
2020-12-20 03:56:20 driver-btm-api.c:222:set_miner_status: STATUS_OKAY
2020-12-20 03:56:21 frequency.c:205:get_ideal_hash_rate_GH: ideal_hash_rate = 22699
2020-12-20 03:56:21 frequency.c:223:get_sale_hash_rate_GH: sale_hash_rate = 22000
2020-12-20 03:56:26 driver-btm-api.c:1496:dhash_chip_send_job: Version num 4.
2020-12-20 03:56:26 driver-btm-api.c:1644:dhash_chip_send_job: stime.tv_sec 1608436586, block_ntime 1608436571
Can someone pls pls advise me of what my next steps should be here. Here are the kernel versions for both machines:
Kernel Version Linux 4.6.0-xilinx-gff8137b-dirty #25 SMP PREEMPT Fri Nov 23 15:30:52 CST 2018
File System Version Tue Jun 2 10:31:07 CST 2020
I am thinking of replacing the board with the temp sensor error on the first machine with the board from the second machine that seems to be working and then maybe sending a full machine away for repairs. Any suggestions?
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: wndsnb on December 20, 2020, 02:26:25 PM
2020-12-20 03:49:15 driver-btm-api.c:1134:check_asic_number_with_power_on: Chain[1]: find 50 asic, times 0
2020-12-20 03:49:26 driver-btm-api.c:1134:check_asic_number_with_power_on: Chain[1]: find 50 asic, times 1
2020-12-20 03:49:37 driver-btm-api.c:1134:check_asic_number_with_power_on: Chain[1]: find 50 asic, times 2
2020-12-20 03:49:37 power_api.c:380:modify_check_asic_voltage: check_asic_voltage_raw = 2100
[...]
2020-12-20 03:55:20 thread.c:1273:asic_status_monitor_thread: ERROR: chain 0 get hashrate_reg_counter 55, require 65, failed times 1: ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo xxxxx xxxxx
2020-12-20 03:55:21 thread.c:1293:asic_status_monitor_thread: chain 0 can't get enough hashrate reg val for 0 times.
2020-12-20 03:55:22 thread.c:1273:asic_status_monitor_thread: ERROR: chain 0 get hashrate_reg_counter 55, require 65, failed times 1: ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo xxxxx xxxxx
2020-12-20 03:55:23 thread.c:1293:asic_status_monitor_thread: chain 0 can't get enough hashrate reg val for 1 times.
2020-12-20 03:55:24 thread.c:1273:asic_status_monitor_thread: ERROR: chain 0 get hashrate_reg_counter 55, require 65, failed times 1: ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo xxxxx xxxxx
2020-12-20 03:55:25 thread.c:1293:asic_status_monitor_thread: chain 0 can't get enough hashrate reg val for 2 times.
2020-12-20 03:55:26 thread.c:1273:asic_status_monitor_thread: ERROR: chain 0 get hashrate_reg_counter 55, require 65, failed times 1: ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo xxxxx xxxxx
2020-12-20 03:55:26 register.c:160:read_asic_reg_with_addr: read asic reg error: expect chain = 2, chip = 150, reg = 28, got chain = 0, chip = 0, reg = 1
2020-12-20 03:55:27 register.c:313:get_register: !!! REG_TYPE = 1. 704673792
2020-12-20 03:55:27 thread.c:1293:asic_status_monitor_thread: chain 0 can't get enough hashrate reg val for 3 times.
2020-12-20 03:55:28 thread.c:1273:asic_status_monitor_thread: ERROR: chain 0 get hashrate_reg_counter 56, require 65, failed times 1: ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo xxxox xxxxx
2020-12-20 03:55:29 thread.c:1293:asic_status_monitor_thread: chain 0 can't get enough hashrate reg val for 4 times.
2020-12-20 03:55:29 thread.c:1297:asic_status_monitor_thread: chain 0 can't get enough hashrate reg val for 5 times, power off.
2020-12-20 03:55:30 temperature.c:843:get_temp_info: read temp sensor failed: chain = 0, sensor = 3, chip = 50, reg = 1
Looks like chain 1 is not able to get status back from chip 51 - 65, which could there is an issue with asic chip 50 or 51, or an issue with the voltage regulation for 51 - 55. Could be bad solder joints, excess solder from the heatsink shorting signals out, or just a bad chip. Essentially the same for chain 0, but it manages to get the status back initially but then fails once the board starts hashing. That can happen because solder connections break or short when the board heats up or the voltage regulation dies once the board starts drawing more current. I don't think you can hurt anything by swapping hashboards around, although some 17 series hashboards don't mix with others, so it may not work. My understanding is that the control board needs all the hashboards to be running the same firmware. Did these machines arrive like this? If so, is coinminingcentral not being helpful? If you've read through this thread then you know sending a miner to Bitmain for repair is not a good idea, so definitely try to find a 3rd party to repair them. If you send it to Bitmain you might never see it again. So in my opinion, best option is to get coinminingcentral to make good in some way, second best option is to find a repair shop.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: mikeywith on December 21, 2020, 05:03:05 AM
There is no firmware on those hash boards, it's just the hex file difference, most miners will show some sort of id type for each hashboard, those need to be identical, these info can be found either on the hash board itself or the kernel log, you should look for things like typeID, major type or minor type, product id or any other info that shows at the top of the kernel log which specifies a certain value for each of the hash boards you have installed. here is an example of mixed boards on an S9: Chain[J6] chip[244] get middle temp offset=28 typeID=55
Chain[J7] chip[244] get middle temp offset=27 typeID=1a
Chain[J8] chip[244] get middle temp offset=27 typeID=55
Chain 7 has a different type id but the miner works just fine because well, it's an S9 after all ;D. Here is another example of an S9k: read chain[0] hardware info:
major type: 0
minor type: 2
chip level: 0
bom version: 0x10
pcb version: 0x39
read chain[2] hardware info:
major type: 0
minor type: 2
chip level: 0
bom version: 0x10
pcb version: 0x39
There is no exact word/value to look for, but it's pretty self-explanatory.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: mtnrotary on December 21, 2020, 06:15:53 PM
They're not hashing at all, or just very low hash. At this point Bitmain have said to ship all three back to them :(. Any tips would be greatly appreciated! Worker 1 Booting Linux on physical CPU 0x0
Linux version 4.6.0-xilinx-gff8137b-dirty (lzq@armdev2) (gcc version 4.8.3 20140320 (prerelease) (Sourcery CodeBench Lite 2014.05-23) ) #25 SMP PREEMPT Fri Nov 23 15:30:52 CST 2018
CPU: ARMv7 Processor [413fc090] revision 0 (ARMv7), cr=18c5387d
CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
Machine model: Xilinx Zynq
cma: Reserved 16 MiB at 0x0e000000
Memory policy: Data cache writealloc
On node 0 totalpages: 61440
free_area_init_node: node 0, pgdat c0b39280, node_mem_map cde10000
Normal zone: 480 pages used for memmap
Normal zone: 0 pages reserved
Normal zone: 61440 pages, LIFO batch:15
percpu: Embedded 12 pages/cpu @cddf1000 s19776 r8192 d21184 u49152
pcpu-alloc: s19776 r8192 d21184 u49152 alloc=12*4096
pcpu-alloc: [0] 0 [0] 1
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 60960
Kernel command line: mem=240M console=ttyPS0,115200 ramdisk_size=33554432 root=/dev/ram rw earlyprintk
PID hash table entries: 1024 (order: 0, 4096 bytes)
Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
Memory: 203544K/245760K available (6345K kernel code, 231K rwdata, 1896K rodata, 1024K init, 223K bss, 25832K reserved, 16384K cma-reserved, 0K highmem)
Virtual kernel memory layout:
vector : 0xffff0000 - 0xffff1000 ( 4 kB)
fixmap : 0xffc00000 - 0xfff00000 (3072 kB)
vmalloc : 0xcf800000 - 0xff800000 ( 768 MB)
lowmem : 0xc0000000 - 0xcf000000 ( 240 MB)
pkmap : 0xbfe00000 - 0xc0000000 ( 2 MB)
modules : 0xbf000000 - 0xbfe00000 ( 14 MB)
.text : 0xc0008000 - 0xc090c424 (9234 kB)
.init : 0xc0a00000 - 0xc0b00000 (1024 kB)
.data : 0xc0b00000 - 0xc0b39fe0 ( 232 kB)
.bss : 0xc0b39fe0 - 0xc0b71c28 ( 224 kB)
Preemptible hierarchical RCU implementation.
Build-time adjustment of leaf fanout to 32.
RCU restricting CPUs from NR_CPUS=4 to nr_cpu_ids=2.
RCU: Adjusting geometry for rcu_fanout_leaf=32, nr_cpu_ids=2
NR_IRQS:16 nr_irqs:16 16
efuse mapped to cf800000
ps7-slcr mapped to cf802000
L2C: platform modifies aux control register: 0x72360000 -> 0x72760000
L2C: DT/platform modifies aux control register: 0x72360000 -> 0x72760000
L2C-310 erratum 769419 enabled
L2C-310 enabling early BRESP for Cortex-A9
L2C-310 full line of zeros enabled for Cortex-A9
L2C-310 ID prefetch enabled, offset 1 lines
L2C-310 dynamic clock gating enabled, standby mode enabled
L2C-310 cache controller enabled, 8 ways, 512 kB
L2C-310: CACHE_ID 0x410000c8, AUX_CTRL 0x76760001
zynq_clock_init: clkc starts at cf802100
Zynq clock init
sched_clock: 64 bits at 333MHz, resolution 3ns, wraps every 4398046511103ns
clocksource: arm_global_timer: mask: 0xffffffffffffffff max_cycles: 0x4ce07af025, max_idle_ns: 440795209040 ns
Switching to timer-based delay loop, resolution 3ns
clocksource: ttc_clocksource: mask: 0xffff max_cycles: 0xffff, max_idle_ns: 537538477 ns
ps7-ttc #0 at cf80a000, irq=18
Console: colour dummy device 80x30
Calibrating delay loop (skipped), value calculated using timer frequency.. 666.66 BogoMIPS (lpj=3333333)
pid_max: default: 32768 minimum: 301
Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
CPU: Testing write buffer coherency: ok
CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
Setting up static identity map for 0x100000 - 0x100058
CPU1: failed to boot: -1
Brought up 1 CPUs
SMP: Total of 1 processors activated (666.66 BogoMIPS).
CPU: All CPU(s) started in SVC mode.
devtmpfs: initialized
VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4
clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
pinctrl core: initialized pinctrl subsystem
NET: Registered protocol family 16
DMA: preallocated 256 KiB pool for atomic coherent allocations
cpuidle: using governor menu
hw-breakpoint: found 5 (+1 reserved) breakpoint and 1 watchpoint registers.
hw-breakpoint: maximum watchpoint size is 4 bytes.
zynq-ocm f800c000.ps7-ocmc: ZYNQ OCM pool: 256 KiB @ 0xcf880000
vgaarb: loaded
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
media: Linux media interface: v0.10
Linux video capture interface: v2.00
pps_core: LinuxPPS API ver. 1 registered
pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
PTP clock support registered
EDAC MC: Ver: 3.0.0
Advanced Linux Sound Architecture Driver Initialized.
clocksource: Switched to clocksource arm_global_timer
NET: Registered protocol family 2
TCP established hash table entries: 2048 (order: 1, 8192 bytes)
TCP bind hash table entries: 2048 (order: 2, 16384 bytes)
TCP: Hash tables configured (established 2048 bind 2048)
UDP hash table entries: 256 (order: 1, 8192 bytes)
UDP-Lite hash table entries: 256 (order: 1, 8192 bytes)
NET: Registered protocol family 1
RPC: Registered named UNIX socket transport module.
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
PCI: CLS 0 bytes, default 64
Trying to unpack rootfs image as initramfs...
rootfs image is not initramfs (no cpio magic); looks like an initrd
Freeing initrd memory: 12792K (cce82000 - cdb00000)
hw perfevents: enabled with armv7_cortex_a9 PMU driver, 7 counters available
futex hash table entries: 512 (order: 3, 32768 bytes)
workingset: timestamp_bits=28 max_order=16 bucket_order=0
jffs2: version 2.2. (NAND) (SUMMARY) © 2001-2006 Red Hat, Inc.
io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered (default)
dma-pl330 f8003000.ps7-dma: Loaded driver for PL330 DMAC-241330
dma-pl330 f8003000.ps7-dma: DBUFF-128x8bytes Num_Chans-8 Num_Peri-4 Num_Events-16
e0000000.serial: ttyPS0 at MMIO 0xe0000000 (irq = 158, base_baud = 6249999) is a xuartps
console [ttyPS0] enabled
xdevcfg f8007000.ps7-dev-cfg: ioremap 0xf8007000 to cf86e000
[drm] Initialized drm 1.1.0 20060810
brd: module loaded
loop: module loaded
CAN device driver interface
gpiod_set_value: invalid GPIO
libphy: MACB_mii_bus: probed
macb e000b000.ethernet eth0: Cadence GEM rev 0x00020118 at 0xe000b000 irq 31 (00:0a:35:00:00:00)
Generic PHY e000b000.etherne:00: attached PHY driver [Generic PHY] (mii_bus:phy_addr=e000b000.etherne:00, irq=-1)
e1000e: Intel(R) PRO/1000 Network Driver - 3.2.6-k
e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
ehci-pci: EHCI PCI platform driver
usbcore: registered new interface driver usb-storage
mousedev: PS/2 mouse device common for all mice
i2c /dev entries driver
Xilinx Zynq CpuIdle Driver started
sdhci: Secure Digital Host Controller Interface driver
sdhci: Copyright(c) Pierre Ossman
sdhci-pltfm: SDHCI platform and OF driver helper
mmc0: SDHCI controller on e0100000.ps7-sdio [e0100000.ps7-sdio] using ADMA
ledtrig-cpu: registered to indicate activity on CPUs
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
nand: device found, Manufacturer ID: 0x2c, Chip ID: 0xda
nand: Micron MT29F2G08ABAEAWP
nand: 256 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 64
nand: WARNING: pl35x-nand: the ECC used on your system is too weak compared to the one required by the NAND chip
Bad block table found at page 131008, version 0x01
Bad block table found at page 130944, version 0x01
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: 6/1, WL threshold: 4096, image sequence number: 262741923
ubi0: available PEBs: 0, total reserved PEBs: 64, PEBs reserved for bad PEB handling: 40
ubi0: background thread "ubi_bgt0d" started, PID 708
UBIFS (ubi0:0): background thread "ubifs_bgt0_0" started, PID 711
UBIFS (ubi0:0): UBIFS: mounted UBI device 0, volume 0, name "configs"
UBIFS (ubi0:0): LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
UBIFS (ubi0:0): FS size: 1396736 bytes (1 MiB, 11 LEBs), journal size 888833 bytes (0 MiB, 5 LEBs)
UBIFS (ubi0:0): reserved for root: 65970 bytes (64 KiB)
UBIFS (ubi0:0): media format: w4/r0 (latest is w4/r0), UUID A9E8BDA4-70DE-45D9-83BE-2DD9F129C0C6, 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: 404/140, WL threshold: 4096, image sequence number: 3563076859
ubi1: available PEBs: 0, total reserved PEBs: 1020, PEBs reserved for bad PEB handling: 36
ubi1: background thread "ubi_bgt1d" started, PID 720
UBIFS (ubi1:0): background thread "ubifs_bgt1_0" started, PID 723
UBIFS (ubi1:0): UBIFS: mounted UBI device 1, volume 0, name "reserve1"
UBIFS (ubi1:0): LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
UBIFS (ubi1:0): FS size: 123039744 bytes (117 MiB, 969 LEBs), journal size 6221824 bytes (5 MiB, 49 LEBs)
UBIFS (ubi1:0): reserved for root: 4952683 bytes (4836 KiB)
UBIFS (ubi1:0): media format: w4/r0 (latest is w4/r0), UUID A21581E4-693A-4BBF-A66A-FCE5ACD2EF7F, 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 = 0xb023
In fpga mem driver!
request_mem_region OK!
fpga mem virtual address is 0xd2000000
random: nonblocking pool is initialized
2020-10-15 11:30:38 driver-btm-api.c:632:init_freq_mode: This is scan-user version
2020-10-15 11:30:38 driver-btm-api.c:1815:bitmain_soc_init: opt_multi_version = 1
2020-10-15 11:30:38 driver-btm-api.c:1816:bitmain_soc_init: opt_bitmain_ab = 1
2020-10-15 11:30:38 driver-btm-api.c:1817:bitmain_soc_init: opt_bitmain_work_mode = 0
2020-10-15 11:30:38 driver-btm-api.c:1818:bitmain_soc_init: Miner compile time: Fri Dec 6 13:23:09 CST 2019 type: Antminer S17+
2020-10-15 11:30:38 driver-btm-api.c:1819:bitmain_soc_init: commit version: c767010 2019-12-04 14:22:30, build by: lol 2019-12-06 13:31:56
2020-10-15 11:30:38 driver-btm-api.c:1655:show_sn: no SN got, please write SN to /nvdata/sn
2020-10-15 11:30:38 fan.c:236:front_fan_power_on: Note: front fan is power on!
2020-10-15 11:30:38 fan.c:248:rear_fan_power_on: Note: rear fan is power on!
2020-10-15 11:30:38 driver-btm-api.c:1110:miner_device_init: Detect 256MB control board of XILINX
2020-10-15 11:30:38 driver-btm-api.c:1058:init_fan_parameter: fan_eft : 0 fan_pwm : 0
2020-10-15 11:30:38 thread.c:731:create_read_nonce_reg_thread: create thread
2020-10-15 11:30:44 driver-btm-api.c:1042:init_miner_version: miner ID : 8168242429e04814
2020-10-15 11:30:44 driver-btm-api.c:1048:init_miner_version: FPGA Version = 0xB023
2020-10-15 11:30:49 driver-btm-api.c:689:get_product_id: product_id[0] = 0
2020-10-15 11:30:49 driver-btm-api.c:689:get_product_id: product_id[1] = 0
2020-10-15 11:30:49 driver-btm-api.c:689:get_product_id: product_id[2] = 0
2020-10-15 11:30:49 driver-btm-api.c:645:_set_project_type: project:0
2020-10-15 11:30:49 driver-btm-api.c:665:_set_project_type: Project type: Antminer S17+
2020-10-15 11:30:49 driver-btm-api.c:676:dump_pcb_bom_version: Chain [0] PCB Version: 0x0100
2020-10-15 11:30:49 driver-btm-api.c:677:dump_pcb_bom_version: Chain [0] BOM Version: 0x0100
2020-10-15 11:30:49 driver-btm-api.c:676:dump_pcb_bom_version: Chain [1] PCB Version: 0x0100
2020-10-15 11:30:49 driver-btm-api.c:677:dump_pcb_bom_version: Chain [1] BOM Version: 0x0100
2020-10-15 11:30:49 driver-btm-api.c:676:dump_pcb_bom_version: Chain [2] PCB Version: 0x0100
2020-10-15 11:30:49 driver-btm-api.c:677:dump_pcb_bom_version: Chain [2] BOM Version: 0x0100
2020-10-15 11:30:53 driver-btm-api.c:1764:bitmain_board_init: Fan check passed.
2020-10-15 11:30:54 board.c:36:jump_and_app_check_restore_pic: chain[0] PIC jump to app
2020-10-15 11:30:56 board.c:40:jump_and_app_check_restore_pic: Check chain[0] PIC fw version=0x88
2020-10-15 11:30:57 board.c:36:jump_and_app_check_restore_pic: chain[1] PIC jump to app
2020-10-15 11:31:00 board.c:40:jump_and_app_check_restore_pic: Check chain[1] PIC fw version=0x88
2020-10-15 11:31:01 board.c:36:jump_and_app_check_restore_pic: chain[2] PIC jump to app
2020-10-15 11:31:03 board.c:40:jump_and_app_check_restore_pic: Check chain[2] PIC fw version=0x88
2020-10-15 11:31:03 thread.c:726:create_pic_heart_beat_thread: create thread
2020-10-15 11:31:03 power_api.c:208:power_init: Power init:
2020-10-15 11:31:03 power_api.c:209:power_init: current_voltage_raw = 0
2020-10-15 11:31:03 power_api.c:210:power_init: highest_voltage_raw = 2100
2020-10-15 11:31:03 power_api.c:211:power_init: working_voltage_raw = 1950
2020-10-15 11:31:03 power_api.c:212:power_init: higher_voltage_raw = 2040
2020-10-15 11:31:03 driver-btm-api.c:1774:bitmain_board_init: Enter 30s sleep to make sure power release finish.
2020-10-15 11:31:03 power_api.c:182:power_off: init gpio907
2020-10-15 11:31:35 power_api.c:262:set_to_highest_voltage: Set to voltage raw 2100, one step.
2020-10-15 11:31:37 power_api.c:83:check_voltage_multi: retry time: 0
2020-10-15 11:31:38 power_api.c:38:_get_avg_voltage: chain = 0, voltage = 21.016624
2020-10-15 11:31:39 power_api.c:38:_get_avg_voltage: chain = 1, voltage = 21.040921
2020-10-15 11:31:40 power_api.c:38:_get_avg_voltage: chain = 2, voltage = 21.089514
2020-10-15 11:31:40 power_api.c:51:_get_avg_voltage: average_voltage = 21.049020
2020-10-15 11:31:40 power_api.c:69:check_voltage: target_vol = 21.00, actural_vol = 21.05, check voltage passed.
2020-10-15 11:31:40 uart.c:71:set_baud: set fpga_baud to 115200
2020-10-15 11:31:40 driver-hash-chip.c:245:dhash_chip_set_baud_v2: chain[0]: chip baud = 115200, chip_divider = 26
2020-10-15 11:31:40 driver-hash-chip.c:245:dhash_chip_set_baud_v2: chain[1]: chip baud = 115200, chip_divider = 26
2020-10-15 11:31:40 driver-hash-chip.c:245:dhash_chip_set_baud_v2: chain[2]: chip baud = 115200, chip_divider = 26
2020-10-15 11:31:51 driver-btm-api.c:982:check_asic_number_with_power_on: Chain[0]: find 65 asic, times 0
2020-10-15 11:32:02 driver-btm-api.c:982:check_asic_number_with_power_on: Chain[1]: find 0 asic, times 0
2020-10-15 11:32:13 driver-btm-api.c:982:check_asic_number_with_power_on: Chain[1]: find 0 asic, times 1
2020-10-15 11:32:23 driver-btm-api.c:982:check_asic_number_with_power_on: Chain[1]: find 0 asic, times 2
2020-10-15 11:32:23 driver-btm-api.c:1010:check_asic_number: Chain 1 only find 0 asic, will power off hash board 1
2020-10-15 11:32:25 driver-btm-api.c:1012:check_asic_number: Chain 1 voltage: an0 = 2.783871, an2 2.790323, an6 2.522581.
2020-10-15 11:32:37 driver-btm-api.c:982:check_asic_number_with_power_on: Chain[2]: find 65 asic, times 0
2020-10-15 11:32:43 driver-hash-chip.c:266:set_uart_relay: set uart relay to 0x330003
2020-10-15 11:32:43 driver-btm-api.c:352:set_order_clock: chain[0]: set order clock, stragegy 3
2020-10-15 11:32:43 driver-btm-api.c:352:set_order_clock: chain[2]: set order clock, stragegy 3
2020-10-15 11:32:43 driver-hash-chip.c:502:set_clock_delay_control: core_data = 0x34
2020-10-15 11:32:43 voltage[0] = 1940
2020-10-15 11:32:43 voltage[2] = 1940
2020-10-15 11:32:43 power_api.c:220:set_working_voltage_raw: working_voltage_raw = 1940
2020-10-15 11:32:44 temperature.c:314:calibrate_temp_sensor_one_chain: chain 0 temp sensor NCT218
2020-10-15 11:32:45 temperature.c:314:calibrate_temp_sensor_one_chain: chain 2 temp sensor NCT218
2020-10-15 11:32:45 uart.c:71:set_baud: set fpga_baud to 12000000
2020-10-15 11:32:45 driver-hash-chip.c:245:dhash_chip_set_baud_v2: chain[0]: chip baud = 12000000, chip_divider = 3
2020-10-15 11:32:45 driver-hash-chip.c:245:dhash_chip_set_baud_v2: chain[2]: chip baud = 12000000, chip_divider = 3
2020-10-15 11:32:46 driver-btm-api.c:241:check_bringup_temp: Bring up temperature is 15
2020-10-15 11:32:46 thread.c:746:create_check_miner_status_thread: create thread
2020-10-15 11:32:46 thread.c:736:create_show_miner_status_thread: create thread
2020-10-15 11:32:46 thread.c:721:create_temperature_monitor_thread: create thread
2020-10-15 11:32:46 freq_tuning.c:145:freq_tuning_get_max_freq: Max freq of tuning is 650
2020-10-15 11:32:46 frequency.c:770:inc_freq_with_fixed_vco: chain = 255, freq = 540, is_higher_voltage = true
2020-10-15 11:32:55 frequency.c:811:inc_freq_with_fixed_step: chain = 0, freq_start = 540, freq_end = 590, freq_step = 5, is_higher_voltage = true
2020-10-15 11:32:57 power_api.c:346:set_to_voltage_by_steps: Set to voltage raw 2090, step by step.
2020-10-15 11:32:58 power_api.c:83:check_voltage_multi: retry time: 0
2020-10-15 11:32:59 power_api.c:38:_get_avg_voltage: chain = 0, voltage = 20.822251
2020-10-15 11:33:00 power_api.c:38:_get_avg_voltage: chain = 2, voltage = 20.892719
2020-10-15 11:33:00 power_api.c:51:_get_avg_voltage: average_voltage = 20.857485
2020-10-15 11:33:00 power_api.c:69:check_voltage: target_vol = 20.90, actural_vol = 20.86, check voltage passed.
2020-10-15 11:33:04 power_api.c:346:set_to_voltage_by_steps: Set to voltage raw 2070, step by step.
2020-10-15 11:33:06 power_api.c:83:check_voltage_multi: retry time: 0
2020-10-15 11:33:07 power_api.c:38:_get_avg_voltage: chain = 0, voltage = 20.627877
2020-10-15 11:33:08 power_api.c:38:_get_avg_voltage: chain = 2, voltage = 20.725064
2020-10-15 11:33:08 power_api.c:51:_get_avg_voltage: average_voltage = 20.676471
2020-10-15 11:33:08 power_api.c:69:check_voltage: target_vol = 20.70, actural_vol = 20.68, check voltage passed.
2020-10-15 11:33:08 frequency.c:840:inc_asic_diff_freq_by_steps: chain = 0, start = 590, freq_step = 5
2020-10-15 11:33:13 frequency.c:840:inc_asic_diff_freq_by_steps: chain = 2, start = 540, freq_step = 5
2020-10-15 11:33:16 driver-btm-api.c:618:set_timeout: freq = 620, percent = 90, hcn = 44236, timeout = 71
2020-10-15 11:33:16 power_api.c:226:set_higher_voltage_raw: higher_voltage_raw = 2040
2020-10-15 11:33:16 power_api.c:332:set_to_higher_voltage_by_steps: Set to voltage raw 2040, step by step.
2020-10-15 11:33:18 power_api.c:83:check_voltage_multi: retry time: 0
2020-10-15 11:33:19 power_api.c:38:_get_avg_voltage: chain = 0, voltage = 20.336317
2020-10-15 11:33:20 power_api.c:38:_get_avg_voltage: chain = 2, voltage = 20.433504
2020-10-15 11:33:20 power_api.c:51:_get_avg_voltage: average_voltage = 20.384910
2020-10-15 11:33:20 power_api.c:69:check_voltage: target_vol = 20.40, actural_vol = 20.38, check voltage passed.
2020-10-15 11:33:20 thread.c:741:create_check_system_status_thread: create thread
2020-10-15 11:33:21 driver-btm-api.c:1919:bitmain_soc_init: Init done!
2020-10-15 11:33:21 driver-btm-api.c:194:set_miner_status: STATUS_INIT
2020-10-15 11:33:25 driver-btm-api.c:194:set_miner_status: STATUS_OKAY
2020-10-15 11:33:26 frequency.c:129:get_ideal_hash_rate_GH: ideal_hash_rate = 49572
2020-10-15 11:33:26 frequency.c:145:get_sale_hash_rate_GH: sale_hash_rate = 49000
2020-10-15 11:33:29 driver-btm-api.c:1292:dhash_chip_send_job: Version num 4
2020-10-15 11:33:38 thread.c:390:check_working_voltage: current PCB min temperature is 28
2020-10-15 11:33:38 thread.c:391:check_working_voltage: current voltage is 2040, recovery to 1940
2020-10-15 11:33:38 power_api.c:304:set_to_working_voltage_by_steps: Set to voltage raw 1940, step by step.
2020-10-15 11:33:43 power_api.c:83:check_voltage_multi: retry time: 0
2020-10-15 11:33:45 power_api.c:38:_get_avg_voltage: chain = 0, voltage = 19.364450
2020-10-15 11:33:46 power_api.c:38:_get_avg_voltage: chain = 2, voltage = 19.436780
2020-10-15 11:33:46 power_api.c:51:_get_avg_voltage: average_voltage = 19.400615
2020-10-15 11:33:46 power_api.c:69:check_voltage: target_vol = 19.40, actural_vol = 19.40, check voltage passed.
2020-10-15 12:03:46 thread.c:214:calc_hashrate_avg: avg rate is 50463.77 in 30 mins
2020-10-15 12:03:46 temperature.c:482:temp_statistics_show: pcb temp 33~64 chip temp 53~81
2020-10-15 12:33:48 thread.c:214:calc_hashrate_avg: avg rate is 50487.23 in 30 mins
2020-10-15 12:33:48 temperature.c:482:temp_statistics_show: pcb temp 35~64 chip temp 54~82
2020-10-15 13:03:49 thread.c:214:calc_hashrate_avg: avg rate is 50529.31 in 30 mins
2020-10-15 13:03:49 temperature.c:482:temp_statistics_show: pcb temp 34~62 chip temp 54~79
2020-10-15 13:33:51 thread.c:214:calc_hashrate_avg: avg rate is 50277.34 in 30 mins
2020-10-15 13:33:51 temperature.c:482:temp_statistics_show: pcb temp 34~63 chip temp 54~80
Worker 2 Booting Linux on physical CPU 0x0
Linux version 4.6.0-xilinx-gff8137b-dirty (lzq@armdev2) (gcc version 4.8.3 20140320 (prerelease) (Sourcery CodeBench Lite 2014.05-23) ) #25 SMP PREEMPT Fri Nov 23 15:30:52 CST 2018
CPU: ARMv7 Processor [413fc090] revision 0 (ARMv7), cr=18c5387d
CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
Machine model: Xilinx Zynq
cma: Reserved 16 MiB at 0x0e000000
Memory policy: Data cache writealloc
On node 0 totalpages: 61440
free_area_init_node: node 0, pgdat c0b39280, node_mem_map cde10000
Normal zone: 480 pages used for memmap
Normal zone: 0 pages reserved
Normal zone: 61440 pages, LIFO batch:15
percpu: Embedded 12 pages/cpu @cddf1000 s19776 r8192 d21184 u49152
pcpu-alloc: s19776 r8192 d21184 u49152 alloc=12*4096
pcpu-alloc: [0] 0 [0] 1
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 60960
Kernel command line: mem=240M console=ttyPS0,115200 ramdisk_size=33554432 root=/dev/ram rw earlyprintk
PID hash table entries: 1024 (order: 0, 4096 bytes)
Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
Memory: 203544K/245760K available (6345K kernel code, 231K rwdata, 1896K rodata, 1024K init, 223K bss, 25832K reserved, 16384K cma-reserved, 0K highmem)
Virtual kernel memory layout:
vector : 0xffff0000 - 0xffff1000 ( 4 kB)
fixmap : 0xffc00000 - 0xfff00000 (3072 kB)
vmalloc : 0xcf800000 - 0xff800000 ( 768 MB)
lowmem : 0xc0000000 - 0xcf000000 ( 240 MB)
pkmap : 0xbfe00000 - 0xc0000000 ( 2 MB)
modules : 0xbf000000 - 0xbfe00000 ( 14 MB)
.text : 0xc0008000 - 0xc090c424 (9234 kB)
.init : 0xc0a00000 - 0xc0b00000 (1024 kB)
.data : 0xc0b00000 - 0xc0b39fe0 ( 232 kB)
.bss : 0xc0b39fe0 - 0xc0b71c28 ( 224 kB)
Preemptible hierarchical RCU implementation.
Build-time adjustment of leaf fanout to 32.
RCU restricting CPUs from NR_CPUS=4 to nr_cpu_ids=2.
RCU: Adjusting geometry for rcu_fanout_leaf=32, nr_cpu_ids=2
NR_IRQS:16 nr_irqs:16 16
efuse mapped to cf800000
ps7-slcr mapped to cf802000
L2C: platform modifies aux control register: 0x72360000 -> 0x72760000
L2C: DT/platform modifies aux control register: 0x72360000 -> 0x72760000
L2C-310 erratum 769419 enabled
L2C-310 enabling early BRESP for Cortex-A9
L2C-310 full line of zeros enabled for Cortex-A9
L2C-310 ID prefetch enabled, offset 1 lines
L2C-310 dynamic clock gating enabled, standby mode enabled
L2C-310 cache controller enabled, 8 ways, 512 kB
L2C-310: CACHE_ID 0x410000c8, AUX_CTRL 0x76760001
zynq_clock_init: clkc starts at cf802100
Zynq clock init
sched_clock: 64 bits at 333MHz, resolution 3ns, wraps every 4398046511103ns
clocksource: arm_global_timer: mask: 0xffffffffffffffff max_cycles: 0x4ce07af025, max_idle_ns: 440795209040 ns
Switching to timer-based delay loop, resolution 3ns
clocksource: ttc_clocksource: mask: 0xffff max_cycles: 0xffff, max_idle_ns: 537538477 ns
ps7-ttc #0 at cf80a000, irq=18
Console: colour dummy device 80x30
Calibrating delay loop (skipped), value calculated using timer frequency.. 666.66 BogoMIPS (lpj=3333333)
pid_max: default: 32768 minimum: 301
Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
CPU: Testing write buffer coherency: ok
CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
Setting up static identity map for 0x100000 - 0x100058
CPU1: failed to boot: -1
Brought up 1 CPUs
SMP: Total of 1 processors activated (666.66 BogoMIPS).
CPU: All CPU(s) started in SVC mode.
devtmpfs: initialized
VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4
clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
pinctrl core: initialized pinctrl subsystem
NET: Registered protocol family 16
DMA: preallocated 256 KiB pool for atomic coherent allocations
cpuidle: using governor menu
hw-breakpoint: found 5 (+1 reserved) breakpoint and 1 watchpoint registers.
hw-breakpoint: maximum watchpoint size is 4 bytes.
zynq-ocm f800c000.ps7-ocmc: ZYNQ OCM pool: 256 KiB @ 0xcf880000
vgaarb: loaded
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
media: Linux media interface: v0.10
Linux video capture interface: v2.00
pps_core: LinuxPPS API ver. 1 registered
pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
PTP clock support registered
EDAC MC: Ver: 3.0.0
Advanced Linux Sound Architecture Driver Initialized.
clocksource: Switched to clocksource arm_global_timer
NET: Registered protocol family 2
TCP established hash table entries: 2048 (order: 1, 8192 bytes)
TCP bind hash table entries: 2048 (order: 2, 16384 bytes)
TCP: Hash tables configured (established 2048 bind 2048)
UDP hash table entries: 256 (order: 1, 8192 bytes)
UDP-Lite hash table entries: 256 (order: 1, 8192 bytes)
NET: Registered protocol family 1
RPC: Registered named UNIX socket transport module.
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
PCI: CLS 0 bytes, default 64
Trying to unpack rootfs image as initramfs...
rootfs image is not initramfs (no cpio magic); looks like an initrd
Freeing initrd memory: 12792K (cce82000 - cdb00000)
hw perfevents: enabled with armv7_cortex_a9 PMU driver, 7 counters available
futex hash table entries: 512 (order: 3, 32768 bytes)
workingset: timestamp_bits=28 max_order=16 bucket_order=0
jffs2: version 2.2. (NAND) (SUMMARY) © 2001-2006 Red Hat, Inc.
io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered (default)
dma-pl330 f8003000.ps7-dma: Loaded driver for PL330 DMAC-241330
dma-pl330 f8003000.ps7-dma: DBUFF-128x8bytes Num_Chans-8 Num_Peri-4 Num_Events-16
e0000000.serial: ttyPS0 at MMIO 0xe0000000 (irq = 158, base_baud = 6249999) is a xuartps
console [ttyPS0] enabled
xdevcfg f8007000.ps7-dev-cfg: ioremap 0xf8007000 to cf86e000
[drm] Initialized drm 1.1.0 20060810
brd: module loaded
loop: module loaded
CAN device driver interface
gpiod_set_value: invalid GPIO
libphy: MACB_mii_bus: probed
macb e000b000.ethernet eth0: Cadence GEM rev 0x00020118 at 0xe000b000 irq 31 (00:0a:35:00:00:00)
Generic PHY e000b000.etherne:00: attached PHY driver [Generic PHY] (mii_bus:phy_addr=e000b000.etherne:00, irq=-1)
e1000e: Intel(R) PRO/1000 Network Driver - 3.2.6-k
e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
ehci-pci: EHCI PCI platform driver
usbcore: registered new interface driver usb-storage
mousedev: PS/2 mouse device common for all mice
i2c /dev entries driver
Xilinx Zynq CpuIdle Driver started
sdhci: Secure Digital Host Controller Interface driver
sdhci: Copyright(c) Pierre Ossman
sdhci-pltfm: SDHCI platform and OF driver helper
mmc0: SDHCI controller on e0100000.ps7-sdio [e0100000.ps7-sdio] using ADMA
ledtrig-cpu: registered to indicate activity on CPUs
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
nand: device found, Manufacturer ID: 0x2c, Chip ID: 0xda
nand: Micron MT29F2G08ABAEAWP
nand: 256 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 64
nand: WARNING: pl35x-nand: the ECC used on your system is too weak compared to the one required by the NAND chip
Bad block table found at page 131008, version 0x01
Bad block table found at page 130944, version 0x01
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: 7/2, WL threshold: 4096, image sequence number: 262741923
ubi0: available PEBs: 0, total reserved PEBs: 64, PEBs reserved for bad PEB handling: 40
ubi0: background thread "ubi_bgt0d" started, PID 708
UBIFS (ubi0:0): background thread "ubifs_bgt0_0" started, PID 711
UBIFS (ubi0:0): UBIFS: mounted UBI device 0, volume 0, name "configs"
UBIFS (ubi0:0): LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
UBIFS (ubi0:0): FS size: 1396736 bytes (1 MiB, 11 LEBs), journal size 888833 bytes (0 MiB, 5 LEBs)
UBIFS (ubi0:0): reserved for root: 65970 bytes (64 KiB)
UBIFS (ubi0:0): media format: w4/r0 (latest is w4/r0), UUID A9E8BDA4-70DE-45D9-83BE-2DD9F129C0C6, 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: 430/137, WL threshold: 4096, image sequence number: 3563076859
ubi1: available PEBs: 0, total reserved PEBs: 1020, PEBs reserved for bad PEB handling: 36
ubi1: background thread "ubi_bgt1d" started, PID 720
UBIFS (ubi1:0): background thread "ubifs_bgt1_0" started, PID 723
UBIFS (ubi1:0): UBIFS: mounted UBI device 1, volume 0, name "reserve1"
UBIFS (ubi1:0): LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
UBIFS (ubi1:0): FS size: 123039744 bytes (117 MiB, 969 LEBs), journal size 6221824 bytes (5 MiB, 49 LEBs)
UBIFS (ubi1:0): reserved for root: 4952683 bytes (4836 KiB)
UBIFS (ubi1:0): media format: w4/r0 (latest is w4/r0), UUID A21581E4-693A-4BBF-A66A-FCE5ACD2EF7F, 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 = 0xb023
In fpga mem driver!
request_mem_region OK!
fpga mem virtual address is 0xd2000000
random: nonblocking pool is initialized
2020-10-15 11:30:38 driver-btm-api.c:632:init_freq_mode: This is scan-user version
2020-10-15 11:30:38 driver-btm-api.c:1815:bitmain_soc_init: opt_multi_version = 1
2020-10-15 11:30:38 driver-btm-api.c:1816:bitmain_soc_init: opt_bitmain_ab = 1
2020-10-15 11:30:38 driver-btm-api.c:1817:bitmain_soc_init: opt_bitmain_work_mode = 0
2020-10-15 11:30:38 driver-btm-api.c:1818:bitmain_soc_init: Miner compile time: Fri Dec 6 13:23:09 CST 2019 type: Antminer S17+
2020-10-15 11:30:38 driver-btm-api.c:1819:bitmain_soc_init: commit version: c767010 2019-12-04 14:22:30, build by: lol 2019-12-06 13:31:56
2020-10-15 11:30:38 driver-btm-api.c:1655:show_sn: no SN got, please write SN to /nvdata/sn
2020-10-15 11:30:38 fan.c:236:front_fan_power_on: Note: front fan is power on!
2020-10-15 11:30:38 fan.c:248:rear_fan_power_on: Note: rear fan is power on!
2020-10-15 11:30:38 driver-btm-api.c:1110:miner_device_init: Detect 256MB control board of XILINX
2020-10-15 11:30:38 driver-btm-api.c:1058:init_fan_parameter: fan_eft : 0 fan_pwm : 0
2020-10-15 11:30:38 thread.c:731:create_read_nonce_reg_thread: create thread
2020-10-15 11:30:44 driver-btm-api.c:1042:init_miner_version: miner ID : 803c442429e0481c
2020-10-15 11:30:44 driver-btm-api.c:1048:init_miner_version: FPGA Version = 0xB023
2020-10-15 11:30:49 driver-btm-api.c:689:get_product_id: product_id[0] = 0
2020-10-15 11:30:49 driver-btm-api.c:689:get_product_id: product_id[1] = 0
2020-10-15 11:30:49 driver-btm-api.c:689:get_product_id: product_id[2] = 0
2020-10-15 11:30:49 driver-btm-api.c:645:_set_project_type: project:0
2020-10-15 11:30:49 driver-btm-api.c:665:_set_project_type: Project type: Antminer S17+
2020-10-15 11:30:49 driver-btm-api.c:676:dump_pcb_bom_version: Chain [0] PCB Version: 0x0100
2020-10-15 11:30:49 driver-btm-api.c:677:dump_pcb_bom_version: Chain [0] BOM Version: 0x0100
2020-10-15 11:30:49 driver-btm-api.c:676:dump_pcb_bom_version: Chain [1] PCB Version: 0x0100
2020-10-15 11:30:49 driver-btm-api.c:677:dump_pcb_bom_version: Chain [1] BOM Version: 0x0100
2020-10-15 11:30:49 driver-btm-api.c:676:dump_pcb_bom_version: Chain [2] PCB Version: 0x0100
2020-10-15 11:30:49 driver-btm-api.c:677:dump_pcb_bom_version: Chain [2] BOM Version: 0x0100
2020-10-15 11:30:53 driver-btm-api.c:1764:bitmain_board_init: Fan check passed.
2020-10-15 11:30:54 board.c:36:jump_and_app_check_restore_pic: chain[0] PIC jump to app
2020-10-15 11:30:56 board.c:40:jump_and_app_check_restore_pic: Check chain[0] PIC fw version=0x88
2020-10-15 11:30:57 board.c:36:jump_and_app_check_restore_pic: chain[1] PIC jump to app
2020-10-15 11:31:00 board.c:40:jump_and_app_check_restore_pic: Check chain[1] PIC fw version=0x88
2020-10-15 11:31:01 board.c:36:jump_and_app_check_restore_pic: chain[2] PIC jump to app
2020-10-15 11:31:03 board.c:40:jump_and_app_check_restore_pic: Check chain[2] PIC fw version=0x88
2020-10-15 11:31:03 thread.c:726:create_pic_heart_beat_thread: create thread
2020-10-15 11:31:03 power_api.c:208:power_init: Power init:
2020-10-15 11:31:03 power_api.c:209:power_init: current_voltage_raw = 0
2020-10-15 11:31:03 power_api.c:210:power_init: highest_voltage_raw = 2100
2020-10-15 11:31:03 power_api.c:211:power_init: working_voltage_raw = 1950
2020-10-15 11:31:03 power_api.c:212:power_init: higher_voltage_raw = 2040
2020-10-15 11:31:03 driver-btm-api.c:1774:bitmain_board_init: Enter 30s sleep to make sure power release finish.
2020-10-15 11:31:03 power_api.c:182:power_off: init gpio907
2020-10-15 11:31:35 power_api.c:262:set_to_highest_voltage: Set to voltage raw 2100, one step.
2020-10-15 11:31:37 power_api.c:83:check_voltage_multi: retry time: 0
2020-10-15 11:31:38 power_api.c:38:_get_avg_voltage: chain = 0, voltage = 21.119138
2020-10-15 11:31:39 power_api.c:38:_get_avg_voltage: chain = 1, voltage = 21.135375
2020-10-15 11:31:40 power_api.c:38:_get_avg_voltage: chain = 2, voltage = 21.081529
2020-10-15 11:31:40 power_api.c:51:_get_avg_voltage: average_voltage = 21.112014
2020-10-15 11:31:40 power_api.c:69:check_voltage: target_vol = 21.00, actural_vol = 21.11, check voltage passed.
2020-10-15 11:31:40 uart.c:71:set_baud: set fpga_baud to 115200
2020-10-15 11:31:40 driver-hash-chip.c:245:dhash_chip_set_baud_v2: chain[0]: chip baud = 115200, chip_divider = 26
2020-10-15 11:31:40 driver-hash-chip.c:245:dhash_chip_set_baud_v2: chain[1]: chip baud = 115200, chip_divider = 26
2020-10-15 11:31:40 driver-hash-chip.c:245:dhash_chip_set_baud_v2: chain[2]: chip baud = 115200, chip_divider = 26
2020-10-15 11:31:51 driver-btm-api.c:982:check_asic_number_with_power_on: Chain[0]: find 65 asic, times 0
2020-10-15 11:32:02 driver-btm-api.c:982:check_asic_number_with_power_on: Chain[1]: find 65 asic, times 0
2020-10-15 11:32:13 driver-btm-api.c:982:check_asic_number_with_power_on: Chain[2]: find 0 asic, times 0
2020-10-15 11:32:24 driver-btm-api.c:982:check_asic_number_with_power_on: Chain[2]: find 0 asic, times 1
2020-10-15 11:32:34 driver-btm-api.c:982:check_asic_number_with_power_on: Chain[2]: find 0 asic, times 2
2020-10-15 11:32:34 driver-btm-api.c:1010:check_asic_number: Chain 2 only find 0 asic, will power off hash board 2
2020-10-15 11:32:35 driver-btm-api.c:1012:check_asic_number: Chain 2 voltage: an0 = 2.793548, an2 2.803226, an6 2.535484.
2020-10-15 11:32:42 driver-hash-chip.c:266:set_uart_relay: set uart relay to 0x330003
2020-10-15 11:32:42 driver-btm-api.c:352:set_order_clock: chain[0]: set order clock, stragegy 3
2020-10-15 11:32:42 driver-btm-api.c:352:set_order_clock: chain[1]: set order clock, stragegy 3
2020-10-15 11:32:42 driver-hash-chip.c:502:set_clock_delay_control: core_data = 0x34
2020-10-15 11:32:42 voltage[0] = 1940
2020-10-15 11:32:42 voltage[1] = 1940
2020-10-15 11:32:42 power_api.c:220:set_working_voltage_raw: working_voltage_raw = 1940
2020-10-15 11:32:43 temperature.c:314:calibrate_temp_sensor_one_chain: chain 0 temp sensor NCT218
2020-10-15 11:32:45 temperature.c:314:calibrate_temp_sensor_one_chain: chain 1 temp sensor NCT218
2020-10-15 11:32:45 uart.c:71:set_baud: set fpga_baud to 12000000
2020-10-15 11:32:45 driver-hash-chip.c:245:dhash_chip_set_baud_v2: chain[0]: chip baud = 12000000, chip_divider = 3
2020-10-15 11:32:45 driver-hash-chip.c:245:dhash_chip_set_baud_v2: chain[1]: chip baud = 12000000, chip_divider = 3
2020-10-15 11:32:46 driver-btm-api.c:241:check_bringup_temp: Bring up temperature is 16
2020-10-15 11:32:46 thread.c:746:create_check_miner_status_thread: create thread
2020-10-15 11:32:46 thread.c:736:create_show_miner_status_thread: create thread
2020-10-15 11:32:46 thread.c:721:create_temperature_monitor_thread: create thread
2020-10-15 11:32:46 freq_tuning.c:145:freq_tuning_get_max_freq: Max freq of tuning is 650
2020-10-15 11:32:46 frequency.c:770:inc_freq_with_fixed_vco: chain = 255, freq = 560, is_higher_voltage = true
2020-10-15 11:32:54 power_api.c:346:set_to_voltage_by_steps: Set to voltage raw 2090, step by step.
2020-10-15 11:32:56 power_api.c:83:check_voltage_multi: retry time: 0
2020-10-15 11:32:57 power_api.c:38:_get_avg_voltage: chain = 0, voltage = 20.924049
2020-10-15 11:32:58 power_api.c:38:_get_avg_voltage: chain = 1, voltage = 20.963010
2020-10-15 11:32:58 power_api.c:51:_get_avg_voltage: average_voltage = 20.943530
2020-10-15 11:32:58 power_api.c:69:check_voltage: target_vol = 20.90, actural_vol = 20.94, check voltage passed.
2020-10-15 11:32:59 power_api.c:346:set_to_voltage_by_steps: Set to voltage raw 2070, step by step.
2020-10-15 11:33:00 power_api.c:83:check_voltage_multi: retry time: 0
2020-10-15 11:33:01 power_api.c:38:_get_avg_voltage: chain = 0, voltage = 20.731644
2020-10-15 11:33:02 power_api.c:38:_get_avg_voltage: chain = 1, voltage = 20.769132
2020-10-15 11:33:02 power_api.c:51:_get_avg_voltage: average_voltage = 20.750388
2020-10-15 11:33:02 power_api.c:69:check_voltage: target_vol = 20.70, actural_vol = 20.75, check voltage passed.
2020-10-15 11:33:02 frequency.c:840:inc_asic_diff_freq_by_steps: chain = 0, start = 560, freq_step = 5
2020-10-15 11:33:09 frequency.c:840:inc_asic_diff_freq_by_steps: chain = 1, start = 560, freq_step = 5
2020-10-15 11:33:13 driver-btm-api.c:618:set_timeout: freq = 610, percent = 90, hcn = 44236, timeout = 72
2020-10-15 11:33:13 power_api.c:226:set_higher_voltage_raw: higher_voltage_raw = 2040
2020-10-15 11:33:13 power_api.c:332:set_to_higher_voltage_by_steps: Set to voltage raw 2040, step by step.
2020-10-15 11:33:15 power_api.c:83:check_voltage_multi: retry time: 0
2020-10-15 11:33:17 power_api.c:38:_get_avg_voltage: chain = 0, voltage = 20.443037
2020-10-15 11:33:18 power_api.c:38:_get_avg_voltage: chain = 1, voltage = 20.454081
2020-10-15 11:33:18 power_api.c:51:_get_avg_voltage: average_voltage = 20.448559
2020-10-15 11:33:18 power_api.c:69:check_voltage: target_vol = 20.40, actural_vol = 20.45, check voltage passed.
2020-10-15 11:33:18 thread.c:741:create_check_system_status_thread: create thread
2020-10-15 11:33:18 driver-btm-api.c:1919:bitmain_soc_init: Init done!
2020-10-15 11:33:18 driver-btm-api.c:194:set_miner_status: STATUS_INIT
2020-10-15 11:33:23 driver-btm-api.c:194:set_miner_status: STATUS_OKAY
2020-10-15 11:33:24 frequency.c:129:get_ideal_hash_rate_GH: ideal_hash_rate = 49572
2020-10-15 11:33:24 frequency.c:145:get_sale_hash_rate_GH: sale_hash_rate = 49000
2020-10-15 11:33:29 driver-btm-api.c:1292:dhash_chip_send_job: Version num 4
2020-10-15 11:33:33 thread.c:390:check_working_voltage: current PCB min temperature is 30
2020-10-15 11:33:33 thread.c:391:check_working_voltage: current voltage is 2040, recovery to 1940
2020-10-15 11:33:33 power_api.c:304:set_to_working_voltage_by_steps: Set to voltage raw 1940, step by step.
2020-10-15 11:33:38 power_api.c:83:check_voltage_multi: retry time: 0
2020-10-15 11:33:39 power_api.c:38:_get_avg_voltage: chain = 0, voltage = 19.481012
2020-10-15 11:33:40 power_api.c:38:_get_avg_voltage: chain = 1, voltage = 19.484694
2020-10-15 11:33:40 power_api.c:51:_get_avg_voltage: average_voltage = 19.482853
2020-10-15 11:33:40 power_api.c:69:check_voltage: target_vol = 19.40, actural_vol = 19.48, check voltage passed.
2020-10-15 12:03:40 thread.c:214:calc_hashrate_avg: avg rate is 50388.11 in 30 mins
2020-10-15 12:03:40 temperature.c:482:temp_statistics_show: pcb temp 33~64 chip temp 53~79
2020-10-15 12:33:42 thread.c:214:calc_hashrate_avg: avg rate is 50508.59 in 30 mins
2020-10-15 12:33:42 temperature.c:482:temp_statistics_show: pcb temp 36~64 chip temp 56~80
2020-10-15 13:03:43 thread.c:214:calc_hashrate_avg: avg rate is 50827.84 in 30 mins
2020-10-15 13:03:43 temperature.c:482:temp_statistics_show: pcb temp 35~64 chip temp 56~79
2020-10-15 13:33:44 thread.c:214:calc_hashrate_avg: avg rate is 50653.24 in 30 mins
2020-10-15 13:33:44 temperature.c:482:temp_statistics_show: pcb temp 36~65 chip temp 57~81
.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: mtnrotary on December 21, 2020, 06:23:36 PM
Worker 3 Booting Linux on physical CPU 0x0
Linux version 4.6.0-xilinx-gff8137b-dirty (lzq@armdev2) (gcc version 4.8.3 20140320 (prerelease) (Sourcery CodeBench Lite 2014.05-23) ) #25 SMP PREEMPT Fri Nov 23 15:30:52 CST 2018
CPU: ARMv7 Processor [413fc090] revision 0 (ARMv7), cr=18c5387d
CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
Machine model: Xilinx Zynq
cma: Reserved 16 MiB at 0x0e000000
Memory policy: Data cache writealloc
On node 0 totalpages: 61440
free_area_init_node: node 0, pgdat c0b39280, node_mem_map cde10000
Normal zone: 480 pages used for memmap
Normal zone: 0 pages reserved
Normal zone: 61440 pages, LIFO batch:15
percpu: Embedded 12 pages/cpu @cddf1000 s19776 r8192 d21184 u49152
pcpu-alloc: s19776 r8192 d21184 u49152 alloc=12*4096
pcpu-alloc: [0] 0 [0] 1
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 60960
Kernel command line: mem=240M console=ttyPS0,115200 ramdisk_size=33554432 root=/dev/ram rw earlyprintk
PID hash table entries: 1024 (order: 0, 4096 bytes)
Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
Memory: 203432K/245760K available (6345K kernel code, 231K rwdata, 1896K rodata, 1024K init, 223K bss, 25944K reserved, 16384K cma-reserved, 0K highmem)
Virtual kernel memory layout:
vector : 0xffff0000 - 0xffff1000 ( 4 kB)
fixmap : 0xffc00000 - 0xfff00000 (3072 kB)
vmalloc : 0xcf800000 - 0xff800000 ( 768 MB)
lowmem : 0xc0000000 - 0xcf000000 ( 240 MB)
pkmap : 0xbfe00000 - 0xc0000000 ( 2 MB)
modules : 0xbf000000 - 0xbfe00000 ( 14 MB)
.text : 0xc0008000 - 0xc090c424 (9234 kB)
.init : 0xc0a00000 - 0xc0b00000 (1024 kB)
.data : 0xc0b00000 - 0xc0b39fe0 ( 232 kB)
.bss : 0xc0b39fe0 - 0xc0b71c28 ( 224 kB)
Preemptible hierarchical RCU implementation.
Build-time adjustment of leaf fanout to 32.
RCU restricting CPUs from NR_CPUS=4 to nr_cpu_ids=2.
RCU: Adjusting geometry for rcu_fanout_leaf=32, nr_cpu_ids=2
NR_IRQS:16 nr_irqs:16 16
efuse mapped to cf800000
ps7-slcr mapped to cf802000
L2C: platform modifies aux control register: 0x72360000 -> 0x72760000
L2C: DT/platform modifies aux control register: 0x72360000 -> 0x72760000
L2C-310 erratum 769419 enabled
L2C-310 enabling early BRESP for Cortex-A9
L2C-310 full line of zeros enabled for Cortex-A9
L2C-310 ID prefetch enabled, offset 1 lines
L2C-310 dynamic clock gating enabled, standby mode enabled
L2C-310 cache controller enabled, 8 ways, 512 kB
L2C-310: CACHE_ID 0x410000c8, AUX_CTRL 0x76760001
zynq_clock_init: clkc starts at cf802100
Zynq clock init
sched_clock: 64 bits at 333MHz, resolution 3ns, wraps every 4398046511103ns
clocksource: arm_global_timer: mask: 0xffffffffffffffff max_cycles: 0x4ce07af025, max_idle_ns: 440795209040 ns
Switching to timer-based delay loop, resolution 3ns
clocksource: ttc_clocksource: mask: 0xffff max_cycles: 0xffff, max_idle_ns: 537538477 ns
ps7-ttc #0 at cf80a000, irq=18
Console: colour dummy device 80x30
Calibrating delay loop (skipped), value calculated using timer frequency.. 666.66 BogoMIPS (lpj=3333333)
pid_max: default: 32768 minimum: 301
Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
CPU: Testing write buffer coherency: ok
CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
Setting up static identity map for 0x100000 - 0x100058
CPU1: failed to boot: -1
Brought up 1 CPUs
SMP: Total of 1 processors activated (666.66 BogoMIPS).
CPU: All CPU(s) started in SVC mode.
devtmpfs: initialized
VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4
clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
pinctrl core: initialized pinctrl subsystem
NET: Registered protocol family 16
DMA: preallocated 256 KiB pool for atomic coherent allocations
cpuidle: using governor menu
hw-breakpoint: found 5 (+1 reserved) breakpoint and 1 watchpoint registers.
hw-breakpoint: maximum watchpoint size is 4 bytes.
zynq-ocm f800c000.ps7-ocmc: ZYNQ OCM pool: 256 KiB @ 0xcf880000
vgaarb: loaded
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
media: Linux media interface: v0.10
Linux video capture interface: v2.00
pps_core: LinuxPPS API ver. 1 registered
pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
PTP clock support registered
EDAC MC: Ver: 3.0.0
Advanced Linux Sound Architecture Driver Initialized.
clocksource: Switched to clocksource arm_global_timer
NET: Registered protocol family 2
TCP established hash table entries: 2048 (order: 1, 8192 bytes)
TCP bind hash table entries: 2048 (order: 2, 16384 bytes)
TCP: Hash tables configured (established 2048 bind 2048)
UDP hash table entries: 256 (order: 1, 8192 bytes)
UDP-Lite hash table entries: 256 (order: 1, 8192 bytes)
NET: Registered protocol family 1
RPC: Registered named UNIX socket transport module.
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
PCI: CLS 0 bytes, default 64
Trying to unpack rootfs image as initramfs...
rootfs image is not initramfs (no cpio magic); looks like an initrd
Freeing initrd memory: 12904K (cce67000 - 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
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: 13/4, WL threshold: 4096, image sequence number: 262741923
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 A9E8BDA4-70DE-45D9-83BE-2DD9F129C0C6, 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: 347/120, WL threshold: 4096, image sequence number: 3563076859
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 A21581E4-693A-4BBF-A66A-FCE5ACD2EF7F, 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 = 0xb023
In fpga mem driver!
request_mem_region OK!
fpga mem virtual address is 0xd2000000
random: nonblocking pool is initialized
macb e000b000.ethernet eth0: link down
macb e000b000.ethernet eth0: unable to generate target frequency: 25000000 Hz
macb e000b000.ethernet eth0: link up (100/Full)
2020-10-14 20:34:55 driver-btm-api.c:779:init_freq_mode: This is scan-user version
2020-10-14 20:34:55 driver-btm-api.c:2451:bitmain_soc_init: opt_multi_version = 1
2020-10-14 20:34:55 driver-btm-api.c:2452:bitmain_soc_init: opt_bitmain_ab = 1
2020-10-14 20:34:55 driver-btm-api.c:2453:bitmain_soc_init: opt_bitmain_work_mode = 0
2020-10-14 20:34:55 driver-btm-api.c:2454:bitmain_soc_init: Miner compile time: Tue Jun 2 10:31:07 CST 2020 type: Antminer S17+
2020-10-14 20:34:55 driver-btm-api.c:2455:bitmain_soc_init: commit version: 1ca50a5 2020-06-01 18:51:22, build by: lol 2020-06-02 10:37:21
2020-10-14 20:34:55 driver-btm-api.c:2083:show_sn: len:16, 8070642a18c0885c
2020-10-14 20:34:55 driver-btm-api.c:2461:bitmain_soc_init: show sn return 1
2020-10-14 20:34:55 driver-btm-api.c:2103:handle_sn_for_factory_mode: show sn return 1
2020-10-14 20:34:55 driver-btm-api.c:2141:handle_sn_for_factory_mode: read sn success, 8070642a18c0885c
2020-10-14 20:34:55 fan.c:284:front_fan_power_on: Note: front fan is power on!
2020-10-14 20:34:55 fan.c:296:rear_fan_power_on: Note: rear fan is power on!
2020-10-14 20:34:55 driver-btm-api.c:1314:miner_device_init: Detect 256MB control board of XILINX
2020-10-14 20:34:55 driver-btm-api.c:1255:init_fan_parameter: fan_eft : 0 fan_pwm : 0
2020-10-14 20:35:01 driver-btm-api.c:1239:init_miner_version: miner ID : 8070642a18c0885c
2020-10-14 20:35:01 driver-btm-api.c:1245:init_miner_version: FPGA Version = 0xB023
2020-10-14 20:35:06 driver-btm-api.c:837:get_product_id: product_id[0] = 0
2020-10-14 20:35:06 driver-btm-api.c:837:get_product_id: product_id[1] = 0
2020-10-14 20:35:06 driver-btm-api.c:837:get_product_id: product_id[2] = 0
2020-10-14 20:35:06 driver-btm-api.c:2234:update_conf_by_power_feedback: Power feedback is disabled
2020-10-14 20:35:06 driver-btm-api.c:2202:get_calibration_voltage: calibration voltage flag is error data.
2020-10-14 20:35:06 driver-btm-api.c:2268:update_conf_by_power_feedback: Note: no calibration voltage, default diff = 0
2020-10-14 20:35:06 frequency.c:1457:adjust_higer_max_vol_table: adjust_higer_max_vol_table, adjust_vol = 0
2020-10-14 20:35:06 thread.c:1363:create_read_nonce_reg_thread: create thread
2020-10-14 20:35:12 driver-btm-api.c:1239:init_miner_version: miner ID : 8070642a18c0885c
2020-10-14 20:35:12 driver-btm-api.c:1245:init_miner_version: FPGA Version = 0xB023
2020-10-14 20:35:18 driver-btm-api.c:837:get_product_id: product_id[0] = 0
2020-10-14 20:35:18 driver-btm-api.c:837:get_product_id: product_id[1] = 0
2020-10-14 20:35:18 driver-btm-api.c:837:get_product_id: product_id[2] = 0
2020-10-14 20:35:18 driver-btm-api.c:792:_set_project_type: project:0
2020-10-14 20:35:18 driver-btm-api.c:813:_set_project_type: Project type: Antminer S17+
2020-10-14 20:35:18 driver-btm-api.c:824:dump_pcb_bom_version: Chain [0] PCB Version: 0x0100
2020-10-14 20:35:18 driver-btm-api.c:825:dump_pcb_bom_version: Chain [0] BOM Version: 0x0100
2020-10-14 20:35:18 driver-btm-api.c:824:dump_pcb_bom_version: Chain [1] PCB Version: 0x0100
2020-10-14 20:35:18 driver-btm-api.c:825:dump_pcb_bom_version: Chain [1] BOM Version: 0x0100
2020-10-14 20:35:18 driver-btm-api.c:824:dump_pcb_bom_version: Chain [2] PCB Version: 0x0100
2020-10-14 20:35:18 driver-btm-api.c:825:dump_pcb_bom_version: Chain [2] BOM Version: 0x0100
2020-10-14 20:35:18 driver-btm-api.c:2372:bitmain_board_init: Fan check passed.
2020-10-14 20:35:19 board.c:36:jump_and_app_check_restore_pic: chain[0] PIC jump to app
2020-10-14 20:35:21 board.c:40:jump_and_app_check_restore_pic: Check chain[0] PIC fw version=0x88
2020-10-14 20:35:22 board.c:36:jump_and_app_check_restore_pic: chain[1] PIC jump to app
2020-10-14 20:35:24 board.c:40:jump_and_app_check_restore_pic: Check chain[1] PIC fw version=0x88
2020-10-14 20:35:25 board.c:36:jump_and_app_check_restore_pic: chain[2] PIC jump to app
2020-10-14 20:35:27 board.c:40:jump_and_app_check_restore_pic: Check chain[2] PIC fw version=0x88
2020-10-14 20:35:27 thread.c:1358:create_pic_heart_beat_thread: create thread
2020-10-14 20:35:27 power_api.c:213:power_init: Power init:
2020-10-14 20:35:27 power_api.c:214:power_init: current_voltage_raw = 0
2020-10-14 20:35:27 power_api.c:215:power_init: highest_voltage_raw = 2100
2020-10-14 20:35:27 power_api.c:216:power_init: working_voltage_raw = 1950
2020-10-14 20:35:27 power_api.c:217:power_init: higher_voltage_raw = 2040
2020-10-14 20:35:27 power_api.c:218:power_init: check_asic_voltage_raw = 2100
2020-10-14 20:35:27 driver-btm-api.c:2382:bitmain_board_init: Enter 30s sleep to make sure power release finish.
2020-10-14 20:35:27 power_api.c:186:power_off: init gpio907
2020-10-14 20:35:59 power_api.c:324:set_to_highest_voltage_by_steps: Set to voltage raw 2100, step by step.
2020-10-14 20:36:25 power_api.c:85:check_voltage_multi: retry time: 0
2020-10-14 20:36:26 power_api.c:40:_get_avg_voltage: chain = 0, voltage = 21.175572
2020-10-14 20:36:27 power_api.c:40:_get_avg_voltage: chain = 1, voltage = 21.027955
2020-10-14 20:36:28 power_api.c:40:_get_avg_voltage: chain = 2, voltage = 21.003812
2020-10-14 20:36:28 power_api.c:53:_get_avg_voltage: average_voltage = 21.069113
2020-10-14 20:36:28 power_api.c:71:check_voltage: target_vol = 21.00, actural_vol = 21.07, check voltage passed.
2020-10-14 20:36:28 uart.c:72:set_baud: set fpga_baud to 115200
2020-10-14 20:36:39 driver-btm-api.c:1134:check_asic_number_with_power_on: Chain[0]: find 0 asic, times 0
2020-10-14 20:36:50 driver-btm-api.c:1134:check_asic_number_with_power_on: Chain[0]: find 0 asic, times 1
2020-10-14 20:37:01 driver-btm-api.c:1134:check_asic_number_with_power_on: Chain[0]: find 0 asic, times 2
2020-10-14 20:37:01 power_api.c:380:modify_check_asic_voltage: check_asic_voltage_raw = 2100
chain 0, IO_DRIVE_STRENGTH_CONFIGURATION reg = 0x f1fffff
2020-10-14 20:37:09 driver-btm-api.c:1157:check_asic_number_with_power_on: Chain[0]: find 0 asic, times 3
2020-10-14 20:37:09 power_api.c:380:modify_check_asic_voltage: check_asic_voltage_raw = 2050
2020-10-14 20:37:09 power_api.c:364:set_to_check_asic_voltage_by_steps: Set to voltage raw 2050, step by step.
2020-10-14 20:37:13 power_api.c:85:check_voltage_multi: retry time: 0
2020-10-14 20:37:15 power_api.c:40:_get_avg_voltage: chain = 0, voltage = 20.641678
2020-10-14 20:37:16 power_api.c:40:_get_avg_voltage: chain = 1, voltage = 20.522900
2020-10-14 20:37:17 power_api.c:40:_get_avg_voltage: chain = 2, voltage = 20.520966
2020-10-14 20:37:17 power_api.c:53:_get_avg_voltage: average_voltage = 20.561848
2020-10-14 20:37:17 power_api.c:71:check_voltage: target_vol = 20.50, actural_vol = 20.56, check voltage passed.
chain 0, IO_DRIVE_STRENGTH_CONFIGURATION reg = 0x f1fffff
2020-10-14 20:37:26 driver-btm-api.c:1157:check_asic_number_with_power_on: Chain[0]: find 0 asic, times 4
2020-10-14 20:37:26 power_api.c:380:modify_check_asic_voltage: check_asic_voltage_raw = 2000
2020-10-14 20:37:26 power_api.c:364:set_to_check_asic_voltage_by_steps: Set to voltage raw 2000, step by step.
2020-10-14 20:37:29 power_api.c:85:check_voltage_multi: retry time: 0
2020-10-14 20:37:30 power_api.c:40:_get_avg_voltage: chain = 0, voltage = 20.134689
2020-10-14 20:37:31 power_api.c:40:_get_avg_voltage: chain = 1, voltage = 20.039440
2020-10-14 20:37:32 power_api.c:40:_get_avg_voltage: chain = 2, voltage = 20.038120
2020-10-14 20:37:32 power_api.c:53:_get_avg_voltage: average_voltage = 20.070750
2020-10-14 20:37:32 power_api.c:71:check_voltage: target_vol = 20.00, actural_vol = 20.07, check voltage passed.
chain 0, IO_DRIVE_STRENGTH_CONFIGURATION reg = 0x f1fffff
2020-10-14 20:37:41 driver-btm-api.c:1157:check_asic_number_with_power_on: Chain[0]: find 0 asic, times 5
2020-10-14 20:37:41 power_api.c:380:modify_check_asic_voltage: check_asic_voltage_raw = 2100
2020-10-14 20:37:41 power_api.c:364:set_to_check_asic_voltage_by_steps: Set to voltage raw 2100, step by step.
2020-10-14 20:37:46 power_api.c:85:check_voltage_multi: retry time: 0
2020-10-14 20:37:47 power_api.c:40:_get_avg_voltage: chain = 0, voltage = 21.124524
2020-10-14 20:37:48 power_api.c:40:_get_avg_voltage: chain = 1, voltage = 21.030534
2020-10-14 20:37:50 power_api.c:40:_get_avg_voltage: chain = 2, voltage = 21.003812
2020-10-14 20:37:50 power_api.c:53:_get_avg_voltage: average_voltage = 21.052957
2020-10-14 20:37:50 power_api.c:71:check_voltage: target_vol = 21.00, actural_vol = 21.05, check voltage passed.
2020-10-14 20:37:50 driver-btm-api.c:1193:check_asic_number: Chain 0 only find 0 asic, will power off hash board 0
2020-10-14 20:37:51 driver-btm-api.c:1195:check_asic_number: Chain 0 voltage: an0 = 2.825806, an2 2.822581, an6 2.538710.
2020-10-14 20:38:02 driver-btm-api.c:1134:check_asic_number_with_power_on: Chain[1]: find 0 asic, times 0
2020-10-14 20:38:13 driver-btm-api.c:1134:check_asic_number_with_power_on: Chain[1]: find 0 asic, times 1
2020-10-14 20:38:24 driver-btm-api.c:1134:check_asic_number_with_power_on: Chain[1]: find 0 asic, times 2
2020-10-14 20:38:24 power_api.c:380:modify_check_asic_voltage: check_asic_voltage_raw = 2100
chain 1, IO_DRIVE_STRENGTH_CONFIGURATION reg = 0x f1fffff
2020-10-14 20:38:33 driver-btm-api.c:1157:check_asic_number_with_power_on: Chain[1]: find 0 asic, times 3
2020-10-14 20:38:33 power_api.c:380:modify_check_asic_voltage: check_asic_voltage_raw = 2050
2020-10-14 20:38:33 power_api.c:364:set_to_check_asic_voltage_by_steps: Set to voltage raw 2050, step by step.
2020-10-14 20:38:36 power_api.c:85:check_voltage_multi: retry time: 0
2020-10-14 20:38:37 power_api.c:40:_get_avg_voltage: chain = 1, voltage = 20.520966
2020-10-14 20:38:38 power_api.c:40:_get_avg_voltage: chain = 2, voltage = 20.520966
2020-10-14 20:38:38 power_api.c:53:_get_avg_voltage: average_voltage = 20.520966
2020-10-14 20:38:38 power_api.c:71:check_voltage: target_vol = 20.50, actural_vol = 20.52, check voltage passed.
chain 1, IO_DRIVE_STRENGTH_CONFIGURATION reg = 0x f1fffff
2020-10-14 20:38:47 driver-btm-api.c:1157:check_asic_number_with_power_on: Chain[1]: find 0 asic, times 4
2020-10-14 20:38:47 power_api.c:380:modify_check_asic_voltage: check_asic_voltage_raw = 2000
2020-10-14 20:38:47 power_api.c:364:set_to_check_asic_voltage_by_steps: Set to voltage raw 2000, step by step.
2020-10-14 20:38:50 power_api.c:85:check_voltage_multi: retry time: 0
2020-10-14 20:38:51 power_api.c:40:_get_avg_voltage: chain = 1, voltage = 20.013978
2020-10-14 20:38:52 power_api.c:40:_get_avg_voltage: chain = 2, voltage = 20.013978
2020-10-14 20:38:52 power_api.c:53:_get_avg_voltage: average_voltage = 20.013978
2020-10-14 20:38:52 power_api.c:71:check_voltage: target_vol = 20.00, actural_vol = 20.01, check voltage passed.
chain 1, IO_DRIVE_STRENGTH_CONFIGURATION reg = 0x f1fffff
2020-10-14 20:39:01 driver-btm-api.c:1157:check_asic_number_with_power_on: Chain[1]: find 0 asic, times 5
2020-10-14 20:39:01 power_api.c:380:modify_check_asic_voltage: check_asic_voltage_raw = 2100
2020-10-14 20:39:01 power_api.c:364:set_to_check_asic_voltage_by_steps: Set to voltage raw 2100, step by step.
2020-10-14 20:39:06 power_api.c:85:check_voltage_multi: retry time: 0
2020-10-14 20:39:07 power_api.c:40:_get_avg_voltage: chain = 1, voltage = 21.003812
2020-10-14 20:39:08 power_api.c:40:_get_avg_voltage: chain = 2, voltage = 21.003812
2020-10-14 20:39:08 power_api.c:53:_get_avg_voltage: average_voltage = 21.003812
2020-10-14 20:39:08 power_api.c:71:check_voltage: target_vol = 21.00, actural_vol = 21.00, check voltage passed.
2020-10-14 20:39:08 driver-btm-api.c:1193:check_asic_number: Chain 1 only find 0 asic, will power off hash board 1
2020-10-14 20:39:09 driver-btm-api.c:1195:check_asic_number: Chain 1 voltage: an0 = 2.812903, an2 2.806452, an6 2.535484.
2020-10-14 20:39:21 driver-btm-api.c:1134:check_asic_number_with_power_on: Chain[2]: find 0 asic, times 0
2020-10-14 20:39:32 driver-btm-api.c:1134:check_asic_number_with_power_on: Chain[2]: find 8 asic, times 1
2020-10-14 20:39:43 driver-btm-api.c:1134:check_asic_number_with_power_on: Chain[2]: find 0 asic, times 2
2020-10-14 20:39:43 power_api.c:380:modify_check_asic_voltage: check_asic_voltage_raw = 2100
chain 2, IO_DRIVE_STRENGTH_CONFIGURATION reg = 0x f1fffff
2020-10-14 20:39:51 driver-btm-api.c:1157:check_asic_number_with_power_on: Chain[2]: find 0 asic, times 3
2020-10-14 20:39:51 power_api.c:380:modify_check_asic_voltage: check_asic_voltage_raw = 2050
2020-10-14 20:39:51 power_api.c:364:set_to_check_asic_voltage_by_steps: Set to voltage raw 2050, step by step.
2020-10-14 20:39:55 power_api.c:85:check_voltage_multi: retry time: 0
2020-10-14 20:39:56 power_api.c:40:_get_avg_voltage: chain = 2, voltage = 20.494923
2020-10-14 20:39:56 power_api.c:53:_get_avg_voltage: average_voltage = 20.494923
2020-10-14 20:39:56 power_api.c:71:check_voltage: target_vol = 20.50, actural_vol = 20.49, check voltage passed.
chain 2, IO_DRIVE_STRENGTH_CONFIGURATION reg = 0x f1fffff
2020-10-14 20:40:05 driver-btm-api.c:1157:check_asic_number_with_power_on: Chain[2]: find 0 asic, times 4
2020-10-14 20:40:05 power_api.c:380:modify_check_asic_voltage: check_asic_voltage_raw = 2000
2020-10-14 20:40:05 power_api.c:364:set_to_check_asic_voltage_by_steps: Set to voltage raw 2000, step by step.
2020-10-14 20:40:08 power_api.c:85:check_voltage_multi: retry time: 0
2020-10-14 20:40:10 power_api.c:40:_get_avg_voltage: chain = 2, voltage = 20.012689
2020-10-14 20:40:10 power_api.c:53:_get_avg_voltage: average_voltage = 20.012689
2020-10-14 20:40:10 power_api.c:71:check_voltage: target_vol = 20.00, actural_vol = 20.01, check voltage passed.
chain 2, IO_DRIVE_STRENGTH_CONFIGURATION reg = 0x f1fffff
2020-10-14 20:40:18 driver-btm-api.c:1157:check_asic_number_with_power_on: Chain[2]: find 0 asic, times 5
2020-10-14 20:40:18 power_api.c:380:modify_check_asic_voltage: check_asic_voltage_raw = 2100
2020-10-14 20:40:18 power_api.c:364:set_to_check_asic_voltage_by_steps: Set to voltage raw 2100, step by step.
2020-10-14 20:40:23 power_api.c:85:check_voltage_multi: retry time: 0
2020-10-14 20:40:25 power_api.c:40:_get_avg_voltage: chain = 2, voltage = 20.977156
2020-10-14 20:40:25 power_api.c:53:_get_avg_voltage: average_voltage = 20.977156
2020-10-14 20:40:25 power_api.c:71:check_voltage: target_vol = 21.00, actural_vol = 20.98, check voltage passed.
2020-10-14 20:40:25 driver-btm-api.c:1193:check_asic_number: Chain 2 only find 0 asic, will power off hash board 2
2020-10-14 20:40:26 driver-btm-api.c:1195:check_asic_number: Chain 2 voltage: an0 = 2.819355, an2 2.806452, an6 2.541935.
2020-10-14 20:40:27 driver-btm-api.c:222:set_miner_status: ERROR_SOC_INIT
2020-10-14 20:40:27 driver-btm-api.c:156:stop_mining: stop mining: soc init failed!
2020-10-14 20:40:27 thread.c:1403:cancel_read_nonce_reg_thread: cancel thread
2020-10-14 20:40:27 driver-btm-api.c:141:killall_hashboard: ****power off hashboard****
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: favebook on December 21, 2020, 08:37:47 PM
What helped me is to use other miner to heat up the one that I am about to boot. After booting it, I move away my "heater" and it doesn't overheat but at least it mines. I have this problem with both S17Pro and S17+.
When not heated S17Pro mines with only one or sometimes no hashboards at all, if I heat it up with my Z11, it mines with 2 or 3 hashboards normally. When not heated S17+ does not mine at all, if I heat it, it mines with one or sometimes two hashboards (third hashboard has loose heatsink so there is no way this method helps it :D).
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: mikeywith on December 21, 2020, 10:29:16 PM
For the first miner: 2020-10-15 11:31:51 driver-btm-api.c:982:check_asic_number_with_power_on: Chain[0]: find 65 asic, times 0
2020-10-15 11:32:02 driver-btm-api.c:982:check_asic_number_with_power_on: Chain[1]: find 0 asic, times 0
2020-10-15 11:32:37 driver-btm-api.c:982:check_asic_number_with_power_on: Chain[2]: find 65 asic, times 0
I would just mine with 2 hash boards rather than sending the gear back to China, the process will take forever and someone mentioned that bitmain couldn't send them their gears back and offered to buy their gears at a very cheap price, so sending them your gears back is a huge risk. for the second worker, did you try a different PSU?
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: wndsnb on December 22, 2020, 03:52:21 AM
First two miners are finding 0 chips on one hashboard at startup. Not something that is generally fixable without getting the hashboard on a test fixture and tracking down the issue. As mikeywith said, your best option is probably to try to just run with 2 hashboards each. If you can find a repair shop reasonably close you could consider sending them to get repaired, but by the time you pay shipping both ways and repair of 2 hashboards it would probably be > $500. Sending them back to Bitmain is not a good option in my opinion. I RMAed a S17pro under warranty to Bitmain's repair facility in California in May and still don't have it back.
As for the 3rd one, it doesn't see any chips on bootup from any hashboard. Not likely that all 3 hashboards decided to die at the same time. So, like mikeywith suggested, you should see if your host will swap a PSU to see if it runs with a good one. If that doesn't do it, you might see if they'll swap the control board out.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: spyroslo on January 02, 2021, 04:37:06 PM
Hi and hapy new year i have two s17_56h in one i take erros and hi does not start Any ideas ....? Booting Linux on physical CPU 0x0
Linux version 4.6.0-xilinx-gff8137b-dirty (lzq@armdev2) (gcc version 4.8.3 20140320 (prerelease) (Sourcery CodeBench Lite 2014.05-23) ) #25 SMP PREEMPT Fri Nov 23 15:30:52 CST 2018
CPU: ARMv7 Processor [413fc090] revision 0 (ARMv7), cr=18c5387d
CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
Machine model: Xilinx Zynq
cma: Reserved 16 MiB at 0x0e000000
Memory policy: Data cache writealloc
On node 0 totalpages: 61440
free_area_init_node: node 0, pgdat c0b39280, node_mem_map cde10000
Normal zone: 480 pages used for memmap
Normal zone: 0 pages reserved
Normal zone: 61440 pages, LIFO batch:15
percpu: Embedded 12 pages/cpu @cddf1000 s19776 r8192 d21184 u49152
pcpu-alloc: s19776 r8192 d21184 u49152 alloc=12*4096
pcpu-alloc: [0] 0 [0] 1
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 60960
Kernel command line: mem=240M console=ttyPS0,115200 ramdisk_size=33554432 root=/dev/ram rw earlyprintk
PID hash table entries: 1024 (order: 0, 4096 bytes)
Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
Memory: 203612K/245760K available (6345K kernel code, 231K rwdata, 1896K rodata, 1024K init, 223K bss, 25764K reserved, 16384K cma-reserved, 0K highmem)
Virtual kernel memory layout:
vector : 0xffff0000 - 0xffff1000 ( 4 kB)
fixmap : 0xffc00000 - 0xfff00000 (3072 kB)
vmalloc : 0xcf800000 - 0xff800000 ( 768 MB)
lowmem : 0xc0000000 - 0xcf000000 ( 240 MB)
pkmap : 0xbfe00000 - 0xc0000000 ( 2 MB)
modules : 0xbf000000 - 0xbfe00000 ( 14 MB)
.text : 0xc0008000 - 0xc090c424 (9234 kB)
.init : 0xc0a00000 - 0xc0b00000 (1024 kB)
.data : 0xc0b00000 - 0xc0b39fe0 ( 232 kB)
.bss : 0xc0b39fe0 - 0xc0b71c28 ( 224 kB)
Preemptible hierarchical RCU implementation.
Build-time adjustment of leaf fanout to 32.
RCU restricting CPUs from NR_CPUS=4 to nr_cpu_ids=2.
RCU: Adjusting geometry for rcu_fanout_leaf=32, nr_cpu_ids=2
NR_IRQS:16 nr_irqs:16 16
efuse mapped to cf800000
ps7-slcr mapped to cf802000
L2C: platform modifies aux control register: 0x72360000 -> 0x72760000
L2C: DT/platform modifies aux control register: 0x72360000 -> 0x72760000
L2C-310 erratum 769419 enabled
L2C-310 enabling early BRESP for Cortex-A9
L2C-310 full line of zeros enabled for Cortex-A9
L2C-310 ID prefetch enabled, offset 1 lines
L2C-310 dynamic clock gating enabled, standby mode enabled
L2C-310 cache controller enabled, 8 ways, 512 kB
L2C-310: CACHE_ID 0x410000c8, AUX_CTRL 0x76760001
zynq_clock_init: clkc starts at cf802100
Zynq clock init
sched_clock: 64 bits at 333MHz, resolution 3ns, wraps every 4398046511103ns
clocksource: arm_global_timer: mask: 0xffffffffffffffff max_cycles: 0x4ce07af025, max_idle_ns: 440795209040 ns
Switching to timer-based delay loop, resolution 3ns
clocksource: ttc_clocksource: mask: 0xffff max_cycles: 0xffff, max_idle_ns: 537538477 ns
ps7-ttc #0 at cf80a000, irq=18
Console: colour dummy device 80x30
Calibrating delay loop (skipped), value calculated using timer frequency.. 666.66 BogoMIPS (lpj=3333333)
pid_max: default: 32768 minimum: 301
Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
CPU: Testing write buffer coherency: ok
CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
Setting up static identity map for 0x100000 - 0x100058
CPU1: failed to boot: -1
Brought up 1 CPUs
SMP: Total of 1 processors activated (666.66 BogoMIPS).
CPU: All CPU(s) started in SVC mode.
devtmpfs: initialized
VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4
clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
pinctrl core: initialized pinctrl subsystem
NET: Registered protocol family 16
DMA: preallocated 256 KiB pool for atomic coherent allocations
cpuidle: using governor menu
hw-breakpoint: found 5 (+1 reserved) breakpoint and 1 watchpoint registers.
hw-breakpoint: maximum watchpoint size is 4 bytes.
zynq-ocm f800c000.ps7-ocmc: ZYNQ OCM pool: 256 KiB @ 0xcf880000
vgaarb: loaded
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
media: Linux media interface: v0.10
Linux video capture interface: v2.00
pps_core: LinuxPPS API ver. 1 registered
pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
PTP clock support registered
EDAC MC: Ver: 3.0.0
Advanced Linux Sound Architecture Driver Initialized.
clocksource: Switched to clocksource arm_global_timer
NET: Registered protocol family 2
TCP established hash table entries: 2048 (order: 1, 8192 bytes)
TCP bind hash table entries: 2048 (order: 2, 16384 bytes)
TCP: Hash tables configured (established 2048 bind 2048)
UDP hash table entries: 256 (order: 1, 8192 bytes)
UDP-Lite hash table entries: 256 (order: 1, 8192 bytes)
NET: Registered protocol family 1
RPC: Registered named UNIX socket transport module.
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
PCI: CLS 0 bytes, default 64
Trying to unpack rootfs image as initramfs...
rootfs image is not initramfs (no cpio magic); looks like an initrd
Freeing initrd memory: 12724K (cce94000 - cdb01000)
hw perfevents: enabled with armv7_cortex_a9 PMU driver, 7 counters available
futex hash table entries: 512 (order: 3, 32768 bytes)
workingset: timestamp_bits=28 max_order=16 bucket_order=0
jffs2: version 2.2. (NAND) (SUMMARY) © 2001-2006 Red Hat, Inc.
io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered (default)
dma-pl330 f8003000.ps7-dma: Loaded driver for PL330 DMAC-241330
dma-pl330 f8003000.ps7-dma: DBUFF-128x8bytes Num_Chans-8 Num_Peri-4 Num_Events-16
e0000000.serial: ttyPS0 at MMIO 0xe0000000 (irq = 158, base_baud = 6249999) is a xuartps
console [ttyPS0] enabled
xdevcfg f8007000.ps7-dev-cfg: ioremap 0xf8007000 to cf86e000
[drm] Initialized drm 1.1.0 20060810
brd: module loaded
loop: module loaded
CAN device driver interface
gpiod_set_value: invalid GPIO
libphy: MACB_mii_bus: probed
macb e000b000.ethernet eth0: Cadence GEM rev 0x00020118 at 0xe000b000 irq 31 (00:0a:35:00:00:00)
Generic PHY e000b000.etherne:00: attached PHY driver [Generic PHY] (mii_bus:phy_addr=e000b000.etherne:00, irq=-1)
e1000e: Intel(R) PRO/1000 Network Driver - 3.2.6-k
e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
ehci-pci: EHCI PCI platform driver
usbcore: registered new interface driver usb-storage
mousedev: PS/2 mouse device common for all mice
i2c /dev entries driver
Xilinx Zynq CpuIdle Driver started
sdhci: Secure Digital Host Controller Interface driver
sdhci: Copyright(c) Pierre Ossman
sdhci-pltfm: SDHCI platform and OF driver helper
mmc0: SDHCI controller on e0100000.ps7-sdio [e0100000.ps7-sdio] using ADMA
ledtrig-cpu: registered to indicate activity on CPUs
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
nand: device found, Manufacturer ID: 0x2c, Chip ID: 0xda
nand: Micron MT29F2G08ABAGAWP
nand: 256 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 128
nand: WARNING: pl35x-nand: the ECC used on your system is too weak compared to the one required by the NAND chip
Bad block table found at page 131008, version 0x01
Bad block table found at page 130944, version 0x01
6 ofpart partitions found on MTD device pl35x-nand
Creating 6 MTD partitions on "pl35x-nand":
0x000000000000-0x000002800000 : "BOOT.bin-env-dts-kernel"
0x000002800000-0x000004800000 : "ramfs"
0x000004800000-0x000005000000 : "configs"
0x000005000000-0x000006000000 : "reserve"
0x000006000000-0x000008000000 : "ramfs-bak"
0x000008000000-0x000010000000 : "reserve1"
NET: Registered protocol family 10
sit: IPv6 over IPv4 tunneling driver
NET: Registered protocol family 17
can: controller area network core (rev 20120528 abi 9)
NET: Registered protocol family 29
can: raw protocol (rev 20120528)
can: broadcast manager protocol (rev 20120528 t)
can: netlink gateway (rev 20130117) max_hops=1
zynq_pm_ioremap: no compatible node found for 'xlnx,zynq-ddrc-a05'
zynq_pm_late_init: Unable to map DDRC IO memory.
Registering SWP/SWPB emulation handler
hctosys: unable to open rtc device (rtc0)
ALSA device list:
No soundcards found.
RAMDISK: gzip image found at block 0
EXT4-fs (ram0): couldn't mount as ext3 due to feature incompatibilities
EXT4-fs (ram0): mounted filesystem without journal. Opts: (null)
VFS: Mounted root (ext4 filesystem) on device 1:0.
devtmpfs: mounted
Freeing unused kernel memory: 1024K (c0a00000 - c0b00000)
EXT4-fs (ram0): re-mounted. Opts: block_validity,delalloc,barrier,user_xattr
random: dd urandom read with 0 bits of entropy available
ubi0: attaching mtd2
ubi0: scanning is finished
ubi0: attached mtd2 (name "configs", size 8 MiB)
ubi0: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
ubi0: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
ubi0: VID header offset: 2048 (aligned 2048), data offset: 4096
ubi0: good PEBs: 64, bad PEBs: 0, corrupted PEBs: 0
ubi0: user volume: 1, internal volumes: 1, max. volumes count: 128
ubi0: max/mean erase counter: 25/10, WL threshold: 4096, image sequence number: 2419912869
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 1303F5C2-F3EF-4059-9B98-C469B28B1788, 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: 443/125, WL threshold: 4096, image sequence number: 2324953515
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 8C5051EC-2BDF-4773-B69A-558999E9CEC7, small LPT model
IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
macb e000b000.ethernet eth0: unable to generate target frequency: 25000000 Hz
macb e000b000.ethernet eth0: link up (100/Full)
IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
In axi fpga driver!
request_mem_region OK!
AXI fpga dev virtual address is 0xcfb38000
*base_vir_addr = 0xab013
In fpga mem driver!
request_mem_region OK!
fpga mem virtual address is 0xd2000000
random: nonblocking pool is initialized
2021-01-02 16:31:17 driver-btm-api.c:542:init_freq_mode: This is scan-user version
2021-01-02 16:31:17 driver-btm-api.c:1877:bitmain_soc_init: opt_multi_version = 1
2021-01-02 16:31:17 driver-btm-api.c:1878:bitmain_soc_init: opt_bitmain_ab = 1
2021-01-02 16:31:17 driver-btm-api.c:1879:bitmain_soc_init: opt_bitmain_work_mode = 2
2021-01-02 16:31:17 driver-btm-api.c:1880:bitmain_soc_init: Miner compile time: Mon Apr 27 13:23:07 CST 2020 type: Antminer S17
2021-01-02 16:31:17 driver-btm-api.c:1881:bitmain_soc_init: commit version: d22f356 2020-04-24 18:30:49, build by: lol 2020-04-27 13:30:25
2021-01-02 16:31:17 driver-btm-api.c:1691:show_sn: no SN got, please write SN to /nvdata/sn
2021-01-02 16:31:17 driver-btm-api.c:1040:miner_device_init: Detect 256MB control board of XILINX
2021-01-02 16:31:17 driver-btm-api.c:988:init_fan_parameter: fan_eft : 0 fan_pwm : 0
2021-01-02 16:31:17 thread.c:783:create_read_nonce_reg_thread: create thread
2021-01-02 16:31:23 driver-btm-api.c:972:init_miner_version: miner ID : 80680c0e7510481c
2021-01-02 16:31:23 driver-btm-api.c:978:init_miner_version: FPGA Version = 0xB013
2021-01-02 16:31:29 driver-btm-api.c:616:get_product_id: product_id[0] = 0
2021-01-02 16:31:29 driver-btm-api.c:616:get_product_id: product_id[1] = 0
2021-01-02 16:31:29 driver-btm-api.c:616:get_product_id: product_id[2] = 0
2021-01-02 16:31:29 driver-btm-api.c:560:_set_project_type: project:1
2021-01-02 16:31:29 driver-btm-api.c:585:_set_project_type: Project type: Antminer S17
2021-01-02 16:31:29 driver-btm-api.c:596:dump_pcb_bom_version: Chain [0] PCB Version: 0x0101
2021-01-02 16:31:29 driver-btm-api.c:597:dump_pcb_bom_version: Chain [0] BOM Version: 0x0103
2021-01-02 16:31:29 driver-btm-api.c:596:dump_pcb_bom_version: Chain [1] PCB Version: 0x0101
2021-01-02 16:31:29 driver-btm-api.c:597:dump_pcb_bom_version: Chain [1] BOM Version: 0x0103
2021-01-02 16:31:29 driver-btm-api.c:596:dump_pcb_bom_version: Chain [2] PCB Version: 0x0101
2021-01-02 16:31:29 driver-btm-api.c:597:dump_pcb_bom_version: Chain [2] BOM Version: 0x0103
2021-01-02 16:31:30 driver-btm-api.c:1802:bitmain_board_init: Fan check passed.
2021-01-02 16:31:38 driver-btm-api.c:321:init_pic: Chain[0] PIC init failed!
2021-01-02 16:31:38 driver-btm-api.c:198:set_miner_status: ERROR_PIC_LOST
2021-01-02 16:31:38 board.c:36:jump_and_app_check_restore_pic: chain[0] PIC jump to app
2021-01-02 16:31:54 board.c:40:jump_and_app_check_restore_pic: Check chain[0] PIC fw version=0xff
2021-01-02 16:31:55 board.c:36:jump_and_app_check_restore_pic: chain[1] PIC jump to app
2021-01-02 16:31:57 board.c:40:jump_and_app_check_restore_pic: Check chain[1] PIC fw version=0xb9
2021-01-02 16:32:05 driver-btm-api.c:321:init_pic: Chain[2] PIC init failed!
2021-01-02 16:32:05 driver-btm-api.c:198:set_miner_status: ERROR_PIC_LOST
2021-01-02 16:32:05 board.c:36:jump_and_app_check_restore_pic: chain[2] PIC jump to app
2021-01-02 16:32:22 board.c:40:jump_and_app_check_restore_pic: Check chain[2] PIC fw version=0xff
2021-01-02 16:32:22 thread.c:778:create_pic_heart_beat_thread: create thread
2021-01-02 16:32:22 power_api.c:207:power_init: Power init:
2021-01-02 16:32:22 power_api.c:208:power_init: current_voltage_raw = 0
2021-01-02 16:32:22 power_api.c:209:power_init: highest_voltage_raw = 2100
2021-01-02 16:32:22 power_api.c:210:power_init: working_voltage_raw = 1830
2021-01-02 16:32:22 power_api.c:211:power_init: higher_voltage_raw = 1950
2021-01-02 16:32:22 driver-btm-api.c:1812:bitmain_board_init: Enter 30s sleep to make sure power release finish.
2021-01-02 16:32:54 power_api.c:251:set_to_highest_voltage: Set to voltage raw 2100, one step.
2021-01-02 16:32:56 power_api.c:87:check_voltage_multi: retry time: 0
2021-01-02 16:32:58 power_api.c:37:_get_avg_voltage: chain = 1, voltage = 21.455156
2021-01-02 16:32:58 power_api.c:50:_get_avg_voltage: average_voltage = 21.455156
2021-01-02 16:32:58 power_api.c:68:check_voltage: target_vol = 21.00, actural_vol = 21.46, check voltage passed.
2021-01-02 16:32:58 uart.c:71:set_baud: set fpga_baud to 115200
2021-01-02 16:33:09 driver-btm-api.c:915:check_asic_number_with_power_on: Chain[1]: find 40 asic, times 0
2021-01-02 16:33:20 driver-btm-api.c:915:check_asic_number_with_power_on: Chain[1]: find 40 asic, times 1
2021-01-02 16:33:31 driver-btm-api.c:915:check_asic_number_with_power_on: Chain[1]: find 40 asic, times 2
2021-01-02 16:33:31 driver-btm-api.c:942:check_asic_number: Chain 1 only find 40 asic, will power off hash board 1
2021-01-02 16:33:32 driver-btm-api.c:198:set_miner_status: ERROR_SOC_INIT
2021-01-02 16:33:32 driver-btm-api.c:139:stop_mining: stop mining: soc init failed!
2021-01-02 16:33:32 thread.c:828:cancel_read_nonce_reg_thread: cancel thread
2021-01-02 16:33:32 driver-btm-api.c:124:killall_hashboard: ****power off hashboard****
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: mikeywith on January 02, 2021, 05:19:13 PM
2021-01-02 16:33:31 driver-btm-api.c:942:check_asic_number: Chain 1 only find 40 asic, will power off hash board 1
This is the problem, Chain 1 shows only 40 asic when it's supposed to signal 48 chips, so there seem to be an issue with the 40th or 41th chip, usually, with these 17 series mining gears it's a loose heatsink that needs soldering. With that being said, where is your chain 0 and chain 2, does this miner run with only 1 hashboard?
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: spyroslo on January 02, 2021, 06:36:07 PM
Thank you for you reply. Do you believe that it is a hardware problem or software? The miner has install free hashboard.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: favebook on January 02, 2021, 10:00:50 PM
This is the problem, Chain 1 shows only 40 asic when it's supposed to signal 48 chips, so there seem to be an issue with the 40th or 41th chip, usually, with these 17 series mining gears it's a loose heatsink that needs soldering.
With that being said, where is your chain 0 and chain 2, does this miner run with only 1 hashboard?
It does have three chains, it just skips them in beginning. Loose heatsinks (they fell off almost certainly) are almost 100% problem on those 2, while chain 1 is just loose heatsinks but still haven't fallen of fully. Thank you for you reply. Do you believe that it is a hardware problem or software? The miner has install free hashboard.
Hardware 100%, check other posts here, you will find very similar or identical problems.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: mikeywith on January 02, 2021, 10:02:31 PM
I am 99% positive that it is a hardware issue, however, i would still test the miner with custom firmware since sometimes it could fix the issue, try vnish (asic.to or awesomeminer), chances are low but you have nothing to lose.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: RRZP028 on January 10, 2021, 11:26:48 PM
I bought a tester from Zeusbtc two months ago, I can tell you that there is still no successful result regarding the repair of my miners, first the tester is of very poor quality, it can be seen that they looked to save on everything, asik 0 on almost all boards and cooperation with them grade 2
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: wndsnb on January 11, 2021, 12:11:32 PM
I bought a tester from Zeusbtc two months ago, I can tell you that there is still no successful result regarding the repair of my miners, first the tester is of very poor quality, it can be seen that they looked to save on everything, asik 0 on almost all boards and cooperation with them grade 2
Yeah, the tester is only a small part of being able to repair hashboards. The output of the test is only sometimes useful, most of the time you need the fixture just to operate the board while you use an oscilloscope and/or voltmeter to measure signals at the test points. Just FYI, with the COVID situation, Bitmain now offers an online repair course for $500. I haven't taken it so I'm not sure how useful it is, but once you complete it you get access to all of their official repair manuals and downloads, and you can order Bitmain's test fixture and spare parts direct from them. Previously it was $1000 and you had to travel to one of their sites to take the 1-week long course. All of the testers of that type are built similarly ... I agree that it is not the best. Just kind of hacked together. I've ordered a different tester from here https://tester.asic.repair/en. It was much more expensive and ships from Russia but looks like a much better product. Slow shipping from Russia to USA though ... ordered a month ago and the tracking estimated arrival is still 3 to 5 more weeks...
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: RRZP028 on January 12, 2021, 10:06:49 PM
did you manage to fix a board, do you have problems with the Asic 0 error that occurs a lot with me and I can't solve it
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: wndsnb on January 13, 2021, 08:13:31 PM
Yes, so far I've repaired 3 S17 hashboards and one S17+ hashboard. Most were reporting 0 Asics at some point. I'd say more issues cause 0 asics than some number fewer than the total asics.
To solve it, you need to trace the signals through the board to try to locate the spot where they go bad. The repair manuals on Zuesbtc are a good place to start. It's not easy though, both the locating of issues and then the techniques to remove/replace heatskins and chips. I'm an Electrical Engineer with >25 years experience and it took me a month of nights and weekends to decode the manuals/reverse engineer the hashboards to get to the point where I could repair one. I'm sure it would have been a lot easier to just take the Bitmain repair course, but I guess I'm just a glutton for punishment...
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: RRZP028 on January 13, 2021, 09:11:37 PM
Well, I'm a beginner in that, today I successfully replaced my first chip, I replaced it after a few attempts, chip No. 01 after that it gave an error on chip 34, I still haven't been able to solve it, can you tell me how to glue a refrigerator for chip and what temperature do you use then and what when should you glue the chip to the hash board.
When it shows Asic 0, I first control the first chip, and then the last. I look at which test point the parameters are not good and after that I start with the control of the chip, first I take off the cooler and check if there are soldering balls then I try to reattach the chip at a temperature of 400 degrees Celsius, if that doesn't help I take off the chip and first try to I put it back again because I clean it nicely, if it doesn't help you either, then I mount a new chip, after that I measure the resistance, if everything is OK, then I go to test and check the values at the checkpoints again.
Has anyone completed the BItmain course that wants to help a little.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: wndsnb on January 16, 2021, 11:36:28 PM
I use a heatgun set at 315 degrees C set at low airflow to remove/attach heatsinks and chips. Attaching heatsinks on S17 boards is pretty tricky. For S17 and S17 pro, I've been removing most residual solder from the heatsink and adding what I think is the correct amount of solder to the top of the ASIC. I put some tacky flux on the top of the chip, then heat the heatsink with my heatgun for ~20 seconds and set it down on the chip. There is then a small window of time where you can adjust the placement of the heatsink. If you are not quick enough, the solder holding the chip to the board can melt and then you can shift the chip. On the S17+, that technique didn't work for chips with the smaller heatsinks. So on those, I prepare the chip and heatsink the same way, but then just place the heatsink on the chip and heat it directly until the solder flows. For attaching chips, I remove the solder from the board with solder wick, apply tacky flux to the board and place the chip in position, then apply heat for ~45 seconds. For new chips, I use a stencil to apply solder paste to the chip and melt the solder before placing it on the board. Nearly every time I do this, all connections are not made, so I add solder paste with a small syringe to the edge of the chip, reflow, add more flux, reflow again, and clean up any excess solder with an exacto knife while the solder is still liquid. Pretty tedious process. Flux I use: https://www.chipquik.com/store/product_info.php?products_id=310003 solder paste I use: https://www.chipquik.com/store/product_info.php?products_id=470006 solder wick: https://www.chipquik.com/store/product_info.php?products_id=640002 Heat gun I use: https://www.masterappliance.com/proheat-1500-lcd-programmable-professional-heat-gun-kit/
Started working on another S17+, this one is a real mess. One hashboard had 9 heatsinks fall off, some with chips still attached. The heatsinks that fell off look like they came off with the film from the top of the chip. Without the film on the chip, it is impossible to get solder to flow evenly on the top of the chip, so impossible to get a good contact with the heatsink. I saw the same issue on some chips on another S17+. Looks like a manufacturing issue with the chip packages. Or maybe it just breaks down if it gets too hot for too long. To save the chips, I'd have to use a thermally conductive adhesive instead of solder to attach the heatsinks. Not too excited about that idea. A lot of the chips got hot enough to melt the solder holding them to the board and slid down towards the bottom of the miner. Pretty sure some/most of them would be toast anyway so might just replace them all. Pretty sure this board is going in the "maybe later" pile. https://i.imgur.com/LYiAolb.png?1 (https://i.imgur.com/LYiAolb.png?1) https://i.imgur.com/yETGcWN.png (https://i.imgur.com/yETGcWN.png) These chips would normally be covered in solder, or would be an amber color if a heatsink was never attached. https://i.imgur.com/YFHHElb.png?1 (https://i.imgur.com/YFHHElb.png?1) Most of the film from the chip is still stuck to the heatsink. https://i.imgur.com/OMYUU4A.png (https://i.imgur.com/OMYUU4A.png)
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: mikeywith on January 17, 2021, 03:41:35 AM
Started working on another S17+, this one is a real mess. One hashboard had 9 heatsinks fall off, some with chips still attached.
I had the same issue with my S17+, these gears are terrible compared to the S17 pro, they are less terrible than T17/T17e but still, the failure rate on my S17+ is 50% easily, and most of the heatsink fell along with the chips unlike the T17s, I also noticed this on the S17, I wish I had the skills, time and tools to fix these chips like you and the other folks, I had some success with the S9s chips but my overall performance was very poor, I had someone else fix them for me after that, and that person is no longer available, so all I can do is watch those gears sit there do nothing.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: wndsnb on January 17, 2021, 03:18:22 PM
I had someone else fix them for me after that, and that person is no longer available, so all I can do is watch those gears sit there do nothing.
If you want to sell any of your dead gear instead of watching it do nothing, shoot me a PM. Shipping might be too expensive to make it worth it, but maybe not. Not sure how commercial places are making money repairing these. Hmtech charges $40 diagnosis + $150/hashboard for "basic" repair, $300/hashboard for "advanced" repair. I'm sure their techs are way more skilled than me, but I wonder if they would repair the board from my last post for $300 or if they'd just say it's not repairable. It's possible it could need $100 worth of replacement chips. So far, every board I've fixed has taken more than 8 hours of work. The S17+ that I repaired took ~24 hours of work, although that was the first S17+ for me so there was some learning curve on that one. I also found on the S17+ that chips will come up with the heatsink when trying to just remove the heatsink. So just pulling heatsinks to get access to repair other chips can cause other issues.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: favebook on January 17, 2021, 03:22:38 PM
I have 2 units that are sometimes working, sometimes not. S17 Pro and S17+. One has dead hashboard (exactly one loose heatsink) while all 5 other hashboards sometimes work. Where are you from and would you try to repair them or want to buy 'em out?
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: wndsnb on January 17, 2021, 04:28:45 PM
I have 2 units that are sometimes working, sometimes not. S17 Pro and S17+. One has dead hashboard (exactly one loose heatsink) while all 5 other hashboards sometimes work. Where are you from and would you try to repair them or want to buy 'em out?
I'm in the northeast USA. I'd consider buying them, but if they are partially working it may be better for you to limp along with them while profitability is as high as it is now. Guess that depends on how often the 5 sometimes working hashboards go down.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: RRZP028 on January 17, 2021, 08:51:05 PM
Every day I spend up to 10 hours on the same hash board and new problems are constantly born, problem Chain 36 after a while an error appears chine 21 then chine 6 then Asic 0 and so constantly, a lot of trouble for a beginner, and those from Zeusbtc will not really cooperate,
Every chip I want to glue, I zoom in ten times to see if everything is in place and again I can't set it up nicely, and I'm also interested in whether you test the desoldering plate right while it's warm or it has to cool down really well.
I ordered all the equipment from Zusbtc https://www.zeusbtc.com/.
Can the solder be removed from the chip with a soldering iron, how safe is it for the chip, and is it wise to clean all the solder from the board before installing a new chip?
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: wndsnb on January 17, 2021, 09:26:34 PM
I use a soldering iron set at 315 deg C to remove solder from chips. As long as you don't let the chip get too hot for too long, it won't get damaged. The key is time + temperature. Most components and the PCB have materials that will start to break down above 150 to 200 degC. Both have specs for how long it can safely be above a certain temperature so they can be reflow soldered in a reflow oven.
As for removing solder from the board before installing a new chip, I do that because I find it very difficult to place the chip when there is solder on both the board and the chip. Since the solder on the board and the chip create rounded bumps, the bumps on the chip nearly always will fall off the bumps on the board.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: mikeywith on January 17, 2021, 11:42:52 PM
If you want to sell any of your dead gear instead of watching it do nothing, shoot me a PM. Shipping might be too expensive to make it worth it, but maybe not.
Shipping from where I live to the U.S will sure cost a ton of money, the same thing to China, it's why I throw away most of the gears that die on me, but depending on your offer we might work it out especially if you only need the hash boards and not whole miners. I'll confirm what do I have left untouched and send you a PM accordingly, I know I have hash boards of these models (S17 pro, S17, T17, T17e, S17+) I just need to confirm the numbers.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: mtnrotary on January 18, 2021, 07:40:02 PM
First two miners are finding 0 chips on one hashboard at startup. Not something that is generally fixable without getting the hashboard on a test fixture and tracking down the issue. As mikeywith said, your best option is probably to try to just run with 2 hashboards each. If you can find a repair shop reasonably close you could consider sending them to get repaired, but by the time you pay shipping both ways and repair of 2 hashboards it would probably be > $500. Sending them back to Bitmain is not a good option in my opinion. I RMAed a S17pro under warranty to Bitmain's repair facility in California in May and still don't have it back.
As for the 3rd one, it doesn't see any chips on bootup from any hashboard. Not likely that all 3 hashboards decided to die at the same time. So, like mikeywith suggested, you should see if your host will swap a PSU to see if it runs with a good one. If that doesn't do it, you might see if they'll swap the control board out.
The miners are located in Eastern Canada. Do you know of any repair sites in that part of the world?
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: RRZP028 on January 18, 2021, 07:48:15 PM
today I ordered another 50 chips, although I haven't even learned how to install them yet, I'm from Serbia, so sending from here is difficult, both to China and the USA,
I ask about the temperature because these with Zeusbtc advise 450 degrees Celsius when it is removed and when the chip is glued, so I assumed that it might not be much and whether that temperature will damage the chip
and how do I know that I haven't burned the chip from overheating and I don't know if I should put pressure on it during the gluing process,
for soldering I use two solder pastes 138celsius and 183 celsius, which is your opinion which is better
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: favebook on January 18, 2021, 08:37:37 PM
I'm in the northeast USA.
I'd consider buying them, but if they are partially working it may be better for you to limp along with them while profitability is as high as it is now. Guess that depends on how often the 5 sometimes working hashboards go down.
Let's say that two out of five hashboards work every 10th try if miner is preheated and other three hashboards work every 3rd try if miner is preheated. If they are not preheated, there is maybe like 5% that 2 of them will work rest will not work at all if atmosphere temperature is under 25C. Sadly as RRZP028 noted, shipping from Serbia to China or USA is way too expensive for anything that is heavy. I am from Serbia as well which means I might be in need of your recently acquired skills RRZP028. :)
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: mikeywith on January 18, 2021, 10:31:13 PM
The miners are located in Eastern Canada. Do you know of any repair sites in that part of the world?
I recall one of the folks here was from Canada, I have a bad memory tho, so let's hope he sees your post and respond to you, meanwhile if sending it to the U.S is an option you might want to have a look at this topic (https://bitcointalk.org/index.php?topic=5297994.0) and perhaps ask your question there since the topic is pinned and related to mining fixing service I suppose you have a better chance in getting answers there than here.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: Scorpyy on January 19, 2021, 04:31:04 AM
Hey guys.
Some info i just found out.
I managed to get all 3 boards to work on one of my miners ( with some of chips getting X tho after couple of minutes of mining, total hashrate ends up at 50 TH/s instead of 60 TH/s ) by placing a miner at tilted at 45 degrees with one side being set on the wall next to it.
Also the 2nd miner works only with 1 board but only if placed on its PSU.
So if your boards are failing you can always try different angles to get them back to life. Worth a try, hopefully it will work with your gear as well.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: wndsnb on January 19, 2021, 01:34:35 PM
Shipping from where I live to the U.S will sure cost a ton of money, the same thing to China, it's why I throw away most of the gears that die on me, but depending on your offer we might work it out especially if you only need the hash boards and not whole miners.
I'll confirm what do I have left untouched and send you a PM accordingly, I know I have hash boards of these models (S17 pro, S17, T17, T17e, S17+) I just need to confirm the numbers.
Thanks, let me know what you find. I have a bunch of APW9s, so one option is to just remove the PSU which is ~40% of the weight.
So if your boards are failing you can always try different angles to get them back to life. Worth a try, hopefully it will work with your gear as well.
I've seen a lot of excess solder that dripped down from heatsinks on hashboards I've repaired. The solder forms small solder balls that can sit right between the exposed pads for the chip connections and the bottom of the heatsink. It can sometimes be very close to shorting out signals, and just a bit of pressure on the heatsink can cause it to touch the signals and short them out. I'm sure the opposite is true as well, so a bit of pressure in the right spot could pull the solder away enough to open a short.
Every day I spend up to 10 hours on the same hash board and new problems are constantly born, problem Chain 36 after a while an error appears chine 21 then chine 6 then Asic 0 and so constantly, a lot of trouble for a beginner, and those from Zeusbtc will not really cooperate...
I find that very frequently heating and removing a heatsink will melt excess solder on nearby chips causing other issues. Also just handling and flexing the board can expose other issues. Especially when starting out, it is a good idea to test in stages as you put chips and heatsinks back on. I set the test fixture to only do the asic count test (this can be set in the config.ini file on the sd card, Only_find_ASIC=1), and will test the board before applying either heatsink, then after applying the back heatsink, and again after applying the top heatsink. Many times the board will find all chips fine, but after applying the back heatsink for the chip I'm working on I get 0 asics.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: RRZP028 on January 19, 2021, 08:25:56 PM
Of course, since we are compatriots and we have the same problems, I will share all my knowledge with you here and I can contact you privately.
although I have a lot of problems so far, today I have solder chips with solder paste up to 138 degrees Celsius and got some positive signals for the first time in a month.
I heated the solder to 350 degrees Celsius on a low speed blower
First he gave me an error on chip number 36 which reported a bad RO which I measure the black pin of the multimeter I prick in the RO behind the chip and the red on the chip itself.
As far as I understand so far, the normal values for RO are minus 1.8..v
So after checking all five signals I concluded that the RO signal is not OK on chip number 35, which I replaced but then I was told the same error on chip number 36 which I also replaced today, after measuring on both chips I later the same values of 1 , 8v but now my problem is chip 34 which gives bad values on CLK, CO, RSD by reducing the voltage by half than normal, after that I did not research more than I left the board to cool down until tomorrow.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: mtnrotary on January 21, 2021, 07:12:44 PM
I recall one of the folks here was from Canada, I have a bad memory tho, so let's hope he sees your post and respond to you, meanwhile if sending it to the U.S is an option you might want to have a look at this topic (https://bitcointalk.org/index.php?topic=5297994.0) and perhaps ask your question there since the topic is pinned and related to mining fixing service I suppose you have a better chance in getting answers there than here.
Thanks for this! I'll get in touch with some of those people there in the interim and see if anyone else pops up here.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: RRZP028 on January 22, 2021, 11:58:56 AM
I still have a problem with the same hash board. Now, after replacing some chips, I had a problem with another chip, the point is that the values on CKL and other points are not OK even after replacing two correct chips.
I will try to present you my problem through pictures.
How to multimeter parameters
https://imgur.com/SVVyvXK
Start loading the saw
https://i.imgur.com/FSy1BLz.jpg
https://i.imgur.com/fEz9bQU.jpg
start testing
https://i.imgur.com/fEz9bQU.jpg
https://i.imgur.com/gVs19Rc.jpg
Chain 2 find 0 asic and look at the values on the multimeter which should be from 0.7v to 0.9v
https://i.imgur.com/HbjoMMx.jpg
https://i.imgur.com/qDl9k91.jpg
https://i.imgur.com/CkACRRN.jpg
https://i.imgur.com/ayeHcwM.jpg
https://i.imgur.com/rl0iujl.jpg
Measuring only the CLK on the previous chip shows the correct values
https://i.imgur.com/Mluu1mq.jpg
https://i.imgur.com/Qz87PFc.jpg
If you think I'm not doing something right feel free to write to me because I'm a beginner.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: wndsnb on January 22, 2021, 02:37:24 PM
Are you checking the IO supply voltages? Once you find where either RO or CO is bad, the next thing you should do is check the IO supply voltages (1.8V and 0.8V) for that chip. The 1.8V voltage is generated by a regulator at each voltage domain, and the 0.8V supply voltage is generated by two different regulators per voltage domain. They are fed through each chip. So the output of the regulator could be fine, but the input to a chip may not be if there is a bad connection to a chip before. If the IO supplies aren't good, then a perfectly good chip will not have good RO, CO, and CLK signals. https://i.imgur.com/rkANC98.png (https://i.imgur.com/rkANC98.png) You can measure the IO voltages for each chip at the capacitors shown below: https://i.imgur.com/DhETVrC.png (https://i.imgur.com/DhETVrC.png)
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: RRZP028 on January 22, 2021, 09:25:48 PM
can I use these capacitors from other hash boards, I have a lot of used ones from D3 + L3, what are their labels and how do they change and how is it examined if you replaced them well
In general, I think I have more problems with voltage than with chips, because where my machines are, there are large voltage oscillations and I would be very grateful to everyone for their help.
this is the first time i see it now i thought it was just measured in front of and behind the chip at those five points
nor did I see Zeusbtc explain the voltage domain nicely
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: wndsnb on January 22, 2021, 09:50:33 PM
The capacitors are just convenient places to measure, if the voltage is not correct they would not be the components you would need to replace. If voltages are bad at the capacitors, then normally either the connections are not being made through the asics, or the voltage regulator has failed.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: RRZP028 on January 23, 2021, 09:20:39 PM
Mr. wndsnb I have to thank you and say you were right for the capacitor
the capacitor in the first example does not give voltage in front of the chip, while the chip in front of it normally sends a voltage of 0.8v and 1.8v
https://imgur.com/zMvEssQ
also on the second hash board we have the same problem but this time it is chip number 1
https://imgur.com/MWKENUE
do you have any solution to this problem
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: wndsnb on January 24, 2021, 01:10:00 AM
First, check that the correct voltage is present at the output of the voltage regulator for that voltage domain, then trace it through each chip to find out where it goes bad. Most likely, a connection in or out of an ASIC chip is not good.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: RRZP028 on January 24, 2021, 10:48:57 PM
if you want to help me then you have to show me where everything you say is measured, as in the previous picture
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: BigStarMine on January 25, 2021, 07:19:42 PM
Hello Everyone,
I am new to this so please bear with me. I have S 17 pros and I am having a problem I have not seen posted on this thread, if it is and i missed it sorry. My miner will start get to hashing power and then after five minutes the it slowly starts to loose hashing power then resets. It will keep doing this forever if i let it. i decided to unplug as this cant be good for the miner. I have checked the log there are no errors, no warning, everything looks normal and can not see a reason for this to happen. it is detecting all 144 chips and all the temps sensors are fine. please help.
2. what does this mean? i can not find it anywhere i look.
[2021/01/25 22:20:02] ERROR: src/power.c:161 Malformed power response
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: mikeywith on January 26, 2021, 12:13:42 AM
[2021/01/25 22:20:02] ERROR: src/power.c:161 Malformed power response
This usually indicates a bad PSU, either the PSU is dying or it gets way too hot because of dust, it could also be a voltage related issue, these PSUs will only function well between 200v and 240v, outside of this range in either direction usually creates problems, so you want to check your voltage as well. There are few more things that need troubleshooting but the info you provided is not enough, please create a new topic and post the following: 1- Complete Kernel Log 2- Miner Status page and of course, any more info you have on this, like was the miner working fine for a long period before? is it brand new? any piece of info you can provide will increase the chances of someone here giving you the right answer.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: HagssFIN on January 26, 2021, 06:12:37 AM
^ In the power.c file, at the row 161,
there is some system check that it has failed.
Most likely something PSU related like Mikey said.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: RRZP028 on January 26, 2021, 07:19:42 AM
First, check that the correct voltage is present at the output of the voltage regulator for that voltage domain, then trace it through each chip to find out where it goes bad. Most likely, a connection in or out of an ASIC chip is not good.
please explain to me a little bit more about where those measuring points are
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: wndsnb on January 26, 2021, 11:51:36 AM
[2021/01/25 22:20:02] ERROR: src/power.c:161 Malformed power response
I'm pretty sure I've seen this error from a flaky control board before, so it might be worth trying another control board. please explain to me a little bit more about where those measuring points are.
The 1.8V for each voltage domain is supplied by a regulator shown in the photo below, and then it is transmitted through each chip. The schematic in my previous post shows the pinouts for the regulators, and the photo from my previous post shows where the voltage can be measured at each chip. I have not worked on a T17+, but on other miners there is 2nd 0.8V regulator near the other side of the board that generates the 0.8V for the chips on that side of the board for the same voltage domain. https://i.imgur.com/ScjiIBW.png (https://i.imgur.com/ScjiIBW.png)
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: BigStarMine on January 26, 2021, 04:19:17 PM
[...]
Ok I will. Thank you.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: mikeywith on February 26, 2021, 09:30:36 PM
... a little sketchy that Zuesbtc is trying to sell it when you can read it yourself with the tools needed to program the chip.
Not sure if I agree with this logic, that is a "know-how" that they utilize just like most other businesses. If members of this forum were not generous enough to share such knowledge for free, most people would not know about using pickit to accomplish the same result, plus, they make the process simpler/faster, you don't need a pc or any extra software to copy-paste and confirm the hex. Of course, if you know how to do that it makes no sense to pay $300+ for that tool, but the average joe would probably not touch a pickit at its basic level, but I don't think it's "sketchy" by any means, and that is just my opinion. I haven't actually programmed a chip with the firmware I read out, so maybe there is some issue with doing that that I'm not seeing. Or maybe some boards do have the read protection bit set and I got lucky.
Nop they don't, you can read and write using MPLAB without an issue.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: Pendrak on March 01, 2021, 05:06:38 AM
What kind of glue use the heatsinks of the S17 T17 hashboards?
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: mikeywith on March 01, 2021, 12:31:18 PM
What kind of glue use the heatsinks of the S17 T17 hashboards?
The cheapest would be the black glue from China, it's available on both Aliexpress and Zuesbtc > https://www.zeusbtc.com/RepairDetails.asp?ID=86, keep in mind that this product can't be stored outside the fridge for more than 10 days, so check with the seller as well as the carrier, the second option which is a lot more expensive but probably has better quality and easier to get would be Arctic > https://www.amazon.com/Arctic-Silver-Premium-Adhesive-ASTA-7G/dp/B0087X7262. wndsnb also mentioned using a different product somewhere which I can't find, I hope he would chime in and post the link
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: wndsnb on March 01, 2021, 03:03:31 PM
What kind of glue use the heatsinks of the S17 T17 hashboards?
At the factory, the heatsinks are soldered on using low-temperature melting point solder (~140 degC). This is what I use https://www.chipquik.com/store/product_info.php?products_id=470006. The soldering only works if the copper plating is still on the top of the chip, and from my experience, most of the time heatsinks fall off it is caused when the plating delaminates. If that is the case, then the only options are to use a thermally conductive adhesive or to replace the chip.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: Pendrak on March 01, 2021, 03:07:17 PM
Solder?? i see. thank you.
If the plating is still there what kind of solder you can use? lead or leaded?i guess have to add just a little for complete.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: RRZP028 on March 04, 2021, 09:41:54 PM
Hello, here I am after a break.
now I have encountered a problem that one capacitor that should pass a voltage of 0.7v does not give me any value. my question is whether to sell to replace with someone else from some other record or to do something else. The hash board is from T17e.
https://imgur.com/Gt9PdtL
https://imgur.com/gEsZ2Cb
https://imgur.com/TD6ZSAb
and I have another problem because when I'm on another hash board from the same machine it performs a voltage check on those capacitors, my test device started the hash board so now I don't know what to do with it because I just turned it off and didn't continue testing because other obligations.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: wndsnb on March 05, 2021, 01:57:31 PM
The side of the capacitor that your probe is touching in the image is the ground side, so it would always measure 0V. The other side should be 0.8V. The 1.8V and 0.8V flow through each chip to the next, in this image the signal travels A -> B -> C. The 0.8V enters the ASIC at A, and exits the chip at B. https://i.imgur.com/OwJLumV.png (https://i.imgur.com/OwJLumV.png) To make sure the connection is being made through the new ASIC you put down, measure the resistance between these two points indicated in the following image. The resistance should be less than 1 ohm. https://i.imgur.com/kM2ydzX.png (https://i.imgur.com/kM2ydzX.png)
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: RRZP028 on March 05, 2021, 10:07:53 PM
Dear Mr. wndsnb, can you tell me from which country, because I am from Europe, the state of Serbia, I am asking you so that I would know when you reply to our messages so that I can respond to you quickly and not just for a few hours.
I have no problem being next to the computer at any time of the day or night just to finally find a way to fix one hash board, also thanks for the tips so far.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: wndsnb on March 06, 2021, 02:19:20 AM
Dear Mr. wndsnb, can you tell me from which country
I'm from east coast USA, but I can't promise quick responses.... I'm pretty busy these days. I respond when I can find time....
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: Moeter81 on March 13, 2021, 05:55:17 AM
[...]
I just wanted to give you a status update. After I sent my defective miner to Bitmain on October 29th, a replacement device was sent to me from Hong Kong today. That was fast!!! I hope the device works longer. I have already bought the M30 + and M30 ++, they have been running without any problems so far and I am satisfied with them. From Bitmain, I will keep my distance first, have had too many defective devices (S17 +).
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: RadekG2 on March 29, 2021, 08:49:57 AM
Haha, same at my side. I sent 5 dead S17 to Bitmain during October and now, more than half year later they sent me 1 working and two dead units. I'll repair them by myself.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: wndsnb on March 29, 2021, 12:43:03 PM
My experience repairing these so far has shown that the faulty miners typically have multiple issues, and all the issues don't always present themselves. I run miners several days after a repair to make sure they are stable, and nearly 100% of the time they fail again, normally in different ways, within a few days. So not surprised to see a lot of reports of "repaired" miners arriving broken.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: Astra2000 on May 07, 2021, 09:36:58 PM
OMG, I have order and pay for a used S17+ from alibaba, I'm already scared what gonna append....
Any thoughts how to prevent the heat sinks from falling?
Any solutions for this problem?
Maybe laying the miner sideways instead upward?
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: mikeywith on May 08, 2021, 09:35:18 AM
OMG, I have order and pay for a used S17+ from alibaba, I'm already scared what gonna append....
Buy first and then do your research, way to go, my friend. :D Any thoughts how to prevent the heat sinks from falling?
Try to keep them cool that will help. Maybe laying the miner sideways instead upward?
some folks reported some tiny percentage of success by placing them horizontally, I'd say it's a fraction of an effect but well, why not? just make sure you place the chips up, the larger heatsink needs to face up.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: Astra2000 on May 08, 2021, 02:02:21 PM
yeh, I'm a mining newbie and I haven't though about the problems associate with the miners S17.
The turn off to buy the S19 was the price, they are selling for 15K and the S17 for 5k ... so for me was a no brainer LOL
maybe I sell it as soon I get them.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: robertpaulsen on October 16, 2021, 01:19:58 PM
I have an issue with my T17, one just 1 hashboard. Sometimes i get 0 asic found sometimes it finds all 30. But in any case, I get the error for all temp sensors on the board. I think I've went through most of the posts here and it most likely resembles the issue I quoted below. As I could see, most likely its loose heatsink, but after my (inexperienced) inspection, none seems loose when tested with mild pressure. Can anyone point me to some diy fix (I have only solder, no heatgun) or just take it to the repair shop? Here are the logs: When finding all asics:2021-10-14 17:42:05 driver-btm-api.c:631:init_freq_mode: This is scan-user version
2021-10-14 17:42:05 driver-btm-api.c:1994:bitmain_soc_init: opt_multi_version = 1
2021-10-14 17:42:05 driver-btm-api.c:1995:bitmain_soc_init: opt_bitmain_ab = 1
2021-10-14 17:42:05 driver-btm-api.c:1996:bitmain_soc_init: opt_bitmain_work_mode = 0
2021-10-14 17:42:05 driver-btm-api.c:1997:bitmain_soc_init: Miner compile time: Tue Dec 24 16:13:07 CST 2019 type: Antminer T17
2021-10-14 17:42:05 driver-btm-api.c:1998:bitmain_soc_init: commit version: e93a09b 2019-12-24 16:03:45, build by: lol 2019-12-24 16:19:49
2021-10-14 17:42:05 driver-btm-api.c:1810:show_sn: no SN got, please write SN to /nvdata/sn
2021-10-14 17:42:05 driver-btm-api.c:1135:miner_device_init: Detect 256MB control board of XILINX
2021-10-14 17:42:05 driver-btm-api.c:1083:init_fan_parameter: fan_eft : 0 fan_pwm : 0
2021-10-14 17:42:05 thread.c:789:create_read_nonce_reg_thread: create thread
2021-10-14 17:42:11 driver-btm-api.c:1067:init_miner_version: miner ID : 803c95042b104814
2021-10-14 17:42:11 driver-btm-api.c:1073:init_miner_version: FPGA Version = 0xB013
2021-10-14 17:42:13 eeprom.c:431:check_pattern_test_level: L1 board
2021-10-14 17:42:15 eeprom.c:431:check_pattern_test_level: L1 board
2021-10-14 17:42:16 eeprom.c:431:check_pattern_test_level: L1 board
2021-10-14 17:42:16 driver-btm-api.c:705:get_product_id: product_id[0] = 1
2021-10-14 17:42:16 driver-btm-api.c:705:get_product_id: product_id[1] = 1
2021-10-14 17:42:16 driver-btm-api.c:705:get_product_id: product_id[2] = 1
2021-10-14 17:42:16 driver-btm-api.c:1633:get_ccdly_opt: ccdly_opt[0] = 1
2021-10-14 17:42:16 driver-btm-api.c:1633:get_ccdly_opt: ccdly_opt[1] = 1
2021-10-14 17:42:16 driver-btm-api.c:1633:get_ccdly_opt: ccdly_opt[2] = 1
2021-10-14 17:42:16 driver-btm-api.c:1877:bitmain_board_init: g_ccdly_opt = 1
2021-10-14 17:42:16 driver-btm-api.c:644:_set_project_type: project:2
2021-10-14 17:42:17 driver-btm-api.c:674:_set_project_type: Project type: Antminer T17
2021-10-14 17:42:17 driver-btm-api.c:685:dump_pcb_bom_version: Chain [0] PCB Version: 0x0100
2021-10-14 17:42:17 driver-btm-api.c:686:dump_pcb_bom_version: Chain [0] BOM Version: 0x0100
2021-10-14 17:42:17 driver-btm-api.c:685:dump_pcb_bom_version: Chain [1] PCB Version: 0x0100
2021-10-14 17:42:17 driver-btm-api.c:686:dump_pcb_bom_version: Chain [1] BOM Version: 0x0100
2021-10-14 17:42:17 driver-btm-api.c:685:dump_pcb_bom_version: Chain [2] PCB Version: 0x0100
2021-10-14 17:42:17 driver-btm-api.c:686:dump_pcb_bom_version: Chain [2] BOM Version: 0x0100
2021-10-14 17:42:18 driver-btm-api.c:1897:bitmain_board_init: Fan check passed.
2021-10-14 17:42:19 board.c:36:jump_and_app_check_restore_pic: chain[0] PIC jump to app
2021-10-14 17:42:23 board.c:40:jump_and_app_check_restore_pic: Check chain[0] PIC fw version=0xb9
2021-10-14 17:42:24 board.c:36:jump_and_app_check_restore_pic: chain[1] PIC jump to app
2021-10-14 17:42:28 board.c:40:jump_and_app_check_restore_pic: Check chain[1] PIC fw version=0xb9
2021-10-14 17:42:30 board.c:36:jump_and_app_check_restore_pic: chain[2] PIC jump to app
2021-10-14 17:42:33 board.c:40:jump_and_app_check_restore_pic: Check chain[2] PIC fw version=0xb9
2021-10-14 17:42:33 thread.c:784:create_pic_heart_beat_thread: create thread
2021-10-14 17:42:33 power_api.c:55:power_init: power init ...
2021-10-14 17:42:33 driver-btm-api.c:1907:bitmain_board_init: Enter 30s sleep to make sure power release finish.
2021-10-14 17:43:05 power_api.c:232:set_iic_power_to_highest_voltage: setting to voltage: 17.00 ...
2021-10-14 17:43:11 power_api.c:124:check_voltage_multi: retry time: 0
2021-10-14 17:43:13 power_api.c:86:get_average_voltage: chain[0], voltage is: 17.677236
2021-10-14 17:43:14 power_api.c:86:get_average_voltage: chain[1], voltage is: 17.120039
2021-10-14 17:43:16 power_api.c:86:get_average_voltage: chain[2], voltage is: 16.917978
2021-10-14 17:43:16 power_api.c:97:get_average_voltage: aveage voltage is: 17.238418
2021-10-14 17:43:16 power_api.c:182:set_iic_power_by_voltage: now set voltage to : 17.000000
2021-10-14 17:43:16 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[0]: chip baud = 115200, chip_divider = 26
2021-10-14 17:43:16 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[1]: chip baud = 115200, chip_divider = 26
2021-10-14 17:43:16 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[2]: chip baud = 115200, chip_divider = 26
2021-10-14 17:43:16 uart.c:80:set_baud: set fpga_baud = 115200, fpga_divider = 26
2021-10-14 17:43:28 driver-btm-api.c:1010:check_asic_number_with_power_on: Chain[0]: find 30 asic, times 0
2021-10-14 17:43:38 driver-btm-api.c:1010:check_asic_number_with_power_on: Chain[1]: find 30 asic, times 0
2021-10-14 17:43:48 driver-btm-api.c:1010:check_asic_number_with_power_on: Chain[2]: find 30 asic, times 0
2021-10-14 17:43:51 driver-btm-api.c:348:set_order_clock: chain[0]: set order clock, stragegy 3 clock_en=0x1
2021-10-14 17:43:51 driver-btm-api.c:348:set_order_clock: chain[1]: set order clock, stragegy 3 clock_en=0x1
2021-10-14 17:43:52 driver-btm-api.c:348:set_order_clock: chain[2]: set order clock, stragegy 3 clock_en=0x1
2021-10-14 17:43:52 driver-hash-chip.c:490:set_clock_delay_control: core_data = 0xb4
2021-10-14 17:43:52 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[0]: chip baud = 3000000, chip_divider = 0
2021-10-14 17:43:52 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[1]: chip baud = 3000000, chip_divider = 0
2021-10-14 17:43:52 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[2]: chip baud = 3000000, chip_divider = 0
2021-10-14 17:43:52 uart.c:80:set_baud: set fpga_baud = 3000000, fpga_divider = 0
2021-10-14 17:43:52 driver-btm-api.c:1660:check_clock_counter: freq 50 clock_counter_limit 6
2021-10-14 17:43:53 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[0]: chip baud = 115200, chip_divider = 26
2021-10-14 17:43:53 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[1]: chip baud = 115200, chip_divider = 26
2021-10-14 17:43:53 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[2]: chip baud = 115200, chip_divider = 26
2021-10-14 17:43:53 uart.c:80:set_baud: set fpga_baud = 115200, fpga_divider = 26
2021-10-14 17:43:53 voltage[0] = 1690
2021-10-14 17:43:53 voltage[1] = 1690
2021-10-14 17:43:53 voltage[2] = 1690
2021-10-14 17:43:53 power_api.c:140:set_working_voltage: working_voltage = 16.900000
2021-10-14 17:43:54 temperature.c:282:calibrate_temp_sensor_one_chain: Temperature sensor calibration: chain 0 success.
2021-10-14 17:43:55 temperature.c:282:calibrate_temp_sensor_one_chain: Temperature sensor calibration: chain 1 success.
2021-10-14 17:43:57 temperature.c:282:calibrate_temp_sensor_one_chain: Temperature sensor calibration: chain 2 success.
2021-10-14 17:43:57 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[0]: chip baud = 6000000, chip_divider = 7
2021-10-14 17:43:57 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[1]: chip baud = 6000000, chip_divider = 7
2021-10-14 17:43:57 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[2]: chip baud = 6000000, chip_divider = 7
2021-10-14 17:43:57 uart.c:80:set_baud: set fpga_baud = 6000000, fpga_divider = 3
2021-10-14 17:43:59 driver-btm-api.c:248:check_bringup_temp: Bring up temperature is 21
2021-10-14 17:43:59 thread.c:804:create_check_miner_status_thread: create thread
2021-10-14 17:43:59 thread.c:794:create_set_miner_status_thread: create thread
2021-10-14 17:43:59 driver-btm-api.c:581:calculate_timeout: dev->timeout = 392
2021-10-14 17:43:59 thread.c:779:create_temperature_monitor_thread: create thread
2021-10-14 17:43:59 freq_tuning.c:154:freq_tuning_get_max_freq: Max freq of tuning is 760
2021-10-14 17:43:59 power_api.c:379:slowly_set_iic_power_to_custom_voltage: slowly setting to voltage: 17.80 ...
2021-10-14 17:44:33 power_api.c:124:check_voltage_multi: retry time: 0
2021-10-14 17:44:35 power_api.c:86:get_average_voltage: chain[0], voltage is: 17.781328
2021-10-14 17:44:37 power_api.c:86:get_average_voltage: chain[1], voltage is: 17.769082
2021-10-14 17:44:39 power_api.c:86:get_average_voltage: chain[2], voltage is: 17.744590
2021-10-14 17:44:39 power_api.c:97:get_average_voltage: aveage voltage is: 17.765000
2021-10-14 17:44:39 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 44 set refdiv: 2, fbdiv: 173, postdiv1: 7, postdiv2: 7, usr divider: 1
2021-10-14 17:44:39 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 51 set refdiv: 2, fbdiv: 173, postdiv1: 7, postdiv2: 6, usr divider: 1
2021-10-14 17:44:39 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 61 set refdiv: 2, fbdiv: 173, postdiv1: 7, postdiv2: 5, usr divider: 1
2021-10-14 17:44:39 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 77 set refdiv: 2, fbdiv: 173, postdiv1: 7, postdiv2: 4, usr divider: 1
2021-10-14 17:44:39 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 102 set refdiv: 2, fbdiv: 173, postdiv1: 7, postdiv2: 3, usr divider: 1
2021-10-14 17:44:39 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 154 set refdiv: 2, fbdiv: 173, postdiv1: 7, postdiv2: 2, usr divider: 1
2021-10-14 17:44:39 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 308 set refdiv: 2, fbdiv: 173, postdiv1: 7, postdiv2: 1, usr divider: 1
2021-10-14 17:44:39 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 360 set refdiv: 2, fbdiv: 173, postdiv1: 6, postdiv2: 1, usr divider: 1
2021-10-14 17:44:40 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 432 set refdiv: 2, fbdiv: 173, postdiv1: 5, postdiv2: 1, usr divider: 1
2021-10-14 17:44:40 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 540 set refdiv: 2, fbdiv: 173, postdiv1: 4, postdiv2: 1, usr divider: 1
2021-10-14 17:44:40 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 720 set refdiv: 2, fbdiv: 173, postdiv1: 3, postdiv2: 1, usr divider: 1
2021-10-14 17:44:40 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 44 set refdiv: 2, fbdiv: 173, postdiv1: 7, postdiv2: 7, usr divider: 1
2021-10-14 17:44:40 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 51 set refdiv: 2, fbdiv: 173, postdiv1: 7, postdiv2: 6, usr divider: 1
2021-10-14 17:44:40 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 61 set refdiv: 2, fbdiv: 173, postdiv1: 7, postdiv2: 5, usr divider: 1
2021-10-14 17:44:40 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 77 set refdiv: 2, fbdiv: 173, postdiv1: 7, postdiv2: 4, usr divider: 1
2021-10-14 17:44:40 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 102 set refdiv: 2, fbdiv: 173, postdiv1: 7, postdiv2: 3, usr divider: 1
2021-10-14 17:44:40 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 154 set refdiv: 2, fbdiv: 173, postdiv1: 7, postdiv2: 2, usr divider: 1
2021-10-14 17:44:41 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 308 set refdiv: 2, fbdiv: 173, postdiv1: 7, postdiv2: 1, usr divider: 1
2021-10-14 17:44:41 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 360 set refdiv: 2, fbdiv: 173, postdiv1: 6, postdiv2: 1, usr divider: 1
2021-10-14 17:44:41 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 432 set refdiv: 2, fbdiv: 173, postdiv1: 5, postdiv2: 1, usr divider: 1
2021-10-14 17:44:41 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 540 set refdiv: 2, fbdiv: 173, postdiv1: 4, postdiv2: 1, usr divider: 1
2021-10-14 17:44:41 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 720 set refdiv: 2, fbdiv: 173, postdiv1: 3, postdiv2: 1, usr divider: 1
2021-10-14 17:44:41 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 44 set refdiv: 2, fbdiv: 173, postdiv1: 7, postdiv2: 7, usr divider: 1
2021-10-14 17:44:41 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 51 set refdiv: 2, fbdiv: 173, postdiv1: 7, postdiv2: 6, usr divider: 1
2021-10-14 17:44:41 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 61 set refdiv: 2, fbdiv: 173, postdiv1: 7, postdiv2: 5, usr divider: 1
2021-10-14 17:44:41 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 77 set refdiv: 2, fbdiv: 173, postdiv1: 7, postdiv2: 4, usr divider: 1
2021-10-14 17:44:41 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 102 set refdiv: 2, fbdiv: 173, postdiv1: 7, postdiv2: 3, usr divider: 1
2021-10-14 17:44:42 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 154 set refdiv: 2, fbdiv: 173, postdiv1: 7, postdiv2: 2, usr divider: 1
2021-10-14 17:44:42 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 308 set refdiv: 2, fbdiv: 173, postdiv1: 7, postdiv2: 1, usr divider: 1
2021-10-14 17:44:42 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 360 set refdiv: 2, fbdiv: 173, postdiv1: 6, postdiv2: 1, usr divider: 1
2021-10-14 17:44:42 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 432 set refdiv: 2, fbdiv: 173, postdiv1: 5, postdiv2: 1, usr divider: 1
2021-10-14 17:44:42 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 540 set refdiv: 2, fbdiv: 173, postdiv1: 4, postdiv2: 1, usr divider: 1
2021-10-14 17:44:42 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 720 set refdiv: 2, fbdiv: 173, postdiv1: 3, postdiv2: 1, usr divider: 1
2021-10-14 17:44:42 driver-btm-api.c:612:set_timeout: freq 720 final timeout=163
2021-10-14 17:44:42 power_api.c:397:slowly_set_iic_power_to_working_voltage: slowly setting to voltage: 16.90 ...
2021-10-14 17:44:48 temperature.c:697:get_temp_info: read temp sensor failed: chain = 0, sensor = 0, chip = 64, reg = 0
2021-10-14 17:45:01 temperature.c:697:get_temp_info: read temp sensor failed: chain = 0, sensor = 0, chip = 64, reg = 1
2021-10-14 17:45:07 temperature.c:697:get_temp_info: read temp sensor failed: chain = 0, sensor = 1, chip = 48, reg = 0
2021-10-14 17:45:17 power_api.c:124:check_voltage_multi: retry time: 0
2021-10-14 17:45:19 power_api.c:86:get_average_voltage: chain[0], voltage is: 16.783271
2021-10-14 17:45:20 temperature.c:697:get_temp_info: read temp sensor failed: chain = 0, sensor = 1, chip = 48, reg = 1
2021-10-14 17:45:21 power_api.c:86:get_average_voltage: chain[1], voltage is: 16.771025
2021-10-14 17:45:22 power_api.c:86:get_average_voltage: chain[2], voltage is: 16.979209
2021-10-14 17:45:22 power_api.c:97:get_average_voltage: aveage voltage is: 16.844502
2021-10-14 17:45:22 frequency.c:540:get_current_min_freq: current min freq 720
2021-10-14 17:45:22 driver-btm-api.c:1660:check_clock_counter: freq 720 clock_counter_limit 92
2021-10-14 17:45:27 temperature.c:697:get_temp_info: read temp sensor failed: chain = 0, sensor = 2, chip = 168, reg = 0
2021-10-14 17:45:40 temperature.c:697:get_temp_info: read temp sensor failed: chain = 0, sensor = 2, chip = 168, reg = 1
2021-10-14 17:45:47 temperature.c:697:get_temp_info: read temp sensor failed: chain = 0, sensor = 3, chip = 184, reg = 0
2021-10-14 17:46:00 temperature.c:697:get_temp_info: read temp sensor failed: chain = 0, sensor = 3, chip = 184, reg = 1
2021-10-14 17:46:04 register.c:1416:quick_dump_core_hash_clock_counter: bad clock counter. chain = 0, asic = 5, core = 0, found 0, clock counter 0x00000000
2021-10-14 17:46:04 driver-btm-api.c:2097:bitmain_soc_init: clock count check failed after retry, wait for hash rate protect later.
2021-10-14 17:46:04 thread.c:799:create_check_system_status_thread: create thread
2021-10-14 17:46:04 driver-btm-api.c:2113:bitmain_soc_init: Init done!
2021-10-14 17:46:04 driver-btm-api.c:201:set_miner_status: STATUS_INIT
2021-10-14 17:46:09 driver-btm-api.c:201:set_miner_status: STATUS_OKAY
2021-10-14 17:46:10 temperature.c:697:get_temp_info: read temp sensor failed: chain = 0, sensor = 0, chip = 64, reg = 0
2021-10-14 17:46:14 driver-btm-api.c:1293:dhash_chip_send_job: Version num 4
2021-10-14 17:46:24 temperature.c:697:get_temp_info: read temp sensor failed: chain = 0, sensor = 0, chip = 64, reg = 1
2021-10-14 17:46:30 temperature.c:697:get_temp_info: read temp sensor failed: chain = 0, sensor = 1, chip = 48, reg = 0
2021-10-14 17:46:43 temperature.c:697:get_temp_info: read temp sensor failed: chain = 0, sensor = 1, chip = 48, reg = 1
2021-10-14 17:46:50 temperature.c:697:get_temp_info: read temp sensor failed: chain = 0, sensor = 2, chip = 168, reg = 0
2021-10-14 17:47:03 temperature.c:697:get_temp_info: read temp sensor failed: chain = 0, sensor = 2, chip = 168, reg = 1
2021-10-14 17:47:09 temperature.c:697:get_temp_info: read temp sensor failed: chain = 0, sensor = 3, chip = 184, reg = 0
2021-10-14 17:47:23 temperature.c:697:get_temp_info: read temp sensor failed: chain = 0, sensor = 3, chip = 184, reg = 1
2021-10-14 17:47:31 temperature.c:697:get_temp_info: read temp sensor failed: chain = 0, sensor = 0, chip = 64, reg = 0
2021-10-14 17:47:44 temperature.c:697:get_temp_info: read temp sensor failed: chain = 0, sensor = 0, chip = 64, reg = 1
2021-10-14 17:47:51 temperature.c:697:get_temp_info: read temp sensor failed: chain = 0, sensor = 1, chip = 48, reg = 0
2021-10-14 17:48:04 temperature.c:697:get_temp_info: read temp sensor failed: chain = 0, sensor = 1, chip = 48, reg = 1
2021-10-14 17:48:11 temperature.c:697:get_temp_info: read temp sensor failed: chain = 0, sensor = 2, chip = 168, reg = 0
2021-10-14 17:48:24 temperature.c:697:get_temp_info: read temp sensor failed: chain = 0, sensor = 2, chip = 168, reg = 1
2021-10-14 17:48:30 temperature.c:697:get_temp_info: read temp sensor failed: chain = 0, sensor = 3, chip = 184, reg = 0
2021-10-14 17:48:43 temperature.c:697:get_temp_info: read temp sensor failed: chain = 0, sensor = 3, chip = 184, reg = 1
2021-10-14 17:48:52 temperature.c:697:get_temp_info: read temp sensor failed: chain = 0, sensor = 0, chip = 64, reg = 0
2021-10-14 17:49:05 temperature.c:697:get_temp_info: read temp sensor failed: chain = 0, sensor = 0, chip = 64, reg = 1
2021-10-14 17:49:12 temperature.c:697:get_temp_info: read temp sensor failed: chain = 0, sensor = 1, chip = 48, reg = 0
2021-10-14 17:49:25 temperature.c:697:get_temp_info: read temp sensor failed: chain = 0, sensor = 1, chip = 48, reg = 1
2021-10-14 17:49:31 temperature.c:697:get_temp_info: read temp sensor failed: chain = 0, sensor = 2, chip = 168, reg = 0
2021-10-14 17:49:44 temperature.c:697:get_temp_info: read temp sensor failed: chain = 0, sensor = 2, chip = 168, reg = 1
2021-10-14 17:49:51 temperature.c:697:get_temp_info: read temp sensor failed: chain = 0, sensor = 3, chip = 184, reg = 0
2021-10-14 17:50:04 temperature.c:697:get_temp_info: read temp sensor failed: chain = 0, sensor = 3, chip = 184, reg = 1
2021-10-14 17:50:13 temperature.c:697:get_temp_info: read temp sensor failed: chain = 0, sensor = 0, chip = 64, reg = 0
2021-10-14 17:50:26 temperature.c:697:get_temp_info: read temp sensor failed: chain = 0, sensor = 0, chip = 64, reg = 1
2021-10-14 17:50:32 temperature.c:697:get_temp_info: read temp sensor failed: chain = 0, sensor = 1, chip = 48, reg = 0
2021-10-14 17:50:46 temperature.c:697:get_temp_info: read temp sensor failed: chain = 0, sensor = 1, chip = 48, reg = 1
2021-10-14 17:50:52 temperature.c:697:get_temp_info: read temp sensor failed: chain = 0, sensor = 2, chip = 168, reg = 0
2021-10-14 17:51:05 temperature.c:697:get_temp_info: read temp sensor failed: chain = 0, sensor = 2, chip = 168, reg = 1
2021-10-14 17:51:12 temperature.c:697:get_temp_info: read temp sensor failed: chain = 0, sensor = 3, chip = 184, reg = 0
2021-10-14 17:51:13 thread.c:422:is_zero_nonce_happened: chain_nonce[0] = 0
2021-10-14 17:51:13 thread.c:422:is_zero_nonce_happened: chain_nonce[1] = 15697
2021-10-14 17:51:13 thread.c:422:is_zero_nonce_happened: chain_nonce[2] = 15686
2021-10-14 17:51:13 thread.c:539:check_system_work_thread: 0 nonce rate happened after retry, wait for hash rate protect later.
2021-10-14 17:51:25 temperature.c:697:get_temp_info: read temp sensor failed: chain = 0, sensor = 3, chip = 184, reg = 1
2021-10-14 17:51:33 temperature.c:697:get_temp_info: read temp sensor failed: chain = 0, sensor = 0, chip = 64, reg = 0 2021-10-14 17:24:48 driver-btm-api.c:631:init_freq_mode: This is scan-user version
2021-10-14 17:24:48 driver-btm-api.c:1994:bitmain_soc_init: opt_multi_version = 1
2021-10-14 17:24:48 driver-btm-api.c:1995:bitmain_soc_init: opt_bitmain_ab = 1
2021-10-14 17:24:48 driver-btm-api.c:1996:bitmain_soc_init: opt_bitmain_work_mode = 0
2021-10-14 17:24:48 driver-btm-api.c:1997:bitmain_soc_init: Miner compile time: Tue Dec 24 16:13:07 CST 2019 type: Antminer T17
2021-10-14 17:24:48 driver-btm-api.c:1998:bitmain_soc_init: commit version: e93a09b 2019-12-24 16:03:45, build by: lol 2019-12-24 16:19:49
2021-10-14 17:24:48 driver-btm-api.c:1810:show_sn: no SN got, please write SN to /nvdata/sn
2021-10-14 17:24:48 driver-btm-api.c:1135:miner_device_init: Detect 256MB control board of XILINX
2021-10-14 17:24:48 driver-btm-api.c:1083:init_fan_parameter: fan_eft : 0 fan_pwm : 0
2021-10-14 17:24:48 thread.c:789:create_read_nonce_reg_thread: create thread
2021-10-14 17:24:54 driver-btm-api.c:1067:init_miner_version: miner ID : 803c95042b104814
2021-10-14 17:24:54 driver-btm-api.c:1073:init_miner_version: FPGA Version = 0xB013
2021-10-14 17:24:56 eeprom.c:431:check_pattern_test_level: L1 board
2021-10-14 17:24:58 eeprom.c:431:check_pattern_test_level: L1 board
2021-10-14 17:24:59 eeprom.c:431:check_pattern_test_level: L1 board
2021-10-14 17:24:59 driver-btm-api.c:705:get_product_id: product_id[0] = 1
2021-10-14 17:24:59 driver-btm-api.c:705:get_product_id: product_id[1] = 1
2021-10-14 17:24:59 driver-btm-api.c:705:get_product_id: product_id[2] = 1
2021-10-14 17:24:59 driver-btm-api.c:1633:get_ccdly_opt: ccdly_opt[0] = 1
2021-10-14 17:24:59 driver-btm-api.c:1633:get_ccdly_opt: ccdly_opt[1] = 1
2021-10-14 17:24:59 driver-btm-api.c:1633:get_ccdly_opt: ccdly_opt[2] = 1
2021-10-14 17:24:59 driver-btm-api.c:1877:bitmain_board_init: g_ccdly_opt = 1
2021-10-14 17:24:59 driver-btm-api.c:644:_set_project_type: project:2
2021-10-14 17:24:59 driver-btm-api.c:674:_set_project_type: Project type: Antminer T17
2021-10-14 17:24:59 driver-btm-api.c:685:dump_pcb_bom_version: Chain [0] PCB Version: 0x0100
2021-10-14 17:24:59 driver-btm-api.c:686:dump_pcb_bom_version: Chain [0] BOM Version: 0x0100
2021-10-14 17:24:59 driver-btm-api.c:685:dump_pcb_bom_version: Chain [1] PCB Version: 0x0100
2021-10-14 17:24:59 driver-btm-api.c:686:dump_pcb_bom_version: Chain [1] BOM Version: 0x0100
2021-10-14 17:24:59 driver-btm-api.c:685:dump_pcb_bom_version: Chain [2] PCB Version: 0x0100
2021-10-14 17:24:59 driver-btm-api.c:686:dump_pcb_bom_version: Chain [2] BOM Version: 0x0100
2021-10-14 17:24:59 driver-btm-api.c:1897:bitmain_board_init: Fan check passed.
2021-10-14 17:25:01 board.c:36:jump_and_app_check_restore_pic: chain[0] PIC jump to app
2021-10-14 17:25:05 board.c:40:jump_and_app_check_restore_pic: Check chain[0] PIC fw version=0xb9
2021-10-14 17:25:06 board.c:36:jump_and_app_check_restore_pic: chain[1] PIC jump to app
2021-10-14 17:25:10 board.c:40:jump_and_app_check_restore_pic: Check chain[1] PIC fw version=0xb9
2021-10-14 17:25:12 board.c:36:jump_and_app_check_restore_pic: chain[2] PIC jump to app
2021-10-14 17:25:15 board.c:40:jump_and_app_check_restore_pic: Check chain[2] PIC fw version=0xb9
2021-10-14 17:25:15 thread.c:784:create_pic_heart_beat_thread: create thread
2021-10-14 17:25:15 power_api.c:55:power_init: power init ...
2021-10-14 17:25:15 driver-btm-api.c:1907:bitmain_board_init: Enter 30s sleep to make sure power release finish.
2021-10-14 17:25:47 power_api.c:232:set_iic_power_to_highest_voltage: setting to voltage: 17.00 ...
2021-10-14 17:25:53 power_api.c:124:check_voltage_multi: retry time: 0
2021-10-14 17:25:54 power_api.c:86:get_average_voltage: chain[0], voltage is: 17.003701
2021-10-14 17:25:56 power_api.c:86:get_average_voltage: chain[1], voltage is: 17.003701
2021-10-14 17:25:58 power_api.c:86:get_average_voltage: chain[2], voltage is: 16.966963
2021-10-14 17:25:58 power_api.c:97:get_average_voltage: aveage voltage is: 16.991455
2021-10-14 17:25:58 power_api.c:182:set_iic_power_by_voltage: now set voltage to : 17.000000
2021-10-14 17:25:58 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[0]: chip baud = 115200, chip_divider = 26
2021-10-14 17:25:58 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[1]: chip baud = 115200, chip_divider = 26
2021-10-14 17:25:58 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[2]: chip baud = 115200, chip_divider = 26
2021-10-14 17:25:58 uart.c:80:set_baud: set fpga_baud = 115200, fpga_divider = 26
2021-10-14 17:26:09 driver-btm-api.c:1010:check_asic_number_with_power_on: Chain[0]: find 0 asic, times 0
2021-10-14 17:26:19 driver-btm-api.c:1010:check_asic_number_with_power_on: Chain[0]: find 0 asic, times 1
2021-10-14 17:26:29 driver-btm-api.c:1010:check_asic_number_with_power_on: Chain[0]: find 0 asic, times 2
2021-10-14 17:26:29 driver-btm-api.c:1037:check_asic_number: Chain 0 only find 0 asic, will power off hash board 0
2021-10-14 17:26:41 driver-btm-api.c:1010:check_asic_number_with_power_on: Chain[1]: find 30 asic, times 0
2021-10-14 17:26:51 driver-btm-api.c:1010:check_asic_number_with_power_on: Chain[2]: find 30 asic, times 0
2021-10-14 17:26:54 driver-btm-api.c:348:set_order_clock: chain[1]: set order clock, stragegy 3 clock_en=0x1
2021-10-14 17:26:54 driver-btm-api.c:348:set_order_clock: chain[2]: set order clock, stragegy 3 clock_en=0x1
2021-10-14 17:26:54 driver-hash-chip.c:490:set_clock_delay_control: core_data = 0xb4
2021-10-14 17:26:54 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[1]: chip baud = 3000000, chip_divider = 0
2021-10-14 17:26:54 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[2]: chip baud = 3000000, chip_divider = 0
2021-10-14 17:26:54 uart.c:80:set_baud: set fpga_baud = 3000000, fpga_divider = 0
2021-10-14 17:26:54 driver-btm-api.c:1660:check_clock_counter: freq 50 clock_counter_limit 6
2021-10-14 17:26:55 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[1]: chip baud = 115200, chip_divider = 26
2021-10-14 17:26:55 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[2]: chip baud = 115200, chip_divider = 26
2021-10-14 17:26:55 uart.c:80:set_baud: set fpga_baud = 115200, fpga_divider = 26
2021-10-14 17:26:55 voltage[1] = 1690
2021-10-14 17:26:55 voltage[2] = 1690
2021-10-14 17:26:55 power_api.c:140:set_working_voltage: working_voltage = 16.900000
2021-10-14 17:26:56 temperature.c:282:calibrate_temp_sensor_one_chain: Temperature sensor calibration: chain 1 success.
2021-10-14 17:26:57 temperature.c:282:calibrate_temp_sensor_one_chain: Temperature sensor calibration: chain 2 success.
2021-10-14 17:26:57 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[1]: chip baud = 6000000, chip_divider = 7
2021-10-14 17:26:57 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[2]: chip baud = 6000000, chip_divider = 7
2021-10-14 17:26:57 uart.c:80:set_baud: set fpga_baud = 6000000, fpga_divider = 3
2021-10-14 17:26:59 driver-btm-api.c:248:check_bringup_temp: Bring up temperature is 25
2021-10-14 17:26:59 thread.c:804:create_check_miner_status_thread: create thread
2021-10-14 17:26:59 thread.c:794:create_set_miner_status_thread: create thread
2021-10-14 17:26:59 driver-btm-api.c:581:calculate_timeout: dev->timeout = 392
2021-10-14 17:26:59 thread.c:779:create_temperature_monitor_thread: create thread
2021-10-14 17:26:59 freq_tuning.c:154:freq_tuning_get_max_freq: Max freq of tuning is 760
2021-10-14 17:26:59 power_api.c:379:slowly_set_iic_power_to_custom_voltage: slowly setting to voltage: 17.80 ...
2021-10-14 17:27:30 power_api.c:124:check_voltage_multi: retry time: 0
2021-10-14 17:27:33 power_api.c:86:get_average_voltage: chain[1], voltage is: 17.781328
2021-10-14 17:27:36 power_api.c:86:get_average_voltage: chain[2], voltage is: 17.769082
2021-10-14 17:27:36 power_api.c:97:get_average_voltage: aveage voltage is: 17.775205
2021-10-14 17:27:36 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 44 set refdiv: 2, fbdiv: 173, postdiv1: 7, postdiv2: 7, usr divider: 1
2021-10-14 17:27:37 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 51 set refdiv: 2, fbdiv: 173, postdiv1: 7, postdiv2: 6, usr divider: 1
2021-10-14 17:27:37 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 61 set refdiv: 2, fbdiv: 173, postdiv1: 7, postdiv2: 5, usr divider: 1
2021-10-14 17:27:37 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 77 set refdiv: 2, fbdiv: 173, postdiv1: 7, postdiv2: 4, usr divider: 1
2021-10-14 17:27:37 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 102 set refdiv: 2, fbdiv: 173, postdiv1: 7, postdiv2: 3, usr divider: 1
2021-10-14 17:27:37 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 154 set refdiv: 2, fbdiv: 173, postdiv1: 7, postdiv2: 2, usr divider: 1
2021-10-14 17:27:37 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 308 set refdiv: 2, fbdiv: 173, postdiv1: 7, postdiv2: 1, usr divider: 1
2021-10-14 17:27:37 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 360 set refdiv: 2, fbdiv: 173, postdiv1: 6, postdiv2: 1, usr divider: 1
2021-10-14 17:27:37 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 432 set refdiv: 2, fbdiv: 173, postdiv1: 5, postdiv2: 1, usr divider: 1
2021-10-14 17:27:37 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 540 set refdiv: 2, fbdiv: 173, postdiv1: 4, postdiv2: 1, usr divider: 1
2021-10-14 17:27:37 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 720 set refdiv: 2, fbdiv: 173, postdiv1: 3, postdiv2: 1, usr divider: 1
2021-10-14 17:27:38 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 44 set refdiv: 2, fbdiv: 173, postdiv1: 7, postdiv2: 7, usr divider: 1
2021-10-14 17:27:38 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 51 set refdiv: 2, fbdiv: 173, postdiv1: 7, postdiv2: 6, usr divider: 1
2021-10-14 17:27:38 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 61 set refdiv: 2, fbdiv: 173, postdiv1: 7, postdiv2: 5, usr divider: 1
2021-10-14 17:27:38 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 77 set refdiv: 2, fbdiv: 173, postdiv1: 7, postdiv2: 4, usr divider: 1
2021-10-14 17:27:38 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 102 set refdiv: 2, fbdiv: 173, postdiv1: 7, postdiv2: 3, usr divider: 1
2021-10-14 17:27:38 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 154 set refdiv: 2, fbdiv: 173, postdiv1: 7, postdiv2: 2, usr divider: 1
2021-10-14 17:27:38 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 308 set refdiv: 2, fbdiv: 173, postdiv1: 7, postdiv2: 1, usr divider: 1
2021-10-14 17:27:38 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 360 set refdiv: 2, fbdiv: 173, postdiv1: 6, postdiv2: 1, usr divider: 1
2021-10-14 17:27:38 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 432 set refdiv: 2, fbdiv: 173, postdiv1: 5, postdiv2: 1, usr divider: 1
2021-10-14 17:27:39 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 540 set refdiv: 2, fbdiv: 173, postdiv1: 4, postdiv2: 1, usr divider: 1
2021-10-14 17:27:39 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 720 set refdiv: 2, fbdiv: 173, postdiv1: 3, postdiv2: 1, usr divider: 1
2021-10-14 17:27:39 driver-btm-api.c:612:set_timeout: freq 720 final timeout=163
2021-10-14 17:27:39 power_api.c:397:slowly_set_iic_power_to_working_voltage: slowly setting to voltage: 16.90 ...
2021-10-14 17:27:58 thread.c:642:check_temperature: over max temp, pcb temp 59 (max 80), chip temp 106(max 103)
2021-10-14 17:27:58 driver-btm-api.c:201:set_miner_status: ERROR_TEMP_TOO_HIGH
2021-10-14 17:27:58 driver-btm-api.c:142:stop_mining: stop mining: over max temp
2021-10-14 17:27:58 thread.c:824:cancel_temperature_monitor_thread: cancel thread
2021-10-14 17:27:58 thread.c:834:cancel_read_nonce_reg_thread: cancel thread
2021-10-14 17:27:58 driver-btm-api.c:128:killall_hashboard: ****power off hashboard****
2021-10-14 17:28:09 power_api.c:124:check_voltage_multi: retry time: 0
2021-10-14 17:28:11 power_api.c:86:get_average_voltage: chain[1], voltage is: 16.948594
2021-10-14 17:28:13 power_api.c:86:get_average_voltage: chain[2], voltage is: 17.205762
2021-10-14 17:28:13 power_api.c:97:get_average_voltage: aveage voltage is: 17.077178
2021-10-14 17:28:13 frequency.c:540:get_current_min_freq: current min freq 720
2021-10-14 17:28:13 driver-btm-api.c:1660:check_clock_counter: freq 720 clock_counter_limit 92
2021-10-14 17:28:16 register.c:1416:quick_dump_core_hash_clock_counter: bad clock counter. chain = 1, asic = 5, core = 0, found 0, clock counter 0x00000000
2021-10-14 17:28:16 driver-btm-api.c:2097:bitmain_soc_init: clock count check failed after retry, wait for hash rate protect later.
2021-10-14 17:28:16 thread.c:799:create_check_system_status_thread: create thread
2021-10-14 17:28:16 driver-btm-api.c:2113:bitmain_soc_init: Init done!
2021-10-14 17:28:16 driver-btm-api.c:201:set_miner_status: STATUS_INIT
2021-10-14 17:28:21 driver-btm-api.c:201:set_miner_status: STATUS_OKAY
2021-10-14 17:28:25 driver-btm-api.c:1293:dhash_chip_send_job: Version num 4 I wouldnt want to use any permeneatny adhesive. Im looking to apply solder. What solder do you know I can use for this that can be taken off and on. Also I have a whole bunch of boards that have the same exact errors when I run the test fixture. All the asic are found but I still get a temp sensor error. 1970-01-01 00:01:52 register.c:185:read_asic_reg_with_addr: read asic reg timeout: expect chain = 0, chip = 14, reg = 28
1970-01-01 00:01:52 register.c:185:read_asic_reg_with_addr: read asic reg timeout: expect chain = 0, chip = 14, reg = 28
1970-01-01 00:01:53 temperature.c:744:get_temp_info: read temp sensor failed: chain = 0, sensor = 0, chip = 14, reg = 1
...
1970-01-01 00:01:53 register.c:185:read_asic_reg_with_addr: read asic reg timeout: expect chain = 0, chip = 10, reg = 28
1970-01-01 00:01:53 register.c:185:read_asic_reg_with_addr: read asic reg timeout: expect chain = 0, chip = 10, reg = 28
1970-01-01 00:01:54 temperature.c:744:get_temp_info: read temp sensor failed: chain = 0, sensor = 1, chip = 10, reg = 1
...
1970-01-01 00:01:54 register.c:185:read_asic_reg_with_addr: read asic reg timeout: expect chain = 0, chip = 54, reg = 28
1970-01-01 00:01:54 register.c:185:read_asic_reg_with_addr: read asic reg timeout: expect chain = 0, chip = 54, reg = 28
1970-01-01 00:01:54 register.c:185:read_asic_reg_with_addr: read asic reg timeout: expect chain = 0, chip = 54, reg = 28
1970-01-01 00:01:55 temperature.c:744:get_temp_info: read temp sensor failed: chain = 0, sensor = 2, chip = 54, reg = 1
1970-01-01 00:01:55 register.c:185:read_asic_reg_with_addr: read asic reg timeout: expect chain = 0, chip = 50, reg = 28
1970-01-01 00:01:55 register.c:185:read_asic_reg_with_addr: read asic reg timeout: expect chain = 0, chip = 50, reg = 28
...
1970-01-01 00:01:56 temperature.c:744:get_temp_info: read temp sensor failed: chain = 0, sensor = 3, chip = 50, reg = 1
1970-01-01 00:01:56 single_board_test.c:1659:wait_warm_up: temper sensor bad
I have this same exact error for over 10 boards. Also the the error states chip 50, 54, 10, 14 as being bad chips but I get this same exact error on many boards. Cant all have the same exact chips with the same exact error. What could this be? My boards are in 100% perfect condition and all the sudden stopped working one day. Showed temp sensor errors and then stopped working completely. Running this test fixture is showing temo sensor is bad but that cant be either. Something is wrong and I dont know how to find the problem. Please advise. Thank you.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: wndsnb on October 16, 2021, 01:40:43 PM
...
I wouldn't really recommend trying to fix yourself. Removing/replacing heatsinks and chips on these hashboards is not easy, and without lots of practice, you'd probably just create more issues. You can search back through this thread to find some potential remedies that may get the board up at least temporarily. Changing the temperature and/or orientation of the miner can sometimes close broken solder joints or open shorts caused by excess solder on the board. In my experience, these are the most likely causes. Best option is to find an experienced repair shop.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: mikeywith on October 16, 2021, 09:55:43 PM
Welcome back man, you went missing for quite a while, by the way, if you are interested, I could add your name here > https://bitcointalk.org/index.php?topic=5297994.0, you are the most experienced member in fixing these hash boards, trusted and can probably do better than most of those overpriced services listed, check it out and let me know.
I have an issue with my T17, one just 1 hashboard. Sometimes i get 0 asic found sometimes it finds all 30. But in any case, I get the error for all temp sensors on the board. I think I've went through most of the posts here and it most likely resembles the issue I quoted below. As I could see, most likely its loose heatsink, but after my (inexperienced) inspection, none seems loose when tested with mild pressure.
It's more like a bad chip connection than just a loose heatsink, in fact, if the heatsink isn't shorting anything, the miner will still run for a very short while before showing "Over-Temp", but getting the temp sensors errors is probably because of a dead/burnt chip or a bad connection between one of the chip and PCB. This problem could also be caused by a bad PSU, do you have another PSU to test with?
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: wndsnb on October 17, 2021, 12:18:12 AM
Thanks, but I have no interest in repairing miners as a service. If I charged enough to make it worth my time I'd be even more expensive than the overpriced services already listed...
Still have >100 dead hashboards of my own to repair anyway which will probably take me more than a year to get through.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: HagssFIN on October 17, 2021, 10:20:27 AM
Whoah, so running a big farm like that easily becomes your full time job if you can also do repairing yourself
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: wndsnb on October 17, 2021, 12:47:22 PM
I'd imagine so. I don't run a big farm but nearly all this dead gear I have I bought from a large farm that shut down last year. They had full-time technicians to repair miners but when they shut down they had piles of dead gear that the technicians either didn't get to or couldn't repair.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: robertpaulsen on October 17, 2021, 04:56:48 PM
Best option is to find an experienced repair shop.
Thanks, I'll probably do that. This problem could also be caused by a bad PSU, do you have another PSU to test with?
No, unfortunately not. I guess it could be the soldier or a burnt chip, although, could there be a log of "find 30 asic" even with a burnt chip? Seems kinda contradictory.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: mikeywith on October 17, 2021, 08:54:21 PM
Whoah, so running a big farm like that easily becomes your full time job if you can also do repairing yourself
I think the type of mining gears running at the farm will determine whether this becomes feasible or not, if the farm is full of 17 series gears, well, then probably a dozen technicians can do that full-time, if it's other robust gears, the amount of work needed could be extremely low. If I charged enough to make it worth my time I'd be even more expensive than the overpriced services already listed...
Makes sense. No, unfortunately not. I guess it could be the soldier or a burnt chip, although, could there be a log of "find 30 asic" even with a burnt chip? Seems kinda contradictory.
If the chips are burnt then they are burnt, the kernel log won't show 30 asics at times and 0 in the others, however, if it's just a bad solder connection then it's pretty normal for the hash board to show 30 asics and then maybe 24 and then 0, I personally managed to fix a few hash boards by freezing them in the freezer, the freezing did something to that solder joint and fixed it, so ya, it's pretty normal for that to happen.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: flashgear on October 19, 2021, 11:19:13 AM
Sooo bringing in $50k worth of T17's 42Th/s is starting to look/sound like a bad idea....
Am I in for a world of pain? - No, I haven't bought them yet.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: wndsnb on October 19, 2021, 03:04:11 PM
It's a gamble. I think the quality control just wasn't good enough for all these 17 series miners to get a reliably good product, but it seems like some batches were fine, others were horrible. I have 10 S17s that came directly from Bitmain in one batch and haven't had a single one go down. Been running for nearly 2 years. Got 7 s17 pros in another batch from Malaysia and had issues with 3 out of 7 in under a year. So could go either way. With used miners, if they've been solidly running with no issues they may be good and the original owners were the ones that took the risk. Or it could be every single miner they are selling had issues and it's just a matter of time before they start failing. I'd just go into it assuming 25% of the hashboards will die. Make sure the #s make sense with that assumption. Consolidate working hashboards into fully working miners and either sell the bad boards for parts or see if you can find a repair shop.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: robertpaulsen on October 19, 2021, 06:21:16 PM
On another note, I plan to underclock my T17 so it uses less power and makes less noise so it will be more acceptable for home mining. When I underlocked it and set power consumption to around 1200W (half of the original), I noticed that the PSU (APW9) is barely getting any heat but the fans are still pretty loud. Is there any way to slow down these small fans? Also, is there any heat sensor in the APW9? I don't wanna mess with it if it will make it unsafe, like fire hazard.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: thierry4wd on October 19, 2021, 09:11:07 PM
Yes, without any problem, just swap original fan by slower fan, i make 8000trs fan, and run good !!! (underclock to, on 35 th)
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: usrzero01 on October 20, 2021, 12:37:54 AM
Hello guys, just had a small rig of gpus since 2018. Have a opportunity to buy a couple of s17 for great price. But doing some research I seen they have a fire hazard, heatsink problems, weak psu, and faulty fans. my buddy said stay away.
If i decided to get them and wanted to overclock them what can I do to reduce risk? Get new power supply, new fan, new heatsink? I have background in computers from the 90s, i put together and taken apart many pc, cpus, heatsinks, fixed or upgraded everything at one time or another over the years.
Also for overclocking i was wondering what firmwares are legit? (ascii.to (the moon))? I like to hear good and bad from actual users to make informed decision.
Thanks guys.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: mikeywith on October 20, 2021, 12:50:05 AM
But doing some research I seen they have a fire hazard, heatsink problems, weak psu, and faulty fans. my buddy said stay away.
If i decided to get them and wanted to overclock them
LOL, so you took all the online advice and your buddy's and just dumped it all in the trash?? why would you do that? I have to sadly inform you that you are likely going to regret doing that, heck, I feel bad for getting those gears LONG before the reviews started coming out, I sure as hell would feel worse if I knew in advance that I was getting some shit-gear. Don't even think about overclocking them, your experience with computers will not serve you once those gears go bad, it isn't a matter of gluing a heatsink, the chips themselves will go bad or become loose, identifying the chip/chips that need fixing require some special tools, acquiring the replacement chip from China is some serious pain on its own, fixing these mining gears isn't something the average joe with some computer background can fix, so chances are you will have to send them for repair, which is costly and takes forever to be done, assuming they will be in a fixable state in the first place. Keep these gears as cool as possible, forget the overclocking thing all together, that's my advice.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: usrzero01 on October 20, 2021, 01:59:28 AM
LOL, so you took all the online advice and your buddy's and just dumped it all in the trash?? why would you do that?
I didn't buy them, yet, his advice made me do more research. He doesn't have any 1st hand experience so that why im posting. I've read some people getting 5 out of 10 machines bad and other saying they been running their machines for couple years and fine.... SO, yeah it is a risk. That is why im asking is there things to do to reduce the risk? PSU, FAN, HEATSINK, turn it on its side, idk just what i read...... As for working on them, there is nothing i cant do in my mind. Been working on computers and taking apart anything and everything and putting back together since the 80's as a kid, coding, building, repairing and replacing chips on pcb, etc.... and i already make enough money not to work, so if the information is out there, have all the time to figure it out... If i had 2 s17 overclocked i would make back my investment in about 2 months, i have free power. So, that is very alluring, but 30% failure rate is very off putting. still undecided....
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: mikeywith on October 20, 2021, 08:31:15 AM
there is nothing i cant do in my mind. Been working on computers and taking apart anything and everything and putting back together since the 80's as a kid, coding, building, repairing and replacing chips on pcb, etc.... and i already make enough money not to work, so if the information is out there, have all the time to figure it out...
If you know that you have what it takes and have all the time in the world, you could provide repair service and charge a premium, you will probably make a lot more money than actually mining, even if that doesn't make sense, it really makes no sense to buy a mining gear with such a high failure rate just because you can fix them, even if you think your time is free, wouldn't you rather watch some movies than having to fix a poorly built ASIC miner? besides, the time you are going to spend fixing them is time wasted not only for you but for the miner itself which would otherwise be generating revenue. If i had 2 s17 overclocked i would make back my investment in about 2 months. Assuming they will survive the overclocking for 2 months, which isn't something anyone would guarantee. I can't think of any reason as to why would anyone (regardless of the circumstances in the world)buy any of those 17 series gears, if someone gives it to me for free, hell ya I'll take it, but will I pay half the price that gets me a Whatsminer or Avalon gear instead? hell, no.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: wndsnb on October 20, 2021, 10:52:13 AM
I agree with mikeywith about the overclocking. The hashboard layout, case, and fans were not built to handle the 3000W required to run these at 70TH or more. The temperature of only 4 out of the 48 ASICs on each hashboard is monitored. So you can very easily get into a situation where one of the non-monitored ASICs that is less efficient or has a poorly attached heatsink, gets hot enough to melt its solder connections, short out a bunch of high power connections, and cause unrepairable damage.
If you're going to ROI in 2 months with overclocking, you'd only need to wait another couple of weeks to ROI without taking the overclocking risk.
Also, not every S17 will overclock that much anyway.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: flashgear on October 24, 2021, 04:29:39 AM
Are the S17 Pro's just as bad as the other 17 range?
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: wndsnb on October 24, 2021, 01:51:39 PM
Are the S17 Pro's just as bad as the other 17 range?
The S17 and S17 Pro are identical, no hardware differences at all. They just select the hashboards that have the best efficiency for the Pro version, and the rest go to the non-pro. The T17 used the identical chip, but put fewer of them in the same area (30 vs 48) with larger heatsinks so they could be run at higher frequencies at the expense of lower efficiency. Many T17s will run the same efficiency as an S17 when you drop the frequency and voltage. So with a bit of luck, your T17 might do 30TH or so at <40W/TH. The S17+ was a redesign of the hashboard that used the newer version of the same chip, 1397AG vs the 1397AD for the S17/T17, and packed a bunch more chips on each hashboard. 65 chips for the S17+ hashboard vs 48 chips for the S17. I couldn't find any information on what the differences might be between AD and AG, but they seem to be interchangeable. I've replaced AD chips on S17s with AG chips and it worked fine. What I did see on the S17+ way more than the S17 was delamination of the copper plating on the top of the chip. The copper plating is what the heatsinks are soldered to, and when it delaminates the heatsink can come off with the copper with little force. If you ship a S17+ that has chips with copper delamination, it will likely show up at its destination with a bunch of heatsinks detached from their chips and jingling around loose. Which is how every one of the S17+s I've looked at arrived. Not sure if the delamination issue was more from the new chip version, or just from the higher possibility of excess heat caused by packing more chips into the same area. Could also be that the temperature got too high for too long during board assembly. The T17+ was the same idea as the T17. I haven't looked at one in person but I'd guess they have the same delamination issues as the S17+. The S17e was a completely different beast, different chip (1396), and an insane number of them on a single board, 135 chips per board. I took a look at a dead one for my host once and after seeing it in person I just sent it back to him. Looked like a complete nightmare to work on. But that was the only one I saw, and I didn't even take a chip off, so I don't really have any thoughts on them other than I don't want to mess with them.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: niko83 on October 24, 2021, 07:45:03 PM
You can use something like https://www.amazon.com/Arctic-Silver-Premium-Adhesive-ASTA-7G/dp/B0087X7262, or use the black glue (https://www.zeusbtc.com/RepairDetails.asp?ID=86) from the same website you got the tool, adding more solder to the existing isn't a good idea, you should clean the chip's surface and then start fresh, ensure that the amount of solder paste is equally even across the whole chip.
Watch this video https://youtu.be/5WH7g61d90w, it's helpful.
Do you know if that glue gets soft when attacked with a heat gun, like the black glue Bitmain uses does?
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: BitMaxz on October 24, 2021, 10:26:50 PM
Do you know if that glue gets soft when attacked with a heat gun, like the black glue Bitmain uses does?
It depends on the temp you set in your heat gun according to the temp range of this glue adhesive it can handle - 40C to >150C. So more than that it can soften the glue if you set it to higher than temp 150c.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: minefarmbuy on November 15, 2021, 10:20:52 PM
Any reports on the thermal adhesive working? Have a unit with about 8 heatsinks fell off and wondering if results are good with the artic silver as my soldering skills are pretty rudimentary and don't want to risk more "transit damage" for more skilled soldering repair.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: wndsnb on November 16, 2021, 11:41:42 AM
I've seen several posts about people asking about using thermal adhesives on these but never saw a post from anyone that had done it and had success or not. The solder used is about 10X better at transferring heat compared to arctic silver, so there will be a larger temperature drop between the heatsink and chip when using the adhesive, which means the chip will run hotter.
Since the miner only monitors the temperature of 4 chips, having some chips with better cooling than others could cause problems especially if one of the 4 monitored chips isn't one that has the thermal adhesive.
About soldering the heastinks back on, many times it is not possible to re-attach. Most of the time I've seen heasinks fall off it is because the copper plating on the top of the chip has delaminated. The copper is what the solder adheres to, and without it, you can't make a good connection. So I've found most of the time the chip needs to be replaced. If you post some pictures of the chips with missing heatsinks, I may be able to determine if it is possible to re-solder them.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: DwarfNo3 on January 13, 2022, 12:12:37 PM
Hello all!
First thing, thank you all for all your posts. I've gone through hundreds and read full threads and it helped me a lot with those darned machines. I have a few T17 that I bought used from China because they had the best ROI, and it turns out there was a reason for that :D
Anyway, I have solved most issues but couldn't find one for this issue. Basically when I connect all 3 boards, one would be 0 volts, the other 17 and the last one 22. if I disconnect one the other two would work fine. I have tried the following:
- Made sure the outlet is grounded and working fine (227 v)
- Tried different:
- Hashboards
- Control board
- Cables (signal, and the small voltage one and the 6 pin power one)
and I keep getting the same issue. The only things that I have not tried replacing are the fans and the case, but I can't imagine them being the issue. Anyone has any idea what could it?
Btw, I noticed that if I don't attach the metal brackets even when it's just two boards, the voltage gets messed up but with them it's fine. Could this be related?
Regards,
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: wndsnb on January 15, 2022, 02:34:36 AM
Post a kernel log and we might be able to give some good advice. From the info you've given, I'd guess it is the PSU. It is the only thing that you haven't swapped, and when the voltages are measured by the hashboards they are measured one at a time and there is some time delay between them. So It could be that the 1st one to measure is getting 22V, the second is getting 17, and by the time the 3rd measures the PSU shut down and is now giving you 0V. Btw, I noticed that if I don't attach the metal brackets even when it's just two boards, the voltage gets messed up but with them it's fine. Could this be related?
No sure what you mean by metal brackets ... If you mean the busbars that connect the main power to the hashboards .... then yeah, not gonna work too well without those attached.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: DwarfNo3 on January 16, 2022, 07:57:31 AM
Thank you wndsnb for your reply, sorry I forgot to mention that I did swap the PSU and nothing changed. what I meant with the metal brackets are the ones that connect the psu with the hashboard I thought they only help keep them in place, but it seems there is something that affects the electric. Here is the kernel log with 3 hashboards connected:
Booting Linux on physical CPU 0x0
Linux version 4.6.0-xilinx-gff8137b-dirty (lzq@armdev2) (gcc version 4.8.3 20140320 (prerelease) (Sourcery CodeBench Lite 2014.05-23) ) #25 SMP PREEMPT Fri Nov 23 15:30:52 CST 2018
CPU: ARMv7 Processor [413fc090] revision 0 (ARMv7), cr=18c5387d
CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
Machine model: Xilinx Zynq
cma: Reserved 16 MiB at 0x0e000000
Memory policy: Data cache writealloc
On node 0 totalpages: 61440
free_area_init_node: node 0, pgdat c0b39280, node_mem_map cde10000
Normal zone: 480 pages used for memmap
Normal zone: 0 pages reserved
Normal zone: 61440 pages, LIFO batch:15
percpu: Embedded 12 pages/cpu @cddf1000 s19776 r8192 d21184 u49152
pcpu-alloc: s19776 r8192 d21184 u49152 alloc=12*4096
pcpu-alloc: [0] 0 [0] 1
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 60960
Kernel command line: mem=240M console=ttyPS0,115200 ramdisk_size=33554432 root=/dev/ram rw earlyprintk
PID hash table entries: 1024 (order: 0, 4096 bytes)
Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
Memory: 203752K/245760K available (6345K kernel code, 231K rwdata, 1896K rodata, 1024K init, 223K bss, 25624K reserved, 16384K cma-reserved, 0K highmem)
Virtual kernel memory layout:
vector : 0xffff0000 - 0xffff1000 ( 4 kB)
fixmap : 0xffc00000 - 0xfff00000 (3072 kB)
vmalloc : 0xcf800000 - 0xff800000 ( 768 MB)
lowmem : 0xc0000000 - 0xcf000000 ( 240 MB)
pkmap : 0xbfe00000 - 0xc0000000 ( 2 MB)
modules : 0xbf000000 - 0xbfe00000 ( 14 MB)
.text : 0xc0008000 - 0xc090c424 (9234 kB)
.init : 0xc0a00000 - 0xc0b00000 (1024 kB)
.data : 0xc0b00000 - 0xc0b39fe0 ( 232 kB)
.bss : 0xc0b39fe0 - 0xc0b71c28 ( 224 kB)
Preemptible hierarchical RCU implementation.
Build-time adjustment of leaf fanout to 32.
RCU restricting CPUs from NR_CPUS=4 to nr_cpu_ids=2.
RCU: Adjusting geometry for rcu_fanout_leaf=32, nr_cpu_ids=2
NR_IRQS:16 nr_irqs:16 16
efuse mapped to cf800000
ps7-slcr mapped to cf802000
L2C: platform modifies aux control register: 0x72360000 -> 0x72760000
L2C: DT/platform modifies aux control register: 0x72360000 -> 0x72760000
L2C-310 erratum 769419 enabled
L2C-310 enabling early BRESP for Cortex-A9
L2C-310 full line of zeros enabled for Cortex-A9
L2C-310 ID prefetch enabled, offset 1 lines
L2C-310 dynamic clock gating enabled, standby mode enabled
L2C-310 cache controller enabled, 8 ways, 512 kB
L2C-310: CACHE_ID 0x410000c8, AUX_CTRL 0x76760001
zynq_clock_init: clkc starts at cf802100
Zynq clock init
sched_clock: 64 bits at 333MHz, resolution 3ns, wraps every 4398046511103ns
clocksource: arm_global_timer: mask: 0xffffffffffffffff max_cycles: 0x4ce07af025, max_idle_ns: 440795209040 ns
Switching to timer-based delay loop, resolution 3ns
clocksource: ttc_clocksource: mask: 0xffff max_cycles: 0xffff, max_idle_ns: 537538477 ns
ps7-ttc #0 at cf80a000, irq=18
Console: colour dummy device 80x30
Calibrating delay loop (skipped), value calculated using timer frequency.. 666.66 BogoMIPS (lpj=3333333)
pid_max: default: 32768 minimum: 301
Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
CPU: Testing write buffer coherency: ok
CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
Setting up static identity map for 0x100000 - 0x100058
CPU1: failed to boot: -1
Brought up 1 CPUs
SMP: Total of 1 processors activated (666.66 BogoMIPS).
CPU: All CPU(s) started in SVC mode.
devtmpfs: initialized
VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4
clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
pinctrl core: initialized pinctrl subsystem
NET: Registered protocol family 16
DMA: preallocated 256 KiB pool for atomic coherent allocations
cpuidle: using governor menu
hw-breakpoint: found 5 (+1 reserved) breakpoint and 1 watchpoint registers.
hw-breakpoint: maximum watchpoint size is 4 bytes.
zynq-ocm f800c000.ps7-ocmc: ZYNQ OCM pool: 256 KiB @ 0xcf880000
vgaarb: loaded
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
media: Linux media interface: v0.10
Linux video capture interface: v2.00
pps_core: LinuxPPS API ver. 1 registered
pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
PTP clock support registered
EDAC MC: Ver: 3.0.0
Advanced Linux Sound Architecture Driver Initialized.
clocksource: Switched to clocksource arm_global_timer
NET: Registered protocol family 2
TCP established hash table entries: 2048 (order: 1, 8192 bytes)
TCP bind hash table entries: 2048 (order: 2, 16384 bytes)
TCP: Hash tables configured (established 2048 bind 2048)
UDP hash table entries: 256 (order: 1, 8192 bytes)
UDP-Lite hash table entries: 256 (order: 1, 8192 bytes)
NET: Registered protocol family 1
RPC: Registered named UNIX socket transport module.
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
PCI: CLS 0 bytes, default 64
Trying to unpack rootfs image as initramfs...
rootfs image is not initramfs (no cpio magic); looks like an initrd
Freeing initrd memory: 12584K (cceb7000 - 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
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: 6/2, WL threshold: 4096, image sequence number: 638989880
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 6593BA4D-00F7-467B-9E0A-A2198CBE84FF, 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: 11/7, WL threshold: 4096, image sequence number: 100324054
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 058C0E40-6EAA-4676-9C52-F694F6D34F3B, 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 = 0xfb013
In fpga mem driver!
request_mem_region OK!
fpga mem virtual address is 0xd2000000
random: nonblocking pool is initialized
Jan 16 07:52:23 (none) user.notice kernel: random: nonblocking pool is initialized
2022-01-16 07:47:52 driver-btm-api.c:663:init_freq_mode: This is scan-user version
2022-01-16 07:47:52 driver-btm-api.c:2028:bitmain_soc_init: opt_multi_version = 1
2022-01-16 07:47:52 driver-btm-api.c:2029:bitmain_soc_init: opt_bitmain_ab = 1
2022-01-16 07:47:52 driver-btm-api.c:2030:bitmain_soc_init: opt_bitmain_work_mode = 0
2022-01-16 07:47:52 driver-btm-api.c:2031:bitmain_soc_init: Miner compile time: Thu Apr 23 16:29:07 CST 2020 type: Antminer T17
2022-01-16 07:47:52 driver-btm-api.c:2032:bitmain_soc_init: commit version: 1c5be6f 2020-04-20 16:18:14, build by: lol 2020-04-23 16:35:04
2022-01-16 07:47:52 driver-btm-api.c:1844:show_sn: no SN got, please write SN to /nvdata/sn
2022-01-16 07:47:52 driver-btm-api.c:1167:miner_device_init: Detect 256MB control board of XILINX
2022-01-16 07:47:52 driver-btm-api.c:1115:init_fan_parameter: fan_eft : 0 fan_pwm : 0
2022-01-16 07:47:52 thread.c:885:create_read_nonce_reg_thread: create thread
2022-01-16 07:47:58 driver-btm-api.c:1099:init_miner_version: miner ID : 8072d5025c20885c
2022-01-16 07:47:58 driver-btm-api.c:1105:init_miner_version: FPGA Version = 0xB013
2022-01-16 07:48:00 eeprom.c:431:check_pattern_test_level: L1 board
2022-01-16 07:48:01 eeprom.c:431:check_pattern_test_level: L1 board
2022-01-16 07:48:03 eeprom.c:431:check_pattern_test_level: L1 board
2022-01-16 07:48:03 driver-btm-api.c:737:get_product_id: product_id[0] = 1
2022-01-16 07:48:03 driver-btm-api.c:737:get_product_id: product_id[1] = 1
2022-01-16 07:48:03 driver-btm-api.c:737:get_product_id: product_id[2] = 1
2022-01-16 07:48:03 driver-btm-api.c:1666:get_ccdly_opt: ccdly_opt[0] = 1
2022-01-16 07:48:03 driver-btm-api.c:1666:get_ccdly_opt: ccdly_opt[1] = 1
2022-01-16 07:48:03 driver-btm-api.c:1666:get_ccdly_opt: ccdly_opt[2] = 1
2022-01-16 07:48:03 driver-btm-api.c:1919:bitmain_board_init: g_ccdly_opt = 1
2022-01-16 07:48:03 driver-btm-api.c:676:_set_project_type: project:2
2022-01-16 07:48:03 driver-btm-api.c:706:_set_project_type: Project type: Antminer T17
2022-01-16 07:48:03 driver-btm-api.c:717:dump_pcb_bom_version: Chain [0] PCB Version: 0x0100
2022-01-16 07:48:03 driver-btm-api.c:718:dump_pcb_bom_version: Chain [0] BOM Version: 0x0100
2022-01-16 07:48:03 driver-btm-api.c:717:dump_pcb_bom_version: Chain [1] PCB Version: 0x0100
2022-01-16 07:48:03 driver-btm-api.c:718:dump_pcb_bom_version: Chain [1] BOM Version: 0x0100
2022-01-16 07:48:03 driver-btm-api.c:717:dump_pcb_bom_version: Chain [2] PCB Version: 0x0100
2022-01-16 07:48:03 driver-btm-api.c:718:dump_pcb_bom_version: Chain [2] BOM Version: 0x0100
2022-01-16 07:48:06 driver-btm-api.c:1939:bitmain_board_init: Fan check passed.
2022-01-16 07:48:08 board.c:36:jump_and_app_check_restore_pic: chain[0] PIC jump to app
2022-01-16 07:48:11 board.c:40:jump_and_app_check_restore_pic: Check chain[0] PIC fw version=0xb9
2022-01-16 07:48:13 board.c:36:jump_and_app_check_restore_pic: chain[1] PIC jump to app
2022-01-16 07:48:17 board.c:40:jump_and_app_check_restore_pic: Check chain[1] PIC fw version=0xb9
2022-01-16 07:48:18 board.c:36:jump_and_app_check_restore_pic: chain[2] PIC jump to app
2022-01-16 07:48:22 board.c:40:jump_and_app_check_restore_pic: Check chain[2] PIC fw version=0xb9
2022-01-16 07:48:22 thread.c:880:create_pic_heart_beat_thread: create thread
2022-01-16 07:48:22 power_api.c:55:power_init: power init ...
2022-01-16 07:48:22 driver-btm-api.c:1949:bitmain_board_init: Enter 30s sleep to make sure power release finish.
2022-01-16 07:48:22 power_api.c:46:power_off: init gpio907
2022-01-16 07:48:54 power_api.c:232:set_iic_power_to_highest_voltage: setting to voltage: 17.00 ...
2022-01-16 07:49:00 power_api.c:124:check_voltage_multi: retry time: 0
2022-01-16 07:49:01 power_api.c:86:get_average_voltage: chain[0], voltage is: 0.061230
2022-01-16 07:49:03 power_api.c:86:get_average_voltage: chain[1], voltage is: 22.398105
2022-01-16 07:49:05 power_api.c:86:get_average_voltage: chain[2], voltage is: 16.966963
2022-01-16 07:49:05 power_api.c:97:get_average_voltage: aveage voltage is: 13.142099
2022-01-16 07:49:05 power_api.c:110:check_voltage: target_vol = 17.00, actural_vol = 13.14, more than 1.0v diff.
2022-01-16 07:49:06 power_api.c:124:check_voltage_multi: retry time: 1
2022-01-16 07:49:08 power_api.c:86:get_average_voltage: chain[0], voltage is: 17.064931
2022-01-16 07:49:09 power_api.c:86:get_average_voltage: chain[1], voltage is: 22.391982
2022-01-16 07:49:13 power_api.c:86:get_average_voltage: chain[2], voltage is: 16.991455
2022-01-16 07:49:13 power_api.c:97:get_average_voltage: aveage voltage is: 18.816123
2022-01-16 07:49:13 power_api.c:110:check_voltage: target_vol = 17.00, actural_vol = 18.82, more than 1.0v diff.
2022-01-16 07:49:14 power_api.c:124:check_voltage_multi: retry time: 2
2022-01-16 07:49:16 power_api.c:86:get_average_voltage: chain[0], voltage is: 17.064931
2022-01-16 07:49:19 power_api.c:86:get_average_voltage: chain[1], voltage is: 22.391982
2022-01-16 07:49:21 power_api.c:86:get_average_voltage: chain[2], voltage is: 16.966963
2022-01-16 07:49:21 power_api.c:97:get_average_voltage: aveage voltage is: 18.807959
2022-01-16 07:49:21 power_api.c:110:check_voltage: target_vol = 17.00, actural_vol = 18.81, more than 1.0v diff.
2022-01-16 07:49:22 power_api.c:124:check_voltage_multi: retry time: 3
2022-01-16 07:49:23 power_api.c:86:get_average_voltage: chain[0], voltage is: 17.083301
2022-01-16 07:49:25 power_api.c:86:get_average_voltage: chain[1], voltage is: 22.379736
2022-01-16 07:49:27 power_api.c:86:get_average_voltage: chain[2], voltage is: 16.973086
2022-01-16 07:49:27 power_api.c:97:get_average_voltage: aveage voltage is: 18.812041
2022-01-16 07:49:27 power_api.c:110:check_voltage: target_vol = 17.00, actural_vol = 18.81, more than 1.0v diff.
2022-01-16 07:49:28 power_api.c:124:check_voltage_multi: retry time: 4
2022-01-16 07:49:31 power_api.c:86:get_average_voltage: chain[0], voltage is: 17.083301
2022-01-16 07:49:34 power_api.c:86:get_average_voltage: chain[1], voltage is: 22.379736
2022-01-16 07:49:37 power_api.c:86:get_average_voltage: chain[2], voltage is: 16.966963
2022-01-16 07:49:37 power_api.c:97:get_average_voltage: aveage voltage is: 18.810000
2022-01-16 07:49:37 power_api.c:110:check_voltage: target_vol = 17.00, actural_vol = 18.81, more than 1.0v diff.
2022-01-16 07:49:38 power_api.c:124:check_voltage_multi: retry time: 5
2022-01-16 07:49:40 power_api.c:86:get_average_voltage: chain[0], voltage is: 17.071054
2022-01-16 07:49:41 power_api.c:86:get_average_voltage: chain[1], voltage is: 22.385859
2022-01-16 07:49:43 power_api.c:86:get_average_voltage: chain[2], voltage is: 16.991455
2022-01-16 07:49:43 power_api.c:97:get_average_voltage: aveage voltage is: 18.816123
2022-01-16 07:49:43 power_api.c:110:check_voltage: target_vol = 17.00, actural_vol = 18.82, more than 1.0v diff.
2022-01-16 07:49:44 power_api.c:124:check_voltage_multi: retry time: 6
2022-01-16 07:49:46 power_api.c:86:get_average_voltage: chain[0], voltage is: 17.071054
2022-01-16 07:49:49 power_api.c:86:get_average_voltage: chain[1], voltage is: 22.367490
2022-01-16 07:49:52 power_api.c:86:get_average_voltage: chain[2], voltage is: 16.979209
2022-01-16 07:49:52 power_api.c:97:get_average_voltage: aveage voltage is: 18.805918
2022-01-16 07:49:52 power_api.c:110:check_voltage: target_vol = 17.00, actural_vol = 18.81, more than 1.0v diff.
2022-01-16 07:49:53 power_api.c:124:check_voltage_multi: retry time: 7
2022-01-16 07:49:55 power_api.c:86:get_average_voltage: chain[0], voltage is: 17.064931
2022-01-16 07:49:57 power_api.c:86:get_average_voltage: chain[1], voltage is: 22.379736
2022-01-16 07:49:59 power_api.c:86:get_average_voltage: chain[2], voltage is: 16.979209
2022-01-16 07:49:59 power_api.c:97:get_average_voltage: aveage voltage is: 18.807959
2022-01-16 07:49:59 power_api.c:110:check_voltage: target_vol = 17.00, actural_vol = 18.81, more than 1.0v diff.
2022-01-16 07:50:00 power_api.c:124:check_voltage_multi: retry time: 8
2022-01-16 07:50:02 power_api.c:86:get_average_voltage: chain[0], voltage is: 17.083301
2022-01-16 07:50:04 power_api.c:86:get_average_voltage: chain[1], voltage is: 22.373613
2022-01-16 07:50:05 power_api.c:86:get_average_voltage: chain[2], voltage is: 16.997578
2022-01-16 07:50:05 power_api.c:97:get_average_voltage: aveage voltage is: 18.818164
2022-01-16 07:50:05 power_api.c:110:check_voltage: target_vol = 17.00, actural_vol = 18.82, more than 1.0v diff.
2022-01-16 07:50:06 power_api.c:124:check_voltage_multi: retry time: 9
2022-01-16 07:50:08 power_api.c:86:get_average_voltage: chain[0], voltage is: 17.071054
2022-01-16 07:50:12 power_api.c:86:get_average_voltage: chain[1], voltage is: 22.379736
2022-01-16 07:50:15 power_api.c:86:get_average_voltage: chain[2], voltage is: 16.991455
2022-01-16 07:50:15 power_api.c:97:get_average_voltage: aveage voltage is: 18.814082
2022-01-16 07:50:15 power_api.c:110:check_voltage: target_vol = 17.00, actural_vol = 18.81, more than 1.0v diff.
2022-01-16 07:50:16 power_api.c:124:check_voltage_multi: retry time: 10
2022-01-16 07:50:18 power_api.c:86:get_average_voltage: chain[0], voltage is: 17.071054
2022-01-16 07:50:19 power_api.c:86:get_average_voltage: chain[1], voltage is: 22.379736
2022-01-16 07:50:21 power_api.c:86:get_average_voltage: chain[2], voltage is: 16.979209
2022-01-16 07:50:21 power_api.c:97:get_average_voltage: aveage voltage is: 18.810000
2022-01-16 07:50:21 power_api.c:110:check_voltage: target_vol = 17.00, actural_vol = 18.81, more than 1.0v diff.
2022-01-16 07:50:22 power_api.c:124:check_voltage_multi: retry time: 11
2022-01-16 07:50:24 power_api.c:86:get_average_voltage: chain[0], voltage is: 17.071054
2022-01-16 07:50:27 power_api.c:86:get_average_voltage: chain[1], voltage is: 22.373613
2022-01-16 07:50:30 power_api.c:86:get_average_voltage: chain[2], voltage is: 16.985332
2022-01-16 07:50:30 power_api.c:97:get_average_voltage: aveage voltage is: 18.810000
2022-01-16 07:50:30 power_api.c:110:check_voltage: target_vol = 17.00, actural_vol = 18.81, more than 1.0v diff.
2022-01-16 07:50:31 power_api.c:124:check_voltage_multi: retry time: 12
2022-01-16 07:50:33 power_api.c:86:get_average_voltage: chain[0], voltage is: 17.077178
2022-01-16 07:50:35 power_api.c:86:get_average_voltage: chain[1], voltage is: 22.398105
2022-01-16 07:50:37 power_api.c:86:get_average_voltage: chain[2], voltage is: 16.979209
2022-01-16 07:50:37 power_api.c:97:get_average_voltage: aveage voltage is: 18.818164
2022-01-16 07:50:37 power_api.c:110:check_voltage: target_vol = 17.00, actural_vol = 18.82, more than 1.0v diff.
2022-01-16 07:50:38 power_api.c:124:check_voltage_multi: retry time: 13
2022-01-16 07:50:40 power_api.c:86:get_average_voltage: chain[0], voltage is: 17.101670
2022-01-16 07:50:41 power_api.c:86:get_average_voltage: chain[1], voltage is: 22.398105
2022-01-16 07:50:43 power_api.c:86:get_average_voltage: chain[2], voltage is: 16.979209
2022-01-16 07:50:43 power_api.c:97:get_average_voltage: aveage voltage is: 18.826328
2022-01-16 07:50:43 power_api.c:110:check_voltage: target_vol = 17.00, actural_vol = 18.83, more than 1.0v diff.
2022-01-16 07:50:44 power_api.c:124:check_voltage_multi: retry time: 14
2022-01-16 07:50:46 power_api.c:86:get_average_voltage: chain[0], voltage is: 17.089424
2022-01-16 07:50:49 power_api.c:86:get_average_voltage: chain[1], voltage is: 22.391982
2022-01-16 07:50:53 power_api.c:86:get_average_voltage: chain[2], voltage is: 16.979209
2022-01-16 07:50:53 power_api.c:97:get_average_voltage: aveage voltage is: 18.820205
2022-01-16 07:50:53 power_api.c:110:check_voltage: target_vol = 17.00, actural_vol = 18.82, more than 1.0v diff.
2022-01-16 07:50:54 power_api.c:124:check_voltage_multi: retry time: 15
2022-01-16 07:50:55 power_api.c:86:get_average_voltage: chain[0], voltage is: 17.089424
2022-01-16 07:50:57 power_api.c:86:get_average_voltage: chain[1], voltage is: 22.391982
2022-01-16 07:50:59 power_api.c:86:get_average_voltage: chain[2], voltage is: 16.997578
2022-01-16 07:50:59 power_api.c:97:get_average_voltage: aveage voltage is: 18.826328
2022-01-16 07:50:59 power_api.c:110:check_voltage: target_vol = 17.00, actural_vol = 18.83, more than 1.0v diff.
2022-01-16 07:51:00 power_api.c:124:check_voltage_multi: retry time: 16
2022-01-16 07:51:02 power_api.c:86:get_average_voltage: chain[0], voltage is: 17.052685
2022-01-16 07:51:05 power_api.c:86:get_average_voltage: chain[1], voltage is: 22.398105
2022-01-16 07:51:08 power_api.c:86:get_average_voltage: chain[2], voltage is: 16.966963
2022-01-16 07:51:08 power_api.c:97:get_average_voltage: aveage voltage is: 18.805918
2022-01-16 07:51:08 power_api.c:110:check_voltage: target_vol = 17.00, actural_vol = 18.81, more than 1.0v diff.
2022-01-16 07:51:09 power_api.c:124:check_voltage_multi: retry time: 17
2022-01-16 07:51:11 power_api.c:86:get_average_voltage: chain[0], voltage is: 17.071054
2022-01-16 07:51:13 power_api.c:86:get_average_voltage: chain[1], voltage is: 22.379736
2022-01-16 07:51:15 power_api.c:86:get_average_voltage: chain[2], voltage is: 16.973086
2022-01-16 07:51:15 power_api.c:97:get_average_voltage: aveage voltage is: 18.807959
2022-01-16 07:51:15 power_api.c:110:check_voltage: target_vol = 17.00, actural_vol = 18.81, more than 1.0v diff.
2022-01-16 07:51:16 power_api.c:124:check_voltage_multi: retry time: 18
2022-01-16 07:51:17 power_api.c:86:get_average_voltage: chain[0], voltage is: 17.083301
2022-01-16 07:51:19 power_api.c:86:get_average_voltage: chain[1], voltage is: 22.391982
2022-01-16 07:51:21 power_api.c:86:get_average_voltage: chain[2], voltage is: 16.973086
2022-01-16 07:51:21 power_api.c:97:get_average_voltage: aveage voltage is: 18.816123
2022-01-16 07:51:21 power_api.c:110:check_voltage: target_vol = 17.00, actural_vol = 18.82, more than 1.0v diff.
2022-01-16 07:51:22 power_api.c:124:check_voltage_multi: retry time: 19
2022-01-16 07:51:24 power_api.c:86:get_average_voltage: chain[0], voltage is: 17.077178
2022-01-16 07:51:27 power_api.c:86:get_average_voltage: chain[1], voltage is: 22.385859
2022-01-16 07:51:30 power_api.c:86:get_average_voltage: chain[2], voltage is: 16.966963
2022-01-16 07:51:30 power_api.c:97:get_average_voltage: aveage voltage is: 18.810000
2022-01-16 07:51:30 power_api.c:110:check_voltage: target_vol = 17.00, actural_vol = 18.81, more than 1.0v diff.
2022-01-16 07:51:31 power_api.c:124:check_voltage_multi: retry time: 20
2022-01-16 07:51:33 power_api.c:86:get_average_voltage: chain[0], voltage is: 17.064931
2022-01-16 07:51:35 power_api.c:86:get_average_voltage: chain[1], voltage is: 22.373613
2022-01-16 07:51:37 power_api.c:86:get_average_voltage: chain[2], voltage is: 16.991455
2022-01-16 07:51:37 power_api.c:97:get_average_voltage: aveage voltage is: 18.810000
2022-01-16 07:51:37 power_api.c:110:check_voltage: target_vol = 17.00, actural_vol = 18.81, more than 1.0v diff.
2022-01-16 07:51:38 power_api.c:124:check_voltage_multi: retry time: 21
2022-01-16 07:51:39 power_api.c:86:get_average_voltage: chain[0], voltage is: 17.064931
2022-01-16 07:51:43 power_api.c:86:get_average_voltage: chain[1], voltage is: 22.373613
2022-01-16 07:51:46 power_api.c:86:get_average_voltage: chain[2], voltage is: 16.985332
2022-01-16 07:51:46 power_api.c:97:get_average_voltage: aveage voltage is: 18.807959
2022-01-16 07:51:46 power_api.c:110:check_voltage: target_vol = 17.00, actural_vol = 18.81, more than 1.0v diff.
2022-01-16 07:51:47 power_api.c:124:check_voltage_multi: retry time: 22
2022-01-16 07:51:49 power_api.c:86:get_average_voltage: chain[0], voltage is: 17.089424
2022-01-16 07:51:51 power_api.c:86:get_average_voltage: chain[1], voltage is: 22.379736
2022-01-16 07:51:52 power_api.c:86:get_average_voltage: chain[2], voltage is: 16.973086
2022-01-16 07:51:52 power_api.c:97:get_average_voltage: aveage voltage is: 18.814082
2022-01-16 07:51:52 power_api.c:110:check_voltage: target_vol = 17.00, actural_vol = 18.81, more than 1.0v diff.
2022-01-16 07:51:53 power_api.c:124:check_voltage_multi: retry time: 23
2022-01-16 07:51:55 power_api.c:86:get_average_voltage: chain[0], voltage is: 17.077178
2022-01-16 07:51:57 power_api.c:86:get_average_voltage: chain[1], voltage is: 22.379736
2022-01-16 07:51:59 power_api.c:86:get_average_voltage: chain[2], voltage is: 16.966963
2022-01-16 07:51:59 power_api.c:97:get_average_voltage: aveage voltage is: 18.807959
2022-01-16 07:51:59 power_api.c:110:check_voltage: target_vol = 17.00, actural_vol = 18.81, more than 1.0v diff.
2022-01-16 07:52:00 power_api.c:124:check_voltage_multi: retry time: 24
2022-01-16 07:52:02 power_api.c:86:get_average_voltage: chain[0], voltage is: 17.089424
2022-01-16 07:52:05 power_api.c:86:get_average_voltage: chain[1], voltage is: 22.391982
2022-01-16 07:52:08 power_api.c:86:get_average_voltage: chain[2], voltage is: 16.985332
2022-01-16 07:52:08 power_api.c:97:get_average_voltage: aveage voltage is: 18.822246
2022-01-16 07:52:08 power_api.c:110:check_voltage: target_vol = 17.00, actural_vol = 18.82, more than 1.0v diff.
2022-01-16 07:52:09 power_api.c:124:check_voltage_multi: retry time: 25
2022-01-16 07:52:11 power_api.c:86:get_average_voltage: chain[0], voltage is: 17.083301
2022-01-16 07:52:13 power_api.c:86:get_average_voltage: chain[1], voltage is: 22.385859
2022-01-16 07:52:15 power_api.c:86:get_average_voltage: chain[2], voltage is: 16.985332
2022-01-16 07:52:15 power_api.c:97:get_average_voltage: aveage voltage is: 18.818164
2022-01-16 07:52:15 power_api.c:110:check_voltage: target_vol = 17.00, actural_vol = 18.82, more than 1.0v diff.
2022-01-16 07:52:16 power_api.c:124:check_voltage_multi: retry time: 26
2022-01-16 07:52:17 power_api.c:86:get_average_voltage: chain[0], voltage is: 17.064931
2022-01-16 07:52:18 http_test.c:111:get_sys_running_seconds: system uptime 311.012022-01-16 07:52:18 http_test.c:371:upload_log_generate: write result.json done
2022-01-16 07:52:20 power_api.c:86:get_average_voltage: chain[1], voltage is: 22.379736
2022-01-16 07:52:24 power_api.c:86:get_average_voltage: chain[2], voltage is: 16.973086
2022-01-16 07:52:24 power_api.c:97:get_average_voltage: aveage voltage is: 18.805918
2022-01-16 07:52:24 power_api.c:110:check_voltage: target_vol = 17.00, actural_vol = 18.81, more than 1.0v diff.
2022-01-16 07:52:25 power_api.c:124:check_voltage_multi: retry time: 27
2022-01-16 07:52:27 power_api.c:86:get_average_voltage: chain[0], voltage is: 17.064931
2022-01-16 07:52:28 power_api.c:86:get_average_voltage: chain[1], voltage is: 22.391982
2022-01-16 07:52:30 power_api.c:86:get_average_voltage: chain[2], voltage is: 16.960840
2022-01-16 07:52:30 power_api.c:97:get_average_voltage: aveage voltage is: 18.805918
2022-01-16 07:52:30 power_api.c:110:check_voltage: target_vol = 17.00, actural_vol = 18.81, more than 1.0v diff.
2022-01-16 07:52:31 power_api.c:124:check_voltage_multi: retry time: 28
2022-01-16 07:52:33 power_api.c:86:get_average_voltage: chain[0], voltage is: 17.089424
2022-01-16 07:52:35 power_api.c:86:get_average_voltage: chain[1], voltage is: 22.391982
2022-01-16 07:52:37 power_api.c:86:get_average_voltage: chain[2], voltage is: 16.966963
2022-01-16 07:52:37 power_api.c:97:get_average_voltage: aveage voltage is: 18.816123
2022-01-16 07:52:37 power_api.c:110:check_voltage: target_vol = 17.00, actural_vol = 18.82, more than 1.0v diff.
2022-01-16 07:52:38 power_api.c:124:check_voltage_multi: retry time: 29
2022-01-16 07:52:40 power_api.c:86:get_average_voltage: chain[0], voltage is: 17.089424
2022-01-16 07:52:43 power_api.c:86:get_average_voltage: chain[1], voltage is: 22.385859
2022-01-16 07:52:46 power_api.c:86:get_average_voltage: chain[2], voltage is: 16.997578
2022-01-16 07:52:46 power_api.c:97:get_average_voltage: aveage voltage is: 18.824287
2022-01-16 07:52:46 power_api.c:110:check_voltage: target_vol = 17.00, actural_vol = 18.82, more than 1.0v diff.
2022-01-16 07:52:47 power_api.c:182:set_iic_power_by_voltage: now set voltage to : 17.000000
2022-01-16 07:52:47 driver-btm-api.c:205:set_miner_status: ERROR_POWER_LOST
2022-01-16 07:52:47 driver-btm-api.c:146:stop_mining: stop mining: power set failed!
2022-01-16 07:52:47 thread.c:930:cancel_read_nonce_reg_thread: cancel thread
2022-01-16 07:52:47 driver-btm-api.c:131:killall_hashboard: ****power off hashboard****
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: DwarfNo3 on January 16, 2022, 08:08:12 AM
and when I swap the hasboard with 22 volts another hashboard goes to 0 volts. So it's probably both PSUs? (both are used)
Booting Linux on physical CPU 0x0
Linux version 4.6.0-xilinx-gff8137b-dirty (lzq@armdev2) (gcc version 4.8.3 20140320 (prerelease) (Sourcery CodeBench Lite 2014.05-23) ) #25 SMP PREEMPT Fri Nov 23 15:30:52 CST 2018
CPU: ARMv7 Processor [413fc090] revision 0 (ARMv7), cr=18c5387d
CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
Machine model: Xilinx Zynq
cma: Reserved 16 MiB at 0x0e000000
Memory policy: Data cache writealloc
On node 0 totalpages: 61440
free_area_init_node: node 0, pgdat c0b39280, node_mem_map cde10000
Normal zone: 480 pages used for memmap
Normal zone: 0 pages reserved
Normal zone: 61440 pages, LIFO batch:15
percpu: Embedded 12 pages/cpu @cddf1000 s19776 r8192 d21184 u49152
pcpu-alloc: s19776 r8192 d21184 u49152 alloc=12*4096
pcpu-alloc: [0] 0 [0] 1
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 60960
Kernel command line: mem=240M console=ttyPS0,115200 ramdisk_size=33554432 root=/dev/ram rw earlyprintk
PID hash table entries: 1024 (order: 0, 4096 bytes)
Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
Memory: 203752K/245760K available (6345K kernel code, 231K rwdata, 1896K rodata, 1024K init, 223K bss, 25624K reserved, 16384K cma-reserved, 0K highmem)
Virtual kernel memory layout:
vector : 0xffff0000 - 0xffff1000 ( 4 kB)
fixmap : 0xffc00000 - 0xfff00000 (3072 kB)
vmalloc : 0xcf800000 - 0xff800000 ( 768 MB)
lowmem : 0xc0000000 - 0xcf000000 ( 240 MB)
pkmap : 0xbfe00000 - 0xc0000000 ( 2 MB)
modules : 0xbf000000 - 0xbfe00000 ( 14 MB)
.text : 0xc0008000 - 0xc090c424 (9234 kB)
.init : 0xc0a00000 - 0xc0b00000 (1024 kB)
.data : 0xc0b00000 - 0xc0b39fe0 ( 232 kB)
.bss : 0xc0b39fe0 - 0xc0b71c28 ( 224 kB)
Preemptible hierarchical RCU implementation.
Build-time adjustment of leaf fanout to 32.
RCU restricting CPUs from NR_CPUS=4 to nr_cpu_ids=2.
RCU: Adjusting geometry for rcu_fanout_leaf=32, nr_cpu_ids=2
NR_IRQS:16 nr_irqs:16 16
efuse mapped to cf800000
ps7-slcr mapped to cf802000
L2C: platform modifies aux control register: 0x72360000 -> 0x72760000
L2C: DT/platform modifies aux control register: 0x72360000 -> 0x72760000
L2C-310 erratum 769419 enabled
L2C-310 enabling early BRESP for Cortex-A9
L2C-310 full line of zeros enabled for Cortex-A9
L2C-310 ID prefetch enabled, offset 1 lines
L2C-310 dynamic clock gating enabled, standby mode enabled
L2C-310 cache controller enabled, 8 ways, 512 kB
L2C-310: CACHE_ID 0x410000c8, AUX_CTRL 0x76760001
zynq_clock_init: clkc starts at cf802100
Zynq clock init
sched_clock: 64 bits at 333MHz, resolution 3ns, wraps every 4398046511103ns
clocksource: arm_global_timer: mask: 0xffffffffffffffff max_cycles: 0x4ce07af025, max_idle_ns: 440795209040 ns
Switching to timer-based delay loop, resolution 3ns
clocksource: ttc_clocksource: mask: 0xffff max_cycles: 0xffff, max_idle_ns: 537538477 ns
ps7-ttc #0 at cf80a000, irq=18
Console: colour dummy device 80x30
Calibrating delay loop (skipped), value calculated using timer frequency.. 666.66 BogoMIPS (lpj=3333333)
pid_max: default: 32768 minimum: 301
Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
CPU: Testing write buffer coherency: ok
CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
Setting up static identity map for 0x100000 - 0x100058
CPU1: failed to boot: -1
Brought up 1 CPUs
SMP: Total of 1 processors activated (666.66 BogoMIPS).
CPU: All CPU(s) started in SVC mode.
devtmpfs: initialized
VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4
clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
pinctrl core: initialized pinctrl subsystem
NET: Registered protocol family 16
DMA: preallocated 256 KiB pool for atomic coherent allocations
cpuidle: using governor menu
hw-breakpoint: found 5 (+1 reserved) breakpoint and 1 watchpoint registers.
hw-breakpoint: maximum watchpoint size is 4 bytes.
zynq-ocm f800c000.ps7-ocmc: ZYNQ OCM pool: 256 KiB @ 0xcf880000
vgaarb: loaded
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
media: Linux media interface: v0.10
Linux video capture interface: v2.00
pps_core: LinuxPPS API ver. 1 registered
pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
PTP clock support registered
EDAC MC: Ver: 3.0.0
Advanced Linux Sound Architecture Driver Initialized.
clocksource: Switched to clocksource arm_global_timer
NET: Registered protocol family 2
TCP established hash table entries: 2048 (order: 1, 8192 bytes)
TCP bind hash table entries: 2048 (order: 2, 16384 bytes)
TCP: Hash tables configured (established 2048 bind 2048)
UDP hash table entries: 256 (order: 1, 8192 bytes)
UDP-Lite hash table entries: 256 (order: 1, 8192 bytes)
NET: Registered protocol family 1
RPC: Registered named UNIX socket transport module.
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
PCI: CLS 0 bytes, default 64
Trying to unpack rootfs image as initramfs...
rootfs image is not initramfs (no cpio magic); looks like an initrd
Freeing initrd memory: 12584K (cceb7000 - 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
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: 6/2, WL threshold: 4096, image sequence number: 638989880
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 6593BA4D-00F7-467B-9E0A-A2198CBE84FF, 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: 12/7, WL threshold: 4096, image sequence number: 100324054
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 058C0E40-6EAA-4676-9C52-F694F6D34F3B, 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 = 0xfb013
In fpga mem driver!
request_mem_region OK!
fpga mem virtual address is 0xd2000000
2022-01-16 08:03:59 driver-btm-api.c:663:init_freq_mode: This is scan-user version
2022-01-16 08:03:59 driver-btm-api.c:2028:bitmain_soc_init: opt_multi_version = 1
2022-01-16 08:03:59 driver-btm-api.c:2029:bitmain_soc_init: opt_bitmain_ab = 1
2022-01-16 08:03:59 driver-btm-api.c:2030:bitmain_soc_init: opt_bitmain_work_mode = 0
2022-01-16 08:03:59 driver-btm-api.c:2031:bitmain_soc_init: Miner compile time: Thu Apr 23 16:29:07 CST 2020 type: Antminer T17
2022-01-16 08:03:59 driver-btm-api.c:2032:bitmain_soc_init: commit version: 1c5be6f 2020-04-20 16:18:14, build by: lol 2020-04-23 16:35:04
2022-01-16 08:03:59 driver-btm-api.c:1844:show_sn: no SN got, please write SN to /nvdata/sn
2022-01-16 08:03:59 driver-btm-api.c:1167:miner_device_init: Detect 256MB control board of XILINX
2022-01-16 08:03:59 driver-btm-api.c:1115:init_fan_parameter: fan_eft : 0 fan_pwm : 0
2022-01-16 08:03:59 thread.c:885:create_read_nonce_reg_thread: create thread
2022-01-16 08:04:05 driver-btm-api.c:1099:init_miner_version: miner ID : 8072d5025c20885c
2022-01-16 08:04:05 driver-btm-api.c:1105:init_miner_version: FPGA Version = 0xB013
2022-01-16 08:04:07 eeprom.c:431:check_pattern_test_level: L1 board
2022-01-16 08:04:09 eeprom.c:431:check_pattern_test_level: L1 board
2022-01-16 08:04:11 eeprom.c:431:check_pattern_test_level: L1 board
2022-01-16 08:04:11 driver-btm-api.c:737:get_product_id: product_id[0] = 1
2022-01-16 08:04:11 driver-btm-api.c:737:get_product_id: product_id[1] = 1
2022-01-16 08:04:11 driver-btm-api.c:737:get_product_id: product_id[2] = 1
2022-01-16 08:04:11 driver-btm-api.c:1666:get_ccdly_opt: ccdly_opt[0] = 1
2022-01-16 08:04:11 driver-btm-api.c:1666:get_ccdly_opt: ccdly_opt[1] = 1
2022-01-16 08:04:11 driver-btm-api.c:1666:get_ccdly_opt: ccdly_opt[2] = 1
2022-01-16 08:04:11 driver-btm-api.c:1919:bitmain_board_init: g_ccdly_opt = 1
2022-01-16 08:04:11 driver-btm-api.c:676:_set_project_type: project:2
2022-01-16 08:04:11 driver-btm-api.c:706:_set_project_type: Project type: Antminer T17
2022-01-16 08:04:11 driver-btm-api.c:717:dump_pcb_bom_version: Chain [0] PCB Version: 0x0100
2022-01-16 08:04:11 driver-btm-api.c:718:dump_pcb_bom_version: Chain [0] BOM Version: 0x0100
2022-01-16 08:04:11 driver-btm-api.c:717:dump_pcb_bom_version: Chain [1] PCB Version: 0x0100
2022-01-16 08:04:11 driver-btm-api.c:718:dump_pcb_bom_version: Chain [1] BOM Version: 0x0100
2022-01-16 08:04:11 driver-btm-api.c:717:dump_pcb_bom_version: Chain [2] PCB Version: 0x0100
2022-01-16 08:04:11 driver-btm-api.c:718:dump_pcb_bom_version: Chain [2] BOM Version: 0x0100
2022-01-16 08:04:13 driver-btm-api.c:1939:bitmain_board_init: Fan check passed.
2022-01-16 08:04:14 board.c:36:jump_and_app_check_restore_pic: chain[0] PIC jump to app
2022-01-16 08:04:18 board.c:40:jump_and_app_check_restore_pic: Check chain[0] PIC fw version=0xb9
2022-01-16 08:04:20 board.c:36:jump_and_app_check_restore_pic: chain[1] PIC jump to app
2022-01-16 08:04:23 board.c:40:jump_and_app_check_restore_pic: Check chain[1] PIC fw version=0xb9
2022-01-16 08:04:25 board.c:36:jump_and_app_check_restore_pic: chain[2] PIC jump to app
2022-01-16 08:04:28 board.c:40:jump_and_app_check_restore_pic: Check chain[2] PIC fw version=0xb9
2022-01-16 08:04:28 thread.c:880:create_pic_heart_beat_thread: create thread
2022-01-16 08:04:28 power_api.c:55:power_init: power init ...
2022-01-16 08:04:28 driver-btm-api.c:1949:bitmain_board_init: Enter 30s sleep to make sure power release finish.
2022-01-16 08:04:28 power_api.c:46:power_off: init gpio907
2022-01-16 08:05:00 power_api.c:232:set_iic_power_to_highest_voltage: setting to voltage: 17.00 ...
2022-01-16 08:05:06 power_api.c:124:check_voltage_multi: retry time: 0
2022-01-16 08:05:08 power_api.c:86:get_average_voltage: chain[0], voltage is: 0.067354
2022-01-16 08:05:10 power_api.c:86:get_average_voltage: chain[1], voltage is: 17.034316
2022-01-16 08:05:11 power_api.c:86:get_average_voltage: chain[2], voltage is: 16.905732
2022-01-16 08:05:11 power_api.c:97:get_average_voltage: aveage voltage is: 11.335801
2022-01-16 08:05:11 power_api.c:110:check_voltage: target_vol = 17.00, actural_vol = 11.34, more than 1.0v diff.
2022-01-16 08:05:12 power_api.c:124:check_voltage_multi: retry time: 1
2022-01-16 08:05:14 power_api.c:86:get_average_voltage: chain[0], voltage is: 17.046562
2022-01-16 08:05:16 power_api.c:86:get_average_voltage: chain[1], voltage is: 17.015947
2022-01-16 08:05:19 power_api.c:86:get_average_voltage: chain[2], voltage is: 16.924101
2022-01-16 08:05:19 power_api.c:97:get_average_voltage: aveage voltage is: 16.995537
2022-01-16 08:05:19 power_api.c:182:set_iic_power_by_voltage: now set voltage to : 17.000000
2022-01-16 08:05:19 uart.c:80:set_baud: set fpga_baud = 115200, fpga_divider = 26
2022-01-16 08:05:29 driver-btm-api.c:1042:check_asic_number_with_power_on: Chain[0]: find 30 asic, times 0
2022-01-16 08:05:39 driver-btm-api.c:1042:check_asic_number_with_power_on: Chain[1]: find 0 asic, times 0
2022-01-16 08:05:48 driver-btm-api.c:1042:check_asic_number_with_power_on: Chain[1]: find 0 asic, times 1
2022-01-16 08:05:59 driver-btm-api.c:1042:check_asic_number_with_power_on: Chain[1]: find 0 asic, times 2
2022-01-16 08:05:59 driver-btm-api.c:1069:check_asic_number: Chain 1 only find 0 asic, will power off hash board 1
2022-01-16 08:06:11 driver-btm-api.c:1042:check_asic_number_with_power_on: Chain[2]: find 30 asic, times 0
2022-01-16 08:06:13 driver-btm-api.c:352:set_order_clock: chain[0]: set order clock, stragegy 3 clock_en=0x1
2022-01-16 08:06:13 driver-btm-api.c:352:set_order_clock: chain[2]: set order clock, stragegy 3 clock_en=0x1
2022-01-16 08:06:13 driver-hash-chip.c:502:set_clock_delay_control: core_data = 0xb4
2022-01-16 08:06:13 uart.c:80:set_baud: set fpga_baud = 3000000, fpga_divider = 0
2022-01-16 08:06:13 driver-btm-api.c:1693:check_clock_counter: freq 50 clock_counter_limit 6
2022-01-16 08:06:14 register.c:1416:quick_dump_core_hash_clock_counter: bad clock counter. chain = 2, asic = 21, core = 105, found 1, clock counter 0x00340000
2022-01-16 08:06:14 uart.c:80:set_baud: set fpga_baud = 115200, fpga_divider = 26
2022-01-16 08:06:14 driver-btm-api.c:1981:bitmain_board_init: clock counter status was not good. Try reset.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: wndsnb on January 16, 2022, 01:49:17 PM
It looks like you have 2 bad hashboards that need repair. The 0V reading is not the issue, there is just a delay between the hashboard reading the voltage, and the psu setting it. The chain[1] board in the 1st log is reading incorrect voltage, the 22V reading is not correct. All 3 hashboards are actually reading the same exact voltage, the one delivered by the busbars. Could be an issue with the pic microcontroller. 2022-01-16 07:49:13 power_api.c:110:check_voltage: target_vol = 17.00, actural_vol = 18.82, more than 1.0v diff.
2022-01-16 07:49:14 power_api.c:124:check_voltage_multi: retry time: 2
...
2022-01-16 07:52:38 power_api.c:124:check_voltage_multi: retry time: 29
2022-01-16 07:52:40 power_api.c:86:get_average_voltage: chain[0], voltage is: 17.089424
2022-01-16 07:52:43 power_api.c:86:get_average_voltage: chain[1], voltage is: 22.385859
2022-01-16 07:52:46 power_api.c:86:get_average_voltage: chain[2], voltage is: 16.997578
2022-01-16 07:52:46 power_api.c:97:get_average_voltage: aveage voltage is: 18.824287
2022-01-16 07:52:46 power_api.c:110:check_voltage: target_vol = 17.00, actural_vol = 18.82, more than 1.0v diff.
2022-01-16 07:52:47 power_api.c:182:set_iic_power_by_voltage: now set voltage to : 17.000000
2022-01-16 07:52:47 driver-btm-api.c:205:set_miner_status: ERROR_POWER_LOST
2022-01-16 07:52:47 driver-btm-api.c:146:stop_mining: stop mining: power set failed!
The chain[1] board in the 2nd log is measuring the voltage correctly, but not finding any ASICs, so there is likely a bad solder connection somewhere on the board. The "find 0 asic" log entry is the issue. 2022-01-16 08:05:00 power_api.c:232:set_iic_power_to_highest_voltage: setting to voltage: 17.00 ...
2022-01-16 08:05:06 power_api.c:124:check_voltage_multi: retry time: 0
2022-01-16 08:05:08 power_api.c:86:get_average_voltage: chain[0], voltage is: 0.067354
2022-01-16 08:05:10 power_api.c:86:get_average_voltage: chain[1], voltage is: 17.034316
2022-01-16 08:05:11 power_api.c:86:get_average_voltage: chain[2], voltage is: 16.905732
2022-01-16 08:05:11 power_api.c:97:get_average_voltage: aveage voltage is: 11.335801
2022-01-16 08:05:11 power_api.c:110:check_voltage: target_vol = 17.00, actural_vol = 11.34, more than 1.0v diff.
2022-01-16 08:05:12 power_api.c:124:check_voltage_multi: retry time: 1
2022-01-16 08:05:14 power_api.c:86:get_average_voltage: chain[0], voltage is: 17.046562
2022-01-16 08:05:16 power_api.c:86:get_average_voltage: chain[1], voltage is: 17.015947
2022-01-16 08:05:19 power_api.c:86:get_average_voltage: chain[2], voltage is: 16.924101
2022-01-16 08:05:19 power_api.c:97:get_average_voltage: aveage voltage is: 16.995537
2022-01-16 08:05:19 power_api.c:182:set_iic_power_by_voltage: now set voltage to : 17.000000
2022-01-16 08:05:19 uart.c:80:set_baud: set fpga_baud = 115200, fpga_divider = 26
2022-01-16 08:05:29 driver-btm-api.c:1042:check_asic_number_with_power_on: Chain[0]: find 30 asic, times 0
2022-01-16 08:05:39 driver-btm-api.c:1042:check_asic_number_with_power_on: Chain[1]: find 0 asic, times 0
2022-01-16 08:05:48 driver-btm-api.c:1042:check_asic_number_with_power_on: Chain[1]: find 0 asic, times 1
2022-01-16 08:05:59 driver-btm-api.c:1042:check_asic_number_with_power_on: Chain[1]: find 0 asic, times 2
2022-01-16 08:05:59 driver-btm-api.c:1069:check_asic_number: Chain 1 only find 0 asic, will power off hash board 1
2022-01-16 08:06:11 driver-btm-api.c:1042:check_asic_number_with_power_on: Chain[2]: find 30 asic, times 0
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: Heathen23 on January 16, 2022, 11:36:13 PM
Hi Guys, I am having trouble with an S17+. This one used to run well and suddenly stopped working. I opened up, cleaned the power supply and the hash-boards. While putting the hash-boards back a capacitor from 3rd hash-board(Chain2) got detached from the board. I soldered it back. Now, Chain 0: starts hashing but is shutoff with the following error "ERROR: chain 0 get hashrate_reg_counter 58, require 65, failed times 1: ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo oooxx xxxxx chain 0 can't get enough hashrate reg val for 30 times, power off." Chain1: working fine. Chain2: is powered off with error: "Chain 2 only find 62 asic, will power off hash board 2". This is the board that lost the capacitor that i have resoldered. - I am thinking I have to re-solder chip 59 on chain 0 and resolder chip 63 on Chain 2. Do you think the problem with chain 2 is the capacitor rather than the 63rd chip? Would you do something different if you faced these errors? I notice that with bosminer all 3 boards start and shut off. Booting Linux on physical CPU 0x0
Linux version 4.6.0-xilinx-gff8137b-dirty (lzq@armdev2) (gcc version 4.8.3 20140320 (prerelease) (Sourcery CodeBench Lite 2014.05-23) ) #25 SMP PREEMPT Fri Nov 23 15:30:52 CST 2018
CPU: ARMv7 Processor [413fc090] revision 0 (ARMv7), cr=18c5387d
CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
Machine model: Xilinx Zynq
cma: Reserved 16 MiB at 0x0e000000
Memory policy: Data cache writealloc
On node 0 totalpages: 61440
free_area_init_node: node 0, pgdat c0b39280, node_mem_map cde10000
Normal zone: 480 pages used for memmap
Normal zone: 0 pages reserved
Normal zone: 61440 pages, LIFO batch:15
percpu: Embedded 12 pages/cpu @cddf1000 s19776 r8192 d21184 u49152
pcpu-alloc: s19776 r8192 d21184 u49152 alloc=12*4096
pcpu-alloc: [0] 0 [0] 1
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 60960
Kernel command line: mem=240M console=ttyPS0,115200 ramdisk_size=33554432 root=/dev/ram rw earlyprintk
PID hash table entries: 1024 (order: 0, 4096 bytes)
Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
Memory: 203316K/245760K available (6345K kernel code, 231K rwdata, 1896K rodata, 1024K init, 223K bss, 26060K reserved, 16384K cma-reserved, 0K highmem)
Virtual kernel memory layout:
vector : 0xffff0000 - 0xffff1000 ( 4 kB)
fixmap : 0xffc00000 - 0xfff00000 (3072 kB)
vmalloc : 0xcf800000 - 0xff800000 ( 768 MB)
lowmem : 0xc0000000 - 0xcf000000 ( 240 MB)
pkmap : 0xbfe00000 - 0xc0000000 ( 2 MB)
modules : 0xbf000000 - 0xbfe00000 ( 14 MB)
.text : 0xc0008000 - 0xc090c424 (9234 kB)
.init : 0xc0a00000 - 0xc0b00000 (1024 kB)
.data : 0xc0b00000 - 0xc0b39fe0 ( 232 kB)
.bss : 0xc0b39fe0 - 0xc0b71c28 ( 224 kB)
Preemptible hierarchical RCU implementation.
Build-time adjustment of leaf fanout to 32.
RCU restricting CPUs from NR_CPUS=4 to nr_cpu_ids=2.
RCU: Adjusting geometry for rcu_fanout_leaf=32, nr_cpu_ids=2
NR_IRQS:16 nr_irqs:16 16
efuse mapped to cf800000
ps7-slcr mapped to cf802000
L2C: platform modifies aux control register: 0x72360000 -> 0x72760000
L2C: DT/platform modifies aux control register: 0x72360000 -> 0x72760000
L2C-310 erratum 769419 enabled
L2C-310 enabling early BRESP for Cortex-A9
L2C-310 full line of zeros enabled for Cortex-A9
L2C-310 ID prefetch enabled, offset 1 lines
L2C-310 dynamic clock gating enabled, standby mode enabled
L2C-310 cache controller enabled, 8 ways, 512 kB
L2C-310: CACHE_ID 0x410000c8, AUX_CTRL 0x76760001
zynq_clock_init: clkc starts at cf802100
Zynq clock init
sched_clock: 64 bits at 333MHz, resolution 3ns, wraps every 4398046511103ns
clocksource: arm_global_timer: mask: 0xffffffffffffffff max_cycles: 0x4ce07af025, max_idle_ns: 440795209040 ns
Switching to timer-based delay loop, resolution 3ns
clocksource: ttc_clocksource: mask: 0xffff max_cycles: 0xffff, max_idle_ns: 537538477 ns
ps7-ttc #0 at cf80a000, irq=18
Console: colour dummy device 80x30
Calibrating delay loop (skipped), value calculated using timer frequency.. 666.66 BogoMIPS (lpj=3333333)
pid_max: default: 32768 minimum: 301
Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
CPU: Testing write buffer coherency: ok
CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
Setting up static identity map for 0x100000 - 0x100058
CPU1: failed to boot: -1
Brought up 1 CPUs
SMP: Total of 1 processors activated (666.66 BogoMIPS).
CPU: All CPU(s) started in SVC mode.
devtmpfs: initialized
VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4
clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
pinctrl core: initialized pinctrl subsystem
NET: Registered protocol family 16
DMA: preallocated 256 KiB pool for atomic coherent allocations
cpuidle: using governor menu
hw-breakpoint: found 5 (+1 reserved) breakpoint and 1 watchpoint registers.
hw-breakpoint: maximum watchpoint size is 4 bytes.
zynq-ocm f800c000.ps7-ocmc: ZYNQ OCM pool: 256 KiB @ 0xcf880000
vgaarb: loaded
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
media: Linux media interface: v0.10
Linux video capture interface: v2.00
pps_core: LinuxPPS API ver. 1 registered
pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
PTP clock support registered
EDAC MC: Ver: 3.0.0
Advanced Linux Sound Architecture Driver Initialized.
clocksource: Switched to clocksource arm_global_timer
NET: Registered protocol family 2
TCP established hash table entries: 2048 (order: 1, 8192 bytes)
TCP bind hash table entries: 2048 (order: 2, 16384 bytes)
TCP: Hash tables configured (established 2048 bind 2048)
UDP hash table entries: 256 (order: 1, 8192 bytes)
UDP-Lite hash table entries: 256 (order: 1, 8192 bytes)
NET: Registered protocol family 1
RPC: Registered named UNIX socket transport module.
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
PCI: CLS 0 bytes, default 64
Trying to unpack rootfs image as initramfs...
rootfs image is not initramfs (no cpio magic); looks like an initrd
Freeing initrd memory: 13020K (cce49000 - cdb00000)
hw perfevents: enabled with armv7_cortex_a9 PMU driver, 7 counters available
futex hash table entries: 512 (order: 3, 32768 bytes)
workingset: timestamp_bits=28 max_order=16 bucket_order=0
jffs2: version 2.2. (NAND) (SUMMARY) © 2001-2006 Red Hat, Inc.
io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered (default)
dma-pl330 f8003000.ps7-dma: Loaded driver for PL330 DMAC-241330
dma-pl330 f8003000.ps7-dma: DBUFF-128x8bytes Num_Chans-8 Num_Peri-4 Num_Events-16
e0000000.serial: ttyPS0 at MMIO 0xe0000000 (irq = 158, base_baud = 6249999) is a xuartps
console [ttyPS0] enabled
xdevcfg f8007000.ps7-dev-cfg: ioremap 0xf8007000 to cf86e000
[drm] Initialized drm 1.1.0 20060810
brd: module loaded
loop: module loaded
CAN device driver interface
gpiod_set_value: invalid GPIO
libphy: MACB_mii_bus: probed
macb e000b000.ethernet eth0: Cadence GEM rev 0x00020118 at 0xe000b000 irq 31 (00:0a:35:00:00:00)
Generic PHY e000b000.etherne:00: attached PHY driver [Generic PHY] (mii_bus:phy_addr=e000b000.etherne:00, irq=-1)
e1000e: Intel(R) PRO/1000 Network Driver - 3.2.6-k
e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
ehci-pci: EHCI PCI platform driver
usbcore: registered new interface driver usb-storage
mousedev: PS/2 mouse device common for all mice
i2c /dev entries driver
Xilinx Zynq CpuIdle Driver started
sdhci: Secure Digital Host Controller Interface driver
sdhci: Copyright(c) Pierre Ossman
sdhci-pltfm: SDHCI platform and OF driver helper
mmc0: SDHCI controller on e0100000.ps7-sdio [e0100000.ps7-sdio] using ADMA
ledtrig-cpu: registered to indicate activity on CPUs
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
nand: device found, Manufacturer ID: 0x2c, Chip ID: 0xda
nand: Micron MT29F2G08ABAEAWP
nand: 256 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 64
nand: WARNING: pl35x-nand: the ECC used on your system is too weak compared to the one required by the NAND chip
Bad block table found at page 131008, version 0x01
Bad block table found at page 130944, version 0x01
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: 1/0, WL threshold: 4096, image sequence number: 11906131
ubi0: available PEBs: 0, total reserved PEBs: 64, PEBs reserved for bad PEB handling: 40
ubi0: background thread "ubi_bgt0d" started, PID 708
UBIFS (ubi0:0): background thread "ubifs_bgt0_0" started, PID 711
UBIFS (ubi0:0): UBIFS: mounted UBI device 0, volume 0, name "configs"
UBIFS (ubi0:0): LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
UBIFS (ubi0:0): FS size: 1396736 bytes (1 MiB, 11 LEBs), journal size 888833 bytes (0 MiB, 5 LEBs)
UBIFS (ubi0:0): reserved for root: 65970 bytes (64 KiB)
UBIFS (ubi0:0): media format: w4/r0 (latest is w4/r0), UUID 5C61C316-5FAD-4CFA-B280-2AFAE13C9D72, 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: 1/0, WL threshold: 4096, image sequence number: 169213079
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): default file-system created
UBIFS (ubi1:0): background thread "ubifs_bgt1_0" started, PID 723
UBIFS (ubi1:0): UBIFS: mounted UBI device 1, volume 0, name "reserve1"
UBIFS (ubi1:0): LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
UBIFS (ubi1:0): FS size: 123039744 bytes (117 MiB, 969 LEBs), journal size 6221824 bytes (5 MiB, 49 LEBs)
UBIFS (ubi1:0): reserved for root: 4952683 bytes (4836 KiB)
UBIFS (ubi1:0): media format: w4/r0 (latest is w4/r0), UUID 6FB1BE46-BF1C-4F4C-9CA2-2F82009B82B4, 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 0xcfb58000
*base_vir_addr = 0xb023
In fpga mem driver!
request_mem_region OK!
fpga mem virtual address is 0xd2000000
random: nonblocking pool is initialized
2022-01-16 22:43:51 driver-btm-api.c:779:init_freq_mode: This is scan-user version
2022-01-16 22:43:51 driver-btm-api.c:2451:bitmain_soc_init: opt_multi_version = 1
2022-01-16 22:43:51 driver-btm-api.c:2452:bitmain_soc_init: opt_bitmain_ab = 1
2022-01-16 22:43:51 driver-btm-api.c:2453:bitmain_soc_init: opt_bitmain_work_mode = 0
2022-01-16 22:43:51 driver-btm-api.c:2454:bitmain_soc_init: Miner compile time: Tue Jun 2 10:31:07 CST 2020 type: Antminer S17+
2022-01-16 22:43:51 driver-btm-api.c:2455:bitmain_soc_init: commit version: 1ca50a5 2020-06-01 18:51:22, build by: lol 2020-06-02 10:37:21
2022-01-16 22:43:51 driver-btm-api.c:2083:show_sn: len:16, 8034b4442b104814
2022-01-16 22:43:51 driver-btm-api.c:2461:bitmain_soc_init: show sn return 1
2022-01-16 22:43:51 driver-btm-api.c:2103:handle_sn_for_factory_mode: show sn return 1
2022-01-16 22:43:51 driver-btm-api.c:2141:handle_sn_for_factory_mode: read sn success, 8034b4442b104814
2022-01-16 22:43:51 fan.c:284:front_fan_power_on: Note: front fan is power on!
2022-01-16 22:43:51 fan.c:296:rear_fan_power_on: Note: rear fan is power on!
2022-01-16 22:43:51 driver-btm-api.c:1314:miner_device_init: Detect 256MB control board of XILINX
2022-01-16 22:43:51 driver-btm-api.c:1255:init_fan_parameter: fan_eft : 0 fan_pwm : 0
2022-01-16 22:43:57 driver-btm-api.c:1239:init_miner_version: miner ID : 8034b4442b104814
2022-01-16 22:43:57 driver-btm-api.c:1245:init_miner_version: FPGA Version = 0xB023
2022-01-16 22:44:02 driver-btm-api.c:837:get_product_id: product_id[0] = 0
2022-01-16 22:44:02 driver-btm-api.c:837:get_product_id: product_id[1] = 0
2022-01-16 22:44:02 driver-btm-api.c:837:get_product_id: product_id[2] = 0
2022-01-16 22:44:02 driver-btm-api.c:2234:update_conf_by_power_feedback: Power feedback is disabled
2022-01-16 22:44:02 driver-btm-api.c:2202:get_calibration_voltage: calibration voltage flag is error data.
2022-01-16 22:44:02 driver-btm-api.c:2268:update_conf_by_power_feedback: Note: no calibration voltage, default diff = 0
2022-01-16 22:44:02 frequency.c:1457:adjust_higer_max_vol_table: adjust_higer_max_vol_table, adjust_vol = 0
2022-01-16 22:44:02 thread.c:1363:create_read_nonce_reg_thread: create thread
2022-01-16 22:44:08 driver-btm-api.c:1239:init_miner_version: miner ID : 8034b4442b104814
2022-01-16 22:44:08 driver-btm-api.c:1245:init_miner_version: FPGA Version = 0xB023
2022-01-16 22:44:14 driver-btm-api.c:837:get_product_id: product_id[0] = 0
2022-01-16 22:44:14 driver-btm-api.c:837:get_product_id: product_id[1] = 0
2022-01-16 22:44:14 driver-btm-api.c:837:get_product_id: product_id[2] = 0
2022-01-16 22:44:14 driver-btm-api.c:792:_set_project_type: project:0
2022-01-16 22:44:14 driver-btm-api.c:813:_set_project_type: Project type: Antminer S17+
2022-01-16 22:44:14 driver-btm-api.c:824:dump_pcb_bom_version: Chain [0] PCB Version: 0x0100
2022-01-16 22:44:14 driver-btm-api.c:825:dump_pcb_bom_version: Chain [0] BOM Version: 0x0100
2022-01-16 22:44:14 driver-btm-api.c:824:dump_pcb_bom_version: Chain [1] PCB Version: 0x0100
2022-01-16 22:44:14 driver-btm-api.c:825:dump_pcb_bom_version: Chain [1] BOM Version: 0x0100
2022-01-16 22:44:14 driver-btm-api.c:824:dump_pcb_bom_version: Chain [2] PCB Version: 0x0100
2022-01-16 22:44:14 driver-btm-api.c:825:dump_pcb_bom_version: Chain [2] BOM Version: 0x0100
2022-01-16 22:44:14 driver-btm-api.c:2372:bitmain_board_init: Fan check passed.
2022-01-16 22:44:15 board.c:36:jump_and_app_check_restore_pic: chain[0] PIC jump to app
2022-01-16 22:44:17 board.c:40:jump_and_app_check_restore_pic: Check chain[0] PIC fw version=0x88
2022-01-16 22:44:18 board.c:36:jump_and_app_check_restore_pic: chain[1] PIC jump to app
2022-01-16 22:44:20 board.c:40:jump_and_app_check_restore_pic: Check chain[1] PIC fw version=0x88
2022-01-16 22:44:21 board.c:36:jump_and_app_check_restore_pic: chain[2] PIC jump to app
2022-01-16 22:44:23 board.c:40:jump_and_app_check_restore_pic: Check chain[2] PIC fw version=0x88
2022-01-16 22:44:23 thread.c:1358:create_pic_heart_beat_thread: create thread
2022-01-16 22:44:23 power_api.c:213:power_init: Power init:
2022-01-16 22:44:23 power_api.c:214:power_init: current_voltage_raw = 0
2022-01-16 22:44:23 power_api.c:215:power_init: highest_voltage_raw = 2100
2022-01-16 22:44:23 power_api.c:216:power_init: working_voltage_raw = 1950
2022-01-16 22:44:23 power_api.c:217:power_init: higher_voltage_raw = 2040
2022-01-16 22:44:23 power_api.c:218:power_init: check_asic_voltage_raw = 2100
2022-01-16 22:44:23 driver-btm-api.c:2382:bitmain_board_init: Enter 30s sleep to make sure power release finish.
2022-01-16 22:44:55 power_api.c:324:set_to_highest_voltage_by_steps: Set to voltage raw 2100, step by step.
2022-01-16 22:45:21 power_api.c:85:check_voltage_multi: retry time: 0
2022-01-16 22:45:22 power_api.c:40:_get_avg_voltage: chain = 0, voltage = 21.070513
2022-01-16 22:45:23 power_api.c:40:_get_avg_voltage: chain = 1, voltage = 21.100258
2022-01-16 22:45:24 power_api.c:40:_get_avg_voltage: chain = 2, voltage = 21.271209
2022-01-16 22:45:24 power_api.c:53:_get_avg_voltage: average_voltage = 21.147326
2022-01-16 22:45:24 power_api.c:71:check_voltage: target_vol = 21.00, actural_vol = 21.15, check voltage passed.
2022-01-16 22:45:24 uart.c:72:set_baud: set fpga_baud to 115200
2022-01-16 22:45:35 driver-btm-api.c:1134:check_asic_number_with_power_on: Chain[0]: find 65 asic, times 0
2022-01-16 22:45:46 driver-btm-api.c:1134:check_asic_number_with_power_on: Chain[1]: find 8 asic, times 0
2022-01-16 22:45:57 driver-btm-api.c:1134:check_asic_number_with_power_on: Chain[1]: find 8 asic, times 1
2022-01-16 22:46:08 driver-btm-api.c:1134:check_asic_number_with_power_on: Chain[1]: find 8 asic, times 2
2022-01-16 22:46:08 power_api.c:380:modify_check_asic_voltage: check_asic_voltage_raw = 2100
chain 1, IO_DRIVE_STRENGTH_CONFIGURATION reg = 0x f1fffff
2022-01-16 22:46:17 driver-btm-api.c:1157:check_asic_number_with_power_on: Chain[1]: find 63 asic, times 3
2022-01-16 22:46:17 power_api.c:380:modify_check_asic_voltage: check_asic_voltage_raw = 2050
2022-01-16 22:46:17 power_api.c:364:set_to_check_asic_voltage_by_steps: Set to voltage raw 2050, step by step.
2022-01-16 22:46:21 power_api.c:85:check_voltage_multi: retry time: 0
2022-01-16 22:46:23 power_api.c:40:_get_avg_voltage: chain = 0, voltage = 20.556977
2022-01-16 22:46:24 power_api.c:40:_get_avg_voltage: chain = 1, voltage = 20.560975
2022-01-16 22:46:25 power_api.c:40:_get_avg_voltage: chain = 2, voltage = 20.758355
2022-01-16 22:46:25 power_api.c:53:_get_avg_voltage: average_voltage = 20.625436
2022-01-16 22:46:25 power_api.c:71:check_voltage: target_vol = 20.50, actural_vol = 20.63, check voltage passed.
chain 1, IO_DRIVE_STRENGTH_CONFIGURATION reg = 0x f1fffff
2022-01-16 22:46:34 driver-btm-api.c:1157:check_asic_number_with_power_on: Chain[1]: find 65 asic, times 4
2022-01-16 22:46:34 power_api.c:324:set_to_highest_voltage_by_steps: Set to voltage raw 2100, step by step.
2022-01-16 22:46:37 power_api.c:85:check_voltage_multi: retry time: 0
2022-01-16 22:46:39 power_api.c:40:_get_avg_voltage: chain = 0, voltage = 21.019205
2022-01-16 22:46:40 power_api.c:40:_get_avg_voltage: chain = 1, voltage = 21.048780
2022-01-16 22:46:41 power_api.c:40:_get_avg_voltage: chain = 2, voltage = 21.246787
2022-01-16 22:46:41 power_api.c:53:_get_avg_voltage: average_voltage = 21.104924
2022-01-16 22:46:41 power_api.c:71:check_voltage: target_vol = 21.00, actural_vol = 21.10, check voltage passed.
2022-01-16 22:46:52 driver-btm-api.c:1134:check_asic_number_with_power_on: Chain[2]: find 62 asic, times 0
2022-01-16 22:47:03 driver-btm-api.c:1134:check_asic_number_with_power_on: Chain[2]: find 62 asic, times 1
2022-01-16 22:47:14 driver-btm-api.c:1134:check_asic_number_with_power_on: Chain[2]: find 62 asic, times 2
2022-01-16 22:47:14 power_api.c:380:modify_check_asic_voltage: check_asic_voltage_raw = 2100
chain 2, IO_DRIVE_STRENGTH_CONFIGURATION reg = 0x f1fffff
2022-01-16 22:47:23 driver-btm-api.c:1157:check_asic_number_with_power_on: Chain[2]: find 62 asic, times 3
2022-01-16 22:47:23 power_api.c:380:modify_check_asic_voltage: check_asic_voltage_raw = 2050
2022-01-16 22:47:23 power_api.c:364:set_to_check_asic_voltage_by_steps: Set to voltage raw 2050, step by step.
2022-01-16 22:47:27 power_api.c:85:check_voltage_multi: retry time: 0
2022-01-16 22:47:28 power_api.c:40:_get_avg_voltage: chain = 0, voltage = 20.556977
2022-01-16 22:47:29 power_api.c:40:_get_avg_voltage: chain = 1, voltage = 20.560975
2022-01-16 22:47:30 power_api.c:40:_get_avg_voltage: chain = 2, voltage = 20.731706
2022-01-16 22:47:30 power_api.c:53:_get_avg_voltage: average_voltage = 20.616553
2022-01-16 22:47:30 power_api.c:71:check_voltage: target_vol = 20.50, actural_vol = 20.62, check voltage passed.
chain 2, IO_DRIVE_STRENGTH_CONFIGURATION reg = 0x f1fffff
2022-01-16 22:47:39 driver-btm-api.c:1157:check_asic_number_with_power_on: Chain[2]: find 62 asic, times 4
2022-01-16 22:47:39 power_api.c:380:modify_check_asic_voltage: check_asic_voltage_raw = 2000
2022-01-16 22:47:39 power_api.c:364:set_to_check_asic_voltage_by_steps: Set to voltage raw 2000, step by step.
2022-01-16 22:47:42 power_api.c:85:check_voltage_multi: retry time: 0
2022-01-16 22:47:43 power_api.c:40:_get_avg_voltage: chain = 0, voltage = 20.046094
2022-01-16 22:47:44 power_api.c:40:_get_avg_voltage: chain = 1, voltage = 20.048780
2022-01-16 22:47:45 power_api.c:40:_get_avg_voltage: chain = 2, voltage = 20.219511
2022-01-16 22:47:45 power_api.c:53:_get_avg_voltage: average_voltage = 20.104795
2022-01-16 22:47:45 power_api.c:71:check_voltage: target_vol = 20.00, actural_vol = 20.10, check voltage passed.
chain 2, IO_DRIVE_STRENGTH_CONFIGURATION reg = 0x f1fffff
2022-01-16 22:47:55 driver-btm-api.c:1157:check_asic_number_with_power_on: Chain[2]: find 62 asic, times 5
2022-01-16 22:47:55 power_api.c:380:modify_check_asic_voltage: check_asic_voltage_raw = 2100
2022-01-16 22:47:55 power_api.c:364:set_to_check_asic_voltage_by_steps: Set to voltage raw 2100, step by step.
2022-01-16 22:48:00 power_api.c:85:check_voltage_multi: retry time: 0
2022-01-16 22:48:01 power_api.c:40:_get_avg_voltage: chain = 0, voltage = 21.043533
2022-01-16 22:48:02 power_api.c:40:_get_avg_voltage: chain = 1, voltage = 21.048780
2022-01-16 22:48:03 power_api.c:40:_get_avg_voltage: chain = 2, voltage = 21.219511
2022-01-16 22:48:03 power_api.c:53:_get_avg_voltage: average_voltage = 21.103941
2022-01-16 22:48:03 power_api.c:71:check_voltage: target_vol = 21.00, actural_vol = 21.10, check voltage passed.
2022-01-16 22:48:03 driver-btm-api.c:1193:check_asic_number: Chain 2 only find 62 asic, will power off hash board 2
2022-01-16 22:48:04 driver-btm-api.c:1195:check_asic_number: Chain 2 voltage: an0 = 2.787097, an2 2.806452, an6 2.512903.
2022-01-16 22:48:11 driver-hash-chip.c:266:set_uart_relay: set uart relay to 0x330003
2022-01-16 22:48:11 driver-btm-api.c:435:set_order_clock: chain[0]: set order clock, stragegy 3
2022-01-16 22:48:11 driver-btm-api.c:435:set_order_clock: chain[1]: set order clock, stragegy 3
2022-01-16 22:48:11 driver-hash-chip.c:502:set_clock_delay_control: core_data = 0x34
2022-01-16 22:48:11 driver-btm-api.c:1892:check_clock_counter: freq 50 clock_counter_limit 6
2022-01-16 22:48:12 voltage[0] = 1920
2022-01-16 22:48:12 voltage[1] = 1920
2022-01-16 22:48:12 power_api.c:226:set_working_voltage_raw: working_voltage_raw = 1920
2022-01-16 22:48:13 temperature.c:340:calibrate_temp_sensor_one_chain: chain 0 temp sensor NCT218
2022-01-16 22:48:14 temperature.c:340:calibrate_temp_sensor_one_chain: chain 1 temp sensor NCT218
2022-01-16 22:48:14 uart.c:72:set_baud: set fpga_baud to 12000000
2022-01-16 22:48:15 driver-btm-api.c:293:check_bringup_temp: Bring up temperature is 23
2022-01-16 22:48:15 thread.c:1378:create_check_miner_status_thread: create thread
2022-01-16 22:48:15 thread.c:1368:create_show_miner_status_thread: create thread
2022-01-16 22:48:15 thread.c:1348:create_temperature_monitor_thread: create thread
2022-01-16 22:48:15 frequency.c:514:check_bringup_temp_dec_freq: dec freq = 0 when bringup temp = 23 dec_freq_index=0
2022-01-16 22:48:15 freq_tuning.c:183:freq_tuning_get_max_freq: Max freq of tuning is 650
2022-01-16 22:48:15 driver-btm-api.c:1765:send_null_work: [DEBUG] Send null work.
2022-01-16 22:48:15 thread.c:1338:create_asic_status_monitor_thread: create thread
2022-01-16 22:48:15 frequency.c:1110:inc_freq_with_fixed_vco: chain = 255, freq = 560, is_higher_voltage = true
2022-01-16 22:49:47 power_api.c:352:set_to_voltage_by_steps: Set to voltage raw 2090, step by step.
2022-01-16 22:49:48 power_api.c:85:check_voltage_multi: retry time: 0
2022-01-16 22:49:49 power_api.c:40:_get_avg_voltage: chain = 0, voltage = 20.897566
2022-01-16 22:49:51 power_api.c:40:_get_avg_voltage: chain = 1, voltage = 20.926828
2022-01-16 22:49:51 power_api.c:53:_get_avg_voltage: average_voltage = 20.912197
2022-01-16 22:49:51 power_api.c:71:check_voltage: target_vol = 20.90, actural_vol = 20.91, check voltage passed.
2022-01-16 22:52:02 power_api.c:352:set_to_voltage_by_steps: Set to voltage raw 2080, step by step.
2022-01-16 22:52:03 power_api.c:85:check_voltage_multi: retry time: 0
2022-01-16 22:52:04 power_api.c:40:_get_avg_voltage: chain = 0, voltage = 20.775927
2022-01-16 22:52:05 power_api.c:40:_get_avg_voltage: chain = 1, voltage = 20.780487
2022-01-16 22:52:05 power_api.c:53:_get_avg_voltage: average_voltage = 20.778207
2022-01-16 22:52:05 power_api.c:71:check_voltage: target_vol = 20.80, actural_vol = 20.78, check voltage passed.
2022-01-16 22:54:29 frequency.c:1152:inc_freq_with_fixed_step: chain = 0, freq_start = 560, freq_end = 570, freq_step = 5, is_higher_voltage = true
2022-01-16 22:54:33 frequency.c:1181:inc_asic_diff_freq_by_steps: chain = 1, start = 560, freq_step = 5
2022-01-16 22:54:35 driver-btm-api.c:765:set_timeout: freq = 570, percent = 90, hcn = 44236, timeout = 77
2022-01-16 22:54:35 power_api.c:310:set_to_working_voltage_by_steps: Set to voltage raw 1920, step by step.
2022-01-16 22:54:42 power_api.c:85:check_voltage_multi: retry time: 0
2022-01-16 22:54:43 power_api.c:40:_get_avg_voltage: chain = 0, voltage = 19.218949
2022-01-16 22:54:44 power_api.c:40:_get_avg_voltage: chain = 1, voltage = 19.219511
2022-01-16 22:54:44 power_api.c:53:_get_avg_voltage: average_voltage = 19.219230
2022-01-16 22:54:44 power_api.c:71:check_voltage: target_vol = 19.20, actural_vol = 19.22, check voltage passed.
2022-01-16 22:54:44 thread.c:1373:create_check_system_status_thread: create thread
2022-01-16 22:54:44 driver-btm-api.c:2618:bitmain_soc_init: Init done!
2022-01-16 22:54:44 driver-btm-api.c:222:set_miner_status: STATUS_INIT
2022-01-16 22:54:49 driver-btm-api.c:222:set_miner_status: STATUS_OKAY
2022-01-16 22:54:50 frequency.c:205:get_ideal_hash_rate_GH: ideal_hash_rate = 48464
2022-01-16 22:54:50 frequency.c:223:get_sale_hash_rate_GH: sale_hash_rate = 46000
2022-01-16 22:54:54 driver-btm-api.c:1496:dhash_chip_send_job: Version num 4.
2022-01-16 22:54:54 driver-btm-api.c:1644:dhash_chip_send_job: stime.tv_sec 1642373694, block_ntime 1642373688
2022-01-16 23:05:51 thread.c:1273:asic_status_monitor_thread: ERROR: chain 0 get hashrate_reg_counter 58, require 65, failed times 1: ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo oooxx xxxxx
2022-01-16 23:05:53 thread.c:1293:asic_status_monitor_thread: chain 0 can't get enough hashrate reg val for 0 times.
2022-01-16 23:05:53 thread.c:1273:asic_status_monitor_thread: ERROR: chain 0 get hashrate_reg_counter 58, require 65, failed times 1: ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo oooxx xxxxx
2022-01-16 23:05:55 thread.c:1293:asic_status_monitor_thread: chain 0 can't get enough hashrate reg val for 1 times.
2022-01-16 23:05:55 thread.c:1273:asic_status_monitor_thread: ERROR: chain 0 get hashrate_reg_counter 58, require 65, failed times 1: ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo oooxx xxxxx
2022-01-16 23:05:57 thread.c:1293:asic_status_monitor_thread: chain 0 can't get enough hashrate reg val for 2 times.
2022-01-16 23:05:57 thread.c:1273:asic_status_monitor_thread: ERROR: chain 0 get hashrate_reg_counter 58, require 65, failed times 1: ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo oooxx xxxxx
2022-01-16 23:05:59 thread.c:1293:asic_status_monitor_thread: chain 0 can't get enough hashrate reg val for 3 times.
2022-01-16 23:05:59 thread.c:1273:asic_status_monitor_thread: ERROR: chain 0 get hashrate_reg_counter 58, require 65, failed times 1: ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo oooxx xxxxx
2022-01-16 23:06:01 thread.c:1293:asic_status_monitor_thread: chain 0 can't get enough hashrate reg val for 4 times.
2022-01-16 23:06:01 thread.c:1273:asic_status_monitor_thread: ERROR: chain 0 get hashrate_reg_counter 58, require 65, failed times 1: ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo oooxx xxxxx
2022-01-16 23:06:03 thread.c:1293:asic_status_monitor_thread: chain 0 can't get enough hashrate reg val for 5 times.
2022-01-16 23:06:03 thread.c:1273:asic_status_monitor_thread: ERROR: chain 0 get hashrate_reg_counter 58, require 65, failed times 1: ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo oooxx xxxxx
2022-01-16 23:06:05 thread.c:1293:asic_status_monitor_thread: chain 0 can't get enough hashrate reg val for 6 times.
2022-01-16 23:06:05 thread.c:1273:asic_status_monitor_thread: ERROR: chain 0 get hashrate_reg_counter 58, require 65, failed times 1: ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo oooxx xxxxx
2022-01-16 23:06:07 thread.c:1293:asic_status_monitor_thread: chain 0 can't get enough hashrate reg val for 7 times.
2022-01-16 23:06:07 thread.c:1273:asic_status_monitor_thread: ERROR: chain 0 get hashrate_reg_counter 58, require 65, failed times 1: ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo oooxx xxxxx
2022-01-16 23:06:09 thread.c:1293:asic_status_monitor_thread: chain 0 can't get enough hashrate reg val for 8 times.
2022-01-16 23:06:09 thread.c:1273:asic_status_monitor_thread: ERROR: chain 0 get hashrate_reg_counter 58, require 65, failed times 1: ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo oooxx xxxxx
2022-01-16 23:06:11 thread.c:1293:asic_status_monitor_thread: chain 0 can't get enough hashrate reg val for 9 times.
2022-01-16 23:06:11 thread.c:1273:asic_status_monitor_thread: ERROR: chain 0 get hashrate_reg_counter 58, require 65, failed times 1: ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo oooxx xxxxx
2022-01-16 23:06:13 thread.c:1293:asic_status_monitor_thread: chain 0 can't get enough hashrate reg val for 10 times.
2022-01-16 23:06:13 thread.c:1273:asic_status_monitor_thread: ERROR: chain 0 get hashrate_reg_counter 58, require 65, failed times 1: ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo oooxx xxxxx
2022-01-16 23:06:15 thread.c:1293:asic_status_monitor_thread: chain 0 can't get enough hashrate reg val for 11 times.
2022-01-16 23:06:15 thread.c:1273:asic_status_monitor_thread: ERROR: chain 0 get hashrate_reg_counter 58, require 65, failed times 1: ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo oooxx xxxxx
2022-01-16 23:06:17 thread.c:1293:asic_status_monitor_thread: chain 0 can't get enough hashrate reg val for 12 times.
2022-01-16 23:06:17 thread.c:1273:asic_status_monitor_thread: ERROR: chain 0 get hashrate_reg_counter 58, require 65, failed times 1: ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo oooxx xxxxx
2022-01-16 23:06:19 thread.c:1293:asic_status_monitor_thread: chain 0 can't get enough hashrate reg val for 13 times.
2022-01-16 23:06:19 thread.c:1273:asic_status_monitor_thread: ERROR: chain 0 get hashrate_reg_counter 58, require 65, failed times 1: ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo oooxx xxxxx
2022-01-16 23:06:21 thread.c:1293:asic_status_monitor_thread: chain 0 can't get enough hashrate reg val for 14 times.
2022-01-16 23:06:21 thread.c:1273:asic_status_monitor_thread: ERROR: chain 0 get hashrate_reg_counter 58, require 65, failed times 1: ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo oooxx xxxxx
2022-01-16 23:06:23 thread.c:1293:asic_status_monitor_thread: chain 0 can't get enough hashrate reg val for 15 times.
2022-01-16 23:06:23 thread.c:1273:asic_status_monitor_thread: ERROR: chain 0 get hashrate_reg_counter 58, require 65, failed times 1: ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo oooxx xxxxx
2022-01-16 23:06:25 thread.c:1293:asic_status_monitor_thread: chain 0 can't get enough hashrate reg val for 16 times.
2022-01-16 23:06:25 thread.c:1273:asic_status_monitor_thread: ERROR: chain 0 get hashrate_reg_counter 58, require 65, failed times 1: ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo oooxx xxxxx
2022-01-16 23:06:27 thread.c:1293:asic_status_monitor_thread: chain 0 can't get enough hashrate reg val for 17 times.
2022-01-16 23:06:27 thread.c:1273:asic_status_monitor_thread: ERROR: chain 0 get hashrate_reg_counter 58, require 65, failed times 1: ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo oooxx xxxxx
2022-01-16 23:06:29 thread.c:1293:asic_status_monitor_thread: chain 0 can't get enough hashrate reg val for 18 times.
2022-01-16 23:06:29 thread.c:1273:asic_status_monitor_thread: ERROR: chain 0 get hashrate_reg_counter 58, require 65, failed times 1: ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo oooxx xxxxx
2022-01-16 23:06:31 thread.c:1293:asic_status_monitor_thread: chain 0 can't get enough hashrate reg val for 19 times.
2022-01-16 23:06:31 thread.c:1273:asic_status_monitor_thread: ERROR: chain 0 get hashrate_reg_counter 58, require 65, failed times 1: ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo oooxx xxxxx
2022-01-16 23:06:33 thread.c:1293:asic_status_monitor_thread: chain 0 can't get enough hashrate reg val for 20 times.
2022-01-16 23:06:33 thread.c:1273:asic_status_monitor_thread: ERROR: chain 0 get hashrate_reg_counter 58, require 65, failed times 1: ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo oooxx xxxxx
2022-01-16 23:06:35 thread.c:1293:asic_status_monitor_thread: chain 0 can't get enough hashrate reg val for 21 times.
2022-01-16 23:06:35 thread.c:1273:asic_status_monitor_thread: ERROR: chain 0 get hashrate_reg_counter 58, require 65, failed times 1: ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo oooxx xxxxx
2022-01-16 23:06:37 thread.c:1293:asic_status_monitor_thread: chain 0 can't get enough hashrate reg val for 22 times.
2022-01-16 23:06:37 thread.c:1273:asic_status_monitor_thread: ERROR: chain 0 get hashrate_reg_counter 58, require 65, failed times 1: ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo oooxx xxxxx
2022-01-16 23:06:39 thread.c:1293:asic_status_monitor_thread: chain 0 can't get enough hashrate reg val for 23 times.
2022-01-16 23:06:39 thread.c:1273:asic_status_monitor_thread: ERROR: chain 0 get hashrate_reg_counter 58, require 65, failed times 1: ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo oooxx xxxxx
2022-01-16 23:06:41 thread.c:1293:asic_status_monitor_thread: chain 0 can't get enough hashrate reg val for 24 times.
2022-01-16 23:06:41 thread.c:1273:asic_status_monitor_thread: ERROR: chain 0 get hashrate_reg_counter 58, require 65, failed times 1: ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo oooxx xxxxx
2022-01-16 23:06:43 thread.c:1293:asic_status_monitor_thread: chain 0 can't get enough hashrate reg val for 25 times.
2022-01-16 23:06:43 thread.c:1273:asic_status_monitor_thread: ERROR: chain 0 get hashrate_reg_counter 58, require 65, failed times 1: ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo oooxx xxxxx
2022-01-16 23:06:45 thread.c:1293:asic_status_monitor_thread: chain 0 can't get enough hashrate reg val for 26 times.
2022-01-16 23:06:45 thread.c:1273:asic_status_monitor_thread: ERROR: chain 0 get hashrate_reg_counter 58, require 65, failed times 1: ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo oooxx xxxxx
2022-01-16 23:06:47 thread.c:1293:asic_status_monitor_thread: chain 0 can't get enough hashrate reg val for 27 times.
2022-01-16 23:06:47 thread.c:1273:asic_status_monitor_thread: ERROR: chain 0 get hashrate_reg_counter 58, require 65, failed times 1: ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo oooxx xxxxx
2022-01-16 23:06:49 thread.c:1293:asic_status_monitor_thread: chain 0 can't get enough hashrate reg val for 28 times.
2022-01-16 23:06:49 thread.c:1273:asic_status_monitor_thread: ERROR: chain 0 get hashrate_reg_counter 58, require 65, failed times 1: ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo oooxx xxxxx
2022-01-16 23:06:51 thread.c:1293:asic_status_monitor_thread: chain 0 can't get enough hashrate reg val for 29 times.
2022-01-16 23:06:51 thread.c:1297:asic_status_monitor_thread: chain 0 can't get enough hashrate reg val for 30 times, power off.
2022-01-16 23:06:52 frequency.c:205:get_ideal_hash_rate_GH: ideal_hash_rate = 24189
2022-01-16 23:06:52 frequency.c:223:get_sale_hash_rate_GH: sale_hash_rate = 22000
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: wndsnb on January 17, 2022, 01:03:31 AM
My question is do you think the problem with chain 2 is the capacitor that the 63rd chip? Would you do something different that re-soldering if you faced these errors?
I assume you're talking about one of the large electrolytic caps? I doubt it would cause the issue you are seeing. If it was one of the caps in the boost circuit that generates the 1.8V signal for the last voltage domain, maybe the regulator could go unstable, so that would mess up all the chips in the last voltage domain though. Also, just re-soldering those chips is a bit of a shot in the dark. The problem could be those chips, or the chips after, or sometimes even just another chip in the same voltage domain.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: Heathen23 on January 17, 2022, 03:41:19 AM
My question is do you think the problem with chain 2 is the capacitor that the 63rd chip? Would you do something different that re-soldering if you faced these errors?
I assume you're talking about one of the large electrolytic caps? I doubt it would cause the issue you are seeing. If it was one of the caps in the boost circuit that generates the 1.8V signal for the last voltage domain, maybe the regulator could go unstable, so that would mess up all the chips in the last voltage domain though. Also, just re-soldering those chips is a bit of a shot in the dark. The problem could be those chips, or the chips after, or sometimes even just another chip in the same voltage domain. Thanks wndsnb for responding. You are right. it is the large 330mf and 30v cap just besides, what I think is, the 63rd chip. Incidentally this board is finding only 62 chip. I encircled the cap and the 63rd chip in black oval in the picture that I borrowed from Zeus manual. https://imgur.com/a/RaQXtuS Another strange thing is after another reboot the error message changed a bit "Chain 2 only find 0 asic, will power off hash board 2" compared to last time "Chain 2 only find 62 asic, will power off hash board 2" So why did it find 62 Asic last time but 0 this time? Outside temperature is sub zero after a round of snow and I don't have insulation / heating in the place where the miner is so excess temperature is ruled out. This is the board where I reinstated the capacitor. i agree with you that the problem may be in chip # 62, 61, 63 or in the entire last column 61 through 65 which is the voltage domain if I am not wrong. I agree that just re-soldering is a shot in the dark but I lack expertise and probably equipment to do anything more. Chain 0 is now saying "chain 0 get hashrate_reg_counter 63, require 65, failed times 1: ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo xxooo" compared to last time chain 0 get hashrate_reg_counter 58, require 65, failed times 1: ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo oooxx xxxxx" This board seem to have done slightly better. If I am reading it right last time chips #59 through 65 failed but this time only chip#61 and 62 failed. Am I reading it right?
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: wndsnb on January 17, 2022, 04:55:15 PM
The chip count is only ever a clue and does often change with multiple attempts on a bad board. A lot of times the core problem is a resistive or flaky connection that can change with temperature. So you might get 0, or a number close to the actual problem area, or a random number. domain if I am not wrong. I agree that just re-soldering is a shot in the dark but I lack expertise and probably equipment to do anything more.
Chain 0 is now saying
"chain 0 get hashrate_reg_counter 63, require 65, failed times 1: ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo xxooo"
compared to last time
chain 0 get hashrate_reg_counter 58, require 65, failed times 1: ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo oooxx xxxxx"
I don't know the exact meaning/format last part of these lines. The chips on the board are all connected in series in a chain, so to get a message from chip 65, it gets forwarded through every other chip on the board. If chip 63 has a problem, it normally won't forward messages from the chips further down the chain and you end up with a count of 62. So I don't know if that "xxooo" on the last domain is just ordered backwards so the two x chips are actually 65 and 64, or if the chips are both forwarding messages correctly but not responding with their own messages correctly.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: Heathen23 on January 17, 2022, 10:43:47 PM
I rebooted one more time as only one hash-board was running. Now it finds all asics on all boards but shuts down due to votage being different!. 2022-01-17 22:27:12 driver-btm-api.c:1134:check_asic_number_with_power_on: Chain[0]: find 65 asic, times 0
2022-01-17 22:27:23 driver-btm-api.c:1134:check_asic_number_with_power_on: Chain[1]: find 65 asic, times 0
2022-01-17 22:27:34 driver-btm-api.c:1134:check_asic_number_with_power_on: Chain[2]: find 65 asic, times 0
-----------------------------------
2022-01-17 22:27:44 voltage[0] = 1920
2022-01-17 22:27:44 voltage[1] = 1920
2022-01-17 22:27:44 voltage[2] = 1960
2022-01-17 22:27:44 Voltage are different. Will exit.
2022-01-17 22:27:44 driver-btm-api.c:222:set_miner_status: ERROR_SOC_INIT
2022-01-17 22:27:44 driver-btm-api.c:156:stop_mining: stop mining: soc init failed!
2022-01-17 22:27:44 thread.c:1403:cancel_read_nonce_reg_thread: cancel thread
2022-01-17 22:27:44 driver-btm-api.c:141:killall_hashboard: ****power off hashboard**** But voltages were 1920 on chain0 and chain1 even when it did not find all asics on chain2 and it started hashing with chain0 and chain1. Why this time despite finding all asics in chain2 it is shutting down Chain0 and chain1 just because chqin2 has a different voltage? Is this the real problem? Any clues about what to do? Chain2 is where I re-soldered the capacitor. Full log below:
Booting Linux on physical CPU 0x0
Linux version 4.6.0-xilinx-gff8137b-dirty (lzq@armdev2) (gcc version 4.8.3 20140320 (prerelease) (Sourcery CodeBench Lite 2014.05-23) ) #25 SMP PREEMPT Fri Nov 23 15:30:52 CST 2018
CPU: ARMv7 Processor [413fc090] revision 0 (ARMv7), cr=18c5387d
CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
Machine model: Xilinx Zynq
cma: Reserved 16 MiB at 0x0e000000
Memory policy: Data cache writealloc
On node 0 totalpages: 61440
free_area_init_node: node 0, pgdat c0b39280, node_mem_map cde10000
Normal zone: 480 pages used for memmap
Normal zone: 0 pages reserved
Normal zone: 61440 pages, LIFO batch:15
percpu: Embedded 12 pages/cpu @cddf1000 s19776 r8192 d21184 u49152
pcpu-alloc: s19776 r8192 d21184 u49152 alloc=12*4096
pcpu-alloc: [0] 0 [0] 1
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 60960
Kernel command line: mem=240M console=ttyPS0,115200 ramdisk_size=33554432 root=/dev/ram rw earlyprintk
PID hash table entries: 1024 (order: 0, 4096 bytes)
Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
Memory: 203316K/245760K available (6345K kernel code, 231K rwdata, 1896K rodata, 1024K init, 223K bss, 26060K reserved, 16384K cma-reserved, 0K highmem)
Virtual kernel memory layout:
vector : 0xffff0000 - 0xffff1000 ( 4 kB)
fixmap : 0xffc00000 - 0xfff00000 (3072 kB)
vmalloc : 0xcf800000 - 0xff800000 ( 768 MB)
lowmem : 0xc0000000 - 0xcf000000 ( 240 MB)
pkmap : 0xbfe00000 - 0xc0000000 ( 2 MB)
modules : 0xbf000000 - 0xbfe00000 ( 14 MB)
.text : 0xc0008000 - 0xc090c424 (9234 kB)
.init : 0xc0a00000 - 0xc0b00000 (1024 kB)
.data : 0xc0b00000 - 0xc0b39fe0 ( 232 kB)
.bss : 0xc0b39fe0 - 0xc0b71c28 ( 224 kB)
Preemptible hierarchical RCU implementation.
Build-time adjustment of leaf fanout to 32.
RCU restricting CPUs from NR_CPUS=4 to nr_cpu_ids=2.
RCU: Adjusting geometry for rcu_fanout_leaf=32, nr_cpu_ids=2
NR_IRQS:16 nr_irqs:16 16
efuse mapped to cf800000
ps7-slcr mapped to cf802000
L2C: platform modifies aux control register: 0x72360000 -> 0x72760000
L2C: DT/platform modifies aux control register: 0x72360000 -> 0x72760000
L2C-310 erratum 769419 enabled
L2C-310 enabling early BRESP for Cortex-A9
L2C-310 full line of zeros enabled for Cortex-A9
L2C-310 ID prefetch enabled, offset 1 lines
L2C-310 dynamic clock gating enabled, standby mode enabled
L2C-310 cache controller enabled, 8 ways, 512 kB
L2C-310: CACHE_ID 0x410000c8, AUX_CTRL 0x76760001
zynq_clock_init: clkc starts at cf802100
Zynq clock init
sched_clock: 64 bits at 333MHz, resolution 3ns, wraps every 4398046511103ns
clocksource: arm_global_timer: mask: 0xffffffffffffffff max_cycles: 0x4ce07af025, max_idle_ns: 440795209040 ns
Switching to timer-based delay loop, resolution 3ns
clocksource: ttc_clocksource: mask: 0xffff max_cycles: 0xffff, max_idle_ns: 537538477 ns
ps7-ttc #0 at cf80a000, irq=18
Console: colour dummy device 80x30
Calibrating delay loop (skipped), value calculated using timer frequency.. 666.66 BogoMIPS (lpj=3333333)
pid_max: default: 32768 minimum: 301
Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
CPU: Testing write buffer coherency: ok
CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
Setting up static identity map for 0x100000 - 0x100058
CPU1: failed to boot: -1
Brought up 1 CPUs
SMP: Total of 1 processors activated (666.66 BogoMIPS).
CPU: All CPU(s) started in SVC mode.
devtmpfs: initialized
VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4
clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
pinctrl core: initialized pinctrl subsystem
NET: Registered protocol family 16
DMA: preallocated 256 KiB pool for atomic coherent allocations
cpuidle: using governor menu
hw-breakpoint: found 5 (+1 reserved) breakpoint and 1 watchpoint registers.
hw-breakpoint: maximum watchpoint size is 4 bytes.
zynq-ocm f800c000.ps7-ocmc: ZYNQ OCM pool: 256 KiB @ 0xcf880000
vgaarb: loaded
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
media: Linux media interface: v0.10
Linux video capture interface: v2.00
pps_core: LinuxPPS API ver. 1 registered
pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
PTP clock support registered
EDAC MC: Ver: 3.0.0
Advanced Linux Sound Architecture Driver Initialized.
clocksource: Switched to clocksource arm_global_timer
NET: Registered protocol family 2
TCP established hash table entries: 2048 (order: 1, 8192 bytes)
TCP bind hash table entries: 2048 (order: 2, 16384 bytes)
TCP: Hash tables configured (established 2048 bind 2048)
UDP hash table entries: 256 (order: 1, 8192 bytes)
UDP-Lite hash table entries: 256 (order: 1, 8192 bytes)
NET: Registered protocol family 1
RPC: Registered named UNIX socket transport module.
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
PCI: CLS 0 bytes, default 64
Trying to unpack rootfs image as initramfs...
rootfs image is not initramfs (no cpio magic); looks like an initrd
Freeing initrd memory: 13020K (cce49000 - cdb00000)
hw perfevents: enabled with armv7_cortex_a9 PMU driver, 7 counters available
futex hash table entries: 512 (order: 3, 32768 bytes)
workingset: timestamp_bits=28 max_order=16 bucket_order=0
jffs2: version 2.2. (NAND) (SUMMARY) © 2001-2006 Red Hat, Inc.
io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered (default)
dma-pl330 f8003000.ps7-dma: Loaded driver for PL330 DMAC-241330
dma-pl330 f8003000.ps7-dma: DBUFF-128x8bytes Num_Chans-8 Num_Peri-4 Num_Events-16
e0000000.serial: ttyPS0 at MMIO 0xe0000000 (irq = 158, base_baud = 6249999) is a xuartps
console [ttyPS0] enabled
xdevcfg f8007000.ps7-dev-cfg: ioremap 0xf8007000 to cf86e000
[drm] Initialized drm 1.1.0 20060810
brd: module loaded
loop: module loaded
CAN device driver interface
gpiod_set_value: invalid GPIO
libphy: MACB_mii_bus: probed
macb e000b000.ethernet eth0: Cadence GEM rev 0x00020118 at 0xe000b000 irq 31 (00:0a:35:00:00:00)
Generic PHY e000b000.etherne:00: attached PHY driver [Generic PHY] (mii_bus:phy_addr=e000b000.etherne:00, irq=-1)
e1000e: Intel(R) PRO/1000 Network Driver - 3.2.6-k
e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
ehci-pci: EHCI PCI platform driver
usbcore: registered new interface driver usb-storage
mousedev: PS/2 mouse device common for all mice
i2c /dev entries driver
Xilinx Zynq CpuIdle Driver started
sdhci: Secure Digital Host Controller Interface driver
sdhci: Copyright(c) Pierre Ossman
sdhci-pltfm: SDHCI platform and OF driver helper
mmc0: SDHCI controller on e0100000.ps7-sdio [e0100000.ps7-sdio] using ADMA
ledtrig-cpu: registered to indicate activity on CPUs
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
nand: device found, Manufacturer ID: 0x2c, Chip ID: 0xda
nand: Micron MT29F2G08ABAEAWP
nand: 256 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 64
nand: WARNING: pl35x-nand: the ECC used on your system is too weak compared to the one required by the NAND chip
Bad block table found at page 131008, version 0x01
Bad block table found at page 130944, version 0x01
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: 1/0, WL threshold: 4096, image sequence number: 11906131
ubi0: available PEBs: 0, total reserved PEBs: 64, PEBs reserved for bad PEB handling: 40
ubi0: background thread "ubi_bgt0d" started, PID 708
UBIFS (ubi0:0): background thread "ubifs_bgt0_0" started, PID 711
UBIFS (ubi0:0): UBIFS: mounted UBI device 0, volume 0, name "configs"
UBIFS (ubi0:0): LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
UBIFS (ubi0:0): FS size: 1396736 bytes (1 MiB, 11 LEBs), journal size 888833 bytes (0 MiB, 5 LEBs)
UBIFS (ubi0:0): reserved for root: 65970 bytes (64 KiB)
UBIFS (ubi0:0): media format: w4/r0 (latest is w4/r0), UUID 5C61C316-5FAD-4CFA-B280-2AFAE13C9D72, 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: 2/0, WL threshold: 4096, image sequence number: 169213079
ubi1: available PEBs: 0, total reserved PEBs: 1020, PEBs reserved for bad PEB handling: 36
ubi1: background thread "ubi_bgt1d" started, PID 720
UBIFS (ubi1:0): background thread "ubifs_bgt1_0" started, PID 723
UBIFS (ubi1:0): UBIFS: mounted UBI device 1, volume 0, name "reserve1"
UBIFS (ubi1:0): LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
UBIFS (ubi1:0): FS size: 123039744 bytes (117 MiB, 969 LEBs), journal size 6221824 bytes (5 MiB, 49 LEBs)
UBIFS (ubi1:0): reserved for root: 4952683 bytes (4836 KiB)
UBIFS (ubi1:0): media format: w4/r0 (latest is w4/r0), UUID 6FB1BE46-BF1C-4F4C-9CA2-2F82009B82B4, 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 = 0xb023
In fpga mem driver!
request_mem_region OK!
fpga mem virtual address is 0xd2000000
2022-01-17 22:25:26 driver-btm-api.c:779:init_freq_mode: This is scan-user version
2022-01-17 22:25:26 driver-btm-api.c:2451:bitmain_soc_init: opt_multi_version = 1
2022-01-17 22:25:26 driver-btm-api.c:2452:bitmain_soc_init: opt_bitmain_ab = 1
2022-01-17 22:25:26 driver-btm-api.c:2453:bitmain_soc_init: opt_bitmain_work_mode = 0
2022-01-17 22:25:26 driver-btm-api.c:2454:bitmain_soc_init: Miner compile time: Tue Jun 2 10:31:07 CST 2020 type: Antminer S17+
2022-01-17 22:25:26 driver-btm-api.c:2455:bitmain_soc_init: commit version: 1ca50a5 2020-06-01 18:51:22, build by: lol 2020-06-02 10:37:21
2022-01-17 22:25:26 driver-btm-api.c:2083:show_sn: len:16, 8034b4442b104814
2022-01-17 22:25:26 driver-btm-api.c:2461:bitmain_soc_init: show sn return 1
2022-01-17 22:25:26 driver-btm-api.c:2103:handle_sn_for_factory_mode: show sn return 1
2022-01-17 22:25:26 driver-btm-api.c:2141:handle_sn_for_factory_mode: read sn success, 8034b4442b104814
2022-01-17 22:25:26 fan.c:284:front_fan_power_on: Note: front fan is power on!
2022-01-17 22:25:26 fan.c:296:rear_fan_power_on: Note: rear fan is power on!
2022-01-17 22:25:26 driver-btm-api.c:1314:miner_device_init: Detect 256MB control board of XILINX
2022-01-17 22:25:26 driver-btm-api.c:1255:init_fan_parameter: fan_eft : 0 fan_pwm : 0
2022-01-17 22:25:32 driver-btm-api.c:1239:init_miner_version: miner ID : 8034b4442b104814
2022-01-17 22:25:32 driver-btm-api.c:1245:init_miner_version: FPGA Version = 0xB023
2022-01-17 22:25:37 driver-btm-api.c:837:get_product_id: product_id[0] = 0
2022-01-17 22:25:37 driver-btm-api.c:837:get_product_id: product_id[1] = 0
2022-01-17 22:25:37 driver-btm-api.c:837:get_product_id: product_id[2] = 0
2022-01-17 22:25:37 driver-btm-api.c:2234:update_conf_by_power_feedback: Power feedback is disabled
2022-01-17 22:25:37 driver-btm-api.c:2202:get_calibration_voltage: calibration voltage flag is error data.
2022-01-17 22:25:37 driver-btm-api.c:2268:update_conf_by_power_feedback: Note: no calibration voltage, default diff = 0
2022-01-17 22:25:37 frequency.c:1457:adjust_higer_max_vol_table: adjust_higer_max_vol_table, adjust_vol = 0
2022-01-17 22:25:37 thread.c:1363:create_read_nonce_reg_thread: create thread
2022-01-17 22:25:43 driver-btm-api.c:1239:init_miner_version: miner ID : 8034b4442b104814
2022-01-17 22:25:43 driver-btm-api.c:1245:init_miner_version: FPGA Version = 0xB023
2022-01-17 22:25:49 driver-btm-api.c:837:get_product_id: product_id[0] = 0
2022-01-17 22:25:49 driver-btm-api.c:837:get_product_id: product_id[1] = 0
2022-01-17 22:25:49 driver-btm-api.c:837:get_product_id: product_id[2] = 0
2022-01-17 22:25:49 driver-btm-api.c:792:_set_project_type: project:0
2022-01-17 22:25:49 driver-btm-api.c:813:_set_project_type: Project type: Antminer S17+
2022-01-17 22:25:49 driver-btm-api.c:824:dump_pcb_bom_version: Chain [0] PCB Version: 0x0100
2022-01-17 22:25:49 driver-btm-api.c:825:dump_pcb_bom_version: Chain [0] BOM Version: 0x0100
2022-01-17 22:25:49 driver-btm-api.c:824:dump_pcb_bom_version: Chain [1] PCB Version: 0x0100
2022-01-17 22:25:49 driver-btm-api.c:825:dump_pcb_bom_version: Chain [1] BOM Version: 0x0100
2022-01-17 22:25:49 driver-btm-api.c:824:dump_pcb_bom_version: Chain [2] PCB Version: 0x0100
2022-01-17 22:25:49 driver-btm-api.c:825:dump_pcb_bom_version: Chain [2] BOM Version: 0x0100
2022-01-17 22:25:51 driver-btm-api.c:2372:bitmain_board_init: Fan check passed.
2022-01-17 22:25:52 board.c:36:jump_and_app_check_restore_pic: chain[0] PIC jump to app
2022-01-17 22:25:54 board.c:40:jump_and_app_check_restore_pic: Check chain[0] PIC fw version=0x88
2022-01-17 22:25:55 board.c:36:jump_and_app_check_restore_pic: chain[1] PIC jump to app
2022-01-17 22:25:57 board.c:40:jump_and_app_check_restore_pic: Check chain[1] PIC fw version=0x88
2022-01-17 22:25:58 board.c:36:jump_and_app_check_restore_pic: chain[2] PIC jump to app
2022-01-17 22:26:00 board.c:40:jump_and_app_check_restore_pic: Check chain[2] PIC fw version=0x88
2022-01-17 22:26:00 thread.c:1358:create_pic_heart_beat_thread: create thread
2022-01-17 22:26:00 power_api.c:213:power_init: Power init:
2022-01-17 22:26:00 power_api.c:214:power_init: current_voltage_raw = 0
2022-01-17 22:26:00 power_api.c:215:power_init: highest_voltage_raw = 2100
2022-01-17 22:26:00 power_api.c:216:power_init: working_voltage_raw = 1950
2022-01-17 22:26:00 power_api.c:217:power_init: higher_voltage_raw = 2040
2022-01-17 22:26:00 power_api.c:218:power_init: check_asic_voltage_raw = 2100
2022-01-17 22:26:00 driver-btm-api.c:2382:bitmain_board_init: Enter 30s sleep to make sure power release finish.
2022-01-17 22:26:00 power_api.c:186:power_off: init gpio907
2022-01-17 22:26:32 power_api.c:324:set_to_highest_voltage_by_steps: Set to voltage raw 2100, step by step.
2022-01-17 22:26:58 power_api.c:85:check_voltage_multi: retry time: 0
2022-01-17 22:26:59 power_api.c:40:_get_avg_voltage: chain = 0, voltage = 21.094872
2022-01-17 22:27:00 power_api.c:40:_get_avg_voltage: chain = 1, voltage = 21.124679
2022-01-17 22:27:01 power_api.c:40:_get_avg_voltage: chain = 2, voltage = 21.295630
2022-01-17 22:27:01 power_api.c:53:_get_avg_voltage: average_voltage = 21.171727
2022-01-17 22:27:01 power_api.c:71:check_voltage: target_vol = 21.00, actural_vol = 21.17, check voltage passed.
2022-01-17 22:27:01 uart.c:72:set_baud: set fpga_baud to 115200
2022-01-17 22:27:12 driver-btm-api.c:1134:check_asic_number_with_power_on: Chain[0]: find 65 asic, times 0
2022-01-17 22:27:23 driver-btm-api.c:1134:check_asic_number_with_power_on: Chain[1]: find 65 asic, times 0
2022-01-17 22:27:34 driver-btm-api.c:1134:check_asic_number_with_power_on: Chain[2]: find 65 asic, times 0
2022-01-17 22:27:43 driver-hash-chip.c:266:set_uart_relay: set uart relay to 0x330003
2022-01-17 22:27:43 driver-btm-api.c:435:set_order_clock: chain[0]: set order clock, stragegy 3
2022-01-17 22:27:43 driver-btm-api.c:435:set_order_clock: chain[1]: set order clock, stragegy 3
2022-01-17 22:27:43 driver-btm-api.c:435:set_order_clock: chain[2]: set order clock, stragegy 3
2022-01-17 22:27:43 driver-hash-chip.c:502:set_clock_delay_control: core_data = 0x34
2022-01-17 22:27:43 driver-btm-api.c:1892:check_clock_counter: freq 50 clock_counter_limit 6
2022-01-17 22:27:44 voltage[0] = 1920
2022-01-17 22:27:44 voltage[1] = 1920
2022-01-17 22:27:44 voltage[2] = 1960
2022-01-17 22:27:44 Voltage are different. Will exit.
2022-01-17 22:27:44 driver-btm-api.c:222:set_miner_status: ERROR_SOC_INIT
2022-01-17 22:27:44 driver-btm-api.c:156:stop_mining: stop mining: soc init failed!
2022-01-17 22:27:44 thread.c:1403:cancel_read_nonce_reg_thread: cancel thread
2022-01-17 22:27:44 driver-btm-api.c:141:killall_hashboard: ****power off hashboard****
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: wndsnb on January 18, 2022, 12:04:47 AM
Looks like chain[2] was originally from a different miner. That voltage is the setting in the eeprom on the hashboard. The miner will not operate if the 3 hashboards don't have the same voltage setting. So you'll either need to buy a programmer to burn the eeprom with compatible settings or use aftermarket firmware.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: Saskfarmer on January 18, 2022, 03:22:53 AM
Those that have both S17 Pro’s and S17+ At the same money for each which would you prefer? I just finished going through the first lot of 50 of S17 pro’s and honestly I’m pleased how well they survived the trip from China. Have the same deal lined up for S17+’s but for some reason I think they have way more failures.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: DwarfNo3 on January 18, 2022, 02:04:22 PM
Thank you wndsnb. I tried to give you merit or something but I'm not very familiar with forums.
I got too confused about the voltage I thought it was something else.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: Heathen23 on January 18, 2022, 02:46:21 PM
Looks like chain[2] was originally from a different miner. That voltage is the setting in the eeprom on the hashboard. The miner will not operate if the 3 hashboards don't have the same voltage setting. So you'll either need to buy a programmer to burn the eeprom with compatible settings or use aftermarket firmware.
Thank you so much for helping me again. You are absolutely correct. I bought this miner 2nd hand and it came with bosminer. It ran fine for few months. When it started to give trouble I switched to stock firmware to troubleshoot. I believe eeprom has a finite reprogramming life. May be the previous owner has already exhausted that. So he was using bosminer to get away with it. It is also possible that I misplaced this 3rd board from another s17+ miner while cleaning or trouble shooting. In this S17+ I have boards with 1920, 1920 and 1960. The board with 1960 being kicked out. In another s17+ cards are running with stock firmware with voltages 1940 & 1960. So it looks like a difference of 40 is unacceptable but a difference of 20 is acceptable? I am thinking if I exchange this board with the one having 1940 in the other s17+ then may be it will run with 1960 there and may be the board with 1940 will be acceptable in this s17+ where others boards are at 1920. I will do that and report back after the day job. I am also thinking about trying vniche and awesome miner if they are better at troubleshooting. While bosminer works fine for running them efficiently it is not good for trouble shooting or I am not good enough to trouble shoot with bosminer. Really appreciate your insight and guidance wndsnb! I gave you a few merits. Being a newbie I don't have much to give.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: wndsnb on January 18, 2022, 06:27:17 PM
Aftermarket firmware like braiins will just ignore the voltage setting. The previous owner probably swapped out a dead hashboard and used the aftermarket firmware to get it to run.
That's interesting that you have one with different voltages that work, I never tested to see if there was an acceptable difference factory firmware would run with. Yeah, see if the 1940 board works with the 1920 boards, I'm interested in seeing the results.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: Heathen23 on January 19, 2022, 12:55:19 AM
I pulled in the board with 1940 voltage but it does not work with the other 2. I am still getting the same error 2022-01-19 00:48:41 voltage[0] = 1920 2022-01-19 00:48:41 voltage[1] = 1920 2022-01-19 00:48:41 voltage[2] = 1940 2022-01-19 00:48:41 Voltage are different. Will exit. 2022-01-19 00:48:41 driver-btm-api.c:222:set_miner_status: ERROR_SOC_INIT 2022-01-19 00:48:41 driver-btm-api.c:156:stop_mining: stop mining: soc init failed! 2022-01-19 00:48:41 thread.c:1403:cancel_read_nonce_reg_thread: cancel thread 2022-01-19 00:48:41 driver-btm-api.c:141:killall_hashboard: ****power off hashboard**** But I think I get this error only when all 3 boards are attempted to be run that is they all detect 65 ASIC. It is not an issue when only 2 boards are running for example when 1 of them finds 0 asic, it tries to start the other two. Booting Linux on physical CPU 0x0
Linux version 4.6.0-xilinx-gff8137b-dirty (lzq@armdev2) (gcc version 4.8.3 20140320 (prerelease) (Sourcery CodeBench Lite 2014.05-23) ) #25 SMP PREEMPT Fri Nov 23 15:30:52 CST 2018
CPU: ARMv7 Processor [413fc090] revision 0 (ARMv7), cr=18c5387d
CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
Machine model: Xilinx Zynq
cma: Reserved 16 MiB at 0x0e000000
Memory policy: Data cache writealloc
On node 0 totalpages: 61440
free_area_init_node: node 0, pgdat c0b39280, node_mem_map cde10000
Normal zone: 480 pages used for memmap
Normal zone: 0 pages reserved
Normal zone: 61440 pages, LIFO batch:15
percpu: Embedded 12 pages/cpu @cddf1000 s19776 r8192 d21184 u49152
pcpu-alloc: s19776 r8192 d21184 u49152 alloc=12*4096
pcpu-alloc: [0] 0 [0] 1
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 60960
Kernel command line: mem=240M console=ttyPS0,115200 ramdisk_size=33554432 root=/dev/ram rw earlyprintk
PID hash table entries: 1024 (order: 0, 4096 bytes)
Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
Memory: 203316K/245760K available (6345K kernel code, 231K rwdata, 1896K rodata, 1024K init, 223K bss, 26060K reserved, 16384K cma-reserved, 0K highmem)
Virtual kernel memory layout:
vector : 0xffff0000 - 0xffff1000 ( 4 kB)
fixmap : 0xffc00000 - 0xfff00000 (3072 kB)
vmalloc : 0xcf800000 - 0xff800000 ( 768 MB)
lowmem : 0xc0000000 - 0xcf000000 ( 240 MB)
pkmap : 0xbfe00000 - 0xc0000000 ( 2 MB)
modules : 0xbf000000 - 0xbfe00000 ( 14 MB)
.text : 0xc0008000 - 0xc090c424 (9234 kB)
.init : 0xc0a00000 - 0xc0b00000 (1024 kB)
.data : 0xc0b00000 - 0xc0b39fe0 ( 232 kB)
.bss : 0xc0b39fe0 - 0xc0b71c28 ( 224 kB)
Preemptible hierarchical RCU implementation.
Build-time adjustment of leaf fanout to 32.
RCU restricting CPUs from NR_CPUS=4 to nr_cpu_ids=2.
RCU: Adjusting geometry for rcu_fanout_leaf=32, nr_cpu_ids=2
NR_IRQS:16 nr_irqs:16 16
efuse mapped to cf800000
ps7-slcr mapped to cf802000
L2C: platform modifies aux control register: 0x72360000 -> 0x72760000
L2C: DT/platform modifies aux control register: 0x72360000 -> 0x72760000
L2C-310 erratum 769419 enabled
L2C-310 enabling early BRESP for Cortex-A9
L2C-310 full line of zeros enabled for Cortex-A9
L2C-310 ID prefetch enabled, offset 1 lines
L2C-310 dynamic clock gating enabled, standby mode enabled
L2C-310 cache controller enabled, 8 ways, 512 kB
L2C-310: CACHE_ID 0x410000c8, AUX_CTRL 0x76760001
zynq_clock_init: clkc starts at cf802100
Zynq clock init
sched_clock: 64 bits at 333MHz, resolution 3ns, wraps every 4398046511103ns
clocksource: arm_global_timer: mask: 0xffffffffffffffff max_cycles: 0x4ce07af025, max_idle_ns: 440795209040 ns
Switching to timer-based delay loop, resolution 3ns
clocksource: ttc_clocksource: mask: 0xffff max_cycles: 0xffff, max_idle_ns: 537538477 ns
ps7-ttc #0 at cf80a000, irq=18
Console: colour dummy device 80x30
Calibrating delay loop (skipped), value calculated using timer frequency.. 666.66 BogoMIPS (lpj=3333333)
pid_max: default: 32768 minimum: 301
Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
CPU: Testing write buffer coherency: ok
CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
Setting up static identity map for 0x100000 - 0x100058
CPU1: failed to boot: -1
Brought up 1 CPUs
SMP: Total of 1 processors activated (666.66 BogoMIPS).
CPU: All CPU(s) started in SVC mode.
devtmpfs: initialized
VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4
clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
pinctrl core: initialized pinctrl subsystem
NET: Registered protocol family 16
DMA: preallocated 256 KiB pool for atomic coherent allocations
cpuidle: using governor menu
hw-breakpoint: found 5 (+1 reserved) breakpoint and 1 watchpoint registers.
hw-breakpoint: maximum watchpoint size is 4 bytes.
zynq-ocm f800c000.ps7-ocmc: ZYNQ OCM pool: 256 KiB @ 0xcf880000
vgaarb: loaded
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
media: Linux media interface: v0.10
Linux video capture interface: v2.00
pps_core: LinuxPPS API ver. 1 registered
pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
PTP clock support registered
EDAC MC: Ver: 3.0.0
Advanced Linux Sound Architecture Driver Initialized.
clocksource: Switched to clocksource arm_global_timer
NET: Registered protocol family 2
TCP established hash table entries: 2048 (order: 1, 8192 bytes)
TCP bind hash table entries: 2048 (order: 2, 16384 bytes)
TCP: Hash tables configured (established 2048 bind 2048)
UDP hash table entries: 256 (order: 1, 8192 bytes)
UDP-Lite hash table entries: 256 (order: 1, 8192 bytes)
NET: Registered protocol family 1
RPC: Registered named UNIX socket transport module.
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
PCI: CLS 0 bytes, default 64
Trying to unpack rootfs image as initramfs...
rootfs image is not initramfs (no cpio magic); looks like an initrd
Freeing initrd memory: 13020K (cce49000 - cdb00000)
hw perfevents: enabled with armv7_cortex_a9 PMU driver, 7 counters available
futex hash table entries: 512 (order: 3, 32768 bytes)
workingset: timestamp_bits=28 max_order=16 bucket_order=0
jffs2: version 2.2. (NAND) (SUMMARY) © 2001-2006 Red Hat, Inc.
io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered (default)
dma-pl330 f8003000.ps7-dma: Loaded driver for PL330 DMAC-241330
dma-pl330 f8003000.ps7-dma: DBUFF-128x8bytes Num_Chans-8 Num_Peri-4 Num_Events-16
e0000000.serial: ttyPS0 at MMIO 0xe0000000 (irq = 158, base_baud = 6249999) is a xuartps
console [ttyPS0] enabled
xdevcfg f8007000.ps7-dev-cfg: ioremap 0xf8007000 to cf86e000
[drm] Initialized drm 1.1.0 20060810
brd: module loaded
loop: module loaded
CAN device driver interface
gpiod_set_value: invalid GPIO
libphy: MACB_mii_bus: probed
macb e000b000.ethernet eth0: Cadence GEM rev 0x00020118 at 0xe000b000 irq 31 (00:0a:35:00:00:00)
Generic PHY e000b000.etherne:00: attached PHY driver [Generic PHY] (mii_bus:phy_addr=e000b000.etherne:00, irq=-1)
e1000e: Intel(R) PRO/1000 Network Driver - 3.2.6-k
e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
ehci-pci: EHCI PCI platform driver
usbcore: registered new interface driver usb-storage
mousedev: PS/2 mouse device common for all mice
i2c /dev entries driver
Xilinx Zynq CpuIdle Driver started
sdhci: Secure Digital Host Controller Interface driver
sdhci: Copyright(c) Pierre Ossman
sdhci-pltfm: SDHCI platform and OF driver helper
mmc0: SDHCI controller on e0100000.ps7-sdio [e0100000.ps7-sdio] using ADMA
ledtrig-cpu: registered to indicate activity on CPUs
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
nand: device found, Manufacturer ID: 0x2c, Chip ID: 0xda
nand: Micron MT29F2G08ABAEAWP
nand: 256 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 64
nand: WARNING: pl35x-nand: the ECC used on your system is too weak compared to the one required by the NAND chip
Bad block table found at page 131008, version 0x01
Bad block table found at page 130944, version 0x01
6 ofpart partitions found on MTD device pl35x-nand
Creating 6 MTD partitions on "pl35x-nand":
0x000000000000-0x000002800000 : "BOOT.bin-env-dts-kernel"
0x000002800000-0x000004800000 : "ramfs"
0x000004800000-0x000005000000 : "configs"
0x000005000000-0x000006000000 : "reserve"
0x000006000000-0x000008000000 : "ramfs-bak"
0x000008000000-0x000010000000 : "reserve1"
NET: Registered protocol family 10
sit: IPv6 over IPv4 tunneling driver
NET: Registered protocol family 17
can: controller area network core (rev 20120528 abi 9)
NET: Registered protocol family 29
can: raw protocol (rev 20120528)
can: broadcast manager protocol (rev 20120528 t)
can: netlink gateway (rev 20130117) max_hops=1
zynq_pm_ioremap: no compatible node found for 'xlnx,zynq-ddrc-a05'
zynq_pm_late_init: Unable to map DDRC IO memory.
Registering SWP/SWPB emulation handler
hctosys: unable to open rtc device (rtc0)
ALSA device list:
No soundcards found.
RAMDISK: gzip image found at block 0
EXT4-fs (ram0): couldn't mount as ext3 due to feature incompatibilities
EXT4-fs (ram0): mounted filesystem without journal. Opts: (null)
VFS: Mounted root (ext4 filesystem) on device 1:0.
devtmpfs: mounted
Freeing unused kernel memory: 1024K (c0a00000 - c0b00000)
EXT4-fs (ram0): re-mounted. Opts: block_validity,delalloc,barrier,user_xattr
random: dd urandom read with 0 bits of entropy available
ubi0: attaching mtd2
ubi0: scanning is finished
ubi0: attached mtd2 (name "configs", size 8 MiB)
ubi0: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
ubi0: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
ubi0: VID header offset: 2048 (aligned 2048), data offset: 4096
ubi0: good PEBs: 64, bad PEBs: 0, corrupted PEBs: 0
ubi0: user volume: 1, internal volumes: 1, max. volumes count: 128
ubi0: max/mean erase counter: 2/0, WL threshold: 4096, image sequence number: 11906131
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 5C61C316-5FAD-4CFA-B280-2AFAE13C9D72, 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: 2/0, WL threshold: 4096, image sequence number: 169213079
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 6FB1BE46-BF1C-4F4C-9CA2-2F82009B82B4, 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 = 0xb023
In fpga mem driver!
request_mem_region OK!
fpga mem virtual address is 0xd2000000
random: nonblocking pool is initialized
2022-01-19 00:46:23 driver-btm-api.c:779:init_freq_mode: This is scan-user version
2022-01-19 00:46:23 driver-btm-api.c:2451:bitmain_soc_init: opt_multi_version = 1
2022-01-19 00:46:23 driver-btm-api.c:2452:bitmain_soc_init: opt_bitmain_ab = 1
2022-01-19 00:46:23 driver-btm-api.c:2453:bitmain_soc_init: opt_bitmain_work_mode = 0
2022-01-19 00:46:23 driver-btm-api.c:2454:bitmain_soc_init: Miner compile time: Tue Jun 2 10:31:07 CST 2020 type: Antminer S17+
2022-01-19 00:46:23 driver-btm-api.c:2455:bitmain_soc_init: commit version: 1ca50a5 2020-06-01 18:51:22, build by: lol 2020-06-02 10:37:21
2022-01-19 00:46:23 driver-btm-api.c:2083:show_sn: len:16, 8034b4442b104814
2022-01-19 00:46:23 driver-btm-api.c:2461:bitmain_soc_init: show sn return 1
2022-01-19 00:46:23 driver-btm-api.c:2103:handle_sn_for_factory_mode: show sn return 1
2022-01-19 00:46:23 driver-btm-api.c:2141:handle_sn_for_factory_mode: read sn success, 8034b4442b104814
2022-01-19 00:46:23 fan.c:284:front_fan_power_on: Note: front fan is power on!
2022-01-19 00:46:23 fan.c:296:rear_fan_power_on: Note: rear fan is power on!
2022-01-19 00:46:23 driver-btm-api.c:1314:miner_device_init: Detect 256MB control board of XILINX
2022-01-19 00:46:23 driver-btm-api.c:1255:init_fan_parameter: fan_eft : 0 fan_pwm : 0
2022-01-19 00:46:29 driver-btm-api.c:1239:init_miner_version: miner ID : 8034b4442b104814
2022-01-19 00:46:29 driver-btm-api.c:1245:init_miner_version: FPGA Version = 0xB023
2022-01-19 00:46:35 driver-btm-api.c:837:get_product_id: product_id[0] = 0
2022-01-19 00:46:35 driver-btm-api.c:837:get_product_id: product_id[1] = 0
2022-01-19 00:46:35 driver-btm-api.c:837:get_product_id: product_id[2] = 0
2022-01-19 00:46:35 driver-btm-api.c:2234:update_conf_by_power_feedback: Power feedback is disabled
2022-01-19 00:46:35 driver-btm-api.c:2202:get_calibration_voltage: calibration voltage flag is error data.
2022-01-19 00:46:35 driver-btm-api.c:2268:update_conf_by_power_feedback: Note: no calibration voltage, default diff = 0
2022-01-19 00:46:35 frequency.c:1457:adjust_higer_max_vol_table: adjust_higer_max_vol_table, adjust_vol = 0
2022-01-19 00:46:35 thread.c:1363:create_read_nonce_reg_thread: create thread
2022-01-19 00:46:41 driver-btm-api.c:1239:init_miner_version: miner ID : 8034b4442b104814
2022-01-19 00:46:41 driver-btm-api.c:1245:init_miner_version: FPGA Version = 0xB023
2022-01-19 00:46:46 driver-btm-api.c:837:get_product_id: product_id[0] = 0
2022-01-19 00:46:46 driver-btm-api.c:837:get_product_id: product_id[1] = 0
2022-01-19 00:46:46 driver-btm-api.c:837:get_product_id: product_id[2] = 0
2022-01-19 00:46:46 driver-btm-api.c:792:_set_project_type: project:0
2022-01-19 00:46:46 driver-btm-api.c:813:_set_project_type: Project type: Antminer S17+
2022-01-19 00:46:46 driver-btm-api.c:824:dump_pcb_bom_version: Chain [0] PCB Version: 0x0100
2022-01-19 00:46:46 driver-btm-api.c:825:dump_pcb_bom_version: Chain [0] BOM Version: 0x0100
2022-01-19 00:46:46 driver-btm-api.c:824:dump_pcb_bom_version: Chain [1] PCB Version: 0x0100
2022-01-19 00:46:46 driver-btm-api.c:825:dump_pcb_bom_version: Chain [1] BOM Version: 0x0100
2022-01-19 00:46:46 driver-btm-api.c:824:dump_pcb_bom_version: Chain [2] PCB Version: 0x0100
2022-01-19 00:46:46 driver-btm-api.c:825:dump_pcb_bom_version: Chain [2] BOM Version: 0x0100
2022-01-19 00:46:48 driver-btm-api.c:2372:bitmain_board_init: Fan check passed.
2022-01-19 00:46:49 board.c:36:jump_and_app_check_restore_pic: chain[0] PIC jump to app
2022-01-19 00:46:51 board.c:40:jump_and_app_check_restore_pic: Check chain[0] PIC fw version=0x88
2022-01-19 00:46:52 board.c:36:jump_and_app_check_restore_pic: chain[1] PIC jump to app
2022-01-19 00:46:54 board.c:40:jump_and_app_check_restore_pic: Check chain[1] PIC fw version=0x88
2022-01-19 00:46:55 board.c:36:jump_and_app_check_restore_pic: chain[2] PIC jump to app
2022-01-19 00:46:57 board.c:40:jump_and_app_check_restore_pic: Check chain[2] PIC fw version=0x88
2022-01-19 00:46:57 thread.c:1358:create_pic_heart_beat_thread: create thread
2022-01-19 00:46:57 power_api.c:213:power_init: Power init:
2022-01-19 00:46:57 power_api.c:214:power_init: current_voltage_raw = 0
2022-01-19 00:46:57 power_api.c:215:power_init: highest_voltage_raw = 2100
2022-01-19 00:46:57 power_api.c:216:power_init: working_voltage_raw = 1950
2022-01-19 00:46:57 power_api.c:217:power_init: higher_voltage_raw = 2040
2022-01-19 00:46:57 power_api.c:218:power_init: check_asic_voltage_raw = 2100
2022-01-19 00:46:57 driver-btm-api.c:2382:bitmain_board_init: Enter 30s sleep to make sure power release finish.
2022-01-19 00:47:29 power_api.c:324:set_to_highest_voltage_by_steps: Set to voltage raw 2100, step by step.
2022-01-19 00:47:55 power_api.c:85:check_voltage_multi: retry time: 0
2022-01-19 00:47:56 power_api.c:40:_get_avg_voltage: chain = 0, voltage = 21.094872
2022-01-19 00:47:57 power_api.c:40:_get_avg_voltage: chain = 1, voltage = 21.097560
2022-01-19 00:47:58 power_api.c:40:_get_avg_voltage: chain = 2, voltage = 21.170731
2022-01-19 00:47:58 power_api.c:53:_get_avg_voltage: average_voltage = 21.121054
2022-01-19 00:47:58 power_api.c:71:check_voltage: target_vol = 21.00, actural_vol = 21.12, check voltage passed.
2022-01-19 00:47:58 uart.c:72:set_baud: set fpga_baud to 115200
2022-01-19 00:48:10 driver-btm-api.c:1134:check_asic_number_with_power_on: Chain[0]: find 65 asic, times 0
2022-01-19 00:48:21 driver-btm-api.c:1134:check_asic_number_with_power_on: Chain[1]: find 65 asic, times 0
2022-01-19 00:48:32 driver-btm-api.c:1134:check_asic_number_with_power_on: Chain[2]: find 65 asic, times 0
2022-01-19 00:48:40 driver-hash-chip.c:266:set_uart_relay: set uart relay to 0x330003
2022-01-19 00:48:40 driver-btm-api.c:435:set_order_clock: chain[0]: set order clock, stragegy 3
2022-01-19 00:48:40 driver-btm-api.c:435:set_order_clock: chain[1]: set order clock, stragegy 3
2022-01-19 00:48:40 driver-btm-api.c:435:set_order_clock: chain[2]: set order clock, stragegy 3
2022-01-19 00:48:41 driver-hash-chip.c:502:set_clock_delay_control: core_data = 0x34
2022-01-19 00:48:41 driver-btm-api.c:1892:check_clock_counter: freq 50 clock_counter_limit 6
2022-01-19 00:48:41 voltage[0] = 1920
2022-01-19 00:48:41 voltage[1] = 1920
2022-01-19 00:48:41 voltage[2] = 1940
2022-01-19 00:48:41 Voltage are different. Will exit.
2022-01-19 00:48:41 driver-btm-api.c:222:set_miner_status: ERROR_SOC_INIT
2022-01-19 00:48:41 driver-btm-api.c:156:stop_mining: stop mining: soc init failed!
2022-01-19 00:48:41 thread.c:1403:cancel_read_nonce_reg_thread: cancel thread
2022-01-19 00:48:41 driver-btm-api.c:141:killall_hashboard: ****power off hashboard****
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: wndsnb on January 19, 2022, 02:33:52 AM
Thanks for the follow-up. That makes sense, looks like it is only checking the settings for the boards that it found all chips on.
So your other miner was only running 2 boards or all 3 with the different voltage values? If it was running all 3, then I'd check to see if both your miners are running the same firmware version.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: Heathen23 on January 19, 2022, 01:59:55 PM
The other miner was running 3 boards but board 2 was down. The boards had volatage 1940, 1960 and 1960. Since the middle board was down it was running with 1940 first and 1960 3rd board and was giving full hash rate. Thus my conclusion when there is only 2 boards the stock firmware does not stop for voltage difference.
So I started with
Miner 1
1920 - issues
1920- good
1960 - issues
Miner 2
1940 - good
1960- Issues
1960- good
I replaced the 3rd 1960 board in machine 1 with 1940 in 2nd. I switched to Hive to get around voltage check of stock firmware and to get a little more clue for chip level monitoring.
So I now have a more interesting puzzle.
Miner 1 -
1920 - good now. Had 0 asic in the same slot & same miner before. Hive on indicating a lot of bad domains but running it in low power mode. Should I re-solder the bad domains?
1920 - good. Was good same slot same miner.
1940 - now 0 asic but was good in machine 2 slot 1. Power supply or power cord issue in this slot? I am thinking about buying a new power supply and a new control board to just get them out of equation. I can't find a new control board from reliable sources. But these 2 machines ran flawlessly even a month ago.
Miner 2 -
1960 - good. had 0 asic when it was in slot 2 but good in slot 1 same machine. Hive on indicating a lot of bad domains but running it in low power mode. Should I re-solder the bad domains?
1960 - good. It was good in slot 3 as well. Same machine.
1960 - o asic. had o asic in machine 1 slot 3. send for repair?
Now I am completely confused
Can anybody confirm that in immersion mining losing connection with a heatsink is not this big a problem? I was planning for a DIY immersion setup. The sinks are visibly attached well to the board. After I soldered few that I did not feel was good from visual inspection, they are all firmly attached to the chips now.
[moderator's note: consecutive posts merged]
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: wndsnb on January 20, 2022, 04:54:35 PM
I find it pretty common to have non-repeatable issues, so what you describe doesn't surprise me at all. Just removing and replacing a board can introduce or temporarily fix an issue. I routinely have to bang hashboards around and/or blow cold air on them to get them to fail so I can identify the location of the issue.
Most likely, every board that you have seen a low asic count on has a problem and needs repair.
If you want to try to eliminate variables, just test out each board one at a time using the same data cable and control board connector.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: Heathen23 on January 20, 2022, 08:19:02 PM
Appreciate your insights wndsnb. Over the weekend I am going to take out each board and heat them up to the point so that the sinks are resoldered. If I find some are really out of place them I am going to take them out and solder them individually. Once cold, I will clean them with canned air. Finally I am going to check the signals also with multimeter. Then will put them one by one into miners and see what happens. I did not buy the test zig. Would you recommend it?
They used to work fine and were producing 75 TH @ 2728 watts each. We had a strange hot week during early Jan and that killed them. Now I think the problem is it is so cold that the boards are finding it difficult to start and of course some of them developed heat sink problem during excessive hot days.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: Arshdeep Singh on February 05, 2022, 09:50:34 AM
I wtb a couple of psu fans f95zone (https://ef95zone.com) for my t17, two of then are not working w40s12bmd5 from nidec
12vdc 0.64a
https://www.nidec.com/en/product/search/category/B101/M111/S100/NCJ-W40S12BMD5-5/
Anyone knows where to buy?
delta makes one that should work it uwatchfree (https://euwatchfree.com) is 40x40x28. same size. it is .81 amp which is close to your spec. it is four pin. ebay item 283157645798 even if you dont order it from that seller you can look for part number. REGARDS
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: agbermejo on March 14, 2022, 12:56:32 PM
I have an issue with my T17, one just 1 hashboard. Sometimes i get 0 asic found sometimes it finds all 30. But in any case, I get the error for all temp sensors on the board. I think I've went through most of the posts here and it most likely resembles the issue I quoted below. As I could see, most likely its loose heatsink, but after my (inexperienced) inspection, none seems loose when tested with mild pressure. Can anyone point me to some diy fix (I have only solder, no heatgun) or just take it to the repair shop? Here are the logs: When finding all asics:2021-10-14 17:42:05 driver-btm-api.c:631:init_freq_mode: This is scan-user version
2021-10-14 17:42:05 driver-btm-api.c:1994:bitmain_soc_init: opt_multi_version = 1
2021-10-14 17:42:05 driver-btm-api.c:1995:bitmain_soc_init: opt_bitmain_ab = 1
2021-10-14 17:42:05 driver-btm-api.c:1996:bitmain_soc_init: opt_bitmain_work_mode = 0
2021-10-14 17:42:05 driver-btm-api.c:1997:bitmain_soc_init: Miner compile time: Tue Dec 24 16:13:07 CST 2019 type: Antminer T17
2021-10-14 17:42:05 driver-btm-api.c:1998:bitmain_soc_init: commit version: e93a09b 2019-12-24 16:03:45, build by: lol 2019-12-24 16:19:49
2021-10-14 17:42:05 driver-btm-api.c:1810:show_sn: no SN got, please write SN to /nvdata/sn
2021-10-14 17:42:05 driver-btm-api.c:1135:miner_device_init: Detect 256MB control board of XILINX
2021-10-14 17:42:05 driver-btm-api.c:1083:init_fan_parameter: fan_eft : 0 fan_pwm : 0
2021-10-14 17:42:05 thread.c:789:create_read_nonce_reg_thread: create thread
2021-10-14 17:42:11 driver-btm-api.c:1067:init_miner_version: miner ID : 803c95042b104814
2021-10-14 17:42:11 driver-btm-api.c:1073:init_miner_version: FPGA Version = 0xB013
2021-10-14 17:42:13 eeprom.c:431:check_pattern_test_level: L1 board
2021-10-14 17:42:15 eeprom.c:431:check_pattern_test_level: L1 board
2021-10-14 17:42:16 eeprom.c:431:check_pattern_test_level: L1 board
2021-10-14 17:42:16 driver-btm-api.c:705:get_product_id: product_id[0] = 1
2021-10-14 17:42:16 driver-btm-api.c:705:get_product_id: product_id[1] = 1
2021-10-14 17:42:16 driver-btm-api.c:705:get_product_id: product_id[2] = 1
2021-10-14 17:42:16 driver-btm-api.c:1633:get_ccdly_opt: ccdly_opt[0] = 1
2021-10-14 17:42:16 driver-btm-api.c:1633:get_ccdly_opt: ccdly_opt[1] = 1
2021-10-14 17:42:16 driver-btm-api.c:1633:get_ccdly_opt: ccdly_opt[2] = 1
2021-10-14 17:42:16 driver-btm-api.c:1877:bitmain_board_init: g_ccdly_opt = 1
2021-10-14 17:42:16 driver-btm-api.c:644:_set_project_type: project:2
2021-10-14 17:42:17 driver-btm-api.c:674:_set_project_type: Project type: Antminer T17
2021-10-14 17:42:17 driver-btm-api.c:685:dump_pcb_bom_version: Chain [0] PCB Version: 0x0100
2021-10-14 17:42:17 driver-btm-api.c:686:dump_pcb_bom_version: Chain [0] BOM Version: 0x0100
2021-10-14 17:42:17 driver-btm-api.c:685:dump_pcb_bom_version: Chain [1] PCB Version: 0x0100
2021-10-14 17:42:17 driver-btm-api.c:686:dump_pcb_bom_version: Chain [1] BOM Version: 0x0100
2021-10-14 17:42:17 driver-btm-api.c:685:dump_pcb_bom_version: Chain [2] PCB Version: 0x0100
2021-10-14 17:42:17 driver-btm-api.c:686:dump_pcb_bom_version: Chain [2] BOM Version: 0x0100
2021-10-14 17:42:18 driver-btm-api.c:1897:bitmain_board_init: Fan check passed.
2021-10-14 17:42:19 board.c:36:jump_and_app_check_restore_pic: chain[0] PIC jump to app
2021-10-14 17:42:23 board.c:40:jump_and_app_check_restore_pic: Check chain[0] PIC fw version=0xb9
2021-10-14 17:42:24 board.c:36:jump_and_app_check_restore_pic: chain[1] PIC jump to app
2021-10-14 17:42:28 board.c:40:jump_and_app_check_restore_pic: Check chain[1] PIC fw version=0xb9
2021-10-14 17:42:30 board.c:36:jump_and_app_check_restore_pic: chain[2] PIC jump to app
2021-10-14 17:42:33 board.c:40:jump_and_app_check_restore_pic: Check chain[2] PIC fw version=0xb9
2021-10-14 17:42:33 thread.c:784:create_pic_heart_beat_thread: create thread
2021-10-14 17:42:33 power_api.c:55:power_init: power init ...
2021-10-14 17:42:33 driver-btm-api.c:1907:bitmain_board_init: Enter 30s sleep to make sure power release finish.
2021-10-14 17:43:05 power_api.c:232:set_iic_power_to_highest_voltage: setting to voltage: 17.00 ...
2021-10-14 17:43:11 power_api.c:124:check_voltage_multi: retry time: 0
2021-10-14 17:43:13 power_api.c:86:get_average_voltage: chain[0], voltage is: 17.677236
2021-10-14 17:43:14 power_api.c:86:get_average_voltage: chain[1], voltage is: 17.120039
2021-10-14 17:43:16 power_api.c:86:get_average_voltage: chain[2], voltage is: 16.917978
2021-10-14 17:43:16 power_api.c:97:get_average_voltage: aveage voltage is: 17.238418
2021-10-14 17:43:16 power_api.c:182:set_iic_power_by_voltage: now set voltage to : 17.000000
2021-10-14 17:43:16 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[0]: chip baud = 115200, chip_divider = 26
2021-10-14 17:43:16 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[1]: chip baud = 115200, chip_divider = 26
2021-10-14 17:43:16 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[2]: chip baud = 115200, chip_divider = 26
2021-10-14 17:43:16 uart.c:80:set_baud: set fpga_baud = 115200, fpga_divider = 26
2021-10-14 17:43:28 driver-btm-api.c:1010:check_asic_number_with_power_on: Chain[0]: find 30 asic, times 0
2021-10-14 17:43:38 driver-btm-api.c:1010:check_asic_number_with_power_on: Chain[1]: find 30 asic, times 0
2021-10-14 17:43:48 driver-btm-api.c:1010:check_asic_number_with_power_on: Chain[2]: find 30 asic, times 0
2021-10-14 17:43:51 driver-btm-api.c:348:set_order_clock: chain[0]: set order clock, stragegy 3 clock_en=0x1
2021-10-14 17:43:51 driver-btm-api.c:348:set_order_clock: chain[1]: set order clock, stragegy 3 clock_en=0x1
2021-10-14 17:43:52 driver-btm-api.c:348:set_order_clock: chain[2]: set order clock, stragegy 3 clock_en=0x1
2021-10-14 17:43:52 driver-hash-chip.c:490:set_clock_delay_control: core_data = 0xb4
2021-10-14 17:43:52 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[0]: chip baud = 3000000, chip_divider = 0
2021-10-14 17:43:52 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[1]: chip baud = 3000000, chip_divider = 0
2021-10-14 17:43:52 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[2]: chip baud = 3000000, chip_divider = 0
2021-10-14 17:43:52 uart.c:80:set_baud: set fpga_baud = 3000000, fpga_divider = 0
2021-10-14 17:43:52 driver-btm-api.c:1660:check_clock_counter: freq 50 clock_counter_limit 6
2021-10-14 17:43:53 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[0]: chip baud = 115200, chip_divider = 26
2021-10-14 17:43:53 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[1]: chip baud = 115200, chip_divider = 26
2021-10-14 17:43:53 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[2]: chip baud = 115200, chip_divider = 26
2021-10-14 17:43:53 uart.c:80:set_baud: set fpga_baud = 115200, fpga_divider = 26
2021-10-14 17:43:53 voltage[0] = 1690
2021-10-14 17:43:53 voltage[1] = 1690
2021-10-14 17:43:53 voltage[2] = 1690
2021-10-14 17:43:53 power_api.c:140:set_working_voltage: working_voltage = 16.900000
2021-10-14 17:43:54 temperature.c:282:calibrate_temp_sensor_one_chain: Temperature sensor calibration: chain 0 success.
2021-10-14 17:43:55 temperature.c:282:calibrate_temp_sensor_one_chain: Temperature sensor calibration: chain 1 success.
2021-10-14 17:43:57 temperature.c:282:calibrate_temp_sensor_one_chain: Temperature sensor calibration: chain 2 success.
2021-10-14 17:43:57 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[0]: chip baud = 6000000, chip_divider = 7
2021-10-14 17:43:57 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[1]: chip baud = 6000000, chip_divider = 7
2021-10-14 17:43:57 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[2]: chip baud = 6000000, chip_divider = 7
2021-10-14 17:43:57 uart.c:80:set_baud: set fpga_baud = 6000000, fpga_divider = 3
2021-10-14 17:43:59 driver-btm-api.c:248:check_bringup_temp: Bring up temperature is 21
2021-10-14 17:43:59 thread.c:804:create_check_miner_status_thread: create thread
2021-10-14 17:43:59 thread.c:794:create_set_miner_status_thread: create thread
2021-10-14 17:43:59 driver-btm-api.c:581:calculate_timeout: dev->timeout = 392
2021-10-14 17:43:59 thread.c:779:create_temperature_monitor_thread: create thread
2021-10-14 17:43:59 freq_tuning.c:154:freq_tuning_get_max_freq: Max freq of tuning is 760
2021-10-14 17:43:59 power_api.c:379:slowly_set_iic_power_to_custom_voltage: slowly setting to voltage: 17.80 ...
2021-10-14 17:44:33 power_api.c:124:check_voltage_multi: retry time: 0
2021-10-14 17:44:35 power_api.c:86:get_average_voltage: chain[0], voltage is: 17.781328
2021-10-14 17:44:37 power_api.c:86:get_average_voltage: chain[1], voltage is: 17.769082
2021-10-14 17:44:39 power_api.c:86:get_average_voltage: chain[2], voltage is: 17.744590
2021-10-14 17:44:39 power_api.c:97:get_average_voltage: aveage voltage is: 17.765000
2021-10-14 17:44:39 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 44 set refdiv: 2, fbdiv: 173, postdiv1: 7, postdiv2: 7, usr divider: 1
2021-10-14 17:44:39 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 51 set refdiv: 2, fbdiv: 173, postdiv1: 7, postdiv2: 6, usr divider: 1
2021-10-14 17:44:39 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 61 set refdiv: 2, fbdiv: 173, postdiv1: 7, postdiv2: 5, usr divider: 1
2021-10-14 17:44:39 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 77 set refdiv: 2, fbdiv: 173, postdiv1: 7, postdiv2: 4, usr divider: 1
2021-10-14 17:44:39 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 102 set refdiv: 2, fbdiv: 173, postdiv1: 7, postdiv2: 3, usr divider: 1
2021-10-14 17:44:39 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 154 set refdiv: 2, fbdiv: 173, postdiv1: 7, postdiv2: 2, usr divider: 1
2021-10-14 17:44:39 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 308 set refdiv: 2, fbdiv: 173, postdiv1: 7, postdiv2: 1, usr divider: 1
2021-10-14 17:44:39 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 360 set refdiv: 2, fbdiv: 173, postdiv1: 6, postdiv2: 1, usr divider: 1
2021-10-14 17:44:40 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 432 set refdiv: 2, fbdiv: 173, postdiv1: 5, postdiv2: 1, usr divider: 1
2021-10-14 17:44:40 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 540 set refdiv: 2, fbdiv: 173, postdiv1: 4, postdiv2: 1, usr divider: 1
2021-10-14 17:44:40 driver-btm-api.c:449:change_freq_one_chain: chain[0] freq: 720 set refdiv: 2, fbdiv: 173, postdiv1: 3, postdiv2: 1, usr divider: 1
2021-10-14 17:44:40 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 44 set refdiv: 2, fbdiv: 173, postdiv1: 7, postdiv2: 7, usr divider: 1
2021-10-14 17:44:40 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 51 set refdiv: 2, fbdiv: 173, postdiv1: 7, postdiv2: 6, usr divider: 1
2021-10-14 17:44:40 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 61 set refdiv: 2, fbdiv: 173, postdiv1: 7, postdiv2: 5, usr divider: 1
2021-10-14 17:44:40 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 77 set refdiv: 2, fbdiv: 173, postdiv1: 7, postdiv2: 4, usr divider: 1
2021-10-14 17:44:40 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 102 set refdiv: 2, fbdiv: 173, postdiv1: 7, postdiv2: 3, usr divider: 1
2021-10-14 17:44:40 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 154 set refdiv: 2, fbdiv: 173, postdiv1: 7, postdiv2: 2, usr divider: 1
2021-10-14 17:44:41 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 308 set refdiv: 2, fbdiv: 173, postdiv1: 7, postdiv2: 1, usr divider: 1
2021-10-14 17:44:41 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 360 set refdiv: 2, fbdiv: 173, postdiv1: 6, postdiv2: 1, usr divider: 1
2021-10-14 17:44:41 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 432 set refdiv: 2, fbdiv: 173, postdiv1: 5, postdiv2: 1, usr divider: 1
2021-10-14 17:44:41 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 540 set refdiv: 2, fbdiv: 173, postdiv1: 4, postdiv2: 1, usr divider: 1
2021-10-14 17:44:41 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 720 set refdiv: 2, fbdiv: 173, postdiv1: 3, postdiv2: 1, usr divider: 1
2021-10-14 17:44:41 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 44 set refdiv: 2, fbdiv: 173, postdiv1: 7, postdiv2: 7, usr divider: 1
2021-10-14 17:44:41 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 51 set refdiv: 2, fbdiv: 173, postdiv1: 7, postdiv2: 6, usr divider: 1
2021-10-14 17:44:41 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 61 set refdiv: 2, fbdiv: 173, postdiv1: 7, postdiv2: 5, usr divider: 1
2021-10-14 17:44:41 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 77 set refdiv: 2, fbdiv: 173, postdiv1: 7, postdiv2: 4, usr divider: 1
2021-10-14 17:44:41 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 102 set refdiv: 2, fbdiv: 173, postdiv1: 7, postdiv2: 3, usr divider: 1
2021-10-14 17:44:42 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 154 set refdiv: 2, fbdiv: 173, postdiv1: 7, postdiv2: 2, usr divider: 1
2021-10-14 17:44:42 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 308 set refdiv: 2, fbdiv: 173, postdiv1: 7, postdiv2: 1, usr divider: 1
2021-10-14 17:44:42 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 360 set refdiv: 2, fbdiv: 173, postdiv1: 6, postdiv2: 1, usr divider: 1
2021-10-14 17:44:42 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 432 set refdiv: 2, fbdiv: 173, postdiv1: 5, postdiv2: 1, usr divider: 1
2021-10-14 17:44:42 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 540 set refdiv: 2, fbdiv: 173, postdiv1: 4, postdiv2: 1, usr divider: 1
2021-10-14 17:44:42 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 720 set refdiv: 2, fbdiv: 173, postdiv1: 3, postdiv2: 1, usr divider: 1
2021-10-14 17:44:42 driver-btm-api.c:612:set_timeout: freq 720 final timeout=163
2021-10-14 17:44:42 power_api.c:397:slowly_set_iic_power_to_working_voltage: slowly setting to voltage: 16.90 ...
2021-10-14 17:44:48 temperature.c:697:get_temp_info: read temp sensor failed: chain = 0, sensor = 0, chip = 64, reg = 0
2021-10-14 17:45:01 temperature.c:697:get_temp_info: read temp sensor failed: chain = 0, sensor = 0, chip = 64, reg = 1
2021-10-14 17:45:07 temperature.c:697:get_temp_info: read temp sensor failed: chain = 0, sensor = 1, chip = 48, reg = 0
2021-10-14 17:45:17 power_api.c:124:check_voltage_multi: retry time: 0
2021-10-14 17:45:19 power_api.c:86:get_average_voltage: chain[0], voltage is: 16.783271
2021-10-14 17:45:20 temperature.c:697:get_temp_info: read temp sensor failed: chain = 0, sensor = 1, chip = 48, reg = 1
2021-10-14 17:45:21 power_api.c:86:get_average_voltage: chain[1], voltage is: 16.771025
2021-10-14 17:45:22 power_api.c:86:get_average_voltage: chain[2], voltage is: 16.979209
2021-10-14 17:45:22 power_api.c:97:get_average_voltage: aveage voltage is: 16.844502
2021-10-14 17:45:22 frequency.c:540:get_current_min_freq: current min freq 720
2021-10-14 17:45:22 driver-btm-api.c:1660:check_clock_counter: freq 720 clock_counter_limit 92
2021-10-14 17:45:27 temperature.c:697:get_temp_info: read temp sensor failed: chain = 0, sensor = 2, chip = 168, reg = 0
2021-10-14 17:45:40 temperature.c:697:get_temp_info: read temp sensor failed: chain = 0, sensor = 2, chip = 168, reg = 1
2021-10-14 17:45:47 temperature.c:697:get_temp_info: read temp sensor failed: chain = 0, sensor = 3, chip = 184, reg = 0
2021-10-14 17:46:00 temperature.c:697:get_temp_info: read temp sensor failed: chain = 0, sensor = 3, chip = 184, reg = 1
2021-10-14 17:46:04 register.c:1416:quick_dump_core_hash_clock_counter: bad clock counter. chain = 0, asic = 5, core = 0, found 0, clock counter 0x00000000
2021-10-14 17:46:04 driver-btm-api.c:2097:bitmain_soc_init: clock count check failed after retry, wait for hash rate protect later.
2021-10-14 17:46:04 thread.c:799:create_check_system_status_thread: create thread
2021-10-14 17:46:04 driver-btm-api.c:2113:bitmain_soc_init: Init done!
2021-10-14 17:46:04 driver-btm-api.c:201:set_miner_status: STATUS_INIT
2021-10-14 17:46:09 driver-btm-api.c:201:set_miner_status: STATUS_OKAY
2021-10-14 17:46:10 temperature.c:697:get_temp_info: read temp sensor failed: chain = 0, sensor = 0, chip = 64, reg = 0
2021-10-14 17:46:14 driver-btm-api.c:1293:dhash_chip_send_job: Version num 4
2021-10-14 17:46:24 temperature.c:697:get_temp_info: read temp sensor failed: chain = 0, sensor = 0, chip = 64, reg = 1
2021-10-14 17:46:30 temperature.c:697:get_temp_info: read temp sensor failed: chain = 0, sensor = 1, chip = 48, reg = 0
2021-10-14 17:46:43 temperature.c:697:get_temp_info: read temp sensor failed: chain = 0, sensor = 1, chip = 48, reg = 1
2021-10-14 17:46:50 temperature.c:697:get_temp_info: read temp sensor failed: chain = 0, sensor = 2, chip = 168, reg = 0
2021-10-14 17:47:03 temperature.c:697:get_temp_info: read temp sensor failed: chain = 0, sensor = 2, chip = 168, reg = 1
2021-10-14 17:47:09 temperature.c:697:get_temp_info: read temp sensor failed: chain = 0, sensor = 3, chip = 184, reg = 0
2021-10-14 17:47:23 temperature.c:697:get_temp_info: read temp sensor failed: chain = 0, sensor = 3, chip = 184, reg = 1
2021-10-14 17:47:31 temperature.c:697:get_temp_info: read temp sensor failed: chain = 0, sensor = 0, chip = 64, reg = 0
2021-10-14 17:47:44 temperature.c:697:get_temp_info: read temp sensor failed: chain = 0, sensor = 0, chip = 64, reg = 1
2021-10-14 17:47:51 temperature.c:697:get_temp_info: read temp sensor failed: chain = 0, sensor = 1, chip = 48, reg = 0
2021-10-14 17:48:04 temperature.c:697:get_temp_info: read temp sensor failed: chain = 0, sensor = 1, chip = 48, reg = 1
2021-10-14 17:48:11 temperature.c:697:get_temp_info: read temp sensor failed: chain = 0, sensor = 2, chip = 168, reg = 0
2021-10-14 17:48:24 temperature.c:697:get_temp_info: read temp sensor failed: chain = 0, sensor = 2, chip = 168, reg = 1
2021-10-14 17:48:30 temperature.c:697:get_temp_info: read temp sensor failed: chain = 0, sensor = 3, chip = 184, reg = 0
2021-10-14 17:48:43 temperature.c:697:get_temp_info: read temp sensor failed: chain = 0, sensor = 3, chip = 184, reg = 1
2021-10-14 17:48:52 temperature.c:697:get_temp_info: read temp sensor failed: chain = 0, sensor = 0, chip = 64, reg = 0
2021-10-14 17:49:05 temperature.c:697:get_temp_info: read temp sensor failed: chain = 0, sensor = 0, chip = 64, reg = 1
2021-10-14 17:49:12 temperature.c:697:get_temp_info: read temp sensor failed: chain = 0, sensor = 1, chip = 48, reg = 0
2021-10-14 17:49:25 temperature.c:697:get_temp_info: read temp sensor failed: chain = 0, sensor = 1, chip = 48, reg = 1
2021-10-14 17:49:31 temperature.c:697:get_temp_info: read temp sensor failed: chain = 0, sensor = 2, chip = 168, reg = 0
2021-10-14 17:49:44 temperature.c:697:get_temp_info: read temp sensor failed: chain = 0, sensor = 2, chip = 168, reg = 1
2021-10-14 17:49:51 temperature.c:697:get_temp_info: read temp sensor failed: chain = 0, sensor = 3, chip = 184, reg = 0
2021-10-14 17:50:04 temperature.c:697:get_temp_info: read temp sensor failed: chain = 0, sensor = 3, chip = 184, reg = 1
2021-10-14 17:50:13 temperature.c:697:get_temp_info: read temp sensor failed: chain = 0, sensor = 0, chip = 64, reg = 0
2021-10-14 17:50:26 temperature.c:697:get_temp_info: read temp sensor failed: chain = 0, sensor = 0, chip = 64, reg = 1
2021-10-14 17:50:32 temperature.c:697:get_temp_info: read temp sensor failed: chain = 0, sensor = 1, chip = 48, reg = 0
2021-10-14 17:50:46 temperature.c:697:get_temp_info: read temp sensor failed: chain = 0, sensor = 1, chip = 48, reg = 1
2021-10-14 17:50:52 temperature.c:697:get_temp_info: read temp sensor failed: chain = 0, sensor = 2, chip = 168, reg = 0
2021-10-14 17:51:05 temperature.c:697:get_temp_info: read temp sensor failed: chain = 0, sensor = 2, chip = 168, reg = 1
2021-10-14 17:51:12 temperature.c:697:get_temp_info: read temp sensor failed: chain = 0, sensor = 3, chip = 184, reg = 0
2021-10-14 17:51:13 thread.c:422:is_zero_nonce_happened: chain_nonce[0] = 0
2021-10-14 17:51:13 thread.c:422:is_zero_nonce_happened: chain_nonce[1] = 15697
2021-10-14 17:51:13 thread.c:422:is_zero_nonce_happened: chain_nonce[2] = 15686
2021-10-14 17:51:13 thread.c:539:check_system_work_thread: 0 nonce rate happened after retry, wait for hash rate protect later.
2021-10-14 17:51:25 temperature.c:697:get_temp_info: read temp sensor failed: chain = 0, sensor = 3, chip = 184, reg = 1
2021-10-14 17:51:33 temperature.c:697:get_temp_info: read temp sensor failed: chain = 0, sensor = 0, chip = 64, reg = 0 2021-10-14 17:24:48 driver-btm-api.c:631:init_freq_mode: This is scan-user version
2021-10-14 17:24:48 driver-btm-api.c:1994:bitmain_soc_init: opt_multi_version = 1
2021-10-14 17:24:48 driver-btm-api.c:1995:bitmain_soc_init: opt_bitmain_ab = 1
2021-10-14 17:24:48 driver-btm-api.c:1996:bitmain_soc_init: opt_bitmain_work_mode = 0
2021-10-14 17:24:48 driver-btm-api.c:1997:bitmain_soc_init: Miner compile time: Tue Dec 24 16:13:07 CST 2019 type: Antminer T17
2021-10-14 17:24:48 driver-btm-api.c:1998:bitmain_soc_init: commit version: e93a09b 2019-12-24 16:03:45, build by: lol 2019-12-24 16:19:49
2021-10-14 17:24:48 driver-btm-api.c:1810:show_sn: no SN got, please write SN to /nvdata/sn
2021-10-14 17:24:48 driver-btm-api.c:1135:miner_device_init: Detect 256MB control board of XILINX
2021-10-14 17:24:48 driver-btm-api.c:1083:init_fan_parameter: fan_eft : 0 fan_pwm : 0
2021-10-14 17:24:48 thread.c:789:create_read_nonce_reg_thread: create thread
2021-10-14 17:24:54 driver-btm-api.c:1067:init_miner_version: miner ID : 803c95042b104814
2021-10-14 17:24:54 driver-btm-api.c:1073:init_miner_version: FPGA Version = 0xB013
2021-10-14 17:24:56 eeprom.c:431:check_pattern_test_level: L1 board
2021-10-14 17:24:58 eeprom.c:431:check_pattern_test_level: L1 board
2021-10-14 17:24:59 eeprom.c:431:check_pattern_test_level: L1 board
2021-10-14 17:24:59 driver-btm-api.c:705:get_product_id: product_id[0] = 1
2021-10-14 17:24:59 driver-btm-api.c:705:get_product_id: product_id[1] = 1
2021-10-14 17:24:59 driver-btm-api.c:705:get_product_id: product_id[2] = 1
2021-10-14 17:24:59 driver-btm-api.c:1633:get_ccdly_opt: ccdly_opt[0] = 1
2021-10-14 17:24:59 driver-btm-api.c:1633:get_ccdly_opt: ccdly_opt[1] = 1
2021-10-14 17:24:59 driver-btm-api.c:1633:get_ccdly_opt: ccdly_opt[2] = 1
2021-10-14 17:24:59 driver-btm-api.c:1877:bitmain_board_init: g_ccdly_opt = 1
2021-10-14 17:24:59 driver-btm-api.c:644:_set_project_type: project:2
2021-10-14 17:24:59 driver-btm-api.c:674:_set_project_type: Project type: Antminer T17
2021-10-14 17:24:59 driver-btm-api.c:685:dump_pcb_bom_version: Chain [0] PCB Version: 0x0100
2021-10-14 17:24:59 driver-btm-api.c:686:dump_pcb_bom_version: Chain [0] BOM Version: 0x0100
2021-10-14 17:24:59 driver-btm-api.c:685:dump_pcb_bom_version: Chain [1] PCB Version: 0x0100
2021-10-14 17:24:59 driver-btm-api.c:686:dump_pcb_bom_version: Chain [1] BOM Version: 0x0100
2021-10-14 17:24:59 driver-btm-api.c:685:dump_pcb_bom_version: Chain [2] PCB Version: 0x0100
2021-10-14 17:24:59 driver-btm-api.c:686:dump_pcb_bom_version: Chain [2] BOM Version: 0x0100
2021-10-14 17:24:59 driver-btm-api.c:1897:bitmain_board_init: Fan check passed.
2021-10-14 17:25:01 board.c:36:jump_and_app_check_restore_pic: chain[0] PIC jump to app
2021-10-14 17:25:05 board.c:40:jump_and_app_check_restore_pic: Check chain[0] PIC fw version=0xb9
2021-10-14 17:25:06 board.c:36:jump_and_app_check_restore_pic: chain[1] PIC jump to app
2021-10-14 17:25:10 board.c:40:jump_and_app_check_restore_pic: Check chain[1] PIC fw version=0xb9
2021-10-14 17:25:12 board.c:36:jump_and_app_check_restore_pic: chain[2] PIC jump to app
2021-10-14 17:25:15 board.c:40:jump_and_app_check_restore_pic: Check chain[2] PIC fw version=0xb9
2021-10-14 17:25:15 thread.c:784:create_pic_heart_beat_thread: create thread
2021-10-14 17:25:15 power_api.c:55:power_init: power init ...
2021-10-14 17:25:15 driver-btm-api.c:1907:bitmain_board_init: Enter 30s sleep to make sure power release finish.
2021-10-14 17:25:47 power_api.c:232:set_iic_power_to_highest_voltage: setting to voltage: 17.00 ...
2021-10-14 17:25:53 power_api.c:124:check_voltage_multi: retry time: 0
2021-10-14 17:25:54 power_api.c:86:get_average_voltage: chain[0], voltage is: 17.003701
2021-10-14 17:25:56 power_api.c:86:get_average_voltage: chain[1], voltage is: 17.003701
2021-10-14 17:25:58 power_api.c:86:get_average_voltage: chain[2], voltage is: 16.966963
2021-10-14 17:25:58 power_api.c:97:get_average_voltage: aveage voltage is: 16.991455
2021-10-14 17:25:58 power_api.c:182:set_iic_power_by_voltage: now set voltage to : 17.000000
2021-10-14 17:25:58 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[0]: chip baud = 115200, chip_divider = 26
2021-10-14 17:25:58 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[1]: chip baud = 115200, chip_divider = 26
2021-10-14 17:25:58 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[2]: chip baud = 115200, chip_divider = 26
2021-10-14 17:25:58 uart.c:80:set_baud: set fpga_baud = 115200, fpga_divider = 26
2021-10-14 17:26:09 driver-btm-api.c:1010:check_asic_number_with_power_on: Chain[0]: find 0 asic, times 0
2021-10-14 17:26:19 driver-btm-api.c:1010:check_asic_number_with_power_on: Chain[0]: find 0 asic, times 1
2021-10-14 17:26:29 driver-btm-api.c:1010:check_asic_number_with_power_on: Chain[0]: find 0 asic, times 2
2021-10-14 17:26:29 driver-btm-api.c:1037:check_asic_number: Chain 0 only find 0 asic, will power off hash board 0
2021-10-14 17:26:41 driver-btm-api.c:1010:check_asic_number_with_power_on: Chain[1]: find 30 asic, times 0
2021-10-14 17:26:51 driver-btm-api.c:1010:check_asic_number_with_power_on: Chain[2]: find 30 asic, times 0
2021-10-14 17:26:54 driver-btm-api.c:348:set_order_clock: chain[1]: set order clock, stragegy 3 clock_en=0x1
2021-10-14 17:26:54 driver-btm-api.c:348:set_order_clock: chain[2]: set order clock, stragegy 3 clock_en=0x1
2021-10-14 17:26:54 driver-hash-chip.c:490:set_clock_delay_control: core_data = 0xb4
2021-10-14 17:26:54 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[1]: chip baud = 3000000, chip_divider = 0
2021-10-14 17:26:54 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[2]: chip baud = 3000000, chip_divider = 0
2021-10-14 17:26:54 uart.c:80:set_baud: set fpga_baud = 3000000, fpga_divider = 0
2021-10-14 17:26:54 driver-btm-api.c:1660:check_clock_counter: freq 50 clock_counter_limit 6
2021-10-14 17:26:55 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[1]: chip baud = 115200, chip_divider = 26
2021-10-14 17:26:55 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[2]: chip baud = 115200, chip_divider = 26
2021-10-14 17:26:55 uart.c:80:set_baud: set fpga_baud = 115200, fpga_divider = 26
2021-10-14 17:26:55 voltage[1] = 1690
2021-10-14 17:26:55 voltage[2] = 1690
2021-10-14 17:26:55 power_api.c:140:set_working_voltage: working_voltage = 16.900000
2021-10-14 17:26:56 temperature.c:282:calibrate_temp_sensor_one_chain: Temperature sensor calibration: chain 1 success.
2021-10-14 17:26:57 temperature.c:282:calibrate_temp_sensor_one_chain: Temperature sensor calibration: chain 2 success.
2021-10-14 17:26:57 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[1]: chip baud = 6000000, chip_divider = 7
2021-10-14 17:26:57 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[2]: chip baud = 6000000, chip_divider = 7
2021-10-14 17:26:57 uart.c:80:set_baud: set fpga_baud = 6000000, fpga_divider = 3
2021-10-14 17:26:59 driver-btm-api.c:248:check_bringup_temp: Bring up temperature is 25
2021-10-14 17:26:59 thread.c:804:create_check_miner_status_thread: create thread
2021-10-14 17:26:59 thread.c:794:create_set_miner_status_thread: create thread
2021-10-14 17:26:59 driver-btm-api.c:581:calculate_timeout: dev->timeout = 392
2021-10-14 17:26:59 thread.c:779:create_temperature_monitor_thread: create thread
2021-10-14 17:26:59 freq_tuning.c:154:freq_tuning_get_max_freq: Max freq of tuning is 760
2021-10-14 17:26:59 power_api.c:379:slowly_set_iic_power_to_custom_voltage: slowly setting to voltage: 17.80 ...
2021-10-14 17:27:30 power_api.c:124:check_voltage_multi: retry time: 0
2021-10-14 17:27:33 power_api.c:86:get_average_voltage: chain[1], voltage is: 17.781328
2021-10-14 17:27:36 power_api.c:86:get_average_voltage: chain[2], voltage is: 17.769082
2021-10-14 17:27:36 power_api.c:97:get_average_voltage: aveage voltage is: 17.775205
2021-10-14 17:27:36 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 44 set refdiv: 2, fbdiv: 173, postdiv1: 7, postdiv2: 7, usr divider: 1
2021-10-14 17:27:37 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 51 set refdiv: 2, fbdiv: 173, postdiv1: 7, postdiv2: 6, usr divider: 1
2021-10-14 17:27:37 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 61 set refdiv: 2, fbdiv: 173, postdiv1: 7, postdiv2: 5, usr divider: 1
2021-10-14 17:27:37 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 77 set refdiv: 2, fbdiv: 173, postdiv1: 7, postdiv2: 4, usr divider: 1
2021-10-14 17:27:37 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 102 set refdiv: 2, fbdiv: 173, postdiv1: 7, postdiv2: 3, usr divider: 1
2021-10-14 17:27:37 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 154 set refdiv: 2, fbdiv: 173, postdiv1: 7, postdiv2: 2, usr divider: 1
2021-10-14 17:27:37 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 308 set refdiv: 2, fbdiv: 173, postdiv1: 7, postdiv2: 1, usr divider: 1
2021-10-14 17:27:37 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 360 set refdiv: 2, fbdiv: 173, postdiv1: 6, postdiv2: 1, usr divider: 1
2021-10-14 17:27:37 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 432 set refdiv: 2, fbdiv: 173, postdiv1: 5, postdiv2: 1, usr divider: 1
2021-10-14 17:27:37 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 540 set refdiv: 2, fbdiv: 173, postdiv1: 4, postdiv2: 1, usr divider: 1
2021-10-14 17:27:37 driver-btm-api.c:449:change_freq_one_chain: chain[1] freq: 720 set refdiv: 2, fbdiv: 173, postdiv1: 3, postdiv2: 1, usr divider: 1
2021-10-14 17:27:38 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 44 set refdiv: 2, fbdiv: 173, postdiv1: 7, postdiv2: 7, usr divider: 1
2021-10-14 17:27:38 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 51 set refdiv: 2, fbdiv: 173, postdiv1: 7, postdiv2: 6, usr divider: 1
2021-10-14 17:27:38 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 61 set refdiv: 2, fbdiv: 173, postdiv1: 7, postdiv2: 5, usr divider: 1
2021-10-14 17:27:38 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 77 set refdiv: 2, fbdiv: 173, postdiv1: 7, postdiv2: 4, usr divider: 1
2021-10-14 17:27:38 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 102 set refdiv: 2, fbdiv: 173, postdiv1: 7, postdiv2: 3, usr divider: 1
2021-10-14 17:27:38 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 154 set refdiv: 2, fbdiv: 173, postdiv1: 7, postdiv2: 2, usr divider: 1
2021-10-14 17:27:38 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 308 set refdiv: 2, fbdiv: 173, postdiv1: 7, postdiv2: 1, usr divider: 1
2021-10-14 17:27:38 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 360 set refdiv: 2, fbdiv: 173, postdiv1: 6, postdiv2: 1, usr divider: 1
2021-10-14 17:27:38 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 432 set refdiv: 2, fbdiv: 173, postdiv1: 5, postdiv2: 1, usr divider: 1
2021-10-14 17:27:39 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 540 set refdiv: 2, fbdiv: 173, postdiv1: 4, postdiv2: 1, usr divider: 1
2021-10-14 17:27:39 driver-btm-api.c:449:change_freq_one_chain: chain[2] freq: 720 set refdiv: 2, fbdiv: 173, postdiv1: 3, postdiv2: 1, usr divider: 1
2021-10-14 17:27:39 driver-btm-api.c:612:set_timeout: freq 720 final timeout=163
2021-10-14 17:27:39 power_api.c:397:slowly_set_iic_power_to_working_voltage: slowly setting to voltage: 16.90 ...
2021-10-14 17:27:58 thread.c:642:check_temperature: over max temp, pcb temp 59 (max 80), chip temp 106(max 103)
2021-10-14 17:27:58 driver-btm-api.c:201:set_miner_status: ERROR_TEMP_TOO_HIGH
2021-10-14 17:27:58 driver-btm-api.c:142:stop_mining: stop mining: over max temp
2021-10-14 17:27:58 thread.c:824:cancel_temperature_monitor_thread: cancel thread
2021-10-14 17:27:58 thread.c:834:cancel_read_nonce_reg_thread: cancel thread
2021-10-14 17:27:58 driver-btm-api.c:128:killall_hashboard: ****power off hashboard****
2021-10-14 17:28:09 power_api.c:124:check_voltage_multi: retry time: 0
2021-10-14 17:28:11 power_api.c:86:get_average_voltage: chain[1], voltage is: 16.948594
2021-10-14 17:28:13 power_api.c:86:get_average_voltage: chain[2], voltage is: 17.205762
2021-10-14 17:28:13 power_api.c:97:get_average_voltage: aveage voltage is: 17.077178
2021-10-14 17:28:13 frequency.c:540:get_current_min_freq: current min freq 720
2021-10-14 17:28:13 driver-btm-api.c:1660:check_clock_counter: freq 720 clock_counter_limit 92
2021-10-14 17:28:16 register.c:1416:quick_dump_core_hash_clock_counter: bad clock counter. chain = 1, asic = 5, core = 0, found 0, clock counter 0x00000000
2021-10-14 17:28:16 driver-btm-api.c:2097:bitmain_soc_init: clock count check failed after retry, wait for hash rate protect later.
2021-10-14 17:28:16 thread.c:799:create_check_system_status_thread: create thread
2021-10-14 17:28:16 driver-btm-api.c:2113:bitmain_soc_init: Init done!
2021-10-14 17:28:16 driver-btm-api.c:201:set_miner_status: STATUS_INIT
2021-10-14 17:28:21 driver-btm-api.c:201:set_miner_status: STATUS_OKAY
2021-10-14 17:28:25 driver-btm-api.c:1293:dhash_chip_send_job: Version num 4 I wouldnt want to use any permeneatny adhesive. Im looking to apply solder. What solder do you know I can use for this that can be taken off and on. Also I have a whole bunch of boards that have the same exact errors when I run the test fixture. All the asic are found but I still get a temp sensor error. 1970-01-01 00:01:52 register.c:185:read_asic_reg_with_addr: read asic reg timeout: expect chain = 0, chip = 14, reg = 28
1970-01-01 00:01:52 register.c:185:read_asic_reg_with_addr: read asic reg timeout: expect chain = 0, chip = 14, reg = 28
1970-01-01 00:01:53 temperature.c:744:get_temp_info: read temp sensor failed: chain = 0, sensor = 0, chip = 14, reg = 1
...
1970-01-01 00:01:53 register.c:185:read_asic_reg_with_addr: read asic reg timeout: expect chain = 0, chip = 10, reg = 28
1970-01-01 00:01:53 register.c:185:read_asic_reg_with_addr: read asic reg timeout: expect chain = 0, chip = 10, reg = 28
1970-01-01 00:01:54 temperature.c:744:get_temp_info: read temp sensor failed: chain = 0, sensor = 1, chip = 10, reg = 1
...
1970-01-01 00:01:54 register.c:185:read_asic_reg_with_addr: read asic reg timeout: expect chain = 0, chip = 54, reg = 28
1970-01-01 00:01:54 register.c:185:read_asic_reg_with_addr: read asic reg timeout: expect chain = 0, chip = 54, reg = 28
1970-01-01 00:01:54 register.c:185:read_asic_reg_with_addr: read asic reg timeout: expect chain = 0, chip = 54, reg = 28
1970-01-01 00:01:55 temperature.c:744:get_temp_info: read temp sensor failed: chain = 0, sensor = 2, chip = 54, reg = 1
1970-01-01 00:01:55 register.c:185:read_asic_reg_with_addr: read asic reg timeout: expect chain = 0, chip = 50, reg = 28
1970-01-01 00:01:55 register.c:185:read_asic_reg_with_addr: read asic reg timeout: expect chain = 0, chip = 50, reg = 28
...
1970-01-01 00:01:56 temperature.c:744:get_temp_info: read temp sensor failed: chain = 0, sensor = 3, chip = 50, reg = 1
1970-01-01 00:01:56 single_board_test.c:1659:wait_warm_up: temper sensor bad
I have this same exact error for over 10 boards. Also the the error states chip 50, 54, 10, 14 as being bad chips but I get this same exact error on many boards. Cant all have the same exact chips with the same exact error. What could this be? My boards are in 100% perfect condition and all the sudden stopped working one day. Showed temp sensor errors and then stopped working completely. Running this test fixture is showing temo sensor is bad but that cant be either. Something is wrong and I dont know how to find the problem. Please advise. Thank you. Did you find a solution for this error? I have 3 boards with this same error. Thanks for answering
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: Akhan.96 on June 09, 2022, 10:47:08 PM
2 of my hashboards are not working and this is kernal log, someone please help in identifying the issue. And also, I can feel the current when the ASIC is turned on. 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: 0xc2, Chip ID: 0xda
nand: Macronix MX30LF2GE8AB
nand: 256 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 64
Bad block table found at page 131008, version 0x01
Bad block table found at page 130944, version 0x01
nand_read_bbt: bad block at 0x00000ff60000
nand_read_bbt: bad block at 0x00000ff80000
nand_read_bbt: bad block at 0x00000ffa0000
nand_read_bbt: bad block at 0x00000ffc0000
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: 129024 bytes
ubi0: min./max. I/O unit sizes: 2048/2048, sub-page size 512
ubi0: VID header offset: 512 (aligned 512), data offset: 2048
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: 34/13, WL threshold: 4096, image sequence number: 1567270514
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: 129024 bytes (126 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
UBIFS (ubi0:0): FS size: 1419264 bytes (1 MiB, 11 LEBs), journal size 903169 bytes (0 MiB, 5 LEBs)
UBIFS (ubi0:0): reserved for root: 67035 bytes (65 KiB)
UBIFS (ubi0:0): media format: w4/r0 (latest is w4/r0), UUID 47B540C7-9D9A-47A8-BA37-D4081EFEDE2D, small LPT model
ubi1: attaching mtd5
ubi1 warning: ubi_io_read: error -74 (ECC error) while reading 64 bytes from PEB 876:0, read only 64 bytes, retry
ubi1 warning: ubi_io_read: error -74 (ECC error) while reading 64 bytes from PEB 876:0, read only 64 bytes, retry
ubi1 warning: ubi_io_read: error -74 (ECC error) while reading 64 bytes from PEB 876:0, read only 64 bytes, retry
ubi1 error: ubi_io_read: error -74 (ECC error) while reading 64 bytes from PEB 876:0, read 64 bytes
CPU: 0 PID: 717 Comm: ubiattach Not tainted 4.6.0-xilinx-gff8137b-dirty #25
Hardware name: Xilinx Zynq Platform
[<c010e718>] (unwind_backtrace) from [<c010a8d0>] (show_stack+0x10/0x14)
[<c010a8d0>] (show_stack) from [<c02fcea4>] (dump_stack+0x84/0xa4)
[<c02fcea4>] (dump_stack) from [<c0405d64>] (ubi_io_read+0x1d4/0x2a8)
[<c0405d64>] (ubi_io_read) from [<c0406050>] (ubi_io_read_ec_hdr+0x68/0x1cc)
[<c0406050>] (ubi_io_read_ec_hdr) from [<c040a1d4>] (ubi_attach+0x130/0x1194)
[<c040a1d4>] (ubi_attach) from [<c0400b28>] (ubi_attach_mtd_dev+0x62c/0xaf8)
[<c0400b28>] (ubi_attach_mtd_dev) from [<c0401ff8>] (ctrl_cdev_ioctl+0xf0/0x1ec)
[<c0401ff8>] (ctrl_cdev_ioctl) from [<c01d6b88>] (vfs_ioctl+0x20/0x34)
[<c01d6b88>] (vfs_ioctl) from [<c01d7488>] (do_vfs_ioctl+0x7d8/0x8b0)
[<c01d7488>] (do_vfs_ioctl) from [<c01d7594>] (SyS_ioctl+0x34/0x5c)
[<c01d7594>] (SyS_ioctl) from [<c0106f00>] (ret_fast_syscall+0x0/0x3c)
ubi1 warning: ubi_io_read: error -74 (ECC error) while reading 512 bytes from PEB 876:512, read only 512 bytes, retry
ubi1 warning: ubi_io_read: error -74 (ECC error) while reading 512 bytes from PEB 876:512, read only 512 bytes, retry
ubi1 warning: ubi_io_read: error -74 (ECC error) while reading 512 bytes from PEB 876:512, read only 512 bytes, retry
ubi1 error: ubi_io_read: error -74 (ECC error) while reading 512 bytes from PEB 876:512, read 512 bytes
CPU: 0 PID: 717 Comm: ubiattach Not tainted 4.6.0-xilinx-gff8137b-dirty #25
Hardware name: Xilinx Zynq Platform
[<c010e718>] (unwind_backtrace) from [<c010a8d0>] (show_stack+0x10/0x14)
[<c010a8d0>] (show_stack) from [<c02fcea4>] (dump_stack+0x84/0xa4)
[<c02fcea4>] (dump_stack) from [<c0405d64>] (ubi_io_read+0x1d4/0x2a8)
[<c0405d64>] (ubi_io_read) from [<c0406220>] (ubi_io_read_vid_hdr+0x6c/0x1d8)
[<c0406220>] (ubi_io_read_vid_hdr) from [<c040a290>] (ubi_attach+0x1ec/0x1194)
[<c040a290>] (ubi_attach) from [<c0400b28>] (ubi_attach_mtd_dev+0x62c/0xaf8)
[<c0400b28>] (ubi_attach_mtd_dev) from [<c0401ff8>] (ctrl_cdev_ioctl+0xf0/0x1ec)
[<c0401ff8>] (ctrl_cdev_ioctl) from [<c01d6b88>] (vfs_ioctl+0x20/0x34)
[<c01d6b88>] (vfs_ioctl) from [<c01d7488>] (do_vfs_ioctl+0x7d8/0x8b0)
[<c01d7488>] (do_vfs_ioctl) from [<c01d7594>] (SyS_ioctl+0x34/0x5c)
[<c01d7594>] (SyS_ioctl) from [<c0106f00>] (ret_fast_syscall+0x0/0x3c)
ubi1 warning: ubi_io_read: error -74 (ECC error) while reading 64 bytes from PEB 1018:0, read only 64 bytes, retry
ubi1 warning: ubi_io_read: error -74 (ECC error) while reading 64 bytes from PEB 1018:0, read only 64 bytes, retry
ubi1 warning: ubi_io_read: error -74 (ECC error) while reading 64 bytes from PEB 1018:0, read only 64 bytes, retry
ubi1 error: ubi_io_read: error -74 (ECC error) while reading 64 bytes from PEB 1018:0, read 64 bytes
CPU: 0 PID: 717 Comm: ubiattach Not tainted 4.6.0-xilinx-gff8137b-dirty #25
Hardware name: Xilinx Zynq Platform
[<c010e718>] (unwind_backtrace) from [<c010a8d0>] (show_stack+0x10/0x14)
[<c010a8d0>] (show_stack) from [<c02fcea4>] (dump_stack+0x84/0xa4)
[<c02fcea4>] (dump_stack) from [<c0405d64>] (ubi_io_read+0x1d4/0x2a8)
[<c0405d64>] (ubi_io_read) from [<c0406050>] (ubi_io_read_ec_hdr+0x68/0x1cc)
[<c0406050>] (ubi_io_read_ec_hdr) from [<c040a1d4>] (ubi_attach+0x130/0x1194)
[<c040a1d4>] (ubi_attach) from [<c0400b28>] (ubi_attach_mtd_dev+0x62c/0xaf8)
[<c0400b28>] (ubi_attach_mtd_dev) from [<c0401ff8>] (ctrl_cdev_ioctl+0xf0/0x1ec)
[<c0401ff8>] (ctrl_cdev_ioctl) from [<c01d6b88>] (vfs_ioctl+0x20/0x34)
[<c01d6b88>] (vfs_ioctl) from [<c01d7488>] (do_vfs_ioctl+0x7d8/0x8b0)
[<c01d7488>] (do_vfs_ioctl) from [<c01d7594>] (SyS_ioctl+0x34/0x5c)
[<c01d7594>] (SyS_ioctl) from [<c0106f00>] (ret_fast_syscall+0x0/0x3c)
ubi1 warning: ubi_io_read: error -74 (ECC error) while reading 512 bytes from PEB 1018:512, read only 512 bytes, retry
ubi1 warning: ubi_io_read: error -74 (ECC error) while reading 512 bytes from PEB 1018:512, read only 512 bytes, retry
ubi1 warning: ubi_io_read: error -74 (ECC error) while reading 512 bytes from PEB 1018:512, read only 512 bytes, retry
ubi1 error: ubi_io_read: error -74 (ECC error) while reading 512 bytes from PEB 1018:512, read 512 bytes
CPU: 0 PID: 717 Comm: ubiattach Not tainted 4.6.0-xilinx-gff8137b-dirty #25
Hardware name: Xilinx Zynq Platform
[<c010e718>] (unwind_backtrace) from [<c010a8d0>] (show_stack+0x10/0x14)
[<c010a8d0>] (show_stack) from [<c02fcea4>] (dump_stack+0x84/0xa4)
[<c02fcea4>] (dump_stack) from [<c0405d64>] (ubi_io_read+0x1d4/0x2a8)
[<c0405d64>] (ubi_io_read) from [<c0406220>] (ubi_io_read_vid_hdr+0x6c/0x1d8)
[<c0406220>] (ubi_io_read_vid_hdr) from [<c040a290>] (ubi_attach+0x1ec/0x1194)
[<c040a290>] (ubi_attach) from [<c0400b28>] (ubi_attach_mtd_dev+0x62c/0xaf8)
[<c0400b28>] (ubi_attach_mtd_dev) from [<c0401ff8>] (ctrl_cdev_ioctl+0xf0/0x1ec)
[<c0401ff8>] (ctrl_cdev_ioctl) from [<c01d6b88>] (vfs_ioctl+0x20/0x34)
[<c01d6b88>] (vfs_ioctl) from [<c01d7488>] (do_vfs_ioctl+0x7d8/0x8b0)
[<c01d7488>] (do_vfs_ioctl) from [<c01d7594>] (SyS_ioctl+0x34/0x5c)
[<c01d7594>] (SyS_ioctl) from [<c0106f00>] (ret_fast_syscall+0x0/0x3c)
ubi1: scanning is finished
ubi1: attached mtd5 (name "reserve1", size 128 MiB)
ubi1: PEB size: 131072 bytes (128 KiB), LEB size: 129024 bytes
ubi1: min./max. I/O unit sizes: 2048/2048, sub-page size 512
ubi1: VID header offset: 512 (aligned 512), data offset: 2048
ubi1: good PEBs: 1019, bad PEBs: 5, corrupted PEBs: 0
ubi1: user volume: 1, internal volumes: 1, max. volumes count: 128
ubi1: max/mean erase counter: 4334/2396, WL threshold: 4096, image sequence number: 1198263195
ubi1: available PEBs: 0, total reserved PEBs: 1019, PEBs reserved for bad PEB handling: 35
ubi1: background thread "ubi_bgt1d" started, PID 720
ubi1 warning: ubi_io_read: error -74 (ECC error) while reading 512 bytes from PEB 876:512, read only 512 bytes, retry
UBIFS (ubi1:0): background thread "ubifs_bgt1_0" started, PID 723
ubi1 warning: ubi_io_read: error -74 (ECC error) while reading 512 bytes from PEB 876:512, read only 512 bytes, retry
UBIFS (ubi1:0): recovery needed
ubi1 warning: ubi_io_read: error -74 (ECC error) while reading 512 bytes from PEB 876:512, read only 512 bytes, retry
ubi1 error: ubi_io_read: error -74 (ECC error) while reading 512 bytes from PEB 876:512, read 512 bytes
CPU: 0 PID: 720 Comm: ubi_bgt1d Not tainted 4.6.0-xilinx-gff8137b-dirty #25
Hardware name: Xilinx Zynq Platform
[<c010e718>] (unwind_backtrace) from [<c010a8d0>] (show_stack+0x10/0x14)
[<c010a8d0>] (show_stack) from [<c02fcea4>] (dump_stack+0x84/0xa4)
[<c02fcea4>] (dump_stack) from [<c0405d64>] (ubi_io_read+0x1d4/0x2a8)
[<c0405d64>] (ubi_io_read) from [<c0406220>] (ubi_io_read_vid_hdr+0x6c/0x1d8)
[<c0406220>] (ubi_io_read_vid_hdr) from [<c0408280>] (wear_leveling_worker+0x1e0/0x6a0)
[<c0408280>] (wear_leveling_worker) from [<c0407770>] (do_work+0xcc/0x100)
[<c0407770>] (do_work) from [<c0408dc8>] (ubi_thread+0x100/0x190)
[<c0408dc8>] (ubi_thread) from [<c0132960>] (kthread+0xdc/0xf0)
[<c0132960>] (kthread) from [<c0106fb8>] (ret_from_fork+0x14/0x3c)
ubi1 warning: ubi_io_read: error -74 (ECC error) while reading 512 bytes from PEB 876:512, read only 512 bytes, retry
ubi1 warning: ubi_io_read: error -74 (ECC error) while reading 512 bytes from PEB 876:512, read only 512 bytes, retry
ubi1 warning: ubi_io_read: error -74 (ECC error) while reading 512 bytes from PEB 876:512, read only 512 bytes, retry
ubi1 error: ubi_io_read: error -74 (ECC error) while reading 512 bytes from PEB 876:512, read 512 bytes
CPU: 0 PID: 720 Comm: ubi_bgt1d Not tainted 4.6.0-xilinx-gff8137b-dirty #25
Hardware name: Xilinx Zynq Platform
[<c010e718>] (unwind_backtrace) from [<c010a8d0>] (show_stack+0x10/0x14)
[<c010a8d0>] (show_stack) from [<c02fcea4>] (dump_stack+0x84/0xa4)
[<c02fcea4>] (dump_stack) from [<c0405d64>] (ubi_io_read+0x1d4/0x2a8)
[<c0405d64>] (ubi_io_read) from [<c0406220>] (ubi_io_read_vid_hdr+0x6c/0x1d8)
[<c0406220>] (ubi_io_read_vid_hdr) from [<c0408280>] (wear_leveling_worker+0x1e0/0x6a0)
[<c0408280>] (wear_leveling_worker) from [<c0407770>] (do_work+0xcc/0x100)
[<c0407770>] (do_work) from [<c0408dc8>] (ubi_thread+0x100/0x190)
[<c0408dc8>] (ubi_thread) from [<c0132960>] (kthread+0xdc/0xf0)
[<c0132960>] (kthread) from [<c0106fb8>] (ret_from_fork+0x14/0x3c)
UBIFS (ubi1:0): recovery completed
UBIFS (ubi1:0): UBIFS: mounted UBI device 1, volume 0, name "reserve1"
UBIFS (ubi1:0): LEB size: 129024 bytes (126 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
UBIFS (ubi1:0): FS size: 125024256 bytes (119 MiB, 969 LEBs), journal size 6322176 bytes (6 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 8D25A753-B1E6-461F-BA97-EE4B6F2054F5, 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 0xcfb40000
*base_vir_addr = 0xab013
In fpga mem driver!
request_mem_region OK!
fpga mem virtual address is 0xd2000000
random: nonblocking pool is initialized
Jun 9 22:30:39 (none) local0.notice bmminer: set_start_time_point total_tv_start_sys=328 total_tv_end_sys=329
Jun 9 22:30:42 (none) local0.notice cgminer: cgminer_socket_init reg bitmain_api_detect return: 0
Jun 9 22:30:43 (none) local0.notice cgminer: cgminer_socket_init reg bitmain_update_job return: 0
Jun 9 22:30:44 (none) local0.notice cgminer: cgminer_socket_init reg bitmain_shutdown return: 0
Jun 9 22:30:44 (none) local0.err cgminer: Miner compile time: Thu Apr 23 16:29:07 CST 2020 type: Antminer T17
Jun 9 22:30:44 (none) local0.notice cgminer[1001]: about to send detect
Jun 9 22:30:44 (none) local0.notice cgminer[1001]: set_start_time_point total_tv_start_sys=333 total_tv_end_sys=334
Jun 9 22:30:44 (none) local0.notice cgminer[1001]: Probing for an alive pool
Jun 9 22:30:50 (none) local0.notice cgminer[1001]: LOW POWER MODE!
Jun 9 22:30:50 (none) local0.notice cgminer[1001]: Switching to pool 1 stratum+tcp://bs.poolbinance.com:3333 - first alive pool
Jun 9 22:30:50 (none) local0.notice cgminer[1001]: in stratum_sthread
Jun 9 22:30:50 (none) local0.notice cgminer[1001]: Pool 1 difficulty changed to 131072
Jun 9 22:30:50 (none) local0.notice cgminer[1001]: LOW POWER MODE!
Jun 9 22:30:50 (none) local0.notice cgminer[1001]: in stratum_sthread
Jun 9 22:30:50 (none) local0.notice cgminer[1001]: Network diff set to 30.3T
Jun 9 22:30:50 (none) local0.notice cgminer[1001]: POOL 1 support ab mode!
Jun 9 22:30:50 (none) local0.notice cgminer[1001]: update job
Jun 9 22:30:50 (none) local0.notice cgminer[1001]: job buf total len:2588, offset:2588
Jun 9 22:30:50 (none) local0.notice cgminer[1001]: about to send job, size is 2588
Jun 9 22:30:50 (none) local0.notice bmminer: bitmain_update_job_cb, rec job data 0xb4800480 size: 2588
Jun 9 22:30:50 (none) local0.notice bmminer: parse job buf len:2588
Jun 9 22:30:51 (none) local0.notice cgminer[1001]: LOW POWER MODE!
Jun 9 22:30:51 (none) local0.warn cgminer[1001]: Pool 0 stratum+tcp://sha256.poolbinance.com:443 alive, testing stability
Jun 9 22:30:51 (none) local0.notice cgminer[1001]: in stratum_sthread
Jun 9 22:30:51 (none) local0.notice cgminer[1001]: Pool 0 difficulty changed to 131072
Jun 9 22:30:51 (none) local0.notice cgminer[1001]: POOL 0 support ab mode!
Jun 9 22:30:55 (none) local0.warn cgminer[1001]: API running in IP access mode on port 4028 (16)
Jun 9 22:30:55 (none) local0.warn cgminer[1001]: Pool 0 stratum+tcp://sha256.poolbinance.com:443 stable for >120 seconds
Jun 9 22:30:55 (none) local0.warn cgminer[1001]: Switching to pool 0 stratum+tcp://sha256.poolbinance.com:443
Jun 9 22:31:22 (none) local0.notice cgminer[1001]: update job
Jun 9 22:31:22 (none) local0.notice cgminer[1001]: job buf total len:2591, offset:2591
Jun 9 22:31:22 (none) local0.notice cgminer[1001]: about to send job, size is 2591
Jun 9 22:31:22 (none) local0.notice bmminer: bitmain_update_job_cb, rec job data 0xb4800480 size: 2591
Jun 9 22:31:22 (none) local0.notice bmminer: parse job buf len:2591
Jun 9 22:31:42 (none) local0.notice bmminer: need data size:491, actual size:491
Jun 9 22:31:42 (none) local0.notice cgminer[1001]: got nonce sz 491
Jun 9 22:31:42 (none) local0.notice cgminer[1001]: Pool 0 stale share detected, submitting as user requested
Jun 9 22:31:42 (none) local0.notice cgminer[1001]: cb_bitmain_submit_nonce nonce submited
Jun 9 22:31:42 (none) local0.notice cgminer[1001]: Accepted 50b85d56 Diff 208K/131072 BTM_SOC 0 pool 0
Jun 9 22:31:50 (none) local0.notice cgminer[1001]: update job
Jun 9 22:31:50 (none) local0.notice cgminer[1001]: job buf total len:2591, offset:2591
Jun 9 22:31:50 (none) local0.notice cgminer[1001]: about to send job, size is 2591
Jun 9 22:31:50 (none) local0.notice bmminer: bitmain_update_job_cb, rec job data 0xb4800480 size: 2591
Jun 9 22:31:50 (none) local0.notice bmminer: parse job buf len:2591
Jun 9 22:31:50 (none) local0.info bmminer: (null) 0: invalid nonce - HW error
Jun 9 22:31:50 (none) local0.info bmminer: (null) 0: invalid nonce - HW error
Jun 9 22:32:16 (none) user.notice kernel: random: nonblocking pool is initialized
Jun 9 22:32:22 (none) local0.notice cgminer[1001]: update job
Jun 9 22:32:22 (none) local0.notice cgminer[1001]: job buf total len:2591, offset:2591
Jun 9 22:32:22 (none) local0.notice cgminer[1001]: about to send job, size is 2591
Jun 9 22:32:22 (none) local0.notice bmminer: bitmain_update_job_cb, rec job data 0xb4800480 size: 2591
Jun 9 22:32:22 (none) local0.notice bmminer: parse job buf len:2591
Jun 9 22:32:52 (none) local0.notice cgminer[1001]: update job
Jun 9 22:32:52 (none) local0.notice cgminer[1001]: job buf total len:2591, offset:2591
Jun 9 22:32:52 (none) local0.notice cgminer[1001]: about to send job, size is 2591
Jun 9 22:32:52 (none) local0.notice bmminer: bitmain_update_job_cb, rec job data 0xb4800480 size: 2591
Jun 9 22:32:52 (none) local0.notice bmminer: parse job buf len:2591
Jun 9 22:33:24 (none) local0.notice cgminer[1001]: update job
Jun 9 22:33:24 (none) local0.notice cgminer[1001]: job buf total len:2591, offset:2591
Jun 9 22:33:24 (none) local0.notice cgminer[1001]: about to send job, size is 2591
Jun 9 22:33:24 (none) local0.notice bmminer: bitmain_update_job_cb, rec job data 0xb4800480 size: 2591
Jun 9 22:33:24 (none) local0.notice bmminer: parse job buf len:2591
Jun 9 22:33:57 (none) local0.notice bmminer: need data size:491, actual size:491
Jun 9 22:33:57 (none) local0.notice cgminer[1001]: got nonce sz 491
Jun 9 22:33:57 (none) local0.notice cgminer[1001]: Pool 0 stale share detected, submitting as user requested
Jun 9 22:33:57 (none) local0.notice cgminer[1001]: cb_bitmain_submit_nonce nonce submited
Jun 9 22:33:57 (none) local0.notice cgminer[1001]: Accepted 780c2d47 Diff 140K/131072 BTM_SOC 0 pool 0
Jun 9 22:33:58 (none) local0.notice cgminer[1001]: update job
Jun 9 22:33:58 (none) local0.notice cgminer[1001]: job buf total len:2591, offset:2591
Jun 9 22:33:58 (none) local0.notice cgminer[1001]: about to send job, size is 2591
Jun 9 22:33:58 (none) local0.notice bmminer: bitmain_update_job_cb, rec job data 0xb4800480 size: 2591
Jun 9 22:33:58 (none) local0.notice bmminer: parse job buf len:2591
Jun 9 22:34:18 (none) local0.notice bmminer: need data size:491, actual size:491
Jun 9 22:34:18 (none) local0.notice cgminer[1001]: got nonce sz 491
Jun 9 22:34:18 (none) local0.notice cgminer[1001]: Pool 0 stale share detected, submitting as user requested
Jun 9 22:34:18 (none) local0.notice cgminer[1001]: cb_bitmain_submit_nonce nonce submited
Jun 9 22:34:18 (none) local0.notice cgminer[1001]: Accepted 5174cdbc Diff 206K/131072 BTM_SOC 0 pool 0
Jun 9 22:34:20 (none) local0.notice bmminer: need data size:491, actual size:491
Jun 9 22:34:20 (none) local0.notice cgminer[1001]: got nonce sz 491
Jun 9 22:34:20 (none) local0.notice cgminer[1001]: Pool 0 stale share detected, submitting as user requested
Jun 9 22:34:20 (none) local0.notice cgminer[1001]: cb_bitmain_submit_nonce nonce submited
Jun 9 22:34:20 (none) local0.notice cgminer[1001]: Accepted 576c3c0d Diff 192K/131072 BTM_SOC 0 pool 0
Jun 9 22:34:21 (none) local0.notice cgminer[1001]: Pool 0 difficulty changed to 65536
Jun 9 22:34:22 (none) local0.notice bmminer: need data size:491, actual size:491
Jun 9 22:34:22 (none) local0.notice cgminer[1001]: got nonce sz 491
Jun 9 22:34:22 (none) local0.notice cgminer[1001]: Pool 0 stale share detected, submitting as user requested
Jun 9 22:34:22 (none) local0.notice cgminer[1001]: cb_bitmain_submit_nonce nonce submited
Jun 9 22:34:22 (none) local0.notice cgminer[1001]: Accepted 4799399e Diff 234K/131072 BTM_SOC 0 pool 0
Jun 9 22:34:22 (none) local0.notice cgminer[1001]: update job
Jun 9 22:34:22 (none) local0.notice cgminer[1001]: job buf total len:2591, offset:2591
Jun 9 22:34:22 (none) local0.notice cgminer[1001]: about to send job, size is 2591
Jun 9 22:34:22 (none) local0.notice bmminer: bitmain_update_job_cb, rec job data 0xb4800480 size: 2591
Jun 9 22:34:22 (none) local0.notice bmminer: parse job buf len:2591
Jun 9 22:34:25 (none) local0.notice bmminer: need data size:491, actual size:491
Jun 9 22:34:25 (none) local0.notice cgminer[1001]: got nonce sz 491
Jun 9 22:34:25 (none) local0.notice cgminer[1001]: Pool 0 stale share detected, submitting as user requested
Jun 9 22:34:25 (none) local0.notice cgminer[1001]: cb_bitmain_submit_nonce nonce submited
Jun 9 22:34:25 (none) local0.notice cgminer[1001]: Accepted 2d36be56 Diff 371K/65536 BTM_SOC 0 pool 0
Jun 9 22:34:27 (none) local0.info bmminer: (null) 0: invalid nonce - HW error
Jun 9 22:34:27 (none) local0.info bmminer: (null) 0: invalid nonce - HW error
Jun 9 22:34:42 (none) local0.info bmminer: (null) 0: invalid nonce - HW error
Jun 9 22:34:42 (none) local0.info bmminer: (null) 0: invalid nonce - HW error
Jun 9 22:34:54 (none) local0.notice cgminer[1001]: update job
Jun 9 22:34:54 (none) local0.notice cgminer[1001]: job buf total len:2591, offset:2591
Jun 9 22:34:54 (none) local0.notice cgminer[1001]: about to send job, size is 2591
Jun 9 22:34:54 (none) local0.notice bmminer: bitmain_update_job_cb, rec job data 0xb4800480 size: 2591
Jun 9 22:34:54 (none) local0.notice bmminer: parse job buf len:2591
Jun 9 22:35:17 (none) local0.notice bmminer: need data size:491, actual size:491
Jun 9 22:35:17 (none) local0.notice cgminer[1001]: got nonce sz 491
Jun 9 22:35:17 (none) local0.notice cgminer[1001]: Pool 0 stale share detected, submitting as user requested
Jun 9 22:35:17 (none) local0.notice cgminer[1001]: cb_bitmain_submit_nonce nonce submited
Jun 9 22:35:17 (none) local0.notice cgminer[1001]: Accepted f42b05d4 Diff 68.7K/65536 BTM_SOC 0 pool 0
Jun 9 22:35:22 (none) local0.notice cgminer[1001]: update job
Jun 9 22:35:22 (none) local0.notice cgminer[1001]: job buf total len:2591, offset:2591
Jun 9 22:35:22 (none) local0.notice cgminer[1001]: about to send job, size is 2591
Jun 9 22:35:22 (none) local0.notice bmminer: bitmain_update_job_cb, rec job data 0xb4800480 size: 2591
Jun 9 22:35:22 (none) local0.notice bmminer: parse job buf len:2591
Jun 9 22:35:31 (none) local0.notice bmminer: need data size:491, actual size:491
Jun 9 22:35:31 (none) local0.notice cgminer[1001]: got nonce sz 491
Jun 9 22:35:31 (none) local0.notice cgminer[1001]: Pool 0 stale share detected, submitting as user requested
Jun 9 22:35:31 (none) local0.notice cgminer[1001]: cb_bitmain_submit_nonce nonce submited
Jun 9 22:35:31 (none) local0.notice cgminer[1001]: Accepted 09b38038 Diff 1.73M/65536 BTM_SOC 0 pool 0
Jun 9 22:35:36 (none) local0.info bmminer: (null) 0: invalid nonce - HW error
Jun 9 22:35:45 (none) local0.notice bmminer: need data size:491, actual size:491
Jun 9 22:35:45 (none) local0.notice cgminer[1001]: got nonce sz 491
Jun 9 22:35:45 (none) local0.notice cgminer[1001]: Pool 0 stale share detected, submitting as user requested
Jun 9 22:35:45 (none) local0.notice cgminer[1001]: cb_bitmain_submit_nonce nonce submited
Jun 9 22:35:45 (none) local0.notice cgminer[1001]: Accepted eaa092d6 Diff 71.5K/65536 BTM_SOC 0 pool 0
Jun 9 22:35:49 (none) local0.notice bmminer: need data size:491, actual size:491
Jun 9 22:35:49 (none) local0.notice cgminer[1001]: got nonce sz 491
Jun 9 22:35:49 (none) local0.notice cgminer[1001]: Pool 0 stale share detected, submitting as user requested
Jun 9 22:35:49 (none) local0.notice cgminer[1001]: cb_bitmain_submit_nonce nonce submited
Jun 9 22:35:49 (none) local0.notice cgminer[1001]: Accepted 96f2d041 Diff 111K/65536 BTM_SOC 0 pool 0
Jun 9 22:35:51 (none) local0.notice bmminer: need data size:491, actual size:491
Jun 9 22:35:51 (none) local0.notice cgminer[1001]: got nonce sz 491
Jun 9 22:35:51 (none) local0.notice cgminer[1001]: Pool 0 stale share detected, submitting as user requested
Jun 9 22:35:51 (none) local0.notice cgminer[1001]: cb_bitmain_submit_nonce nonce submited
Jun 9 22:35:51 (none) local0.notice cgminer[1001]: Accepted ab4853f4 Diff 97.9K/65536 BTM_SOC 0 pool 0
Jun 9 22:35:54 (none) local0.notice cgminer[1001]: update job
Jun 9 22:35:54 (none) local0.notice cgminer[1001]: job buf total len:2591, offset:2591
Jun 9 22:35:54 (none) local0.notice cgminer[1001]: about to send job, size is 2591
Jun 9 22:35:54 (none) local0.notice bmminer: bitmain_update_job_cb, rec job data 0xb4800480 size: 2591
Jun 9 22:35:54 (none) local0.notice bmminer: parse job buf len:2591
Jun 9 22:36:09 (none) local0.notice bmminer: need data size:491, actual size:491
Jun 9 22:36:09 (none) local0.notice cgminer[1001]: got nonce sz 491
Jun 9 22:36:09 (none) local0.notice cgminer[1001]: Pool 0 stale share detected, submitting as user requested
Jun 9 22:36:09 (none) local0.notice cgminer[1001]: cb_bitmain_submit_nonce nonce submited
Jun 9 22:36:09 (none) local0.notice cgminer[1001]: Accepted addf7af1 Diff 96.5K/65536 BTM_SOC 0 pool 0
Jun 9 22:36:24 (none) local0.notice bmminer: need data size:491, actual size:491
Jun 9 22:36:24 (none) local0.notice cgminer[1001]: got nonce sz 491
Jun 9 22:36:24 (none) local0.notice cgminer[1001]: Pool 0 stale share detected, submitting as user requested
Jun 9 22:36:24 (none) local0.notice cgminer[1001]: cb_bitmain_submit_nonce nonce submited
Jun 9 22:36:24 (none) local0.notice cgminer[1001]: Accepted 81716e83 Diff 130K/65536 BTM_SOC 0 pool 0
Jun 9 22:36:24 (none) local0.notice cgminer[1001]: update job
Jun 9 22:36:24 (none) local0.notice cgminer[1001]: job buf total len:2591, offset:2591
Jun 9 22:36:24 (none) local0.notice cgminer[1001]: about to send job, size is 2591
Jun 9 22:36:24 (none) local0.notice bmminer: bitmain_update_job_cb, rec job data 0xb4800480 size: 2591
Jun 9 22:36:24 (none) local0.notice bmminer: parse job buf len:2591
Jun 9 22:36:54 (none) local0.notice cgminer[1001]: update job
Jun 9 22:36:54 (none) local0.notice cgminer[1001]: job buf total len:2591, offset:2591
Jun 9 22:36:54 (none) local0.notice cgminer[1001]: about to send job, size is 2591
Jun 9 22:36:54 (none) local0.notice bmminer: bitmain_update_job_cb, rec job data 0xb4800480 size: 2591
Jun 9 22:36:54 (none) local0.notice bmminer: parse job buf len:2591
Jun 9 22:37:25 (none) local0.notice cgminer[1001]: update job
Jun 9 22:37:25 (none) local0.notice cgminer[1001]: job buf total len:2591, offset:2591
Jun 9 22:37:25 (none) local0.notice cgminer[1001]: about to send job, size is 2591
Jun 9 22:37:25 (none) local0.notice bmminer: bitmain_update_job_cb, rec job data 0xb4800480 size: 2591
Jun 9 22:37:25 (none) local0.notice bmminer: parse job buf len:2591
Jun 9 22:37:56 (none) local0.notice bmminer: need data size:491, actual size:491
Jun 9 22:37:56 (none) local0.notice cgminer[1001]: got nonce sz 491
Jun 9 22:37:56 (none) local0.notice cgminer[1001]: Pool 0 stale share detected, submitting as user requested
Jun 9 22:37:56 (none) local0.notice cgminer[1001]: cb_bitmain_submit_nonce nonce submited
Jun 9 22:37:56 (none) local0.notice cgminer[1001]: Accepted 07b837b6 Diff 2.17M/65536 BTM_SOC 0 pool 0
Jun 9 22:37:57 (none) local0.notice cgminer[1001]: update job
Jun 9 22:37:57 (none) local0.notice cgminer[1001]: job buf total len:2591, offset:2591
Jun 9 22:37:57 (none) local0.notice cgminer[1001]: about to send job, size is 2591
Jun 9 22:37:57 (none) local0.notice bmminer: bitmain_update_job_cb, rec job data 0xb4800480 size: 2591
Jun 9 22:37:57 (none) local0.notice bmminer: parse job buf len:2591
Jun 9 22:38:06 (none) local0.notice bmminer: need data size:491, actual size:491
Jun 9 22:38:06 (none) local0.notice cgminer[1001]: got nonce sz 491
Jun 9 22:38:06 (none) local0.notice cgminer[1001]: Pool 0 stale share detected, submitting as user requested
Jun 9 22:38:06 (none) local0.notice cgminer[1001]: cb_bitmain_submit_nonce nonce submited
Jun 9 22:38:06 (none) local0.notice cgminer[1001]: Accepted 120987b0 Diff 930K/65536 BTM_SOC 0 pool 0
Jun 9 22:38:11 (none) local0.notice cgminer[1001]: Stratum from pool 0 detected new block at height 740105
Jun 9 22:38:11 (none) local0.notice cgminer[1001]: update job
Jun 9 22:38:11 (none) local0.notice cgminer[1001]: job buf total len:2207, offset:2207
Jun 9 22:38:11 (none) local0.notice cgminer[1001]: about to send job, size is 2207
Jun 9 22:38:11 (none) local0.notice bmminer: bitmain_update_job_cb, rec job data 0xb4800480 size: 2207
Jun 9 22:38:11 (none) local0.notice bmminer: parse job buf len:2207
Jun 9 22:38:11 (none) local0.notice cgminer[1001]: update job
Jun 9 22:38:11 (none) local0.notice cgminer[1001]: job buf total len:2207, offset:2207
Jun 9 22:38:11 (none) local0.notice cgminer[1001]: about to send job, size is 2207
Jun 9 22:38:11 (none) local0.notice bmminer: bitmain_update_job_cb, rec job data 0xb4800480 size: 2207
Jun 9 22:38:11 (none) local0.notice bmminer: parse job buf len:2207
Jun 9 22:38:13 (none) local0.notice cgminer[1001]: update job
Jun 9 22:38:13 (none) local0.notice cgminer[1001]: job buf total len:2560, offset:2560
Jun 9 22:38:13 (none) local0.notice cgminer[1001]: about to send job, size is 2560
Jun 9 22:38:13 (none) local0.notice bmminer: bitmain_update_job_cb, rec job data 0xb4800480 size: 2560
Jun 9 22:38:13 (none) local0.notice bmminer: parse job buf len:2560
Jun 9 22:38:40 (none) local0.notice bmminer: need data size:491, actual size:491
Jun 9 22:38:40 (none) local0.notice cgminer[1001]: got nonce sz 491
Jun 9 22:38:40 (none) local0.notice cgminer[1001]: Pool 0 stale share detected, submitting as user requested
Jun 9 22:38:40 (none) local0.notice cgminer[1001]: cb_bitmain_submit_nonce nonce submited
Jun 9 22:38:41 (none) local0.notice cgminer[1001]: Accepted a7ba88c2 Diff 100K/65536 BTM_SOC 0 pool 0
Jun 9 22:38:43 (none) local0.notice cgminer[1001]: update job
Jun 9 22:38:43 (none) local0.notice cgminer[1001]: job buf total len:2559, offset:2559
Jun 9 22:38:43 (none) local0.notice cgminer[1001]: about to send job, size is 2559
Jun 9 22:38:43 (none) local0.notice bmminer: bitmain_update_job_cb, rec job data 0xb4800480 size: 2559
Jun 9 22:38:43 (none) local0.notice bmminer: parse job buf len:2559
Jun 9 22:38:51 (none) local0.notice bmminer: need data size:491, actual size:491
Jun 9 22:38:51 (none) local0.notice cgminer[1001]: got nonce sz 491
Jun 9 22:38:51 (none) local0.notice cgminer[1001]: Pool 0 stale share detected, submitting as user requested
Jun 9 22:38:51 (none) local0.notice cgminer[1001]: cb_bitmain_submit_nonce nonce submited
Jun 9 22:38:51 (none) local0.notice cgminer[1001]: Accepted 50d75dbc Diff 208K/65536 BTM_SOC 0 pool 0
Jun 9 22:39:07 (none) local0.notice bmminer: need data size:491, actual size:491
Jun 9 22:39:07 (none) local0.notice cgminer[1001]: got nonce sz 491
Jun 9 22:39:07 (none) local0.notice cgminer[1001]: Pool 0 stale share detected, submitting as user requested
Jun 9 22:39:07 (none) local0.notice cgminer[1001]: cb_bitmain_submit_nonce nonce submited
Jun 9 22:39:07 (none) local0.notice cgminer[1001]: Accepted 44c67cba Diff 244K/65536 BTM_SOC 0 pool 0
Jun 9 22:39:10 (none) local0.notice bmminer: need data size:491, actual size:491
Jun 9 22:39:10 (none) local0.notice cgminer[1001]: got nonce sz 491
Jun 9 22:39:10 (none) local0.notice cgminer[1001]: Pool 0 stale share detected, submitting as user requested
Jun 9 22:39:10 (none) local0.notice cgminer[1001]: cb_bitmain_submit_nonce nonce submited
Jun 9 22:39:10 (none) local0.notice cgminer[1001]: Accepted 369f909c Diff 307K/65536 BTM_SOC 0 pool 0
Jun 9 22:39:13 (none) local0.notice cgminer[1001]: update job
Jun 9 22:39:13 (none) local0.notice cgminer[1001]: job buf total len:2559, offset:2559
Jun 9 22:39:13 (none) local0.notice cgminer[1001]: about to send job, size is 2559
Jun 9 22:39:13 (none) local0.notice bmminer: bitmain_update_job_cb, rec job data 0xb4800480 size: 2559
Jun 9 22:39:13 (none) local0.notice bmminer: parse job buf len:2559
Jun 9 22:39:16 (none) local0.notice bmminer: need data size:491, actual size:491
Jun 9 22:39:16 (none) local0.notice cgminer[1001]: got nonce sz 491
Jun 9 22:39:16 (none) local0.notice cgminer[1001]: Pool 0 stale share detected, submitting as user requested
Jun 9 22:39:16 (none) local0.notice cgminer[1001]: cb_bitmain_submit_nonce nonce submited
Jun 9 22:39:16 (none) local0.notice cgminer[1001]: Accepted db12fb04 Diff 76.6K/65536 BTM_SOC 0 pool 0
Jun 9 22:39:43 (none) local0.notice cgminer[1001]: update job
Jun 9 22:39:43 (none) local0.notice cgminer[1001]: job buf total len:2559, offset:2559
Jun 9 22:39:43 (none) local0.notice cgminer[1001]: about to send job, size is 2559
Jun 9 22:39:43 (none) local0.notice bmminer: bitmain_update_job_cb, rec job data 0xb4800480 size: 2559
Jun 9 22:39:43 (none) local0.notice bmminer: parse job buf len:2559
Jun 9 22:39:49 (none) local0.notice bmminer: need data size:491, actual size:491
Jun 9 22:39:49 (none) local0.notice cgminer[1001]: got nonce sz 491
Jun 9 22:39:49 (none) local0.notice cgminer[1001]: Pool 0 stale share detected, submitting as user requested
Jun 9 22:39:49 (none) local0.notice cgminer[1001]: cb_bitmain_submit_nonce nonce submited
Jun 9 22:39:50 (none) local0.notice cgminer[1001]: Accepted 8c7fb881 Diff 119K/65536 BTM_SOC 0 pool 0
Jun 9 22:39:51 (none) local0.notice bmminer: need data size:491, actual size:491
Jun 9 22:39:51 (none) local0.notice cgminer[1001]: got nonce sz 491
Jun 9 22:39:51 (none) local0.notice cgminer[1001]: Pool 0 stale share detected, submitting as user requested
Jun 9 22:39:51 (none) local0.notice cgminer[1001]: cb_bitmain_submit_nonce nonce submited
Jun 9 22:39:51 (none) local0.notice cgminer[1001]: Accepted bfb82bc7 Diff 87.5K/65536 BTM_SOC 0 pool 0
Jun 9 22:39:57 (none) local0.notice bmminer: need data size:491, actual size:491
Jun 9 22:39:57 (none) local0.notice cgminer[1001]: got nonce sz 491
Jun 9 22:39:57 (none) local0.notice cgminer[1001]: Pool 0 stale share detected, submitting as user requested
Jun 9 22:39:57 (none) local0.notice cgminer[1001]: cb_bitmain_submit_nonce nonce submited
Jun 9 22:39:58 (none) local0.notice cgminer[1001]: Accepted 27768741 Diff 425K/65536 BTM_SOC 0 pool 0
Jun 9 22:40:00 (none) local0.notice bmminer: need data size:491, actual size:491
Jun 9 22:40:00 (none) local0.notice cgminer[1001]: got nonce sz 491
Jun 9 22:40:00 (none) local0.notice cgminer[1001]: Pool 0 stale share detected, submitting as user requested
Jun 9 22:40:00 (none) local0.notice cgminer[1001]: cb_bitmain_submit_nonce nonce submited
Jun 9 22:40:00 (none) local0.notice cgminer[1001]: Accepted 8f1ae91b Diff 117K/65536 BTM_SOC 0 pool 0
Jun 9 22:40:07 (none) local0.notice bmminer: need data size:491, actual size:491
Jun 9 22:40:07 (none) local0.notice cgminer[1001]: got nonce sz 491
Jun 9 22:40:07 (none) local0.notice cgminer[1001]: Pool 0 stale share detected, submitting as user requested
Jun 9 22:40:07 (none) local0.notice cgminer[1001]: cb_bitmain_submit_nonce nonce submited
Jun 9 22:40:07 (none) local0.notice cgminer[1001]: Accepted 84a54b66 Diff 126K/65536 BTM_SOC 0 pool 0
Jun 9 22:40:12 (none) local0.notice bmminer: need data size:491, actual size:491
Jun 9 22:40:12 (none) local0.notice cgminer[1001]: got nonce sz 491
Jun 9 22:40:12 (none) local0.notice cgminer[1001]: Pool 0 stale share detected, submitting as user requested
Jun 9 22:40:12 (none) local0.notice cgminer[1001]: cb_bitmain_submit_nonce nonce submited
Jun 9 22:40:13 (none) local0.notice cgminer[1001]: Accepted b279646a Diff 94K/65536 BTM_SOC 0 pool 0
Jun 9 22:40:15 (none) local0.notice cgminer[1001]: update job
Jun 9 22:40:15 (none) local0.notice cgminer[1001]: job buf total len:2559, offset:2559
Jun 9 22:40:15 (none) local0.notice cgminer[1001]: about to send job, size is 2559
Jun 9 22:40:15 (none) local0.notice bmminer: bitmain_update_job_cb, rec job data 0xb4800480 size: 2559
Jun 9 22:40:15 (none) local0.notice bmminer: parse job buf len:2559
Jun 9 22:40:16 (none) local0.notice bmminer: need data size:491, actual size:491
Jun 9 22:40:16 (none) local0.notice cgminer[1001]: got nonce sz 491
Jun 9 22:40:16 (none) local0.notice cgminer[1001]: Pool 0 stale share detected, submitting as user requested
Jun 9 22:40:16 (none) local0.notice cgminer[1001]: cb_bitmain_submit_nonce nonce submited
Jun 9 22:40:16 (none) local0.notice cgminer[1001]: Accepted 6eaaf1ff Diff 152K/65536 BTM_SOC 0 pool 0
Jun 9 22:40:22 (none) local0.notice bmminer: need data size:491, actual size:491
Jun 9 22:40:22 (none) local0.notice cgminer[1001]: got nonce sz 491
Jun 9 22:40:22 (none) local0.notice cgminer[1001]: Pool 0 stale share detected, submitting as user requested
Jun 9 22:40:22 (none) local0.notice cgminer[1001]: cb_bitmain_submit_nonce nonce submited
Jun 9 22:40:22 (none) local0.notice cgminer[1001]: Accepted 7d258eb8 Diff 134K/65536 BTM_SOC 0 pool 0
Jun 9 22:40:28 (none) local0.notice bmminer: need data size:491, actual size:491
Jun 9 22:40:28 (none) local0.notice cgminer[1001]: got nonce sz 491
Jun 9 22:40:28 (none) local0.notice cgminer[1001]: Pool 0 stale share detected, submitting as user requested
Jun 9 22:40:28 (none) local0.notice cgminer[1001]: cb_bitmain_submit_nonce nonce submited
Jun 9 22:40:28 (none) local0.notice cgminer[1001]: Accepted 2deb0936 Diff 365K/65536 BTM_SOC 0 pool 0
Jun 9 22:40:43 (none) local0.notice cgminer[1001]: update job
Jun 9 22:40:43 (none) local0.notice cgminer[1001]: job buf total len:2559, offset:2559
Jun 9 22:40:43 (none) local0.notice cgminer[1001]: about to send job, size is 2559
Jun 9 22:40:43 (none) local0.notice bmminer: bitmain_update_job_cb, rec job data 0xb4800480 size: 2559
Jun 9 22:40:43 (none) local0.notice bmminer: parse job buf len:2559
Jun 9 22:41:08 (none) local0.notice bmminer: need data size:491, actual size:491
Jun 9 22:41:08 (none) local0.notice cgminer[1001]: got nonce sz 491
Jun 9 22:41:08 (none) local0.notice cgminer[1001]: Pool 0 stale share detected, submitting as user requested
Jun 9 22:41:08 (none) local0.notice cgminer[1001]: cb_bitmain_submit_nonce nonce submited
Jun 9 22:41:08 (none) local0.notice cgminer[1001]: Accepted b48ec3e4 Diff 92.9K/65536 BTM_SOC 0 pool 0
Jun 9 22:41:15 (none) local0.notice cgminer[1001]: update job
Jun 9 22:41:15 (none) local0.notice cgminer[1001]: job buf total len:2559, offset:2559
Jun 9 22:41:15 (none) local0.notice cgminer[1001]: about to send job, size is 2559
Jun 9 22:41:15 (none) local0.notice bmminer: bitmain_update_job_cb, rec job data 0xb4800480 size: 2559
Jun 9 22:41:15 (none) local0.notice bmminer: parse job buf len:2559
Jun 9 22:41:43 (none) local0.notice cgminer[1001]: update job
Jun 9 22:41:43 (none) local0.notice cgminer[1001]: job buf total len:2559, offset:2559
Jun 9 22:41:43 (none) local0.notice cgminer[1001]: about to send job, size is 2559
Jun 9 22:41:43 (none) local0.notice bmminer: bitmain_update_job_cb, rec job data 0xb4800480 size: 2559
Jun 9 22:41:43 (none) local0.notice bmminer: parse job buf len:2559
Jun 9 22:41:49 (none) local0.notice bmminer: need data size:491, actual size:491
Jun 9 22:41:49 (none) local0.notice cgminer[1001]: got nonce sz 491
Jun 9 22:41:49 (none) local0.notice cgminer[1001]: Pool 0 stale share detected, submitting as user requested
Jun 9 22:41:49 (none) local0.notice cgminer[1001]: cb_bitmain_submit_nonce nonce submited
Jun 9 22:41:49 (none) local0.notice cgminer[1001]: Accepted 1a1df987 Diff 642K/65536 BTM_SOC 0 pool 0
Jun 9 22:42:15 (none) local0.notice cgminer[1001]: update job
Jun 9 22:42:15 (none) local0.notice cgminer[1001]: job buf total len:2559, offset:2559
Jun 9 22:42:15 (none) local0.notice cgminer[1001]: about to send job, size is 2559
Jun 9 22:42:15 (none) local0.notice bmminer: bitmain_update_job_cb, rec job data 0xb4800480 size: 2559
Jun 9 22:42:15 (none) local0.notice bmminer: parse job buf len:2559
Jun 9 22:42:19 (none) local0.notice bmminer: need data size:491, actual size:491
Jun 9 22:42:19 (none) local0.notice cgminer[1001]: got nonce sz 491
Jun 9 22:42:19 (none) local0.notice cgminer[1001]: Pool 0 stale share detected, submitting as user requested
Jun 9 22:42:19 (none) local0.notice cgminer[1001]: cb_bitmain_submit_nonce nonce submited
Jun 9 22:42:19 (none) local0.notice cgminer[1001]: Accepted 26d0d94b Diff 432K/65536 BTM_SOC 0 pool 0
Jun 9 22:42:37 (none) local0.notice bmminer: need data size:491, actual size:491
Jun 9 22:42:37 (none) local0.notice cgminer[1001]: got nonce sz 491
Jun 9 22:42:37 (none) local0.notice cgminer[1001]: Pool 0 stale share detected, submitting as user requested
Jun 9 22:42:37 (none) local0.notice cgminer[1001]: cb_bitmain_submit_nonce nonce submited
Jun 9 22:42:37 (none) local0.notice cgminer[1001]: Accepted bd3bd0b1 Diff 88.7K/65536 BTM_SOC 0 pool 0
Jun 9 22:42:45 (none) local0.notice cgminer[1001]: update job
Jun 9 22:42:45 (none) local0.notice cgminer[1001]: job buf total len:2559, offset:2559
Jun 9 22:42:45 (none) local0.notice cgminer[1001]: about to send job, size is 2559
Jun 9 22:42:45 (none) local0.notice bmminer: bitmain_update_job_cb, rec job data 0xb4800480 size: 2559
Jun 9 22:42:45 (none) local0.notice bmminer: parse job buf len:2559
Jun 9 22:43:10 (none) local0.notice bmminer: need data size:491, actual size:491
Jun 9 22:43:10 (none) local0.notice cgminer[1001]: got nonce sz 491
Jun 9 22:43:10 (none) local0.notice cgminer[1001]: Pool 0 stale share detected, submitting as user requested
Jun 9 22:43:10 (none) local0.notice cgminer[1001]: cb_bitmain_submit_nonce nonce submited
Jun 9 22:43:10 (none) local0.notice cgminer[1001]: Accepted 3372d7e4 Diff 326K/65536 BTM_SOC 0 pool 0
Jun 9 22:43:11 (none) local0.notice bmminer: need data size:491, actual size:491
Jun 9 22:43:11 (none) local0.notice cgminer[1001]: got nonce sz 491
Jun 9 22:43:11 (none) local0.notice cgminer[1001]: Pool 0 stale share detected, submitting as user requested
Jun 9 22:43:11 (none) local0.notice cgminer[1001]: cb_bitmain_submit_nonce nonce submited
Jun 9 22:43:11 (none) local0.notice cgminer[1001]: Accepted 1d9ab3c9 Diff 567K/65536 BTM_SOC 0 pool 0
Jun 9 22:43:15 (none) local0.notice cgminer[1001]: update job
Jun 9 22:43:15 (none) local0.notice cgminer[1001]: job buf total len:2591, offset:2591
Jun 9 22:43:15 (none) local0.notice cgminer[1001]: about to send job, size is 2591
Jun 9 22:43:15 (none) local0.notice bmminer: bitmain_update_job_cb, rec job data 0xb4800480 size: 2591
Jun 9 22:43:15 (none) local0.notice bmminer: parse job buf len:2591
Jun 9 22:43:32 (none) local0.notice bmminer: need data size:491, actual size:491
Jun 9 22:43:32 (none) local0.notice cgminer[1001]: got nonce sz 491
Jun 9 22:43:32 (none) local0.notice cgminer[1001]: Pool 0 stale share detected, submitting as user requested
Jun 9 22:43:32 (none) local0.notice cgminer[1001]: cb_bitmain_submit_nonce nonce submited
Jun 9 22:43:32 (none) local0.notice cgminer[1001]: Accepted b65784d0 Diff 92K/65536 BTM_SOC 0 pool 0
Jun 9 22:43:33 (none) local0.notice bmminer: need data size:491, actual size:491
Jun 9 22:43:33 (none) local0.notice cgminer[1001]: got nonce sz 491
Jun 9 22:43:33 (none) local0.notice cgminer[1001]: Pool 0 stale share detected, submitting as user requested
Jun 9 22:43:33 (none) local0.notice cgminer[1001]: cb_bitmain_submit_nonce nonce submited
Jun 9 22:43:33 (none) local0.notice cgminer[1001]: Accepted b6844e1f Diff 91.9K/65536 BTM_SOC 0 pool 0
Jun 9 22:43:45 (none) local0.notice cgminer[1001]: update job
Jun 9 22:43:45 (none) local0.notice cgminer[1001]: job buf total len:2591, offset:2591
Jun 9 22:43:45 (none) local0.notice cgminer[1001]: about to send job, size is 2591
Jun 9 22:43:45 (none) local0.notice bmminer: bitmain_update_job_cb, rec job data 0xb4800480 size: 2591
Jun 9 22:43:45 (none) local0.notice bmminer: parse job buf len:2591
Jun 9 22:44:14 (none) local0.notice bmminer: need data size:491, actual size:491
Jun 9 22:44:14 (none) local0.notice cgminer[1001]: got nonce sz 491
Jun 9 22:44:14 (none) local0.notice cgminer[1001]: Pool 0 stale share detected, submitting as user requested
Jun 9 22:44:14 (none) local0.notice cgminer[1001]: cb_bitmain_submit_nonce nonce submited
Jun 9 22:44:18 (none) local0.notice cgminer[1001]: Accepted fb612c48 Diff 66.7K/65536 BTM_SOC 0 pool 0
Jun 9 22:44:19 (none) local0.notice cgminer[1001]: update job
Jun 9 22:44:19 (none) local0.notice cgminer[1001]: job buf total len:2591, offset:2591
Jun 9 22:44:19 (none) local0.notice cgminer[1001]: about to send job, size is 2591
Jun 9 22:44:19 (none) local0.notice bmminer: bitmain_update_job_cb, rec job data 0xb4800480 size: 2591
Jun 9 22:44:19 (none) local0.notice bmminer: parse job buf len:2591
2022-06-09 22:26:08 driver-btm-api.c:663:init_freq_mode: This is scan-user version
2022-06-09 22:26:08 driver-btm-api.c:2028:bitmain_soc_init: opt_multi_version = 1
2022-06-09 22:26:08 driver-btm-api.c:2029:bitmain_soc_init: opt_bitmain_ab = 1
2022-06-09 22:26:08 driver-btm-api.c:2030:bitmain_soc_init: opt_bitmain_work_mode = 0
2022-06-09 22:26:08 driver-btm-api.c:2031:bitmain_soc_init: Miner compile time: Thu Apr 23 16:29:07 CST 2020 type: Antminer T17
2022-06-09 22:26:08 driver-btm-api.c:2032:bitmain_soc_init: commit version: 1c5be6f 2020-04-20 16:18:14, build by: lol 2020-04-23 16:35:04
2022-06-09 22:26:08 driver-btm-api.c:1844:show_sn: no SN got, please write SN to /nvdata/sn
2022-06-09 22:26:08 driver-btm-api.c:1167:miner_device_init: Detect 256MB control board of XILINX
2022-06-09 22:26:08 driver-btm-api.c:1115:init_fan_parameter: fan_eft : 0 fan_pwm : 0
2022-06-09 22:26:08 thread.c:885:create_read_nonce_reg_thread: create thread
2022-06-09 22:26:14 driver-btm-api.c:1099:init_miner_version: miner ID : 816c6d282b10481c
2022-06-09 22:26:14 driver-btm-api.c:1105:init_miner_version: FPGA Version = 0xB013
2022-06-09 22:26:15 eeprom.c:431:check_pattern_test_level: L1 board
2022-06-09 22:26:17 eeprom.c:431:check_pattern_test_level: L1 board
2022-06-09 22:26:19 eeprom.c:431:check_pattern_test_level: L1 board
2022-06-09 22:26:19 driver-btm-api.c:737:get_product_id: product_id[0] = 1
2022-06-09 22:26:19 driver-btm-api.c:737:get_product_id: product_id[1] = 1
2022-06-09 22:26:19 driver-btm-api.c:737:get_product_id: product_id[2] = 1
2022-06-09 22:26:19 driver-btm-api.c:1666:get_ccdly_opt: ccdly_opt[0] = 1
2022-06-09 22:26:19 driver-btm-api.c:1666:get_ccdly_opt: ccdly_opt[1] = 1
2022-06-09 22:26:19 driver-btm-api.c:1666:get_ccdly_opt: ccdly_opt[2] = 1
2022-06-09 22:26:19 driver-btm-api.c:1919:bitmain_board_init: g_ccdly_opt = 1
2022-06-09 22:26:19 driver-btm-api.c:676:_set_project_type: project:2
2022-06-09 22:26:19 driver-btm-api.c:706:_set_project_type: Project type: Antminer T17
2022-06-09 22:26:19 driver-btm-api.c:717:dump_pcb_bom_version: Chain [0] PCB Version: 0x0100
2022-06-09 22:26:19 driver-btm-api.c:718:dump_pcb_bom_version: Chain [0] BOM Version: 0x0100
2022-06-09 22:26:19 driver-btm-api.c:717:dump_pcb_bom_version: Chain [1] PCB Version: 0x0100
2022-06-09 22:26:19 driver-btm-api.c:718:dump_pcb_bom_version: Chain [1] BOM Version: 0x0100
2022-06-09 22:26:19 driver-btm-api.c:717:dump_pcb_bom_version: Chain [2] PCB Version: 0x0100
2022-06-09 22:26:19 driver-btm-api.c:718:dump_pcb_bom_version: Chain [2] BOM Version: 0x0100
2022-06-09 22:26:22 driver-btm-api.c:1939:bitmain_board_init: Fan check passed.
2022-06-09 22:26:24 board.c:36:jump_and_app_check_restore_pic: chain[0] PIC jump to app
2022-06-09 22:26:27 board.c:40:jump_and_app_check_restore_pic: Check chain[0] PIC fw version=0xb9
2022-06-09 22:26:29 board.c:36:jump_and_app_check_restore_pic: chain[1] PIC jump to app
2022-06-09 22:26:32 board.c:40:jump_and_app_check_restore_pic: Check chain[1] PIC fw version=0xb9
2022-06-09 22:26:34 board.c:36:jump_and_app_check_restore_pic: chain[2] PIC jump to app
2022-06-09 22:26:38 board.c:40:jump_and_app_check_restore_pic: Check chain[2] PIC fw version=0xb9
2022-06-09 22:26:38 thread.c:880:create_pic_heart_beat_thread: create thread
2022-06-09 22:26:38 power_api.c:55:power_init: power init ...
2022-06-09 22:26:38 driver-btm-api.c:1949:bitmain_board_init: Enter 30s sleep to make sure power release finish.
2022-06-09 22:26:38 power_api.c:46:power_off: init gpio907
2022-06-09 22:27:10 power_api.c:232:set_iic_power_to_highest_voltage: setting to voltage: 17.00 ...
2022-06-09 22:27:15 power_api.c:124:check_voltage_multi: retry time: 0
2022-06-09 22:27:17 power_api.c:86:get_average_voltage: chain[0], voltage is: 20.493838
2022-06-09 22:27:19 power_api.c:86:get_average_voltage: chain[1], voltage is: 19.838672
2022-06-09 22:27:21 power_api.c:86:get_average_voltage: chain[2], voltage is: 19.269228
2022-06-09 22:27:21 power_api.c:97:get_average_voltage: aveage voltage is: 19.867246
2022-06-09 22:27:21 power_api.c:110:check_voltage: target_vol = 17.00, actural_vol = 19.87, more than 1.0v diff.
2022-06-09 22:27:22 power_api.c:124:check_voltage_multi: retry time: 1
2022-06-09 22:27:23 power_api.c:86:get_average_voltage: chain[0], voltage is: 18.295664
2022-06-09 22:27:25 power_api.c:86:get_average_voltage: chain[1], voltage is: 17.738467
2022-06-09 22:27:28 power_api.c:86:get_average_voltage: chain[2], voltage is: 16.862871
2022-06-09 22:27:28 power_api.c:97:get_average_voltage: aveage voltage is: 17.632334
2022-06-09 22:27:28 power_api.c:182:set_iic_power_by_voltage: now set voltage to : 17.000000
2022-06-09 22:27:28 uart.c:80:set_baud: set fpga_baud = 115200, fpga_divider = 26
2022-06-09 22:27:38 driver-btm-api.c:1042:check_asic_number_with_power_on: Chain[0]: find 18 asic, times 0
2022-06-09 22:27:48 driver-btm-api.c:1042:check_asic_number_with_power_on: Chain[0]: find 18 asic, times 1
2022-06-09 22:27:58 driver-btm-api.c:1042:check_asic_number_with_power_on: Chain[0]: find 18 asic, times 2
2022-06-09 22:27:58 driver-btm-api.c:1069:check_asic_number: Chain 0 only find 18 asic, will power off hash board 0
2022-06-09 22:28:11 driver-btm-api.c:1042:check_asic_number_with_power_on: Chain[1]: find 0 asic, times 0
2022-06-09 22:28:21 driver-btm-api.c:1042:check_asic_number_with_power_on: Chain[1]: find 0 asic, times 1
2022-06-09 22:28:31 driver-btm-api.c:1042:check_asic_number_with_power_on: Chain[1]: find 0 asic, times 2
2022-06-09 22:28:31 driver-btm-api.c:1069:check_asic_number: Chain 1 only find 0 asic, will power off hash board 1
2022-06-09 22:28:43 driver-btm-api.c:1042:check_asic_number_with_power_on: Chain[2]: find 30 asic, times 0
2022-06-09 22:28:44 driver-btm-api.c:352:set_order_clock: chain[2]: set order clock, stragegy 3 clock_en=0x1
2022-06-09 22:28:44 driver-hash-chip.c:502:set_clock_delay_control: core_data = 0xb4
2022-06-09 22:28:44 uart.c:80:set_baud: set fpga_baud = 3000000, fpga_divider = 0
2022-06-09 22:28:44 driver-btm-api.c:1693:check_clock_counter: freq 50 clock_counter_limit 6
2022-06-09 22:28:44 uart.c:80:set_baud: set fpga_baud = 115200, fpga_divider = 26
2022-06-09 22:28:44 voltage[2] = 1690
2022-06-09 22:28:44 power_api.c:140:set_working_voltage: working_voltage = 16.900000
2022-06-09 22:28:46 temperature.c:282:calibrate_temp_sensor_one_chain: Temperature sensor calibration: chain 2 success.
2022-06-09 22:28:46 uart.c:80:set_baud: set fpga_baud = 6000000, fpga_divider = 3
2022-06-09 22:28:46 driver-btm-api.c:252:check_bringup_temp: Bring up temperature is 32
2022-06-09 22:28:46 thread.c:900:create_check_miner_status_thread: create thread
2022-06-09 22:28:46 thread.c:890:create_set_miner_status_thread: create thread
2022-06-09 22:28:46 driver-btm-api.c:613:calculate_timeout: dev->timeout = 392
2022-06-09 22:28:46 thread.c:875:create_temperature_monitor_thread: create thread
2022-06-09 22:28:46 freq_tuning.c:159:freq_tuning_get_max_freq: Max freq of tuning is 760
2022-06-09 22:28:46 power_api.c:379:slowly_set_iic_power_to_custom_voltage: slowly setting to voltage: 17.60 ...
2022-06-09 22:29:12 power_api.c:124:check_voltage_multi: retry time: 0
2022-06-09 22:29:14 power_api.c:86:get_average_voltage: chain[2], voltage is: 17.762959
2022-06-09 22:29:14 power_api.c:97:get_average_voltage: aveage voltage is: 17.762959
2022-06-09 22:30:10 driver-btm-api.c:644:set_timeout: freq 720 final timeout=163
2022-06-09 22:30:10 power_api.c:397:slowly_set_iic_power_to_working_voltage: slowly setting to voltage: 16.90 ...
2022-06-09 22:30:31 power_api.c:124:check_voltage_multi: retry time: 0
2022-06-09 22:30:34 power_api.c:86:get_average_voltage: chain[2], voltage is: 17.089424
2022-06-09 22:30:34 power_api.c:97:get_average_voltage: aveage voltage is: 17.089424
2022-06-09 22:30:34 frequency.c:654:get_current_min_freq: current min freq 720
2022-06-09 22:30:34 driver-btm-api.c:1693:check_clock_counter: freq 720 clock_counter_limit 92
2022-06-09 22:30:35 thread.c:895:create_check_system_status_thread: create thread
2022-06-09 22:30:35 driver-btm-api.c:2155:bitmain_soc_init: Init done!
2022-06-09 22:30:35 driver-btm-api.c:205:set_miner_status: STATUS_INIT
2022-06-09 22:30:39 driver-btm-api.c:205:set_miner_status: STATUS_OKAY
2022-06-09 22:30:50 driver-btm-api.c:1325:dhash_chip_send_job: Version num 4
2022-06-09 22:35:50 thread.c:441:is_zero_nonce_happened: chain_nonce[2] = 15762
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: mikeywith on June 11, 2022, 01:02:41 AM
2 of my hashboards are not working and this is kernal log, someone please help in identifying the issue. And also, I can feel the current when the ASIC is turned on. 2022-06-09 22:27:38 driver-btm-api.c:1042:check_asic_number_with_power_on: Chain[0]: find 18 asic, times 0
2022-06-09 22:28:31 driver-btm-api.c:1042:check_asic_number_with_power_on: Chain[1]: find 0 asic, times 2
2022-06-09 22:28:43 driver-btm-api.c:1042:check_asic_number_with_power_on: Chain[2]: find 30 asic, times 0
The answer is in these 3 lines which I copied from your kernel log, your miner is T17 which has 30 chips of on each hashboard, they work in series which means one missing chip will stop the whole hash board, your chain 0 and 1 both have bad chips, chain 0 loses the signal on the 18th chip, chain 1 doesn't sense any chip at all, this is a very common issue with all the 17 series, most often caused by bad contact between the chip and the board itself, fixing it isn't an easy job and needs a good set of skills and hardware. if you don't have those and don't want to send it for repair, try the freezer trick, seal the two hashboard in a plastic bag, drop them in the freezer for 2 days, not sure what does that exactly do to these hash boards, but it does work sometimes if you are lucky enough.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: unisahmed on June 16, 2022, 05:17:36 PM
I've got the same issue.
I have 2 T17 42T, one is running with 1 board and the other with 2 boards.
Can i swap one board to the other machine?
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: mikeywith on June 20, 2022, 05:27:12 PM
I've got the same issue.
I have 2 T17 42T, one is running with 1 board and the other with 2 boards.
Can i swap one board to the other machine?
If you use the stock firmware you will have to try, there is a combination of voltages stored in the EPROM of each hash board, some will match well some won't, if you use custom firmware, you can simply mix and match as they don't care about the voltage readings. However, why do you want to do that in the first place? unless you are going to sell the other PSU and Control board, or you are running out of space, it's better to keep 1 working board in 1 miner and 2 in the other, the 3 working boards will run a lot cooler sitting next to dead hash boards.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: unisahmed on June 22, 2022, 02:08:00 AM
Hi Mike, thanks for the reply. The very first day i ran these machines they were working with all 30 chips and 3 boards. After 30 minutes one Chain failed and then 2nd failed. so i decided to test the 2nd machine and the same shit repeated but only one chain failed on this machine. I moved the running board on to the 2nd machine and ran the stock firmware and surprisingly its been running pretty well for the past 4 days and 17hrs. I'm getting 42T with the stock firmware. As for the 1st machine, ill try to find someone locally and get it fixed. https://www.linkpicture.com/q/T17-42T-4Days-Mining.jpg
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: BitMaxz on June 22, 2022, 04:01:48 PM
Hi Mike, thanks for the reply.
The very first day i ran these machines they were working with all 30 chips and 3 boards. After 30 minutes one Chain failed and then 2nd failed. so i decided to test the 2nd machine and the same shit repeated but only one chain failed on this machine. I moved the running board on to the 2nd machine and ran the stock firmware and surprisingly its been running pretty well for the past 4 days and 17hrs. I'm getting 42T with the stock firmware.
As for the 1st machine, ill try to find someone locally and get it fixed.
If you can take the kernel logs from your first machine with the 2nd hashboard(Failed) maybe we can see some other reason under your kernel logs why the 2nd hashboard chain fail. You can post the whole kernel logs here and make sure to paste it inside the insert code tag(A # button when editing/posting) or you can use pastebin.com and share the URL here. Sometimes the issue is due to sensors or overheating and kernel logs will explain everything that happens in your machine.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: mikeywith on June 25, 2022, 11:11:48 PM
I moved the running board on to the 2nd machine and ran the stock firmware and surprisingly its been running pretty well for the past 4 days and 17hrs.
Like I explained in the first post, you could get lucky, I don't know how many combinations are there "I remember 3 of them for S9k", they could be the same", so every board you mix has a 1/3 chance, so more often than not, it doesn't work, but seems like you are pretty lucky, maybe mine to a solo pool and hit a whole block with that gear? :D I would also be interested in the new kernel log for the bad machine.
Title: Re: T17/S17 malfunction: cases, solutions, remedies, RMA history
Post by: wndsnb on June 26, 2022, 02:49:18 PM
The voltage setting stored in the eeproms (for the current mode if a s17) needs to be the same on all hashboards in a miner for stock firmware to work. If you have logs from the miners with the boards you want to mix, you can tell in advance if they will work together. You just need to find the following section in the logs and check that the voltage setting is the same in the two miners you want to mix and match boards from/to. 022-05-17 22:44:27 uart.c:71:set_baud: set fpga_baud to 115200
2022-05-17 22:44:38 driver-btm-api.c:915:check_asic_number_with_power_on: Chain[0]: find 48 asic, times 0
2022-05-17 22:44:49 driver-btm-api.c:915:check_asic_number_with_power_on: Chain[1]: find 48 asic, times 0
2022-05-17 22:45:00 driver-btm-api.c:915:check_asic_number_with_power_on: Chain[2]: find 48 asic, times 0
2022-05-17 22:45:05 driver-btm-api.c:345:set_order_clock: chain[0]: set order clock, stragegy 3
2022-05-17 22:45:05 driver-btm-api.c:345:set_order_clock: chain[1]: set order clock, stragegy 3
2022-05-17 22:45:05 driver-btm-api.c:345:set_order_clock: chain[2]: set order clock, stragegy 3
2022-05-17 22:45:05 driver-hash-chip.c:502:set_clock_delay_control: core_data = 0x34
2022-05-17 22:45:05 uart.c:71:set_baud: set fpga_baud to 3000000
2022-05-17 22:45:05 driver-btm-api.c:1574:check_clock_counter: freq 50 clock_counter_limit 6
2022-05-17 22:45:07 uart.c:71:set_baud: set fpga_baud to 115200
2022-05-17 22:45:07 voltage[0] = 1780
2022-05-17 22:45:07 voltage[1] = 1780
2022-05-17 22:45:07 voltage[2] = 1780
2022-05-17 22:45:07 power_api.c:219:set_working_voltage_raw: working_voltage_raw = 1780
|
