Summary: | r600g: glx-swap-pixmap causes screen corruption | ||
---|---|---|---|
Product: | xorg | Reporter: | Kai <kai> |
Component: | Driver/Radeon | Assignee: | xf86-video-ati maintainers <xorg-driver-ati> |
Status: | RESOLVED FIXED | QA Contact: | Xorg Project Team <xorg-team> |
Severity: | normal | ||
Priority: | medium | CC: | pavel.ondracka |
Version: | git | ||
Hardware: | x86-64 (AMD64) | ||
OS: | Linux (All) | ||
Whiteboard: | |||
i915 platform: | i915 features: |
Description
Kai
2011-11-14 03:59:37 UTC
Todays run showed one difference in what was reported by Piglit:
> Probe at (0,0)
> Expected: 0.000000 1.000000 0.000000 0.000000
> Observed: 0.000000 0.000000 0.000000 1.000000
> PIGLIT: {'result': 'fail' }
apart from that, the screen is still corrupted (a KDM restart fixes the screen again; also non-X TTYs aren't affected either).
Used stack:
Mesa: Git/9d4d9d34
libdrm: 2.4.27-1
Kernel: 3.1.1
X.org: 1.11.1.902-1
does xrandr to a new mode and back help? (In reply to comment #2) > does xrandr to a new mode and back help? Yes, that restores a normal screen. AFAICT there is no vestige of the corruption left. The weekend's Piglit run showed the bug with Mesa git/03df791c. Apart from that I noticed, that this bug was assigned to dri-devel and not mesa-dev. Is that correct? This is, after all, most likely a bug in r600g and I thought Gallium driver development happened on mesa-dev. > But I'm no Mesa/Piglit expert, so my assumption might be wrong.
I have the very same issue here on evergreen, 32-bit userland on i7; debian unstable.
mesa: git 2eafd07323891944b9c012a17359cd5f07a87890 (cloned as of today)
libdrm: 2.4.29-1
kernel: 3.2-rc6
xorg: 1.11.2.902-1
(BTW, when using gnome-shell, the corruption is fixed automatically after half a second or so; using fluxbox, the screen stays corrupted.)
HTH,
Fixed in xf86-video-ati Git ae45d7e6d8e6844cd4586c9ee97c21b257fa788f ('DRI2: Can't use page flipping for pixmaps.'). |
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.