Low hash rate with S9 bath13, Boards apear to be fine

Razon

jr. member

Activity: 39

Merit: 3

I suggest a factory reset first before anything, if your using the latest firmware, I suggest downgrading to a more stable version.

It's showing your running 12.9 THS with a large amount of HW errors vs the other boards.

Your board is running a "tad" low.. The 15 c temp notification is probably a separate issue

r01k

jr. member

Activity: 84

Merit: 3

Quote from: tim-bc on July 09, 2018, 11:17:29 PM

Are you running on 220V? Do all the temps of your boards stay similar to each other?

Yes, I'm on 230V with APW3++. The problem started after I shut down the miner for a few hours. Board 1 is stuck at 15C, hashes low and the red LED on top turns on only sporadically. The other 2 boards temperature is similar or within 1 degree from each other.

https://imgur.com/9cnCyoC

tim-bc

full member

Activity: 538

Merit: 175

Quote from: r01k on July 06, 2018, 08:44:19 PM

I know this is old but did you find a solution or had to end up sending it for repair? I'm having the same problem just today.

Are you running on 220V? Do all the temps of your boards stay similar to each other?

r01k

jr. member

Activity: 84

Merit: 3

Quote from: carlos8calderon on February 15, 2018, 02:01:01 PM

I tried resetting it like 20 times already in all 3 different ways as reloading the firmware as well, but nothing changes when i check on the antminer website everything seems fine all boards are 000000000000000, etc but there is only something weird with one of the board which is the temp is always at 15 while the other ones keep changing from 70-80 as is supposed to.
Every time I resets it all boards have their red light on but after a while the same hash board giving me problems red light goes off but ones again it does not show me any xxxx or ----, it is all 0's

...

I know this is old but did you find a solution or had to end up sending it for repair? I'm having the same problem just today.

castiel0504

full member

Activity: 266

Merit: 109

Ultra Mega Giga Super Cool Flying Oposum!

First thing i saw is that you are using 110v. Not sure is your PSU working same as Bitmans APW3+ . But that PSUs are working with maximum efficiency on 220v. Each hashing board uses 450w, and on 110v you are not getting maximum 1600w.

carlos8calderon

newbie

Activity: 1

Merit: 0

I'm so frustrated because I just got my antminer s9 after wait for it like 3 months, and it's giving me problems already. The first time I tried it i work at its full hashrate but later I turned it off to set it up on its right place, so since then it's been working under 13500GH the maximun it reaches is like 11900-12380GH.

I have a EVGA G2 1600W, I'm living in Canada so we use 110v.

I tried resetting it like 20 times already in all 3 different ways as reloading the firmware as well, but nothing changes when i check on the antminer website everything seems fine all boards are 000000000000000, etc but there is only something weird with one of the board which is the temp is always at 15 while the other ones keep changing from 70-80 as is supposed to.
Every time I resets it all boards have their red light on but after a while the same hash board giving me problems red light goes off but ones again it does not show me any xxxx or ----, it is all 0's

I contact Bitmain but they want me to send the whole thing to them and I do not think is even worth to pay for ship it to them and wait who know how long to get it back

I’m posting the kernel logs if someone is good at this cuz is so confused to me I being honest, all I can find in the is that it show me that chain 7 fails always trying to open some chip cores. and the problem with the temp
but I’m still having the hope that my board is fine specially because it works but not at its full hashrate and it does not show me any x or - as I mention before.

Code:

