Summary: | Mesa DRI Intel 845G GEM Drivers returning artifacts in textures that can lockup PC on glxSwapBuffers. | ||
---|---|---|---|
Product: | Mesa | Reporter: | Jane <janedoe7236> |
Component: | Drivers/DRI/i915 | Assignee: | Default DRI bug account <dri-devel> |
Status: | RESOLVED MOVED | QA Contact: | |
Severity: | critical | ||
Priority: | medium | ||
Version: | unspecified | ||
Hardware: | x86 (IA32) | ||
OS: | Linux (All) | ||
Whiteboard: | |||
i915 platform: | i915 features: |
Description
Jane
2010-06-07 20:39:43 UTC
What does it take for a bug report to show up on the FreeDesktop Bugzilla – Bug List? Did I waste a couple hours of my life writing it just to be ignored? Did I show too many drivers at one time thereby turning into a hot-potato between various driver writers? I have never before taken the time to submit a bug-report to an open-source project and may never waste my time again if it does no good... Reassigning away from freedesktop.org, this looks like a mesa issue, not a problem with anything of the freedesktop.org infrastructure. Reassigning to i915. Probably needs to be retested. I can't see any artefacts on i915 with GM45. In fact there the rendering looks better then with the llvmpipe software renderer and r600. These two create over-bright pixels that are not present with i915. Versions tested: - i915 and llvmpipe: Mesa 13.0.6 - r600 and llvmpipe: Mesa 18.1.0-devel (git-dcd8730445 -- 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/680. |
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.