• State
  • Locked Locked
  • Replies 6 replies
  • Subscribers 98 subscribers
  • Views 1729 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.

PVR GPU errors

Kiran Chandramohan
Prodigy 220 points


Hi,

I was trying android on the omap5 board to do some OpenCL programming with the PVR GPU. I am getting some errors when android boots up. The relevant errors are given below. I have also given the entire boot log as attachment. I am using prebuilit images available from the following location.
http://software-dl.ti.com/omap/omap5/omap5_public_sw/OMAP5432-EVM/5AJ_1_5_1_Release/index_FDS.html

PVR_K:(Error): PVRSRVOpenDCDeviceKM: no devnode matching index 0 [0, ]
PVR_K:(Error): PVRSRVOpenDCDeviceKM: no devnode matching index 0 [0, ]
PVR_K:(Error): PVRSRVOpenDCDeviceKM: no devnode matching index 0 [0, ]
PVR_K:(Error): PVRSRVOpenDCDeviceKM: no devnode matching index 32 [0, ]
PVR_K:(Error): PVRSRVOpenDCDeviceKM: no devnode matching index 0 [0, ]

Is there some changes required to get the PVR GPU working ?

--Kiran

  • 0
    TI__Genius 10965 points

    Hi Kiran,

    Can you try insmoding the pvr kernel modules and see  if it is done without problem.

    Regards,

    Boyko

  • 0 in reply to Boyko Kazakov
    Prodigy 220 points

    Hello Boyko,

    Thanks for your reply.

    The only pvr kernel module that i can  find is "pvrsrvkm_sgx544_116". But this is already loaded.

    130|shell@android:/ $ lsmod
    wl18xx 64919 0 - Live 0x00000000 (O)
    wl12xx 44424 0 - Live 0x00000000 (O)
    wlcore 164350 2 wl18xx,wl12xx, Live 0x00000000 (O)
    mac80211 501361 2 wl18xx,wlcore, Live 0x00000000 (O)
    pvrsrvkm_sgx544_116 343150 60 - Live 0x00000000 (O)
    cfg80211 184905 3 wl18xx,wlcore,mac80211, Live 0x00000000 (O)
    compat 3353 4 wl18xx,wl12xx,mac80211,cfg80211, Live 0x00000000 (O)

    When I try to remove the module, it fails. Hence i cannot reinsert this module.

    127|shell@android:/ $ rmmod pvrsrvkm_sgx544_116
    rmmod: delete_module 'pvrsrvkm_sgx544_116' failed (errno 1)

    --Kiran

  • 0 in reply to Kiran Chandramohan
    TI__Genius 10965 points

    Hmm, the SGX module is build in the android system and it should be running flawlessly right after flash. You may try re-flashing the system and compare the boot logs.

    Have you made any changes to the kernel sources ( or different versions of the  softuere sources written in the release note)? And also what configuration is used ( is HDMI or DSI display used with the board, because i  noticed strange logs about the hdmi connection)? And also have you applied the usb patch? which it might intervene with the gpu driver initialisation.

    Regards,

    Boyko

  • 0 in reply to Boyko Kazakov
    Prodigy 220 points

    Hello Boyko,

    I have not made any changes to the kernel sources.

    I have tried with and without HDMI connected. These errors are there in both cases.

    I have not applied the usb patch.

    Can you or someone provide me with the logs of a clean boot of omap5 ?

    I am using the omap5432evm from svtronics. By default I have the network, keyboard, mouse, the debug usb and usb3.0 connected.

    I tried reflashing and it shows the same errors. The PVR logs and errors are given below. This is with a new installation without connecting HDMI or DSI.

    [ 5.842224] PVR: PVRCore_Init
    [ 5.845947] PVR: LinuxMMInit: Maximum page pool size: 10800
    [ 5.852478] PVR: PVRSRVDriverProbe(pDevice=d24ea200)
    [ 5.860504] PVR: SGX register base: 0x56000000
    [ 5.865447] PVR: SGX register size: 65535
    [ 5.869873] PVR: SGX IRQ: 53
    [ 5.874237] PVR: EnableSystemClocks: Enabling System Clocks
    [ 5.880828] PVR: PVRCore_Init: major device 246
    [ 5.920623] PVR_K:(Error): BridgedDispatchKM: Driver initialisation not completed yet. [0, ]
    [ 5.979919] PVR_K:(Error): BridgedDispatchKM: Driver initialisation not completed yet. [0, ]
    [ 6.042083] PVR_K:(Error): BridgedDispatchKM: Driver initialisation not completed yet. [0, ]
    [ 6.102142] PVR_K:(Error): BridgedDispatchKM: Driver initialisation not completed yet. [0, ]
    [ 6.161285] PVR_K:(Error): BridgedDispatchKM: Driver initialisation not completed yet. [0, ]
    [ 6.176239] PVR: Installing MISR with cookie bf08557c
    [ 6.181793] PVR: Installing device LISR SGX ISR on IRQ 53 with cookie d1faa080
    [ 6.189971] PVR: SysFinalise: Version string: SGX revision = 1.1.6
    [ 6.196746] omaplfb: OMAPLFBInitFBDev: Device 2: invalid framebuffer size
    [ 6.203887] omaplfb: OMAPLFBInitFBDev: Device 1: invalid framebuffer size
    [ 6.270294] PVR_K:(Error): PVRSRVOpenDCDeviceKM: no devnode matching index 0 [0, ]
    [ 29.194824] PVR_K:(Error): PVRSRVOpenDCDeviceKM: no devnode matching index 32 [0, ]
    [ 30.389709] PVR_K:(Error): PVRSRVOpenDCDeviceKM: no devnode matching index 0 [0, ]
    [ 96.575408] PVR_K:(Error): PVRSRVOpenDCDeviceKM: no devnode matching index 0 [0, ]


    I see some messages about ldisc uninstallation on the first boot as given below. These disappear the second time I boot.

    [ 31.169128] (stc): st_register(4)
    [ 31.172607] (stc): chnl_id list empty :4
    [ 31.176849] (stk) : st_kim_start
    [ 33.415130] (stk) :ldisc_install = 1
    [ 34.415161] (stk) :ldisc installation timeout
    [ 34.419799] (stk) :ldisc_install = 0
    [ 35.422943] (stk) : timed out waiting for ldisc to be un-installed
    [ 35.540130] (stk) :ldisc_install = 1
    [ 42.917541] (stk) :ldisc installation timeout
    [ 42.922149] (stk) :ldisc_install = 0
    [ 43.925018] (stk) : timed out waiting for ldisc to be un-installed
    [ 43.933227] (hci_tty): st_register failed -22

    --Kiran

  • 0 in reply to Kiran Chandramohan
    TI__Genius 10965 points

    Hi Kiran,

    I recommend you remove all peripherals connected to the device and leave only  the  serial cable( in case if some driver routine is called it intervenes with the sgx  initialisation).

    About the second problem is it observed when the wifi drivers are  included?

    Regards,
    Boyko

  • 0 in reply to Boyko Kazakov
    Prodigy 220 points

    Hello Boyko,

    I removed all the peripherals except for the USB 3.0 and i still get the same errors.

    If I remove the USB3.0 wire then I get some errors(as given at the end of this mail).

    I dont know whether the second problem is when wifi drivers are included. I am using the prebuilt images without any changes. The following modules are listed with lsmod command.

    shell@android:/ # lsmod
    wl18xx 64919 0 - Live 0x00000000 (O)
    wl12xx 44424 0 - Live 0x00000000 (O)
    wlcore 164350 2 wl18xx,wl12xx, Live 0x00000000 (O)
    mac80211 501361 2 wl18xx,wlcore, Live 0x00000000 (O)
    pvrsrvkm_sgx544_116 343150 68 - Live 0x00000000 (O)
    cfg80211 184905 3 wl18xx,wlcore,mac80211, Live 0x00000000 (O)
    compat 3353 4 wl18xx,wl12xx,mac80211,cfg80211, Live 0x00000000 (O)

    --Kiran

    [ 207.513183] PM: Syncing filesystems ... done.
    [ 207.518280] Freezing user space processes ... (elapsed 0.02 seconds) done.
    [ 207.551025] Freezing remaining freezable tasks ... (elapsed 0.02 seconds) done.
    [ 207.582244] Suspending console(s) (use no_console_suspend to debug)
    [ 207.611755] PVR: PVRSRVDriverSuspend(pDevice=d24ea200)
    [ 207.611755] PVR: SysSystemPrePowerState: Entering state D3
    [ 207.611755] PVR: Uninstalling device LISR on IRQ 53 with cookie d182b5c0
    [ 207.611785] PVR: DisableSystemClocks: Disabling System Clocks
    [ 207.617584] PM: suspend of devices complete after 28.383 msecs
    [ 207.617767] PM: late suspend of devices complete after 0.163 msecs
    [ 207.618164] omap_device: omapdss_dpi: omap_device not built
    [ 207.618469] PM: noirq suspend of devices complete after 0.699 msecs
    [ 207.618469] Disabling non-boot CPUs ...
    [ 207.627044] CPU1: shutdown
    [ 207.627532] Powerdomain (core_pwrdm) didn't enter target state CSWR (achieved=ON current=ON saved=ON)
    [ 207.627532] Powerdomain (emu_pwrdm) didn't enter target state OFF (achieved=ON current=ON saved=OFF)
    [ 207.627532] Could not enter target state in pm_suspend
    [ 207.627532] At Resume pending I/O pad: Reg - 0x4A002A10, CONTROL_PADCONF_WAKEUPEVENT_5[25]
    [ 207.627532] Suspended for 9.727 seconds
    [ 207.627563] wakeup wake lock: alarm
    [ 207.627624] Enabling non-boot CPUs ...
    [ 207.644012] CPU1: Booted secondary processor
    [ 207.644042] CPU1: Unknown IPI message 0x1
    [ 207.644348] CPU1 is up
    [ 207.644805] omap_device: omapdss_dpi: omap_device not built
    [ 207.644836] dpm_run_callback(): _od_resume_noirq+0x0/0x84 returns -19
    [ 207.644836] PM: Device omapdss_dpi failed to resume noirq: error -19
    [ 207.645080] PM: noirq resume of devices complete after 0.707 msecs
    [ 207.645446] PM: early resume of devices complete after 0.140 msecs
    [ 207.830200] dmm dmm: omap_dmm_resume: omap_dmm_resume:PAT entries restored
    [ 207.830261] PVR: PVRSRVDriverResume(pDevice=d24ea200)
    [ 207.830261] PVR: SysSystemPostPowerState: Entering state D0
    [ 207.830291] PVR: EnableSystemClocks: Enabling System Clocks
    [ 207.830291] PVR: Installing device LISR SGX ISR on IRQ 53 with cookie d182b5c0
    [ 207.939453] PM: resume of devices complete after 294.005 msecs
    [ 208.123504] Restarting tasks ...
    [ 208.132263] done.
    [ 208.134460] suspend: exit suspend, ret = 0 (2000-01-15 00:07:07.454782135 UTC)
    [ 208.670959] omap_hsmmc omap_hsmmc.2: Timeout waiting on controller reset in omap_hsmmc_reset_controller_fsm
    [ 208.684875] omap_hsmmc omap_hsmmc.2: Timeout waiting on controller reset in omap_hsmmc_reset_controller_fsm
    [ 208.704803] omap_hsmmc omap_hsmmc.2: Timeout waiting on controller reset in omap_hsmmc_reset_controller_fsm
    [ 208.718719] omap_hsmmc omap_hsmmc.2: Timeout waiting on controller reset in omap_hsmmc_reset_controller_fsm
    [ 208.732604] omap_hsmmc omap_hsmmc.2: Timeout waiting on controller reset in omap_hsmmc_reset_controller_fsm
    [ 208.747406] omap_hsmmc omap_hsmmc.2: Timeout waiting on controller reset in omap_hsmmc_reset_controller_fsm
    [ 208.761322] omap_hsmmc omap_hsmmc.2: Timeout waiting on controller reset in omap_hsmmc_reset_controller_fsm
    [ 208.775238] omap_hsmmc omap_hsmmc.2: Timeout waiting on controller reset in omap_hsmmc_reset_controller_fsm
    [ 208.789123] omap_hsmmc omap_hsmmc.2: Timeout waiting on controller reset in omap_hsmmc_reset_controller_fsm
    [ 208.803039] omap_hsmmc omap_hsmmc.2: Timeout waiting on controller reset in omap_hsmmc_reset_controller_fsm
    [ 208.814636] omap_hsmmc omap_hsmmc.2: Timeout waiting on controller reset in omap_hsmmc_reset_controller_fsm
    [ 208.826232] omap_hsmmc omap_hsmmc.2: Timeout waiting on controller reset in omap_hsmmc_reset_controller_fsm
    [ 208.838226] PM: Syncing filesystems ... done.
    [ 208.843383] Freezing user space processes ... (elapsed 0.02 seconds) done.
    [ 208.871368] Freezing remaining freezable tasks ... (elapsed 0.02 seconds) done.
    [ 208.902587] Suspending console(s) (use no_console_suspend to debug)