total send work number:57456
require valid nonce number:57456
repeated_nonce_num:0
err_nonce_num:14777
last_nonce_num:99928
chain[5]: All chip cores are opened OK!
Test Patten on chain[5]: OK!
chain[6]: All chip cores are opened OK!
Test Patten on chain[6]: FAILED!
chain[7]: some chip cores are not opened FAILED!
Test Patten on chain[7]: FAILED!
setStartTimePoint total_tv_start_sys=668 total_tv_end_sys=669
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]=74.7590 Asic[02]=73.1480 Asic[03]=68.4170 Asic[04]=73.5000 Asic[05]=67.8470 Asic[06]=68.9710 Asic[07]=73.4330 Asic[08]=75.0780 
Asic[09]=65.6660 Asic[10]=66.0010 Asic[11]=70.4640 Asic[12]=73.1310 Asic[13]=75.2450 Asic[14]=73.0140 Asic[15]=70.9500 Asic[16]=79.6410 
Asic[17]=71.6890 Asic[18]=69.6920 Asic[19]=73.3490 Asic[20]=68.2660 Asic[21]=73.5170 Asic[22]=73.0140 Asic[23]=72.5270 Asic[24]=74.1720 
Asic[25]=67.6960 Asic[26]=69.9600 Asic[27]=71.1350 Asic[28]=73.5510 Asic[29]=73.2150 Asic[30]=70.2960 Asic[31]=74.6750 Asic[32]=72.6110 
Asic[33]=77.3760 Asic[34]=72.8800 Asic[35]=71.2860 Asic[36]=73.5340 Asic[37]=76.1510 Asic[38]=75.5980 Asic[39]=72.4940 Asic[40]=71.8560 
Asic[41]=71.1850 Asic[42]=76.7380 Asic[43]=72.9800 Asic[44]=77.7280 Asic[45]=68.7860 Asic[46]=72.4270 Asic[47]=68.2160 Asic[48]=76.7380 
Asic[49]=70.2960 Asic[50]=71.0680 Asic[51]=73.0140 Asic[52]=72.5950 Asic[53]=78.6340 Asic[54]=71.8230 Asic[55]=76.4530 Asic[56]=82.1410 
Asic[57]=74.4740 Asic[58]=71.9230 Asic[59]=65.4140 Asic[60]=73.0640 Asic[61]=71.9400 Asic[62]=70.2120 Asic[63]=69.8770 

get RT hashrate from Chain[6]: (asic index start from 1-63)
Asic[01]=73.5510 Asic[02]=64.4910 Asic[03]=72.9300 Asic[04]=74.7250 Asic[05]=68.1650 Asic[06]=67.4940 Asic[07]=66.2860 Asic[08]=71.2020 
Asic[09]=70.1110 Asic[10]=69.9770 Asic[11]=71.6890 Asic[12]=71.1010 Asic[13]=69.9600 Asic[14]=70.3460 Asic[15]=73.4330 Asic[16]=69.9940 
Asic[17]=72.7290 Asic[18]=69.4240 Asic[19]=77.0400 Asic[20]=66.4710 Asic[21]=67.7120 Asic[22]=71.6050 Asic[23]=72.7620 Asic[24]=74.0210 
Asic[25]=71.5380 Asic[26]=68.8700 Asic[27]=73.7690 Asic[28]=71.3700 Asic[29]=70.6150 Asic[30]=71.7720 Asic[31]=73.7350 Asic[32]=69.5080 
Asic[33]=72.2930 Asic[34]=71.9740 Asic[35]=75.6820 Asic[36]=72.2090 Asic[37]=73.3830 Asic[38]=73.9870 Asic[39]=71.5210 Asic[40]=68.1150 
Asic[41]=70.3460 Asic[42]=80.0440 Asic[43]=68.1320 Asic[44]=68.7190 Asic[45]=69.5910 Asic[46]=73.8190 Asic[47]=70.3300 Asic[48]=69.6420 
Asic[49]=65.7160 Asic[50]=70.3800 Asic[51]=64.9440 Asic[52]=73.4330 Asic[53]=72.6450 Asic[54]=73.7350 Asic[55]=75.4130 Asic[56]=80.3120 
Asic[57]=73.8020 Asic[58]=75.5980 Asic[59]=78.3490 Asic[60]=71.9070 Asic[61]=71.0010 Asic[62]=76.3860 Asic[63]=80.7310 

