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 82835] [NV92] GeForce 8800 GS VDPAU h264 decoding hang
Date: Tue, 02 Sep 2014 16:55:42 +0000	[thread overview]
Message-ID: <bug-82835-8800-Owhg4axn66@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-82835-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>


[-- Attachment #1.1: Type: text/plain, Size: 1155 bytes --]

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

--- Comment #6 from Ilia Mirkin <imirkin-FrUbXkNCsVf2fBVCVOL8/A@public.gmane.org> ---
Hm, just noticed this (same as last time, but I guess I wasn't paying enough
attention):

nouveau E[  PGRAPH][0000:05:00.0] ch 4 [0x00178fb000 mplayer[1645]] subc 3
class 0x8297 mthd 0x1b0c data 0x1000f010
nouveau E[     PFB][0000:05:00.0] trapped write at 0x00204050c0 on channel
0x000178fb [mplayer[1645]] PGRAPH/PROP/RT0 reason: PAGE_NOT_PRESENT

method 1b0c == QUERY_GET. However the data is 0x1000f010, not 0xf010, which
means it's not coming from the video stuff or the screen fence stuff, but
rather is a PIPE_QUERY_GPU_FINISHED query. Which is interesting, because
nothing appears to actually use that PIPE_QUERY type...

Could you stick a assert(0) right before

      nv50_query_get(push, q, 0, 0x1000f010);

in nv50_query.c and see if it triggers (make sure to use a debug build... or
make it something nastier than assert), and get a backtrace from gdb? (Or
actually just set a breakpoint on that line and see if gdb hits it...)

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 1897 bytes --]

[-- Attachment #2: Type: text/plain, Size: 181 bytes --]

_______________________________________________
Nouveau mailing list
Nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
http://lists.freedesktop.org/mailman/listinfo/nouveau

  parent reply	other threads:[~2014-09-02 16:55 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-20  3:55 [Bug 82835] New: GeForce 8800 GS VDPAU h264 decoding hang bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
     [not found] ` <bug-82835-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2014-08-20  3:55   ` [Bug 82835] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-08-20  4:04   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-08-24 15:22   ` [Bug 82835] [NV92] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-09-01 22:57   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-09-02 16:24   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-09-02 16:25   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-09-02 16:55   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
2014-09-02 23:51   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-09-03  0:03   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-09-03  1:57   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-09-03  1:58   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-09-03  1:59   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-09-03  3:35   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-09-03  6:50   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-10-12 11:51   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-03-21 17:46   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-03-21 18:13   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-03-21 18:53   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-03-21 19:04   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-03-21 19:55   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-10-19 14:56   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-04-10  6:51   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-05-05 19:22   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-05-05 19:32   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-11-25 12:24   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-12-04  8:48   ` 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=bug-82835-8800-Owhg4axn66@http.bugs.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.