<div dir="ltr"><div><div><div><div>Hi,<br><br></div>@Ping<br><br></div>Please advise further pointers if any. <br><br><br></div>Thanks<br></div>Shrikant<br><div><div><div><div><div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Aug 25, 2016 at 8:13 PM, srikanth krishnakar <span dir="ltr"><<a href="mailto:skrishnakar@gmail.com" target="_blank">skrishnakar@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div><div><div><div><div><font face="monospace,monospace">Hello All, <br><br></font></div><font face="monospace,monospace">I am building latest yocto with core-image-sato and noticed that matchbox session or its relative apps are using kernel context and eventually these are shown when the window manager is terminated or the target is rebooted. Please see the logs below:<br><br></font></div><div><font face="monospace,monospace">Target: i.MX6Q ARM<br></font></div><div><font face="monospace,monospace">Kernel: Linux-4.1<br></font></div><div><font face="monospace,monospace">Yocto: master (7b9f59)<br></font><table summary="commit info" height="24" width="369"><tbody><tr><th><br></th><td colspan="2"><br></td></tr></tbody></table></div><div><font face="monospace,monospace">------------------------------<wbr>--------<br>root@mx6q:~# ps | grep match<br> 558 root 7080 S matchbox-window-manager -theme Sato -use_cursor yes<br> 612 root 174m S matchbox-desktop<br> 614 root 174m S matchbox-panel --start-applets showdesktop,windowselector --end-applets clock,battery,,systray,<wbr>startup-notify,notify<br> 677 root 2752 S grep match<br>root@mx6q:~# <br>root@mx6q:~# <br>root@mx6q:~# opkg list | grep -i xserver-xorg<br>xserver-xorg - 2:1.18.4-r0.3<br>xserver-xorg-extension-glx - 2:1.18.4-r0.3<br>xserver-xorg-extension-viv-<wbr>autohdmi - 3:5.0.11.p8.4-r0.3<br>xserver-xorg-module-exa - 2:1.18.4-r0.3<br>root@mx6q:~# opkg list | grep -i matchbox <br>matchbox-config-gtk - 0.2-r0.2<br>matchbox-desktop - 2.1-r0.2<br>matchbox-keyboard - 0.1.1-r0.2<br>matchbox-keyboard-applet - 0.1.1-r0.2<br>matchbox-keyboard-im - 0.1.1-r0.2<br>matchbox-panel-2 - 2.11-r0.2<br>matchbox-session - 0.1-r4.0<br>matchbox-session-sato - 0.1-r30.0<br>matchbox-terminal - 0.1-r0.2<br>matchbox-theme-sato - 0.2-r0.0<br>matchbox-wm - 1.2.1-r0.1<br>root@mx6q:~# <br>root@mx6q:~# kill 558<br>root@mx6q:~# [ 404.937507] [drm:drm_legacy_unlock] *ERROR* Process 614 using kernel context 0<br>[ 404.947643] [drm:drm_lock_take] *ERROR* 1 holds heavyweight lock<br>[ 404.953752] [drm:drm_legacy_unlock] *ERROR* Process 612 using kernel context 0<br>[ 405.132658] [drm:drm_legacy_unlock] *ERROR* Process 612 using kernel context 0<br>[ 405.140370] [drm:drm_legacy_unlock] *ERROR* Process 614 using kernel context 0<br>------------------------------<wbr>--------<br><br></font></div><font face="monospace,monospace">Reboot scenario:<br>------------------------------<wbr>---------<br>root@mx6q:~# <br>root@mx6q:~# ps | grep -i match<br> 569 root 7080 S matchbox-window-manager -theme Sato -use_cursor yes<br> 621 root 174m S matchbox-desktop<br> 622 root 174m S matchbox-panel --start-applets showdesktop,windowselector --end-applets clock,battery,,systray,<wbr>startup-notify,notify<br> 652 root 2752 S grep -i match<br>root@mx6q:~# <br>root@mx6q:~# reboot<br>[ 26.234069] [drm:drm_legacy_unlock] *ERROR* Process 622 using kernel context 0<br>[ 26.247957] [drm:drm_legacy_unlock] *ERROR* Process 622 using kernel context 0<br>[ 26.261257] [drm:drm_legacy_unlock] *ERROR* Process 621 using kernel context 0<br>[ 26.268810] [drm:drm_lock_take] *ERROR* 1 holds heavyweight lock<br>------------------------------<wbr>---------<br><br></font></div><font face="monospace,monospace">Killing Xorg directly does not have any issue related to DRM lockup, but termination of matchbox session is showing up these errors. The target has DRM support and runs on accelerated graphics. <br><br></font></div><div><font face="monospace,monospace">This is not seen on "krogoth yocto-2.1" builds. <br><br></font></div><font face="monospace,monospace">Did anyone notice this on most recent core-image-sato running on DRM enabled target ?<br><br></font></div><font face="monospace,monospace">Any pointers will be much appreciated. <br><br></font></div><font face="monospace,monospace">TIA!<br></font></div>
<br>--<br>
______________________________<wbr>_________________<br>
Openembedded-core mailing list<br>
<a href="mailto:Openembedded-core@lists.openembedded.org">Openembedded-core@lists.<wbr>openembedded.org</a><br>
<a href="http://lists.openembedded.org/mailman/listinfo/openembedded-core" rel="noreferrer" target="_blank">http://lists.openembedded.org/<wbr>mailman/listinfo/openembedded-<wbr>core</a><br>
<br></blockquote></div><br></div></div></div></div></div></div></div>