|
|
I was trying to do a render of a HUGE pile of .pov files using a bash
session. When I came back the next morning, I found that the system was
locked up, and that it had essentially stopped mid-render.
I am trying to diagnose the problem. (At first I worried it a quirk of
linux or KDE and thoroughly embarassed myself on my local LUG email list.)
So here's my current top readout when things appear to be running well.
Suppose I find another alleged system lock-up tomorrow morning and am able
to get top to run. What kinds of things could go wrong, and how would I
differentiate between a problem in KDE's abruptly sending system to sleep,
or my use of povray using up all the memory, memory leaks, etc?
Thanks.
----------------------------------------------------
top - 12:37:18 up 5:55, 1 user, load average: 1.13, 1.26, 1.23
Tasks: 81 total, 2 running, 79 sleeping, 0 stopped, 0 zombie
Cpu(s): 97.3% us, 2.7% sy, 0.0% ni, 0.0% id, 0.0% wa, 0.0% hi, 0.0% si
Mem: 515984k total, 509000k used, 6984k free, 76864k buffers
Swap: 2963984k total, 0k used, 2963984k free, 153340k cached
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
9969 greg 25 0 8196 3884 2132 R 93.2 0.8 17:18.41 povray
8865 root 15 0 126m 50m 2652 S 4.3 10.0 2:20.25 Xorg
9937 greg 15 0 30188 16m 13m S 3.0 3.3 0:14.38 konsole
1 root 16 0 1560 524 456 S 0.0 0.1 0:00.95 init
2 root 34 19 0 0 0 S 0.0 0.0 0:00.00 ksoftirqd/0
3 root 10 -5 0 0 0 S 0.0 0.0 0:00.18 events/0
4 root 16 -5 0 0 0 S 0.0 0.0 0:00.01 khelper
5 root 10 -5 0 0 0 S 0.0 0.0 0:00.00 kthread
7 root 20 -5 0 0 0 S 0.0 0.0 0:00.00 kacpid
--------------------------------------------
Post a reply to this message
|
|