Pages:
Author

Topic: Repairing Antminer S9j (Read 329 times)

member
Activity: 199
Merit: 37
March 24, 2023, 08:53:09 PM
#30

OP, since you like fixing stuff, the issue with that bad hashboard is kind of straight forward, the kernel log states

Code:
driver-btm-c5.c:13522:bitmain_c5_init: retry Chain[J7] has 15 asic


This means that the test signal stops at chip 15, it either reaches there and doesn't move to the next one, or simply just doesn't get there, so you are going to need to check chips 15 and 14, here is a good guide on how to proceed.

https://www.zeusbtc.com/manuals/Antminer-S9-Hash-Board-Repair-Guide.asp

Thank you very much, I'll have a closer look at it when I take the miner apart the next time. At the moment the broken hashboard is in the running miner (not powered or connected to the control board, just for stopping air from finding an easier way past the 2 running hashboards).
member
Activity: 199
Merit: 37
March 24, 2023, 08:50:23 PM
#29
Sounds like the PSU overheats and triggers some kind of protection. You can check if it is full of dust or the fan runs to slow. The issue with the very loud PSU is a general issue with the standard PSU and can be solved with aftermarket Computer PSUs. If you open up the PSU be careful, it contains power even if not plugged in!

Thanks, I had already cleaned the PSU before it failed and it is still clean.

What ever made it fail (10VDC instead of 12vDC) did not revert by just cooling down again, it was still broken hours or days after the drop to 10V.
But then after weeks in the 'naughty box', when I decided to investigate, it was making 12VDC again.

I have since then powered the miner (with only 2 instead of 3 hashboards) for a day or so with the dodgy PSU and it has continued to function as it should.
Interestingly, I cannot detect a difference in efficiency (measured at the wall) between using the beat-up and noisy old PSU and my almost brand new 2050W PSU, except that the new one is practically silent.

The old PSU is back in the 'naughty box' for being too loud (but I am quite certain that the noise level is the same as when it was new. The noise would not matter if the miner was operating by using it's stock fans, but the miner is now very quiet due to the Phresh 8" 240V fan).
legendary
Activity: 2170
Merit: 6279
be constructive or S.T.F.U
March 22, 2023, 07:59:19 PM
#28
You can try to run the hashboard with a different (higher) frequency with Braiinos

Do you mean higher voltage? because usually that is the case, many hashboards will need lower frequency or/and higher voltage to run stable, higher frequency cases issues even to stable hashboards.

OP, since you like fixing stuff, the issue with that bad hashboard is kind of straight forward, the kernel log states

Code:
driver-btm-c5.c:13522:bitmain_c5_init: retry Chain[J7] has 15 asic


This means that the test signal stops at chip 15, it either reaches there and doesn't move to the next one, or simply just doesn't get there, so you are going to need to check chips 15 and 14, here is a good guide on how to proceed.

https://www.zeusbtc.com/manuals/Antminer-S9-Hash-Board-Repair-Guide.asp
hero member
Activity: 938
Merit: 642
Magic
March 22, 2023, 01:05:39 PM
#27
Sounds like the PSU overheats and triggers some kind of protection. You can check if it is full of dust or the fan runs to slow. The issue with the very loud PSU is a general issue with the standard PSU and can be solved with aftermarket Computer PSUs. If you open up the PSU be careful, it contains power even if not plugged in!
member
Activity: 199
Merit: 37
March 17, 2023, 11:44:44 PM
#26
Bugger me, but the old PSU is suddenly working again!

After it has been sitting in time-out in a cardboard box for over a month, I decided to have a look why it is producing 10VDC instead of 12VDC, and it is again making 11.97VDC.

I wonder if there is some component that fails when used for some hours, and then slowly recovers while resting?

Any ideas what this 'self-repairing' part may be?

To find out, I have connected the old PSU to the miner with it's 2 functioning hashboards. It is now running BraiinsOS+ so I have much control over the power consumption.

The old PSU is at least several times louder than the entire miner with the 200mm Phresh fan cooling it! It is impossible to hear the miner because of the PSU noise.

I start testing the old PSU by running the miner on 900W setting, which will actually use about 657W because of the missing hashboard. This setting is the most efficient one I have found so far, using 74J/TH at the wall, including PSU, fan and WiFi extender.

I'll crank up the power until the PSU fails again and then see if anythings is obvious as the cause.
hero member
Activity: 728
Merit: 512
March 16, 2023, 07:00:17 AM
#25
I bought a used S9j miner and it is not in good working order.

Now I am trying to decide if I should send it back or negotiate a price drop and then learn how to repair it. Any helpful hints would be much appreciated!

One of the three hashboards does not work. The red LED comes on sometimes, and sometimes a small number shows in the GH/S(RT) column, but it never heats up or produces significant hashes. Mostly it hashes zero.



The power supply has damage to multiple cables, they must have been chafing against sharp metal shelve edges or something like it. L


Some of the output capacitors in the PSU seem to be getting much hotter than others, and the miner (hashing on 2 boards only) stops hashing every few minutes and starts over. I don't know if the PSU might be too weak, have not investigated in any detail yet.

Questions:
1) Is it potentially possible to repair the hashboard? I have swapped over the cables between the control board and the hash board, the fault is in the hashboard not the cable or control board.

2) Can the capacitors be replaced? It looks to me like I can solder new ones in, but I have no idea if they are hard to find, and if I would need to replace all of them instead of the 2 that look hotter on an infrared photo.

3) Could a replacement hashboard be used, or do they need to be a 'matching set' or specific serial number?

4) I think I can de-solder the cables at the PSU board and then put shrink-wrap around the damaged parts and solder them back on. Or is that a particularly stupid idea?

Thanks for any helpful hints!
If I have to be frank with you mate you have got a lot of work and spending to do. From all indication going by your explanations I think before you end up making replacements and repairs of the said miner parts in addition to any negotiation amount the seller and you might agreed upon you must have end up expending a significant sum that could have afford you with an almost new miner in the market.  It would be better to send it back cause it's most likely after you must have made few repairs you may not make some profits enough to cover for all your expenses before another repairing needs may arise again.
member
Activity: 199
Merit: 37
March 02, 2023, 04:57:16 PM
#24
Quote
The 140mm is 158CFM, while the 200mm is just 88CFM. The factory fans are usually 210CFM..
And do remember that the air flow rate is not the whole story - it is the air flow against back pressure that matters the most.

Miner fans are chosen to work against a fair bit of restriction caused by the heatsinks. (that is why they run so fast and loud) Most regular PC case fans are only rated for free flow and a fairly low back pressure so against the restrictions the resulting flow will be MUCH lower.

One interesting result from testing the S9J with Phresh fan is that some of the high pitch whining noise is actually created in the miner, not in the fan. Once airflow gets high enough (or probably 'too high'), that wind starts to howl around some corners of the heat sinks.
member
Activity: 199
Merit: 37
March 02, 2023, 04:53:31 PM
#23
I have seen people successfully using the 140mm 3k "industrial" Noctua with 3d printed adapters, but 200mm? Cheesy

The 140mm is 158CFM, while the 200mm is just 88CFM. The factory fans are usually 210CFM...

I don't recommend using the 200mm Noctua, but I had some lying around and also half-finished 3D print designs for adaptors, so it was worth a try.
I still think in cold environments this could work quite well, for example to keep a cellar frost free in winter without hearing the miner upstairs. The 200mm fans just turn down the speed of the stock fans by a few notches, but it does make a difference to the noise level.
legendary
Activity: 3612
Merit: 2506
Evil beware: We have waffles!
March 02, 2023, 02:24:19 PM
#22
Quote
The 140mm is 158CFM, while the 200mm is just 88CFM. The factory fans are usually 210CFM..
And do remember that the air flow rate is not the whole story - it is the air flow against back pressure that matters the most.

Miner fans are chosen to work against a fair bit of restriction caused by the heatsinks. (that is why they run so fast and loud) Most regular PC case fans are only rated for free flow and a fairly low back pressure so against the restrictions inside of a miner the resulting flow will be MUCH lower.
legendary
Activity: 1988
Merit: 1561
CLEAN non GPL infringing code made in Rust lang
March 02, 2023, 02:05:42 PM
#21
I have seen people successfully using the 140mm 3k "industrial" Noctua with 3d printed adapters, but 200mm? Cheesy

The 140mm is 158CFM, while the 200mm is just 88CFM. The factory fans are usually 210CFM...
member
Activity: 199
Merit: 37
February 13, 2023, 07:32:47 PM
#20
I have added 2 Noctua 200mm fans.

It makes some difference to the noise levels, but not as much as I hoped. I think that might be due to the hot weather, the ambient air is 31degC . In Winter the cooling effect of the added fans will probably lead to a much more drastic reduction in the stock-fan speeds and therefore more noise reduction.

