Does it seem that you still don't solve the issue?
Do you have a multimeter tester? Could you try to check the power terminal if it's shorted point the positive polarity into the ground then the negative polarity into power terminal one by one to check if there is resistance to all terminals on each plug.
If it's shorted there is a high chance that few capacitors are shorted you need to find those shorted parts remove the capacitor without replacing it won't be a problem.
Topic: Antminer T17e ERROR_POWER_LOST (Read 121 times)
Please try hash board separately.
Impedance looks fine.
And please make a detailed(macro) photo of hash board, TOP and BOTTOM side.
Maybe was repaired and voltage feedback have bad reference.
Already tried it alone and still id doesn't work, I'm now packaging the boards to send back to china for repair Impedance looks fine.
And please make a detailed(macro) photo of hash board, TOP and BOTTOM side.
Maybe was repaired and voltage feedback have bad reference.
thank you for your kind help
it is not the issue with PSU because power lost error message is coming only with One board I even disconnect other boards and connect only this board and error still appears, once I disconnect this specific board and reconnect the remaining two device is hashing normally
so I think this board is already dead and shorted somewhere ,
so I think this board is already dead and shorted somewhere ,
Did you buy a used(2nd hand) miner?
If not, then you can send them back to bitmain for repair.
Can you try to check the hashboard physically and maybe there are some burnt parts under the power terminal. If not, try to clean the whole power terminal and some parts with lacquer flo thinner then try to run it again.
Also, you can troubleshoot the hashboard follow the guide from here https://www.zeusbtc.com/articles/information/185-antminer-t17e-manual-download
Please try hash board separately.
Impedance looks fine.
And please make a detailed(macro) photo of hash board, TOP and BOTTOM side.
Maybe was repaired and voltage feedback have bad reference.
Impedance looks fine.
And please make a detailed(macro) photo of hash board, TOP and BOTTOM side.
Maybe was repaired and voltage feedback have bad reference.
it is not the issue with PSU because power lost error message is coming only with One board I even disconnect other boards and connect only this board and error still appears, once I disconnect this specific board and reconnect the remaining two device is hashing normally
so I think this board is already dead and shorted somewhere ,
so I think this board is already dead and shorted somewhere ,
Did you buy a used(2nd hand) miner?
If not, then you can send them back to bitmain for repair.
Can you try to check the hashboard physically and maybe there are some burnt parts under the power terminal. If not, try to clean the whole power terminal and some parts with lacquer flo thinner then try to run it again.
Also, you can troubleshoot the hashboard follow the guide from here https://www.zeusbtc.com/articles/information/185-antminer-t17e-manual-download
Where did you attach the photos to? i can't see them.
Anyway i think your PSU is dying and it can't run three hash boards so when you discconected one of them the miner worked fine, a faully hash board does not really cause the kernel log to report power loss.
You can confirm this by swapping another hash board (the one you think is faulty) with one of the two running now.
pictures are in the quote, i will post here again Anyway i think your PSU is dying and it can't run three hash boards so when you discconected one of them the miner worked fine, a faully hash board does not really cause the kernel log to report power loss.
You can confirm this by swapping another hash board (the one you think is faulty) with one of the two running now.
https://imgbb.com/bPGfKvs Q2 Measurement
https://imgbb.com/vvf9QqD Q1 Measurement
https://imgbb.com/YfnDM9K Q4 Measurements
it is not the issue with PSU because power lost error message is coming only with One board I even disconnect other boards and connect only this board and error still appears, once I disconnect this specific board and reconnect the remaining two device is hashing normally
so I think this board is already dead and shorted somewhere ,
Where did you attach the photos to? i can't see them.
Anyway i think your PSU is dying and it can't run three hash boards so when you discconected one of them the miner worked fine, a faully hash board does not really cause the kernel log to report power loss.
You can confirm this by swapping another hash board (the one you think is faulty) with one of the two running now.
Anyway i think your PSU is dying and it can't run three hash boards so when you discconected one of them the miner worked fine, a faully hash board does not really cause the kernel log to report power loss.
You can confirm this by swapping another hash board (the one you think is faulty) with one of the two running now.
In my log you can saw .
Set to voltage raw 1800, step by step. -> You must measure PSU output voltage 18V +-
Set to voltage raw 2000, step by step. -> You must measure PSU output voltage 20V +-
And here is photo where measure output voltage on PSU
https://ibb.co/B3nM0BV
If you have a multimeter you can measure impedance(Ohm) on Chain0 between Source and Drain and Gate ( MOS transistor)
And give us result.
Here is photo what to do.
https://ibb.co/85hLtRd
https://ibb.co/bPGfKvs Q2 measurement
And you can try measure impedance between V_Boost and Input Voltage -> on the Chain 0
https://ibb.co/8shv4wH
https://ibb.co/vvf9QqD Q1 measurement
https://ibb.co/YfnDM9K Q4 measurement
Set to voltage raw 1800, step by step. -> You must measure PSU output voltage 18V +-
Set to voltage raw 2000, step by step. -> You must measure PSU output voltage 20V +-
And here is photo where measure output voltage on PSU
https://ibb.co/B3nM0BV
If you have a multimeter you can measure impedance(Ohm) on Chain0 between Source and Drain and Gate ( MOS transistor)
And give us result.
Here is photo what to do.
https://ibb.co/85hLtRd
https://ibb.co/bPGfKvs Q2 measurement
And you can try measure impedance between V_Boost and Input Voltage -> on the Chain 0
https://ibb.co/8shv4wH
https://ibb.co/vvf9QqD Q1 measurement
https://ibb.co/YfnDM9K Q4 measurement
Code:
1970-01-01 00:01:34:board.c:81:jump_and_app_check_restore_pic: chain[0] PIC jump to app
1970-01-01 00:01:36:board.c:94:jump_and_app_check_restore_pic: Check chain[0] PIC fw version=0x88
1970-01-01 00:01:36:thread.c:762:create_pic_heart_beat_thread: create thread
1970-01-01 00:01:40:power_api.c:322:set_to_check_asic_voltage_by_steps: Set to voltage raw 1800, step by step.
1970-01-01 00:01:58:uart.c:69:set_baud: set UART baud to 115200
1970-01-01 00:02:01:power_api.c:322:set_to_check_asic_voltage_by_steps: Set to voltage raw 1800, step by step.
1970-01-01 00:02:10:driver-btm-api.c:906:check_asic_number_with_power_on: Chain[0]: find 78 asic, times 0
1970-01-01 00:02:10:power_api.c:383:set_to_highest_voltage_by_steps: Set to voltage raw 2000, step by step.
1970-01-01 00:01:36:board.c:94:jump_and_app_check_restore_pic: Check chain[0] PIC fw version=0x88
1970-01-01 00:01:36:thread.c:762:create_pic_heart_beat_thread: create thread
1970-01-01 00:01:40:power_api.c:322:set_to_check_asic_voltage_by_steps: Set to voltage raw 1800, step by step.
1970-01-01 00:01:58:uart.c:69:set_baud: set UART baud to 115200
1970-01-01 00:02:01:power_api.c:322:set_to_check_asic_voltage_by_steps: Set to voltage raw 1800, step by step.
1970-01-01 00:02:10:driver-btm-api.c:906:check_asic_number_with_power_on: Chain[0]: find 78 asic, times 0
1970-01-01 00:02:10:power_api.c:383:set_to_highest_voltage_by_steps: Set to voltage raw 2000, step by step.
thank you for your reply i done as you suggested and attached photos in quote please check them
In my log you can saw .
Set to voltage raw 1800, step by step. -> You must measure PSU output voltage 18V +-
Set to voltage raw 2000, step by step. -> You must measure PSU output voltage 20V +-
And here is photo where measure output voltage on PSU
If you have a multimeter you can measure impedance(Ohm) on Chain0 between Source and Drain and Gate ( MOS transistor)
And give us result.
Here is photo what to do.
And you can try measure impedance between V_Boost and Input Voltage -> on the Chain 0
Set to voltage raw 1800, step by step. -> You must measure PSU output voltage 18V +-
Set to voltage raw 2000, step by step. -> You must measure PSU output voltage 20V +-
And here is photo where measure output voltage on PSU
If you have a multimeter you can measure impedance(Ohm) on Chain0 between Source and Drain and Gate ( MOS transistor)
And give us result.
Here is photo what to do.
And you can try measure impedance between V_Boost and Input Voltage -> on the Chain 0
Code:
1970-01-01 00:01:34:board.c:81:jump_and_app_check_restore_pic: chain[0] PIC jump to app
1970-01-01 00:01:36:board.c:94:jump_and_app_check_restore_pic: Check chain[0] PIC fw version=0x88
1970-01-01 00:01:36:thread.c:762:create_pic_heart_beat_thread: create thread
1970-01-01 00:01:40:power_api.c:322:set_to_check_asic_voltage_by_steps: Set to voltage raw 1800, step by step.
1970-01-01 00:01:58:uart.c:69:set_baud: set UART baud to 115200
1970-01-01 00:02:01:power_api.c:322:set_to_check_asic_voltage_by_steps: Set to voltage raw 1800, step by step.
1970-01-01 00:02:10:driver-btm-api.c:906:check_asic_number_with_power_on: Chain[0]: find 78 asic, times 0
1970-01-01 00:02:10:power_api.c:383:set_to_highest_voltage_by_steps: Set to voltage raw 2000, step by step.
1970-01-01 00:01:36:board.c:94:jump_and_app_check_restore_pic: Check chain[0] PIC fw version=0x88
1970-01-01 00:01:36:thread.c:762:create_pic_heart_beat_thread: create thread
1970-01-01 00:01:40:power_api.c:322:set_to_check_asic_voltage_by_steps: Set to voltage raw 1800, step by step.
1970-01-01 00:01:58:uart.c:69:set_baud: set UART baud to 115200
1970-01-01 00:02:01:power_api.c:322:set_to_check_asic_voltage_by_steps: Set to voltage raw 1800, step by step.
1970-01-01 00:02:10:driver-btm-api.c:906:check_asic_number_with_power_on: Chain[0]: find 78 asic, times 0
1970-01-01 00:02:10:power_api.c:383:set_to_highest_voltage_by_steps: Set to voltage raw 2000, step by step.
Hello,
You disconnected Chain 0 or Chain 2 ?
Try to measure voltage on metal plates when miner is powering up, not 12V output to control board.
Normal output voltage is 18V (first voltage check) ... second is 20V, third 21V ...
Try every chain separately and give us result.
M.
You disconnected Chain 0 or Chain 2 ?
Try to measure voltage on metal plates when miner is powering up, not 12V output to control board.
Normal output voltage is 18V (first voltage check) ... second is 20V, third 21V ...
Try every chain separately and give us result.
M.
sorry, I disconnected chain 0
I dont get what you mean by first one is 18v and second is 20 v , do you mean voltage for each hash board ? and between which points i should measure the voltage ?
Hello,
You disconnected Chain 0 or Chain 2 ?
Try to measure voltage on metal plates when miner is powering up, not 12V output to control board.
Normal output voltage is 18V (first voltage check) ... second is 20V, third 21V ...
Try every chain separately and give us result.
M.
You disconnected Chain 0 or Chain 2 ?
Try to measure voltage on metal plates when miner is powering up, not 12V output to control board.
Normal output voltage is 18V (first voltage check) ... second is 20V, third 21V ...
Try every chain separately and give us result.
M.
hello everyone
I recently bought T17e (which was the worst thing I done recently) anyway it run for one time then power lost error message keep appearing
I replaced voltage regulation cable and message still there and no mining
I checked the output of the PSU and it was 12.27 Volt
I also change the socket where i connect the miner and problem is still there
i flashed the latest bitmain firmware and nothing changed
I dont know what to do next
is there anything i've missed ?
please check below kernel log
Edit: one time I flashed S17e firmware by mistake and then revert back to T17e bitmain firmware
UPDATE: I disconnect chain 2 hash board and was able to mine with 2 hash boards, I didn't try this before I only tried to swap cables between all the 3 hash boards I never tried to disconnect a hash board, so I guess I have a dead hash board need to be replaced.
I recently bought T17e (which was the worst thing I done recently) anyway it run for one time then power lost error message keep appearing
I replaced voltage regulation cable and message still there and no mining
I checked the output of the PSU and it was 12.27 Volt
I also change the socket where i connect the miner and problem is still there
i flashed the latest bitmain firmware and nothing changed
I dont know what to do next
is there anything i've missed ?
please check below kernel log
Edit: one time I flashed S17e firmware by mistake and then revert back to T17e bitmain firmware
UPDATE: I disconnect chain 2 hash board and was able to mine with 2 hash boards, I didn't try this before I only tried to swap cables between all the 3 hash boards I never tried to disconnect a hash board, so I guess I have a dead hash board need to be replaced.
Code:
NET: Registered protocol family 17
can: controller area network core (rev 20120528 abi 9)
NET: Registered protocol family 29
can: raw protocol (rev 20120528)
can: broadcast manager protocol (rev 20120528 t)
can: netlink gateway (rev 20130117) max_hops=1
zynq_pm_ioremap: no compatible node found for 'xlnx,zynq-ddrc-a05'
zynq_pm_late_init: Unable to map DDRC IO memory.
Registering SWP/SWPB emulation handler
hctosys: unable to open rtc device (rtc0)
ALSA device list:
No soundcards found.
RAMDISK: gzip image found at block 0
EXT4-fs (ram0): couldn't mount as ext3 due to feature incompatibilities
EXT4-fs (ram0): mounted filesystem without journal. Opts: (null)
VFS: Mounted root (ext4 filesystem) on device 1:0.
devtmpfs: mounted
Freeing unused kernel memory: 1024K (c0a00000 - c0b00000)
EXT4-fs (ram0): re-mounted. Opts: block_validity,delalloc,barrier,user_xattr
random: dd urandom read with 0 bits of entropy available
ubi0: attaching mtd2
ubi0: scanning is finished
ubi0: attached mtd2 (name "configs", size 8 MiB)
ubi0: PEB size: 131072 bytes (128 KiB), LEB size: 129024 bytes
ubi0: min./max. I/O unit sizes: 2048/2048, sub-page size 512
ubi0: VID header offset: 512 (aligned 512), data offset: 2048
ubi0: good PEBs: 64, bad PEBs: 0, corrupted PEBs: 0
ubi0: user volume: 1, internal volumes: 1, max. volumes count: 128
ubi0: max/mean erase counter: 6/2, WL threshold: 4096, image sequence number: 614353782
ubi0: available PEBs: 0, total reserved PEBs: 64, PEBs reserved for bad PEB handling: 40
ubi0: background thread "ubi_bgt0d" started, PID 708
UBIFS (ubi0:0): background thread "ubifs_bgt0_0" started, PID 711
UBIFS (ubi0:0): recovery needed
UBIFS (ubi0:0): recovery completed
UBIFS (ubi0:0): UBIFS: mounted UBI device 0, volume 0, name "configs"
UBIFS (ubi0:0): LEB size: 129024 bytes (126 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
UBIFS (ubi0:0): FS size: 1419264 bytes (1 MiB, 11 LEBs), journal size 903169 bytes (0 MiB, 5 LEBs)
UBIFS (ubi0:0): reserved for root: 67035 bytes (65 KiB)
UBIFS (ubi0:0): media format: w4/r0 (latest is w4/r0), UUID 70BCC183-B57C-4138-BB2B-76F5CD328150, small LPT model
ubi1: attaching mtd5
ubi1 warning: ubi_io_read: error -74 (ECC error) while reading 64 bytes from PEB 713:0, read only 64 bytes, retry
ubi1 warning: ubi_io_read: error -74 (ECC error) while reading 64 bytes from PEB 713:0, read only 64 bytes, retry
ubi1 warning: ubi_io_read: error -74 (ECC error) while reading 64 bytes from PEB 713:0, read only 64 bytes, retry
ubi1 error: ubi_io_read: error -74 (ECC error) while reading 64 bytes from PEB 713:0, read 64 bytes
CPU: 0 PID: 717 Comm: ubiattach Not tainted 4.6.0-xilinx-gff8137b-dirty #25
Hardware name: Xilinx Zynq Platform
[] (unwind_backtrace) from [] (show_stack+0x10/0x14)
[] (show_stack) from [] (dump_stack+0x84/0xa4)
[] (dump_stack) from [] (ubi_io_read+0x1d4/0x2a8)
[] (ubi_io_read) from [] (ubi_io_read_ec_hdr+0x68/0x1cc)
[] (ubi_io_read_ec_hdr) from [] (ubi_attach+0x130/0x1194)
[] (ubi_attach) from [] (ubi_attach_mtd_dev+0x62c/0xaf8)
[] (ubi_attach_mtd_dev) from [] (ctrl_cdev_ioctl+0xf0/0x1ec)
[] (ctrl_cdev_ioctl) from [] (vfs_ioctl+0x20/0x34)
[] (vfs_ioctl) from [] (do_vfs_ioctl+0x7d8/0x8b0)
[] (do_vfs_ioctl) from [] (SyS_ioctl+0x34/0x5c)
[] (SyS_ioctl) from [] (ret_fast_syscall+0x0/0x3c)
ubi1 warning: ubi_io_read: error -74 (ECC error) while reading 512 bytes from PEB 713:512, read only 512 bytes, retry
ubi1 warning: ubi_io_read: error -74 (ECC error) while reading 512 bytes from PEB 713:512, read only 512 bytes, retry
ubi1 warning: ubi_io_read: error -74 (ECC error) while reading 512 bytes from PEB 713:512, read only 512 bytes, retry
ubi1 error: ubi_io_read: error -74 (ECC error) while reading 512 bytes from PEB 713:512, read 512 bytes
CPU: 0 PID: 717 Comm: ubiattach Not tainted 4.6.0-xilinx-gff8137b-dirty #25
Hardware name: Xilinx Zynq Platform
[] (unwind_backtrace) from [] (show_stack+0x10/0x14)
[] (show_stack) from [] (dump_stack+0x84/0xa4)
[] (dump_stack) from [] (ubi_io_read+0x1d4/0x2a8)
[] (ubi_io_read) from [] (ubi_io_read_vid_hdr+0x6c/0x1d8)
[] (ubi_io_read_vid_hdr) from [] (ubi_attach+0x1ec/0x1194)
[] (ubi_attach) from [] (ubi_attach_mtd_dev+0x62c/0xaf8)
[] (ubi_attach_mtd_dev) from [] (ctrl_cdev_ioctl+0xf0/0x1ec)
[] (ctrl_cdev_ioctl) from [] (vfs_ioctl+0x20/0x34)
[] (vfs_ioctl) from [] (do_vfs_ioctl+0x7d8/0x8b0)
[] (do_vfs_ioctl) from [] (SyS_ioctl+0x34/0x5c)
[] (SyS_ioctl) from [] (ret_fast_syscall+0x0/0x3c)
ubi1: scanning is finished
ubi1: attached mtd5 (name "reserve1", size 128 MiB)
ubi1: PEB size: 131072 bytes (128 KiB), LEB size: 129024 bytes
ubi1: min./max. I/O unit sizes: 2048/2048, sub-page size 512
ubi1: VID header offset: 512 (aligned 512), data offset: 2048
ubi1: good PEBs: 1019, bad PEBs: 5, corrupted PEBs: 0
ubi1: user volume: 1, internal volumes: 1, max. volumes count: 128
ubi1: max/mean erase counter: 2/0, WL threshold: 4096, image sequence number: 1313025816
ubi1: available PEBs: 0, total reserved PEBs: 1019, PEBs reserved for bad PEB handling: 35
ubi1: background thread "ubi_bgt1d" started, PID 720
ubi1 warning: ubi_io_read: error -74 (ECC error) while reading 512 bytes from PEB 713:512, read only 512 bytes, retry
UBIFS (ubi1:0): background thread "ubifs_bgt1_0" started, PID 723
ubi1 warning: ubi_io_read: error -74 (ECC error) while reading 512 bytes from PEB 713:512, read only 512 bytes, retry
UBIFS (ubi1:0): recovery needed
ubi1 warning: ubi_io_read: error -74 (ECC error) while reading 512 bytes from PEB 713:512, read only 512 bytes, retry
ubi1 error: ubi_io_read: error -74 (ECC error) while reading 512 bytes from PEB 713:512, read 512 bytes
CPU: 0 PID: 720 Comm: ubi_bgt1d Not tainted 4.6.0-xilinx-gff8137b-dirty #25
Hardware name: Xilinx Zynq Platform
[] (unwind_backtrace) from [] (show_stack+0x10/0x14)
[] (show_stack) from [] (dump_stack+0x84/0xa4)
[] (dump_stack) from [] (ubi_io_read+0x1d4/0x2a8)
[] (ubi_io_read) from [] (ubi_io_read_vid_hdr+0x6c/0x1d8)
[] (ubi_io_read_vid_hdr) from [] (wear_leveling_worker+0x1e0/0x6a0)
[] (wear_leveling_worker) from [] (do_work+0xcc/0x100)
[] (do_work) from [] (ubi_thread+0x100/0x190)
[] (ubi_thread) from [] (kthread+0xdc/0xf0)
[] (kthread) from [] (ret_from_fork+0x14/0x3c)
ubi1 warning: ubi_io_read: error -74 (ECC error) while reading 512 bytes from PEB 709:512, read only 512 bytes, retry
UBIFS (ubi1:0): recovery completed
UBIFS (ubi1:0): UBIFS: mounted UBI device 1, volume 0, name "reserve1"
UBIFS (ubi1:0): LEB size: 129024 bytes (126 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
UBIFS (ubi1:0): FS size: 125024256 bytes (119 MiB, 969 LEBs), journal size 6322176 bytes (6 MiB, 49 LEBs)
UBIFS (ubi1:0): reserved for root: 4952683 bytes (4836 KiB)
UBIFS (ubi1:0): media format: w4/r0 (latest is w4/r0), UUID 56FEEE2C-2E65-40CA-B9BE-11962482CC9D, small LPT model
ubi1 warning: ubi_io_read: error -74 (ECC error) while reading 512 bytes from PEB 709:512, read only 512 bytes, retry
ubi1 warning: ubi_io_read: error -74 (ECC error) while reading 512 bytes from PEB 709:512, read only 512 bytes, retry
ubi1 error: ubi_io_read: error -74 (ECC error) while reading 512 bytes from PEB 709:512, read 512 bytes
CPU: 0 PID: 720 Comm: ubi_bgt1d Not tainted 4.6.0-xilinx-gff8137b-dirty #25
Hardware name: Xilinx Zynq Platform
[] (unwind_backtrace) from [] (show_stack+0x10/0x14)
[] (show_stack) from [] (dump_stack+0x84/0xa4)
[] (dump_stack) from [] (ubi_io_read+0x1d4/0x2a8)
[] (ubi_io_read) from [] (ubi_io_read_vid_hdr+0x6c/0x1d8)
[] (ubi_io_read_vid_hdr) from [] (ubi_eba_copy_leb+0x294/0x468)
[] (ubi_eba_copy_leb) from [] (wear_leveling_worker+0x248/0x6a0)
[] (wear_leveling_worker) from [] (do_work+0xcc/0x100)
[] (do_work) from [] (ubi_thread+0x100/0x190)
[] (ubi_thread) from [] (kthread+0xdc/0xf0)
[] (kthread) from [] (ret_from_fork+0x14/0x3c)
ubi1: run torture test for PEB 709
ubi1: PEB 709 passed torture test, do not mark it as bad
ubi1 warning: ubi_io_read: error -74 (ECC error) while reading 512 bytes from PEB 713:512, read only 512 bytes, retry
ubi1 warning: ubi_io_read: error -74 (ECC error) while reading 512 bytes from PEB 713:512, read only 512 bytes, retry
ubi1 warning: ubi_io_read: error -74 (ECC error) while reading 512 bytes from PEB 713:512, read only 512 bytes, retry
ubi1 error: ubi_io_read: error -74 (ECC error) while reading 512 bytes from PEB 713:512, read 512 bytes
CPU: 0 PID: 720 Comm: ubi_bgt1d Not tainted 4.6.0-xilinx-gff8137b-dirty #25
Hardware name: Xilinx Zynq Platform
[] (unwind_backtrace) from [] (show_stack+0x10/0x14)
[] (show_stack) from [] (dump_stack+0x84/0xa4)
[] (dump_stack) from [] (ubi_io_read+0x1d4/0x2a8)
[] (ubi_io_read) from [] (ubi_io_read_vid_hdr+0x6c/0x1d8)
[] (ubi_io_read_vid_hdr) from [] (wear_leveling_worker+0x1e0/0x6a0)
[] (wear_leveling_worker) from [] (do_work+0xcc/0x100)
[] (do_work) from [] (ubi_thread+0x100/0x190)
[] (ubi_thread) from [] (kthread+0xdc/0xf0)
[] (kthread) from [] (ret_from_fork+0x14/0x3c)
IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
ubi1 warning: ubi_io_read: error -74 (ECC error) while reading 512 bytes from PEB 709:512, read only 512 bytes, retry
ubi1 warning: ubi_io_read: error -74 (ECC error) while reading 512 bytes from PEB 709:512, read only 512 bytes, retry
IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
ubi1 warning: ubi_io_read: error -74 (ECC error) while reading 512 bytes from PEB 709:512, read only 512 bytes, retry
ubi1 error: ubi_io_read: error -74 (ECC error) while reading 512 bytes from PEB 709:512, read 512 bytes
CPU: 0 PID: 720 Comm: ubi_bgt1d Not tainted 4.6.0-xilinx-gff8137b-dirty #25
Hardware name: Xilinx Zynq Platform
[] (unwind_backtrace) from [] (show_stack+0x10/0x14)
[] (show_stack) from [] (dump_stack+0x84/0xa4)
[] (dump_stack) from [] (ubi_io_read+0x1d4/0x2a8)
[] (ubi_io_read) from [] (ubi_io_read_vid_hdr+0x6c/0x1d8)
[] (ubi_io_read_vid_hdr) from [] (ubi_eba_copy_leb+0x294/0x468)
[] (ubi_eba_copy_leb) from [] (wear_leveling_worker+0x248/0x6a0)
[] (wear_leveling_worker) from [] (do_work+0xcc/0x100)
[] (do_work) from [] (ubi_thread+0x100/0x190)
[] (ubi_thread) from [] (kthread+0xdc/0xf0)
[] (kthread) from [] (ret_from_fork+0x14/0x3c)
ubi1: run torture test for PEB 709
macb e000b000.ethernet eth0: unable to generate target frequency: 25000000 Hz
macb e000b000.ethernet eth0: link up (100/Full)
IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
ubi1: PEB 709 passed torture test, do not mark it as bad
ubi1 warning: ubi_io_read: error -74 (ECC error) while reading 512 bytes from PEB 713:512, read only 512 bytes, retry
ubi1 warning: ubi_io_read: error -74 (ECC error) while reading 512 bytes from PEB 713:512, read only 512 bytes, retry
ubi1 warning: ubi_io_read: error -74 (ECC error) while reading 512 bytes from PEB 713:512, read only 512 bytes, retry
ubi1 error: ubi_io_read: error -74 (ECC error) while reading 512 bytes from PEB 713:512, read 512 bytes
CPU: 0 PID: 720 Comm: ubi_bgt1d Not tainted 4.6.0-xilinx-gff8137b-dirty #25
Hardware name: Xilinx Zynq Platform
[] (unwind_backtrace) from [] (show_stack+0x10/0x14)
[] (show_stack) from [] (dump_stack+0x84/0xa4)
[] (dump_stack) from [] (ubi_io_read+0x1d4/0x2a8)
[] (ubi_io_read) from [] (ubi_io_read_vid_hdr+0x6c/0x1d8)
[] (ubi_io_read_vid_hdr) from [] (wear_leveling_worker+0x1e0/0x6a0)
[] (wear_leveling_worker) from [] (do_work+0xcc/0x100)
[] (do_work) from [] (ubi_thread+0x100/0x190)
[] (ubi_thread) from [] (kthread+0xdc/0xf0)
[] (kthread) from [] (ret_from_fork+0x14/0x3c)
ubi1: scrubbed PEB 713 (LEB 0:230), data moved to PEB 709
In axi fpga driver!
request_mem_region OK!
AXI fpga dev virtual address is 0xcfb5c000
*base_vir_addr = 0xb023
In fpga mem driver!
request_mem_region OK!
fpga mem virtual address is 0xd2000000
random: nonblocking pool is initialized
2021-08-23 07:50:27:thread.c:1555:create_bitmain_soc_init_thread: create thread
2021-08-23 07:50:27:driver-btm-api.c:682:init_freq_mode: This is scan-user version
2021-08-23 07:50:27:driver-btm-api.c:2518:bitmain_soc_init: Miner compile time: Fri Jan 8 22:35:06 CST 2021 type: Antminer T17e
2021-08-23 07:50:27:driver-btm-api.c:2519:bitmain_soc_init: commit version: 37668c9 2021-01-08 18:20:11, build by: jenkins 2021-01-08 22:39:58
2021-08-23 07:50:27:driver-btm-api.c:2520:bitmain_soc_init: opt_multi_version = 1
2021-08-23 07:50:27:driver-btm-api.c:2521:bitmain_soc_init: opt_bitmain_ab = 1
2021-08-23 07:50:27:driver-btm-api.c:2522:bitmain_soc_init: mid_auto_gen = 0
2021-08-23 07:50:27:driver-btm-api.c:2523:bitmain_soc_init: work_mode = 0
2021-08-23 07:50:27:driver-btm-api.c:2524:bitmain_soc_init: power_feedback_en = true
2021-08-23 07:50:27:driver-btm-api.c:2067:show_sn: no SN got, please write SN to /config/sn
2021-08-23 07:50:27:driver-btm-api.c:1384:miner_device_init: Detect 256MB control board of XILINX
2021-08-23 07:50:27:driver-btm-api.c:1325:init_fan_parameter: fan_eft : 0 fan_pwm : 0
2021-08-23 07:50:33:driver-btm-api.c:1309:init_miner_version: miner ID : 8044e50618c08854
2021-08-23 07:50:33:driver-btm-api.c:1315:init_miner_version: FPGA Version = 0xB023
2021-08-23 07:50:39:auto_adapt.c:100:_get_board_info: chain[0] board bin: 1, chip bin: 3, chip ft: A4V4, chip version: AB
2021-08-23 07:50:39:auto_adapt.c:100:_get_board_info: chain[1] board bin: 1, chip bin: 3, chip ft: A4V4, chip version: AB
2021-08-23 07:50:39:auto_adapt.c:100:_get_board_info: chain[2] board bin: 1, chip bin: 3, chip ft: A4V4, chip version: AB
2021-08-23 07:50:39:driver-btm-api.c:2164:get_calibration_voltage: calibration voltage flag is error data.
2021-08-23 07:50:39 voltage[0] = 1840
2021-08-23 07:50:39 voltage[1] = 1840
2021-08-23 07:50:39 voltage[2] = 1840
2021-08-23 07:50:39:auto_adapt.c:273:is_sweep_failed_before: open sweep tag failed
voltage_ref = 1840
2100 2100 2100 2100 2100 2100
2100 2100 2100 2100 2100 2100
2100 2100 2100 2100 2100 2100
2100 2100 2100 2100 2100 2060
2100 2100 2100 2100 2070 2020
2070 2060 2060 2050 2020 1970
2020 2010 2010 2000 1980 1920
1980 1970 1960 1950 1910 1860
1980 1970 1960 1950 1910 1860
2021-08-23 07:50:39:thread.c:1523:create_read_nonce_reg_thread: create thread
2021-08-23 07:50:39:driver-btm-api.c:698:dump_pcb_bom_version: Chain [0] PCB Version: 0x010a
2021-08-23 07:50:39:driver-btm-api.c:699:dump_pcb_bom_version: Chain [0] BOM Version: 0x0100
2021-08-23 07:50:39:driver-btm-api.c:698:dump_pcb_bom_version: Chain [1] PCB Version: 0x010a
2021-08-23 07:50:39:driver-btm-api.c:699:dump_pcb_bom_version: Chain [1] BOM Version: 0x0100
2021-08-23 07:50:39:driver-btm-api.c:698:dump_pcb_bom_version: Chain [2] PCB Version: 0x010a
2021-08-23 07:50:39:driver-btm-api.c:699:dump_pcb_bom_version: Chain [2] BOM Version: 0x0100
2021-08-23 07:50:45:driver-btm-api.c:2344:bitmain_board_init: Fan check passed.
2021-08-23 07:50:46:board.c:81:jump_and_app_check_restore_pic: chain[0] PIC jump to app
2021-08-23 07:50:49:board.c:94:jump_and_app_check_restore_pic: Check chain[0] PIC fw version=0x88
2021-08-23 07:50:50:board.c:81:jump_and_app_check_restore_pic: chain[1] PIC jump to app
2021-08-23 07:50:52:board.c:94:jump_and_app_check_restore_pic: Check chain[1] PIC fw version=0x88
2021-08-23 07:50:53:board.c:81:jump_and_app_check_restore_pic: chain[2] PIC jump to app
2021-08-23 07:50:55:board.c:94:jump_and_app_check_restore_pic: Check chain[2] PIC fw version=0x88
2021-08-23 07:50:55:thread.c:1518:create_pic_heart_beat_thread: create thread
2021-08-23 07:50:56:power_api.c:241:power_init: power type version: 0x0042
2021-08-23 07:50:58:power_api.c:259:power_init: Power init:
2021-08-23 07:50:58:power_api.c:260:power_init: current_voltage_raw = 2136
2021-08-23 07:50:58:power_api.c:261:power_init: highest_voltage_raw = 2000
2021-08-23 07:50:58:power_api.c:262:power_init: working_voltage_raw = 1800
2021-08-23 07:50:58:power_api.c:263:power_init: higher_voltage_raw = 1850
2021-08-23 07:50:58:power_api.c:264:power_init: check_asic_voltage_raw = 1800
2021-08-23 07:50:58:driver-btm-api.c:2354:bitmain_board_init: Enter 60s sleep to make sure power release finish.
2021-08-23 07:52:00:driver-btm-api.c:1123:check_asic_number_until_volt_balance: THIS is No.1 time boost asic:
2021-08-23 07:52:00:power_api.c:334:modify_check_asic_voltage: check_asic_voltage_raw = 1800
2021-08-23 07:52:03:power_api.c:298:set_to_check_asic_voltage_by_steps: Set to voltage raw 1800, step by step.
2021-08-23 07:52:18:power_api.c:89:check_voltage: chain[0] target_vol = 18.00, actural_vol = 24.89, more than 1.0v diff.
2021-08-23 07:52:22:power_api.c:89:check_voltage: chain[0] target_vol = 18.00, actural_vol = 24.89, more than 1.0v diff.
2021-08-23 07:52:26:power_api.c:89:check_voltage: chain[0] target_vol = 18.00, actural_vol = 24.89, more than 1.0v diff.
2021-08-23 07:52:31:power_api.c:89:check_voltage: chain[0] target_vol = 18.00, actural_vol = 24.89, more than 1.0v diff.
2021-08-23 07:52:35:power_api.c:89:check_voltage: chain[0] target_vol = 18.00, actural_vol = 24.89, more than 1.0v diff.
2021-08-23 07:52:39:power_api.c:89:check_voltage: chain[0] target_vol = 18.00, actural_vol = 24.89, more than 1.0v diff.
2021-08-23 07:52:44:power_api.c:89:check_voltage: chain[0] target_vol = 18.00, actural_vol = 24.86, more than 1.0v diff.
2021-08-23 07:52:48:power_api.c:89:check_voltage: chain[0] target_vol = 18.00, actural_vol = 24.89, more than 1.0v diff.
2021-08-23 07:52:52:power_api.c:89:check_voltage: chain[0] target_vol = 18.00, actural_vol = 24.89, more than 1.0v diff.
2021-08-23 07:52:56:power_api.c:89:check_voltage: chain[0] target_vol = 18.00, actural_vol = 24.89, more than 1.0v diff.
2021-08-23 07:53:01:power_api.c:89:check_voltage: chain[0] target_vol = 18.00, actural_vol = 24.89, more than 1.0v diff.
2021-08-23 07:53:05:power_api.c:89:check_voltage: chain[0] target_vol = 18.00, actural_vol = 24.89, more than 1.0v diff.
2021-08-23 07:53:09:power_api.c:89:check_voltage: chain[0] target_vol = 18.00, actural_vol = 24.89, more than 1.0v diff.
2021-08-23 07:53:14:power_api.c:89:check_voltage: chain[0] target_vol = 18.00, actural_vol = 24.89, more than 1.0v diff.
2021-08-23 07:53:18:power_api.c:89:check_voltage: chain[0] target_vol = 18.00, actural_vol = 24.89, more than 1.0v diff.
2021-08-23 07:53:22:power_api.c:89:check_voltage: chain[0] target_vol = 18.00, actural_vol = 24.89, more than 1.0v diff.
2021-08-23 07:53:27:power_api.c:89:check_voltage: chain[0] target_vol = 18.00, actural_vol = 24.89, more than 1.0v diff.
2021-08-23 07:53:31:power_api.c:89:check_voltage: chain[0] target_vol = 18.00, actural_vol = 24.89, more than 1.0v diff.
2021-08-23 07:53:35:power_api.c:89:check_voltage: chain[0] target_vol = 18.00, actural_vol = 24.89, more than 1.0v diff.
2021-08-23 07:53:39:power_api.c:89:check_voltage: chain[0] target_vol = 18.00, actural_vol = 24.89, more than 1.0v diff.
2021-08-23 07:53:44:power_api.c:89:check_voltage: chain[0] target_vol = 18.00, actural_vol = 24.89, more than 1.0v diff.
2021-08-23 07:53:48:power_api.c:89:check_voltage: chain[0] target_vol = 18.00, actural_vol = 24.89, more than 1.0v diff.
2021-08-23 07:53:52:power_api.c:89:check_voltage: chain[0] target_vol = 18.00, actural_vol = 24.89, more than 1.0v diff.
2021-08-23 07:53:57:power_api.c:89:check_voltage: chain[0] target_vol = 18.00, actural_vol = 24.86, more than 1.0v diff.
2021-08-23 07:54:01:power_api.c:89:check_voltage: chain[0] target_vol = 18.00, actural_vol = 24.89, more than 1.0v diff.
2021-08-23 07:54:05:power_api.c:89:check_voltage: chain[0] target_vol = 18.00, actural_vol = 24.89, more than 1.0v diff.
2021-08-23 07:54:09:power_api.c:89:check_voltage: chain[0] target_vol = 18.00, actural_vol = 24.89, more than 1.0v diff.
2021-08-23 07:54:14:power_api.c:89:check_voltage: chain[0] target_vol = 18.00, actural_vol = 24.89, more than 1.0v diff.
2021-08-23 07:54:18:power_api.c:89:check_voltage: chain[0] target_vol = 18.00, actural_vol = 24.89, more than 1.0v diff.
2021-08-23 07:54:22:power_api.c:89:check_voltage: chain[0] target_vol = 18.00, actural_vol = 24.89, more than 1.0v diff.
2021-08-23 07:54:26:sweep_err.c:59:sweep_error_code_save2file: file /config/sweep_error_code already exists, do not overwrite it
2021-08-23 07:54:26:sweep_err.c:185:sweep_set_error_code: Sweep error string = V:1.
2021-08-23 07:54:26:driver-btm-api.c:247:set_miner_status: ERROR_POWER_LOST
2021-08-23 07:54:26:driver-btm-api.c:176:stop_mining: stop mining: power set failed!
2021-08-23 07:54:26:thread.c:1595:cancel_read_nonce_reg_thread: cancel thread
2021-08-23 07:54:26:driver-btm-api.c:147:killall_hashboard: ****power off hashboard****
can: controller area network core (rev 20120528 abi 9)
NET: Registered protocol family 29
can: raw protocol (rev 20120528)
can: broadcast manager protocol (rev 20120528 t)
can: netlink gateway (rev 20130117) max_hops=1
zynq_pm_ioremap: no compatible node found for 'xlnx,zynq-ddrc-a05'
zynq_pm_late_init: Unable to map DDRC IO memory.
Registering SWP/SWPB emulation handler
hctosys: unable to open rtc device (rtc0)
ALSA device list:
No soundcards found.
RAMDISK: gzip image found at block 0
EXT4-fs (ram0): couldn't mount as ext3 due to feature incompatibilities
EXT4-fs (ram0): mounted filesystem without journal. Opts: (null)
VFS: Mounted root (ext4 filesystem) on device 1:0.
devtmpfs: mounted
Freeing unused kernel memory: 1024K (c0a00000 - c0b00000)
EXT4-fs (ram0): re-mounted. Opts: block_validity,delalloc,barrier,user_xattr
random: dd urandom read with 0 bits of entropy available
ubi0: attaching mtd2
ubi0: scanning is finished
ubi0: attached mtd2 (name "configs", size 8 MiB)
ubi0: PEB size: 131072 bytes (128 KiB), LEB size: 129024 bytes
ubi0: min./max. I/O unit sizes: 2048/2048, sub-page size 512
ubi0: VID header offset: 512 (aligned 512), data offset: 2048
ubi0: good PEBs: 64, bad PEBs: 0, corrupted PEBs: 0
ubi0: user volume: 1, internal volumes: 1, max. volumes count: 128
ubi0: max/mean erase counter: 6/2, WL threshold: 4096, image sequence number: 614353782
ubi0: available PEBs: 0, total reserved PEBs: 64, PEBs reserved for bad PEB handling: 40
ubi0: background thread "ubi_bgt0d" started, PID 708
UBIFS (ubi0:0): background thread "ubifs_bgt0_0" started, PID 711
UBIFS (ubi0:0): recovery needed
UBIFS (ubi0:0): recovery completed
UBIFS (ubi0:0): UBIFS: mounted UBI device 0, volume 0, name "configs"
UBIFS (ubi0:0): LEB size: 129024 bytes (126 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
UBIFS (ubi0:0): FS size: 1419264 bytes (1 MiB, 11 LEBs), journal size 903169 bytes (0 MiB, 5 LEBs)
UBIFS (ubi0:0): reserved for root: 67035 bytes (65 KiB)
UBIFS (ubi0:0): media format: w4/r0 (latest is w4/r0), UUID 70BCC183-B57C-4138-BB2B-76F5CD328150, small LPT model
ubi1: attaching mtd5
ubi1 warning: ubi_io_read: error -74 (ECC error) while reading 64 bytes from PEB 713:0, read only 64 bytes, retry
ubi1 warning: ubi_io_read: error -74 (ECC error) while reading 64 bytes from PEB 713:0, read only 64 bytes, retry
ubi1 warning: ubi_io_read: error -74 (ECC error) while reading 64 bytes from PEB 713:0, read only 64 bytes, retry
ubi1 error: ubi_io_read: error -74 (ECC error) while reading 64 bytes from PEB 713:0, read 64 bytes
CPU: 0 PID: 717 Comm: ubiattach Not tainted 4.6.0-xilinx-gff8137b-dirty #25
Hardware name: Xilinx Zynq Platform
[
[
[
[
[
[
[
[
[
[
[
ubi1 warning: ubi_io_read: error -74 (ECC error) while reading 512 bytes from PEB 713:512, read only 512 bytes, retry
ubi1 warning: ubi_io_read: error -74 (ECC error) while reading 512 bytes from PEB 713:512, read only 512 bytes, retry
ubi1 warning: ubi_io_read: error -74 (ECC error) while reading 512 bytes from PEB 713:512, read only 512 bytes, retry
ubi1 error: ubi_io_read: error -74 (ECC error) while reading 512 bytes from PEB 713:512, read 512 bytes
CPU: 0 PID: 717 Comm: ubiattach Not tainted 4.6.0-xilinx-gff8137b-dirty #25
Hardware name: Xilinx Zynq Platform
[
[
[
[
[
[
[
[
[
[
[
ubi1: scanning is finished
ubi1: attached mtd5 (name "reserve1", size 128 MiB)
ubi1: PEB size: 131072 bytes (128 KiB), LEB size: 129024 bytes
ubi1: min./max. I/O unit sizes: 2048/2048, sub-page size 512
ubi1: VID header offset: 512 (aligned 512), data offset: 2048
ubi1: good PEBs: 1019, bad PEBs: 5, corrupted PEBs: 0
ubi1: user volume: 1, internal volumes: 1, max. volumes count: 128
ubi1: max/mean erase counter: 2/0, WL threshold: 4096, image sequence number: 1313025816
ubi1: available PEBs: 0, total reserved PEBs: 1019, PEBs reserved for bad PEB handling: 35
ubi1: background thread "ubi_bgt1d" started, PID 720
ubi1 warning: ubi_io_read: error -74 (ECC error) while reading 512 bytes from PEB 713:512, read only 512 bytes, retry
UBIFS (ubi1:0): background thread "ubifs_bgt1_0" started, PID 723
ubi1 warning: ubi_io_read: error -74 (ECC error) while reading 512 bytes from PEB 713:512, read only 512 bytes, retry
UBIFS (ubi1:0): recovery needed
ubi1 warning: ubi_io_read: error -74 (ECC error) while reading 512 bytes from PEB 713:512, read only 512 bytes, retry
ubi1 error: ubi_io_read: error -74 (ECC error) while reading 512 bytes from PEB 713:512, read 512 bytes
CPU: 0 PID: 720 Comm: ubi_bgt1d Not tainted 4.6.0-xilinx-gff8137b-dirty #25
Hardware name: Xilinx Zynq Platform
[
[
[
[
[
[
[
[
[
ubi1 warning: ubi_io_read: error -74 (ECC error) while reading 512 bytes from PEB 709:512, read only 512 bytes, retry
UBIFS (ubi1:0): recovery completed
UBIFS (ubi1:0): UBIFS: mounted UBI device 1, volume 0, name "reserve1"
UBIFS (ubi1:0): LEB size: 129024 bytes (126 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
UBIFS (ubi1:0): FS size: 125024256 bytes (119 MiB, 969 LEBs), journal size 6322176 bytes (6 MiB, 49 LEBs)
UBIFS (ubi1:0): reserved for root: 4952683 bytes (4836 KiB)
UBIFS (ubi1:0): media format: w4/r0 (latest is w4/r0), UUID 56FEEE2C-2E65-40CA-B9BE-11962482CC9D, small LPT model
ubi1 warning: ubi_io_read: error -74 (ECC error) while reading 512 bytes from PEB 709:512, read only 512 bytes, retry
ubi1 warning: ubi_io_read: error -74 (ECC error) while reading 512 bytes from PEB 709:512, read only 512 bytes, retry
ubi1 error: ubi_io_read: error -74 (ECC error) while reading 512 bytes from PEB 709:512, read 512 bytes
CPU: 0 PID: 720 Comm: ubi_bgt1d Not tainted 4.6.0-xilinx-gff8137b-dirty #25
Hardware name: Xilinx Zynq Platform
[
[
[
[
[
[
[
[
[
[
ubi1: run torture test for PEB 709
ubi1: PEB 709 passed torture test, do not mark it as bad
ubi1 warning: ubi_io_read: error -74 (ECC error) while reading 512 bytes from PEB 713:512, read only 512 bytes, retry
ubi1 warning: ubi_io_read: error -74 (ECC error) while reading 512 bytes from PEB 713:512, read only 512 bytes, retry
ubi1 warning: ubi_io_read: error -74 (ECC error) while reading 512 bytes from PEB 713:512, read only 512 bytes, retry
ubi1 error: ubi_io_read: error -74 (ECC error) while reading 512 bytes from PEB 713:512, read 512 bytes
CPU: 0 PID: 720 Comm: ubi_bgt1d Not tainted 4.6.0-xilinx-gff8137b-dirty #25
Hardware name: Xilinx Zynq Platform
[
[
[
[
[
[
[
[
[
IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
ubi1 warning: ubi_io_read: error -74 (ECC error) while reading 512 bytes from PEB 709:512, read only 512 bytes, retry
ubi1 warning: ubi_io_read: error -74 (ECC error) while reading 512 bytes from PEB 709:512, read only 512 bytes, retry
IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
ubi1 warning: ubi_io_read: error -74 (ECC error) while reading 512 bytes from PEB 709:512, read only 512 bytes, retry
ubi1 error: ubi_io_read: error -74 (ECC error) while reading 512 bytes from PEB 709:512, read 512 bytes
CPU: 0 PID: 720 Comm: ubi_bgt1d Not tainted 4.6.0-xilinx-gff8137b-dirty #25
Hardware name: Xilinx Zynq Platform
[
[
[
[
[
[
[
[
[
[
ubi1: run torture test for PEB 709
macb e000b000.ethernet eth0: unable to generate target frequency: 25000000 Hz
macb e000b000.ethernet eth0: link up (100/Full)
IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
ubi1: PEB 709 passed torture test, do not mark it as bad
ubi1 warning: ubi_io_read: error -74 (ECC error) while reading 512 bytes from PEB 713:512, read only 512 bytes, retry
ubi1 warning: ubi_io_read: error -74 (ECC error) while reading 512 bytes from PEB 713:512, read only 512 bytes, retry
ubi1 warning: ubi_io_read: error -74 (ECC error) while reading 512 bytes from PEB 713:512, read only 512 bytes, retry
ubi1 error: ubi_io_read: error -74 (ECC error) while reading 512 bytes from PEB 713:512, read 512 bytes
CPU: 0 PID: 720 Comm: ubi_bgt1d Not tainted 4.6.0-xilinx-gff8137b-dirty #25
Hardware name: Xilinx Zynq Platform
[
[
[
[
[
[
[
[
[
ubi1: scrubbed PEB 713 (LEB 0:230), data moved to PEB 709
In axi fpga driver!
request_mem_region OK!
AXI fpga dev virtual address is 0xcfb5c000
*base_vir_addr = 0xb023
In fpga mem driver!
request_mem_region OK!
fpga mem virtual address is 0xd2000000
random: nonblocking pool is initialized
2021-08-23 07:50:27:thread.c:1555:create_bitmain_soc_init_thread: create thread
2021-08-23 07:50:27:driver-btm-api.c:682:init_freq_mode: This is scan-user version
2021-08-23 07:50:27:driver-btm-api.c:2518:bitmain_soc_init: Miner compile time: Fri Jan 8 22:35:06 CST 2021 type: Antminer T17e
2021-08-23 07:50:27:driver-btm-api.c:2519:bitmain_soc_init: commit version: 37668c9 2021-01-08 18:20:11, build by: jenkins 2021-01-08 22:39:58
2021-08-23 07:50:27:driver-btm-api.c:2520:bitmain_soc_init: opt_multi_version = 1
2021-08-23 07:50:27:driver-btm-api.c:2521:bitmain_soc_init: opt_bitmain_ab = 1
2021-08-23 07:50:27:driver-btm-api.c:2522:bitmain_soc_init: mid_auto_gen = 0
2021-08-23 07:50:27:driver-btm-api.c:2523:bitmain_soc_init: work_mode = 0
2021-08-23 07:50:27:driver-btm-api.c:2524:bitmain_soc_init: power_feedback_en = true
2021-08-23 07:50:27:driver-btm-api.c:2067:show_sn: no SN got, please write SN to /config/sn
2021-08-23 07:50:27:driver-btm-api.c:1384:miner_device_init: Detect 256MB control board of XILINX
2021-08-23 07:50:27:driver-btm-api.c:1325:init_fan_parameter: fan_eft : 0 fan_pwm : 0
2021-08-23 07:50:33:driver-btm-api.c:1309:init_miner_version: miner ID : 8044e50618c08854
2021-08-23 07:50:33:driver-btm-api.c:1315:init_miner_version: FPGA Version = 0xB023
2021-08-23 07:50:39:auto_adapt.c:100:_get_board_info: chain[0] board bin: 1, chip bin: 3, chip ft: A4V4, chip version: AB
2021-08-23 07:50:39:auto_adapt.c:100:_get_board_info: chain[1] board bin: 1, chip bin: 3, chip ft: A4V4, chip version: AB
2021-08-23 07:50:39:auto_adapt.c:100:_get_board_info: chain[2] board bin: 1, chip bin: 3, chip ft: A4V4, chip version: AB
2021-08-23 07:50:39:driver-btm-api.c:2164:get_calibration_voltage: calibration voltage flag is error data.
2021-08-23 07:50:39 voltage[0] = 1840
2021-08-23 07:50:39 voltage[1] = 1840
2021-08-23 07:50:39 voltage[2] = 1840
2021-08-23 07:50:39:auto_adapt.c:273:is_sweep_failed_before: open sweep tag failed
voltage_ref = 1840
2100 2100 2100 2100 2100 2100
2100 2100 2100 2100 2100 2100
2100 2100 2100 2100 2100 2100
2100 2100 2100 2100 2100 2060
2100 2100 2100 2100 2070 2020
2070 2060 2060 2050 2020 1970
2020 2010 2010 2000 1980 1920
1980 1970 1960 1950 1910 1860
1980 1970 1960 1950 1910 1860
2021-08-23 07:50:39:thread.c:1523:create_read_nonce_reg_thread: create thread
2021-08-23 07:50:39:driver-btm-api.c:698:dump_pcb_bom_version: Chain [0] PCB Version: 0x010a
2021-08-23 07:50:39:driver-btm-api.c:699:dump_pcb_bom_version: Chain [0] BOM Version: 0x0100
2021-08-23 07:50:39:driver-btm-api.c:698:dump_pcb_bom_version: Chain [1] PCB Version: 0x010a
2021-08-23 07:50:39:driver-btm-api.c:699:dump_pcb_bom_version: Chain [1] BOM Version: 0x0100
2021-08-23 07:50:39:driver-btm-api.c:698:dump_pcb_bom_version: Chain [2] PCB Version: 0x010a
2021-08-23 07:50:39:driver-btm-api.c:699:dump_pcb_bom_version: Chain [2] BOM Version: 0x0100
2021-08-23 07:50:45:driver-btm-api.c:2344:bitmain_board_init: Fan check passed.
2021-08-23 07:50:46:board.c:81:jump_and_app_check_restore_pic: chain[0] PIC jump to app
2021-08-23 07:50:49:board.c:94:jump_and_app_check_restore_pic: Check chain[0] PIC fw version=0x88
2021-08-23 07:50:50:board.c:81:jump_and_app_check_restore_pic: chain[1] PIC jump to app
2021-08-23 07:50:52:board.c:94:jump_and_app_check_restore_pic: Check chain[1] PIC fw version=0x88
2021-08-23 07:50:53:board.c:81:jump_and_app_check_restore_pic: chain[2] PIC jump to app
2021-08-23 07:50:55:board.c:94:jump_and_app_check_restore_pic: Check chain[2] PIC fw version=0x88
2021-08-23 07:50:55:thread.c:1518:create_pic_heart_beat_thread: create thread
2021-08-23 07:50:56:power_api.c:241:power_init: power type version: 0x0042
2021-08-23 07:50:58:power_api.c:259:power_init: Power init:
2021-08-23 07:50:58:power_api.c:260:power_init: current_voltage_raw = 2136
2021-08-23 07:50:58:power_api.c:261:power_init: highest_voltage_raw = 2000
2021-08-23 07:50:58:power_api.c:262:power_init: working_voltage_raw = 1800
2021-08-23 07:50:58:power_api.c:263:power_init: higher_voltage_raw = 1850
2021-08-23 07:50:58:power_api.c:264:power_init: check_asic_voltage_raw = 1800
2021-08-23 07:50:58:driver-btm-api.c:2354:bitmain_board_init: Enter 60s sleep to make sure power release finish.
2021-08-23 07:52:00:driver-btm-api.c:1123:check_asic_number_until_volt_balance: THIS is No.1 time boost asic:
2021-08-23 07:52:00:power_api.c:334:modify_check_asic_voltage: check_asic_voltage_raw = 1800
2021-08-23 07:52:03:power_api.c:298:set_to_check_asic_voltage_by_steps: Set to voltage raw 1800, step by step.
2021-08-23 07:52:18:power_api.c:89:check_voltage: chain[0] target_vol = 18.00, actural_vol = 24.89, more than 1.0v diff.
2021-08-23 07:52:22:power_api.c:89:check_voltage: chain[0] target_vol = 18.00, actural_vol = 24.89, more than 1.0v diff.
2021-08-23 07:52:26:power_api.c:89:check_voltage: chain[0] target_vol = 18.00, actural_vol = 24.89, more than 1.0v diff.
2021-08-23 07:52:31:power_api.c:89:check_voltage: chain[0] target_vol = 18.00, actural_vol = 24.89, more than 1.0v diff.
2021-08-23 07:52:35:power_api.c:89:check_voltage: chain[0] target_vol = 18.00, actural_vol = 24.89, more than 1.0v diff.
2021-08-23 07:52:39:power_api.c:89:check_voltage: chain[0] target_vol = 18.00, actural_vol = 24.89, more than 1.0v diff.
2021-08-23 07:52:44:power_api.c:89:check_voltage: chain[0] target_vol = 18.00, actural_vol = 24.86, more than 1.0v diff.
2021-08-23 07:52:48:power_api.c:89:check_voltage: chain[0] target_vol = 18.00, actural_vol = 24.89, more than 1.0v diff.
2021-08-23 07:52:52:power_api.c:89:check_voltage: chain[0] target_vol = 18.00, actural_vol = 24.89, more than 1.0v diff.
2021-08-23 07:52:56:power_api.c:89:check_voltage: chain[0] target_vol = 18.00, actural_vol = 24.89, more than 1.0v diff.
2021-08-23 07:53:01:power_api.c:89:check_voltage: chain[0] target_vol = 18.00, actural_vol = 24.89, more than 1.0v diff.
2021-08-23 07:53:05:power_api.c:89:check_voltage: chain[0] target_vol = 18.00, actural_vol = 24.89, more than 1.0v diff.
2021-08-23 07:53:09:power_api.c:89:check_voltage: chain[0] target_vol = 18.00, actural_vol = 24.89, more than 1.0v diff.
2021-08-23 07:53:14:power_api.c:89:check_voltage: chain[0] target_vol = 18.00, actural_vol = 24.89, more than 1.0v diff.
2021-08-23 07:53:18:power_api.c:89:check_voltage: chain[0] target_vol = 18.00, actural_vol = 24.89, more than 1.0v diff.
2021-08-23 07:53:22:power_api.c:89:check_voltage: chain[0] target_vol = 18.00, actural_vol = 24.89, more than 1.0v diff.
2021-08-23 07:53:27:power_api.c:89:check_voltage: chain[0] target_vol = 18.00, actural_vol = 24.89, more than 1.0v diff.
2021-08-23 07:53:31:power_api.c:89:check_voltage: chain[0] target_vol = 18.00, actural_vol = 24.89, more than 1.0v diff.
2021-08-23 07:53:35:power_api.c:89:check_voltage: chain[0] target_vol = 18.00, actural_vol = 24.89, more than 1.0v diff.
2021-08-23 07:53:39:power_api.c:89:check_voltage: chain[0] target_vol = 18.00, actural_vol = 24.89, more than 1.0v diff.
2021-08-23 07:53:44:power_api.c:89:check_voltage: chain[0] target_vol = 18.00, actural_vol = 24.89, more than 1.0v diff.
2021-08-23 07:53:48:power_api.c:89:check_voltage: chain[0] target_vol = 18.00, actural_vol = 24.89, more than 1.0v diff.
2021-08-23 07:53:52:power_api.c:89:check_voltage: chain[0] target_vol = 18.00, actural_vol = 24.89, more than 1.0v diff.
2021-08-23 07:53:57:power_api.c:89:check_voltage: chain[0] target_vol = 18.00, actural_vol = 24.86, more than 1.0v diff.
2021-08-23 07:54:01:power_api.c:89:check_voltage: chain[0] target_vol = 18.00, actural_vol = 24.89, more than 1.0v diff.
2021-08-23 07:54:05:power_api.c:89:check_voltage: chain[0] target_vol = 18.00, actural_vol = 24.89, more than 1.0v diff.
2021-08-23 07:54:09:power_api.c:89:check_voltage: chain[0] target_vol = 18.00, actural_vol = 24.89, more than 1.0v diff.
2021-08-23 07:54:14:power_api.c:89:check_voltage: chain[0] target_vol = 18.00, actural_vol = 24.89, more than 1.0v diff.
2021-08-23 07:54:18:power_api.c:89:check_voltage: chain[0] target_vol = 18.00, actural_vol = 24.89, more than 1.0v diff.
2021-08-23 07:54:22:power_api.c:89:check_voltage: chain[0] target_vol = 18.00, actural_vol = 24.89, more than 1.0v diff.
2021-08-23 07:54:26:sweep_err.c:59:sweep_error_code_save2file: file /config/sweep_error_code already exists, do not overwrite it
2021-08-23 07:54:26:sweep_err.c:185:sweep_set_error_code: Sweep error string = V:1.
2021-08-23 07:54:26:driver-btm-api.c:247:set_miner_status: ERROR_POWER_LOST
2021-08-23 07:54:26:driver-btm-api.c:176:stop_mining: stop mining: power set failed!
2021-08-23 07:54:26:thread.c:1595:cancel_read_nonce_reg_thread: cancel thread
2021-08-23 07:54:26:driver-btm-api.c:147:killall_hashboard: ****power off hashboard****
Jump to: