From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 46557] nouveau: NV4E acceleration corruption when DMA above 31-bit (2 Gig barrier)
Date: Fri, 30 Nov 2012 17:42:41 +0000 [thread overview]
Message-ID: <bug-46557-8800-N59C4O8ZzJ@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-46557-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
[-- Attachment #1.1: Type: text/plain, Size: 810 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=46557
--- Comment #27 from Raphaël Droz <gibboris-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> ---
Created attachment 70841
--> https://bugs.freedesktop.org/attachment.cgi?id=70841&action=edit
nouveau CALL_SUBR_ACTIVE errors using dma_bits=32 kernel on NV34
I tried your suggestion about setting dma_bits to 32 inside
drivers/gpu/drm/nouveau/core/subdev/vm/nv44.c.
but sadly the same issue arises (dmesg attached).
I hope I'm still wise to post those traces (from my NV34) in this bug report
and hope the root cause is common.
I currently use the drm kernel module with debug=2, debug=3 dumps too much
output, but let me know if this can provide additional useful info.
--
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
next prev parent reply other threads:[~2012-11-30 17:42 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-24 6:13 [Bug 46557] New: nouveau: nv40 display corruption in framebuffer and X lockups unless nouveau.noaccel=1 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
[not found] ` <bug-46557-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2012-02-24 6:13 ` [Bug 46557] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-05-04 8:30 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-05-09 22:53 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-05-13 8:07 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-05-17 18:30 ` [Bug 46557] nouveau: nv40 2D acceleration broken on 64-bit kernel; works on 32-bit bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-05-22 9:54 ` [Bug 46557] nouveau: nv4E " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-05-22 16:55 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-05-22 16:57 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-06-02 5:51 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-06-17 10:52 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-06-17 13:10 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-06-17 13:14 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-06-17 13:16 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-06-17 13:18 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-06-17 13:19 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-06-17 13:25 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-06-17 13:26 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-06-17 13:26 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-06-17 13:27 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-06-17 14:16 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-06-17 15:03 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-06-17 16:02 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-06-17 20:00 ` [Bug 46557] nouveau: NV4E acceleration corruption when DMA about 31-bit (2 G) bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-06-17 20:12 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-06-17 21:26 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-06-19 5:20 ` [Bug 46557] nouveau: NV4E acceleration corruption when DMA above 31-bit (2 Gig barrier) bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-09-16 19:45 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-10-02 16:24 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-10-03 7:47 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-10-03 11:14 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-10-03 11:21 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-10-03 22:38 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-10-29 14:26 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-11-07 12:19 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-11-30 17:42 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
2012-12-26 17:15 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-12-28 1:33 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-12-28 23:38 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-12-29 12:21 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-12-29 13:06 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-12-29 13:09 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-12-29 14:35 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-03-01 17:53 ` 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-46557-8800-N59C4O8ZzJ@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.