Hi, @ping,
Please advise further pointers if any. similar thread for this issue & more details @ https://lists.yoctoproject.org/pipermail/meta-freescale/2016-September/019237.html Thanks Shrikant On Thu, Sep 22, 2016 at 2:41 PM, Shrikant Bobade <bobadeshrik...@gmail.com> wrote: > Hi, > > @Ping > > Please advise further pointers if any. > > > Thanks > Shrikant > > On Thu, Aug 25, 2016 at 8:13 PM, srikanth krishnakar < > skrishna...@gmail.com> wrote: > >> Hello All, >> >> 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: >> >> Target: i.MX6Q ARM >> Kernel: Linux-4.1 >> Yocto: master (7b9f59) >> >> >> -------------------------------------- >> root@mx6q:~# ps | grep match >> 558 root 7080 S matchbox-window-manager -theme Sato -use_cursor >> yes >> 612 root 174m S matchbox-desktop >> 614 root 174m S matchbox-panel --start-applets >> showdesktop,windowselector --end-applets clock,battery,,systray,startup >> -notify,notify >> 677 root 2752 S grep match >> root@mx6q:~# >> root@mx6q:~# >> root@mx6q:~# opkg list | grep -i xserver-xorg >> xserver-xorg - 2:1.18.4-r0.3 >> xserver-xorg-extension-glx - 2:1.18.4-r0.3 >> xserver-xorg-extension-viv-autohdmi - 3:5.0.11.p8.4-r0.3 >> xserver-xorg-module-exa - 2:1.18.4-r0.3 >> root@mx6q:~# opkg list | grep -i matchbox >> matchbox-config-gtk - 0.2-r0.2 >> matchbox-desktop - 2.1-r0.2 >> matchbox-keyboard - 0.1.1-r0.2 >> matchbox-keyboard-applet - 0.1.1-r0.2 >> matchbox-keyboard-im - 0.1.1-r0.2 >> matchbox-panel-2 - 2.11-r0.2 >> matchbox-session - 0.1-r4.0 >> matchbox-session-sato - 0.1-r30.0 >> matchbox-terminal - 0.1-r0.2 >> matchbox-theme-sato - 0.2-r0.0 >> matchbox-wm - 1.2.1-r0.1 >> root@mx6q:~# >> root@mx6q:~# kill 558 >> root@mx6q:~# [ 404.937507] [drm:drm_legacy_unlock] *ERROR* Process 614 >> using kernel context 0 >> [ 404.947643] [drm:drm_lock_take] *ERROR* 1 holds heavyweight lock >> [ 404.953752] [drm:drm_legacy_unlock] *ERROR* Process 612 using kernel >> context 0 >> [ 405.132658] [drm:drm_legacy_unlock] *ERROR* Process 612 using kernel >> context 0 >> [ 405.140370] [drm:drm_legacy_unlock] *ERROR* Process 614 using kernel >> context 0 >> -------------------------------------- >> >> Reboot scenario: >> --------------------------------------- >> root@mx6q:~# >> root@mx6q:~# ps | grep -i match >> 569 root 7080 S matchbox-window-manager -theme Sato -use_cursor >> yes >> 621 root 174m S matchbox-desktop >> 622 root 174m S matchbox-panel --start-applets >> showdesktop,windowselector --end-applets clock,battery,,systray,startup >> -notify,notify >> 652 root 2752 S grep -i match >> root@mx6q:~# >> root@mx6q:~# reboot >> [ 26.234069] [drm:drm_legacy_unlock] *ERROR* Process 622 using kernel >> context 0 >> [ 26.247957] [drm:drm_legacy_unlock] *ERROR* Process 622 using kernel >> context 0 >> [ 26.261257] [drm:drm_legacy_unlock] *ERROR* Process 621 using kernel >> context 0 >> [ 26.268810] [drm:drm_lock_take] *ERROR* 1 holds heavyweight lock >> --------------------------------------- >> >> 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. >> >> This is not seen on "krogoth yocto-2.1" builds. >> >> Did anyone notice this on most recent core-image-sato running on DRM >> enabled target ? >> >> Any pointers will be much appreciated. >> >> TIA! >> >> -- >> _______________________________________________ >> Openembedded-core mailing list >> Openembedded-core@lists.openembedded.org >> http://lists.openembedded.org/mailman/listinfo/openembedded-core >> >> >
-- _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