What I get with 2 out of 3 hashboards powered up, using Low Power Enhanced Mode in 31-32 deg C air is this:

    Power at wall (W):   558
    Fans 5+6 speed (rpm): 4800  4560
             
    Temp(Chip2):     66  64
           
     TH/s(RT)    3.536    3.566

    W/THs: 79 (including PSU losses)





Adapter for 200mm Noctua fan printed using Polymax PC-FR.

Openscad code in case someone wants to print one:
Code:
$fn=160;
_min = 0.01; // translate([-_min,0,0])

difference(){// for section view of S9J to Noctua 200mm fan dapter

union(){// 200mm Noctua fan attachment for S9J

difference(){// Main fan shroud hull to be hollowed by 2nd hull


hull(){// Outer hull


// Opening for S9J fan adapter - a sqare with extra's for the screws
// inner cube: 119.5
// outer cube: 119.5 + 2 x wall thickness 3 layers = 121.9mm
cube([121.9, 121.9, 0.1], center=true);// S9j fan outer square size + 1.2mm wall thickness

translate([0,0,-50])// z determines height of shroud
cylinder(r=98.5, h=0.1);// defines shape of 200mm fan round attachment

}
// End outer hull


hull(){// Inner hull


// Opening for S9J fan adapter - a sqare with extra's for the screws
// inner cube: 119.5
// outer cube: 119.5 + wall thickness 3 layers = 120.7mm
cube([119.5, 119.5, 0.1], center=true);// S9j fan outer square size + 1.2mm wall thickness

translate([0,0,-50])// z determines height of shroud
cylinder(r=97.3, h=0.1);// defines shape of 200mm fan round attachment

}
// End outer hull

}
// End difference main fan shroud

translate([0,0,5])
difference(){// Square part that fits on S9J fan

cube([121.9, 121.9, 10], center=true);// S9j fan outer square size + 1.2mm wall thickness
cube([119.5, 119.5, 10], center=true);// S9j fan outer square size + 1.2mm wall thickness

}
// End difference square part to fit on S9j fan



difference(){// Screw holders - removing the outer fan shroud to remove overhangs on outside of shroud

union(){// 4 screw holders

difference(){// hollowing and adjusting 1 screw holder

translate([62.5,-62.5,-8])
rotate([-35,-45,0])
translate([0,0,-5.5])
cylinder(r=7,h=30, center=false);


translate([52.5,-52.5,-10])
cylinder (r=2.35, h=21);// screw hole

translate([0,0,10])
cube([200,200,20],center=true);

}
// End difference

rotate([0,0,90])
difference(){// hollowing and adjusting 1 screw holder

translate([62.5,-62.5,-8])
rotate([-35,-45,0])
translate([0,0,-5.5])
cylinder(r=7,h=30, center=false);

translate([52.5,-52.5,-10])
cylinder (r=2.35, h=21);// screw hole

translate([0,0,10])
cube([200,200,20],center=true);

}
// End difference

rotate([0,0,180])
difference(){// hollowing and adjusting 1 screw holder

translate([62.5,-62.5,-8])
rotate([-35,-45,0])
translate([0,0,-5.5])
cylinder(r=7,h=30, center=false);

translate([52.5,-52.5,-10])
cylinder (r=2.35, h=21);// screw hole

translate([0,0,10])
cube([200,200,20],center=true);

}
// End difference

rotate([0,0,270])
difference(){// hollowing and adjusting 1 screw holder

translate([62.5,-62.5,-8])
rotate([-35,-45,0])
translate([0,0,-5.5])
cylinder(r=7,h=30, center=false);

translate([52.5,-52.5,-10])
cylinder (r=2.35, h=21);// screw hole

translate([0,0,10])
cube([200,200,20],center=true);

}
// End difference

}
// End union of 4 screw holders


difference(){// making negative of outer hull to remove screw holder overhangs on outside

cube([500,500,500],center=true);


hull(){// Outer hull
cube([121.9, 121.9, 0.1], center=true);// S9j fan outer square size + 1.2mm wall thickness

translate([0,0,-50])// z determines height of shroud
cylinder(r=98.5, h=0.1);// defines shape of 200mm fan round attachment

}
// End outer hull

}
// End difference negative of outer hull

}
// End difference making screw holders by removing outer hull

translate([0,0,0.5])
difference(){// 200mm fan attachment level top plate
// holes distance: 170mm ; 4.5mm diameter But it seems to shrink after printing,
// width 140mm
// thickness 32mm

translate([0,0,-50])
cube([200,200,1.0], center=true);// top plate


union(){// 4 x Quarter rings for corner rounding of the top late

// rounding corners by differencing 1/4th rings in each corner
translate([89,89,-100])// moving the quarter ring where it needs to be
difference(){// a quarter ring
cylinder (r=25, h=200);

cylinder (r=11, h=200);

rotate([0,0,45])
cube([15,1500,400],center=true);

translate([-18,0,0])
rotate([0,0,45])
cube([25,1500,400],center=true);




}
// End difference of a quarter ring

rotate([0,0,90])
translate([89,89,-100])// moving the quarter ring where it needs to be
difference(){// a quarter ring
cylinder (r=25, h=200);

cylinder (r=11, h=200);

rotate([0,0,45])
cube([15,1500,400],center=true);

translate([-18,0,0])
rotate([0,0,45])
cube([25,1500,400],center=true);




}
// End difference of a quarter ring

rotate([0,0,180])
translate([89,89,-100])// moving the quarter ring where it needs to be
difference(){// a quarter ring
cylinder (r=25, h=200);

cylinder (r=11, h=200);

rotate([0,0,45])
cube([15,1500,400],center=true);

translate([-18,0,0])
rotate([0,0,45])
cube([25,1500,400],center=true);




}
// End difference of a quarter ring

rotate([0,0,270])
translate([89,89,-100])// moving the quarter ring where it needs to be
difference(){// a quarter ring
cylinder (r=25, h=200);

cylinder (r=11, h=200);

rotate([0,0,45])
cube([15,1500,400],center=true);

translate([-18,0,0])
rotate([0,0,45])
cube([25,1500,400],center=true);




}
// End difference of a quarter ring

}
// End union 4 x quarter rings for corner rounding


translate([0,0,-55])
cylinder(h=100.02, r=97.5);// 200mm fan sized hole 192.5mm diameter

translate([-85,-85,-55])
union(){// Fan screw holes group of 4

translate([0,0,0])
cylinder(h=1000, r=2.35);// increased from r=2.25 in v20221030c

translate([170,0,0])
cylinder(h=1000, r=2.35);

translate([0,170,0])
cylinder(h=1000, r=2.35);

translate([170,170,0])
cylinder(h=1000, r=2.35);

}
// End union fan screw holes group of 4

}
// End difference fan attachment level top

}
// End 200mm Noctua S9j adapter


union(){// sectioning

*translate([0,0,-59])
cube([200,200,100],center=true);// sectioning for partial print test

rotate([0,0,45])
translate([50,50,-50])
cube([100,100,200],center=true);// to section the whole thing

translate([50,50,-50])
cube([100,100,200],center=true);// to section the whole thing
}
// End union for sectioning

}
// End difference of entire fan shroud assembly for sectioning

member
Activity: 199
Merit: 37
February 05, 2023, 07:43:39 AM
#19

That's a normal value if it's coming from the power supply and actually the power changes depending on the control board signal that is why you see some different power output and also you can adjust power and frequencies from this unit.

There is Vnish firmware where you can adjust power and frequencies or use auto-tuning and let it run for a while until it found the best freq and power for your miner to run stable.

Auto-tuning on BraiinsOS is also a good option as suggested above to test until you get some hints. But I guess PSU is working fine 1 of your hashboard is I think overheating after running for a while so auto-tuning is the best solution to still keep some chips running safely(From red to green).

The (broken) PSU gets no feedback from the miner (apart from the current draw) and it should provide stable 12V DC output if the current draw does not exceed it's specifications. It puts out 11V DC when open cicuit and also when the miner is connected.

The faulty hashboard does not overheat, it never draws any significant amount of power and stays cool. It never reports a temperature reading and it never heats the exhaust air and it never draws much power as measured at the AC wall outlet.

With a new 700W PSU I can operate each of the 2 good hash boards individually, and the bad hashboard stays dead and cold.

Anyway, I found a way to make the S9J a little quieter: I 3D printed a baffle from fire retardant polycarbonate so that the air flow is directed mainly to the top of the three hashboards. Until a more powerful PSU arrives, I can only run one hashboard at a time anyway.

No point pushing cooling air through the inactive boards.