get RT hashrate from Chain[7]: (asic index start from 1-63)
Asic[01]=71.1180 Asic[02]=5.70400 Asic[03]=70.0780 Asic[04]=76.0170 Asic[05]=74.5740 Asic[06]=771.751 Asic[07]=3.95900 Asic[08]=78.5000 
Asic[09]=67.5450 Asic[10]=3.57300 Asic[11]=74.5240 Asic[12]=69.0880 Asic[13]=68.1650 Asic[14]=73.8530 Asic[15]=6.96200 Asic[16]=38.8890 
Asic[17]=36.3560 Asic[18]=32.0780 Asic[19]=35.7850 Asic[20]=64.7600 Asic[21]=3.42200 Asic[22]=34.9630 Asic[23]=34.9970 Asic[24]=78.7010 
Asic[25]=70.9840 Asic[26]=5.01600 Asic[27]=34.2420 Asic[28]=42.8320 Asic[29]=74.0540 Asic[30]=73.2660 Asic[31]=71.3190 Asic[32]=74.0710 
Asic[33]=671.088 Asic[34]=75.8490 Asic[35]=74.0040 Asic[36]=788.529 Asic[37]=68.9200 Asic[38]=36.1040 Asic[39]=5.28400 Asic[40]=76.8560 
Asic[41]=3.00300 Asic[42]=67.5780 Asic[43]=72.0580 Asic[44]=34.9800 Asic[45]=72.1920 Asic[46]=2.39900 Asic[47]=20.5180 Asic[48]=71.8900 
Asic[49]=5.98900 Asic[50]=69.8090 Asic[51]=14.2600 Asic[52]=70.4300 Asic[53]=1.44200 Asic[54]=75.0610 Asic[55]=71.8900 Asic[56]=73.3160 
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)
Asic[06]=771.751000
Asic[33]=671.088000
Asic[36]=788.529000
Done check_asic_reg
do read temp on Chain[5]
Chain[5] Chip[62] TempTypeID=55 middle offset=32
Chain[5] Chip[62] local Temp=48
Chain[5] Chip[62] middle Temp=35
Special fix Chain[5] Chip[62] middle Temp = 63
Done read temp on Chain[5]
do read temp on Chain[6]
Chain[6] Chip[62] TempTypeID=55 middle offset=32
Chain[6] Chip[62] local Temp=55
Chain[6] Chip[62] middle Temp=40
Special fix Chain[6] Chip[62] middle Temp = 70
Done read temp on Chain[6]
do read temp on Chain[7]
Chain[7] Chip[62] TempTypeID=00 middle offset=27
read failed, old value: Chain[7] Chip[62] local Temp=0
read failed on Chain[7] Chip[62] middle Temp old value:15
Special fix Chain[7] Chip[62] middle Temp = 15
Done read temp on Chain[7]
Set fixed full fan speed
FAN PWM: 100
read_temp_func Done!
CRC error counter=20888

MyRig

donator

Activity: 792

Merit: 510

[email protected]

You may want to use 1 PSU to power on your S9! that may help a bit of reducing problematic hash rate

Quote from: ChrisHaefner on January 14, 2017, 12:18:06 AM

Hello everyone. I have ran into a problem with my S9, so like I usually do I make a video. Basically what happened is after a successful night of mining, I went to power on my miner this morning and it wouldn't log onto my pool. I believe the pool was down. I tried once again after the pool was up with no success. So I reset the miner, installed new firmware and I was able to begin mining. Well now I'm stuck at a low hash rate and cant figure out why. If anyone could help or give insight it would be really appreciated! Thank you!

https://youtu.be/dRwalK8KpCE

My miner is an S9 Batch 13
Here are the two PSU’s I am using.

ChrisHaefner

member

Activity: 64

Merit: 10

crap.... okay, that's what bitmain basically said. Thank you

Posted From bitcointalk.org Android App

philipma1957

legendary

Activity: 4116

Merit: 7849

'The right to privacy matters'

Quote from: ChrisHaefner on January 18, 2017, 11:48:36 PM

Yes I live in the USA. However I did do an unsuccessful firmware upgrade while trouble shooting with a bitmain support person through email. I'll get some photos up.

Posted From bitcointalk.org Android App

Too bad. Once the red light is off on the hash boards firmware updates don't work.

Did batch 13 always auto tune?

Or were you able to under clock it?

You will need to send it in to be repaired.

You can try bitmainwarranty if you are out of warranty or send it to China if you are in warranty.

Is that screen shot of the controller and no boards?

If that is the case the controller looks okay.

You just have dead boards. ybitmainwarranty

May just want the three boards and repair them for about 300 or 400.

Good luck

ChrisHaefner

member

Activity: 64

Merit: 10

S9 Miner Status https://imgur.com/gallery/2Ypfc

Posted From bitcointalk.org Android App

ChrisHaefner

member

Activity: 64

Merit: 10

Yes I live in the USA. However I did do an unsuccessful firmware upgrade while trouble shooting with a bitmain support person through email. I'll get some photos up.

Posted From bitcointalk.org Android App

philipma1957

legendary

Activity: 4116

Merit: 7849

'The right to privacy matters'

Quote from: ChrisHaefner on January 14, 2017, 01:24:52 PM

I don't know how to share pictures on here, but if you follow this link you can see the bazaar way my miner status is displaying. It is only seeing 68 chips on my hash board. Like I said the miner was showing no problems the night before.
https://hashclub.org/topic/1312/needing-help-with-my-s9-batch-13

Posted From bitcointalk.org Android App

Power off all gear.

Do you live in the USA?

The gear is dead.

And I really hope you did not do any firmware upgrades.

Dis connect all the boards and fire up the controller.

I really hope you left the old firmware.

Join imgur for photos.

Screen shot the gui and post to imgur.

Post the screen shots here in 1600 by 1000 size.

Once again tell me what country you live in.

