[Bug 6893] kernel oops with radeon and mythfrontend

2007-02-01 Thread bugme-daemon
http://bugzilla.kernel.org/show_bug.cgi?id=6893 --- Additional Comments From [EMAIL PROTECTED] 2007-02-01 02:58 --- Created an attachment (id=10247) -- (http://bugzilla.kernel.org/attachment.cgi?id=10247action=view) Test patch Not sure how this can happen with the !dev-irq_enabled

Small memory leak in __glXReportDamage

2007-02-01 Thread Panagiotis Papadakos
We don't free XRectangle *xrects memory. Patch attached. -- Papadakos Panagiotis --- src/glx/x11/glxext.c 2007-02-01 14:39:37.0 +0200 +++ src/glx/x11/glxext_new.c 2007-02-01 14:38:35.0 +0200 @@ -758,6 +758,7 @@ xrects[i].height = rects[i].y2 - rects[i].y1; } region =

Invalid reads from intersect_rect in radeon_state.c of r300 driver. [PATCH included]

2007-02-01 Thread Panagiotis Papadakos
Checking with valgrind I got some invalid reads. The message was like the following: ==6988== Invalid read of size 4 ==6988==at 0x4B3C7FD: intersect_rect (radeon_state.c:61) ==6988==by 0x4B3C9DA: radeonRecalcScissorRects (radeon_state.c:108) ==6988==by 0x4B3CAEC: radeonUpdateScissor

drm:radeon_cp_cmdbuf] *ERROR* radeon_cp_cmdbuf called without lock held problem

2007-02-01 Thread Panagiotis Papadakos
My application sometimes crashes with the following message (most of the times when I run it with valgrind): drmRadeonCmdBuffer: -22 (exiting) And in dmesg I get the following: [drm:radeon_cp_cmdbuf] *ERROR* radeon_cp_cmdbuf called without lock held, held -2147483648 owner d0297cc0 c7f35240