Re: fsl-community-bsp (master): fsl-image throws error: "drm_lock_take] *ERROR* 1 holds heavyweight lock" during reboot

* Re: fsl-community-bsp (master): fsl-image throws error: "drm_lock_take] *ERROR* 1 holds heavyweight lock" during reboot
@ 2016-09-22 12:30 Shrikant Bobade
  2016-09-22 12:41 ` Otavio Salvador
  0 siblings, 1 reply; 6+ messages in thread
From: Shrikant Bobade @ 2016-09-22 12:30 UTC (permalink / raw)
  To: meta-freescale

[-- Attachment #1: Type: text/plain, Size: 6181 bytes --]

Hi,

I am also facing similar DRM lock error issue.

@Ping

Please advise updates if any.

Thanks
Shrikant

Hello Prabhu,
>
> On Fri, Aug 26, 2016 at 12:30 PM, srikanth krishnakar
> <skrishnakar@gmail.com> wrote:
> > I have been building fsl-image-multimedia master branch of
> fsl-community-bsp
> > for "imx6qsabresd" machine and all seems functional but during reboot
> > process I could see that DRM lock messages are thrown, and kernel DRM
> says
> > process using kernel context, further subsequent reboot will result in
> > reboot hang for significant amount of time. Following are the attempts
> made
> > in order to narrow down the issue and see what works and what not:
> >
> > 1.Krogoth build of fsl-community-bsp - (linux-4.1.15) -- ** WORKS **
> > 2.Downgrade Xorg-1.18.4 -> Xorg-1.18.0  -- DRM issue is seen!
> > 3.Downgrade libdrm-2.4.70 -> 2.4.67 -- DRM issue is seen!
> > 4.Downgrade XCB 1.12 -> 1.11.1  -- DRM issue is seen!
> >
> > Target: imx6qsabresd
> > Kernel: Linux imx6qsabresd 4.1.29-fslc+g59b38c3
> > Rootfs: fsl-image-multimedia-imx6qsabresd-20160826120801.
> rootfs.sdcard.gz
> >
> > Error Log:
> > ---------------------------------------------------------
> > udhcpc (v1.24.1) started
> > Sending discover...
> > Sending discover...
> > fec 2188000.ethernet eth0: Link is Up - 1Gbps/Full - flow control rx/tx
> > IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
> > Sending discover...
> > sh: a: unknown operand
> > Starting Xserver
> > sh: a: unknown operand
> > Starting system message bus: dbus.
> > Starting Dropbear SSH server: dropbear.
> > Starting rpcbind daemon...done.
> > Starting bluetooth
> > bluetoothd
> > Starting syslogd/klogd: done
> >  * Starting Avahi mDNS/DNS-SD Daemon: avahi-daemon
> >    ...done.
> > Starting Telephony daemon
> > Starting Linux NFC daemon
> > Starting autohdmi:
> >
> > Poky (Yocto Project Reference Distro) 2.1+snapshot-20160825 imx6qsabresd
> > /dev/ttymxc0
> >
> > imx6qsabresd login: root
> > root@imx6qsabresd:~#
> > root@imx6qsabresd:~# uname -a
> > Linux imx6qsabresd 4.1.29-fslc+g59b38c3 #1 SMP PREEMPT Fri Aug 26
> 02:32:13
> > IST 2016 armv7l GNU/Linux
> > root@imx6qsabresd:~#
> > root@imx6qsabresd:~# rpm -qa | grep xserver-xorg
> > xserver-xorg-1.18.4-r0.cortexa9hf_neon_mx6qdl
> > xserver-xorg-module-exa-1.18.4-r0.cortexa9hf_neon_mx6qdl
> > xserver-xorg-extension-viv-autohdmi-5.0.11.p8.4-r1.
> cortexa9hf_neon_mx6qdl
> > xserver-xorg-extension-glx-1.18.4-r0.cortexa9hf_neon_mx6qdl
> > root@imx6qsabresd:~#
> > root@imx6qsabresd:~#
> > root@imx6qsabresd:~# rpm -qa | grep xserver-xorg-1
> > xserver-xorg-1.18.4-r0.cortexa9hf_neon_mx6qdl
> > root@imx6qsabresd:~# rpm -qa | grep libdrm
> > libdrm2-2.4.70-r0.cortexa9hf_neon_mx6qdl
> > root@imx6qsabresd:~# rpm -qa | grep vivante
> > libvivante-dri-mx6-5.0.11.p8.4+hfp-r0.cortexa9hf_neon_mx6qdl
> > xf86-video-imxfb-vivante-5.0.11.p8.4-r1.cortexa9hf_neon_mx6qdl
> > root@imx6qsabresd:~#
> > root@imx6qsabresd:~# lsmod | grep -i galcore
> > galcore               225044  4
> > root@imx6qsabresd:~#
> > root@imx6qsabresd:~# dmesg | grep -i drm
> > [drm] Initialized drm 1.1.0 20060810
> > [drm] Initialized vivante 1.0.0 20120216 on minor 0
> > root@imx6qsabresd:~#
> > root@imx6qsabresd:~# dmesg | grep -i fb
> > Kernel command line: console=ttymxc0,115200 root=/dev/mmcblk2p2 rootwait
> rw
> > video=mxcfb0:dev=hdmi,1280x720M@60,if=RGB24
> > video=mxcfb1:dev=ldb,LDB-XGA,if=RGB666
> > video=mxcfb2:dev=lcd,CLAA-WVGA,if=RGB666
> > fbcvt: 1280x720@60: CVT Name - .921M9
> > mxc_sdc_fb fb@0: registered mxc display driver hdmi
> > mxc_sdc_fb fb@1: registered mxc display driver ldb
> > mxc_sdc_fb fb@2: registered mxc display driver lcd
> > mxc_sdc_fb fb@2: ipu0-di0 already in use
> > mxc_sdc_fb: probe of fb@2 failed with error -16
> > mxc_sdc_fb fb@3: registered mxc display driver ldb
> > root@imx6qsabresd:~#
> >
> > root@imx6qsabresd:~# ps | grep -i match
> >   476 root      7100 S    matchbox-window-manager
> >   502 root      193m S    matchbox-terminal
> >   536 root      2736 S    grep -i match
> > root@imx6qsabresd:~#
> > root@imx6qsabresd:~# reboot
> >
> > The system is going down for reboot NOW! (ttymxc0) (Fri Aug 26 14:56:28
> > 2016)
> > INIT: Switching to runlevel: 6
> > INIT: Sending processes the TERM signal
> > Stopping XServer
> > [drm:drm_legacy_unlock] *ERROR* Process 502 using kernel context 0
> > <<<<<<< ERROR  <<<<<
> > [drm:drm_lock_take] *ERROR* 1 holds heavyweight lock
> > <<<<<<< ERROR  <<<<<
> > ---------------------------------------------------------
> >
> > The process-id mentioned by DRM is none other than matchbox-terminal, so
> > killing matchbox terminal would also result in the same error when
> system is
> > up and running as seen below:
> >
> > ---------------------------------------------------------
> > root@imx6qsabresd:~# ps | grep -i Xorg
> >   428 root      3240 S    xinit /etc/X11/Xsession -- /usr/bin/Xorg -br
> -pn
> > -nolisten tcp
> >   431 root      158m S <  /usr/bin/Xorg :0 -br -pn -nolisten tcp
> >   611 root      2736 S    grep -i Xorg
> > root@imx6qsabresd:~#
> > root@imx6qsabresd:~# ps | grep -i matchbox
> >   479 root      7100 S    matchbox-window-manager
> >   505 root      193m S    matchbox-terminal
> >   614 root      2736 S    grep -i matchbox
> > root@imx6qsabresd:~#
> > root@imx6qsabresd:~# kill 505
> > root@imx6qsabresd:~# [drm:drm_legacy_unlock] *ERROR* Process 505 using
> > kernel context 0     <<<<< ERROR  <<<<<
> > ---------------------------------------------------------
> >
> > Did anyone test latest fsl-community-bsp (master) builds with
> > fsl-image-multimedia ? Could anyone confirm this behavior on imx6 with
> X11
> > graphics running ? I have not tested wayland part though.
> >
> > Any pointers and comments would be much appreciated.
>
> Does it sounds any bell?
>
>
> --
> Otavio Salvador                             O.S. Systems
> http://www.ossystems.com.br        http://code.ossystems.com.br
> Mobile: +55 (53) 9981-7854            Mobile: +1 (347) 903-9750
>

[-- Attachment #2: Type: text/html, Size: 7682 bytes --]

^ permalink raw reply	[flat|nested] 6+ messages in thread