[drm : i830_wait_ring] *ERROR* space : 131056 wanted 131064
Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
sorry I got no real clue what could cause this I think the first thing you could do is to identify the original cause why your x-server hangs and not the symptom (x-server itself). When you change to the console, locate the cpu-consuming task(s) with the command "top". If you have got these you could kill them or look for further solutions.
After reading some postings on this in the Google groups I think it might not be related to some very cpu-consuming tasks, but rather a problem with your x-server itself. Maybe trying a newer version of x-org could make you happier?
Thanks titopoquito it was really kind of you answer to my this post also
This type of problem comes when a big application is running and it hangs the X server or say if some application is running very slowly and it makes everything very slow so i kill the X server and get the above errors. Some specific examples are :
i)When i play quake3 in Gnome or in kde with the arts server disabled it hangs (though quake works fine in kde with arts enabled)
ii)While playing some games with wine the game hangs my X and if i kill it i get the same error.
the output of the top command in the case when quake3 hangs is :
PID USER PRI NI SIZE RSS SHARE STAT %CPU %MEM TIME CPU COMMAND
5049 root 25 0 108M 79M 2692 R 99.8 33.0 3:56 0 quake3.x86
5012 root 16 0 1092 1092 884 R 0.1 0.4 0:00 0 top
1 root 16 0 400 368 344 S 0.0 0.1 0:04 0 init
and so on
looks like quake3.x86 was consuming a lot of my resources
but these are not the only situations only when i get this error. I have experienced this error during startup when the X would refuse to start and give the same error. People using Fedora Core 2 have also experienced the same sort of error with the X
I'll also take your advice and try getting a newer version of X