All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 108500] New: Crash when creating a depth buffer on GeForce 320M
Date: Fri, 19 Oct 2018 16:59:49 +0000	[thread overview]
Message-ID: <bug-108500-8800@http.bugs.freedesktop.org/> (raw)


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

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

            Bug ID: 108500
           Summary: Crash when creating a depth buffer on GeForce 320M
           Product: Mesa
           Version: 18.2
          Hardware: x86-64 (AMD64)
                OS: Linux (All)
            Status: NEW
          Severity: critical
          Priority: medium
         Component: Drivers/DRI/nouveau
          Assignee: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
          Reporter: timo.wiren-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
        QA Contact: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org

Created attachment 142101
  --> https://bugs.freedesktop.org/attachment.cgi?id=142101&action=edit
glxinfo

Every OpenGL application that wants to use a depth buffer always crashes,
including glxgears:

glxgears: dri2.c:906: dri2_allocate_textures: Assertion `*zsbuf' failed.

I debugged the assertion with gdb:

templ structure contents passed to resource_create():
$2 = {reference = {count = 0}, width0 = 300, height0 = 300, depth0 = 1,
array_size = 1, format = PIPE_FORMAT_Z24X8_UNORM,
  target = PIPE_TEXTURE_2D, last_level = 0, nr_samples = 0, nr_storage_samples
= 0, usage = 0, bind = 1, flags = 0,
  next = 0x0, screen = 0x0}

In nv50_miptree_create() in gallium/drivers/nouveau/nv50/nv50_miptree.c:389
the call to nouveau_bo_new() returns -22 that causes it to return NULL. 

MESA_DEBUG=1 glxgears prints the following before segfaulting:
Mesa: User error: GL_OUT_OF_MEMORY in Resizing framebuffer

Computer: MacBook Pro 2010 (NVIDIA GeForce 320M "MCP89")
Resolution: 1280x800
OS: Lubuntu 18.10
Mesa: 18.2.2, but happens also with the versions that come with Lubuntu 16.04
and 18.04

I can compile and run mesa from sources, if it helps debugging.

-- 
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: 3357 bytes --]

[-- Attachment #2: Type: text/plain, Size: 154 bytes --]

_______________________________________________
Nouveau mailing list
Nouveau@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/nouveau

             reply	other threads:[~2018-10-19 16:59 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-19 16:59 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
     [not found] ` <bug-108500-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2018-10-19 18:15   ` [Bug 108500] Crash when creating a depth buffer on GeForce 320M 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
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@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.