https://bugs.freedesktop.org/show_bug.cgi?id=31567
Summary: [r300] swrast/s_span.c:1267: _swrast_write_rgba_span:
Assertion `rb->PutValues' failed.
Product: Mesa
Version: git
Platform: x86 (IA32)
OS/Version: Linux (All)
Status: NEW
Severity: critical
Priority: medium
Component: Drivers/DRI/r300
AssignedTo: dri-devel(a)lists.freedesktop.org
ReportedBy: vlee(a)vmware.com
mesa: d18df9e336b5d2e68a4a6185f7b9d0d0c095c3c4 (master)
chipset: RV530 71C5 (ATI Radeon X1600)
system architecture: i686
libdrm-dev: 2.4.21-1ubuntu2.1
kernel version: 2.6.35-22-generic
Linux distribution: Ubuntu 10.10 i386
Machine model: iMac4,1
Run piglit fbo-scissor-bitmap test.
$ ./bin/fbo-scissor-bitmap
...
radeonSetSpanFunctions: bad format: 0x0002
radeonSetSpanFunctions: bad format: 0x0002
fbo-scissor-bitmap: swrast/s_span.c:1267: _swrast_write_rgba_span: Assertion
`rb->PutValues' failed.
(gdb) bt
#0 0x00808416 in __kernel_vsyscall ()
#1 0x00b0a941 in raise (sig=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
#2 0x00b0de42 in abort () at abort.c:92
#3 0x00b038e8 in __assert_fail (assertion=0x122ec21 "rb->PutValues",
file=0x124138c "swrast/s_span.c", line=1267, function=0x124170c
"_swrast_write_rgba_span") at assert.c:81
#4 0x0110fa87 in _swrast_write_rgba_span (ctx=0x9550460, span=0xbfe29174) at
swrast/s_span.c:1267
#5 0x010fe66d in _swrast_Bitmap (ctx=0x9550460, px=224, py=229, width=64,
height=53, unpack=0x955f130, bitmap=0x804e200 "") at swrast/s_bitmap.c:128
#6 0x011a3084 in _mesa_Bitmap (width=64, height=53, xorig=0, yorig=0, xmove=0,
ymove=0, bitmap=0x804e200 "") at main/drawpix.c:246
#7 0x0804ad06 in draw_and_test (destination=0x804e1d6 "FBO",
drawable_width=512, drawable_height=512) at
piglit/tests/fbo/fbo-scissor-bitmap.c:185
#8 0x0804b9b9 in piglit_display () at
piglit/tests/fbo/fbo-scissor-bitmap.c:370
#9 0x0804d9b3 in display () at piglit/tests/util/piglit-framework.c:52
#10 0x00370820 in fghRedrawWindow (window=0x9533058, enumerator=0xbfe29d98) at
freeglut_main.c:210
#11 fghcbDisplayWindow (window=0x9533058, enumerator=0xbfe29d98) at
freeglut_main.c:227
#12 0x00374660 in fgEnumWindows (enumCallback=0x370790 <fghcbDisplayWindow>,
enumerator=0xbfe29d98) at freeglut_structure.c:394
#13 0x00370cdb in fghDisplayAll () at freeglut_main.c:249
#14 glutMainLoopEvent () at freeglut_main.c:1450
#15 0x00371605 in glutMainLoop () at freeglut_main.c:1498
#16 0x0804db5c in main (argc=1, argv=0xbfe2a024) at
piglit/tests/util/piglit-framework.c:118
(gdb) frame 4
#4 0x0110fa87 in _swrast_write_rgba_span (ctx=0x9550460, span=0xbfe29174) at
swrast/s_span.c:1267
1267 ASSERT(rb->PutValues);
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=47289
Bug #: 47289
Summary: SIGSEGV at r300_state.c:1066
Classification: Unclassified
Product: Mesa
Version: 7.11
Platform: x86-64 (AMD64)
OS/Version: FreeBSD
Status: NEW
Severity: critical
Priority: medium
Component: Drivers/DRI/r300
AssignedTo: dri-devel(a)lists.freedesktop.org
ReportedBy: rfg-freedesktop(a)tristatelogic.com
I have been using a program called "gthumb" for some time now, and it
has worked well for me.
Recently, I upgraded some of my hardware. Specifically, I bought a new
monitor and a nice "X600" (Radeon) card to hang that off of. Since then,
gthumb crashes consistantly, shortly after startup. (I'm on FreeBSD 8.2,
by the way.)
I made some modest efforts to try to find out what was going on, but frankly,
this graphics stuff is pretty much all greek to me. I did however rebuild
and re-install both gthumb and dri with debugging info so that I could at
least get a stack trace from the coredump file.
So here is some (gdb) context for the SIGSEGV crash of gthumb:
#0 0x0000000805453233 in r300UpdateWindow (ctx=0x80534a000)
at r300_state.c:1066
1066 GLfloat sx = v[MAT_SX];
[New Thread 8052041c0 (LWP 100247)]
(gdb) where
#0 0x0000000805453233 in r300UpdateWindow (ctx=0x80534a000)
at r300_state.c:1066
#1 0x0000000805456a83 in r300ResetHwState (r300=0x8052f8000)
at r300_state.c:2195
#2 0x00000008054588ec in r300InitState (r300=0x8052f8000) at r300_state.c:2750
#3 0x00000008054451fd in r300CreateContext (glVisual=0x805308700,
driContextPriv=0x80524d220, sharedContextPrivate=0x0) at r300_context.c:382
#4 0x000000080543b5bf in radeonCreateContext (glVisual=0x805308700,
driContextPriv=0x80524d220, sharedContextPriv=0x0) at radeon_screen.c:1143
#5 0x0000000805435793 in driCreateNewContext (psp=0x80524e480,
config=0x805308700, render_type=32788, shared=0x0, hwContext=3,
data=0x80524d1f0) at ../common/dri_util.c:587
#6 0x0000000802f2d70f in driCreateContext () from /usr/local/lib/libGL.so.1
#7 0x0000000802f08320 in CreateContext () from /usr/local/lib/libGL.so.1
#8 0x0000000802f086dc in glXCreateNewContext () from /usr/local/lib/libGL.so.1
#9 0x0000000800a61255 in cogl_pango_glyph_cache_new ()
from /usr/local/lib/libclutter-glx-1.0.so.0
#10 0x00000008009ebfdb in clutter_feature_available ()
from /usr/local/lib/libclutter-glx-1.0.so.0
#11 0x00000008009f6045 in clutter_get_option_group_without_init ()
from /usr/local/lib/libclutter-glx-1.0.so.0
#12 0x00000008009f626f in clutter_init ()
from /usr/local/lib/libclutter-glx-1.0.so.0
#13 0x00000000004c3b59 in main (argc=1, argv=0x7fffffffe300) at main.c:561
(gdb) print v
$1 = (const GLfloat *) 0x800000000
(gdb) print *$1
Cannot access memory at address 0x800000000
(gdb)
I did some grepping around and found that MAT_SX is #defined to the value 0.
Thus, the gdb command "print v[0]" or equivalently "print *v" should give a
clearer picture of what is causing the problem, and as you can see, indeed
it does. The process virtual space at 0x800000000 is apparently not mapped
in. Thus, the attempt to fetch the contents of v[MAT_SX] quite reasonably
results in a SIGSEGV and a coredump.
After getting this far, I read the page:
http://dri.freedesktop.org/wiki/DriTroubleshooting
and checked everything I could that was listed there and all seems to be
well. The radeon.ko module does seem to be loaded into the kernel, and the
folliowing line does exist in my /var/log/Xorg.0.log file:
(II) RADEON(0): Direct rendering enabled
Additionally, after doing "setenv LIBGL_DEBUG verbose" and re-running
gthumb, most everything seems to be OK, however it is apparent that
there are a couple of (optional?) DRI configuration files that simply
are not present. (Do I need to have one or both of these?)
% gthumb .
libGL: XF86DRIGetClientDriverName: 5.3.0 r300 (screen 0)
libGL: OpenDriver: trying /usr/local/lib/dri/r300_dri.so
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 6, (OK)
drmOpenByBusid: Searching for BusID pci:0000:02:00.0
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 6, (OK)
drmOpenByBusid: drmOpenMinor returns 6
drmOpenByBusid: drmGetBusid reports pci:0000:02:00.0
libGL error:
Can't open configuration file /etc/drirc: No such file or directory.
libGL error:
Can't open configuration file /usr/home/rfg/.drirc: No such file or directory.
Segmentation fault (core dumped)
So anyway, long story short, I could use some help here. I'd kinda like
to be able to run gthumb again, you know, without it crashing right off
the bat.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=27786
Summary: Freeze if boss-key (Shift-Esc) pressed while busy
doing network stuff and game engine not running
Product: Mesa
Version: unspecified
Platform: x86-64 (AMD64)
OS/Version: Linux (All)
Status: NEW
Severity: major
Priority: medium
Component: Drivers/DRI/r300
AssignedTo: dri-devel(a)lists.freedesktop.org
ReportedBy: luke-jr+freedesktop(a)utopios.org
If I press Shift-Esc while Armagetron Advanced is in a network-only state
(fetching server list, between rounds, etc), the game locks up until I manually
kill it (SIGINT works)
--- Backtrace ---
#0 0x00007ffb139827c4 in __lll_lock_wait () from /lib/libpthread.so.0
#1 0x00007ffb1397e029 in _L_lock_534 () from /lib/libpthread.so.0
#2 0x00007ffb1397de3e in pthread_mutex_lock () from /lib/libpthread.so.0
#3 0x00007ffb12e029dd in ?? () from //usr/lib64/opengl/xorg-x11/lib/libGL.so.1
#4 0x00007ffb12e030b3 in ?? () from //usr/lib64/opengl/xorg-x11/lib/libGL.so.1
#5 0x00007ffb12e01825 in glXMakeCurrentReadSGI ()
from //usr/lib64/opengl/xorg-x11/lib/libGL.so.1
#6 0x00007ffb12996f04 in ?? () from /usr/lib/libSDL-1.2.so.0
#7 0x00007ffb1299acfe in ?? () from /usr/lib/libSDL-1.2.so.0
#8 0x00007ffb1299af17 in ?? () from /usr/lib/libSDL-1.2.so.0
#9 0x00007ffb1298b902 in SDL_VideoQuit () from /usr/lib/libSDL-1.2.so.0
#10 0x00007ffb1296516d in SDL_QuitSubSystem () from /usr/lib/libSDL-1.2.so.0
#11 0x00007ffb129651ee in SDL_Quit () from /usr/lib/libSDL-1.2.so.0
#12 0x00007ffb12965a0f in ?? () from /usr/lib/libSDL-1.2.so.0
#13 <signal handler called>
#14 0x00007ffb0dc18540 in radeonFlush () from /usr/lib64/dri/r300_dri.so
#15 0x00007ffb0dc0e028 in ?? () from /usr/lib64/dri/r300_dri.so
#16 0x00007ffb0dc91cc4 in _mesa_reference_texobj ()
from /usr/lib64/dri/r300_dri.so
#17 0x00007ffb0dc947eb in _mesa_free_texture_data ()
from /usr/lib64/dri/r300_dri.so
#18 0x00007ffb0dc31938 in _mesa_free_context_data ()
from /usr/lib64/dri/r300_dri.so
#19 0x00007ffb0dc31a5e in _mesa_destroy_context ()
from /usr/lib64/dri/r300_dri.so
#20 0x00007ffb0dc175fd in radeonDestroyContext ()
from /usr/lib64/dri/r300_dri.so
#21 0x00007ffb0dbf40f0 in ?? () from /usr/lib64/dri/r300_dri.so
#22 0x00007ffb12e2429f in ?? () from
//usr/lib64/opengl/xorg-x11/lib/libGL.so.1
#23 0x00007ffb12e001a8 in ?? () from
//usr/lib64/opengl/xorg-x11/lib/libGL.so.1
#24 0x00007ffb12996f22 in ?? () from /usr/lib/libSDL-1.2.so.0
#25 0x00007ffb1299acfe in ?? () from /usr/lib/libSDL-1.2.so.0
#26 0x00007ffb1299af17 in ?? () from /usr/lib/libSDL-1.2.so.0
#27 0x00007ffb1298b902 in SDL_VideoQuit () from /usr/lib/libSDL-1.2.so.0
#28 0x00007ffb1296516d in SDL_QuitSubSystem () from /usr/lib/libSDL-1.2.so.0
#29 0x000000000042a1e9 in main ()
Video card: ATi Radeon X850 AGP
--- Software versions (Gentoo) ---
Armagetron Advanced trunk: bzr co lp:armagetronad -r 968
sys-libs/glibc-2.10.1-r1 (libpthread)
media-libs/mesa-7.7.1 (libGL, r300_dri)
media-libs/libsdl-1.2.13-r1 (libSDL)
x11-base/xorg-server-1.7.6
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=29110
Summary: X server crash when entering address in addressbar of
konqueror
Product: Mesa
Version: git
Platform: x86-64 (AMD64)
OS/Version: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/DRI/r300
AssignedTo: dri-devel(a)lists.freedesktop.org
ReportedBy: ich(a)kuja.in
Created an attachment (id=37126)
--> (https://bugs.freedesktop.org/attachment.cgi?id=37126)
Xorg log
(sorry for the poor bug summary, but this is a way of breaking things, others
have been discovered by me as well)
a quite random crash, sometimes it happens right away, sometimes it takes a few
tries, the backtrace doesn't go that far to either make QT or KDE guilty of
that, i think.
non-gallium and non-drm currently, also tried latest 7.8 release.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=40936
Summary: register address overlap make line stipple error
Product: Mesa
Version: 7.11
Platform: Other
OS/Version: All
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/DRI/R600
AssignedTo: dri-devel(a)lists.freedesktop.org
ReportedBy: raoxianhong(a)163.net
In file r700_chip.c function r700SendSUState:
R600_OUT_BATCH_REGSEQ(PA_SU_POINT_SIZE, 4);
R600_OUT_BATCH(r700->PA_SU_POINT_SIZE.u32All);
R600_OUT_BATCH(r700->PA_SU_POINT_MINMAX.u32All);
R600_OUT_BATCH(r700->PA_SU_LINE_CNTL.u32All);
R600_OUT_BATCH(r700->PA_SU_VTX_CNTL.u32All);
must be:
R600_OUT_BATCH_REGSEQ(PA_SU_POINT_SIZE, 3);
R600_OUT_BATCH(r700->PA_SU_POINT_SIZE.u32All);
R600_OUT_BATCH(r700->PA_SU_POINT_MINMAX.u32All);
R600_OUT_BATCH(r700->PA_SU_LINE_CNTL.u32All);
R600_OUT_BATCH_REGVAL(PA_SU_VTX_CNTL, r700->PA_SU_VTX_CNTL.u32All);
NOTE:
PA_SU_POINT_SIZE ; /* 0xA280 */
PA_SU_POINT_MINMAX ; /* 0xA281 */
PA_SU_LINE_CNTL ; /* 0xA282 */
PA_SU_VTX_CNTL ; /* 0xA302 */
PA_SC_LINE_STIPPLE ; /* 0xA283 */
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=37490
Summary: texture corruption in r600/r600g when using DRI2, no
texture corruption in r600 with dri1
Product: Mesa
Version: 7.10
Platform: x86-64 (AMD64)
OS/Version: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/DRI/R600
AssignedTo: dri-devel(a)lists.freedesktop.org
ReportedBy: nenolod(a)systeminplace.net
hi,
i get texture corruption as seen in the attached screenshot when using dri2.
when running more 3D intensive applications (like say, etracer), the texture
corruption increases resulting in some graphics primitives not being rendered.
this does not happen with DRI1, with DRI1, there is no corruption and all
primitives are rendered as expected.
this is on linux 2.6.38.6 with alpine patches, mesa 7.10.2 and xorg 1.10 with
xf86-video-ati 6.14.1, libdrm 2.4.25 and uclibc 0.9.32-rc3 (also with alpine
patches).
there are some bugs that look similar to what i am seeing, but they are all
marked RESOLVED, and none of them mention DRI2.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=34377
Summary: Radeon driver PCIe throughput not up to PCIe2.0 levels
Product: Mesa
Version: git
Platform: x86 (IA32)
OS/Version: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/DRI/R600
AssignedTo: dri-devel(a)lists.freedesktop.org
ReportedBy: lucvermoesen(a)gmail.com
Created an attachment (id=43476)
--> (https://bugs.freedesktop.org/attachment.cgi?id=43476)
test data and test program for PCIe gen2 issue
On an HD5450 card, when I load the latest gallium3D driver with kernel
2.6.38-rc4 and firmware I got from
http://people.freedesktop.org/~agd5f/radeon_ucode/ , this together with the
latest git checkouts for X and modules (and thus also xf86-video-ati) and
latest mesa git checkout that has been built with –enable-gallium-r600
installing the radeon kernel module with
modprobe radeon modeset=1 pcie_gen2=1
Then I get 0.5GB/s CPU->GPU
>From GPU -> CPU, I get about the same 0.5GB/s.
When I load the fglrx ati proprietary driver (11.1) for the 5450 card, then I
get throughputs of about 2GB/s in both directions.
Running the same test in same environment on the HD5970
with the gallium drivers and kernel mode setting and pcie_gen2 activation, i
get about the same figures as above.
With fglrx for 5970, then 5970 only performs well in CPU->GPU with about 2GB/s
and only 0.5GB/s in GPU->CPU direction
I have included the test and configuration output for both cases (fglrx and
radeon) and also code for the testprogram might you want to reproduce this
case.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.