From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 30626] New: bisected nexuiz issue since r600g: don't double count dirty block
Date: Tue, 5 Oct 2010 06:29:50 -0700 (PDT) [thread overview]
Message-ID: <bug-30626-502@http.bugs.freedesktop.org/> (raw)
https://bugs.freedesktop.org/show_bug.cgi?id=30626
Summary: bisected nexuiz issue since r600g: don't double count
dirty block
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
rv790, d-r-t, git ddx, mesa,libdrm and xserver 1.9. wait vline and dri2 vsync
off.
Test is nexuiz 2.5.2, timedemo demos/demo1, effects normal, fullscreen
1920x1080.
The nexuiz sdl client isn't affected as badly as the glx client and will run to
completion the demo. It may sometimes show the libc error on exit. The glx
client will bail out during the demo with either a segfault or the libc trace
below.
Both since the commit -
commit dde1391cc95478f4dedccdf920ba0a6607472937
Author: John Doe <glisse@barney.(none)>
Date: Thu Sep 30 17:30:25 2010 -0400
r600g: don't double count dirty block
This avoid to overcount the number of dwords we need and
thus avoid maximazation of cs buffer use.
Will give an error in dmesg.
[drm:radeon_cs_parser_init] *ERROR* cs IB too big: 16390
[drm:radeon_cs_ioctl] *ERROR* Failed to initialize parser !
The libc trace -
*** glibc detected *** ./nexuiz-linux-686-glx: double free or corruption
(!prev): 0x0ba5e510 ***
======= Backtrace: =========
/lib/libc.so.6[0xb73d4d9a]
/lib/libc.so.6(cfree+0x6e)[0xb73d697e]
/home/andy/Src/Mesa-git/mesa/lib/gallium/r600_dri.so[0xb6179950]
/home/andy/Src/Mesa-git/mesa/lib/gallium/r600_dri.so[0xb61580aa]
/home/andy/Src/Mesa-git/mesa/lib/gallium/r600_dri.so[0xb62a9169]
/home/andy/Src/Mesa-git/mesa/lib/gallium/r600_dri.so[0xb623184d]
/home/andy/Src/Mesa-git/mesa/lib/gallium/r600_dri.so[0xb6174b70]
/home/andy/Src/Mesa-git/mesa/lib/gallium/r600_dri.so[0xb6154737]
/home/andy/Src/Xorg-git/modular/lib/libGL.so.1[0xb64edc40]
/home/andy/Src/Xorg-git/modular/lib/libGL.so.1[0xb64c8457]
/home/andy/Src/Xorg-git/modular/lib/libGL.so.1[0xb64c8bb6]
/home/andy/Src/Xorg-git/modular/lib/libX11.so.6(XCloseDisplay+0xb6)[0xb76a19c6]
./nexuiz-linux-686-glx[0x804d82d]
./nexuiz-linux-686-glx[0x80dec52]
./nexuiz-linux-686-glx[0x8198b15]
[0xffffe400]
/home/andy/Src/Mesa-git/mesa/lib/gallium/r600_dri.so[0xb616a7a0]
/home/andy/Src/Mesa-git/mesa/lib/gallium/r600_dri.so[0xb62de8c8]
/home/andy/Src/Mesa-git/mesa/lib/gallium/r600_dri.so[0xb619f8ca]
./nexuiz-linux-686-glx[0x80ae84c]
./nexuiz-linux-686-glx[0x8082b51]
./nexuiz-linux-686-glx[0x8087e9c]
./nexuiz-linux-686-glx[0x80dfb5f]
./nexuiz-linux-686-glx[0x804b0fd]
/lib/libc.so.6(__libc_start_main+0xd0)[0xb7387380]
./nexuiz-linux-686-glx[0x804aff1]
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next reply other threads:[~2010-10-05 13:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-05 13:29 bugzilla-daemon [this message]
2010-10-05 20:05 ` [Bug 30626] bisected nexuiz issue since r600g: don't double count dirty block bugzilla-daemon
2010-10-05 20:14 ` 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-30626-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.