Bug 56464

After totem and minecraft have got killed, gnome-shell is running slow (also totem is), and glxgears is not running vsynced.

Created attachment 69156 [details]
Xorg log, if there is anything usefull.

Does it work better with mesa 8.0.x?  Might be related to bug 56405.

(In reply to comment #3)
> Does it work better with mesa 8.0.x?  Might be related to bug 56405.

Will test with mesa 8.0.4 when i get time, i can also confirm that i have bug 56405.

(In reply to comment #4)
> (In reply to comment #3)
> > Does it work better with mesa 8.0.x?  Might be related to bug 56405.
> 
> Will test with mesa 8.0.4 when i get time, i can also confirm that i have
> bug 56405.
Problems seems solved with mesa 8.0.4. Also can't mesa 9.0 to work realy with gdm, works 1 out of 10 times or something.

Any chance you can bisect to identify what commit is causing the problem?

(In reply to comment #6)
> Any chance you can bisect to identify what commit is causing the problem?

"Just" all this commit http://cgit.freedesktop.org/mesa/mesa/log/?h=9.0 ? and could the problem also be in mesa 8.0.5? Because then i will mesa 8.0.5

(In reply to comment #7)
> (In reply to comment #6)
> > Any chance you can bisect to identify what commit is causing the problem?
> 
> "Just" all this commit http://cgit.freedesktop.org/mesa/mesa/log/?h=9.0 ?
> and could the problem also be in mesa 8.0.5? Because then i will mesa 8.0.5

If 8.0.5 has a similar problem, then you could just focus on the 8.0 branch.  Otherwise, it's probably easiest to checkout master and try master.  If that has the same issues as 9.0, then switch to a commit near where the 8.0 branch was branched, then bisect between that and the top of master.

(In reply to comment #8)
> (In reply to comment #7)
> > (In reply to comment #6)
> > > Any chance you can bisect to identify what commit is causing the problem?
> > 
> > "Just" all this commit http://cgit.freedesktop.org/mesa/mesa/log/?h=9.0 ?
> > and could the problem also be in mesa 8.0.5? Because then i will mesa 8.0.5
> 
> If 8.0.5 has a similar problem, then you could just focus on the 8.0 branch.
> Otherwise, it's probably easiest to checkout master and try master.  If that
> has the same issues as 9.0, then switch to a commit near where the 8.0
> branch was branched, then bisect between that and the top of master.
For some unknown reason mesa master won't compile:
Last lines:
r600_shader.c: In function ‘r600_compute_shader_create’:
r600_shader.c:252:2: fejl: too few arguments to function ‘r600_bytecode_init’
In file included from r600_shader.h:26:0,
                 from r600_shader.c:27:
r600_asm.h:224:6: bemærk: declared here
r600_llvm.c: In function ‘llvm_load_input’:
r600_llvm.c:124:11: advarsel: variable ‘offset’ set but not used [-Wunused-but-set-variable]
make[4]: *** [r600_shader.o] Fejl 1
make[4]: *** Venter på uafsluttede job....
In file included from r600_llvm.c:3:0:
r600_llvm.c: In function ‘llvm_load_system_value’:
../../../../src/gallium/auxiliary/gallivm/lp_bld_const.h:124:23: advarsel: ‘chan’ may be used uninitialized in this function [-Wmaybe-uninitialized]
r600_llvm.c:41:11: bemærk: ‘chan’ was declared here
make[4]: Forlader katalog '/home/kristian/Hentninger/mesa-git/src/build/src/gallium/drivers/r600'
make[3]: *** [all-recursive] Fejl 1
make[3]: Forlader katalog '/home/kristian/Hentninger/mesa-git/src/build/src/gallium/drivers'
make[2]: *** [all-recursive] Fejl 1
make[2]: Forlader katalog '/home/kristian/Hentninger/mesa-git/src/build/src/gallium'
make[1]: *** [all-recursive] Fejl 1
make[1]: Forlader katalog '/home/kristian/Hentninger/mesa-git/src/build/src'
make: *** [all-recursive] Fejl 1

*** This bug has been marked as a duplicate of bug 56405 ***