From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 108500] Crash when creating a depth buffer on GeForce 320M
Date: Tue, 30 Oct 2018 20:21:42 +0000 [thread overview]
Message-ID: <bug-108500-8800-qhp397aTJr@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-108500-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
[-- Attachment #1.1: Type: text/plain, Size: 789 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=108500
--- Comment #8 from Ilia Mirkin <imirkin-FrUbXkNCsVf2fBVCVOL8/A@public.gmane.org> ---
Could you edit
drivers/gpu/drm/nouveau/nvkm/subdev/mmu/vmmnv50.c:nv50_vmm_valid, and change it
to set aper = 0 in the if (ram->stolen) case (so aper=0 in both of the VRAM
cases). Let me know if you need me to make you a proper patch.
Then see if ... stuff works. At least glxgears, but would be good to test more
complex things too which make extensive use of depth as well as compressible
color formats (something like xonotic would be more than sufficient).
Unfortunately we're not sure if this works on MCP89 or not.
--
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1569 bytes --]
[-- Attachment #2: Type: text/plain, Size: 154 bytes --]
_______________________________________________
Nouveau mailing list
Nouveau@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/nouveau
next prev parent reply other threads:[~2018-10-30 20:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-19 16:59 [Bug 108500] New: Crash when creating a depth buffer on GeForce 320M bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
[not found] ` <bug-108500-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2018-10-19 18:15 ` [Bug 108500] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-10-20 5:55 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-10-20 15:02 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-10-20 16:28 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-10-24 4:55 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-10-24 13:48 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-10-25 3:33 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-10-30 20:21 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
2018-11-01 18:16 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-05-16 18:31 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-05-16 19:42 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-05-17 15:19 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-07-20 9:04 ` 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-108500-8800-qhp397aTJr@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;
as well as URLs for NNTP newsgroup(s).