All of lore.kernel.org
 help / color / mirror / Atom feed
* 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
* Re: fsl-community-bsp (master): fsl-image throws error: "drm_lock_take] *ERROR* 1 holds heavyweight lock" during reboot
  2016-09-22 12:30 fsl-community-bsp (master): fsl-image throws error: "drm_lock_take] *ERROR* 1 holds heavyweight lock" during reboot Shrikant Bobade
@ 2016-09-22 12:41 ` Otavio Salvador
  2016-09-26  6:32   ` Shrikant Bobade
  0 siblings, 1 reply; 6+ messages in thread
From: Otavio Salvador @ 2016-09-22 12:41 UTC (permalink / raw)
  To: Shrikant Bobade; +Cc: meta-freescale

On Thu, Sep 22, 2016 at 9:30 AM, Shrikant Bobade
<bobadeshrikant@gmail.com> wrote:
> I am also facing similar DRM lock error issue.

Please try to reproduce the issue removing the 'wayland' distro
feature. So it is going to use pure X11.

-- 
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


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

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

Hi,

Please have a look, DRM lock issue reproducible without 'wayland' distro
feature.

build set-up: https://github.com/Freescale/fsl-community-bsp-platform
master branch
image: fsl-image-multimedia
customization: without 'wayland' distro, i.e. DISTRO_FEATURES_remove = "
wayland" at local.conf

build tag:

Build Configuration:
BB_VERSION        = "1.31.1"
BUILD_SYS         = "x86_64-linux"
NATIVELSBSTRING   = "Ubuntu-14.04"
TARGET_SYS        = "arm-poky-linux-gnueabi"
MACHINE           = "imx6qsabresd"
DISTRO            = "poky"
DISTRO_VERSION    = "2.1+snapshot-20160923"
TUNE_FEATURES     = "arm armv7a vfp thumb neon
callconvention-hard       cortexa9"
TARGET_FPU        = "hard"
meta
meta-poky         = "HEAD:88df0e4d5d09dadba0cb1e3139b19f9f2866d499"
meta-oe
meta-multimedia   = "HEAD:24e387aaf78bc0f68a46abb1fab3a76364804bd1"
meta-fsl-arm      = "HEAD:32d08927dd286fe2bc4b234b980431e95537f77c"
meta-fsl-arm-extra = "HEAD:27428e7308ee7cd006759d0f776c5bc63818dfac"
meta-fsl-demos    = "HEAD:07a566b613786691fdc4b917dd79a91b7d1af1a9"


DRM lock issue log:

root@imx6qsabresd:~# ps | grep match
  472 root      7100 S    matchbox-window-manager
  498 root      193m S    matchbox-terminal
  529 root      2736 S    grep match
root@imx6qsabresd:~#
root@imx6qsabresd:~# reboot

The system is going down for reboot NOW! (ttymxc0) (Fri Sep 23 11:10:05
2016)
INIT: Switching to runlevel: 6
INIT: Sending processes the TERM signal
Stopping XServer
[drm:drm_legacy_unlock] *ERROR* Process 498 using kernel context 0
 * Stopping Avahi mDNS/DNS-SD Daemon: avahi-daemon
[drm:drm_lock_take] *ERROR* 1 holds heavyweight lock
   ...done.



Please advise further pointers if any, It will be a great help.

Thanks
Shrikant


On Thu, Sep 22, 2016 at 6:11 PM, Otavio Salvador <
otavio.salvador@ossystems.com.br> wrote:

> On Thu, Sep 22, 2016 at 9:30 AM, Shrikant Bobade
> <bobadeshrikant@gmail.com> wrote:
> > I am also facing similar DRM lock error issue.
>
> Please try to reproduce the issue removing the 'wayland' distro
> feature. So it is going to use pure X11.
>
> --
> 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: 3696 bytes --]

^ permalink raw reply	[flat|nested] 6+ messages in thread
* Re: fsl-community-bsp (master): fsl-image throws error: "drm_lock_take] *ERROR* 1 holds heavyweight lock" during reboot
  2016-09-26  6:32   ` Shrikant Bobade
@ 2016-09-27  7:13     ` Shrikant Bobade
  0 siblings, 0 replies; 6+ messages in thread
From: Shrikant Bobade @ 2016-09-27  7:13 UTC (permalink / raw)
  To: Otavio Salvador; +Cc: meta-freescale

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

Hi,

@Ping

Please advise updates if any.

Thanks
Shrikant

On Mon, Sep 26, 2016 at 12:02 PM, Shrikant Bobade <bobadeshrikant@gmail.com>
wrote:

