From: Karsten Merker <karsten@excalibur.cologne.de>
To: Ralf Baechle <ralf@oss.sgi.com>
Cc: linux-mips@fnet.fr, linux-mips@oss.sgi.com
Subject: Re: process lockups
Date: Tue, 24 Oct 2000 19:55:55 +0200 [thread overview]
Message-ID: <20001024195555.A4469@excalibur.cologne.de> (raw)
In-Reply-To: <20001024163843.A7342@bacchus.dhis.org>; from Ralf Baechle on Tue, Oct 24, 2000 at 04:38:43PM +0200
On Tue, Oct 24, 2000 at 04:38:43PM +0200, Ralf Baechle wrote:
> Which is a problem - I need exactly the WCHAN information to debug this
> problem.
Here we go...
Two major processes are running: a tar zxvf (PIDs 212 and 213) and a
dpkg-buildpackage. Both together should consume all CPU time available,
but they do not, they just sit idle. Interesting is that here there is no
process in state "D" as I had before. This seems to be reproducible.
These logs were created from a fresh cvs-checkout (already including your
patch).
root# ps -laww
F S UID PID PPID C PRI NI ADDR SZ WCHAN TTY TIME CMD
100 S 0 189 168 0 60 0 - 1000 pause ttyp0 00:00:00 screen
100 S 0 212 191 1 60 0 - 579 ? ttya0 00:00:00 tar
000 S 0 213 212 0 60 0 - 394 pipe_w ttya0 00:00:00 gzip
100 S 0 220 197 0 60 0 - 873 wait4 ttya2 00:00:00 dpkg-buildpacka
100 S 0 272 220 0 60 0 - 1563 wait4 ttya2 00:00:02 dpkg-source
000 S 0 277 272 0 60 0 - 394 pipe_w ttya2 00:00:00 gunzip
100 S 0 278 272 0 60 0 - 536 ? ttya2 00:00:00 cpio
000 S 0 279 278 0 60 0 - 864 wait4 ttya2 00:00:00 sh
000 S 0 280 279 0 60 0 - 333 pipe_w ttya2 00:00:00 egrep
000 R 0 283 196 0 60 0 - 800 - ttya1 00:00:00 ps
While this happens, top tells:
27 processes: 26 sleeping, 1 running, 0 zombie, 0 stopped
CPU states: 10.5% user, 9.5% system, 0.0% nice, 79.9% idle
Mem: 127056K av, 22064K used, 104992K free, 0K shrd, 488K buff
Swap: 0K av, 0K used, 0K free 10952K cached
PID USER PRI NI SIZE RSS SHARE STAT LIB %CPU %MEM TIME COMMAND
284 root 0 0 1048 1048 684 R 0 12.9 0.8 0:00 top
190 root 0 0 1204 1204 984 S 0 0.8 0.9 0:02 screen
1 root 0 0 484 484 408 S 0 0.0 0.3 0:02 init
[...]
Any further processes have 0% CPU.
After some time the tar zxvf suddenly starts running and decompresses the
archive in one step.
Hope this description is helpful, if you need further information, just
mail me.
Greetings,
Karsten
--
#include <standard_disclaimer>
Nach Paragraph 28 Abs. 3 Bundesdatenschutzgesetz widerspreche ich der Nutzung
oder Uebermittlung meiner Daten fuer Werbezwecke oder fuer die Markt- oder
Meinungsforschung.
next prev parent reply other threads:[~2000-10-24 17:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-24 1:22 process lockups Karsten Merker
2000-10-24 2:47 ` Ralf Baechle
2000-10-24 5:51 ` Houten K.H.C. van (Karel)
2000-10-24 11:15 ` Karsten Merker
2000-10-24 14:38 ` Ralf Baechle
2000-10-24 17:55 ` Karsten Merker [this message]
2000-10-25 1:29 ` Ralf Baechle
2000-10-24 15:09 ` Ralf Baechle
2000-10-24 12:25 ` Florian Lohoff
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20001024195555.A4469@excalibur.cologne.de \
--to=karsten@excalibur.cologne.de \
--cc=linux-mips@fnet.fr \
--cc=linux-mips@oss.sgi.com \
--cc=ralf@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox