public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Taliver Heath <taliver@cs.rutgers.edu>
To: linux-kernel@vger.kernel.org
Subject: Kernel 2.6.0-test9 Zombie Issue
Date: Wed, 19 Nov 2003 09:07:30 -0500	[thread overview]
Message-ID: <1069250850.11115.5.camel@leblon> (raw)

[-- Attachment #1: Type: text/plain, Size: 1918 bytes --]

linux_ver:
Linux leblon 2.6.0-test9 #1 Thu Nov 13 09:18:59 EST 2003 i686 unknown

Gnu C                  3.3.2
Gnu make               3.80
binutils               2.14.90.0.7
util-linux             2.12
mount                  2.11n
module-init-tools      0.9.15-pre3
e2fsprogs              1.27
xfsprogs               2.6.0
PPP                    2.4.1
Linux C Library        2.3.2
Dynamic linker (ldd)   2.3.2
Procps                 100.
Net-tools              1.60
Kbd                    1.06
Sh-utils               2.0.11
Modules Loaded         uhci_hcd visor usbserial intel_agp agpgart
parport_pc lp parport hid 8250 serial_core cpuid msr apm es1371
soundcore ac97_codec usbkbd usbcore


Problem description:
I've noticed that if my system is very heavily loaded, I start to get
Zombies for any short lived processes.  I've googled for this, but can't
seem to find anything relating to it.  I'm running the 2.6.0-test9
kernel.  Is this something in the FAQ?

Specifically, I can recreate this behavior by getting my system
overloaded (converting .wav to .ogg, xmms, mozilla 10 page reload, on
fluxbox on a PIII 667) and then running many instances of aumix from the
keyboard shortcut.  Fluxbox normally detects the death of the children,
and I have a few Zombies which come from other programs as well
(mozilla, evolution, and others).

My theory is, and this has no code check to back it up in the slightest,
is that the preempt patch is throwing off the process management of the
kernel.  Or worse, perhaps the wait call is returning that it was
interrupted, and few programs are written to suppoort error checking on
the wait call (since in many instances you don't really care what
happened to the process).

I apologize for not scouring the kernel archives about this before I
emailed, but a quick scan didn't seem to turn up anything relevant.

--Taliver Heath

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

                 reply	other threads:[~2003-11-19 14:07 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=1069250850.11115.5.camel@leblon \
    --to=taliver@cs.rutgers.edu \
    --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