All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 35876] Hard GPU hang on nvidia
Date: Fri,  1 Apr 2011 19:49:11 -0700 (PDT)	[thread overview]
Message-ID: <20110402024911.C366613004E@annarchy.freedesktop.org> (raw)
In-Reply-To: <bug-35876-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>

https://bugs.freedesktop.org/show_bug.cgi?id=35876

--- Comment #1 from maximlevitsky-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org 2011-04-01 19:49:11 PDT ---
I might have being lucky with this bug, dunno.
I looked at docomentation at envytools and it mentions that you can't do a tlb
flush while pgraph is running on NV86.

Well, thats known and code contains a workaround.

What I did in addition to that is I took Martin Peres's code that
suspends/resumes pgraph and hooked it into nv84_graph_tlb_flush.
No hangs yet, but that doesn't mean anything yet.

I added this code:

    nv50_graph_pause(dev);
    nv50_vm_flush_engine(dev, 0);
    nv50_graph_unpause(dev);

So PGRAPH is paused when it is supposed to be idle.
Yet, his nv50_graph_pause often complains that:

[18931.100046] [drm] nouveau 0000:01:00.0: PGRAPH: PGRAPH paused while running
a ctxprog, NV40_PGRAPH_CTXCTL_0310 = 0x11
[18937.770017] [drm] nouveau 0000:01:00.0: PGRAPH: wait for idle fail: 00000000
00000000 00000000 00000101!

Let wait and see, but it could be that I am right and we need to pause PGRAPH
more aggressively here.

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

  parent reply	other threads:[~2011-04-02  2:49 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-01 15:58 [Bug 35876] New: Hard GPU hang on nvidia bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
     [not found] ` <bug-35876-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2011-04-02  2:49   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
2011-05-07 13:51   ` [Bug 35876] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-05-21  2:44   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-05-21  2:46   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-05-21  2:58   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-05-21 13:47   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-05-21 13:47   ` [Bug 35876] Hard GPU hangs on NV86 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-08-05  0:08   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-08-12 22:24   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-08-12 23:37   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-08-12 23:39   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-08-13  0:49   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-08-14  0:33   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-08-23  2:45   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-08-23  3:51   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-08-24  1:02   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-08-24  1:04   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-08-24  1:05   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-08-25 20:41   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-08-25 20:43   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-08-25 23:55   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-08-27  2:56   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-08-27  2:57   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-08-27  2:57   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-08-27  3:04   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-08-27  3:05   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-08-27 21:30   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-08-27 21:31   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-08-31  0:48   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-08-31  1:56   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-08-31  1:57   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-08-31  1:57   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-02-12 21:14   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20110402024911.C366613004E@annarchy.freedesktop.org \
    --to=bugzilla-daemon-cc+yj3umiyqdupfqwhejaq@public.gmane.org \
    --cc=nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.