All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 36914] New: r600g: add rv670 flushing workaround. Causes games and some mesa demos to segfault.
Date: Fri,  6 May 2011 10:02:43 -0700 (PDT)	[thread overview]
Message-ID: <bug-36914-502@http.bugs.freedesktop.org/> (raw)

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

           Summary: r600g: add rv670 flushing workaround. Causes games and
                    some mesa demos to segfault.
           Product: Mesa
           Version: git
          Platform: x86 (IA32)
        OS/Version: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: Drivers/Gallium/r600
        AssignedTo: dri-devel@lists.freedesktop.org
        ReportedBy: lists@andyfurniss.entadsl.com


RV670 AGP card with agpmode=-1, d-r-t kernel as it was 16/03/11

Since

5066f7cd0e010db46b42f8f08a33c10cb34f8726
r600g: add rv670 flushing workaround.

I am getting segfaults with openarena, nexuiz, etqw and a few mesa demos - 

gltestperf,clearspd and ipers.

The bt of the segfault seems to repeat for ever.

Starting program: /home/andy/Src/Mesa-git/demos/src/demos/ipers 
[Thread debugging using libthread_db enabled]
IperS V1.0
Written by David Bucciarelli (tech.hmw@plus.it)
[New Thread 0xb726f700 (LWP 14143)]

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xb726f700 (LWP 14143)]
r600_context_flush (ctx=0x8074e10) at r600_hw_context.c:1282
1282    {
(gdb) bt
#0  r600_context_flush (ctx=0x8074e10) at r600_hw_context.c:1282
#1  0xb6eeed3b in r600_context_flush_all (ctx=0x8074e10, flush_flags=128) at
r600_hw_context.c:786
#2  0xb6eeef18 in r600_context_bo_flush (ctx=0x8074e10, flush_flags=33554496,
flush_mask=0, rbo=0x83c1488) at r600_hw_context.c:814
#3  0xb6eef030 in r600_context_flush_dest_caches (ctx=0x8074e10) at
r600_hw_context.c:1197
#4  0xb6eee833 in r600_context_flush (ctx=0x8074e10) at r600_hw_context.c:1298
#5  0xb6eeed3b in r600_context_flush_all (ctx=0x8074e10, flush_flags=128) at
r600_hw_context.c:786
#6  0xb6eeef18 in r600_context_bo_flush (ctx=0x8074e10, flush_flags=33554496,
flush_mask=0, rbo=0x83c1488) at r600_hw_context.c:814
#7  0xb6eef030 in r600_context_flush_dest_caches (ctx=0x8074e10) at
r600_hw_context.c:1197
#8  0xb6eee833 in r600_context_flush (ctx=0x8074e10) at r600_hw_context.c:1298
#9  0xb6eeed3b in r600_context_flush_all (ctx=0x8074e10, flush_flags=128) at
r600_hw_context.c:786
#10 0xb6eeef18 in r600_context_bo_flush (ctx=0x8074e10, flush_flags=33554496,
flush_mask=0, rbo=0x83c1488) at r600_hw_context.c:814
#11 0xb6eef030 in r600_context_flush_dest_caches (ctx=0x8074e10) at
r600_hw_context.c:1197
#12 0xb6eee833 in r600_context_flush (ctx=0x8074e10) at r600_hw_context.c:1298

-- 
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-06 17:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-06 17:02 bugzilla-daemon [this message]
2011-05-06 17:21 ` [Bug 36914] r600g: add rv670 flushing workaround. Causes games and some mesa demos to segfault bugzilla-daemon
2011-05-06 19:53 ` 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-36914-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.