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: Wed, 24 Oct 2018 13:48:46 +0000 [thread overview]
Message-ID: <bug-108500-8800-i6DqYC4fs1@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-108500-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1463 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=108500
--- Comment #6 from Timo Wiren <timo.wiren-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> ---
(In reply to Ilia Mirkin from comment #5)
> Could you boot with
>
> nouveau.debug=mmu=debug
>
> and see what gets printed? I think I see why the -22 (EINVAL) is being
> generated -- the RAM is marked as stolen, and it rejects compressed memory
> on it. However I'm not sure that's actually correct.
Thanks for looking into this. Here's the output:
[ 110.000223] nouveau 0000:04:00.0: mmu: user: comp 3 0a
[ 110.000227] nouveau 0000:04:00.0: mmu: user: invalid -22
[ 110.000275] nouveau 0000:04:00.0: mmu: user: comp 3 0a
[ 110.000277] nouveau 0000:04:00.0: mmu: user: invalid -22
[ 110.003636] nouveau 0000:04:00.0: mmu: user: comp 3 0a
[ 110.003639] nouveau 0000:04:00.0: mmu: user: invalid -22
[ 110.003676] nouveau 0000:04:00.0: mmu: user: comp 3 0a
[ 110.003678] nouveau 0000:04:00.0: mmu: user: invalid -22
[ 110.003697] glxgears[1196]: segfault at 1a ip 00007fa0080b533d sp
00007ffc0a624b00 error 4 in nouveau_dri.so[7fa007ee1000+819000]
[ 110.003705] Code: c6 44 24 07 00 49 8b 9d c0 01 00 00 48 85 db 0f 84 e4 00
00 00 80 bb 91 00 00 00 00 0f 85 03 01 00 00 48 8b 4b 58 0f b7 14 24 <0f> b7 41
1a 66 39 51 18 48 89 4c 24 48 66 0f 46 51 18 66 39 44 24
--
You are receiving this mail because:
You are the assignee for the bug.
You are the QA Contact for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2331 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-24 13:48 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 [this message]
2018-10-25 3:33 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-10-30 20:21 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
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-i6DqYC4fs1@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