brm Posted October 6, 2020 Share Posted October 6, 2020 Armbianmonitor: http://ix.io/2zWh Hi. I am getting a kernel Oops in the Pine64+ . . . .see below. Kernel is 5.8.13-sunxi64. It was installed after a recent update. I would like to drop back to the previous kernel if possible. Does this seem like a reasonable search term for a suitable kernel? Any ideas on searching and installing a previous kernel appreciated. sudo apt-cache search kernel 5.8* | grep sunxi64 linux-dtb-current-sunxi64 - Linux DTB, version 5.8.13-sunxi64 linux-dtb-dev-sunxi64 - Linux DTB, version 5.9.0-rc7-sunxi64 linux-dtb-legacy-sunxi64 - Linux DTB, version 5.4.62-sunxi64 linux-headers-current-sunxi64 - Linux kernel headers for 5.8.13-sunxi64 on arm64 linux-headers-dev-sunxi64 - Linux kernel headers for 5.9.0-rc7-sunxi64 on arm64 linux-headers-legacy-sunxi64 - Linux kernel headers for 5.4.62-sunxi64 on arm64 linux-image-current-sunxi64 - Linux kernel, version 5.8.13-sunxi64 linux-image-dev-sunxi64 - Linux kernel, version 5.9.0-rc7-sunxi64 linux-image-legacy-sunxi64 - Linux kernel, version 5.4.62-sunxi64 linux-source-5.4.58-legacy-sunxi64 - This package provides the source code for the Linux kernel 5.4.58 linux-source-5.4.61-legacy-sunxi64 - This package provides the source code for the Linux kernel 5.4.61 [ 23.475944] ------------[ cut here ]------------ [ 23.478571] WARNING: CPU: 3 PID: 171 at drivers/clocksource/arm_arch_timer.c:364 sun50i_a64_read_cntpct_el0+0x30/0x38 [ 23.480502] Modules linked in: cpufreq_dt realtek dwmac_sun8i pinctrl_axp209 mdio_mux i2c_mv64xxx [ 23.483003] CPU: 3 PID: 171 Comm: kworker/3:3 Not tainted 5.8.13-sunxi64 #20.08.7 [ 23.484968] Hardware name: Pine64+ (DT) [ 23.487226] Workqueue: events dbs_work_handler [ 23.489416] pstate: 80000005 (Nzcv daif -PAN -UAO BTYPE=--) [ 23.491571] pc : sun50i_a64_read_cntpct_el0+0x30/0x38 [ 23.493700] lr : arch_counter_get_cntpct_stable+0x3c/0x80 [ 23.495784] sp : ffff800011afb9c0 [ 23.497758] x29: ffff800011afb9c0 x28: ffff0000743a9a00 [ 23.499861] x27: ffff0000713ed600 x26: ffff0000743a9c68 [ 23.501992] x25: ffff000072e38228 x24: 0000000000000000 [ 23.504054] x23: 0000000000000001 x22: ffff800011afbb10 [ 23.506137] x21: 0000000000000000 x20: 0000000000000018 [ 23.508260] x19: ffff8000113dd000 [ 23.510328] hrtimer: interrupt took 27046125 ns [ 23.512242] x18: ffff800011afb9b8 [ 23.514290] x17: 0000000000000004 x16: 0000000000000001 [ 23.516399] x15: 0000000000000018 x14: 0000000000000002 [ 23.518455] x13: 0000000000000001 x12: 0000000000000001 [ 23.520483] x11: 0000000000000005 x10: 0000000000000021 [ 23.522575] x9 : 0000000044aa2000 x8 : ffff8000113aaf98 [ 23.524628] x7 : 0000000000000000 x6 : 00000000112a8800 [ 23.526731] x5 : 0000000000000010 x4 : 0000000000000012 [ 23.528810] x3 : 0000000000000050 x2 : 000000002ec5d477 [ 23.530879] x1 : 0000000000000000 x0 : 000000002ec5d47d [ 23.532925] Call trace: [ 23.535068] sun50i_a64_read_cntpct_el0+0x30/0x38 [ 23.537130] __delay+0x24/0xa8 [ 23.539201] __udelay+0x2c/0x38 [ 23.541332] ccu_mux_notifier_cb+0x64/0xa0 [ 23.543415] notifier_call_chain+0x54/0x98 [ 23.545482] __srcu_notifier_call_chain+0x58/0x98 [ 23.547538] srcu_notifier_call_chain+0x18/0x28 [ 23.549615] __clk_notify+0x88/0xd0 [ 23.551707] clk_propagate_rate_change+0xc4/0xd8 [ 23.553808] clk_core_set_rate_nolock+0x114/0x1f8 [ 23.555895] clk_set_rate+0x38/0xa8 [ 23.558113] dev_pm_opp_set_rate+0x264/0x618 [ 23.560250] set_target+0x40/0x88 [cpufreq_dt] [ 23.562349] __cpufreq_driver_target+0x2c4/0x668 [ 23.564464] od_dbs_update+0x140/0x1a0 [ 23.566542] dbs_work_handler+0x40/0x80 [ 23.568628] process_one_work+0x1c8/0x378 [ 23.570711] worker_thread+0x14c/0x4c8 [ 23.572806] kthread+0xf8/0x128 [ 23.574887] ret_from_fork+0x10/0x30 [ 23.576963] ---[ end trace 32a37354cad394e6 ]--- [ 23.735669] sun8i-ce 1c15000.crypto: Set mod clock to 300000000 (300 Mhz) from 24000000 (24 Mhz) [ 23.735961] sun8i-ce 1c15000.crypto: will run requests pump with realtime priority Link to comment Share on other sites More sharing options...
Igor Posted October 6, 2020 Share Posted October 6, 2020 1 hour ago, brm said: I would like to drop back to the previous kernel if possible. armbian-config -> system -> alternative kernels Link to comment Share on other sites More sharing options...
brm Posted October 6, 2020 Author Share Posted October 6, 2020 Thanks for the suggestion. Kernel 5.8.10-sunxi64 is exhibiting the same problem. Not sure how this will impact things. No locking up so should I just go with it - ignore and carry on? It is used as a Tinker board more than anything. It is running docker and a few containers. Link to comment Share on other sites More sharing options...
Igor Posted October 7, 2020 Share Posted October 7, 2020 Allwinner A64 board are all experiencing some issues lately. Try kernel 5.4.y Link to comment Share on other sites More sharing options...
Recommended Posts