My hope is the boards need a repair and you can send all three to bitmainwarranty in the USA
Will cost you around 300 maybe more.

ChrisHaefner

member

Activity: 64

Merit: 10

I don't know how to share pictures on here, but if you follow this link you can see the bazaar way my miner status is displaying. It is only seeing 68 chips on my hash board. Like I said the miner was showing no problems the night before.
https://hashclub.org/topic/1312/needing-help-with-my-s9-batch-13

Posted From bitcointalk.org Android App

ChrisHaefner

member

Activity: 64

Merit: 10

I tried the new psu and it didn't work. I did notice one of my hashboards has a solid red light that is on and the others do not. I don't know if it has always been like this or not.

ChrisHaefner

member

Activity: 64

Merit: 10

Hello everyone. I have ran into a problem with my S9, so like I usually do I make a video. Basically what happened is after a successful night of mining, I went to power on my miner this morning and it wouldn't log onto my pool. I believe the pool was down. I tried once again after the pool was up with no success. So I reset the miner, installed new firmware and I was able to begin mining. Well now I'm stuck at a low hash rate and cant figure out why. If anyone could help or give insight it would be really appreciated! Thank you!

https://youtu.be/dRwalK8KpCE

My miner is an S9 Batch 13
Here are the two PSU’s I am using.

Specifications

Code:

Output	DC Voltage	12.25V
	Rated Current (220V input)	216A
	Rated Power (220V input)	2600W
	Rated Current (110V input)	108A
	Rated Power (110V input)	1300W
	Ripple & Noise	<1%
	Voltage Regulation	<2%
	Source Regulation	<1%
	Load Regulation	<1%
	Setup, Rise Time	<5S
	Power off Protection Trip Time	>10mS
	Interface Type	7pairs of 6pin PCI-E connectors. 380mm length for each PCI-E cable.
 
 
 
Input	Voltage Range	90-265V AC
	Current Range	10.5-16.5A
	Starting Voltage	100-240V AC
	Frequency Range	47-63Hz
	Power Factor	>0.95(full load)
	Leakage Current	<1.5mA (220V 50Hz)
 
 
Protection
 	Low-voltage Input	90-100V AC
	Output Short Circuit	Yes
	Output Overcurrent (220V input)	216-255A
	Output Overcurrent (110V input)	108-135A
	Overheat Protection	Yes
Environment   Conditions	Operating Temperature	-20 - +60℃
	Operating Humidity	20%-90% RH (non-condensing)
Structure
 	Dimensions	266mm*125mm*86mm
	Weight	2.5Kg
Cooling	Fan	Forced-air cooling
	Fan speed
 	When the temperature of the heat sink is higher than 80 ℃, the fan runs at full speed

Here are my options for firmware, which I am unaware of which to use.

Code:

Antminer S9 - Firmware
FileName	Description
Antminer-S9-all-201611290613-autofreq-user.tar.gz
* Support different frequency for each chips
* Use a higher voltage for hashboard initialization, to make chips work better in low temperature
* Attention: do not use this fw on old S9 miners with fixed frequency.
s9-20160715-550M.tar.gz
* Support S9 with fixed frequency 550M
s9-20160715-600M.tar.gz
* Support S9 with fixed frequency 600M
s9-20160715-650M.tar.gz
* Support S9 with fixed frequency 650M

I do not know what my monitor monitors but here is that info

Code:

