Hi All,
We are running Yocto L3.10.53-1.1.2_patch with wayland backend on our customized board.
We sometimes get errors when we use google-chrome.
The system sometimes hangs or only console is alive.
The console.log is dumped from console when system hangs.
The chrome_debug.log is the log that we find in chrome dir when system hangs but console is alive.
BSP: Yocto L3.10.53-1.1.2_patch with wayland backend
CPU: i.MX6Q 1.2 GHZ
RAM: 1GB
Chrome version: 40.0.2214.91
I'd appreciate any advice to solve this problem. Thanks.
Original Attachment has been moved to: console.log.zip
Original Attachment has been moved to: chrome_debug.log.zip
HI Wei-Fong
from console.log:
"1.2G chip, increase VDDARM_IN/VDDSOC_IN
Read SW1AB error!
....
pfuze100-regulator 1-0008: unrecognized pfuze chip ID!
pfuze100-regulator: probe of 1-0008 failed with error -5 "
seems you are not using pmic mmpf0100 or use ldo-bypass mode.
For 1.2GHz chip one needs to use only ldo enable option
(from i.MX_Linux_Release_Notes.pdf):
Best regards
igor
-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------
Hi igorpadykov,
Thanks for apply.
I trace the source code of chrome. I find it shows gpu out of memory error.
Then I add "--gpu-program-cache-size-kb=5242880" parameter when I start chrome.
It makes situation better.
So, my questions are
1. How do I know the current gpu memory usage ?
2. How do I increase the reserved gpu memory ?
Many Thanks,
Frank