Please do not reply to this email: if you want to comment on the bug, go to
the URL shown below and enter yourcomments there.
https://bugs.freedesktop.org/show_bug.cgi?id=2078
------- Additional Comments From benh@... 2004-12-17 00:52 -------
Ok, more data. The texture problem is unrelated to the lockup. There is a
texture problem when using VLC in GL mode, the colors are wrong (and it's very
slow). Unrelated to that, there is a lockup problem when I wake up from sleep
that I isolated to beeing caused by radeonfb enabling dynamic clocks on the
card. This is the radeonfb version from my latest sleep patches (not yet
upstream). It mimmics the dynamic clocks code from X.org, but might actually be
enabling _more_ clock PM than the X code since it merges the code in X.org with
the previous code I had from ATI, which in some case did set a bit more bits
here or there.
I'll investigate that issue separately. The symptom is basically one wakeup, 3D
activity works for a second or so, and the entire card locks up. CCE-based 2D is
fine tho.
However, that shows that there is definitely one problem with the X.org dynamic
clock code and maybe two:
- The dynamic clock stuff is only done on server entry. It should be re-done on
"resume" (EnterVT) since that's typically wakeup from sleep, wether it's
actually enabling or disabling the dynamic clocks.
- I wonder if we should force some more clocks during engine reset/setup, like
we used to do even before X had any "workarounds" for dynamic clock issues. Does
the reset cycle of every engine part performs properly when dynamic clocks are
enabled ?
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
|