Mem: 18836K used, 997336K free, 0K shrd, 0K buff, 5684K cached
CPU:  0.0% usr 10.0% sys  0.0% nic 90.0% idle  0.0% io  0.0% irq  0.0% sirq
Load average: 1.75 1.19 0.53 2/67 1138
PID  PPID USER     STAT   VSZ %VSZ CPU %CPU COMMAND
29010 29009 root     S <   165m 16.5   0  5.0 /usr/bin/bmminer --version-file /usr/bin/compile_time --api-listen --default-config /config/bmminer.conf
1051  1049 root     R     2836  0.2   0  5.0 top -b -n 1
281     1 root     S     3084  0.3   0  0.0 /usr/bin/ntpd -p /var/run/ntp.pid -g
219     1 root     S     2984  0.2   0  0.0 /usr/bin/monitor-recobtn /usr/bin/factory_config_reset.sh
232     1 root     S     2840  0.2   0  0.0 /sbin/getty 115200 ttyS0
233     1 root     S     2840  0.2   0  0.0 /sbin/getty 38400 tty1
234     1 root     S     2836  0.2   0  0.0 {monitorcg} /bin/sh /sbin/monitorcg
274     1 root     S     2836  0.2   0  0.0 udhcpc -b -t 10 -A 10 -x hostname antMiner -i eth0
1049   198 root     S     2836  0.2   0  0.0 /bin/sh /www/pages/cgi-bin/monitor.cgi
1052  1049 root     S     2836  0.2   0  0.0 /bin/sh /www/pages/cgi-bin/monitor.cgi
198     1 root     S     2776  0.2   0  0.0 /usr/sbin/lighttpd -f /etc/lighttpd.conf
24412   234 root     S     2704  0.2   0  0.0 sleep 3m
189     1 avahi    S     2612  0.2   0  0.0 avahi-daemon: running [antMiner.local]
190   189 avahi    S     2612  0.2   0  0.0 avahi-daemon: chroot helper
29009     1 root     S     2556  0.2   0  0.0 {screen} SCREEN -S bmminer -t bmminer -m -d /usr/bin/bmminer --version-file /usr/bin/compile_time --api-listen --default-config /config/bmminer.conf
180     1 root     S     2092  0.2   0  0.0 /usr/sbin/dropbear -r /config/dropbear_rsa_host_key -p 22
1     0 root     S     1688  0.1   0  0.0 init [5]
72     1 root     S     1676  0.1   0  0.0 /usr/bin/monitor-ipsig
22     2 root     SW       0  0.0   0  0.0 [kworker/0:1]
9     2 root     SW       0  0.0   0  0.0 [rcu_sched]
3     2 root     SW       0  0.0   0  0.0 [ksoftirqd/0]
64     2 root     SWN      0  0.0   0  0.0 [jffs2_gcd_mtd3]
6     2 root     DW       0  0.0   0  0.0 [kworker/u4:0]
2     0 root     SW       0  0.0   0  0.0 [kthreadd]
4     2 root     SW       0  0.0   0  0.0 [kworker/0:0]
5     2 root     SW<      0  0.0   0  0.0 [kworker/0:0H]
7     2 root     SW       0  0.0   0  0.0 [migration/0]
8     2 root     SW       0  0.0   0  0.0 [rcu_bh]
10     2 root     RW       0  0.0   0  0.0 [migration/1]
11     2 root     RW       0  0.0   0  0.0 [ksoftirqd/1]
12     2 root     SW       0  0.0   0  0.0 [kworker/1:0]
13     2 root     SW<      0  0.0   0  0.0 [kworker/1:0H]
14     2 root     SW<      0  0.0   0  0.0 [khelper]
15     2 root     SW       0  0.0   0  0.0 [kdevtmpfs]
16     2 root     SW<      0  0.0   0  0.0 [netns]
17     2 root     SW<      0  0.0   0  0.0 [writeback]
18     2 root     SW<      0  0.0   0  0.0 [bioset]
19     2 root     SW<      0  0.0   0  0.0 [kblockd]
20     2 root     SW       0  0.0   0  0.0 [khubd]
21     2 root     SW<      0  0.0   0  0.0 [rpciod]
23     2 root     SW       0  0.0   0  0.0 [khungtaskd]
24     2 root     SW       0  0.0   0  0.0 [kswapd0]
25     2 root     SW       0  0.0   0  0.0 [fsnotify_mark]
26     2 root     SW<      0  0.0   0  0.0 [nfsiod]
27     2 root     SW       0  0.0   0  0.0 [kworker/u4:1]
34     2 root     SW<      0  0.0   0  0.0 [fff00000.spi]
39     2 root     SW<      0  0.0   0  0.0 [kpsmoused]
40     2 root     SW<      0  0.0   0  0.0 [dw-mci-card]
41     2 root     SW<      0  0.0   0  0.0 [deferwq]
42     2 root     SW       0  0.0   0  0.0 [kworker/u4:2]

Lastly here is my Kernel Log

Code:

