Nouveau Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 70390] [NV84] Repeated system crashes under graphics load, E[PFIFO] DMA_PUSHER and lots of E[PGRAPH]
Date: Thu, 17 Oct 2013 19:44:02 +0000	[thread overview]
Message-ID: <bug-70390-8800-Y4A4LFVCpd@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-70390-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>


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

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

--- Comment #13 from Ilia Mirkin <imirkin-FrUbXkNCsVf2fBVCVOL8/A@public.gmane.org> ---
nv84_fence_emit32+0xda/0x1a0

Can you figure out exactly which write this is pointing at? For some of the
values, it could be perfectly legitimate to have the 0x406040 value (e.g. the
sequence id, or the low bits of the address).

(Load up nouveau.ko in gdb, and run "disassemble nv84_fence_emit32". Note that
gdb emits offsets in decimal as opposed to the above offsets which are in hex,
for maximal confusion.)

Ideally we'd have some sort of (optional) command stream validator that made
sure that there was no funny business going on.

My point about nv50_dma_push is that this is the path that user-submitted
command streams take; they don't go through nouveau_bo_wr*, they are written by
userspace via mmap'd sections, and then commands are written to the ring to
jump to them.

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

[-- Attachment #1.2: Type: text/html, Size: 1844 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:[~2013-10-17 19:44 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-11 20:33 [Bug 70390] New: G84: Repeated system crashes under graphics load, E[PFIFO] DMA_PUSHER and lots of E[PGRAPH] bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
     [not found] ` <bug-70390-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2013-10-11 20:34   ` [Bug 70390] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-10-11 20:35   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-10-11 20:37   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-10-11 20:37   ` [Bug 70390] [NV84] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-10-11 20:44   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-10-11 21:22   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-10-11 21:30   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-10-11 22:07   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-10-11 22:30   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-10-12  8:07   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-10-13 12:09   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-10-13 15:39   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-10-17 18:54   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-10-17 19:44   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
2013-10-17 20:30   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-12-21 13:02   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-03-07 21:21   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-03-08  0:38   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-03-09 23:04   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-04-05 19:34   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-04-08 20:07   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-06-02 13:01   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-06-02 13:02   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-06-02 13:21   ` [Bug 70390] [NV84] Repeated system crashes under graphics load, E[PFIFO] DMA_PUSHER 0x00406040 " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-11-09  7:56   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-03-18 20:25   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-08-14 11:12   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-10-19  9:09   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-12-04  8:38   ` 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-70390-8800-Y4A4LFVCpd@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox