On Wed, Jun 08, 2016 at 04:47:48PM +0200, Maarten Lankhorst wrote: > Op 08-06-16 om 15:35 schreef Ville Syrjälä: > > On Wed, Jun 08, 2016 at 03:23:33PM +0200, Maarten Lankhorst wrote: > >> Op 08-06-16 om 15:12 schreef Ville Syrjälä: > >>> On Wed, Jun 08, 2016 at 01:25:32PM +0200, Maarten Lankhorst wrote: > >>>> This reduces the runtime of the tests from ~200s on my 30 fps 4k panel > >>>> to 10s. > >>> Does it still find the problem reliably on CHV pipe C (if you remove the > >>> kernel w/a)? > >> Yeah, a single coordinate is enough to trigger the fifo underrun. Rest is probably still slightly overkill. :) > > Hmm. IIRC it wasn't quite that easy to trigger on my CHV. Sometime > > it survived for a few iterations. But I'm too lazy to retest it now, > > so I'll take your word for it. > > > Weird, even kms_cursor_crc random test triggered it for me on the first try with negative coordinates. Might be that I'm only recalling the visual feedback. That is, maybe I sometimes failed to see the underrun even though it did happen. -- Ville Syrjälä Intel OTC _______________________________________________ Intel-gfx mailing list Intel-gfx@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/intel-gfx