l2x0: 8 ways, CACHE_ID 0x410030c9, AUX_CTRL 0x32460000, Cache size: 524288 B
syscon fffef000.l2-cache: regmap [mem 0xfffef000-0xfffeffff] registered
syscon ffd05000.rstmgr: regmap [mem 0xffd05000-0xffd05fff] registered
syscon ffc25000.sdrctl: regmap [mem 0xffc25000-0xffc25fff] registered
syscon ff800000.l3regs: regmap [mem 0xff800000-0xff800fff] registered
syscon ffd08000.sysmgr: regmap [mem 0xffd08000-0xffd0bfff] registered
hw-breakpoint: found 5 (+1 reserved) breakpoint and 1 watchpoint registers.
hw-breakpoint: maximum watchpoint size is 4 bytes.
altera_hps2fpga_bridge fpgabridge.2: fpga bridge [hps2fpga] registered as device hps2fpga
altera_hps2fpga_bridge fpgabridge.2: init-val not specified
altera_hps2fpga_bridge fpgabridge.3: fpga bridge [lshps2fpga] registered as device lwhps2fpga
altera_hps2fpga_bridge fpgabridge.3: init-val not specified
altera_hps2fpga_bridge fpgabridge.4: fpga bridge [fpga2hps] registered as device fpga2hps
altera_hps2fpga_bridge fpgabridge.4: init-val not specified
bio: create slab  at 0
FPGA Mangager framework driver
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
pps_core: LinuxPPS API ver. 1 registered
pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti 
PTP clock support registered
Switching to clocksource timer0
NET: Registered protocol family 2
TCP established hash table entries: 8192 (order: 4, 65536 bytes)
TCP bind hash table entries: 8192 (order: 4, 65536 bytes)
TCP: Hash tables configured (established 8192 bind 8192)
TCP: reno registered
UDP hash table entries: 512 (order: 2, 16384 bytes)
UDP-Lite hash table entries: 512 (order: 2, 16384 bytes)
NET: Registered protocol family 1
RPC: Registered named UNIX socket transport module.
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
hw perfevents: enabled with ARMv7 Cortex-A9 PMU driver, 7 counters available
arm-pmu arm-pmu: PMU:CTI successfully enabled for 1 cores
NFS: Registering the id_resolver key type
Key type id_resolver registered
Key type id_legacy registered
NTFS driver 2.1.30 [Flags: R/W].
jffs2: version 2.2. (NAND) © 2001-2006 Red Hat, Inc.
msgmni has been set to 1984
io scheduler noop registered (default)
Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled
ffc02000.serial0: ttyS0 at MMIO 0xffc02000 (irq = 194) is a 16550A
console [ttyS0] enabled
altera_fpga_manager ff706000.fpgamgr: fpga manager [Altera FPGA Manager] registered as minor 0
brd: module loaded
denali-nand-dt ff900000.nand: Dump timing register values:acc_clks: 4, re_2_we: 20, re_2_re: 20
we_2_re: 12, addr_2_data: 14, rdwr_en_lo_cnt: 2
rdwr_en_hi_cnt: 2, cs_setup_cnt: 2
ONFI param page 0 valid
ONFI flash detected
NAND device: Manufacturer ID: 0x2c, Chip ID: 0xda (Micron MT29F2G08ABAEAWP), 256MiB, page size: 2048, OOB size: 64
Bad block table found at page 131008, version 0x01
Bad block table found at page 130944, version 0x01
5 ofpart partitions found on MTD device denali-nand
Creating 5 MTD partitions on "denali-nand":
0x000000000000-0x000001000000 : "NAND Flash Boot Area 16MB"
0x000001000000-0x000002000000 : "NAND Flash Boot Area backup1 16MB"
0x000002000000-0x000003000000 : "NAND Flash Boot Area backup2 16MB"
0x000003000000-0x00000b000000 : "NAND Flash jffs2 Root Filesystem 128MB"
0x00000b000000-0x000010000000 : "NAND Flash jffs2 Root Filesystem 80MB"
dw_spi_mmio fff00000.spi: master is unqueued, this is deprecated
CAN device driver interface
c_can_platform ffc00000.d_can: invalid resource
c_can_platform ffc00000.d_can: control memory is not used for raminit
c_can_platform ffc00000.d_can: c_can_platform device registered (regs=bf8dc000, irq=163)
stmmac_hw_init: 1000M
stmmac - user ID: 0x10, Synopsys ID: 0x37
 Ring mode enabled
 DMA HW capability register supported
 Enhanced/Alternate descriptors
	Enabled extended descriptors
 RX Checksum Offload Engine supported (type 2)
 TX Checksum insertion supported
 Enable RX Mitigation via HW Watchdog Timer
