• State
  • Locked Locked
  • Replies 6 replies
  • Subscribers 98 subscribers
  • Views 506 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

AM5728: am57xx-evm kernel warning around omapdrm on boot

Nathan Wright
Intellectual 782 points

Part Number: AM5728
Other Parts Discussed in Thread: TPD12S015

Tool/software:

Hello,

I am getting the following kernel warning on boot using SDK 9.3.6.5 with an am57xx-evm.

[    9.783416] omapdrm omapdrm.0: [drm] fb0: omapdrmdrmfb frame buffer device
[    9.954925] ------------[ cut here ]------------
[    9.959594] WARNING: CPU: 0 PID: 142 at drivers/gpu/drm/drm_bridge.c:1416 drm_bridge_hpd_enable+0x7c/0x80
[    9.969268] Hot plug detection already enabled
[    9.973724] Modules linked in: omapdrm(+) snd_soc_simple_card snd_soc_simple_card_utils pwm_fan cec omap_aes_driver libaes icss_iep ahci_dwc omap_wdt omap_hwspinlock ti_vpe ti_vip ti_sc ti_csc v4l2_mem2mem ti_vpdma videobuf2_dma_contig v4l2_fwnode v4l2_async videobuf2_memops videobuf2_v4l2 videobuf2_common videodev dwc3_omap mc rtc_omap snd_soc_davinci_mcasp snd_soc_ti_udma snd_soc_ti_edma snd_soc_ti_sdma pwm_tiehrpwm omap_des omap_crypto libdes snd_soc_tlv320aic3x_i2c snd_soc_tlv320aic3x snd_soc_core snd_pcm_dmaengine ac97_bus snd_pcm snd_timer snd extcon_palmas soundcore omap_sham crypto_engine omap_remoteproc display_connector ti_tpd12s015 cryptodev(O)
[   10.032348] CPU: 0 PID: 142 Comm: systemd-udevd Tainted: G           O       6.1.119-ti-ge4e8b16e66f5 #1
[   10.041870] Hardware name: Generic DRA74X (Flattened Device Tree)
[   10.048004]  unwind_backtrace from show_stack+0x10/0x14
[   10.053283]  show_stack from dump_stack_lvl+0x40/0x4c
[   10.058349]  dump_stack_lvl from __warn+0x7c/0x158
[   10.063171]  __warn from warn_slowpath_fmt+0x124/0x1c0
[   10.068359]  warn_slowpath_fmt from drm_bridge_hpd_enable+0x7c/0x80
[   10.074676]  drm_bridge_hpd_enable from pdev_probe+0x5e8/0x788 [omapdrm]
[   10.081512]  pdev_probe [omapdrm] from platform_probe+0x5c/0xbc
[   10.087554]  platform_probe from really_probe+0xc8/0x2ec
[   10.092895]  really_probe from __driver_probe_device+0x88/0x1a0
[   10.098846]  __driver_probe_device from driver_probe_device+0x30/0x104
[   10.105407]  driver_probe_device from __driver_attach+0x90/0x174
[   10.111450]  __driver_attach from bus_for_each_dev+0x74/0xc0
[   10.117156]  bus_for_each_dev from bus_add_driver+0x164/0x1f0
[   10.122924]  bus_add_driver from driver_register+0x88/0x11c
[   10.128509]  driver_register from __platform_register_drivers+0x38/0x88
[   10.135162]  __platform_register_drivers from omap_drm_init+0x3c/0x50 [omapdrm]
[   10.142639]  omap_drm_init [omapdrm] from do_one_initcall+0x48/0x254
[   10.149108]  do_one_initcall from do_init_module+0x44/0x1d4
[   10.154724]  do_init_module from sys_finit_module+0xc0/0x110
[   10.160430]  sys_finit_module from __sys_trace_return+0x0/0x10
[   10.166290] Exception stack(0xf1e8dfa8 to 0xf1e8dff0)
[   10.171356] dfa0:                   00000000 00000000 00000011 b6daa878 00000000 00020000
[   10.179595] dfc0: 00000000 00000000 00000000 0000017b 00000000 00092450 00000007 00000000
[   10.187805] dfe0: bea21710 bea21700 b6da5d2f b6cdb052
[   10.192962] ---[ end trace 0000000000000000 ]---
[   10.475341] [drm] Initialized omapdrm 1.0.0 20110917 for omapdrm.0 on minor 0

It doesn't appear to have any negative effects (yet).  Is something else (other than omapdrm) setting up the GPU before omap does?

Thanks,

Nathan

  • 0
    TI__Guru**** 171290 points

    Hello Nathan,

    Could you confirm that this comes up with the default SDK? No custom changes made on top? 

    Best Regards,

    Keerthy

  • 0 in reply to Keerthy J
    Intellectual 782 points

    Hi Keerthy,

    We are using arago.  Our config is the same as the 9.3.6.5 SDK. I have included it here for completeness...

    # This file takes repo entries in the format
# repo name,repo uri,repo branch,repo commit[,layers=layer1:layer2...:layern]

