All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 99307] [r600g, bisected] Segmentation fault in every application
Date: Fri, 06 Jan 2017 21:07:41 +0000	[thread overview]
Message-ID: <bug-99307-502@http.bugs.freedesktop.org/> (raw)


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

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

            Bug ID: 99307
           Summary: [r600g, bisected] Segmentation fault in every
                    application
           Product: Mesa
           Version: git
          Hardware: x86-64 (AMD64)
                OS: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: Drivers/Gallium/r600
          Assignee: dri-devel@lists.freedesktop.org
          Reporter: megwattt@gmail.com
        QA Contact: dri-devel@lists.freedesktop.org

Created attachment 128801
  --> https://bugs.freedesktop.org/attachment.cgi?id=128801&action=edit
Glxgears gdb output

On my JUNIPER XT GPU, every OpenGL application will crash at the beginning. 
The commit which cause this problem is 9a3296bf1cf8d45349b14b31eeb0d81f8b8774fc
: radeonsi: use SDMA for initial clearing of DCC/CMASK/HTILE on CIK-VI.

I have attached the output when glxgears is debugged with gdb.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 2562 bytes --]

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

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

             reply	other threads:[~2017-01-06 21:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-06 21:07 bugzilla-daemon [this message]
2017-01-06 21:08 ` [Bug 99307] [r600g, bisected] Segmentation fault in every application bugzilla-daemon

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-99307-502@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon@freedesktop.org \
    --cc=dri-devel@lists.freedesktop.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.