[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date: Mon, 2 Feb 2009 10:17:32 -0800
From: Greg KH <gregkh@...e.de>
To: Jesper Krogh <jesper@...gh.cc>
Cc: linux-kernel@...r.kernel.org,
Andrew Morton <akpm@...ux-foundation.org>,
torvalds@...ux-foundation.org, stable@...nel.org
Subject: Re: Linux 2.6.27.13
On Sun, Feb 01, 2009 at 02:21:13PM +0100, Jesper Krogh wrote:
> 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.
Does this also happen on older .27-stable releases? Or is it something
new to .13?
thanks,
greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists