dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 30551] New: r600c: Segfaults with Evergreen
Date: Fri,  1 Oct 2010 16:08:29 -0700 (PDT)	[thread overview]
Message-ID: <bug-30551-502@http.bugs.freedesktop.org/> (raw)

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

           Summary: r600c: Segfaults with Evergreen
           Product: Mesa
           Version: git
          Platform: Other
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: Drivers/DRI/R600
        AssignedTo: dri-devel@lists.freedesktop.org
        ReportedBy: monraaf@gmail.com


Created an attachment (id=39109)
 View: https://bugs.freedesktop.org/attachment.cgi?id=39109
 Review: https://bugs.freedesktop.org/review?bug=30551&attachment=39109

fixes segfaults on Evergreen

With latest git master I see a lot of segfaults with Evergreen GPU. Even with
the simple redbook hello program.

Program received signal SIGSEGV, Segmentation fault.
0xb76eb25f in evergreenSendDB (ctx=0x807df78, atom=0x807aca8) at
evergreen_chip.c:956
956         zheight = rrb->base.Height;

It's trying to dereference a null pointer (rrb) here. Proposed fix attached.

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

             reply	other threads:[~2010-10-01 23:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-01 23:08 bugzilla-daemon [this message]
2010-10-02  0:15 ` [Bug 30551] r600c: Segfaults with Evergreen 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-30551-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox