Bug 36018

(In reply to comment #1)
> Are these messages serious, any things i can provide to get rid of them?

They mean that some rendering operations are dropped, do you notice any visual elements missing or looking incorrect? Is there anything related in the stderr output of 3D apps?

Please attach (as opposed to paste) the output of glxinfo.

Created attachment 45340 [details]
glxinfo output

GlxInfo Output.
Sometimes i miss the graphics of my gnome cpufreq applets (got 4 - 2 are showing, 2 are garbled - don't know if this is related to those error messages).

(In reply to comment #2)
> Sometimes i miss the graphics of my gnome cpufreq applets (got 4 - 2 are
> showing, 2 are garbled - don't know if this is related to those error
> messages).

It might be. If you disable/remove the garbled ones, do the kernel messages stop?

Are you using compiz or another compositing manager that uses OpenGL?

At the moment all are showing fine and nothing is garbled - no kernel messages shown at the moment (don't know how to trigger them).
No i am using plain metacity - all effects disabled, no OpenGL usage afaik.

If there's no OpenGL involved, it can't be a Mesa driver issue. So you're saying that the messages happened while only using the X driver, and only with kernel 2.6.38.2? Which kernel did you use before?

Those messages i did see since using 2.6.38(.2) one (natty build).
Yes there's no OpenGL involved (afaik tell, i did not explicitly used opengl - maybe some program i am using does use opengl and i don't know it - as i don't know exactly which program/usage does force those errors i cant tell for sure - sorry - only guess) - maybe i can run some opengl programs or do other "tests" to provoke those messages - maybe you've got an idea what might be the cause of this issue and things i can try.

Before i used the maverick 2.6.35.x kernel and i am really sure i did not see unknown packet type or invalid command stream messages - if i find a way to get them reproduced i can test this.

(In reply to comment #6)
> Yes there's no OpenGL involved (afaik tell, i did not explicitly used opengl -
> maybe some program i am using does use opengl and i don't know it - as i don't
> know exactly which program/usage does force those errors i cant tell for sure -
> sorry - only guess)

Something like

 sudo lsof|grep _dri.so

should show every process using a Mesa 3D driver.


> maybe you've got an idea what might be the cause of this issue and things i can
> try.

The cpufreq applets seem like the most promising lead at this point. Basically, any time you notice any visual element(s) missing or looking wrong, check if new messages appeared in the kernel output around the same time.

(In reply to comment #7)

> Something like
> 
>  sudo lsof|grep _dri.so
> 
> should show every process using a Mesa 3D driver.

The only thing is:

Xorg       7982       root  mem       REG                8,3     3443360    6621153 /usr/lib/dri/r300_dri.so

Xorg itself.


> 
> 
> The cpufreq applets seem like the most promising lead at this point. Basically,
> any time you notice any visual element(s) missing or looking wrong, check if
> new messages appeared in the kernel output around the same time.

At the moment there are again some glitches - 3 of the 4 applets are "iconless" but clicking on them still get my interaction - so yes, they are there but not shown (whatever may cause this - maybe unrelated) - resizing the panel does bring them back but does not cause erros to appear.
I've got only 2 lines from yesterday to today:

[80165.008860] [drm:r100_cs_packet_parse] *ERROR* Unknown packet type 1 at 13234 !
[80165.008865] [drm:radeon_cs_ioctl] *ERROR* Invalid command stream !

So i am still unable to tell (yet) which program or X usage does cause this.

Mass closure: This bug has been untouched for more than six years, and is not
obviously still valid. Please reopen this bug or file a new report if you continue to experience issues with current releases.