Comment # 37
on bug 56139
from Alexandre Demers
(In reply to comment #36) > (In reply to comment #33) > > > Here is a partial kernel.log tracking what is going on at boot with some > > > debug printk in evergreen_mc_stop() and evergreen_mc_resume(). Strangely, > > > only one crtc is saved as enabled in the _stop function, but four are > > > restored in the _resume function. Pretty sure it's not the problem we are > > > looking for, but it is abnormal since only one crtc should be restored on > > > resume. This is a bug by itself showing a problem in the > > > save(stop)/restore(resume) mechanism. > > > > I should have said "... but six are restored..." instead of "... but four > > are restored..." I also made a small error in a debug string, but it doesn't > > change the read value. If you have any question on my patch, let me know. > > That issue is fixed in attachment 69573 [details] [review] [review] which is already > upstream. I know it should have been fixed and that's why I added a printk(KERN_INFO "Restoring crtc[%d] since it was enabled.\n", i) just after it to check it. For some reason it seems to not be working properly. Have a look at my patch (attachment 70233 [details]) which was written on a 3.7.0-rc6 kernel. I'll add some other printk when I'll get home (like a printk just before this check to output its value).
You are receiving this mail because:
- You are the assignee for the bug.
_______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/dri-devel
