View previous topic :: View next topic |
Author |
Message |
djf_jeff Apprentice
Joined: 17 Feb 2003 Posts: 174 Location: Quebec
|
Posted: Thu Mar 17, 2005 4:52 am Post subject: dmesg, logging and ATI driver |
|
|
Hi,
I have installed the lastest ATI driver and get something like :
[fglrx:firegl_alloc_bufs] *ERROR* Failed to create buffer queue (-12)
that fill up my syslog and dmesg. When I play at Unreal, I think this make the unresponsive (it log up to 10000 entry of them). I try to fix this issue but I found nothing on the net. So I have to "hack" this and make a quick fix.
What I do, is before I start the game, I run a small script that remove kernel logging from syslogd.
But, how can I remove the entry to show up in dmesg? I have read something about the "-n X" switch. How to set it back to normal behaviour after playing my game?
And what to do and klogd?
Thanks a lot in advance |
|
Back to top |
|
|
Sith_Happens Veteran
Joined: 15 Dec 2004 Posts: 1807 Location: The University of Maryland at College Park
|
Posted: Thu Mar 17, 2005 5:39 am Post subject: |
|
|
Well, any logger just reads the output of various sources (/dev/log, /proc/kmsg...) and writes the output to files. You can usually apply filters to these when it comes to actually saving the logs. dmesg is a little different. It outputs the contents of the kernel ring buffer, you can't really change what's in the kernel ring buffer (besides clearing it with dmesg -c). Using the -n flag will only show messages with a certain log level. It doesn't however change the contents of the buffer, so you don't have to worry about losing any information. _________________ "That question was less stupid; though you asked it in a profoundly stupid way."
I'm the brains behind Jackass! | Tutorials: Shorewall |
|
Back to top |
|
|
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|