Rock64 kernel oops after update

[moonman]

Hi Guys,

So after some time I did an update which pulled in the latest 5.4 kernel, but I noticed that SSH was not available after the restart. So I leverged the Uart and have the following,

$this->bbcode_second_pass_code('', ' OK ] Started Network Service.
[ 9.747359] audit: type=1130 audit(1576586649.390:6): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-netwo'
Starting Wait for Network to be Configured...
[ OK ] Found device /dev/disk/by-label/boot.
[ 9.973149] Unable to handle kernel NULL pointer dereference at virtual address 0000000000000378
[ 9.973938] Mem abort info:
[ 9.974190] ESR = 0x96000004
[ 9.974466] EC = 0x25: DABT (current EL), IL = 32 bits
[ 9.974937] SET = 0, FnV = 0
[ 9.975207] EA = 0, S1PTW = 0
[ 9.975558] Data abort info:
[ 9.975830] ISV = 0, ISS = 0x00000004
[ 9.976174] CM = 0, WnR = 0
[ 9.976445] user pgtable: 4k pages, 48-bit VAs, pgdp=00000000f3b53000
[ 9.977015] [0000000000000378] pgd=0000000000000000
[ 9.977452] Internal error: Oops: 96000004 [#1] SMP
[ 9.977887] Modules linked in: rc_cec snd_soc_hdmi_codec dw_hdmi_i2s_audio dw_hdmi_cec(+) snd_soc_audio_graph_card snd_sf
[ 9.981335] CPU: 0 PID: 476 Comm: systemd-network Not tainted 5.4.8-1-ARCH #1
[ 9.981963] Hardware name: Pine64 Rock64 (DT)
[ 9.982352] pstate: 40000005 (nZcv daif -PAN -UAO)
[ 9.982782] pc : mdiobus_get_phy+0x20/0x40
[ 9.983171] lr : stmmac_open+0x6c0/0x858 [stmmac]
[ 9.983587] sp : ffff800011e43650
[ 9.983881] x29: ffff800011e43650 x28: ffff0000f1b408c0
[ 9.984350] x27: ffff0000f2278c10 x26: ffff800011e43bd0
[ 9.984819] x25: 0000000000000001 x24: 0000000000000000
[ 9.985289] x23: 0000000000001002 x22: ffff8000090ef0b8
[ 9.985760] x21: ffff800011e43bd0 x20: 0000000000000000
[ 9.986228] x19: fffffffffffffff8 x18: 0000000000000000
[ 9.986699] x17: 0000000000000000 x16: 0000000000000000
[ 9.987168] x15: 0000000000000000 x14: 0000000000000000
[ 9.987638] x13: 0000000000000000 x12: 0000000000000000
[ 9.988107] x11: 0000000000000003 x10: 0101010101010101
[ 9.988577] x9 : fffffffffffffff9 x8 : 7f7f7f7f7f7f7f7f
[ 9.989046] x7 : fefefeff646c606d x6 : 1e091448e4e5f6e9
[ 9.989516] x5 : 697665644814091e x4 : 8080808000000000
[ 9.989986] x3 : 8343c96b232bb348 x2 : ffff0000f23e8480
[ 9.990457] x1 : 00000000ffffffff x0 : ffff8000090db7b8
[ 9.990928] Call trace:
[ 9.991152] mdiobus_get_phy+0x20/0x40
[ 9.991507] stmmac_open+0x6c0/0x858 [stmmac]
[ 9.991897] __dev_open+0x104/0x198
[ 9.992208] __dev_change_flags+0x19c/0x1f8
[ 9.992581] dev_change_flags+0x3c/0x78
[ 9.992922] do_setlink+0x75c/0x8b0
[ 9.993233] rtnl_setlink+0xe4/0x160
[ 9.993551] rtnetlink_rcv_msg+0x298/0x330
[ 9.993917] netlink_rcv_skb+0x5c/0x118
[ 9.994259] rtnetlink_rcv+0x28/0x38
[ 9.994578] netlink_unicast+0x180/0x208
[ 9.994926] netlink_sendmsg+0x1a0/0x348
[ 9.995276] sock_sendmsg+0x54/0x60
[ 9.995537] Registered IR keymap rc-cec
[ 9.995591] __sys_sendto+0xe4/0x150
[ 9.996091] rc rc1: dw_hdmi as /devices/platform/ff3c0000.hdmi/rc/rc1
[ 9.996250] __arm64_sys_sendto+0x30/0x40
[ 9.997007] input: dw_hdmi as /devices/platform/ff3c0000.hdmi/rc/rc1/input1
[ 9.997178] el0_svc_handler+0x84/0x190
[ 9.997184] el0_svc+0x8/0xc
[ 9.998406] Code: aa0003f4 aa1e03e0 8b33ce93 d503201f (f941c260)
[ 9.998948] ---[ end trace 026a3ab73ec46fa0 ]---
[ 10.005884] audit: type=1131 audit(1576586649.650:7): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-netwo'
[ OK ] Stopped Network Service.
[ 10.035756] audit: type=1130 audit(1576586649.680:8): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-netwo'
[ 10.037455] audit: type=1131 audit(1576586649.680:9): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-netwo'
Starting Network Service...
[ OK ] Started Monitoring of LVM2��… dmeventd or progress polling.
[ 10.105958] audit: type=1130 audit(1576586649.750:10): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=lvm2-monitor'
[ OK ] Reached target Local File Systems (Pre).
Mounting /boot...
[ 10.155114] FAT-fs (mmcblk1p6): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
[ OK ] Mounted /boot.
[ OK ] Reached target Local File Systems.
Starting Create Volatile Files and Directories...
[ OK ] Started Create Volatile Files and Directories.
[ 10.295847] audit: type=1130 audit(1576586649.940:11): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-tmpf'
Starting Update UTMP about System Boot/Shutdown...
[ OK ] Started Update UTMP about System Boot/Shutdown.
[ OK ] Reached target System Initialization.
[ OK ] Started Daily rotation of log files.
[ OK ] Started Daily man-db regeneration.
[ OK ] Started Daily verification of password and group files.
[ OK ] Started Daily Cleanup of Temporary Directories.
[ OK ] Started Daily locate database update.
[ OK ] Reached target Timers.
[ OK ] Listening on D-Bus System Message Bus Socket.
[ OK ] Reached target Sockets.
[ OK ] Reached target Basic System.
[ OK ] Started D-Bus System Message Bus.
[ OK ] Started System Logger Daemon.
[ OK ] Started Mosquitto MQTT Broker daemon.
Starting Login Service...
[ OK ] Started Login Service.
[FAILED] Failed to start Wait for Network to be Configured.
See 'systemctl status systemd-networkd-wait-online.service' for details.
')

So it looks like the kernel oops is something important as the networkd startup just fails and retries with a new start job once the last attempt fails and shuts down. I have taken out all configurations from networking as I have the system on a removable emmc card.

I will remove the link to stop networkd from auto starting also in an attempt to be able to login as its holding the uart in an infinite bootloop, is this something more widespread or perhaps it is something with my systems here.

Nige

[nsollars]

So to solve this one I went ahead and used the official Arch install and have successfully updated to 5.4.11-1

Linux archarm 5.4.11-1-ARCH #1 SMP Sun Jan 12 09:24:02 MST 2020 aarch64 GNU/Linux


I believe since the install I had was made some time ago and I have not touched uboot and or boot.scr since I did the install, perhaps there was an inconsistency that caused this panic.

Hope this helps someone whom may see the same issues...

[PmaxP]

Hello, i still have this problem on the latest kernel, 5.4.13

System boots but randomly goes into kernel panic.

rolled back to earlier version (5.4.6.1) and all works without problems!

[nsollars]

Interesting,

I noticed that after some time my system is not available over SSH, perhaps it is panicing also. I will hook up a unit to the uart and take a look. If I remember right my unit is running 5.4.12 ( might be mistaken ), il most likely roll back also at this stage.

Nige

[ITwrx]

mine has been panicking intermittently since i got it last summer. i'm probably going to try openSUSE's JeOS and see if it will run properly. Reading other forums, it sounds like it may be upstream and hardware compatibility, unfortunately.

[twarm]

I've had lots of issues with my V2. On Arch-arm I can't compile anything above -j1 without it segfaulting.
SSH locks up randomly. I've read of others at armbian having probs too with some V2's. KP's on boot is what I got on any recent images. Old 4.4 bionic is only img that works and it compiles fine. I'll most likely get some other board like a odroid n2 that peeps seem happy with. Lot more $ though.

[PmaxP]

After some tests, I noticed that kernel panics occurs when I have the UART serial cable connected. Unplugging it, kernel panics are gone....

Tested with all latest kernel releases (on Pine rock64 v3)