bitbake,https://git.openembedded.org/bitbake,2.0,3f88b005244a0afb5d5c7260e54a94a453ec9b3e
meta-arago,https://git.yoctoproject.org/meta-arago,kirkstone,f8ad2232a4e52b50aecc6c847ee7cfa24fc84070,layers=meta-arago-distro:meta-arago-extras:meta-arago-demos:meta-arago-test
#meta-browser,https://github.com/OSSystems/meta-browser.git,master,d3d16b47e17dc899e5298cff698dc32e5e639ab4,layers=meta-chromium
meta-qt5,https://github.com/meta-qt5/meta-qt5.git,kirkstone,644ebf220245bdc06e7696ccc90acc97a0dd2566,layers=
meta-virtualization,https://git.yoctoproject.org/meta-virtualization,kirkstone,a055d7dcafc58855081a5eac9a46b93b9b51012b,layers=
meta-openembedded,https://git.openembedded.org/meta-openembedded,kirkstone,7b3fdcdfaab2fc964bbf9eec2cce4e03001fa8cf,layers=meta-networking:meta-python:meta-oe:meta-gnome:meta-filesystems
meta-ti,https://git.yoctoproject.org/meta-ti,kirkstone,417233481d8daa46633045fac358260d07cf1670,layers=meta-ti-extras:meta-ti-bsp
meta-arm,https://git.yoctoproject.org/meta-arm,kirkstone,936c02ec13661bd86a05f7f90e1b920d5092d670,layers=meta-arm:meta-arm-toolchain
meta-clang,https://github.com/kraj/meta-clang,kirkstone-clang12,c2e89dc7e1dfcc1bbe432afca2dc43d6560cb007,layers=
oe-core,https://git.openembedded.org/openembedded-core,kirkstone,e42b6a40a3a01e328966bb5ee1bb3e0993975b15,layers=meta

OECORELAYERCONF=./sample-files/bblayers.conf.sample
OECORELOCALCONF=./sample-files/local-arago64-v2.conf.sample
BITBAKE_INCLUSIVE_VARS=yes

meta-tisdk,https://git.ti.com/git/ti-sdk-linux/meta-tisdk.git,am57x-9.x,0eed214c0ff621f4d03700a647a1b4f1a02b5a7c,layers=
meta-swupdate,https://github.com/sbabic/meta-swupdate.git,kirkstone,HEAD,layers=

# Set extra configs in local.conf
LOCALCONF:TOOLCHAIN_HOST_TASK:apppend = " nativesdk-cmake nativesdk-ninja "
LOCALCONF:INHERIT           += " rm_work"
LOCALCONF:RM_WORK_EXCLUDE += " swupdate-cert "
#LOCALCONF:INHERIT           += " archiver"
#LOCALCONF:ARCHIVER_MODE[src] = "original"
LOCALCONF:# Add http/https protocol as possible git mirror to handle github deprecating the git: protocol
LOCALCONF:PREMIRRORS:append = " git://.*/.* git://HOST/PATH;protocol=https \n git://.*/.* git://HOST/PATH;protocol=http \n"
LOCALCONF:# Ignore QA errors for version going backwards, the docker builds seem to trip this every build.
LOCALCONF:## As long as we aren't creating a package repo, versions going backwards is fine.
LOCALCONF:ERROR_QA:remove = "version-going-backwards"

    We add in two layers...

    • meta-swupdate
    • meta-adbsg (our layer)

    We have two images that exhibit the behavior, one for SD and one for eMMC, both modeled on what you guys have in the SDK.

    One could describe the images accordingly...

    • emmc image
      • requires recipes-core/images/arago-image.inc
      • adds in
        • packagegroup-arago-base
        • packagegroup-arago-console
        • psplash
        • pru-icss
        • libegl
        • glmark2
        • packagegroup-arago-tisdk-crypto
        • gdbserver
        • ptpd
        • libdrm-kms
    • sd emmc flasher image
      • requires recipes-core/images/arago-image.inc
      • adds in
        • packagegroup-arago-base
        • packagegroup-arago-console
        • emmc-flash (our script recipe)
        • mmc-utils

    The warning comes out on both images.  If you remove our flasher script and mmc-utils, our sd card image is near identical to tisdk-base-image.

    Thanks,

    Nathan

  • 0 in reply to Keerthy J
    Intellectual 782 points

    Hi Keerthy, I replied but it flagged it as spam.  Can you recover my reply or do I need to resubmit it?

  • 0 in reply to Nathan Wright
    TI__Mastermind 41586 points

    Hi Nathan, 

    Yes, you would have to re-submit. did you have lots of links on it?

    I have seen this and a JIRA has been created for it. I have not seen any display fail yet because of this. Nonetheless, we are trying to fix the warning.

    -Josue

  • 0 in reply to Josue Zamitiz-Ayala
    Intellectual 782 points

    Ok, well here is the abbreviated repeat of my reply...

    • We are using arago at 9.3.6.5
    • We are building 2 images, one with graphics added manually (emmc one).
    • SD card image is the emmc flasher and is essentially a tisdk-base-image.bb plus a script
    • Both images display the warning

    So is the response that it is safe to ignore this warning?

    Thanks,

    Nathan

  • 0 in reply to Nathan Wright
    TI__Mastermind 41586 points

    Nathan,

    I do not know that I can say 

    Nathan Wright said:
    is safe to ignore this warning

    but, it has not shown any negative effects on display testing so far.

    -Josue