Jump to content
  • 0

SSHD crashes at kernel 5.4.8 by using rsync


Nobby42
 Share

Question

Hi,

when I used rsync to copy several GB of data from the NMV3 to a USB SSD, the SSHD crashed.

 

[96500.101926] ------------[ cut here ]------------

[96500.102376] kernel BUG at arch/arm64/kernel/traps.c:405!

[96500.102858] Internal error: Oops - BUG: 0 [#2] PREEMPT SMP

[96500.103343] Modules linked in: sg uas hci_uart bluetooth cpufreq_userspace zstd zram dw_hdmi_i2s_audio rockchip_rga v4l2_mem2mem videobuf2_dma_sg panfrost fusb302 tcpm videobuf2_memops gpu_sched typec videobuf2_v4l2 videobuf2_common videodev mc brcmfmac brcmutil cfg80211 rfkill rockchipdrm analogix_dp dw_mipi_dsi dw_hdmi ip_tables ipv6 crc_ccitt phy_rockchip_typec phy_rockchip_pcie dwmac_rk stmmac_platform stmmac phylink

[96500.106655] CPU: 3 PID: 14434 Comm: sshd Tainted: G      D W         5.4.8-rockchip64 #19.11.7

[96500.107413] Hardware name: FriendlyElec NanoPi M4 Ver2.0 (DT)

[96500.107921] pstate: 00000005 (nzcv daif -PAN -UAO)

[96500.108354] pc : do_undefinstr+0x2e4/0x310

[96500.108718] lr : do_undefinstr+0x1dc/0x310

[96500.109081] sp : ffff8000130237d0

[96500.109375] x29: ffff8000130237d0 x28: ffff00003a6ae200

[96500.109846] x27: 00000000327efa40 x26: 000057c3dbe99326

[96500.110315] x25: 0000000000000010 x24: 0000000000000000

[96500.110785] x23: 0000000040000005 x22: ffff800010c89364

[96500.111255] x21: ffff800013023970 x20: ffff800013023830

[96500.111724] x19: ffff80001136b508 x18: 0000000000000000

[96500.112194] x17: 0000000000000000 x16: 0000000000000000

[96500.112664] x15: 0000000000000000 x14: 7f6754efac8b8b63

[96500.113133] x13: 64022bac43b4cbe6 x12: 000000000003d440

[96500.113603] x11: 0000000000000074 x10: 0000000000000001

[96500.114073] x9 : 0000000093637393 x8 : 0000000000000000

[96500.114542] x7 : 0000000000000001 x6 : 0000000000000000

[96500.115012] x5 : 00000000d5300000 x4 : ffff800011381370

[96500.115481] x3 : 0000000000000001 x2 : 0000000000000000

[96500.115951] x1 : ffff00003a6ae200 x0 : 0000000040000005

[96500.116422] Call trace:

[96500.116644] do_undefinstr+0x2e4/0x310

[96500.116978] el1_undef+0x10/0x84

[96500.117272] __ip_queue_xmit+0x3c/0x390

[96500.117615] ip_queue_xmit+0x10/0x18

[96500.117937] __tcp_transmit_skb+0x4b0/0xae0

[96500.118310] tcp_write_xmit+0x39c/0x1080

[96500.118659] __tcp_push_pending_frames+0x38/0xc0

[96500.119067] tcp_push+0x114/0x160

[96500.119364] tcp_sendmsg_locked+0xab4/0xbe8

[96500.119735] tcp_sendmsg+0x34/0x58

[96500.120041] inet_sendmsg+0x40/0x68

[96500.120353] sock_write_iter+0x8c/0xe8

[96500.120689] new_sync_write+0x100/0x180

[96500.121028] __vfs_write+0x2c/0x40

[96500.121332] vfs_write+0xb0/0x1d0

[96500.121627] ksys_write+0x64/0xe8

[96500.121923] __arm64_sys_write+0x18/0x20

[96500.122273] el0_svc_common.constprop.1+0x88/0x178

[96500.122699] el0_svc_handler+0x20/0x80

[96500.123032] el0_svc+0x8/0xc

[96500.123293] Code: f9401bf7 17ffff7d a9025bf5 f9001bf7 (d4210000)

[96500.123833] ---[ end trace 4a19b31e1f6dad94 ]---

 

It is a kernel problem?

Link to comment
Share on other sites

7 answers to this question

Recommended Posts

Armbian is a community driven open source project. Do you like to contribute your code?

  • 0

I've seem to have the same when copying data.

 

I was using a sata had with an hdd and a usb3 disk.

When copying files it fails.

 

Since I'm new to this any help to get this resolved is welcome.  

 

 -->  Linux nanopim4v2 5.4.7-rockchip64 #19.11.5 SMP PREEMPT Wed Jan 1 09:39:17 CET 2020 aarch64 GNU/Linux
 

 

 

Log that I found

 

 

Jan 17 12:54:19 nanopim4v2 kernel: [21912.080372] Modules linked in: hci_uart bluetooth cpufreq_userspace zstd zram dw_hdmi_i2s_audio rockchip_rga brcmfmac brcmutil v4l2_mem2mem videobuf2_dma_sg videobuf2_memops videobuf2_v4l2 videobuf2_common cfg80211 videodev rfkill fusb302 mc tcpm typec panfrost gpu_sched rockchipdrm analogix_dp dw_mipi_dsi dw_hdmi ip_tables ipv6 crc_ccitt uas raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx raid1 raid0 multipath linear md_mod phy_rockchip_typec phy_rockchip_pcie dwmac_rk stmmac_platform stmmac phylink
Jan 17 12:54:19 nanopim4v2 kernel: [21912.088969] CPU: 5 PID: 273 Comm: kswapd0 Not tainted 5.4.7-rockchip64 #19.11.5
Jan 17 12:54:19 nanopim4v2 kernel: [21912.091123] Hardware name: FriendlyElec NanoPi M4 Ver2.0 (DT)
Jan 17 12:54:19 nanopim4v2 kernel: [21912.093184] pstate: 40000005 (nZcv daif -PAN -UAO)
Jan 17 12:54:19 nanopim4v2 kernel: [21912.095088] pc : __call_rcu+0x2c/0x1c0
Jan 17 12:54:19 nanopim4v2 kernel: [21912.096945] lr : call_rcu+0x10/0x18
Jan 17 12:54:19 nanopim4v2 kernel: [21912.098769] sp : ffff800011e9b8c0
Jan 17 12:54:19 nanopim4v2 kernel: [21912.100562] x29: ffff800011e9b8c0 x28: 00000000000000b2
Jan 17 12:54:19 nanopim4v2 kernel: [21912.102569] x27: ffff0000ee567c40 x26: 0000000000000000
Jan 17 12:54:19 nanopim4v2 kernel: [21912.104553] x25: 0000000000000000 x24: 0000000000000000
Jan 17 12:54:19 nanopim4v2 kernel: [21912.106518] x23: ffff8000105d8618 x22: ffff0000ed9ac1d8
Jan 17 12:54:19 nanopim4v2 kernel: [21912.108482] x21: ffff800010dbfe60 x20: 0000000080000000
Jan 17 12:54:19 nanopim4v2 kernel: [21912.110455] x19: 0000000000000000 x18: 0000000000000001
Jan 17 12:54:19 nanopim4v2 kernel: [21912.112396] x17: 0000000000000000 x16: 0000000000000000
Jan 17 12:54:19 nanopim4v2 kernel: [21912.114370] x15: ffffffffffffffff x14: ffff80001135b508
Jan 17 12:54:19 nanopim4v2 kernel: [21912.116348] x13: fffffe0002d60540 x12: 0000000000000001
Jan 17 12:54:19 nanopim4v2 kernel: [21912.118310] x11: 0000000000000000 x10: 00000000000009d0
Jan 17 12:54:19 nanopim4v2 kernel: [21912.120259] x9 : ffff800011e9b8f0 x8 : 0000000000000000
Jan 17 12:54:19 nanopim4v2 kernel: [21912.122214] x7 : 0000000000000001 x6 : 0000000000000000
Jan 17 12:54:19 nanopim4v2 kernel: [21912.124095] x5 : 0000000000000001 x4 : ffff0000ee567800
Jan 17 12:54:19 nanopim4v2 kernel: [21912.125973] x3 : ffff0000edb70c70 x2 : 0000000000000000
Jan 17 12:54:19 nanopim4v2 kernel: [21912.127822] x1 : ffff8000105d8618 x0 : 0000000080000000
Jan 17 12:54:19 nanopim4v2 kernel: [21912.129690] Call trace:
Jan 17 12:54:19 nanopim4v2 kernel: [21912.131269]  __call_rcu+0x2c/0x1c0
Jan 17 12:54:19 nanopim4v2 kernel: [21912.132934]  call_rcu+0x10/0x18
Jan 17 12:54:19 nanopim4v2 kernel: [21912.134582]  security_inode_free+0x48/0x58
Jan 17 12:54:19 nanopim4v2 kernel: [21912.136306]  __destroy_inode+0xb0/0x218
Jan 17 12:54:19 nanopim4v2 kernel: [21912.138016]  destroy_inode+0x2c/0x70
Jan 17 12:54:19 nanopim4v2 kernel: [21912.139725]  evict+0x104/0x168
Jan 17 12:54:19 nanopim4v2 kernel: [21912.141386]  iput+0xd8/0x190
Jan 17 12:54:19 nanopim4v2 kernel: [21912.143010]  dentry_unlink_inode+0x114/0x160
Jan 17 12:54:19 nanopim4v2 kernel: [21912.144727]  __dentry_kill+0xc0/0x1c0
Jan 17 12:54:19 nanopim4v2 kernel: [21912.146396]  shrink_dentry_list+0x7c/0xd8
Jan 17 12:54:19 nanopim4v2 kernel: [21912.148088]  prune_dcache_sb+0x5c/0x88
Jan 17 12:54:19 nanopim4v2 kernel: [21912.149767]  super_cache_scan+0xcc/0x160
Jan 17 12:54:19 nanopim4v2 kernel: [21912.151433]  do_shrink_slab+0x134/0x248
Jan 17 12:54:19 nanopim4v2 kernel: [21912.153082]  shrink_slab+0xb4/0x2a8
Jan 17 12:54:19 nanopim4v2 kernel: [21912.154701]  shrink_node+0xc0/0x468
Jan 17 12:54:19 nanopim4v2 kernel: [21912.156292]  balance_pgdat+0x2c8/0x540
Jan 17 12:54:19 nanopim4v2 kernel: [21912.157926]  kswapd+0x1c4/0x370
Jan 17 12:54:19 nanopim4v2 kernel: [21912.159511]  kthread+0x120/0x128
Jan 17 12:54:19 nanopim4v2 kernel: [21912.161065]  ret_from_fork+0x10/0x18
Jan 17 12:54:19 nanopim4v2 kernel: [21912.164486] ---[ end trace 04aebd1132e57ca5 ]---
root@nanopim4v2:~# ~~~

 

Link to comment
Share on other sites

  • 0
6 hours ago, Noboot said:

I've seem to have the same when copying data.

 

I was using a sata had with an hdd and a usb3 disk.

When copying files it fails.

 

Since I'm new to this any help to get this resolved is welcome.  

 

 -->  Linux nanopim4v2 5.4.7-rockchip64 #19.11.5 SMP PREEMPT Wed Jan 1 09:39:17 CET 2020 aarch64 GNU/Linux
 

 

 

Log that I found

 

 


Jan 17 12:54:19 nanopim4v2 kernel: [21912.080372] Modules linked in: hci_uart bluetooth cpufreq_userspace zstd zram dw_hdmi_i2s_audio rockchip_rga brcmfmac brcmutil v4l2_mem2mem videobuf2_dma_sg videobuf2_memops videobuf2_v4l2 videobuf2_common cfg80211 videodev rfkill fusb302 mc tcpm typec panfrost gpu_sched rockchipdrm analogix_dp dw_mipi_dsi dw_hdmi ip_tables ipv6 crc_ccitt uas raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx raid1 raid0 multipath linear md_mod phy_rockchip_typec phy_rockchip_pcie dwmac_rk stmmac_platform stmmac phylink
Jan 17 12:54:19 nanopim4v2 kernel: [21912.088969] CPU: 5 PID: 273 Comm: kswapd0 Not tainted 5.4.7-rockchip64 #19.11.5
Jan 17 12:54:19 nanopim4v2 kernel: [21912.091123] Hardware name: FriendlyElec NanoPi M4 Ver2.0 (DT)
Jan 17 12:54:19 nanopim4v2 kernel: [21912.093184] pstate: 40000005 (nZcv daif -PAN -UAO)
Jan 17 12:54:19 nanopim4v2 kernel: [21912.095088] pc : __call_rcu+0x2c/0x1c0
Jan 17 12:54:19 nanopim4v2 kernel: [21912.096945] lr : call_rcu+0x10/0x18
Jan 17 12:54:19 nanopim4v2 kernel: [21912.098769] sp : ffff800011e9b8c0
Jan 17 12:54:19 nanopim4v2 kernel: [21912.100562] x29: ffff800011e9b8c0 x28: 00000000000000b2
Jan 17 12:54:19 nanopim4v2 kernel: [21912.102569] x27: ffff0000ee567c40 x26: 0000000000000000
Jan 17 12:54:19 nanopim4v2 kernel: [21912.104553] x25: 0000000000000000 x24: 0000000000000000
Jan 17 12:54:19 nanopim4v2 kernel: [21912.106518] x23: ffff8000105d8618 x22: ffff0000ed9ac1d8
Jan 17 12:54:19 nanopim4v2 kernel: [21912.108482] x21: ffff800010dbfe60 x20: 0000000080000000
Jan 17 12:54:19 nanopim4v2 kernel: [21912.110455] x19: 0000000000000000 x18: 0000000000000001
Jan 17 12:54:19 nanopim4v2 kernel: [21912.112396] x17: 0000000000000000 x16: 0000000000000000
Jan 17 12:54:19 nanopim4v2 kernel: [21912.114370] x15: ffffffffffffffff x14: ffff80001135b508
Jan 17 12:54:19 nanopim4v2 kernel: [21912.116348] x13: fffffe0002d60540 x12: 0000000000000001
Jan 17 12:54:19 nanopim4v2 kernel: [21912.118310] x11: 0000000000000000 x10: 00000000000009d0
Jan 17 12:54:19 nanopim4v2 kernel: [21912.120259] x9 : ffff800011e9b8f0 x8 : 0000000000000000
Jan 17 12:54:19 nanopim4v2 kernel: [21912.122214] x7 : 0000000000000001 x6 : 0000000000000000
Jan 17 12:54:19 nanopim4v2 kernel: [21912.124095] x5 : 0000000000000001 x4 : ffff0000ee567800
Jan 17 12:54:19 nanopim4v2 kernel: [21912.125973] x3 : ffff0000edb70c70 x2 : 0000000000000000
Jan 17 12:54:19 nanopim4v2 kernel: [21912.127822] x1 : ffff8000105d8618 x0 : 0000000080000000
Jan 17 12:54:19 nanopim4v2 kernel: [21912.129690] Call trace:
Jan 17 12:54:19 nanopim4v2 kernel: [21912.131269]  __call_rcu+0x2c/0x1c0
Jan 17 12:54:19 nanopim4v2 kernel: [21912.132934]  call_rcu+0x10/0x18
Jan 17 12:54:19 nanopim4v2 kernel: [21912.134582]  security_inode_free+0x48/0x58
Jan 17 12:54:19 nanopim4v2 kernel: [21912.136306]  __destroy_inode+0xb0/0x218
Jan 17 12:54:19 nanopim4v2 kernel: [21912.138016]  destroy_inode+0x2c/0x70
Jan 17 12:54:19 nanopim4v2 kernel: [21912.139725]  evict+0x104/0x168
Jan 17 12:54:19 nanopim4v2 kernel: [21912.141386]  iput+0xd8/0x190
Jan 17 12:54:19 nanopim4v2 kernel: [21912.143010]  dentry_unlink_inode+0x114/0x160
Jan 17 12:54:19 nanopim4v2 kernel: [21912.144727]  __dentry_kill+0xc0/0x1c0
Jan 17 12:54:19 nanopim4v2 kernel: [21912.146396]  shrink_dentry_list+0x7c/0xd8
Jan 17 12:54:19 nanopim4v2 kernel: [21912.148088]  prune_dcache_sb+0x5c/0x88
Jan 17 12:54:19 nanopim4v2 kernel: [21912.149767]  super_cache_scan+0xcc/0x160
Jan 17 12:54:19 nanopim4v2 kernel: [21912.151433]  do_shrink_slab+0x134/0x248
Jan 17 12:54:19 nanopim4v2 kernel: [21912.153082]  shrink_slab+0xb4/0x2a8
Jan 17 12:54:19 nanopim4v2 kernel: [21912.154701]  shrink_node+0xc0/0x468
Jan 17 12:54:19 nanopim4v2 kernel: [21912.156292]  balance_pgdat+0x2c8/0x540
Jan 17 12:54:19 nanopim4v2 kernel: [21912.157926]  kswapd+0x1c4/0x370
Jan 17 12:54:19 nanopim4v2 kernel: [21912.159511]  kthread+0x120/0x128
Jan 17 12:54:19 nanopim4v2 kernel: [21912.161065]  ret_from_fork+0x10/0x18
Jan 17 12:54:19 nanopim4v2 kernel: [21912.164486] ---[ end trace 04aebd1132e57ca5 ]---
root@nanopim4v2:~# ~~~

 

Since I set the CPU frequency to 1.4/1.8Ghz I have no problems.
Look at this topic

 

 

Link to comment
Share on other sites

  • 0

 

Hi,

First, I use a mean well S-100F-12 (12 Volt 8.5 A) 

https://www.meanwell-web.com/nl-nl/ac-dc-enclosed-power-supply-output-12vdc-at-8-5a-s--100f--12

This one I had some time and I wasn't using it.

I power the NanoPi true the 4-pin connector on the sata hat with a connector used from an old PC power supply.  (All 4 wires connected)

 

 

I had some spare time this week-end and did some test with my NanoPi.  

The problem seems to be more noticeable when I use midnight commander and copy files from usb to the sata hat.

It also shows up when copying files from network to sata true a samba share on the NanoPi.

 

Slowing down the CPU to 1800 ,1600 and 1400 did not make a difference.

 

Temperature found with htop was approx. 42-40°C at max CPU and at 1600 - 1400 about 36°C

I have a large slow turning fan on the NanoPi and a 50mm direct above the sata hat.

 

What I found strange is, that when I started from a cooled down NanoPi the NanoPi worked longer before failing than when is just rebooted and started again. (Or it is my imagination :-))

 

After another tip on https://forum.openmediavault.org/index.php/Thread/30512-Nanopi-crashes-on-file-transfers/ I restarted and used kernel 4.4.

The CPU is now running at 1800 with a temp of 30 a 35°C and I don’t seem to have this problem anymore.

 

At this point I'm not sure it's a power problem or a temperature problem but I'm planning to spend some more time on it this weekend.

There is also still a possibility that I received a faulty NanoPi or hat . . .

 

Any further input about this is always welcome.

 

 

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
 Share

×
×
  • Create New...