Hi,
I am trying AOSP snapshot 184 [1] + UEFI snapshot 75 [2] on my HiKey board, and I'm seeing some corruption on the HDMI display [3]. OpenGLRenderer logs some 'Out of memory' errors.
Am I doing something wrong? Is this a known issue? (I found nothing in the bug tracker [4]).
I have posted the outputs of 'adbg logcat' [5] and 'adbg shell dmesg' [6], taken shortly after a clean boot.
[1] http://builds.96boards.org/snapshots/hikey/linaro/aosp/184/ [2] http://builds.96boards.org/snapshots/hikey/linaro/uefi/75/ [3] http://postimg.org/gallery/38rg8vffo/ [4] https://bugs.96boards.org/buglist.cgi?bug_status=__open__&list_id=144&am... [4] https://pastebin.linaro.org/view/8813a18f [5] https://pastebin.linaro.org/view/30dbc19b
Thanks,
Hi Jerome,
This is a known issue but a bug was not opened on this one. This is the caused by the below commit: https://github.com/96boards/linux/pull/118
A fix for this is being worked on. You can try it: diff --git a/arch/arm64/boot/dts/hi6220.dtsi b/arch/arm64/boot/dts/hi6220.dtsi index 7ffdc2b..17c0f86 100644 --- a/arch/arm64/boot/dts/hi6220.dtsi +++ b/arch/arm64/boot/dts/hi6220.dtsi @@ -993,7 +993,6 @@ mali:mali@f4080000 { compatible = "arm,mali-450", "arm,mali-utgard"; reg = <0x0 0x3f100000 0x0 0x00708000>; - dma-coherent; clocks = <&clock_media HI6220_G3D_CLK>, <&clock_media HI6220_G3D_PCLK>; clock-names = "clk_g3d", "pclk_g3d";
Hi Vishal,
On Thu, Oct 15, 2015 at 3:51 PM, Vishal Bhoj vishal.bhoj@linaro.org wrote:
Hi Jerome,
This is a known issue but a bug was not opened on this one. This is the caused by the below commit: https://github.com/96boards/linux/pull/118
A fix for this is being worked on. You can try it: diff --git a/arch/arm64/boot/dts/hi6220.dtsi b/arch/arm64/boot/dts/hi6220.dtsi index 7ffdc2b..17c0f86 100644 --- a/arch/arm64/boot/dts/hi6220.dtsi +++ b/arch/arm64/boot/dts/hi6220.dtsi @@ -993,7 +993,6 @@ mali:mali@f4080000 { compatible = "arm,mali-450", "arm,mali-utgard"; reg = <0x0 0x3f100000 0x0 0x00708000>;
- dma-coherent; clocks = <&clock_media HI6220_G3D_CLK>, <&clock_media HI6220_G3D_PCLK>; clock-names = "clk_g3d", "pclk_g3d";
-- 1.9.1
Yep, this fixes the issue! Awesome. Many thanks :)