All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 31167] New: X server crash on r600c and r600g (DRI2SwapBuffers?)
Date: Wed, 27 Oct 2010 09:31:12 -0700 (PDT)	[thread overview]
Message-ID: <bug-31167-502@http.bugs.freedesktop.org/> (raw)

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

           Summary: X server crash on r600c and r600g (DRI2SwapBuffers?)
           Product: Mesa
           Version: git
          Platform: x86-64 (AMD64)
        OS/Version: Linux (All)
            Status: NEW
          Severity: major
          Priority: medium
         Component: Drivers/DRI/R600
        AssignedTo: dri-devel@lists.freedesktop.org
        ReportedBy: henri.valta@kemi.fi


Created an attachment (id=39811)
 --> (https://bugs.freedesktop.org/attachment.cgi?id=39811)
backtrace from a few days older version

X server is crashing on certain situations.

One way to easily reproduce is visit
http://www.zachstronaut.com/lab/isocube.html
on Chromium

Xorg/Mesa is bleeding edge versions from Ubuntu xorg-edgers PPA (Maverick)
xserver-xorg-video-radeon 1:6.13.99+git20101025.df92245e-0ubuntu0sarvatt
xserver-xorg-core
2:1.9.1+git20101025+server-1.9-branch.6e1f78bd-0ubuntu0sarvatt
libgl1-mesa-dri 7.10.0+git20101026.547e7619-0ubuntu0sarvatt
kernel 2.6.36-1.7

HW: ATI Technologies Inc Mobility Radeon HD 3400 Series (Lenovo T400)

The crash seem to happen on both r600c and r600g. The logs are captured using
r600g.

-- 
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-27 16:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-27 16:31 bugzilla-daemon [this message]
2010-10-27 16:32 ` [Bug 31167] X server crash on r600c and r600g (DRI2SwapBuffers?) bugzilla-daemon
2010-10-27 16:36 ` bugzilla-daemon
2010-10-27 16:36 ` 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-31167-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.