Tx1 device boot up with error message and system becomes very slow

Dear Sir,
I had download Jetpack3.2 OS for Tx1 and flash Jetpack3.2 OS on Tx1 device ,it works normal ,but when I get R28.2 source code and build dtb ,then use following cmd to flash dtb file (tegra210-jetson-tx1-p2597-2180-a01-devkit.dtb)

sudo ./flash.sh -k DTB jetson-tx1 mmcblk0p1

after reboot device, device can boot up,but after a while ,it will show error message ,system becomes slow and abnormal.Would you please help to analyze the root cause,Thansk a lot!

nvidia@tegra-ubuntu:~$ [ 9.046130] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 9.121311] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 10.892573] Setting pll_a = 45158400 Hz clk_out = 11289600 Hz
[ 10.937594] Setting pll_a = 45158400 Hz clk_out = 11289600 Hz
[ 10.972629] Setting pll_a = 45158400 Hz clk_out = 11289600 Hz
[ 11.016836] Setting pll_a = 45158400 Hz clk_out = 11289600 Hz
[ 11.029067] Setting pll_a = 45158400 Hz clk_out = 11289600 Hz
[ 11.038854] Setting pll_a = 45158400 Hz clk_out = 11289600 Hz
[ 11.069815] Setting pll_a = 45158400 Hz clk_out = 11289600 Hz
[ 11.078316] Setting pll_a = 45158400 Hz clk_out = 11289600 Hz
[ 11.100396] Setting pll_a = 45158400 Hz clk_out = 11289600 Hz
[ 11.156465] Setting pll_a = 45158400 Hz clk_out = 11289600 Hz
[ 44.456629] bpmp_wait_ack() returned -110 on ch 0
[ 44.461528] mrq 2 data [0x0 0x0 0x0 0x0 0xe 0x0 0x0 0x0 0x11 0x0 0x0 0x0 ]
[ 44.469405] ------------[ cut here ]------------
[ 44.474099] WARNING: at /dvs/git/dirty/git-master_linux/kernel/kernel-4.4/drivers/firmware/tegra/mail.c:357
[ 44.483882] Modules linked in: bcmdhd bluedroid_pm
[ 44.488877]
[ 44.490468] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 4.4.38-tegra #1
[ 44.496961] Hardware name: jetson_tx1 (DT)
[ 44.501128] task: ffffffc0012d5ac0 ti: ffffffc0012c0000 task.ti: ffffffc0012c0000
[ 44.508742] PC is at tegra_bpmp_send_receive_atomic+0xe4/0x138
[ 44.514652] LR is at tegra_bpmp_send_receive_atomic+0xe4/0x138
[ 44.520541] pc : [] lr : [] pstate: 800001c5
[ 44.527977] sp : ffffffc0012c3d50
[ 44.531341] x29: ffffffc0012c3d50 x28: 0000000000000000
[ 44.536798] x27: ffffffc0000801d8 x26: 0000000081528000
[ 44.542248] x25: 00000000ffffff92 x24: 0000000000000002
[ 44.547695] x23: ffffffc0012c3db0 x22: 0000000000000004
[ 44.553138] x21: ffffffc0012c3db8 x20: 000000000000000c
[ 44.558576] x19: 0000000000000000 x18: 0000000000000000
[ 44.564018] x17: 0000000000000000 x16: 0000000000000000
[ 44.569455] x15: 0000000000000000 x14: 0000000000000000
[ 44.574893] x13: 0000000000000000 x12: 0000000000000000
[ 44.580330] x11: 0000000000000000 x10: 0000000000000000
[ 44.585772] x9 : 0000000000000000 x8 : ffffffc0002f061c
[ 44.591212] x7 : 0000000000000000 x6 : 0000000000000002
[ 44.596652] x5 : 0000000000000001 x4 : ffffffc0012c3b30
[ 44.602093] x3 : 0000000000000007 x2 : 0000000000000000
[ 44.607529] x1 : 0000000000000002 x0 : 0000000000000001
[ 44.612965]

I didn’t make any change in dts and other code

You are likely to get much faster and better answers in the TX1 forum next door:

https://devtalk.nvidia.com/default/board/164/jetson-tx1/

Dear Njuffa,
Thanks! After porting Jetpack3.2.1 R28.2 sources, the issue was fixed.