On Sat, July 4, 2009 03:58, Volker Armin Hemmann wrote: > On Samstag 04 Juli 2009, Jesús Guerrero wrote: > > > I don't filter anything. Just default metalog with default settings.
I use sysklogd, that shouldn't matter much though. The config is pretty standard, and certainly there's nothing related to fglrx in there. The logs on a normal day are, at most, a few kb's (without fglrx+.30). With that combo into scene, kern.log and syslog grow around 500mb each filling the whole var. I need to delete these two files and restart sysklogd to get some free space in /var (just in case someone around has a similar problem). A quick hack on the printk code in the kernel can be used though to solve all this spam. But the cpu usage doesn't get any better. I know not the reason why, but the truth is that xv wastes lots more of cpu to play video when I have fglrx+.30, with or without the logs, with or without patching the kernel. I really, really doubt that the configuration of my system has anything to do with this, unless it has to do something with some kernel setting. > I know how the logs are filled up with 3d apps - but it is not as bad on > THIS > system. So what might be the reason? No idea. But it's all fglrx spam, that's for sure. Why does it generate more in my system? Well, I blame the hardware, since it's a driver who creates all the spam, there are really few things that I could "missconfigure", besides my kernel, that would affect it. I don't use any essoteric stuff in xorg.conf, and I do not even use a compositing wm. > sorry about that last line. No harm done. Heat raises easily sometimes. I apologize for anything I've done wrong as well. Regards. -- Jesús Guerrero
