All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 28259] New: [bisected r300g] Freeorion crash at startup
Date: Wed, 26 May 2010 05:00:47 -0700 (PDT)	[thread overview]
Message-ID: <bug-28259-502@http.bugs.freedesktop.org/> (raw)

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

           Summary: [bisected r300g] Freeorion crash at startup
           Product: Mesa
           Version: git
          Platform: Other
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: Drivers/DRI/r300
        AssignedTo: dri-devel@lists.freedesktop.org
        ReportedBy: drakkk@centrum.cz


Created an attachment (id=35864)
 --> (https://bugs.freedesktop.org/attachment.cgi?id=35864)
terminal output + backtrace

Freeorion crash at startup with:
../../../../src/gallium/auxiliary/util/u_inlines.h:82:pipe_reference: Assertion
`pipe_is_referenced(ptr)' failed.
This is a regression introduced by this commit:

commit 2c072c8f72647a3b32e9855f7635b37ba399f5be
Author: Marek Olšák <maraeo@gmail.com>
Date:   Wed May 26 01:23:07 2010 +0200

    r300g: implement fake but compliant fences

my card: 01:00.0 VGA compatible controller: ATI Technologies Inc M56P [Radeon
Mobility X1600]

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

             reply	other threads:[~2010-05-26 12:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-26 12:00 bugzilla-daemon [this message]
2010-05-26 12:01 ` [Bug 28259] [bisected r300g] Freeorion crash at startup bugzilla-daemon
2010-05-26 14:40 ` 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-28259-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.