On Sun, Apr 17, 2011 at 10:09 AM, Joerg Roedel <joro@xxxxxxxxxx> wrote: > On Sat, Apr 16, 2011 at 02:54:04PM -0400, Jerome Glisse wrote: > >> If you want to go the printk way you can add printk before each test >> ring_test, ib_test in r600.c this 2 functions are the own that might >> trigger the first GPU gart activities. > > Okay, I found the place in source that triggers this. It happens in the > function r600_ib_test. The interesting thing is that not the ib-command > itself is responsible but the fence that is emitted afterwards (proved > by removing the fence command, where the problem went away). > I don't know enough about the command semantics to make a guess what > goes wrong there. But maybe you GPU folks have an idea? > > Joerg > > I can't think of any theory, at that point the wb, irq ring, cp buffer & ib pool are all allocated and pinned into gtt so they all have valid entry backed by a real page. Maybe the GART flush & update is seriously buggy but i expect we would have been hurt sooner by such things. Maybe there is a bug in the hw... wouldn't be surprised. Will try to think to crazy theory. Cheers, Jerome _______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/dri-devel
