public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Priit Randla <priit.randla@eyp.ee>
To: linux-kernel@vger.kernel.org
Subject: scheduler went mad?
Date: Wed, 11 Apr 2001 16:24:48 +0200	[thread overview]
Message-ID: <3AD46930.B6CC9565@eyp.ee> (raw)



Hi,
   

   Yesterday i tried to start cdda2wav but somehow it didn't do
anything.
  It didn't die to kill -9 too. Machine was slow but usable. 
  vmstat 10 output:

  procs                      memory    swap          io    
system         cpu
 r  b  w   swpd   free   buff  cache  si  so    bi    bo   in    cs  us 
sy  id
 2  0  1   2972  40916    108  18292   0   0     0     0  121 12735   0
100   0
 2  0  1   2972  40492    108  18292   0   0     0     0  109 12740   1 
99   0
 2  0  1   2972  40492    108  18292   0   0     0     0  103 12996   0
100   0
 3  0  0   2972  40492    108  18292   0   0     0     0  102 12932   0
100   0
 3  0  1   2972  40492    108  18292   0   0     0     0  131 12652   1 
99   0
 2  0  0   2972  40496    108  18292   0   0     0     0  142 12562   1 
99   0
 2  0  0   2972  40500    108  18292   0   0     0     0  120 12684   0
100   0
 2  0  1   2972  40496    108  18292   0   0     0     0  140 12480   1 
99   0
 2  0  0   2972  39952    108  18292   0   0     0     0  160 11445   7 
93   0
 3  0  0   2972  39952    108  18292   0   0     0     0  178 12295   2 
98   0
 2  0  0   2972  39956    108  18292   0   0     0     0  214 11958   2 
98   0
 3  0  1   2972  39952    108  18292   0   0     0     0  138 12579   1 
99   0

cs field is absolutely ridiculous for my machine.																							

ps showed cdda2wav & kswapd eating all of processor time. When i tried
to close
netscape, it hang too and joined cdda2wav and kswapd:

  PID USER     PRI  NI  SIZE  RSS SHARE STAT  LIB %CPU %MEM   TIME
COMMAND
 9990 priitr    17   0 42380  41M  9928 R       0 32.5 33.4  21:47
netscape-commun
    3 root      17   0     0    0     0 SW      0 32.3  0.0  11:12
kswapd
10538 priitr    16   0    84    8     0 R       0 32.3  0.0  11:09
cdda2wav
    5 root       9   0     0    0     0 SW      0  1.5  0.0   0:19
bdflush
10616 priitr    13   0   856  856   668 R       0  0.7  0.6   0:00 top
  657 root       9   0 21160  20M  1668 S       0  0.1 16.7  29:36 X


I couldn't leave X and had to kill it. After that, both netscape and
cdda2wav were
gone and everything looks normal since then.
I'm running 2.4.3ac3 right now.

dmesg:

             reply	other threads:[~2001-04-11 14:29 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-11 14:24 Priit Randla [this message]
2001-04-11 18:46 ` scheduler went mad? Josh McKinney
2001-04-12 15:46   ` Jens Axboe
  -- strict thread matches above, loose matches on Subject: below --
2001-04-12 14:57 Valdis.Kletnieks
2001-04-12 15:12 ` Alan Cox
2001-04-12 15:44   ` Valdis.Kletnieks
2001-04-12 18:31   ` Valdis.Kletnieks
2001-04-12 15:43 ` Hugh Dickins
2001-04-12 16:02   ` Alan Cox
2001-04-12 16:29     ` Rik van Riel
2001-04-12 15:08       ` Marcelo Tosatti
2001-04-12 15:10         ` Marcelo Tosatti
2001-04-12 18:18           ` Szabolcs Szakacsits
2001-04-12 17:56             ` Rik van Riel
2001-04-12 20:12               ` Szabolcs Szakacsits
2001-04-12 20:18                 ` Rik van Riel
2001-04-12 23:02                   ` Szabolcs Szakacsits
2001-04-12 22:24                     ` Valdis.Kletnieks
2001-04-12 16:53         ` Rik van Riel

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=3AD46930.B6CC9565@eyp.ee \
    --to=priit.randla@eyp.ee \
    --cc=linux-kernel@vger.kernel.org \
    /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