Bug 102368

Summary: Since Archlinux testing migrate to mesa 17.1.7, I got a pink overlay in webcam software.
Product: Mesa Reporter: Frederic Bezies <fredbezies>
Component: Drivers/DRI/nouveauAssignee: Nouveau Project <nouveau>
Status: RESOLVED MOVED QA Contact: Nouveau Project <nouveau>
Severity: normal    
Priority: medium CC: andyrtr, fdsfgs
Version: unspecified   
Hardware: Other   
OS: All   
Whiteboard:
i915 platform: i915 features:
Attachments: Pink overlay in webcam software

Description Frederic Bezies 2017-08-23 10:29:47 UTC
Created attachment 133714 [details]
Pink overlay in webcam software

I reported a bug on archlinux tracker : https://bugs.archlinux.org/task/55243

But I noticed that if I installed nvidia-340xx for my old GeForce G210 graphic card, this pink overlay is no more alive.

Here is my card : 

02:00.0 VGA compatible controller: NVIDIA Corporation GT218 [GeForce 210] (rev a2)

I noticed reverting to Mesa 17.1.6 fixed the bug, but it is not a long term solution.
Comment 1 Karol Herbst 2017-08-23 10:56:02 UTC
(In reply to Frederic Bezies from comment #0)
> Created attachment 133714 [details]
> Pink overlay in webcam software
> 
> I reported a bug on archlinux tracker : https://bugs.archlinux.org/task/55243
> 
> But I noticed that if I installed nvidia-340xx for my old GeForce G210
> graphic card, this pink overlay is no more alive.
> 
> Here is my card : 
> 
> 02:00.0 VGA compatible controller: NVIDIA Corporation GT218 [GeForce 210]
> (rev a2)
> 
> I noticed reverting to Mesa 17.1.6 fixed the bug, but it is not a long term
> solution.

would you be able to git bisect mesa to figure out the exact commit breaking it? I fear it is my saturation patch, but you never know for sure before trying.
Comment 2 Frederic Bezies 2017-08-23 11:12:11 UTC
I won't have today to do so. Sorry. Maybe tomorrow.
Comment 3 Frederic Bezies 2017-08-23 11:51:42 UTC
Another option : just give me a link to your patch I can reverse and rebuild mesa 17.1.7 without it. It will be quicker and more direct :)

Thanks!
Comment 4 Karol Herbst 2017-08-23 12:29:34 UTC
(In reply to Frederic Bezies from comment #3)
> Another option : just give me a link to your patch I can reverse and rebuild
> mesa 17.1.7 without it. It will be quicker and more direct :)
> 
> Thanks!

I will try to reproduce on my system first, but this also has to wait today.
Comment 6 Frederic Bezies 2017-08-23 14:02:03 UTC
(In reply to Ilia Mirkin from comment #5)
> https://cgit.freedesktop.org/mesa/mesa/commit/?h=17.
> 1&id=8aa358bd69862d4a88148942c85ee74048fa2561

Thanks. I'll to rebuild mesa 17.1.7 with this patch reversed asap.
Comment 7 Ilia Mirkin 2017-08-23 14:21:47 UTC
If that doesn't fix it, there were two more nouveau patches in the 17.1.7 release:

https://cgit.freedesktop.org/mesa/mesa/commit/?h=17.1&id=75ce282ee243272e937275c6d086b5a391f8ca47
https://cgit.freedesktop.org/mesa/mesa/commit/?h=17.1&id=37e61310e3673de8c23fdb1c1c5181a5e1cdc116

The rest of the patches seem harmless. But I also don't immediately see why any of these would be broken. Could well be that some "other" issue gets triggered as a result of these fixes.

Please grab an apitrace of the application that reproduces the issue. This will be required whether one of these patches is determined to be the cause or not.
Comment 8 Frederic Bezies 2017-08-24 16:36:40 UTC
Looks like it is related to archlinux toolchain. See this bug on archlinux tracker : https://bugs.archlinux.org/task/55244
Comment 9 GitLab Migration User 2019-09-18 20:45:48 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/mesa/mesa/issues/1139.

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.