CPU usage shooting almost aFC 13 hangs from time to time

eliassal · 11-07-2010, 03:03 PM

Since IOI rebooted ince morning, until now I was working fine, all of a sudden and for no obvious reason Fedora 13 again freezed.

I logged on using remote desktop, and found the following

Quote:

PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
9578 root 20 0 110m 6364 3504 R 84.7 0.3 1:16.66 Xorg
8108 root 20 0 123m 18m 4964 S 52.6 0.9 1:17.60 Xorg
7228 root 20 0 147m 39m 9.8m R 45.1 2.0 3:38.08 Xorg

after refresh

Quote:

PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
7228 root 20 0 147m 39m 9.8m S 77.8 2.0 5:15.90 Xorg
9648 root 20 0 110m 6360 3504 R 49.2 0.3 0:39.80 Xorg
8108 root 20 0 123m 18m 4964 R 48.9 0.9 2:40.06 Xorg

Here is the memory stat

Quote:

salam@salamlinux ~]$ free
total used free shared buffers cached
Mem: 2057208 1671936 385272 0 223868 562132
-/+ buffers/cache: 885936 1171272
Swap: 4095992 3780 4092212

I used your -9 flag with Kill, I got a white ugly screen on the display attached to the linux machine

paulsm4 · 11-07-2010, 10:10 PM

OK - so the problem definitely isn't memory

Q: Any idea why you've got *three* "Xorg" processes? Which, together, are using 184% of your CPU? I'm guessing this is Xrdp...

Q: You have a multi-core CPU, I presume.

Q: Does the problem ever occur when you're NOT using remote GUI login?

Q: When the problem occurs during remote login, can you do a command-line "ssh", kill the offending Xorg process(es), and stabilize the system that way?

Please do the following, cut/paste the relevant output:
1. cat /etc/*red*

2. uname -a

3. cat /proc/cpuinfo (just the relevant parts from your first CPU)

4. less /var/log/Xorg.0.log
<= Search for any errors ("EE")

eliassal · 11-08-2010, 02:45 AM

Q 1 - No idea, I started having several Xorg when I issued the "Kill -9 offending xorh pid"

Q2 - Yes dual core AMD brand new

Q3 - Problem occurs in different scenarios, sometimes while doin g nothing, after 1 hour of booting, sometimes continue working correctly for 2 days and then fedora freezes. I always access remotly after fedora freezes.

Q4 - I dont understand the question. As I said I log using remote desktop from a windows 7 machine (xrdp runs on my server), open a commend line and do "Kill.....". Is using SSH needs a different procedure.

Point 1 - Outpt

Quote:

[salam@salamlinux ~]$ cat /etc/*red*
cat: /etc/redhat-lsb: Is a directory
Fedora release 13 (Goddard)

Point 2

Quote:

Linux salamlinux 2.6.33.6-147.fc13.x86_64 #1 SMP Tue Jul 6 22:32:17 UTC 2010 x86_64 x86_64 x86_64 GNU/Linux

Point 3

Quote:

[salam@salamlinux ~]$ cat /proc/cpuinfo
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 23
model name : Pentium(R) Dual-Core CPU E5300 @ 2.60GHz
stepping : 10
cpu MHz : 1200.000
cache size : 2048 KB
physical id : 0
siblings : 2
core id : 0
cpu cores : 2
apicid : 0
initial apicid : 0
fpu : yes
fpu_exception : yes
cpuid level : 13
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts rep_good aperfmperf pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm xsave lahf_lm tpr_shadow vnmi flexpriority
bogomips : 5200.10
clflush size : 64
cache_alignment : 64
address sizes : 36 bits physical, 48 bits virtual
power management:

Point 4

Quote:

X.Org X Server 1.8.2
Release Date: 2010-07-01
[ 34.454] X Protocol Version 11, Revision 0
[ 34.454] Build Operating System: x86-07 2.6.18-194.3.1.el5
[ 34.454] Current Operating System: Linux salamlinux 2.6.33.6-147.fc13.x86_64 #1 SMP Tue Jul 6 22:32:17 UTC 2010 x86_64
[ 34.454] Kernel command line: ro root=UUID=ae72b7f7-2a24-4797-9be6-dd079a3e713a rd_NO_LUKS rd_NO_LVM rd_NO_MD rd_NO_DM LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYTABLE=us rhgb quiet
[ 34.454] Build Date: 01 July 2010 06:04:08AM
[ 34.454] Build ID: xorg-x11-server 1.8.2-1.fc13
[ 34.456] Current version of pixman: 0.18.0
[ 34.456] Before reporting problems, check http://bodhi.fedoraproject.org/
to make sure that you have the latest version.
[ 34.456] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 34.456] (==) Log file: "/var/log/Xorg.0.log", Time: Mon Nov 8 09:23:53 2010
[ 34.497] (==) Using config directory: "/etc/X11/xorg.conf.d"
[ 34.497] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[ 34.539] (==) No Layout section. Using the first Screen section.
[ 34.539] (==) No screen section available. Using defaults.
[ 34.539] (**) |-->Screen "Default Screen Section" (0)
[ 34.539] (**) | |-->Monitor "<default monitor>"
[ 34.540] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[ 34.540] (==) Automatically adding devices
[ 34.540] (==) Automatically enabling devices
[ 34.540] (==) FontPath set to:
catalogue:/etc/X11/fontpath.d,
built-ins
[ 34.540] (==) ModulePath set to "/usr/lib64/xorg/modules"
[ 34.540] (II) The server relies on udev to provide the list of input devices.
If no devices become available, reconfigure udev or disable AutoAddDevices.
[ 34.540] (II)
***************************************************************
***************************************************************
** Fedora switched to udev-based device detection with **
** xorg-x11-server-1.7.99.901-1. Custom HAL configuration **
** stored in /etc/hal/fdi/policy will not be seen by this **
** server version. If you have such configuration you will **
:

eliassal · 11-08-2010, 03:12 AM

Here is the full output of the . What is astonishing ne I see nVidia in it.
2 months back, I tried to install nVidia driver for 3D samsung screen and got errors, so I thought it didnt install.

unSpawn · 11-18-2010, 03:32 AM

Please post your topic in only one thread. Posting a single thread will make it easier for members to help you and will keep the discussion in one place. Your threads have been merged to help your question get the exposure it deserves.