Openscad code in case someone wants to use it (the plate could be a bit thinner and the bottom corners need a touch of trimming after printing):
Code:
union(){// Baffle for top slot single board use S9J
// 125mm wide at slots
// 120mm wide without slots
// 2.0mm thick slots
// 66mm high
// first slot 25mm - 27mm hight
// 2nd slot 64-66mm hight
// spacers to closing plate: 10mm high and 5mm in addition to the 2.5mm

difference(){// creating slot protrusions in plate

cube([125,66,2],center=true);

translate([-123,20.5,0])
cube([125,25,2],center=true);

translate([-123,-12.4999,0])
cube([125,37,2],center=true);

translate([123,20.5001,0])
cube([125,25,2],center=true);

translate([123,-12.4999,0])
cube([125,37,2],center=true);

}
// End difference for creating slot protrusions in plate

translate([55,6,-1])
cube([7.5,2,10]);

translate([55,-33,-1])
cube([7.5,2,10]);

translate([-62.5,6,-1])
cube([7.5,2,10]);

translate([-62.5,-33,-1])
cube([7.5,2,10]);

}
// End union baffle for top slot single board use

Fits nicely and is held firmly in place once the plate for the fan is crewed on again.




The main effect of the baffle is less noise with slightly cooler chip temperature (using a 700W PSU and only connecting the top board in the S9J, in about 28C air temp and in 'Low Power Enhanced Mode)':

Without baffle:
    Power at wall (W):    305.5
    Fans 5+6 speed:        4920     4680
    Temp(Chip2):        68
    TH/s(RT)        3.560
    W/THs:        85.81

With Baffle:
    Power at wall (W):        303.5
    Fans 5+6 speed:      4440    4320
    Temp(Chip2):       67
    TH/s(RT)      3.548
    W/THs:        85.54

That is a lot quieter than it would be if it was running full bore, but it is still way way louder than my heavily modified Apollo when it's hashing at a similar rate.

But, I can buy several crappy Antminer S9J's for the price of 1 new Apollo and the extra fan to make it less noisy.

Either of them only make financial sense if you think in Sats and/or have free electricity.

But this cheap and partially tamed used S9J can now be used part time at a house with solar panels when the panels produce a little more than what can be used or sold to the grid.

But still needs to get quieter......
legendary
Activity: 3206
Merit: 2904
Block halving is coming.
February 03, 2023, 07:43:16 PM
#18
The PSU was working when I took the screen shots after first firing up the miner.
Two hashboards were working, one not working when I took the screenshots.
The PSU failed after running continuously for 3,5 hrs with the 2 good boards hashing and now it only makes 11V DC.

That's a normal value if it's coming from the power supply and actually the power changes depending on the control board signal that is why you see some different power output and also you can adjust power and frequencies from this unit.

There is Vnish firmware where you can adjust power and frequencies or use auto-tuning and let it run for a while until it found the best freq and power for your miner to run stable.

Auto-tuning on BraiinsOS is also a good option as suggested above to test until you get some hints. But I guess PSU is working fine 1 of your hashboard is I think overheating after running for a while so auto-tuning is the best solution to still keep some chips running safely(From red to green).
member
Activity: 199
Merit: 37
February 03, 2023, 06:36:13 PM
#17
You can try to run the hashboard with a different (higher) frequency with Braiinos
You can run it from a micro SD, only for the test, and after that you will be able to use the stock firmware again when you remove the sd card

I had some dead hashboards with Antminer S9j, S9 and R4.
In most cases Braiinos helped a lot, I cannot really explain why but to modify the frequency gives very nice results.

Please carefully read the readme/github of the firmware Braiinos before doing any major change in the settings


Edit : https://asicbasics.com/fix-it/fix-it-bitmain-antminer-s9/

This website is super cool, you should have a look on it

Cheers for that!
I had not even spotted the SD card slot on the miner! Very green and wet behind the ears!  Grin
hero member
Activity: 504
Merit: 1065
Crypto Swap Exchange
February 03, 2023, 04:00:51 PM
#16
You can try to run the hashboard with a different (higher) frequency with Braiinos
You can run it from a micro SD, only for the test, and after that you will be able to use the stock firmware again when you remove the sd card

I had some dead hashboards with Antminer S9j, S9 and R4.
In most cases Braiinos helped a lot, I cannot really explain why but to modify the frequency gives very nice results.

Please carefully read the readme/github of the firmware Braiinos before doing any major change in the settings


Edit : https://asicbasics.com/fix-it/fix-it-bitmain-antminer-s9/

This website is super cool, you should have a look on it
member
Activity: 199
Merit: 37
February 02, 2023, 06:02:32 AM
#15
Here is the kernel log created when powering up the faulty hashboard by itself (using a new 700W PSU):

Code:
[    0.000000] Booting Linux on physical CPU 0x0
[    0.000000] Linux version 3.14.0-xilinx-ga36f3af-dirty (lzq@ubuntu) (gcc version 4.8.3 20140320 (prerelease) (Sourcery CodeBench Lite 2014.05-23) ) #90 SMP PREEMPT Thu Jun 20 15:01:47 CST 2019
[    0.000000] CPU: ARMv7 Processor [413fc090] revision 0 (ARMv7), cr=18c5387d
[    0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
[    0.000000] Machine model: Xilinx Zynq
[    0.000000] cma: CMA: reserved 128 MiB at 16800000
[    0.000000] Memory policy: Data cache writealloc
[    0.000000] On node 0 totalpages: 126976
[    0.000000] free_area_init_node: node 0, pgdat c075a640, node_mem_map debd8000
[    0.000000]   Normal zone: 992 pages used for memmap
[    0.000000]   Normal zone: 0 pages reserved
[    0.000000]   Normal zone: 126976 pages, LIFO batch:31
[    0.000000] PERCPU: Embedded 8 pages/cpu @debc1000 s9344 r8192 d15232 u32768
[    0.000000] pcpu-alloc: s9344 r8192 d15232 u32768 alloc=8*4096
[    0.000000] pcpu-alloc: [0] 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: 364252K/507904K available (5094K kernel code, 292K rwdata, 1948K rodata, 209K init, 259K bss, 143652K reserved, 0K highmem)
[    0.000000] Virtual kernel memory layout:
[    0.000000]     vector  : 0xffff0000 - 0xffff1000   (   4 kB)
[    0.000000]     fixmap  : 0xfff00000 - 0xfffe0000   ( 896 kB)
[    0.000000]     vmalloc : 0xdf800000 - 0xff000000   ( 504 MB)
[    0.000000]     lowmem  : 0xc0000000 - 0xdf000000   ( 496 MB)
[    0.000000]     pkmap   : 0xbfe00000 - 0xc0000000   (   2 MB)
[    0.000000]     modules : 0xbf000000 - 0xbfe00000   (  14 MB)
[    0.000000]       .text : 0xc0008000 - 0xc06e8cf4   (7044 kB)
[    0.000000]       .init : 0xc06e9000 - 0xc071d480   ( 210 kB)
[    0.000000]       .data : 0xc071e000 - 0xc0767058   ( 293 kB)
[    0.000000]        .bss : 0xc0767064 - 0xc07a7d64   ( 260 kB)
[    0.000000] Preemptible hierarchical RCU implementation.
[    0.000000] Dump stacks of tasks blocking RCU-preempt GP.
[    0.000000] RCU restricting CPUs from NR_CPUS=4 to nr_cpu_ids=2.
[    0.000000] RCU: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=2
[    0.000000] NR_IRQS:16 nr_irqs:16 16
[    0.000000] ps7-slcr mapped to df802000
[    0.000000] zynq_clock_init: clkc starts at df802100
[    0.000000] Zynq clock init
[    0.000014] sched_clock: 64 bits at 333MHz, resolution 3ns, wraps every 3298534883328ns
[    0.000296] ps7-ttc #0 at df804000, irq=43
[    0.000598] Console: colour dummy device 80x30
[    0.000627] Calibrating delay loop... 1332.01 BogoMIPS (lpj=6660096)
[    0.090241] pid_max: default: 32768 minimum: 301
[    0.090450] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
[    0.090469] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
[    0.092671] CPU: Testing write buffer coherency: ok
[    0.092990] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
[    0.093047] Setting up static identity map for 0x4d3ec0 - 0x4d3f18
[    0.093266] L310 cache controller enabled
[    0.093285] l2x0: 8 ways, CACHE_ID 0x410000c8, AUX_CTRL 0x72760000, Cache size: 512 kB
[    0.170989] CPU1: Booted secondary processor
[    0.260219] CPU1: thread -1, cpu 1, socket 0, mpidr 80000001
[    0.260348] Brought up 2 CPUs
[    0.260367] SMP: Total of 2 processors activated.
[    0.260376] CPU: All CPU(s) started in SVC mode.
[    0.261038] devtmpfs: initialized
[    0.263492] VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4
[    0.264693] regulator-dummy: no parameters
[    0.272152] NET: Registered protocol family 16
[    0.274435] DMA: preallocated 256 KiB pool for atomic coherent allocations
[    0.276707] cpuidle: using governor ladder
[    0.276721] cpuidle: using governor menu
[    0.284136] syscon f8000000.ps7-slcr: regmap [mem 0xf8000000-0xf8000fff] registered
[    0.285666] hw-breakpoint: found 5 (+1 reserved) breakpoint and 1 watchpoint registers.
[    0.285680] hw-breakpoint: maximum watchpoint size is 4 bytes.
[    0.285791] zynq-ocm f800c000.ps7-ocmc: ZYNQ OCM pool: 256 KiB @ 0xdf880000
[    0.308199] bio: create slab at 0
[    0.309599] vgaarb: loaded
[    0.310425] SCSI subsystem initialized
[    0.311362] usbcore: registered new interface driver usbfs
[    0.311535] usbcore: registered new interface driver hub
[    0.311763] usbcore: registered new device driver usb
[    0.312281] media: Linux media interface: v0.10
[    0.312453] Linux video capture interface: v2.00
[    0.312693] pps_core: LinuxPPS API ver. 1 registered
[    0.312705] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti
[    0.312835] PTP clock support registered
[    0.313185] EDAC MC: Ver: 3.0.0
[    0.314249] Advanced Linux Sound Architecture Driver Initialized.
[    0.317005] DMA-API: preallocated 4096 debug entries
[    0.317019] DMA-API: debugging enabled by kernel config
[    0.317093] Switched to clocksource arm_global_timer
[    0.338499] NET: Registered protocol family 2
[    0.339150] TCP established hash table entries: 4096 (order: 2, 16384 bytes)
[    0.339207] TCP bind hash table entries: 4096 (order: 3, 32768 bytes)
[    0.339293] TCP: Hash tables configured (established 4096 bind 4096)
[    0.339337] TCP: reno registered
[    0.339354] UDP hash table entries: 256 (order: 1, 8192 bytes)
[    0.339386] UDP-Lite hash table entries: 256 (order: 1, 8192 bytes)
[    0.339620] NET: Registered protocol family 1
[    0.339961] RPC: Registered named UNIX socket transport module.
[    0.339973] RPC: Registered udp transport module.
[    0.339981] RPC: Registered tcp transport module.
[    0.339989] RPC: Registered tcp NFSv4.1 backchannel transport module.
[    0.340002] PCI: CLS 0 bytes, default 64
[    0.340430] hw perfevents: enabled with ARMv7 Cortex-A9 PMU driver, 7 counters available
[    0.342426] futex hash table entries: 512 (order: 3, 32768 bytes)
[    0.344491] jffs2: version 2.2. (NAND) © 2001-2006 Red Hat, Inc.
[    0.344683] msgmni has been set to 967
[    0.345452] io scheduler noop registered
[    0.345465] io scheduler deadline registered
[    0.345506] io scheduler cfq registered (default)
[    0.355844] dma-pl330 f8003000.ps7-dma: Loaded driver for PL330 DMAC-2364208
[    0.355865] dma-pl330 f8003000.ps7-dma: DBUFF-128x8bytes Num_Chans-8 Num_Peri-4 Num_Events-16
[    0.482016] e0001000.serial: ttyPS0 at MMIO 0xe0001000 (irq = 82, base_baud = 3124999) is a xuartps
[    1.049514] console [ttyPS0] enabled
[    1.053788] xdevcfg f8007000.ps7-dev-cfg: ioremap 0xf8007000 to df866000
[    1.061413] [drm] Initialized drm 1.1.0 20060810
[    1.078454] brd: module loaded
[    1.087839] loop: module loaded
[    1.097286] e1000e: Intel(R) PRO/1000 Network Driver - 2.3.2-k
[    1.103035] e1000e: Copyright(c) 1999 - 2013 Intel Corporation.
[    1.110847] libphy: XEMACPS mii bus: probed
[    1.115214] ------------- phy_id = 0x3625e62
[    1.120137] xemacps e000b000.ps7-ethernet: pdev->id -1, baseaddr 0xe000b000, irq 54
[    1.128788] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[    1.135402] ehci-pci: EHCI PCI platform driver
[    1.142893] zynq-dr e0002000.ps7-usb: Unable to init USB phy, missing?
[    1.149790] usbcore: registered new interface driver usb-storage
[    1.156625] mousedev: PS/2 mouse device common for all mice
[    1.162751] i2c /dev entries driver
[    1.169670] zynq-edac f8006000.ps7-ddrc: ecc not enabled
[    1.175148] cpufreq_cpu0: failed to get cpu0 regulator: -19
[    1.181075] Xilinx Zynq CpuIdle Driver started
[    1.185916] sdhci: Secure Digital Host Controller Interface driver
[    1.192120] sdhci: Copyright(c) Pierre Ossman
[    1.196388] sdhci-pltfm: SDHCI platform and OF driver helper
[    1.203208] mmc0: no vqmmc regulator found
[    1.207255] mmc0: no vmmc regulator found
[    1.247110] mmc0: SDHCI controller on e0100000.ps7-sdio [e0100000.ps7-sdio] using ADMA
[    1.255822] usbcore: registered new interface driver usbhid
[    1.261336] usbhid: USB HID core driver
[    1.266036] nand: device found, Manufacturer ID: 0x2c, Chip ID: 0xda
[    1.272328] nand: Micron MT29F2G08ABAEAWP
[    1.276300] nand: 256MiB, SLC, page size: 2048, OOB size: 64
[    1.282250] Bad block table found at page 131008, version 0x01
[    1.288498] Bad block table found at page 130944, version 0x01
[    1.294553] 3 ofpart partitions found on MTD device pl353-nand
[    1.300329] Creating 3 MTD partitions on "pl353-nand":
[    1.305425] 0x000000000000-0x000002000000 : "BOOT.bin-env-dts-kernel"
[    1.313472] 0x000002000000-0x00000b000000 : "angstram-rootfs"
[    1.320827] 0x00000b000000-0x000010000000 : "upgrade-rootfs"
[    1.329528] nf_conntrack version 0.5.0 (7739 buckets, 30956 max)
[    1.336066] ip_tables: (C) 2000-2006 Netfilter Core Team
[    1.341389] TCP: cubic registered
[    1.344620] NET: Registered protocol family 17
[    1.349322] Registering SWP/SWPB emulation handler
[    1.355200] regulator-dummy: disabling
[    1.359575] UBI: attaching mtd1 to ubi0
[    1.886933] UBI: scanning is finished
[    1.898570] UBI: attached mtd1 (name "angstram-rootfs", size 144 MiB) to ubi0
[    1.905625] UBI: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
[    1.912422] UBI: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
[    1.919098] UBI: VID header offset: 2048 (aligned 2048), data offset: 4096
[    1.925936] UBI: good PEBs: 1152, bad PEBs: 0, corrupted PEBs: 0
[    1.931945] UBI: user volume: 1, internal volumes: 1, max. volumes count: 128
[    1.939056] UBI: max/mean erase counter: 3/1, WL threshold: 4096, image sequence number: 408383306
[    1.948000] UBI: available PEBs: 0, total reserved PEBs: 1152, PEBs reserved for bad PEB handling: 40
[    1.957217] UBI: background thread "ubi_bgt0d" started, PID 1085
[    1.957222] drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
[    1.961249] ALSA device list:
[    1.961252]   No soundcards found.
[    1.977569] UBIFS: background thread "ubifs_bgt0_0" started, PID 1087
[    2.006506] UBIFS: recovery needed
[    2.084139] UBIFS: recovery completed
[    2.087821] UBIFS: mounted UBI device 0, volume 0, name "rootfs"
[    2.093744] UBIFS: LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
[    2.102876] UBIFS: FS size: 128626688 bytes (122 MiB, 1013 LEBs), journal size 9023488 bytes (8 MiB, 72 LEBs)
[    2.112769] UBIFS: reserved for root: 0 bytes (0 KiB)
[    2.117803] UBIFS: media format: w4/r0 (latest is w4/r0), UUID 3AB50DA4-F7D1-4711-9EEE-D3D8DA845970, small LPT model
[    2.128858] VFS: Mounted root (ubifs filesystem) on device 0:11.
[    2.135567] devtmpfs: mounted
[    2.138704] Freeing unused kernel memory: 208K (c06e9000 - c071d000)
[    2.973161] random: dd urandom read with 0 bits of entropy available
[    3.397105]
[    3.397105] bcm54xx_config_init
[    4.467139]
[    4.467139] bcm54xx_config_init
[    8.467953] xemacps e000b000.ps7-ethernet: Set clk to 124999998 Hz
[    8.474053] xemacps e000b000.ps7-ethernet: link up (1000/FULL)
[   26.889662] In axi fpga driver!
[   26.892736] request_mem_region OK!
[   26.896127] AXI fpga dev virtual address is 0xdf9fc000
[   26.901262] *base_vir_addr = 0xc51e
[   26.916312] In fpga mem driver!
[   26.919441] request_mem_region OK!
[   26.922949] fpga mem virtual address is 0xe2000000
[   27.716505]
[   27.716505] bcm54xx_config_init
[   28.826390]
[   28.826390] bcm54xx_config_init
[   32.826817] xemacps e000b000.ps7-ethernet: Set clk to 124999998 Hz
[   32.832926] xemacps e000b000.ps7-ethernet: link up (1000/FULL)
main.c:13992: log_level = 4
main.c:14019: This is XILINX board. Totalram:       507424768
main.c:14031: Detect 512MB control board of XILINX
driver-bitmain.c:1776: mmap axi_fpga_addr = 0xb6f05000
driver-bitmain.c:1781: axi_fpga_addr data = 0xc51e
driver-bitmain.c:1797: mmap fpga_mem_addr = 0xb5cfe000
driver-bitmain.c:994: forceFreq=-1 forceFlag=0
driver-bitmain.c:1696: min work minertest[0]:912


main.c:8570: DETECT HW version=0000c51e
main.c:14064: miner ID : 80608d881c20881c
main.c:14089: Miner Type = S9
main.c:14101: AsicType = 1387
main.c:14104: real AsicNum = 63
main.c:14197: use critical mode to search freq...
driver-bitmain.c:1876: get PLUG ON=0x00000040
driver-bitmain.c:1946: Find hashboard on Chain[6]
main.c:2282: Check chain[6] PIC fw version=0x03
main.c:8940: read pic freq and badcore num...
main.c:8961: chain[6]: [63:22] [63:5] [63:24] [63:25] [63:16] [63:34] [63:255] [63:255]
main.c:9003: has freq in PIC, will disable freq setting.
main.c:9099: chain[6] has freq in PIC and will jump over...
main.c:9103: Chain[6] has core num in PIC
main.c:2282: Check chain[6] PIC fw version=0x03
main.c:9183: get PIC voltage=57 on chain[6], value=910
main.c:9349: chain[6] temp offset record: 62,0,0,0,0,0,35,28
main.c:9366: chain[6] temp chip I2C addr=0x98
main.c:9372: chain[6] has no middle temp, use special fix mode.
main.c:13956: total_exist_chain_num = 1
board_frq_tuning.c:628: single_board_frq_tuning enter
board_frq_tuning.c:629: min_rate, des_rate, fix_volt:13800, 14000, 880
board_frq_tuning.c:254: force_freq not set, don't need tuning
main.c:14645: restart Miner chance num=2
main.c:14685: waiting for receive_func to exit!
main.c:14699: waiting for pic heart to exit!
main.c:13927: bmminer not found= 1948 root       0:00 grep bmminer

main.c:14758: bmminer not found, restart bmminer ...
driver-btm-c5.c:12285:bitmain_c5_init: This is user mode for mining
driver-btm-c5.c:12334:bitmain_c5_init: Detect 512MB control board of XILINX
driver-btm-c5.c:12355:bitmain_c5_init: Miner Type = S9
driver-btm-c5.c:12366:bitmain_c5_init: Miner compile time: Tue Jul 30 20:56:49 CST 2019 type: Antminer S9j
driver-btm-c5.c:12456:bitmain_c5_init: miner ID : 80608d881c20881c
driver-btm-c5.c:12613:bitmain_c5_init: Checking fans...
driver-btm-c5.c:2990:check_fan_beforeInit: get fan[4] speed=5880
driver-btm-c5.c:2990:check_fan_beforeInit: get fan[4] speed=5880
driver-btm-c5.c:2990:check_fan_beforeInit: get fan[5] speed=5640
driver-btm-c5.c:2990:check_fan_beforeInit: get fan[4] speed=5880
driver-btm-c5.c:2990:check_fan_beforeInit: get fan[5] speed=5640
driver-btm-c5.c:2990:check_fan_beforeInit: get fan[4] speed=5880
driver-btm-c5.c:2990:check_fan_beforeInit: get fan[5] speed=5640
driver-btm-c5.c:13148:bitmain_c5_init: chain[6]: [63:22] [63:5] [63:24] [63:25] [63:16] [63:34] [63:255] [63:255]
driver-btm-c5.c:13162:bitmain_c5_init: last_freq: 0x00 0x7d 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x03 0x4e 0x03 0x4e 0x03 0x4e 0x03 0x4e 0x03 0x4e 0x03 0x4e 0x01 0x4e 0x01 0x4e 0x0f 0x4e 0x0e 0x4e 0x02 0x4e 0x01 0x4e 0x05 0x4e 0x0c 0x4e 0x23 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e 0x00 0x4e
driver-btm-c5.c:13189:bitmain_c5_init: Detect: use voltage limit rules on single board!
driver-btm-c5.c:13195:bitmain_c5_init: Detect: S9_63 use voltage level=1 : 1
driver-btm-c5.c:13211:bitmain_c5_init: Chain[J7] has backup chain_voltage=920
driver-btm-c5.c:13233:bitmain_c5_init: scan based on domain
driver-btm-c5.c:1883:jump_to_app_CheckAndRestorePIC: Check chain[6] PIC fw version=0x03
driver-btm-c5.c:12237:init_exist_chain_table: total_exist_chain_num = 1
driver-btm-c5.c:13361:bitmain_c5_init: Chain[J7] orignal chain_voltage_pic=57 value=910
driver-btm-c5.c:13362:bitmain_c5_init: Chain[J7] original chain_voltage_value=920 adjusted chain_voltage_value:920, value=910
driver-btm-c5.c:13379:bitmain_c5_init: Chain[J7] will use backup chain_voltage_pic=920 [40]
driver-btm-c5.c:13389:bitmain_c5_init: Chain[J7] get working chain_voltage_pic=40
driver-btm-c5.c:13494:bitmain_c5_init: Chain[J7] has 15 asic
driver-btm-c5.c:13522:bitmain_c5_init: retry Chain[J7] has 15 asic
driver-btm-c5.c:13522:bitmain_c5_init: retry Chain[J7] has 15 asic
driver-btm-c5.c:13522:bitmain_c5_init: retry Chain[J7] has 15 asic
driver-btm-c5.c:13522:bitmain_c5_init: retry Chain[J7] has 15 asic
driver-btm-c5.c:13522:bitmain_c5_init: retry Chain[J7] has 15 asic
driver-btm-c5.c:13522:bitmain_c5_init: retry Chain[J7] has 15 asic
driver-btm-c5.c:4543:set_frequency: Chain[J7] has core num in PIC
driver-btm-c5.c:3768:get_total_rate_from_eeprom: totalrate = 4847
driver-btm-c5.c:4583:set_frequency: miner total rate=4847GH/s ideal_total_hash_rate = 4500GH/s
driver-btm-c5.c:4608:set_frequency: read PIC voltage=910 on chain[6]
driver-btm-c5.c:4610:set_frequency: Chain:6 chipnum=15
driver-btm-c5.c:4630:set_frequency: Chain[J7] voltage added=0.0V
driver-btm-c5.c:4780:set_frequency: Chain:6 temp offset=0
driver-btm-c5.c:4785:set_frequency: Chain:6 base freq=100
Asic[ 0]:675 Asic[ 1]:675 Asic[ 2]:675 Asic[ 3]:675 Asic[ 4]:675 Asic[ 5]:675 Asic[ 6]:675 Asic[ 7]:675
Asic[ 8]:675 Asic[ 9]:675 Asic[10]:675 Asic[11]:675 Asic[12]:675 Asic[13]:675 Asic[14]:675
driver-btm-c5.c:4821:set_frequency: Chain:6 max freq=675
driver-btm-c5.c:4822:set_frequency: Chain:6 min freq=675


driver-btm-c5.c:4831:set_frequency: Miner fix freq ...
driver-btm-c5.c:4866:set_frequency: read PIC voltage=910 on chain[6]
driver-btm-c5.c:4867:set_frequency: Chain:6 chipnum=15
driver-btm-c5.c:4886:set_frequency: Chain[J7] voltage added=0.0V
driver-btm-c5.c:5070:set_frequency: Chain:6 temp offset=0
driver-btm-c5.c:5075:set_frequency: Chain:6 base freq=100
Asic[ 0]:675 Asic[ 1]:675 Asic[ 2]:675 Asic[ 3]:675 Asic[ 4]:675 Asic[ 5]:675 Asic[ 6]:675 Asic[ 7]:675
Asic[ 8]:675 Asic[ 9]:675 Asic[10]:675 Asic[11]:675 Asic[12]:675 Asic[13]:675 Asic[14]:675
driver-btm-c5.c:5122:set_frequency: Chain:6 max freq=675
driver-btm-c5.c:5123:set_frequency: Chain:6 min freq=675

driver-btm-c5.c:5131:set_frequency: max freq = 675
driver-btm-c5.c:4149:ProcessFixFreq: totalRate = 4500, fixed_totalRate = 4500
driver-btm-c5.c:9614:init_uart_baud: set baud=1
driver-btm-c5.c:13824:bitmain_c5_init: open core three times
driver-btm-c5.c:12129:set_working_voltage: setting to working voltage...
driver-btm-c5.c:14027:bitmain_c5_init: start thread for read temp
setStartTimePoint total_tv_start_sys=117 total_tv_end_sys=118
driver-btm-c5.c:10330:check_system_work: restartNum = 2 , auto-reinit enabled...
util.c:3207:initiate_stratum: mining.subscribe:{"id": 0, "method": "mining.subscribe", "params": ["bmminer/2.0.0/Antminer S9j/4500"]}
driver-btm-c5.c:8738:read_temp_func: bring_up_pcb_temp = -100
do read_temp_func once...

get RT hashrate from Chain[6]: (asic index start from 1-63)
Asic[01]=0.00000 Asic[02]=0.00000 Asic[03]=0.00000 Asic[04]=0.00000 Asic[05]=0.00000 Asic[06]=0.00000 Asic[07]=0.00000 Asic[08]=0.00000
Asic[09]=0.00000 Asic[10]=0.00000 Asic[11]=0.00000 Asic[12]=0.00000 Asic[13]=50.3310 Asic[14]=0.00000 Check Chain[J7] ASIC RT error: (asic index start from 1-63)
Done check_asic_reg
Done read temp on Chain[6]
Max pcb temp : -100
set FAN speed according to: temp_highest=-100 temp_top1[PWM_T]=-100 temp_top1[TEMP_POS_LOCAL]=-100 temp_change=0 fix_fan_steps=0
FAN PWM: 0
read_temp_func Done!
CRC error counter=510


And this is one of the good hashboards (drawing 445W @240V and producing 4713GH/s:

Code:
[    0.000000] Booting Linux on physical CPU 0x0
[    0.000000] Linux version 3.14.0-xilinx-ga36f3af-dirty (lzq@ubuntu) (gcc version 4.8.3 20140320 (prerelease) (Sourcery CodeBench Lite 2014.05-23) ) #90 SMP PREEMPT Thu Jun 20 15:01:47 CST 2019
[    0.000000] CPU: ARMv7 Processor [413fc090] revision 0 (ARMv7), cr=18c5387d
[    0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
[    0.000000] Machine model: Xilinx Zynq
[    0.000000] cma: CMA: reserved 128 MiB at 16800000
[    0.000000] Memory policy: Data cache writealloc
[    0.000000] On node 0 totalpages: 126976
[    0.000000] free_area_init_node: node 0, pgdat c075a640, node_mem_map debd8000
[    0.000000]   Normal zone: 992 pages used for memmap
[    0.000000]   Normal zone: 0 pages reserved
[    0.000000]   Normal zone: 126976 pages, LIFO batch:31
[    0.000000] PERCPU: Embedded 8 pages/cpu @debc1000 s9344 r8192 d15232 u32768
[    0.000000] pcpu-alloc: s9344 r8192 d15232 u32768 alloc=8*4096
[    0.000000] pcpu-alloc: [0] 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: 364252K/507904K available (5094K kernel code, 292K rwdata, 1948K rodata, 209K init, 259K bss, 143652K reserved, 0K highmem)
[    0.000000] Virtual kernel memory layout:
[    0.000000]     vector  : 0xffff0000 - 0xffff1000   (   4 kB)
[    0.000000]     fixmap  : 0xfff00000 - 0xfffe0000   ( 896 kB)
[    0.000000]     vmalloc : 0xdf800000 - 0xff000000   ( 504 MB)
[    0.000000]     lowmem  : 0xc0000000 - 0xdf000000   ( 496 MB)
[    0.000000]     pkmap   : 0xbfe00000 - 0xc0000000   (   2 MB)
[    0.000000]     modules : 0xbf000000 - 0xbfe00000   (  14 MB)
[    0.000000]       .text : 0xc0008000 - 0xc06e8cf4   (7044 kB)
[    0.000000]       .init : 0xc06e9000 - 0xc071d480   ( 210 kB)
[    0.000000]       .data : 0xc071e000 - 0xc0767058   ( 293 kB)
[    0.000000]        .bss : 0xc0767064 - 0xc07a7d64   ( 260 kB)
[    0.000000] Preemptible hierarchical RCU implementation.
[    0.000000] Dump stacks of tasks blocking RCU-preempt GP.
[    0.000000] RCU restricting CPUs from NR_CPUS=4 to nr_cpu_ids=2.
[    0.000000] RCU: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=2
[    0.000000] NR_IRQS:16 nr_irqs:16 16
[    0.000000] ps7-slcr mapped to df802000
[    0.000000] zynq_clock_init: clkc starts at df802100
[    0.000000] Zynq clock init
[    0.000014] sched_clock: 64 bits at 333MHz, resolution 3ns, wraps every 3298534883328ns
[    0.000292] ps7-ttc #0 at df804000, irq=43
[    0.000597] Console: colour dummy device 80x30
[    0.000627] Calibrating delay loop... 1325.46 BogoMIPS (lpj=6627328)
[    0.040195] pid_max: default: 32768 minimum: 301
[    0.040409] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
[    0.040428] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
[    0.042635] CPU: Testing write buffer coherency: ok
[    0.042961] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
[    0.043019] Setting up static identity map for 0x4d3ec0 - 0x4d3f18
[    0.043237] L310 cache controller enabled
[    0.043256] l2x0: 8 ways, CACHE_ID 0x410000c8, AUX_CTRL 0x72760000, Cache size: 512 kB
[    0.120988] CPU1: Booted secondary processor
[    0.210218] CPU1: thread -1, cpu 1, socket 0, mpidr 80000001
[    0.210347] Brought up 2 CPUs
[    0.210366] SMP: Total of 2 processors activated.
[    0.210374] CPU: All CPU(s) started in SVC mode.
[    0.211033] devtmpfs: initialized
[    0.213483] VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4
[    0.214685] regulator-dummy: no parameters
[    0.221757] NET: Registered protocol family 16
[    0.223981] DMA: preallocated 256 KiB pool for atomic coherent allocations
[    0.226254] cpuidle: using governor ladder
[    0.226267] cpuidle: using governor menu
[    0.233662] syscon f8000000.ps7-slcr: regmap [mem 0xf8000000-0xf8000fff] registered
[    0.235193] hw-breakpoint: found 5 (+1 reserved) breakpoint and 1 watchpoint registers.
[    0.235207] hw-breakpoint: maximum watchpoint size is 4 bytes.
[    0.235318] zynq-ocm f800c000.ps7-ocmc: ZYNQ OCM pool: 256 KiB @ 0xdf880000
[    0.257876] bio: create slab at 0
[    0.259265] vgaarb: loaded
[    0.259971] SCSI subsystem initialized
[    0.261006] usbcore: registered new interface driver usbfs
[    0.261183] usbcore: registered new interface driver hub
[    0.261411] usbcore: registered new device driver usb
[    0.261940] media: Linux media interface: v0.10
[    0.262097] Linux video capture interface: v2.00
[    0.262337] pps_core: LinuxPPS API ver. 1 registered
[    0.262349] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti
[    0.262473] PTP clock support registered
[    0.262829] EDAC MC: Ver: 3.0.0
[    0.263890] Advanced Linux Sound Architecture Driver Initialized.
[    0.266649] DMA-API: preallocated 4096 debug entries
[    0.266663] DMA-API: debugging enabled by kernel config
[    0.266739] Switched to clocksource arm_global_timer
[    0.287442] NET: Registered protocol family 2
[    0.288090] TCP established hash table entries: 4096 (order: 2, 16384 bytes)
[    0.288146] TCP bind hash table entries: 4096 (order: 3, 32768 bytes)
[    0.288231] TCP: Hash tables configured (established 4096 bind 4096)
[    0.288276] TCP: reno registered
[    0.288293] UDP hash table entries: 256 (order: 1, 8192 bytes)
[    0.288323] UDP-Lite hash table entries: 256 (order: 1, 8192 bytes)
[    0.288552] NET: Registered protocol family 1
[    0.288898] RPC: Registered named UNIX socket transport module.
[    0.288910] RPC: Registered udp transport module.
[    0.288918] RPC: Registered tcp transport module.
[    0.288926] RPC: Registered tcp NFSv4.1 backchannel transport module.
[    0.288938] PCI: CLS 0 bytes, default 64
[    0.289370] hw perfevents: enabled with ARMv7 Cortex-A9 PMU driver, 7 counters available
[    0.291357] futex hash table entries: 512 (order: 3, 32768 bytes)
[    0.293428] jffs2: version 2.2. (NAND) © 2001-2006 Red Hat, Inc.
[    0.293624] msgmni has been set to 967
[    0.294394] io scheduler noop registered
[    0.294408] io scheduler deadline registered
[    0.294451] io scheduler cfq registered (default)
[    0.305485] dma-pl330 f8003000.ps7-dma: Loaded driver for PL330 DMAC-2364208
[    0.305505] dma-pl330 f8003000.ps7-dma: DBUFF-128x8bytes Num_Chans-8 Num_Peri-4 Num_Events-16
[    0.428221] e0001000.serial: ttyPS0 at MMIO 0xe0001000 (irq = 82, base_baud = 3124999) is a xuartps
[    0.995926] console [ttyPS0] enabled
[    1.000206] xdevcfg f8007000.ps7-dev-cfg: ioremap 0xf8007000 to df866000
[    1.007827] [drm] Initialized drm 1.1.0 20060810
[    1.024915] brd: module loaded
[    1.034306] loop: module loaded
[    1.043753] e1000e: Intel(R) PRO/1000 Network Driver - 2.3.2-k
[    1.049758] e1000e: Copyright(c) 1999 - 2013 Intel Corporation.
[    1.057542] libphy: XEMACPS mii bus: probed
[    1.061915] ------------- phy_id = 0x3625e62
[    1.066616] xemacps e000b000.ps7-ethernet: pdev->id -1, baseaddr 0xe000b000, irq 54
[    1.075365] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[    1.082012] ehci-pci: EHCI PCI platform driver
[    1.089389] zynq-dr e0002000.ps7-usb: Unable to init USB phy, missing?
[    1.096203] usbcore: registered new interface driver usb-storage
[    1.103135] mousedev: PS/2 mouse device common for all mice
[    1.109270] i2c /dev entries driver
[    1.116139] zynq-edac f8006000.ps7-ddrc: ecc not enabled
[    1.121647] cpufreq_cpu0: failed to get cpu0 regulator: -19
[    1.127575] Xilinx Zynq CpuIdle Driver started
[    1.132415] sdhci: Secure Digital Host Controller Interface driver
[    1.138529] sdhci: Copyright(c) Pierre Ossman
[    1.142845] sdhci-pltfm: SDHCI platform and OF driver helper
[    1.149735] mmc0: no vqmmc regulator found
[    1.153751] mmc0: no vmmc regulator found
[    1.196761] mmc0: SDHCI controller on e0100000.ps7-sdio [e0100000.ps7-sdio] using ADMA
[    1.205445] usbcore: registered new interface driver usbhid
[    1.210951] usbhid: USB HID core driver
[    1.215651] nand: device found, Manufacturer ID: 0x2c, Chip ID: 0xda
[    1.221947] nand: Micron MT29F2G08ABAEAWP
[    1.225916] nand: 256MiB, SLC, page size: 2048, OOB size: 64
[    1.231857] Bad block table found at page 131008, version 0x01
[    1.238083] Bad block table found at page 130944, version 0x01
[    1.244134] 3 ofpart partitions found on MTD device pl353-nand
[    1.249920] Creating 3 MTD partitions on "pl353-nand":
[    1.255012] 0x000000000000-0x000002000000 : "BOOT.bin-env-dts-kernel"
[    1.263056] 0x000002000000-0x00000b000000 : "angstram-rootfs"
[    1.270364] 0x00000b000000-0x000010000000 : "upgrade-rootfs"
[    1.279067] nf_conntrack version 0.5.0 (7739 buckets, 30956 max)
[    1.285593] ip_tables: (C) 2000-2006 Netfilter Core Team
[    1.290921] TCP: cubic registered
[    1.294150] NET: Registered protocol family 17
[    1.298884] Registering SWP/SWPB emulation handler
[    1.304786] regulator-dummy: disabling
[    1.309169] UBI: attaching mtd1 to ubi0
[    1.836326] UBI: scanning is finished
[    1.847951] UBI: attached mtd1 (name "angstram-rootfs", size 144 MiB) to ubi0
[    1.855008] UBI: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
[    1.861803] UBI: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
[    1.868480] UBI: VID header offset: 2048 (aligned 2048), data offset: 4096
[    1.875317] UBI: good PEBs: 1152, bad PEBs: 0, corrupted PEBs: 0
[    1.881328] UBI: user volume: 1, internal volumes: 1, max. volumes count: 128
[    1.888438] UBI: max/mean erase counter: 3/1, WL threshold: 4096, image sequence number: 408383306
[    1.897381] UBI: available PEBs: 0, total reserved PEBs: 1152, PEBs reserved for bad PEB handling: 40
[    1.906579] UBI: background thread "ubi_bgt0d" started, PID 1085
[    1.906585] drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
[    1.910621] ALSA device list:
[    1.910624]   No soundcards found.
[    1.926954] UBIFS: background thread "ubifs_bgt0_0" started, PID 1087
[    1.956157] UBIFS: recovery needed
[    2.030972] UBIFS: recovery completed
[    2.034635] UBIFS: mounted UBI device 0, volume 0, name "rootfs"
[    2.040583] UBIFS: LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
[    2.049721] UBIFS: FS size: 128626688 bytes (122 MiB, 1013 LEBs), journal size 9023488 bytes (8 MiB, 72 LEBs)
[    2.059587] UBIFS: reserved for root: 0 bytes (0 KiB)
[    2.064608] UBIFS: media format: w4/r0 (latest is w4/r0), UUID 3AB50DA4-F7D1-4711-9EEE-D3D8DA845970, small LPT model
[    2.075676] VFS: Mounted root (ubifs filesystem) on device 0:11.
[    2.082400] devtmpfs: mounted
[    2.085513] Freeing unused kernel memory: 208K (c06e9000 - c071d000)
[    2.924212] random: dd urandom read with 0 bits of entropy available
[    3.346756]
[    3.346756] bcm54xx_config_init
[    4.406796]
[    4.406796] bcm54xx_config_init
[    8.407614] xemacps e000b000.ps7-ethernet: Set clk to 124999998 Hz
[    8.413715] xemacps e000b000.ps7-ethernet: link up (1000/FULL)
[   23.186524] In axi fpga driver!
[   23.189592] request_mem_region OK!
[   23.192984] AXI fpga dev virtual address is 0xdf9fc000
[   23.198116] *base_vir_addr = 0xc51e
[   23.213466] In fpga mem driver!
[   23.216596] request_mem_region OK!
[   23.220102] fpga mem virtual address is 0xe2000000
[   24.016173]
[   24.016173] bcm54xx_config_init
[   25.126071]
[   25.126071] bcm54xx_config_init
[   29.126465] xemacps e000b000.ps7-ethernet: Set clk to 124999998 Hz
[   29.132567] xemacps e000b000.ps7-ethernet: link up (1000/FULL)
main.c:13992: log_level = 4
main.c:14019: This is XILINX board. Totalram:       507424768
main.c:14031: Detect 512MB control board of XILINX
driver-bitmain.c:1776: mmap axi_fpga_addr = 0xb6fc7000
driver-bitmain.c:1781: axi_fpga_addr data = 0xc51e
driver-bitmain.c:1797: mmap fpga_mem_addr = 0xb5dc0000
driver-bitmain.c:994: forceFreq=-1 forceFlag=0
driver-bitmain.c:1696: min work minertest[0]:912


main.c:8570: DETECT HW version=0000c51e
main.c:14064: miner ID : 80608d881c20881c
main.c:14089: Miner Type = S9
main.c:14101: AsicType = 1387
main.c:14104: real AsicNum = 63
main.c:14197: use critical mode to search freq...
driver-bitmain.c:1876: get PLUG ON=0x00000040
driver-bitmain.c:1946: Find hashboard on Chain[6]
main.c:2282: Check chain[6] PIC fw version=0x03
main.c:8940: read pic freq and badcore num...
main.c:8961: chain[6]: [63:22] [63:5] [63:24] [63:24] [63:69] [63:3] [63:255] [63:255]
main.c:9003: has freq in PIC, will disable freq setting.
main.c:9099: chain[6] has freq in PIC and will jump over...
main.c:9103: Chain[6] has core num in PIC
main.c:9113: Chain[6] ASIC[21] has core num=5
main.c:2282: Check chain[6] PIC fw version=0x03
main.c:9183: get PIC voltage=125 on chain[6], value=870
main.c:9349: chain[6] temp offset record: 62,0,0,0,0,0,35,28
main.c:9366: chain[6] temp chip I2C addr=0x98
main.c:9372: chain[6] has no middle temp, use special fix mode.
main.c:13956: total_exist_chain_num = 1
board_frq_tuning.c:628: single_board_frq_tuning enter
board_frq_tuning.c:629: min_rate, des_rate, fix_volt:13800, 14000, 880
board_frq_tuning.c:254: force_freq not set, don't need tuning
main.c:14645: restart Miner chance num=2
main.c:14685: waiting for receive_func to exit!
main.c:14699: waiting for pic heart to exit!
main.c:13927: bmminer not found= 1947 root       0:00 grep bmminer

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


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

driver-btm-c5.c:5131:set_frequency: max freq = 656
driver-btm-c5.c:4149:ProcessFixFreq: totalRate = 4708, fixed_totalRate = 4500
driver-btm-c5.c:9614:init_uart_baud: set baud=1
driver-btm-c5.c:6605:calibration_sensor_offset: Chain[J7] PIC temp offset: 62,0,0,0,0,0,35,28,0,0,0,0,0,0,0,0,0,0,
driver-btm-c5.c:6639:calibration_sensor_offset: chain[7] temp chip I2C addr=0x98
driver-btm-c5.c:6647:calibration_sensor_offset: chain[7] has no middle temp, use special fix mode.
driver-btm-c5.c:6672:calibration_sensor_offset: Chain[J7] chip[244] use PIC middle temp offset=0 typeID=55
driver-btm-c5.c:6396:do_calibration_sensor_offset: New offset Chain[7] chip[244] local:27 remote:30 offset:27
driver-btm-c5.c:6765:calibration_sensor_offset: Chain[J7] chip[244] get middle temp offset=27 typeID=55
driver-btm-c5.c:12129:set_working_voltage: setting to working voltage...
driver-btm-c5.c:12109:slowly_downgrade_voltage_all_chain: chain[6] set voltage to 900
driver-btm-c5.c:12109:slowly_downgrade_voltage_all_chain: chain[6] set voltage to 890
driver-btm-c5.c:12109:slowly_downgrade_voltage_all_chain: chain[6] set voltage to 880
driver-btm-c5.c:12109:slowly_downgrade_voltage_all_chain: chain[6] set voltage to 870
driver-btm-c5.c:14027:bitmain_c5_init: start thread for read temp
setStartTimePoint total_tv_start_sys=91 total_tv_end_sys=92
driver-btm-c5.c:10330:check_system_work: restartNum = 2 , auto-reinit enabled...
util.c:3207:initiate_stratum: mining.subscribe:{"id": 0, "method": "mining.subscribe", "params": ["bmminer/2.0.0/Antminer S9j/4500"]}
driver-btm-c5.c:8738:read_temp_func: bring_up_pcb_temp = 38
driver-btm-c5.c:12129:set_working_voltage: setting to working voltage...
driver-btm-c5.c:10521:check_system_work: voltage_check_done
driver-btm-c5.c:9897:if_avg_hash_ok: avg hash rate = 4865.336975, ideal hash rate = 4500
driver-btm-c5.c:10415:check_system_work: hash rate is ok now
do read_temp_func once...

get RT hashrate from Chain[6]: (asic index start from 1-63)
Asic[01]=80.6810 Asic[02]=69.2220 Asic[03]=72.3760 Asic[04]=72.8130 Asic[05]=73.9700 Asic[06]=73.9030 Asic[07]=74.6580 Asic[08]=72.2250
Asic[09]=72.3260 Asic[10]=77.0400 Asic[11]=75.7990 Asic[12]=75.0440 Asic[13]=75.1950 Asic[14]=71.8230 Asic[15]=73.7190 Asic[16]=76.6880
Asic[17]=72.6280 Asic[18]=77.9460 Asic[19]=72.3930 Asic[20]=72.9970 Asic[21]=73.8190 Asic[22]=76.1350 Asic[23]=77.6780 Asic[24]=73.6180
Asic[25]=79.9430 Asic[26]=74.6920 Asic[27]=77.3760 Asic[28]=72.5110 Asic[29]=69.6080 Asic[30]=74.2220 Asic[31]=79.2720 Asic[32]=77.0400
Asic[33]=75.3460 Asic[34]=74.7760 Asic[35]=72.0410 Asic[36]=77.1410 Asic[37]=74.3560 Asic[38]=73.2490 Asic[39]=73.0310 Asic[40]=78.2150
Asic[41]=73.2660 Asic[42]=76.5710 Asic[43]=75.3460 Asic[44]=71.6720 Asic[45]=74.9600 Asic[46]=75.5140 Asic[47]=74.0540 Asic[48]=76.8390
Asic[49]=71.3700 Asic[50]=72.4940 Asic[51]=75.4630 Asic[52]=77.6610 Asic[53]=74.8260 Asic[54]=76.4530 Asic[55]=78.6680 Asic[56]=75.1450
Asic[57]=75.1450 Asic[58]=68.7360 Asic[59]=77.8790 Asic[60]=75.0780 Asic[61]=74.0710 Asic[62]=76.0670 Asic[63]=71.3530
Check Chain[J7] ASIC RT error: (asic index start from 1-63)
Done check_asic_reg
Chain[6] Chip[244] pcb temperature=56
Chain[6] Chip[62] junction temperature=68
Special fix Chain[6] Chip[62] middle Temp = 71
Done read temp on Chain[6]
Max pcb temp : 56
set FAN speed according to: temp_highest=56 temp_top1[PWM_T]=56 temp_top1[TEMP_POS_LOCAL]=56 temp_change=-1 fix_fan_steps=0
FAN PWM: 64
read_temp_func Done!
CRC error counter=0
member
Activity: 199
Merit: 37
February 01, 2023, 11:22:42 PM
#14

Don't take screenshots instead copy them and paste them here and put them inside the insert code tag it's a # button while editing your post.
The kernel logs are safe to share here and it should contain some errors so we can see the current situation of your miner while it's running.

But it's your choice if you want to directly suspect the PSU and if you have a budget to buy a new PSU if it's not a PSU you can still use it in the future for testing or to replace your current PSU.
The PSU was working when I took the screen shots after first firing up the miner.
Two hashboards were working, one not working when I took the screenshots.
The PSU failed after running continuously for 3,5 hrs with the 2 good boards hashing and now it only makes 11V DC.

I do not have a sufficiently powerful PSU to run all three hashboarsds, or even 2 of them at the same time.

But I connected a 700W PSU to each of the individual boards and get the same results: one is broken, 2 work.

Writing this has just given me an idea how I can figure out at what point the bad board fails: Just copy and paste the logs from the good boards and the bad board and compare them.

legendary
Activity: 3206
Merit: 2904
Block halving is coming.
February 01, 2023, 07:12:22 PM
#13
I did take screenshots of the kernel log when I first turned the miner on, with all three boards in it, but it's 7 screenshots full of geek-speak and I don't yet know what I'm looking for.
I'll read through it and see if anything sticks out and what I can share.

Don't take screenshots instead copy them and paste them here and put them inside the insert code tag it's a # button while editing your post.
The kernel logs are safe to share here and it should contain some errors so we can see the current situation of your miner while it's running.

But it's your choice if you want to directly suspect the PSU and if you have a budget to buy a new PSU if it's not a PSU you can still use it in the future for testing or to replace your current PSU.
member
Activity: 199
Merit: 37
February 01, 2023, 04:59:52 PM
#12
All of the things that you mentioned can be replaced, especially the caps, while the cables you already replaced/fix as I can see.

Very hot caps or even MPUs that pop out on a thermal scan can indicate a short or a chip that went bad. It's a pretty common technique for troubleshooting something like laptops.

If you have a multimeter and a spec sheet for some of those MPUs that is getting hot, you could check if the voltages are correct on the pinouts.

Thanks, good to know it can be fixed!

For now, I'm researching what PSU I can buy that will solve future problems as well. I expect to get more miners to renovate or down-size for home use.

Looking at this one: https://www.silverstonetek.com/en/product/info/power-supplies/HELA2050Platinum/
It seems to be available and should allow me to test any miner that I have in mind for experimenting with, because I want to stay below 2.4kW so it can be plugged into the wall without fuss.

When I have a bit more time, then I'll take the broken PSU apart again and see if I can fix it.
member
Activity: 199
Merit: 37
February 01, 2023, 04:53:00 PM
#11
I don't know what power you have in your house if it's 110v or 220v. Maybe the power source is not stable which is why it drops after a few hours and you must run this miner at 220v but if you run the miner at low power or 110v the miner will experience some issues like overheating and drops in hash rate.

I hope that you can share the kernel logs here so that we can understand what happened to your miner without them we can't just find the solution by guessing.
Thanks a lot!

I'm on 240V power supply and it typically goes too high (up to 250V) than too low.

The PSU was putting out 11.98V until it suddenly dropped to 11.0V (even without any load on it), so I'm pretty certain something broke in it.

I did take screenshots of the kernel log when I first turned the miner on, with all three boards in it, but it's 7 screenshots full of geek-speak and I don't yet know what I'm looking for.
I'll read through it and see if anything sticks out and what I can share.

Pages:
Jump to: