From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org Subject: [Bug 20341] NV31 lockup Date: Fri, 23 Aug 2013 15:14:23 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============2051796870==" Return-path: In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: nouveau-bounces+gcfxn-nouveau=m.gmane.org-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org Errors-To: nouveau-bounces+gcfxn-nouveau=m.gmane.org-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org List-Id: nouveau.vger.kernel.org --===============2051796870== Content-Type: multipart/alternative; boundary="1377270863.6c83eb41.31268"; charset="us-ascii" --1377270863.6c83eb41.31268 Date: Fri, 23 Aug 2013 15:14:23 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" https://bugs.freedesktop.org/show_bug.cgi?id=20341 --- Comment #15 from Ilia Mirkin --- Hm, after more careful review, I take back my comment about the scheme being fragile. (I mean, it's still fragile, but not AS fragile as I thought. I don't see a way for it to fail under normal circumstances.) However one very simple explanation is that a call command is making it onto the userspace-supplied pushbuf. Let's make sure that this is not the case -- Get valgrind-mmt going (http://nouveau.freedesktop.org/wiki/Valgrind-mmt/), and run X inside of mmt, and run x11perf until it dies, e.g. valgrind --tool=mmt --mmt-trace-file=/dev/dri/card0 --mmt-trace-nouveau-ioctls xinit x11perf -putimage500 -- :1 >& xorg-mmt.log or something along those lines. (And you can run it in a separate X server so you don't have to kill your "real" session.) -- You are receiving this mail because: You are the assignee for the bug. --1377270863.6c83eb41.31268 Date: Fri, 23 Aug 2013 15:14:23 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8"

Comment # 15 on bug 20341 from 
Hm, after more careful review, I take back my comment about the scheme being
fragile. (I mean, it's still fragile, but not AS fragile as I thought. I don't
see a way for it to fail under normal circumstances.)

However one very simple explanation is that a call command is making it onto
the userspace-supplied pushbuf. Let's make sure that this is not the case --
Get valgrind-mmt going (http://nouveau.freedesktop.org/wiki/Valgrind-mmt/), and
run X inside of mmt, and run x11perf until it dies, e.g.

valgrind --tool=mmt --mmt-trace-file=/dev/dri/card0 --mmt-trace-nouveau-ioctls
xinit x11perf -putimage500 -- :1 >& xorg-mmt.log

or something along those lines. (And you can run it in a separate X server so
you don't have to kill your "real" session.)

You are receiving this mail because:
  • You are the assignee for the bug.
--1377270863.6c83eb41.31268-- --===============2051796870== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Nouveau mailing list Nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org http://lists.freedesktop.org/mailman/listinfo/nouveau --===============2051796870==--