S9, no matter what frequency I still get XXXXXs

[mettalmag]

It was running for more than a day and then suddenly all XXXXs. I tried lower frequency but I still get XXXXs.
All other miners are running without any issues, max temperature is 88 degrees C.
I haven't tried resetting it and I'm not sure if it will help.
Any ideas ?

[MyRig]

May be to physically power it off, wait for about 30 seconds and power it back on.  Wait for 10 minutes and log into the control panel 1st page and look for status.  If you see some error connection refused, then the PCB may still in the process of initialization.

It was running for more than a day and then suddenly all XXXXs. I tried lower frequency but I still get XXXXs.
All other miners are running without any issues, max temperature is 88 degrees C.
I haven't tried resetting it and I'm not sure if it will help.
Any ideas ?

[mettalmag]

May be to physically power it off, wait for about 30 seconds and power it back on.  Wait for 10 minutes and log into the control panel 1st page and look for status.  If you see some error connection refused, then the PCB may still in the process of initialization.

It was running for more than a day and then suddenly all XXXXs. I tried lower frequency but I still get XXXXs.
All other miners are running without any issues, max temperature is 88 degrees C.
I haven't tried resetting it and I'm not sure if it will help.
Any ideas ?

I have some "Name CRC failed on node at ..." in kernel log and here's the log which says that CPU failed to enable

Code:

SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=2, Nodes=1
Hierarchical RCU implementation.
NR_IRQS:16 nr_irqs:16 16
sched_clock: 32 bits at 100MHz, resolution 10ns, wraps every 42949ms
Console: colour dummy device 80x30
Calibrating delay loop... 1196.85 BogoMIPS (lpj=5984256)
pid_max: default: 32768 minimum: 301
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
ftrace: allocating 17687 entries in 52 pages
CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
Setting up static identity map for 0x804ab220 - 0x804ab278
CPU1: failed to come online
Brought up 1 CPUs
SMP: Total of 1 processors activated (1196.85 BogoMIPS).
CPU: All CPU(s) started in SVC mode.
devtmpfs: initialized
NET: Registered protocol family 16
fpga bridge driver
DMA: preallocated 256 KiB pool for atomic coherent allocations
L310 cache controller enabled

[mettalmag]

Reseting won't help also neither unpluging even for 30 mins

[mettalmag]

May be to physically power it off, wait for about 30 seconds and power it back on.  Wait for 10 minutes and log into the control panel 1st page and look for status.  If you see some error connection refused, then the PCB may still in the process of initialization.

It was running for more than a day and then suddenly all XXXXs. I tried lower frequency but I still get XXXXs.
All other miners are running without any issues, max temperature is 88 degrees C.
I haven't tried resetting it and I'm not sure if it will help.
Any ideas ?

anybody ?
somebody ?

[wmabern]

What is the model of the S9?

If it is an earlier model or a model without the auto tune firmware, you may want to try to flash it with the newest firmware. Or even try to re-flash it with same if it already contains the latest FW. When it comes back up for the first time, it will let you set the frequency that one time. Set it to the frequency it is supposed to run at.

I'm not one to randomly suggest flashing miner firmware. My thoughts are if it ain't broke, don't mess with it. But in your case, it is broke. So what do you have to loose?

I flashed a flakey older S9 that was showing random X's on all boards no mater what frequency it was set to. Amazingly, the newest S9 firmware took care of that problem and the S9 is still hashing away at its stated frequency after over 3 weeks with no X's.

The new firmware will raise your PCB and chip temps by about 10c. But I have had no issues with mine since flashing.

If you try that, let us know what happens.

Good luck!!

EDIT: A note of warning!!! After flashing, it MAY take as long as 30 minutes to come back up. BE PATIENT and wait. The new firmware takes a long time to start up each time it is powered on. Again, BE PATIENT and don't try powering it off.

[mettalmag]

What is the model of the S9?

If it is an earlier model or a model without the auto tune firmware, you may want to try to flash it with the newest firmware. Or even try to re-flash it with same if it already contains the latest FW. When it comes back up for the first time, it will let you set the frequency that one time. Set it to the frequency it is supposed to run at.

I'm not one to randomly suggest flashing miner firmware. My thoughts are if it ain't broke, don't mess with it. But in your case, it is broke. So what do you have to loose?

I flashed a flakey older S9 that was showing random X's on all boards no mater what frequency it was set to. Amazingly, the newest S9 firmware took care of that problem and the S9 is still hashing away at its stated frequency after over 3 weeks with no X's.

The new firmware will raise your PCB and chip temps by about 10c. But I have had no issues with mine since flashing.

If you try that, let us know what happens.

Good luck!!

EDIT: A note of warning!!! After flashing, it MAY take as long as 30 minutes to come back up. BE PATIENT and wait. The new firmware takes a long time to start up each time it is powered on. Again, BE PATIENT and don't try powering it off.

Quite rough situation here, I actually have 3 different batches, first thing I thought was to swap the hashing boards and plug them on another S9 which is working perfectly and see if it works, if yeas than I have to change BB board. Since I have only remote access to my hardware till the Feb 20 I think I'll try with firmware and I'm also afraid of it because I never did it before, July and August batches are with their original firmware no changes has been made since then.