Unexplained behaviour by imx6slevk on enabling pmic

[sujay1]

I'm using an imx6slevk board with 512 MB DDR which hangs at boot time saying

EXT4-fs (mmcblk1p2): re-mounted. Opts: (null)
[ OK ] Reached target Paths.
[ OK ] Reached target Host and Network Name Lookups.
[ OK ] Listening on Journal Socket (/dev/log).
4galcore: loading out-of-tree module taints kernel.
galcore: loading out-of-tree module taints kernel.
galcore: clk_get gpu3d_clk failed, disable 3d!
galcore: clk_get gpu3d_clk failed, disable 3d!
6Galcore version 6.2.4.150331
Galcore version 6.2.4.150331
Starting Journal Service...
usb 2-1: device not accepting address 4, error -71
Starting Setup Virtual Console...
usb 2-1: device not accepting address 4, error -71
[ OK ] Mounted Kernel Debug File System.
[ OK ] Mounted Temporary Directory (/tmp).

I'm guessing its galcore that creates the problem here is there a way to avoid galcore?

on disabling I2c1 which has pmic regulators tied to it the board boos completely.

A few hours later I enbled i2c1 and flashed only the compiled kernel and dtb (no rootfs) using mfg tool this time the board boots fine and everything works fine.

Now I reflashed the images with rootfs and the board hangs again.

What could be causing this strange behavior?

[sujay1 · Accepted solution]

The issue was because of the galcore module, it was solve by blacklisting it by adding the lines

KERNEL_MODULE_PROBECONF += "galcore"
module_conf_galcore = "blacklist galcore"

and removing

KERNEL_MODULE_AUTOLOAD = "galcore"

in the recipe kernel-module-imx-gpu-viv_6.2.4.p1.2.bb

[igorpadykov]

Hi Sujay

one can try to build and run core-image-minimal (without gui, galcore ) as described

in Table 1. i.MX Yocto project images.

Regarding pmic, one can check i2c signals with oscilloscope and debug it using

sect.2.5.2 PMIC PF Regulator attached Linux Manual.

Best regards
igor
-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------

[sujay1]

Hi Igor

The problem is definitely with the galcore module found in 

/lib/modules/4.9.88-imx_4.9.88_2.0.0_ga+g5e23f9d/extra/galcore.ko

I deleted this .ko file and flashed the rootfs and the board boots fine however I can't seem to remove this module in yocto source.

I found a .bb file at

~/imx-yocto-bsp/sources/meta-fsl-bsp-release/imx/meta-bsp/recipes-kernel/kernel-module-imx-gpu-viv/kernel-module-imx-gpu-viv_6.2.4.p1.2.bb

with these lines

EXTRA_OEMAKE += "CONFIG_MXC_GPU_VIV=m"
KERNEL_MODULE_AUTOLOAD = "galcore"

on modifying either of these the rootfs build throws an error

ERROR: kernel-module-imx-gpu-viv-6.2.4.p1.2-r0 do_package: QA Issue: kernel-module-imx-gpu-viv: Files/directories were installed but not shipped in any package:
/lib
/lib/modules
/lib/modules/4.9.88-imx_4.9.88_2.0.0_ga+g5e23f9d61147
/lib/modules/4.9.88-imx_4.9.88_2.0.0_ga+g5e23f9d61147/extra
Please set FILES such that these items are packaged. Alternatively if they are unneeded, avoid installing them or delete them within do_install

What is the correct way to remove this .ko file?

[igorpadykov]

Hi Sujay

one can try to change gpu driver usage using sect.5.1.2.4 Menu Configuration Options

attached Linux Manual.

Best regards
igor