On Tue, Jul 21, 2020 at 05:33:00AM +0000, Sidong Yang wrote: > Hi, Daniel and Melissa > > I tested some code for this problem trying to find the code that make problem in igt test. > kms_cursor_crc test in igt test has 3 steps (preparation, test, cleanup). I check each steps > and I found that without cleanup step, the problem solved. > In cleanup step, igt test code seems like this. > > drmModeSetCrtc(display->drm_fd, crtc_id, 0 /* fb_id */, 0, > 0 /* x, y */, NULL /* connector */, 0, NULL /* mode */) > > I commented out this function call and there is no problem in executing tests repeatedly. > I'm trying to find out what's happen in this call. but don't know until now > I hope this information help to solve the problem. Ah yes that fits the evidence we have from Melissa pretty well: Not turning off the CRTC means the next test wont have to turn it back on again. And the vblank bug seems to be in the code which turns the crtc back on. At least inserting a vblank wait in there is enough to paper over all the issues, per Melissa's testing. So at least we're now fairly confident where the bug is, that's some solid progress. -Daniel -- Daniel Vetter Software Engineer, Intel Corporation http://blog.ffwll.ch _______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/dri-devel
