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

2007-02-28 Thread Panagiotis Papadakos
I can't reproduce this error with the scratch patch I sent earlier. ;-) On Thursday 01 February 2007 20:08, Panagiotis Papadakos wrote: > My application sometimes crashes with the following message (most of the > times when I run it with valgrind): > drmRadeonCmdBuffer: -22 (exiting) > > And in dm

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

2007-02-02 Thread Panagiotis Papadakos
On Friday 02 February 2007 12:01, Michel Dänzer wrote: > Hmm, I think this could only happen with several file descriptors > using the same DRM context ID. Is your application multithreaded? No, my application is not multithreaded. > > > This is using r300 driver and aiglx. > > FWIW, does disablin

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

2007-02-02 Thread Michel Dänzer
[ Please follow up to one list only, I suggest dri-devel ] On Thu, 2007-02-01 at 20:08 +0200, Panagiotis Papadakos wrote: > 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

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 Th