public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Derek Glidden <dglidden@illusionary.com>
To: linux-kernel@vger.kernel.org
Subject: strange kapm-idled behaviour
Date: Tue, 02 Oct 2001 13:30:09 -0400	[thread overview]
Message-ID: <3BB9F9A1.3030803@illusionary.com> (raw)


(this is *not* a "why does kapm-ideld take up all my CPU time" question!)

I've noticed that on occasion, often when Java-based programs but not 
necessarily always, kapm-idled stops running, even when something like 
gkrellm or xosview doesn't show any CPU activity and when "w" shows zero 
load on the machine.

That in itself isn't too odd, but if, when kapm-idled gets in one of 
these weird states, I do 'ps' or run 'top', the kapm-idled thread will 
all of a sudden "come to life" and start running, but it will frequently 
"give up" and go completely idle after periods of other CPU activity.

I've tried to narrow down the conditions when kapm-idled starts acting 
like this, but the best I've come up with is "usually when I run a Java 
app, but not always, and sometimes when nothing out of the ordinary 
seems to be going on."

Usually when this strange behaviour is happening, doing a 'ps' shows 
that the kapm-idled thread is in 'SW' state.

I'm seeing this with the 2.4.10 kernel.  I don't remember noticing it 
with 2.4.9 or anything else previous.  I have SGI's XFS patches applied, 
but otherwise a stock kernel.

This is obviously not a critical issue, it's just strange.

Please CC me directly on any replies if anyone would like further 
information.

-- 
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
#!/usr/bin/perl -w
$_='while(read+STDIN,$_,2048){$a=29;$b=73;$c=142;$t=255;@t=map
{$_%16or$t^=$c^=($m=(11,10,116,100,11,122,20,100)[$_/16%8])&110;
$t^=(72,@z=(64,72,$a^=12*($_%16-2?0:$m&17)),$b^=$_%64?12:0,@z)
[$_%8]}(16..271);if((@a=unx"C*",$_)[20]&48){$h=5;$_=unxb24,join
"",@b=map{xB8,unxb8,chr($_^$a[--$h+84])}@ARGV;s/...$/1$&/;$d=
unxV,xb25,$_;$e=256|(ord$b[4])<<9|ord$b[3];$d=$d>>8^($f=$t&($d
 >>12^$d>>4^$d^$d/8))<<17,$e=$e>>8^($t&($g=($q=$e>>14&7^$e)^$q*
8^$q<<6))<<9,$_=$t[$_]^(($h>>=8)+=$f+(~$g&$t))for@a[128..$#a]}
print+x"C*",@a}';s/x/pack+/g;eval

usage: qrpff 153 2 8 105 225 < /mnt/dvd/VOB_FILENAME \
     | extract_mpeg2 | mpeg2dec -

          http://www.cs.cmu.edu/~dst/DeCSS/Gallery/
http://www.eff.org/                   http://www.anti-dmca.org/
    http://www.sciencemag.org/cgi/content/full/293/5537/2028


                 reply	other threads:[~2001-10-02 17:30 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=3BB9F9A1.3030803@illusionary.com \
    --to=dglidden@illusionary.com \
    --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