Amd CCC...nexuiz... and X full CPU...but glxgears fix the problem?!

[rbmorse]

so.....the only solution is running glxgears at every xorg start? WOW great fglrx driver -_-"

Or, just don't run the control center (amdcccle).

If you do run the control center you have to kill it manually OR run glxgears after you close the CCC window.

Other than that, it works pretty well for me.

[karlpiuemeno]

Or, just don't run the control center (amdcccle).

If you do run the control center you have to kill it manually OR run glxgears after you close the CCC window.

Other than that, it works pretty well for me.

no.. xorg goes crazy also if I run only nexuiz...
for example..


I turn on my pc... ok desktop.... I open NEXUIZ... nothing happen.... I open terminal, glxgears... puff, nexuiz screen pops up!

same thing with amdccc.......

[rbmorse]

Ok...then don't do that <g>.

Have you filed a bug report? Sometimes it helps.

[wojtek5001]

bug already filled by someone

It is bug #1003 http://ati.cchtml.com/show_bug.cgi?id=1003
I have also submited simple workaround there. It works for me.


I've also made some deeper investigation - compare strace output (strace glxinfo) at first time and second time. Here are results (buggy output is submitted in bugzilla):
Line 528 bad:

ioctl(5, 0x4008642a, 0x7fffb2c30cb0)    = 0

not called in normal run

Line 576 good:

ioctl(5, 0x4008642a, 0x7fff22eeac50)    = 0

not called in badly run

loop seems to begin on line 754, where in
normal run couple of:

ioctl(5, 0xc03064a6, 0x7fff22eecca0)

is called,

and fews calls later output messages are printed.

In case of bug, loop begins:

select(4, [3], [3], NULL, NULL)         = 1 (out [3])
writev(3, [{"+\1\1\0", 4}], 1)          = 4
select(4, [3], [], NULL, NULL)          = 1 (in [3])
read(3, "\1\2&\0\0\0\0\0\f\0`\1\0\0\0\0D\f\0\0\0\0\0\0\340\37>\245"..., 4096) = 32
read(3, 0x605eb4, 4096)                 = -1 EAGAIN (Resource temporarily unavailable)
select(4, [3], [3], NULL, NULL)         = 1 (out [3])
writev(3, [{"\3\1\2\0\2\0\200\1\16\0\2\0\2\0\200\1", 16}], 1) = 16
select(4, [3], [], NULL, NULL)          = 1 (in [3])
read(3, "\1\0\'\0\3\0\0\0*\0\0\0\1\0\0\1\377\377\377\377\0\0\0\0"..., 4096) = 76
read(3, 0x605eb4, 4096)                 = -1 EAGAIN (Resource temporarily unavailable)
select(4, [3], [3], NULL, NULL)         = 1 (out [3])
writev(3, [{"\223\1\3\0\0\0\0\0\2\0\200\1", 12}], 1) = 12
select(4, [3], [], NULL, NULL)          = 1 (in [3])
read(3, "\1\334)\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0d\0d\0\0\0\0\0"..., 4096) = 32
read(3, 0x605eb4, 4096)                 = -1 EAGAIN (Resource temporarily unavailable)
ioctl(5, 0x4008642a, 0x7fffb2c32ac0)    = 0

(that strange ioclt 0x4008642a again

Can someone explain that ioctl. I can't find it in any kernel sources, so it must be some proprietary AMD/ATI driver call (or I overlooked something?).

I probably shuld write that to bugzilla, but no one seems to care ...