From: Jesper Krogh <jesper@krogh.cc>
To: Greg KH <gregkh@suse.de>
Cc: linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
torvalds@linux-foundation.org, stable@kernel.org
Subject: Re: Linux 2.6.27.13
Date: Sun, 01 Feb 2009 14:21:13 +0100 [thread overview]
Message-ID: <4985A1C9.4050005@krogh.cc> (raw)
In-Reply-To: <20090125004823.GA6711@kroah.com>
Greg KH wrote:
> We (the -stable team) are announcing the release of the 2.6.27.13
> kernel.
>
> It contains a wide range of bugfixes, and all users of the 2.6.27 kernel
> series are strongly encouraged to upgrade.
>
> I'll also be replying to this message with a copy of the patch between
> 2.6.27.12 and 2.6.27.13
>
> The updated 2.6.27.y git tree can be found at:
> git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-2.6.27.y.git
> and can be browsed at the normal kernel.org git web browser:
> http://git.kernel.org/?p=linux/kernel/git/stable/linux-2.6.27.y.git;a=summary
This may be just noise, but recently I have begun seeing Zombie
processes hanging on some nodes in the computescluster:
2006 2055 0.0 0.0 9144 1260 ? Ss 07:24 0:00 \_
-bash /z/gridengine/default/spool/node30/job_scripts/692747
2006 2060 39.0 38.7 1696468 1573884 ? S 07:24 160:21
\_ /usr/bin/perl /z/home/trunk//bin/workqueue/worker
2006 2225 0.0 0.0 0 0 ? Z 07:29 0:00
\_ [sh] <defunct>
ps faux output.
Killing the parent process makes it go awasy, but this one has been
sitting there for almost 7 hours by now, without going away, essentially
hagning this process.
Any suggestions?
--
Jesper
next prev parent reply other threads:[~2009-02-01 13:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-25 0:48 Linux 2.6.27.13 Greg KH
2009-01-25 0:49 ` Greg KH
2009-01-26 20:01 ` Jesper Krogh
2009-01-26 21:07 ` Greg KH
2009-01-27 0:37 ` Brandeburg, Jesse
2009-01-27 19:36 ` Jesper Krogh
2009-01-28 12:58 ` Jesper Krogh
2009-01-28 19:33 ` Trond Myklebust
2009-01-29 0:37 ` [stable] " Greg KH
2009-02-01 13:21 ` Jesper Krogh [this message]
2009-02-02 18:17 ` Greg KH
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=4985A1C9.4050005@krogh.cc \
--to=jesper@krogh.cc \
--cc=akpm@linux-foundation.org \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@kernel.org \
--cc=torvalds@linux-foundation.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