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.

TDA4VE-Q1: High IO wait and PVR log

Part Number: TDA4VE-Q1

Tool/software:

Hi expert,

Our customer using TDA4VE is observing high “IO Wait” on the system. After checking the dmesg logs, they found that PVR log are printed at the same time when high IO Wait occurs.

Could you please help to check if there is a correlation between the high IO Wait and the PVR log? We are suspecting GPU operations are causing to IO Wait. Thank you

dmesg_0610.txt

Best Regards,

Xingyu Zhu

  • Another question is that after multiple tests, I found that this type of log sometimes appears and sometimes does not appear. Why is it a probabilistic event? Is there any problem with this?

  • Hi Xingyu.,

    Our GPU expert is currently on vacation. Please expect a delayed response on this thread.

    Could you please help to check if there is a correlation between the high IO Wait and the PVR log? We are suspecting GPU operations are causing to IO Wait.

    In general, these should be unrelated. I see this during boot-log, I suspect an issue with one of the offending peripherals. You may want to retry the boot by not loading the GPU module (either blacklist the module in your rootfs, or rename the kernel module name).

    What are you running in your file-system that is exercising GPU during the boot?

    In anycase, this may not be a GPU issue.

    regards

    Suman

  • Hi 

                  The printed log is in the pvr driver. If you don't load this ko file, there will definitely be no log.

  • Hi Gaston, 

    Apologies for the delay, I was out of office and catching up on several topics. What SDK and version are you using? Are you using the default filesystem or have you made changes? 

    Before we assess, could you go through this FAQ and provide the necessary logs and information to analyze the GPU (FAQ).

    Thanks,
    Sarabesh S.