Title: Antminer S9 one hashboard stop appearing in STATUS
Post by: ikon31 on August 30, 2017, 08:32:59 AM
Hi everyone.
i am having trouble with my S9 12.5TH/s.
I bought the miner on May 2017 and put it mining in a server room with no dust and room temperature from 19 to 23 Celsius max.
The miner had chip temps around 69min-82max and fans around 2000min-3200max rpms.
I use the APW3 of Bitmain`s PSU.
Yesterday i noticed that one of the hashboards does not appear in the STATUS window(NO XXXXXXXX`s NO --------------`s just not appearing.it only shows 2 blades).
The miner hashes at 2/3 of the total power and consumes the 2/3 of the maximum voltage.
I also touched with my finger the top end of the circuit boards of the 3 blades and one of them is DEAD cold. The other 2 are just a liiiiiiitle bit worm(i believe this means no current passes through the one board?).
Also there is a red light in every hashboard and on the COLD hashboard is NOT light.
Is there a way to fix it or do i need to sent it to bitmain?
I mean if flashing new firmware, change cables, hard reset(if there is such a thing), check control board etc is going to help.
Please any tips are welcome.
Please note that i don`t have other antminer in hand. it is the only one.
Thank you in advance and sorry for my English as they are not my primary language.
UPDATE:
1) I left onboard only the one blade that does not had the red light on and connected 3 6pin power cables from the other 2 blades which they were working and switched ON. NOTHING happened. NO hashing.
2) I used different 18pin signal cable from the controller in case that was the problem and switched it ON. Still NO hashing.
I believe updating the new firmware wont do nothing?
Plz help.
Thank you
Title: Re: Antminer S9 one hashboard stop appearing in STATUS
Post by: HagssFIN on August 30, 2017, 11:50:07 AM
Time for a warranty repair with Bitmain and if there is no warranty time left then it's time for a repair with Bitmainwarranty (different company than Bitmain). See their repair guide for more https://shop.bitmain.com/workOrderGuide.htm You must carefully follow their instructions in the repair guide for the shipment and everything ...
b. For the miner, if your miner is:
S9: Shipped before October 1, 2016, please ship the defective part
Shipped after October 1, 2016, please ship the whole machine
Title: Re: Antminer S9 one hashboard stop appearing in STATUS
Post by: fanatic26 on August 30, 2017, 04:28:27 PM
A firmware flash only affects the controller. You have a bad hash board. These are string design and it only takes one failure point to kill an entire board. If you purchased it new from bitmain in May you are still under warranty. You can put a ticket in and ship it to the los angeles depot for repair.
Title: Re: Antminer S9 one hashboard stop appearing in STATUS
Post by: ikon31 on September 26, 2017, 06:38:40 PM
New UPDATE 26/9/2017
I tried and flashed the new bitmain firmware and all of a sudden the third hashboard appeard in the miners status and for a couple of hours it worked perfect.
The hashrate came back to 12.5ths.
BUT two hours later the hashboard desappeared again :(
Does anyone know what is happening?
Plz help.
Title: Re: Antminer S9 one hashboard stop appearing in STATUS
Post by: NotFuzzyWarm on September 26, 2017, 06:46:24 PM
As said before - you have a hash board that is failing/has failed. It is not uncommon for a bad board to run for a bit and then drop out.
Title: Re: Antminer S9 one hashboard stop appearing in STATUS
Post by: ikon31 on September 26, 2017, 06:51:15 PM
Thanks For The fast replay.
I will try to repair it although i dont know if it is worth doing so or just leave it with the two boards hashing.
Thanks once again people.
Title: Re: Antminer S9 one hashboard stop appearing in STATUS
Post by: shemoura on November 26, 2017, 01:19:33 AM
Hi, i have this same problem with s9 13.5 :'( a hashboard disappeared from the panel, now only working with two hashboards. I have already done firmware update several times, already tested the hashboard in other connectors and the cable of the controller card also and nothing to work, I noticed that when the equipment is turned on, the red light on the hashboard lights, but then it goes out and does not come back on again If anyone has any solutions thank you for the attention. Thank you very much, good luck to all. look img panel. https://i.imgur.com/DXlMUib.png (https://i.imgur.com/DXlMUib.png) https://i.imgur.com/DXlMUib.png*** After 1 day off the machine and restart again and the hashboard show in panel as the image shows, but the temperature is marking 0. Any solution ??? please All thanks https://i.imgur.com/wCW6rAV.pngkernel log Miner fix freq ...
read PIC voltage=940 on chain[5]
Chain:5 chipnum=63
Asic[ 0]:600
Asic[ 1]:600 Asic[ 2]:600 Asic[ 3]:600 Asic[ 4]:600 Asic[ 5]:600 Asic[ 6]:600 Asic[ 7]:600 Asic[ 8]:600
Asic[ 9]:600 Asic[10]:600 Asic[11]:600 Asic[12]:600 Asic[13]:600 Asic[14]:600 Asic[15]:600 Asic[16]:600
Asic[17]:600 Asic[18]:600 Asic[19]:600 Asic[20]:600 Asic[21]:600 Asic[22]:600 Asic[23]:600 Asic[24]:600
Asic[25]:600 Asic[26]:600 Asic[27]:600 Asic[28]:600 Asic[29]:600 Asic[30]:600 Asic[31]:600 Asic[32]:600
Asic[33]:600 Asic[34]:600 Asic[35]:600 Asic[36]:600 Asic[37]:600 Asic[38]:600 Asic[39]:600 Asic[40]:600
Asic[41]:600 Asic[42]:600 Asic[43]:600 Asic[44]:600 Asic[45]:600 Asic[46]:600 Asic[47]:600 Asic[48]:600
Asic[49]:600 Asic[50]:600 Asic[51]:600 Asic[52]:600 Asic[53]:600 Asic[54]:600 Asic[55]:600 Asic[56]:600
Asic[57]:600 Asic[58]:600 Asic[59]:600 Asic[60]:600 Asic[61]:600 Asic[62]:600
Chain:5 max freq=600
Chain:5 min freq=600
read PIC voltage=940 on chain[6]
Chain:6 chipnum=63
Asic[ 0]:600
Asic[ 1]:600 Asic[ 2]:600 Asic[ 3]:600 Asic[ 4]:600 Asic[ 5]:600 Asic[ 6]:600 Asic[ 7]:600 Asic[ 8]:600
Asic[ 9]:600 Asic[10]:600 Asic[11]:600 Asic[12]:600 Asic[13]:600 Asic[14]:600 Asic[15]:600 Asic[16]:600
Asic[17]:600 Asic[18]:600 Asic[19]:600 Asic[20]:600 Asic[21]:600 Asic[22]:600 Asic[23]:600 Asic[24]:600
Asic[25]:600 Asic[26]:600 Asic[27]:600 Asic[28]:600 Asic[29]:600 Asic[30]:600 Asic[31]:600 Asic[32]:600
Asic[33]:600 Asic[34]:600 Asic[35]:600 Asic[36]:600 Asic[37]:600 Asic[38]:600 Asic[39]:600 Asic[40]:600
Asic[41]:600 Asic[42]:600 Asic[43]:600 Asic[44]:600 Asic[45]:600 Asic[46]:600 Asic[47]:600 Asic[48]:600
Asic[49]:600 Asic[50]:600 Asic[51]:600 Asic[52]:600 Asic[53]:600 Asic[54]:600 Asic[55]:600 Asic[56]:600
Asic[57]:600 Asic[58]:600 Asic[59]:600 Asic[60]:600 Asic[61]:600 Asic[62]:600
Chain:6 max freq=600
Chain:6 min freq=600
read PIC voltage=940 on chain[7]
Chain:7 chipnum=63
Asic[ 0]:600
Asic[ 1]:600 Asic[ 2]:600 Asic[ 3]:600 Asic[ 4]:600 Asic[ 5]:600 Asic[ 6]:600 Asic[ 7]:600 Asic[ 8]:600
Asic[ 9]:600 Asic[10]:600 Asic[11]:600 Asic[12]:600 Asic[13]:600 Asic[14]:600 Asic[15]:600 Asic[16]:600
Asic[17]:600 Asic[18]:600 Asic[19]:600 Asic[20]:600 Asic[21]:600 Asic[22]:600 Asic[23]:600 Asic[24]:600
Asic[25]:600 Asic[26]:600 Asic[27]:600 Asic[28]:600 Asic[29]:600 Asic[30]:600 Asic[31]:600 Asic[32]:600
Asic[33]:600 Asic[34]:600 Asic[35]:600 Asic[36]:600 Asic[37]:600 Asic[38]:600 Asic[39]:600 Asic[40]:600
Asic[41]:600 Asic[42]:600 Asic[43]:600 Asic[44]:600 Asic[45]:600 Asic[46]:600 Asic[47]:600 Asic[48]:600
Asic[49]:600 Asic[50]:600 Asic[51]:600 Asic[52]:600 Asic[53]:600 Asic[54]:600 Asic[55]:600 Asic[56]:600
Asic[57]:600 Asic[58]:600 Asic[59]:600 Asic[60]:600 Asic[61]:600 Asic[62]:600
Chain:7 max freq=600
Chain:7 min freq=600
max freq = 600
set baud=1
Chain[J6] PIC temp offset=62,-4,0,0,0,0,0,0
Chain[J6] chip[244] use PIC middle temp offset=-4 typeID=55
New offset Chain[5] chip[244] local:36 remote:38 offset:29
Chain[J6] chip[244] get middle temp offset=29 typeID=55
Chain[J7] PIC temp offset=62,-4,0,0,0,0,0,0
Chain[J7] chip[244] use PIC middle temp offset=-4 typeID=55
New offset Chain[6] chip[244] local:28 remote:30 offset:28
Chain[J7] chip[244] get middle temp offset=28 typeID=55
Chain[J8] PIC temp offset=62,-5,0,0,0,0,0,0
Chain[J8] chip[244] use PIC middle temp offset=-5 typeID=55
New offset Chain[7] chip[244] local:34 remote:36 offset:29
Chain[J8] chip[244] get middle temp offset=29 typeID=55
Chain[J6] set working voltage=930 [23]
Chain[J7] set working voltage=930 [23]
Chain[J8] set working voltage=930 [23]
setStartTimePoint total_tv_start_sys=60 total_tv_end_sys=61
restartNum = 2 , auto-reinit enabled...
do read_temp_func once...
do check_asic_reg 0x08
get RT hashrate from Chain[5]: (asic index start from 1-63)
Asic[01]=75.0100 Asic[02]=66.4710 Asic[03]=68.3160 Asic[04]=72.4940 Asic[05]=70.1450 Asic[06]=66.2020 Asic[07]=68.2830 Asic[08]=70.0780
Asic[09]=69.8090 Asic[10]=70.3460 Asic[11]=68.6020 Asic[12]=65.0950 Asic[13]=70.9840 Asic[14]=71.7720 Asic[15]=68.8530 Asic[16]=73.5000
Asic[17]=70.3800 Asic[18]=70.8830 Asic[19]=72.7290 Asic[20]=66.9740 Asic[21]=68.7360 Asic[22]=64.9440 Asic[23]=61.6050 Asic[24]=62.5450
Asic[25]=60.3810 Asic[26]=62.2770 Asic[27]=68.5010 Asic[28]=64.8770 Asic[29]=63.6350 Asic[30]=67.4440 Asic[31]=68.0810 Asic[32]=66.7390
Asic[33]=66.2860 Asic[34]=67.7960 Asic[35]=72.8290 Asic[36]=64.3400 Asic[37]=68.1650 Asic[38]=66.5550 Asic[39]=67.4100 Asic[40]=73.5340
Asic[41]=68.2490 Asic[42]=71.0170 Asic[43]=71.3870 Asic[44]=70.8160 Asic[45]=66.5710 Asic[46]=68.9710 Asic[47]=66.4200 Asic[48]=70.2290
Asic[49]=76.7220 Asic[50]=70.8660 Asic[51]=68.6180 Asic[52]=72.9470 Asic[53]=71.3530 Asic[54]=64.4410 Asic[55]=63.6190 Asic[56]=69.0550
Asic[57]=68.0650 Asic[58]=71.3190 Asic[59]=71.4540 Asic[60]=69.7760 Asic[61]=70.5310 Asic[62]=64.8770 Asic[63]=71.2360
get RT hashrate from Chain[6]: (asic index start from 1-63)
get RT hashrate from Chain[7]: (asic index start from 1-63)
Asic[01]=71.9400 Asic[02]=70.3800 Asic[03]=73.7520 Asic[04]=69.9100 Asic[05]=75.0100 Asic[06]=75.4470 Asic[07]=67.8130 Asic[08]=69.2890
Asic[09]=66.5710 Asic[10]=63.0480 Asic[11]=68.2320 Asic[12]=73.0310 Asic[13]=62.5950 Asic[14]=75.3120 Asic[15]=71.5380 Asic[16]=69.2890
Asic[17]=66.7060 Asic[18]=64.3400 Asic[19]=73.9200 Asic[20]=70.8830 Asic[21]=74.5570 Asic[22]=70.3130 Asic[23]=64.2060 Asic[24]=66.9570
Asic[25]=67.1920 Asic[26]=65.7160 Asic[27]=68.4670 Asic[28]=64.4910 Asic[29]=70.0440 Asic[30]=69.1220 Asic[31]=70.1620 Asic[32]=68.3330
Asic[33]=70.6320 Asic[34]=67.2260 Asic[35]=76.0670 Asic[36]=68.4840 Asic[37]=63.5520 Asic[38]=73.6010 Asic[39]=64.5080 Asic[40]=68.0480
Asic[41]=70.5480 Asic[42]=67.0240 Asic[43]=70.3800 Asic[44]=74.7420 Asic[45]=70.9670 Asic[46]=59.5420 Asic[47]=72.2590 Asic[48]=63.4840
Asic[49]=70.1620 Asic[50]=66.6890 Asic[51]=66.3530 Asic[52]=70.4470 Asic[53]=69.4570 Asic[54]=72.2760 Asic[55]=71.3190 Asic[56]=72.5110
Asic[57]=64.5080 Asic[58]=70.7830 Asic[59]=69.2060 Asic[60]=64.2730 Asic[61]=70.4130 Asic[62]=67.0080 Asic[63]=73.0310
Check Chain[J6] ASIC RT error: (asic index start from 1-63)
Check Chain[J7] ASIC RT error: (asic index start from 1-63)
Asic[57]=348.613000
Check Chain[J8] ASIC RT error: (asic index start from 1-63)
Done check_asic_reg
do read temp on Chain[5]
Chain[5] Chip[62] TempTypeID=55 middle offset=29
Chain[5] Chip[62] local Temp=69
Chain[5] Chip[62] middle Temp=82
Done read temp on Chain[5]
do read temp on Chain[6]
Chain[6] Chip[62] TempTypeID=55 middle offset=28
read failed, old value: Chain[6] Chip[62] local Temp=0
read failed on Chain[6] Chip[62] middle Temp old value:0
Done read temp on Chain[6]
do read temp on Chain[7]
Chain[7] Chip[62] TempTypeID=55 middle offset=29
Chain[7] Chip[62] local Temp=66
Chain[7] Chip[62] middle Temp=78
Done read temp on Chain[7]
set FAN speed according to: temp_highest=82 temp_top1[PWM_T]=82 temp_top1[TEMP_POS_LOCAL]=69 temp_change=0 fix_fan_steps=0
FAN PWM: 84
read_temp_func Done!
CRC error counter=0
Title: Re: Antminer S9 one hashboard stop appearing in STATUS
Post by: ccs on December 04, 2017, 10:06:30 PM
I have the same exact problem.... :'( , I Even swapped the cables from the psu to the hashboards around just to rule out the cables, and for a brief moment the hash board in middle's(The one not working) light alone was on, then back to the two outer hash boards working with the light of each one and the one in the middle off, I have mined for 48 hours total the first 5 of whick I was mining at an avg 14TH and after in an avg of 8.5TH. Of course that bitmain will take an eternity to answer... so I was wondering if any computer technician could see anything like a loose cable and just attach it back, or is the miner such a weird device that a normal computer person wouldt understand. I am out of warranty and prefer to mine at 2/3 capacity than not to mine at all.
Thanks Bros
https://postimg.org/image/638d5l4sn/
https://postimg.org/image/rcvzgfst3/
Title: Re: Antminer S9 one hashboard stop appearing in STATUS
Post by: fanatic26 on December 04, 2017, 10:13:01 PM
The hashing board is dead, and there really arent any parts serviceable by someone not adept at board level repair.
The only solution is to send your board out for repair. It is normal to have blades randomly die on older s9s.
Title: Re: Antminer S9 one hashboard stop appearing in STATUS
Post by: ccs on December 04, 2017, 10:16:25 PM
Sad to hear that... Specially since I was not able to install the machine until last week because some personal issues. The machine is out of warranty but never used except for these 48 hours I mentioned
Title: Re: Antminer S9 one hashboard stop appearing in STATUS
Post by: shemoura on December 06, 2017, 07:05:24 AM
Hi all, >:(
I got Bitman response:
Please try these three methods to reset your machine: https://enforum.bitmain.com/bbs/topics/3957
Then load the firmware from this page: https://shop.bitmain.com/support.htm?pid=00720161126080548570Q2tDBXAH065D
Select the file in the last row of the table.
Run the miner for 20 minutes after loading the firmware.
If the issue is not resolved please carefully read and follow these instructions to create a Repair ticket and ship the machine back to us: https://shop.bitmain.com/workOrderGuide.htm
Please let us know if you have additional questions or concerns.
:(
I made all the attempts and no success the middle hashboard still does not back work.
complicated to have to send the complete machine to repair only the board that this problem., they should make change of hashboard with problem even if it has some cost.
and the time of receiving the machine back and absurd custom tax rates depending on the country that will be charged.
I'm trying to contact some technician in China to do repair and send only the hashboard with problem. :-\ >:(
Title: Re: Antminer S9 one hashboard stop appearing in STATUS
Post by: btcurrencies on December 11, 2017, 12:14:55 PM
For all of you with this problem....
i found the solution for the third chain missing!
its only due to the bitmain PSU.
change it to one 1600W not bitmain and your issue will be solved!
this worked for 4 s9 ! not only one.. just change your bitmain PSU
Title: Re: Antminer S9 one hashboard stop appearing in STATUS
Post by: beebo on December 11, 2017, 12:54:52 PM
Hi I also unpacked a brand new antminer s9 yesterday, 1 hashboard not showing. Checked all cables and reloaded firmware, still not showing. Using bitmains psu.
@btcurrencies. I have 1 1000watt psu available. Can I try powering just the faulty hashboard with the 1000watt psu or will I need to purchase a 1600 watt.
Any suggestions to which 1600 watt power supply to purchase.
Thankyou in advance.
Title: Re: Antminer S9 one hashboard stop appearing in STATUS
Post by: mstubs on December 13, 2017, 04:38:32 AM
Im having the same problem with TWO 13.5TH S9s I just got today. I tried 2 different Bitmain PSUs and both S9s sometimes show one board, sometimes 2, and for a few hours before a restart all 3. Can you confirm another PSU will fixed this?
Also I have an L3 that mines just fine with both PSUs. What gives???
Title: Re: Antminer S9 one hashboard stop appearing in STATUS
Post by: btcurrencies on December 16, 2017, 08:55:36 PM
Hi I also unpacked a brand new antminer s9 yesterday, 1 hashboard not showing. Checked all cables and reloaded firmware, still not showing. Using bitmains psu.
@btcurrencies. I have 1 1000watt psu available. Can I try powering just the faulty hashboard with the 1000watt psu or will I need to purchase a 1600 watt.
Any suggestions to which 1600 watt power supply to purchase.
Thankyou in advance.
you need a 1600w not not the bitmain one. you will see that by changing the bitmain one to a standard one will fix the card hashing..
Title: Re: Antminer S9 one hashboard stop appearing in STATUS
Post by: lightfoot on December 17, 2017, 02:22:53 PM
That's interesting. Any chance one of you who did this and has it working can go back to the old supply and check the voltages at the PCIe plugs on each board? I'm wondering if there is a sag somewhere, maybe the problem is one of the Bitmain supply rails is going bad and it shows up as a dead card..... (assuming their PS has three rails this could happen)
Title: Re: Antminer S9 one hashboard stop appearing in STATUS
Post by: Minestrone on January 13, 2018, 03:47:24 PM
Set up my new s9 yesterday with three 750w psu`s , one of the psu`s also powers the control board. Everything was running fine until I turned off the machine to tidy up some cables. When I powered it back up I noticed the middle hashing board was not working and the psu powering this board had stopped. I swapped around the psu`s and whichever psu is connected to the middle board it won`t run. Tried a reset to no effect. Its almost as if there`s a short on that board and the psu that is connected to it is shutting down to protect itself. Anyone else had this problem? I prefer to fix it myself rather than returning it to Bitmain.
Title: Re: Antminer S9 one hashboard stop appearing in STATUS
Post by: lightfoot on January 13, 2018, 11:42:45 PM
If you want to fix it you probably have to pull the FETs on the board, at least the high side ones. This will require hot air tools, good flux, and a good pre-heater. I have all of these, if you want me to look at it drop me a PM and I'll send you my address.
Lightfoot.
Title: Re: Antminer S9 one hashboard stop appearing in STATUS
Post by: Minestrone on January 15, 2018, 12:58:42 PM
Thanks for the offer, I think your in the U.S. so as i`m in the U.K. i`ll wait till I get a reply from Bitmain. I`ve asked them to replace just the board so I don`t have to return the whole unit. For some reason they offer this service for other miners but not the S9. If they won`t agree to that then I guess its going to be an attempt at repair. I have a heat gun and experience with soldering/desoldering components, assuming I can source those particular components here. I sill don`t get why these boards fail so regularly, (I had the same problem with an S7)
Title: Re: Antminer S9 one hashboard stop appearing in STATUS
Post by: lightfoot on January 17, 2018, 03:21:08 AM
My one recommendation is get a board preheater. Really, it makes air tool removal easy, clean, and reliable. A hundred buck Aoyue quartz preheater is like God in a little box.
That and a Hakko battery powered part picker will make you a champ.
Title: Re: Antminer S9 one hashboard stop appearing in STATUS
Post by: Minestrone on January 17, 2018, 12:29:59 PM
If you want to fix it you probably have to pull the FETs on the board, at least the high side ones. This will require hot air tools, good flux, and a good pre-heater. I have all of these, if you want me to look at it drop me a PM and I'll send you my address.
Lightfoot.
As Bitmain are not going to respond until the 25th I pulled the board anyway. There`s no obvious problems on visual inspection. Which FETs do you you mean by "the high side ones"? There seem to be four on the back of the board two marked 6040 an two marked 8040.
Title: Re: Antminer S9 one hashboard stop appearing in STATUS
Post by: MinerMEDIC on January 17, 2018, 06:15:11 PM
If you want to fix it you probably have to pull the FETs on the board, at least the high side ones. This will require hot air tools, good flux, and a good pre-heater. I have all of these, if you want me to look at it drop me a PM and I'll send you my address.
Lightfoot.
As Bitmain are not going to respond until the 25th I pulled the board anyway. There`s no obvious problems on visual inspection. Which FETs do you you mean by "the high side ones"? There seem to be four on the back of the board two marked 6040 an two marked 8040. The high side MOSFET are the two Square chips closest to the power connector. The 6040 and 8040 are drivers because I believe that buck controller is only designed to drive one MOSFET(per side).
Title: Re: Antminer S9 one hashboard stop appearing in STATUS
Post by: lightfoot on January 18, 2018, 12:59:26 AM
Usually you would drive a high side and two low sides. The problem isn't providing gate current, it's the speed at which a normal gate switches. On a normal buck inverter most times the ground is on, with short excursions of the high side being on. Thus low side should have two FETs to ground the power line, and the high side needs just one to do the quick transition. If you put two FETs on the high side you need more gate power *and* the gates will switch more slowly due to capacitance.
On the S9 it's a bit more interesting, the voltage is closer to the median than the S7, so they felt the need for dual FETs on both sides. Which needs more gate current.
Fun stuff.
Title: Re: Antminer S9 one hashboard stop appearing in STATUS
Post by: Minestrone on January 18, 2018, 12:11:33 PM
Surprisingly Bitmain responded quickly but unsurprisingly asked me to return the whole unit. They did offer to give me one of their coupons to cover the shipping costs. So basically they`ve sold me something that stopped working properly after only one day, well within the warranty period and expect me to pay shipping and repay import duties if it is returned to me, and it will only be returned if they deem it DOA. But I will get a coupon (value unspecified) to help buy another unit from them. What a joke!
Title: Re: Antminer S9 one hashboard stop appearing in STATUS
Post by: MinerMEDIC on January 18, 2018, 12:49:37 PM
Usually you would drive a high side and two low sides. The problem isn't providing gate current, it's the speed at which a normal gate switches. On a normal buck inverter most times the ground is on, with short excursions of the high side being on. Thus low side should have two FETs to ground the power line, and the high side needs just one to do the quick transition. If you put two FETs on the high side you need more gate power *and* the gates will switch more slowly due to capacitance.
On the S9 it's a bit more interesting, the voltage is closer to the median than the S7, so they felt the need for dual FETs on both sides. Which needs more gate current.
Fun stuff.
Ya, that and the fact that they switched to a new buck controller that cannot be purchased easily, ON semi however makes almost identical parts(hell they probably copied ONsemi, lol). I have absolutely no idea what the 8040 or 6040 transistor specs are(no datasheets exist as far as I can find), might have to get the converter and MOSFET data and do the math. Wish BITMAIN would release the '87 datasheet already too.
Title: Re: Antminer S9 one hashboard stop appearing in STATUS
Post by: vyking_ua on January 19, 2018, 10:19:55 AM
http://prntscr.com/i2l2frI tried to restart, set to default, reboot methods - no results. In Kernel Logs: [ 0.000000] Booting Linux on physical CPU 0x0
[ 0.000000] Linux version 3.14.0-xilinx-ge8a2f71-dirty (lzq@armdev2) (gcc version 4.8.3 20140320 (prerelease) (Sourcery CodeBench Lite 2014.05-23) ) #82 SMP PREEMPT Tue May 16 19:49:53 CST 2017
[ 0.000000] CPU: ARMv7 Processor [413fc090] revision 0 (ARMv7), cr=18c5387d
[ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
[ 0.000000] Machine model: Xilinx Zynq
[ 0.000000] cma: CMA: reserved 128 MiB at 16800000
[ 0.000000] Memory policy: Data cache writealloc
[ 0.000000] On node 0 totalpages: 126976
[ 0.000000] free_area_init_node: node 0, pgdat c0740a40, node_mem_map debd8000
[ 0.000000] Normal zone: 992 pages used for memmap
[ 0.000000] Normal zone: 0 pages reserved
[ 0.000000] Normal zone: 126976 pages, LIFO batch:31
[ 0.000000] PERCPU: Embedded 8 pages/cpu @debc1000 s9088 r8192 d15488 u32768
[ 0.000000] pcpu-alloc: s9088 r8192 d15488 u32768 alloc=8*4096
[ 0.000000] pcpu-alloc: [0] 0 [0] 1
[ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 125984
[ 0.000000] Kernel command line: noinitrd mem=496M console=ttyPS0,115200 root=ubi0:rootfs ubi.mtd=1 rootfstype=ubifs rw rootwait
[ 0.000000] PID hash table entries: 2048 (order: 1, 8192 bytes)
[ 0.000000] Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
[ 0.000000] Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
[ 0.000000] Memory: 364356K/507904K available (5032K kernel code, 283K rwdata, 1916K rodata, 204K init, 258K bss, 143548K reserved, 0K highmem)
[ 0.000000] Virtual kernel memory layout:
[ 0.000000] vector : 0xffff0000 - 0xffff1000 ( 4 kB)
[ 0.000000] fixmap : 0xfff00000 - 0xfffe0000 ( 896 kB)
[ 0.000000] vmalloc : 0xdf800000 - 0xff000000 ( 504 MB)
[ 0.000000] lowmem : 0xc0000000 - 0xdf000000 ( 496 MB)
[ 0.000000] pkmap : 0xbfe00000 - 0xc0000000 ( 2 MB)
[ 0.000000] modules : 0xbf000000 - 0xbfe00000 ( 14 MB)
[ 0.000000] .text : 0xc0008000 - 0xc06d1374 (6949 kB)
[ 0.000000] .init : 0xc06d2000 - 0xc0705380 ( 205 kB)
[ 0.000000] .data : 0xc0706000 - 0xc074cf78 ( 284 kB)
[ 0.000000] .bss : 0xc074cf84 - 0xc078d9fc ( 259 kB)
[ 0.000000] Preemptible hierarchical RCU implementation.
[ 0.000000] Dump stacks of tasks blocking RCU-preempt GP.
[ 0.000000] RCU restricting CPUs from NR_CPUS=4 to nr_cpu_ids=2.
[ 0.000000] RCU: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=2
[ 0.000000] NR_IRQS:16 nr_irqs:16 16
[ 0.000000] ps7-slcr mapped to df802000
[ 0.000000] zynq_clock_init: clkc starts at df802100
[ 0.000000] Zynq clock init
[ 0.000016] sched_clock: 64 bits at 333MHz, resolution 3ns, wraps every 3298534883328ns
[ 0.000322] ps7-ttc #0 at df804000, irq=43
[ 0.000632] Console: colour dummy device 80x30
[ 0.000663] Calibrating delay loop... 1325.46 BogoMIPS (lpj=6627328)
[ 0.040216] pid_max: default: 32768 minimum: 301
[ 0.040438] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
[ 0.040459] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
[ 0.042626] CPU: Testing write buffer coherency: ok
[ 0.042973] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
[ 0.043033] Setting up static identity map for 0x4c4b00 - 0x4c4b58
[ 0.043258] L310 cache controller enabled
[ 0.043278] l2x0: 8 ways, CACHE_ID 0x410000c8, AUX_CTRL 0x72760000, Cache size: 512 kB
[ 0.121043] CPU1: Booted secondary processor
[ 0.210234] CPU1: thread -1, cpu 1, socket 0, mpidr 80000001
[ 0.210368] Brought up 2 CPUs
[ 0.210386] SMP: Total of 2 processors activated.
[ 0.210395] CPU: All CPU(s) started in SVC mode.
[ 0.211092] devtmpfs: initialized
[ 0.213511] VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4
[ 0.214763] regulator-dummy: no parameters
[ 0.223344] NET: Registered protocol family 16
[ 0.225660] DMA: preallocated 256 KiB pool for atomic coherent allocations
[ 0.227989] cpuidle: using governor ladder
[ 0.228002] cpuidle: using governor menu
[ 0.235536] syscon f8000000.ps7-slcr: regmap [mem 0xf8000000-0xf8000fff] registered
[ 0.237089] hw-breakpoint: found 5 (+1 reserved) breakpoint and 1 watchpoint registers.
[ 0.237103] hw-breakpoint: maximum watchpoint size is 4 bytes.
[ 0.237223] zynq-ocm f800c000.ps7-ocmc: ZYNQ OCM pool: 256 KiB @ 0xdf880000
[ 0.259468] bio: create slab <bio-0> at 0
[ 0.261145] vgaarb: loaded
[ 0.261867] SCSI subsystem initialized
[ 0.262758] usbcore: registered new interface driver usbfs
[ 0.262941] usbcore: registered new interface driver hub
[ 0.263181] usbcore: registered new device driver usb
[ 0.263726] media: Linux media interface: v0.10
[ 0.263884] Linux video capture interface: v2.00
[ 0.264134] pps_core: LinuxPPS API ver. 1 registered
[ 0.264145] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
[ 0.264271] PTP clock support registered
[ 0.264652] EDAC MC: Ver: 3.0.0
[ 0.265729] Advanced Linux Sound Architecture Driver Initialized.
[ 0.268739] DMA-API: preallocated 4096 debug entries
[ 0.268754] DMA-API: debugging enabled by kernel config
[ 0.268843] Switched to clocksource arm_global_timer
[ 0.289998] NET: Registered protocol family 2
[ 0.290663] TCP established hash table entries: 4096 (order: 2, 16384 bytes)
[ 0.290720] TCP bind hash table entries: 4096 (order: 3, 32768 bytes)
[ 0.290805] TCP: Hash tables configured (established 4096 bind 4096)
[ 0.290860] TCP: reno registered
[ 0.290879] UDP hash table entries: 256 (order: 1, 8192 bytes)
[ 0.290915] UDP-Lite hash table entries: 256 (order: 1, 8192 bytes)
[ 0.291172] NET: Registered protocol family 1
[ 0.291544] RPC: Registered named UNIX socket transport module.
[ 0.291557] RPC: Registered udp transport module.
[ 0.291565] RPC: Registered tcp transport module.
[ 0.291573] RPC: Registered tcp NFSv4.1 backchannel transport module.
[ 0.291587] PCI: CLS 0 bytes, default 64
[ 0.292050] hw perfevents: enabled with ARMv7 Cortex-A9 PMU driver, 7 counters available
[ 0.294120] futex hash table entries: 512 (order: 3, 32768 bytes)
[ 0.296303] jffs2: version 2.2. (NAND) © 2001-2006 Red Hat, Inc.
[ 0.296503] msgmni has been set to 967
[ 0.297311] io scheduler noop registered
[ 0.297326] io scheduler deadline registered
[ 0.297364] io scheduler cfq registered (default)
[ 0.310321] dma-pl330 f8003000.ps7-dma: Loaded driver for PL330 DMAC-2364208
[ 0.310343] dma-pl330 f8003000.ps7-dma: DBUFF-128x8bytes Num_Chans-8 Num_Peri-4 Num_Events-16
[ 0.434864] e0001000.serial: ttyPS0 at MMIO 0xe0001000 (irq = 82, base_baud = 3124999) is a xuartps
[ 1.002533] console [ttyPS0] enabled
[ 1.006830] xdevcfg f8007000.ps7-dev-cfg: ioremap 0xf8007000 to df866000
[ 1.014470] [drm] Initialized drm 1.1.0 20060810
[ 1.031674] brd: module loaded
[ 1.041159] loop: module loaded
[ 1.050913] e1000e: Intel(R) PRO/1000 Network Driver - 2.3.2-k
[ 1.056661] e1000e: Copyright(c) 1999 - 2013 Intel Corporation.
[ 1.064713] libphy: XEMACPS mii bus: probed
[ 1.069084] ------------- phy_id = 0x3625e62
[ 1.073829] xemacps e000b000.ps7-ethernet: pdev->id -1, baseaddr 0xe000b000, irq 54
[ 1.082608] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[ 1.089332] ehci-pci: EHCI PCI platform driver
[ 1.096552] zynq-dr e0002000.ps7-usb: Unable to init USB phy, missing?
[ 1.103387] usbcore: registered new interface driver usb-storage
[ 1.110284] mousedev: PS/2 mouse device common for all mice
[ 1.116377] i2c /dev entries driver
[ 1.123356] zynq-edac f8006000.ps7-ddrc: ecc not enabled
[ 1.128877] cpufreq_cpu0: failed to get cpu0 regulator: -19
[ 1.134777] Xilinx Zynq CpuIdle Driver started
[ 1.139668] sdhci: Secure Digital Host Controller Interface driver
[ 1.145760] sdhci: Copyright(c) Pierre Ossman
[ 1.150176] sdhci-pltfm: SDHCI platform and OF driver helper
[ 1.156918] mmc0: no vqmmc regulator found
[ 1.160955] mmc0: no vmmc regulator found
[ 1.198861] mmc0: SDHCI controller on e0100000.ps7-sdio [e0100000.ps7-sdio] using ADMA
[ 1.207563] usbcore: registered new interface driver usbhid
[ 1.213071] usbhid: USB HID core driver
[ 1.217802] nand: device found, Manufacturer ID: 0x2c, Chip ID: 0xda
[ 1.224095] nand: Micron MT29F2G08ABAEAWP
[ 1.228067] nand: 256MiB, SLC, page size: 2048, OOB size: 64
[ 1.234010] Bad block table found at page 131008, version 0x01
[ 1.240228] Bad block table found at page 130944, version 0x01
[ 1.246279] 3 ofpart partitions found on MTD device pl353-nand
[ 1.252044] Creating 3 MTD partitions on "pl353-nand":
[ 1.257149] 0x000000000000-0x000002000000 : "BOOT.bin-env-dts-kernel"
[ 1.265272] 0x000002000000-0x00000b000000 : "angstram-rootfs"
[ 1.272613] 0x00000b000000-0x000010000000 : "upgrade-rootfs"
[ 1.281627] TCP: cubic registered
[ 1.284862] NET: Registered protocol family 17
[ 1.289614] Registering SWP/SWPB emulation handler
[ 1.295524] regulator-dummy: disabling
[ 1.299923] UBI: attaching mtd1 to ubi0
[ 1.825702] UBI: scanning is finished
[ 1.837349] UBI: attached mtd1 (name "angstram-rootfs", size 144 MiB) to ubi0
[ 1.844435] UBI: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
[ 1.851197] UBI: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
[ 1.857861] UBI: VID header offset: 2048 (aligned 2048), data offset: 4096
[ 1.864739] UBI: good PEBs: 1152, bad PEBs: 0, corrupted PEBs: 0
[ 1.870719] UBI: user volume: 1, internal volumes: 1, max. volumes count: 128
[ 1.877826] UBI: max/mean erase counter: 7/3, WL threshold: 4096, image sequence number: 1283732989
[ 1.886869] UBI: available PEBs: 0, total reserved PEBs: 1152, PEBs reserved for bad PEB handling: 40
[ 1.896087] UBI: background thread "ubi_bgt0d" started, PID 1080
[ 1.896093] drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
[ 1.900189] ALSA device list:
[ 1.900192] No soundcards found.
[ 1.916555] UBIFS: background thread "ubifs_bgt0_0" started, PID 1082
[ 1.945448] UBIFS: recovery needed
[ 2.006535] UBIFS: recovery completed
[ 2.010227] UBIFS: mounted UBI device 0, volume 0, name "rootfs"
[ 2.016150] UBIFS: LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
[ 2.025319] UBIFS: FS size: 128626688 bytes (122 MiB, 1013 LEBs), journal size 9023488 bytes (8 MiB, 72 LEBs)
[ 2.035173] UBIFS: reserved for root: 0 bytes (0 KiB)
[ 2.040209] UBIFS: media format: w4/r0 (latest is w4/r0), UUID C72F8006-6DFF-46BA-BBE9-380960A89F92, small LPT model
[ 2.051729] VFS: Mounted root (ubifs filesystem) on device 0:11.
[ 2.059158] devtmpfs: mounted
[ 2.062263] Freeing unused kernel memory: 204K (c06d2000 - c0705000)
[ 2.912010] random: dd urandom read with 0 bits of entropy available
[ 3.338876]
[ 3.338876] bcm54xx_config_init
[ 3.948885]
[ 3.948885] bcm54xx_config_init
[ 7.949724] xemacps e000b000.ps7-ethernet: Set clk to 24999999 Hz
[ 7.955813] xemacps e000b000.ps7-ethernet: link up (100/FULL)
[ 24.356096] In axi fpga driver!
[ 24.359191] request_mem_region OK!
[ 24.362561] AXI fpga dev virtual address is 0xdf9fc000
[ 24.367666] *base_vir_addr = 0x8c510
[ 24.383194] In fpga mem driver!
[ 24.386268] request_mem_region OK!
[ 24.389888] fpga mem virtual address is 0xe2000000
[ 25.208286]
[ 25.208286] bcm54xx_config_init
[ 25.838238]
[ 25.838238] bcm54xx_config_init
[ 29.838719] xemacps e000b000.ps7-ethernet: Set clk to 24999999 Hz
[ 29.844741] xemacps e000b000.ps7-ethernet: link up (100/FULL)
[ 412.308717]
[ 412.308717] bcm54xx_config_init
[ 416.309189] xemacps e000b000.ps7-ethernet: Set clk to 24999999 Hz
[ 416.315205] xemacps e000b000.ps7-ethernet: link up (100/FULL)
[ 624.602972] random: nonblocking pool is initialized
This is XILINX board. Totalram: 507527168
Detect 512MB control board of XILINX
DETECT HW version=0008c510
miner ID : 813875cc68808814
Miner Type = S9
AsicType = 1387
real AsicNum = 63
use critical mode to search freq...
get PLUG ON=0x000000e0
Find hashboard on Chain[5]
Find hashboard on Chain[6]
Find hashboard on Chain[7]
set_reset_allhashboard = 0x0000ffff
Check chain[5] PIC fw version=0x03
Check chain[6] PIC fw version=0x03
Check chain[7] PIC fw version=0x03
chain[5]: [63:255] [63:255] [63:255] [63:255] [63:255] [63:255] [63:255] [63:255]
has freq in PIC, will disable freq setting.
chain[5] has freq in PIC and will jump over...
Chain[5] has core num in PIC
Check chain[5] PIC fw version=0x03
chain[6]: [63:255] [63:255] [63:255] [63:255] [63:255] [63:255] [63:255] [63:255]
has freq in PIC, will disable freq setting.
chain[6] has freq in PIC and will jump over...
Chain[6] has core num in PIC
Chain[6] ASIC[17] has core num=4
Chain[6] ASIC[61] has core num=2
Check chain[6] PIC fw version=0x03
chain[7]: [63:255] [63:255] [63:255] [63:255] [63:255] [63:255] [63:255] [63:255]
has freq in PIC, will disable freq setting.
chain[7] has freq in PIC and will jump over...
Chain[7] has core num in PIC
Check chain[7] PIC fw version=0x03
get PIC voltage=74 on chain[5], value=900
get PIC voltage=74 on chain[6], value=900
get PIC voltage=74 on chain[7], value=900
set_reset_allhashboard = 0x00000000
chain[5] temp offset record: 62,0,0,0,0,0,35,28
chain[5] temp chip I2C addr=0x98
chain[5] has no middle temp, use special fix mode.
chain[6] temp offset record: 62,0,0,0,0,0,35,28
chain[6] temp chip I2C addr=0x98
chain[6] has no middle temp, use special fix mode.
chain[7] temp offset record: 62,0,0,0,0,0,35,28
chain[7] temp chip I2C addr=0x98
chain[7] has no middle temp, use special fix mode.
set_reset_allhashboard = 0x0000ffff
set_reset_allhashboard = 0x00000000
CRC error counter=0
set command mode to VIL
--- check asic number
After Get ASIC NUM CRC error counter=0
set_baud=0
The min freq=700
set real timeout 52, need sleep=379392
After TEST CRC error counter=0
set_reset_allhashboard = 0x0000ffff
set_reset_allhashboard = 0x00000000
search freq for 1 times, completed chain = 3, total chain num = 3
set_reset_allhashboard = 0x0000ffff
set_reset_allhashboard = 0x00000000
restart Miner chance num=2
waiting for receive_func to exit!
waiting for pic heart to exit!
bmminer not found=24627 root 0:00 grep bmminer
bmminer not found, restart bmminer ...
bmminer not found=25241 root 0:00 grep bmminer
bmminer not found, restart bmminer ...
This is user mode for mining
Detect 512MB control board of XILINX
Miner Type = S9
Miner compile time: Fri Nov 17 17:37:49 CST 2017 type: Antminer S9set_reset_allhashboard = 0x0000ffff
set_reset_allhashboard = 0x00000000
set_reset_allhashboard = 0x0000ffff
miner ID : 813875cc68808814
set_reset_allhashboard = 0x0000ffff
Checking fans!get fan[2] speed=4320
get fan[2] speed=4320
get fan[2] speed=4320
get fan[2] speed=4320
get fan[2] speed=4320
get fan[2] speed=4320
get fan[2] speed=4320
get fan[2] speed=4320
get fan[2] speed=4320
get fan[5] speed=5640
get fan[2] speed=4320
get fan[5] speed=5640
get fan[2] speed=4320
get fan[5] speed=5640
chain[5]: [63:255] [63:255] [63:255] [63:255] [63:255] [63:255] [63:255] [63:255]
Detect: use voltage limit rules on single board!
Detect: S9_63 use voltage level=1 : 1
Chain[J6] has backup chain_voltage=890
Check chain[5] PIC fw version=0x03
chain[6]: [63:255] [63:255] [63:255] [63:255] [63:255] [63:255] [63:255] [63:255]
Detect: use voltage limit rules on single board!
Detect: S9_63 use voltage level=1 : 1
Chain[J7] has backup chain_voltage=890
Check chain[6] PIC fw version=0x03
chain[7]: [63:255] [63:255] [63:255] [63:255] [63:255] [63:255] [63:255] [63:255]
Detect: use voltage limit rules on single board!
Detect: S9_63 use voltage level=1 : 1
Chain[J8] has backup chain_voltage=890
Check chain[7] PIC fw version=0x03
Chain[J6] orignal chain_voltage_pic=91 value=890
Chain[J7] orignal chain_voltage_pic=91 value=890
Chain[J8] orignal chain_voltage_pic=91 value=890
set_reset_allhashboard = 0x0000ffff
set_reset_allhashboard = 0x00000000
Chain[J6] has 63 asic
Chain[J7] has 39 asic
set_reset_hashboard = 0x00000040
set_reset_hashboard = 0x00000000
retry Chain[J7] has 39 asic
set_reset_hashboard = 0x00000040
set_reset_hashboard = 0x00000000
retry Chain[J7] has 39 asic
set_reset_hashboard = 0x00000040
set_reset_hashboard = 0x00000000
retry Chain[J7] has 39 asic
set_reset_hashboard = 0x00000040
set_reset_hashboard = 0x00000000
retry Chain[J7] has 39 asic
set_reset_hashboard = 0x00000040
set_reset_hashboard = 0x00000000
retry Chain[J7] has 39 asic
set_reset_hashboard = 0x00000040
set_reset_hashboard = 0x00000000
retry Chain[J7] has 39 asic
Chain[J8] has 63 asic
Chain[J6] has core num in PIC
Chain[J7] has core num in PIC
Chain[J7] ASIC[17] has core num=4
Chain[J7] ASIC[61] has core num=2
Chain[J8] has core num in PIC
miner total rate=13591GH/s fixed rate=13500GH/s
read PIC voltage=940 on chain[5]
Chain:5 chipnum=63
Chain[J6] voltage added=0.0V
Chain:5 temp offset=0
Chain:5 base freq=631
Asic[ 0]:631
Asic[ 1]:631 Asic[ 2]:631 Asic[ 3]:631 Asic[ 4]:631 Asic[ 5]:631 Asic[ 6]:631 Asic[ 7]:631 Asic[ 8]:631
Asic[ 9]:631 Asic[10]:631 Asic[11]:631 Asic[12]:631 Asic[13]:631 Asic[14]:631 Asic[15]:631 Asic[16]:631
Asic[17]:631 Asic[18]:631 Asic[19]:631 Asic[20]:631 Asic[21]:631 Asic[22]:631 Asic[23]:631 Asic[24]:631
Asic[25]:631 Asic[26]:631 Asic[27]:631 Asic[28]:631 Asic[29]:631 Asic[30]:631 Asic[31]:631 Asic[32]:631
Asic[33]:631 Asic[34]:631 Asic[35]:631 Asic[36]:631 Asic[37]:631 Asic[38]:631 Asic[39]:631 Asic[40]:631
Asic[41]:631 Asic[42]:631 Asic[43]:631 Asic[44]:631 Asic[45]:631 Asic[46]:631 Asic[47]:631 Asic[48]:631
Asic[49]:631 Asic[50]:631 Asic[51]:631 Asic[52]:631 Asic[53]:631 Asic[54]:631 Asic[55]:631 Asic[56]:631
Asic[57]:631 Asic[58]:631 Asic[59]:631 Asic[60]:631 Asic[61]:631 Asic[62]:631
Chain:5 max freq=631
Chain:5 min freq=631
Check Chain[J6] ASIC RT error: (asic index start from 1-63)
Check Chain[J7] ASIC RT error: (asic index start from 1-63)
Check Chain[J8] ASIC RT error: (asic index start from 1-63)
Done check_asic_reg
do read temp on Chain[5]
Chain[5] Chip[62] TempTypeID=55 middle offset=24
Chain[5] Chip[62] local Temp=56
Chain[5] Chip[62] middle Temp=47
Special fix Chain[5] Chip[62] middle Temp = 71
Done read temp on Chain[5]
do read temp on Chain[6]
Done read temp on Chain[6]
do read temp on Chain[7]
Chain[7] Chip[62] TempTypeID=55 middle offset=25
Chain[7] Chip[62] local Temp=57
Chain[7] Chip[62] middle Temp=47
Special fix Chain[7] Chip[62] middle Temp = 72
Done read temp on Chain[7]
set FAN speed according to: temp_highest=57 temp_top1[PWM_T]=57 temp_top1[TEMP_POS_LOCAL]=57 temp_change=1 fix_fan_steps=0
FAN PWM: 62
read_temp_func Done!
CRC error counter=3729
Any other idea, how to fix it?
Title: Re: Antminer S9 one hashboard stop appearing in STATUS
Post by: Firstblackhaw on January 20, 2018, 04:54:13 AM
Hi
Sometime my S9 have same proplem. I unplug power cable, unplug all 6 pin 12 Vdc connect from power supply to machine. Wait 5 minute and plug all back. This is solve my problem.
I think that this problem occur when temp hash board to high and HW asic component error so machine try to reboot, or there are sync sock of power supply.
Title: Re: Antminer S9 one hashboard stop appearing in STATUS
Post by: arominer on January 24, 2018, 06:08:46 AM
Firstblackhaw
You're a gent, this seems to have fixed my problem. Previously I flashed firmware and reset, which always got the board hashing for 1 - 2 hours, but I tried everything you stated and it's been 4+ hours and it's OK.
I do wonder whether it's the PSU....
Title: Re: Antminer S9 one hashboard stop appearing in STATUS
Post by: arominer on January 24, 2018, 08:40:03 PM
Unfortunately it didn't work. I have just switched pools however, so I am going to see if this may work....
Again each time I reboot it restores hashing
Title: Re: Antminer S9 one hashboard stop appearing in STATUS
Post by: lightfoot on February 05, 2018, 05:15:12 PM
Unfortunately it didn't work. I have just switched pools however, so I am going to see if this may work....
Again each time I reboot it restores hashing
So it runs for a bit then crashes? May be a bad chip that is showing signs of thermal expansion. Want to send it over and I'll look at it in IR? C
|
