From: Vincent Lefevre <vincent@vinc17.org>
To: zsh-workers@sunsite.dk
Cc: 482346@bugs.debian.org
Subject: Re: Bug#482346: zsh doesn't always wait for its children (-> zombie)
Date: Sun, 25 May 2008 02:41:01 +0200 [thread overview]
Message-ID: <20080525004101.GT7056@prunille.vinc17.org> (raw)
In-Reply-To: <20080524234002.GA35143@redoubt.spodhuis.org>
On 2008-05-24 16:40:02 -0700, Phil Pennock wrote:
> Since you're on a rarer architecture that doesn't see so much Linux
> kernel debugging, I'd be inclined to look at what has changed in the
> kernel's architecture-specific signal handling code. (But see below).
I don't know if the bug is new. I've never killed vlc in such a way
in the past. The current kernel is linux-image-2.6.24-1-powerpc
2.6.24-7.
> Further, it's strange that zombies are contributing to load average; if
> zsh is gone (killed off and no longer even possibly stuck in a tight
> loop) and there's the zombie and init left, then there shouldn't be
> anything contributing to load avg.
Yes, that's strange.
> If you use tools such as top(1), what processes are they attributing the
> load to?
None, and the CPU is idle:
top - 02:31:55 up 22:19, 6 users, load average: 4.09, 4.24, 4.25
Tasks: 117 total, 1 running, 115 sleeping, 0 stopped, 1 zombie
Cpu(s): 0.7%us, 0.7%sy, 0.0%ni, 98.4%id, 0.0%wa, 0.3%hi, 0.0%si, 0.0%st
Mem: 255432k total, 233456k used, 21976k free, 3004k buffers
Swap: 524280k total, 22820k used, 501460k free, 105548k cached
(The zombie is vlc.)
> Is the high load average confirmed by vmstat reports of idle
> CPU, or is the load avg really out of sync with CPU reality?
Here's vmstat output:
ay:~> vmstat
procs -----------memory---------- ---swap-- -----io---- -system-- ----cpu----
r b swpd free buff cache si so bi bo in cs us sy id wa
0 0 22820 26456 5520 99688 0 0 15 35 30 196 8 1 88 3
--
Vincent Lefèvre <vincent@vinc17.org> - Web: <http://www.vinc17.org/>
100% accessible validated (X)HTML - Blog: <http://www.vinc17.org/blog/>
Work: CR INRIA - computer arithmetic / Arenaire project (LIP, ENS-Lyon)
next prev parent reply other threads:[~2008-05-25 0:41 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20080521235008.GA5600@ay.vinc17.org>
[not found] ` <20080521235930.GW7056@prunille.vinc17.org>
2008-05-22 23:33 ` Clint Adams
2008-05-23 14:39 ` Bart Schaefer
2008-05-23 14:57 ` Clint Adams
2008-05-23 22:43 ` Vincent Lefevre
2008-05-23 22:45 ` Vincent Lefevre
2008-05-23 23:04 ` Vincent Lefevre
2008-05-24 2:55 ` Clint Adams
2008-05-24 12:44 ` Vincent Lefevre
2008-05-24 14:25 ` Peter Stephenson
2008-05-24 15:27 ` Stephane Chazelas
2008-05-24 15:58 ` Stephane Chazelas
2008-05-24 17:53 ` Clint Adams
2008-05-24 17:41 ` Bart Schaefer
2008-05-24 18:25 ` Stephane Chazelas
2008-05-24 23:40 ` Phil Pennock
2008-05-25 0:41 ` Vincent Lefevre [this message]
2008-05-25 1:23 ` Phil Pennock
2008-05-25 21:37 ` Vincent Lefevre
2008-05-25 22:26 ` Phil Pennock
2008-05-25 23:34 ` Vincent Lefevre
2008-05-25 23:43 ` Vincent Lefevre
2008-05-26 0:31 ` Bart Schaefer
2008-05-25 10:08 ` Stephane Chazelas
2008-05-25 21:54 ` Vincent Lefevre
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=20080525004101.GT7056@prunille.vinc17.org \
--to=vincent@vinc17.org \
--cc=482346@bugs.debian.org \
--cc=zsh-workers@sunsite.dk \
/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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).