libphy: stmmac: probed
eth0: PHY ID 0007c0f1 at 0 IRQ POLL (stmmac-0:00) active
usbcore: registered new interface driver usb-storage
mousedev: PS/2 mouse device common for all mice
i2c /dev entries driver
Synopsys Designware Multimedia Card Interface Driver
dwmmc_socfpga ff704000.dwmmc0: couldn't determine pwr-en, assuming pwr-en = 0
dwmmc_socfpga ff704000.dwmmc0: Using internal DMA controller.
dwmmc_socfpga ff704000.dwmmc0: Version ID is 240a
dwmmc_socfpga ff704000.dwmmc0: DW MMC controller at irq 171, 32 bit host data width, 1024 deep fifo
mmc_host mmc0: Bus speed (slot 0) = 50000000Hz (slot req 400000Hz, actual 396825HZ div = 63)
dwmmc_socfpga ff704000.dwmmc0: 1 slots initialized
ledtrig-cpu: registered to indicate activity on CPUs
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
oprofile: using arm/armv7-ca9
TCP: cubic registered
NET: Registered protocol family 10
sit: IPv6 over IPv4 tunneling driver
NET: Registered protocol family 17
NET: Registered protocol family 15
can: controller area network core (rev 20120528 abi 9)
NET: Registered protocol family 29
can: raw protocol (rev 20120528)
can: broadcast manager protocol (rev 20120528 t)
can: netlink gateway (rev 20130117) max_hops=1
8021q: 802.1Q VLAN Support v1.8
Key type dns_resolver registered
VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4
ThumbEE CPU extension supported.
Registering SWP/SWPB emulation handler
mmc_host mmc0: Bus speed (slot 0) = 50000000Hz (slot req 300000Hz, actual 297619HZ div = 84)
mmc_host mmc0: Timeout sending command (cmd 0x202000 arg 0x0 status 0x80202000)
mmc_host mmc0: Timeout sending command (cmd 0x202000 arg 0x0 status 0x80202000)
mmc_host mmc0: Timeout sending command (cmd 0x202000 arg 0x0 status 0x80202000)
jffs2: Empty flash at 0x00fd5150 ends at 0x00fd5800
jffs2: jffs2_scan_eraseblock(): Node at 0x063647f8 {0x1985, 0xe002, 0x00000079) has invalid CRC 0xe0021985 (calculated 0x9ab6db61)
jffs2: jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x063647fc: 0x0079 instead
jffs2: jffs2_scan_inode_node(): CRC failed on node at 0x063697cc: Read 0xffffffff, calculated 0xbc7d35f3
VFS: Mounted root (jffs2 filesystem) on device 31:3.
devtmpfs: mounted
Freeing unused kernel memory: 328K (8065b000 - 806ad000)
eth0: device MAC address 52:bb:24:0d:bf:12
init phy ok 
PHY DMA init OK
eth0: device MAC address 38:3f:93:19:4d:f0
init phy ok 
PHY DMA init OK
IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
libphy: stmmac-0:00 - Link is Up - 100/Full
IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
In axi fpga driver!
Original value in RESET_MANAGER_BASE_ADDR + BRGMODRST_ADDR is 0x0
request_mem_region OK!
AXI fpga dev virtual address is 0xbf942000
*base_vir_addr = 0xc504
In fpga mem driver!
request_mem_region OK!
fpga mem virtual address is 0xc0000000
eth0: device MAC address 38:3f:93:19:4d:f0
init phy ok 
PHY DMA init OK
IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
eth0: device MAC address 38:3f:93:19:4d:f0
init phy ok 
PHY DMA init OK
IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
libphy: stmmac-0:00 - Link is Up - 100/Full
IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
INFO: task kworker/u4:0:6 blocked for more than 120 seconds.
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
kworker/u4:0    D 804a9948     0     6      2 0x00000000
Workqueue: kmmcd mmc_rescan
[<804a9948>] (__schedule+0x1f4/0x600) from [<804a9e48>] (schedule+0x40/0x80)
[<804a9e48>] (schedule+0x40/0x80) from [<804a7f68>] (schedule_timeout+0x140/0x1c8)
[<804a7f68>] (schedule_timeout+0x140/0x1c8) from [<804a9464>] (wait_for_common+0xd8/0x180)
[<804a9464>] (wait_for_common+0xd8/0x180) from [<804a952c>] (wait_for_completion+0x20/0x24)
[<804a952c>] (wait_for_completion+0x20/0x24) from [<8036b4a0>] (mmc_wait_for_req+0x70/0xec)
[<8036b4a0>] (mmc_wait_for_req+0x70/0xec) from [<8036b5a0>] (mmc_wait_for_cmd+0x84/0xa4)
[<8036b5a0>] (mmc_wait_for_cmd+0x84/0xa4) from [<8037527c>] (mmc_io_rw_direct_host+0xa8/0x11c)
[<8037527c>] (mmc_io_rw_direct_host+0xa8/0x11c) from [<8037579c>] (sdio_reset+0x3c/0x74)
[<8037579c>] (sdio_reset+0x3c/0x74) from [<8036d8bc>] (mmc_rescan+0x224/0x2d4)
[<8036d8bc>] (mmc_rescan+0x224/0x2d4) from [<8003ed7c>] (process_one_work+0x160/0x3f0)
[<8003ed7c>] (process_one_work+0x160/0x3f0) from [<8003f4a8>] (worker_thread+0x144/0x3bc)
[<8003f4a8>] (worker_thread+0x144/0x3bc) from [<8004567c>] (kthread+0xb4/0xc0)
[<8004567c>] (kthread+0xb4/0xc0) from [<8000e818>] (ret_from_fork+0x14/0x20)
INFO: task kworker/u4:0:6 blocked for more than 120 seconds.
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
kworker/u4:0    D 804a9948     0     6      2 0x00000000
Workqueue: kmmcd mmc_rescan
[<804a9948>] (__schedule+0x1f4/0x600) from [<804a9e48>] (schedule+0x40/0x80)
[<804a9e48>] (schedule+0x40/0x80) from [<804a7f68>] (schedule_timeout+0x140/0x1c8)
[<804a7f68>] (schedule_timeout+0x140/0x1c8) from [<804a9464>] (wait_for_common+0xd8/0x180)
[<804a9464>] (wait_for_common+0xd8/0x180) from [<804a952c>] (wait_for_completion+0x20/0x24)
[<804a952c>] (wait_for_completion+0x20/0x24) from [<8036b4a0>] (mmc_wait_for_req+0x70/0xec)
[<8036b4a0>] (mmc_wait_for_req+0x70/0xec) from [<8036b5a0>] (mmc_wait_for_cmd+0x84/0xa4)
[<8036b5a0>] (mmc_wait_for_cmd+0x84/0xa4) from [<8037527c>] (mmc_io_rw_direct_host+0xa8/0x11c)
[<8037527c>] (mmc_io_rw_direct_host+0xa8/0x11c) from [<8037579c>] (sdio_reset+0x3c/0x74)
[<8037579c>] (sdio_reset+0x3c/0x74) from [<8036d8bc>] (mmc_rescan+0x224/0x2d4)
[<8036d8bc>] (mmc_rescan+0x224/0x2d4) from [<8003ed7c>] (process_one_work+0x160/0x3f0)
[<8003ed7c>] (process_one_work+0x160/0x3f0) from [<8003f4a8>] (worker_thread+0x144/0x3bc)
[<8003f4a8>] (worker_thread+0x144/0x3bc) from [<8004567c>] (kthread+0xb4/0xc0)
[<8004567c>] (kthread+0xb4/0xc0) from [<8000e818>] (ret_from_fork+0x14/0x20)
INFO: task kworker/u4:0:6 blocked for more than 120 seconds.
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
kworker/u4:0    D 804a9948     0     6      2 0x00000000
Workqueue: kmmcd mmc_rescan
[<804a9948>] (__schedule+0x1f4/0x600) from [<804a9e48>] (schedule+0x40/0x80)
[<804a9e48>] (schedule+0x40/0x80) from [<804a7f68>] (schedule_timeout+0x140/0x1c8)
[<804a7f68>] (schedule_timeout+0x140/0x1c8) from [<804a9464>] (wait_for_common+0xd8/0x180)
[<804a9464>] (wait_for_common+0xd8/0x180) from [<804a952c>] (wait_for_completion+0x20/0x24)
[<804a952c>] (wait_for_completion+0x20/0x24) from [<8036b4a0>] (mmc_wait_for_req+0x70/0xec)
[<8036b4a0>] (mmc_wait_for_req+0x70/0xec) from [<8036b5a0>] (mmc_wait_for_cmd+0x84/0xa4)
[<8036b5a0>] (mmc_wait_for_cmd+0x84/0xa4) from [<8037527c>] (mmc_io_rw_direct_host+0xa8/0x11c)
[<8037527c>] (mmc_io_rw_direct_host+0xa8/0x11c) from [<8037579c>] (sdio_reset+0x3c/0x74)
[<8037579c>] (sdio_reset+0x3c/0x74) from [<8036d8bc>] (mmc_rescan+0x224/0x2d4)
[<8036d8bc>] (mmc_rescan+0x224/0x2d4) from [<8003ed7c>] (process_one_work+0x160/0x3f0)
[<8003ed7c>] (process_one_work+0x160/0x3f0) from [<8003f4a8>] (worker_thread+0x144/0x3bc)
[<8003f4a8>] (worker_thread+0x144/0x3bc) from [<8004567c>] (kthread+0xb4/0xc0)
[<8004567c>] (kthread+0xb4/0xc0) from [<8000e818>] (ret_from_fork+0x14/0x20)

Topic: Low hash rate with S9 bath13, Boards apear to be fine (Read 1737 times)