| Summary: | Graphic corruption for Android apps Telegram and KineMaster | ||
|---|---|---|---|
| Product: | Mesa | Reporter: | Dmytro Chystiakov <dmytro.chystiakov> |
| Component: | Drivers/DRI/i965 | Assignee: | Jason Ekstrand <jason> |
| Status: | RESOLVED FIXED | QA Contact: | Intel 3D Bugs Mailing List <intel-3d-bugs> |
| Severity: | normal | ||
| Priority: | medium | CC: | lemody |
| Version: | 17.3 | ||
| Hardware: | x86-64 (AMD64) | ||
| OS: | Linux (All) | ||
| Whiteboard: | |||
| i915 platform: | i915 features: | ||
| Bug Depends on: | |||
| Bug Blocks: | 104757 | ||
| Attachments: |
Patch to workaround an issue
KineMaster graphic corruption Telegram graphic corruption |
||
|
Description
Dmytro Chystiakov
2018-01-22 22:17:10 UTC
Created attachment 136907 [details]
KineMaster graphic corruption
Created attachment 136908 [details]
Telegram graphic corruption
That is a very old commit (2017 Jul) while AndroidIA Mesa is rebased currently at top of commit 9ef5b3d (2018 Jan), is this a some chromium Mesa branch? I see that latest ARC branch is arc-17.3.0-rc5, have you tried to reproduce using that one? Issue is reproducible on ChromeOS and on AndroidIA. Both with 17.3 Jason's AUX series should address most of the issues. Can you rebase/retry on top of current master or df13588d2176dcf4800a882d926f389667772b46 at the very least. Unfortunately I haven't gotten a compatible version of Playstore so I can't test or even debug this .. but I haven't seen this on Android-IA GL or Vulkan apps. Just reproduced the issue on AndroidIA with MESA 17.4 and Telegram app. If you don't have the Play Store you can install it on any x86 Android device, pull apk with adb command and install it manually. Can attached patch be upstreamed before actual solution is in place? Thanks for help! > Just reproduced the issue on AndroidIA with MESA 17.4 and Telegram app. Mesa 17.4 does not exist - that's why I pointed at particular commit. Make sure your testing is based on it or later commit in the master branch. > Can attached patch be upstreamed before actual solution is in place? Thanks for help! Please send patches to the ML - see the instructions for specifics [1] Tl;Dr - base patch against master and git send-email it. You want the following (three) tags in the commit message: Cc: Jason Ekstrand <jason.ekstrand@intel.com> Fixes: be0e13e49f0 ("i965: Only call create_for_planar_image for multiple planes") BUgzilla: https://bugs.freedesktop.org/show_bug.cgi?id=104741 Thanks [1] https://www.mesa3d.org/submittingpatches.html (In reply to Dmytro Chystiakov from comment #8) > Can attached patch be upstreamed before actual solution is in place? Thanks > for help! I'd rather not if we can help it. That patch is quite drastic. Once I get done fighting with Android and can test something, I'll take a look and see if we can get a proper solution. A proper patch is on the list: https://patchwork.freedesktop.org/patch/201848/ I *should* get playstore for O today so I will testing if this happens. I've verified that patch in comment #11 fixes this bug and pushed this fix to Android-IA tree. Fixed by the following commit in master: commit 2f7205be47bbb730cdfa0a037224b9ebd5224fd1 Author: Jason Ekstrand <jason.ekstrand@intel.com> Date: Wed Jan 31 17:31:39 2018 -0800 i965: Call prepare_external after implicit window-system MSAA resolves This fixes some rendering corruption in a couple of Android apps that use window-system MSAA. Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=104741 Cc: mesa-stable@lists.freedesktop.org Reviewed-by: Tapani Pälli <tapani.palli@intel.com> |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.