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 37157] New: [bisected] KDE KWin crashes on start with delayed BO mapping
Date: Thu, 12 May 2011 18:55:27 -0700 (PDT)	[thread overview]
Message-ID: <bug-37157-502@http.bugs.freedesktop.org/> (raw)

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

           Summary: [bisected] KDE KWin crashes on start with delayed BO
                    mapping
           Product: Mesa
           Version: git
          Platform: x86-64 (AMD64)
        OS/Version: Linux (All)
            Status: NEW
          Severity: critical
          Priority: medium
         Component: Drivers/Gallium/r600
        AssignedTo: dri-devel@lists.freedesktop.org
        ReportedBy: jlp.bugs@gmail.com


After updating the mesa today KWin started to crash/segfault on start. I've
bisected and the first commmit that causes the crash is:
5e15497452cf3e4d2fc76fdc6ed8113d0891b467
r600g: delay mapping until first map request. (v2)

This is with KDE KWin 4.6.3 and on a laptop with integrated ATI Mobility Radeon
HD 5470.

Later I've also tried with glxgears, which appears to work fine if in window
and crashes if started with -fullscreen option.

-- 
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:[~2011-05-13  1:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-13  1:55 bugzilla-daemon [this message]
2011-05-13  1:56 ` [Bug 37157] [bisected] KDE KWin crashes on start with delayed BO mapping bugzilla-daemon
2011-05-13  1:57 ` bugzilla-daemon
2011-05-13  3:47 ` bugzilla-daemon
2011-05-13  4:05 ` bugzilla-daemon
2011-05-13 10:56 ` 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-37157-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