From mboxrd@z Thu Jan 1 00:00:00 1970 From: Joerg Roedel Subject: Re: Linux 2.6.39-rc3 Date: Sun, 17 Apr 2011 16:09:24 +0200 Message-ID: <20110417140924.GU18463@8bytes.org> References: <4DA655E7.3000904@zytor.com> <20110415131152.GJ18463@8bytes.org> <20110415131650.GB18660@elte.hu> <20110415154604.GN18463@8bytes.org> <20110416163509.GS18463@8bytes.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org To: Jerome Glisse Cc: Ingo Molnar , Linus Torvalds , Linux Kernel Mailing List , "dri-devel@lists.freedesktop.org" , Tejun Heo , "H. Peter Anvin" , Thomas Gleixner , Yinghai Lu , alexandre.f.demers@gmail.com List-Id: dri-devel@lists.freedesktop.org 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