[Bug 33867] [bisected] Graphics corruption related to pageflip ioctl support in 2.6.38-rc*
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Thu Feb 3 19:46:40 PST 2011
https://bugs.freedesktop.org/show_bug.cgi?id=33867
--- Comment #2 from Dave Witbrodt <dawitbro at sbcglobal.net> 2011-02-03 19:46:40 PST ---
To determine whether I goofed something up with the kernel I described in my
preliminary report, I built kernels from the drm-airlied/drm-fixes git tree
corresponding to the important commits in the bisection process:
1. f5a8020903932624cf020dc72455a10a3e005087
drm/kms/radeon: Add support for precise vblank timestamping.
2. 6f34be50bd1bdd2ff3c955940e033a80d05f248a
drm/radeon/kms: add pageflip ioctl support (v3)
3. 147666fb3b93b8c484f562da33a37f886ddff768
drm/radeon: Use the ttm execbuf utilities
4. 1e644d6dce366a7bae22484f60133b61ba322911
drm/radeon/kms: re-emit full context state for evergreen blits
Kernel #1 was identified by 'git bisect' as the last "good" kernel, while
kernel #2 was the first "bad" kernel (hangs 'prboom-plus'). During the
bisection, I found that several commits after kernel #2, the the problem with
the test program hanging was resolved, but melt/fade effect when playing again
after being killed was now all black; the first commit which caused this change
was #3. (Kernel #4 is simply the kernel I tried first, where I first noticed
the problem with the black melts/fades.)
Today I built kernels directly from drm-airlied/drm-fixes (instead of the drawn
out process I used before). Here is a table comparing the results from my
preliminary report and my builds directly from drm-fixes:
Kernel # Preliminary drm-fixes
-------- ----------- -----------
1 OK OK
2 hangs hangs
3 black fades OK
4 black fades black fades
The difference in case #3 is baffling. It is possible that I missed some
important commit(s) when trying to cherry-pick the relevant stuff into stable
2.6.37; however, those first 3 kernels (when taken from drm-fixes) are actually
based on 2.6.37-rc{2,3}, so the rest of the kernel was very different from the
stable 2.6.37 sources I was adding cherry-picks to.
At any rate, it looks like the hangs were resolved in the commits between #2
and #3. This suggests that I can bisect drm-fixes and find the commit that
introduced the black fades/melts in prboom-plus. I have not attempted that
yet, but I will do so now.
I also discovered that the kernels with the black fades/melts dump messages
like this into dmesg (and syslog):
[drm:radeon_cs_ioctl] *ERROR* Failed to parse relocation -35!
That looks significant: none of the other kernels exhibit that behavior. (Off
to bisecting again....)
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
More information about the dri-devel
mailing list