LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Newbie (https://www.linuxquestions.org/questions/linux-newbie-8/)
-   -   [drm : i830_wait_ring] *ERROR* space : 131056 wanted 131064 (https://www.linuxquestions.org/questions/linux-newbie-8/%5Bdrm-i830_wait_ring%5D-%2Aerror%2A-space-131056-wanted-131064-a-301407/)

koodoo 03-14-2005 06:49 AM

X server hangs.Gives error on being killed
 
Hi,

I am using Fedora Core 1.
Sometimes due to some processes my X server hangs

So with no option left i do CTRL-ALT-F2 and go to the text mode screen. There i kill the X server and get the following error message :

[root@localhost root]# [drm : i830_wait_ring] *ERROR* space : 131056 wanted 131064
[drm : i830_wait_ring] *ERROR* space : 131056 wanted 131064
[drm : i830_wait_ring] *ERROR* lockup
[drm : i830_wait_ring] *ERROR* space : 131048 wanted 131064
[drm : i830_wait_ring] *ERROR* lockup
[drm : i830_wait_ring] *ERROR* space : 131040 wanted 131064
[drm : i830_wait_ring] *ERROR* lockup
[drm : i830_wait_ring] *ERROR* space : 131032 wanted 131064
[drm : i830_wait_ring] *ERROR* lockup
[drm : i830_wait_ring] *ERROR* space : 131024 wanted 131064
[drm : i830_wait_ring] *ERROR* lockup
[drm : i830_wait_ring] *ERROR* space : 131016 wanted 131064
[drm : i830_wait_ring] *ERROR* lockup
[drm : i830_wait_ring] *ERROR* space : 131008 wanted 131064
[drm : i830_wait_ring] *ERROR* lockup
[drm : i830_wait_ring] *ERROR* space : 131000 wanted 131064
[drm : i830_wait_ring] *ERROR* lockup
[drm : i830_wait_ring] *ERROR* space : 130992 wanted 131064
[drm : i830_wait_ring] *ERROR* lockup
[drm : i830_wait_ring] *ERROR* space : 130984 wanted 131064
[drm : i830_wait_ring] *ERROR* lockup
[root@localhost root]#


What could be the cause of this and what should i do ?


Thanx in anticipation

My system specifications are :
P4 2.4 Ghz processor
256 MB of RAM
Intel 845 chipset motherboard (on board video card Intel 845)
Distribution : Fedora Core 1

titopoquito 03-18-2005 12:26 AM

Hi koodoo,

sorry I got no real clue what could cause this :confused: 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.

titopoquito

titopoquito 03-18-2005 12:52 AM

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? :scratch:

koodoo 03-19-2005 12:27 AM

Hi,

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

Thanks again. You've been a great help!!!


All times are GMT -5. The time now is 03:01 PM.