From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 39988] New: [NVA5] Created FIFOs do not work
Date: Wed, 10 Aug 2011 14:23:45 -0700 (PDT) [thread overview]
Message-ID: <bug-39988-8800@http.bugs.freedesktop.org/> (raw)
https://bugs.freedesktop.org/show_bug.cgi?id=39988
Summary: [NVA5] Created FIFOs do not work
Product: xorg
Version: git
Platform: x86-64 (AMD64)
OS/Version: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Driver/nouveau
AssignedTo: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
ReportedBy: patmandin-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
QAContact: xorg-team-go0+a7rfsptAfugRpC6u6w@public.gmane.org
Created an attachment (id=50104)
--> (https://bugs.freedesktop.org/attachment.cgi?id=50104)
kernel log with drm.debug=15
I must currently use 'noaccel=1' to use nouveau on my NVA5 (GT 220, 1GB vram).
While debugging, it appeared the extra created FIFOs simply do not run at all,
and trigger PFIFO_DMA_PUSHER errors, with IB_EMPTY status. The first of these
errors happen in nouveau_dma_init() function, which is the first one to be run
after creation of a new FIFO.
I must add 'vram_pushbuf=1' to kernel parameters to not have these errors at
start, however, adding 'vram_notify=1' appears to have not effect.
X crashes at start if I do not use 'noaccel=1', with or without
'vram_pushbuf=1', triggering PFIFO_DMA_PUSHER errors, with INVALID_CMD status.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next reply other threads:[~2011-08-10 21:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-10 21:23 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
[not found] ` <bug-39988-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2011-08-10 21:28 ` [Bug 39988] [NVA5] Created FIFOs do not work bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-08-10 21:29 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-08-10 23:00 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-08-11 9:54 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-08-11 11:05 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-08-11 11:14 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-08-11 14:16 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-08-11 14:17 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-08-12 0:25 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-08-12 14:00 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-11-23 20:57 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-12-06 19:56 ` 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-39988-8800@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.