gartox Posted February 1, 2023 Share Posted February 1, 2023 Hello All, Do you also have this kind of messages in syslog ? [ 1601.687044] ------------[ cut here ]------------ [ 1601.687070] WARNING: CPU: 2 PID: 112 at drivers/gpu/drm/rockchip/rockchip_drm_vop2.c:2986 vop2_crtc_load_lut+0x54/0x310 [ 1601.687075] Modules linked in: bnep zstd joydev sch_fq_codel fuse ip_tables ipv6 r8152 panfrost gpu_sched [ 1601.687114] CPU: 2 PID: 112 Comm: kworker/u16:1 Tainted: G W 5.10.110-rockchip-rk3588 #trunk.0184 [ 1601.687117] Hardware name: Orange Pi 5 (DT) [ 1601.687127] Workqueue: events_unbound commit_work [ 1601.687134] pstate: 40c00009 (nZcv daif +PAN +UAO -TCO BTYPE=--) [ 1601.687138] pc : vop2_crtc_load_lut+0x54/0x310 [ 1601.687142] lr : vop2_crtc_load_lut+0x4c/0x310 [ 1601.687145] sp : ffffffc012d0bbd0 [ 1601.687148] x29: ffffffc012d0bbd0 x28: ffffff812bbbc000 [ 1601.687155] x27: ffffffc01113d020 x26: ffffff821141aa00 [ 1601.687162] x25: ffffff82108a0058 x24: ffffff81053b2080 [ 1601.687168] x23: 0000000000000400 x22: ffffffc011598cf8 [ 1601.687175] x21: ffffff81053b0080 x20: ffffff81053b0080 [ 1601.687182] x19: ffffff81053b00f8 x18: 0000000000000000 [ 1601.687189] x17: 0000000000000000 x16: 0000000000000000 [ 1601.687195] x15: 0000000000000010 x14: 0000000034325258 [ 1601.687202] x13: ffffffc012d0bb98 x12: ffffffffffffffff [ 1601.687208] x11: 0000000000000040 x10: 00000000fffffffe [ 1601.687214] x9 : ffffffc0107e6030 x8 : 0000000000000000 [ 1601.687221] x7 : ffffff81053d0080 x6 : 00000000000003ff [ 1601.687227] x5 : 0000000000000400 x4 : 00000000000003ff [ 1601.687233] x3 : 000000003fffffff x2 : 00000000000003ff [ 1601.687240] x1 : ffffffc012d05000 x0 : 0000000000000000 [ 1601.687247] Call trace: [ 1601.687253] vop2_crtc_load_lut+0x54/0x310 [ 1601.687258] vop2_crtc_atomic_flush+0x948/0xc18 [ 1601.687262] drm_atomic_helper_commit_planes+0x1c0/0x1c8 [ 1601.687269] rockchip_drm_atomic_helper_commit_tail_rpm+0xa4/0x144 [ 1601.687273] commit_tail+0x80/0x108 [ 1601.687277] commit_work+0x1c/0x28 [ 1601.687283] process_one_work+0x1d8/0x290 [ 1601.687287] worker_thread+0x1e0/0x270 [ 1601.687293] kthread+0xf4/0x104 [ 1601.687299] ret_from_fork+0x10/0x30 [ 1601.687302] ... followed by large dump in hex I really don't have any clue of where it may come from. I'm using the Armbian 22.11 Jammy Gnome Release date: Jan 23, 2023, and I unfreeze nighlies to have latest kernel updates/testings : Linux orangepi5 5.10.110-rockchip-rk3588 #trunk.0220 SMP Tue Jan 31 16:58:49 UTC 2023 aarch64 aarch64 aarch64 GNU/Linux All seems to be working just fine. I would just like to report. thanks ! 0 Quote Link to comment Share on other sites More sharing options...
martivo Posted February 2, 2023 Share Posted February 2, 2023 [ 35.994282] ------------[ cut here ]------------ [ 35.994307] WARNING: CPU: 3 PID: 219 at drivers/gpu/drm/rockchip/rockchip_drm_vop2.c:2986 vop2_crtc_load_lut+0x54/0x310 [ 35.994311] Modules linked in: xt_nat veth xt_conntrack nft_chain_nat xt_MASQUERADE nf_nat nf_conntrack_netlink nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nft_counter xt_addrtype nft_compat nf_tables nfnetlink br_netfilter bridge stp llc overlay zstd joydev sch_fq_codel fuse ip_tables ipv6 raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx raid1 raid0 multipath linear md_mod panfrost gpu_sched [ 35.994461] CPU: 3 PID: 219 Comm: kworker/u16:4 Not tainted 5.10.110-rockchip-rk3588 #trunk.0184 [ 35.994465] Hardware name: Orange Pi 5 (DT) [ 35.994476] Workqueue: events_unbound commit_work [ 35.994485] pstate: 40c00009 (nZcv daif +PAN +UAO -TCO BTYPE=--) [ 35.994491] pc : vop2_crtc_load_lut+0x54/0x310 [ 35.994497] lr : vop2_crtc_load_lut+0x4c/0x310 [ 35.994500] sp : ffffffc0162c3bd0 [ 35.994505] x29: ffffffc0162c3bd0 x28: ffffff8145226800 [ 35.994515] x27: ffffffc01113d020 x26: ffffff818d398180 [ 35.994525] x25: ffffff81609cc058 x24: ffffff8105492080 [ 35.994534] x23: 0000000000000400 x22: ffffffc011598cf8 [ 35.994543] x21: ffffff8105490080 x20: ffffff8105490080 [ 35.994553] x19: ffffff81054900f8 x18: 0000000000000000 [ 35.994562] x17: 0000000000000000 x16: 0000000000000000 [ 35.994572] x15: 0000000000000010 x14: 0000000034325258 [ 35.994581] x13: ffffffc0162c3b98 x12: ffffffffffffffff [ 35.994591] x11: 0000000000000040 x10: 00000000fffffffe [ 35.994600] x9 : ffffffc0107e6030 x8 : 0000000000000000 [ 35.994610] x7 : ffffff81054e0080 x6 : 00000000000003ff [ 35.994619] x5 : 0000000000000400 x4 : 00000000000003ff [ 35.994628] x3 : 000000003fffffff x2 : 00000000000003ff [ 35.994638] x1 : ffffffc012d05000 x0 : 0000000000000000 [ 35.994647] Call trace: [ 35.994654] vop2_crtc_load_lut+0x54/0x310 [ 35.994661] vop2_crtc_atomic_flush+0x948/0xc18 [ 35.994667] drm_atomic_helper_commit_planes+0x1c0/0x1c8 [ 35.994675] rockchip_drm_atomic_helper_commit_tail_rpm+0xa4/0x144 [ 35.994681] commit_tail+0x80/0x108 [ 35.994686] commit_work+0x1c/0x28 [ 35.994694] process_one_work+0x1d8/0x290 [ 35.994700] worker_thread+0x1e0/0x270 [ 35.994706] kthread+0xf4/0x104 [ 35.994714] ret_from_fork+0x10/0x30 [ 35.994719] PC: 0xffffffc0107e6038: [ 35.994723] 5e38 910003fd a90153f3 aa0003f4 d2800201 a9025bf5 f0006d96 9133e2d6 a90363f7 ... [ 36.010446] ---[ end trace d5485d5fc9687633 ]--- I also noticed these in my dmesg, but have not had time to look into it. I can confirm that I get them too. root@loovsys:~# uname -a Linux loovsys.eu 5.10.110-rockchip-rk3588 #trunk.0184 SMP Fri Jan 20 18:24:04 UTC 2023 aarch64 aarch64 aarch64 GNU/Linux 0 Quote Link to comment Share on other sites More sharing options...
eshelton Posted February 2, 2023 Share Posted February 2, 2023 A few additional pieces of info. The kernel warning is from this line of code. If you do a fresh install of trunk, the warning is not generated. For me, the warning consistently begin appearing after installing panfork, etc and switching to Wayland for hw acceleration. The warning is produced pretty frequently, making the kernel log quickly grow to a large size. Not sure if this is a result of the frankenkernel that is BSP -- I don't know much about the guts of DRM. If it is, maybe patch out this specific instance of "WARN_ON"? 0 Quote Link to comment Share on other sites More sharing options...
gartox Posted February 2, 2023 Author Share Posted February 2, 2023 I also think that everything happened after switching to Waylang for hw acceleration. 0 Quote Link to comment Share on other sites More sharing options...
martivo Posted February 2, 2023 Share Posted February 2, 2023 I am also using Wayland and hw acceleration. 0 Quote Link to comment Share on other sites More sharing options...
eshelton Posted February 4, 2023 Share Posted February 4, 2023 Over the last few months, Ubuntu 22.10 users on Intel seem to have encountered similar kernel warnings: https://www.reddit.com/r/framework/comments/yvkdog/kernel_modeset_warning_with_ubuntu_2210_on_11th/ This patch seems fairly on point: https://kernel.googlesource.com/pub/scm/linux/kernel/git/balbi/usb/+/5ec1cebd59300ddd26dbaa96c17c508764eef911 I briefly looked into applying a similar patch to see if that helps, but there is too much difference between drivers/gpu/drm/drm_atomic.c in BSP and mainline to do an easy backport. Assuming BSP has some kind of issue like this, and the funky state of its DRM kernel code, patching out the warning might be a reasonable approach... 0 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.