Running Torizon OS 7.1.0+build.4 + torizon/weston-imx8:4.4.0 on Verdin iMX8M-Plus I can see a lot of messages like these ones:
g2d_blitEx: Invalid src rect, left 0, top 0, right 0, bottom 0, width 0, height 0, stride 0!
[16:46:01.772] SRC: physicAddr = 0 left = 0 right = 0 top=0 bottom=0 stride= 0 tiling = 0, format=0
[16:46:01.772] DST: physicAddr = afb00000 left = 0 right = 1024 top=0 bottom=768 stride= 1920 tiling = 1, format=4
g2d_blitEx: Invalid src rect, left 0, top 0, right 0, bottom 0, width 0, height 0, stride 0!
[16:46:01.838] SRC: physicAddr = 0 left = 0 right = 0 top=0 bottom=0 stride= 0 tiling = 0, format=0
[16:46:01.838] DST: physicAddr = b0300000 left = 0 right = 1024 top=0 bottom=768 stride= 1920 tiling = 1, format=4
g2d_blitEx: Invalid src rect, left 0, top 0, right 0, bottom 0, width 0, height 0, stride 0!
[16:46:01.896] SRC: physicAddr = 0 left = 0 right = 0 top=0 bottom=0 stride= 0 tiling = 0, format=0
[16:46:01.896] DST: physicAddr = af300000 left = 0 right = 1024 top=0 bottom=768 stride= 1920 tiling = 1, format=4
...
They’re the same messages I reported in this topic some months ago - the topic was for another main issue
The answer frpom @bruno.tx on the logs was
I though that they would have been fixed in next versions of torizon/weston-imx8 but they’re there.
What is the main reason for them?
Have they some eimpact on my application?
Hi, I’m the Toradex AI Assistant. The Toradex Support team will follow up with you shortly!
Did you like my answer?
Hello,
Thank you for reaching out with your question about the ‘g2d blitex’ messages in the Weston logs on your Verdin iMX8M Plus. While I don’t have specific information about these log messages, I can confirm that you are using the correct Weston container for your hardware, as the Verdin iMX8M Plus requires the weston-vivante container.
For general troubleshooting with Weston, you can monitor the logs by using the following command:
docker logs weston
This command will help you gather more information about what might be happening in your system. If you are looking to further investigate or configure Weston, you might consider exploring the Weston configuration files or reviewing the documentation for any additional settings that could be relevant.
If you have any more questions or need further assistance, feel free to ask!
Best regards,
Toradex AI Assistant.
Please, also check if these links can help you solve your problem:
I see the same messages when using the more recent stable-rc tags either. Let me ask our team for clarification on what these log messages entail. Though I don’t believe they’re anything inherently harmful.
After discussing with the team, this seems to be an NXP issue.
To explain, that g2d* log message comes from the proprietary library shipped by NXP. In our containers we are simply packaging and installing these libraries as is from NXP.
We can’t really comment further on what’s going on in the library itself that is causing these messages, since as I said these are proprietary libraries.
The team can confirm we have this commit that NXP is referring to. That said, we have no further knowledge about these log messages. What we can say currently is that we simply integrate the libraries, packages, and such from NXP directly. We do observe these log messages, but as far as we can see in our own testing these log messages do not seem to correlate to any issues. Therefore it’s hard for us to justify investigation of these log messages in the near future.
If you do find an issue with these log messages related to your use-case, then we are happy to review any contributions you can make to our containers repository.
Hi @jeremias.tx
thanks for your answer.
I understand it, and it’s not Toradex that can investigate what comes from NXP.
Can you answer to the question that is relevant for NXP support?
which NXP BSP is included in the weston container torizon/weston-imx8:4.4.0 ?
which NXP BSP is included in the weston container torizon/weston-imx8:4.4.0 ?
We follow the NXP BSP they use in Yocto Scarthgap. Which is NXP BSP verson “6.6.52_2.2.0”. For example the version of weston-imx in our containers is “12.0.4”. Which matches the version of weston-imx that NXP uses in their “6.6.52_2.2.0” BSP.
Even though in Torizon OS packages like weston-imx live inside the container rather than on the OS, we still match the versions because things like GPU drivers and such are still on the OS. So we try to match versions of things in and outside of the container to avoid issues related to mixing versions of things that NXP did not release together.