> Hi,
>
> Please have a look, DRM lock issue reproducible without 'wayland' distro
> feature.
>
> build set-up: https://github.com/Freescale/fsl-community-bsp-platform
> master branch
> image: fsl-image-multimedia
> customization: without 'wayland' distro, i.e. DISTRO_FEATURES_remove = "
> wayland" at local.conf
>
> build tag:
>
> Build Configuration:
> BB_VERSION        = "1.31.1"
> BUILD_SYS         = "x86_64-linux"
> NATIVELSBSTRING   = "Ubuntu-14.04"
> TARGET_SYS        = "arm-poky-linux-gnueabi"
> MACHINE           = "imx6qsabresd"
> DISTRO            = "poky"
> DISTRO_VERSION    = "2.1+snapshot-20160923"
> TUNE_FEATURES     = "arm armv7a vfp thumb neon
> callconvention-hard       cortexa9"
> TARGET_FPU        = "hard"
> meta
> meta-poky         = "HEAD:88df0e4d5d09dadba0cb1e3139b19f9f2866d499"
> meta-oe
> meta-multimedia   = "HEAD:24e387aaf78bc0f68a46abb1fab3a76364804bd1"
> meta-fsl-arm      = "HEAD:32d08927dd286fe2bc4b234b980431e95537f77c"
> meta-fsl-arm-extra = "HEAD:27428e7308ee7cd006759d0f776c5bc63818dfac"
> meta-fsl-demos    = "HEAD:07a566b613786691fdc4b917dd79a91b7d1af1a9"
>
>
> DRM lock issue log:
>
> root@imx6qsabresd:~# ps | grep match
>   472 root      7100 S    matchbox-window-manager
>   498 root      193m S    matchbox-terminal
>   529 root      2736 S    grep match
> root@imx6qsabresd:~#
> root@imx6qsabresd:~# reboot
>
> The system is going down for reboot NOW! (ttymxc0) (Fri Sep 23 11:10:05
> 2016)
> INIT: Switching to runlevel: 6
> INIT: Sending processes the TERM signal
> Stopping XServer
> [drm:drm_legacy_unlock] *ERROR* Process 498 using kernel context 0
>  * Stopping Avahi mDNS/DNS-SD Daemon: avahi-daemon
> [drm:drm_lock_take] *ERROR* 1 holds heavyweight lock
>    ...done.
>
>
>
> Please advise further pointers if any, It will be a great help.
>
> Thanks
> Shrikant
>
>
>
> On Thu, Sep 22, 2016 at 6:11 PM, Otavio Salvador <
> otavio.salvador@ossystems.com.br> wrote:
>
>> On Thu, Sep 22, 2016 at 9:30 AM, Shrikant Bobade
>> <bobadeshrikant@gmail.com> wrote:
>> > I am also facing similar DRM lock error issue.
>>
>> Please try to reproduce the issue removing the 'wayland' distro
>> feature. So it is going to use pure X11.
>>
>> --
>> 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: 4524 bytes --]

^ permalink raw reply	[flat|nested] 6+ messages in thread
* Re: fsl-community-bsp (master): fsl-image throws error: "drm_lock_take] *ERROR* 1 holds heavyweight lock" during reboot
  2016-08-26 15:30 srikanth krishnakar
@ 2016-08-26 19:57 ` Otavio Salvador
  0 siblings, 0 replies; 6+ messages in thread
From: Otavio Salvador @ 2016-08-26 19:57 UTC (permalink / raw)
  To: srikanth krishnakar; +Cc: meta-freescale, Prabhu Sundararaj

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


^ permalink raw reply	[flat|nested] 6+ messages in thread
* fsl-community-bsp (master): fsl-image throws error: "drm_lock_take] *ERROR* 1 holds heavyweight lock" during reboot
@ 2016-08-26 15:30 srikanth krishnakar
  2016-08-26 19:57 ` Otavio Salvador
  0 siblings, 1 reply; 6+ messages in thread
From: srikanth krishnakar @ 2016-08-26 15:30 UTC (permalink / raw)
  To: meta-freescale

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

Hello,

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.

Thanks,
Srikanth

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

^ permalink raw reply	[flat|nested] 6+ messages in thread
end of thread, other threads:[~2016-09-27  7:13 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2016-09-22 12:30 fsl-community-bsp (master): fsl-image throws error: "drm_lock_take] *ERROR* 1 holds heavyweight lock" during reboot Shrikant Bobade
2016-09-22 12:41 ` Otavio Salvador
2016-09-26  6:32   ` Shrikant Bobade
2016-09-27  7:13     ` Shrikant Bobade
  -- strict thread matches above, loose matches on Subject: below --
2016-08-26 15:30 srikanth krishnakar
2016-08-26 19:57 ` Otavio Salvador

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.