Orange Pi 3B crash

Troubleshooting
1

Hi all,

Recently I encounter a issue that freezes the entire Orange Pi and no of the services are working. It usually happens one or two days and I have to manually restart it.

This is the journalclt

image
image1359×114 7.23 KB

Can it be realated to this: Initializing XFRM netlink socket
I’ve made a research and it should not be a issue.
This is new as I have the Pi connected to a NAS via NFS and it was not a issue before when I didn’t have it. This is my NFS mount:

image

image

Distro: bookworm
Kernel: Linux DietPi 6.19.0-rc4-edge-rockchip64 | arm64
SD Card: Sandisk Ultra Plus 10 128GB

Thanks for your help.

2

Sorry, this is also in journal too many times:
Jan 16 21:00:05 DietPi kernel: sprdwl:ctx_id = 0, sm_state = 4, bssid =ff:ff:ff:ff:ff:ff

3

The short fragment does not contain any information, and it also appears to be part of the boot process.

You need the entire log, not just those few lines.

4

Those are the last lines from last crash

Jan 17 19:00:06 DietPi kernel: sprdwl:ctx_id = 0, sm_state = 4, bssid =33:33:00:00:00:16
Jan 17 19:00:06 DietPi kernel: sprdwl:ctx_id = 0, sm_state = 4, bssid =33:33:00:00:00:16
Jan 17 19:00:06 DietPi kernel: sprdwl:ctx_id = 0, sm_state = 4, bssid =ff:ff:ff:ff:ff:ff
Jan 17 19:00:06 DietPi kernel: sprdwl:ctx_id = 0, sm_state = 4, bssid =ff:ff:ff:ff:ff:ff
Jan 17 19:00:06 DietPi kernel: sprdwl:ctx_id = 0, sm_state = 4, bssid =33:33:00:00:00:16
Jan 17 19:00:06 DietPi kernel: sprdwl:ctx_id = 0, sm_state = 4, bssid =33:33:00:00:00:16
Jan 17 19:00:06 DietPi kernel: sprdwl:ctx_id = 0, sm_state = 4, bssid =33:33:ff:67:72:5c
Jan 17 19:00:06 DietPi kernel: sprdwl:ctx_id = 0, sm_state = 4, bssid =33:33:ff:67:72:5c
Jan 17 19:00:07 DietPi kernel: sprdwl:ctx_id = 0, sm_state = 4, bssid =33:33:00:00:00:16
Jan 17 19:00:07 DietPi kernel: sprdwl:ctx_id = 0, sm_state = 4, bssid =33:33:00:00:00:16
Jan 17 19:00:07 DietPi kernel: sprdwl:ctx_id = 0, sm_state = 4, bssid =33:33:00:00:00:02
Jan 17 19:00:07 DietPi kernel: sprdwl:ctx_id = 0, sm_state = 4, bssid =33:33:00:00:00:02
Jan 17 19:00:08 DietPi kernel: sprdwl:ctx_id = 0, sm_state = 5, bssid =33:33:00:00:00:16
Jan 17 19:00:08 DietPi kernel: sprdwl:ctx_id = 0, sm_state = 5, bssid =33:33:00:00:00:16
Jan 17 19:00:10 DietPi kernel: unisoc_wifi unisoc_wifi wlan0: sprdwl_report_connection Wifi_name failed status code:1!
Jan 17 19:00:11 DietPi kernel: sprdwl:ctx_id = 0, sm_state = 5, bssid =33:33:00:00:00:02
Jan 17 19:00:11 DietPi kernel: sprdwl:ctx_id = 0, sm_state = 5, bssid =33:33:00:00:00:02
5

These are just some messages about wifi, I doubt they have anything to do with the freeze.

You said it occurs since you use the NFS share.
What do you have on the share? Is some process regularly accessing something on it?

You could try other mounting options in your fstab which are more safe if something is wrong with the share:

<IP>:/path  /mnt/nfs_client nfs noauto,x-systemd.automount,soft,timeo=10,retrans=3,rsize=1048576,wsize=1048576 0 0

If the NFS server doesn’t respond, operations fail instead of hanging the client. Timeout is set to 1 second in retry to 3.

1 Like
6

I will try what yo suggest here, thank you

7

It still happen, from what I see in journalctl it happens randomly at o clock hours.