On 2011-08-09 17:51:42 -0500, Jonathan Nieder wrote:
> Makes sense. Vincent, could you run
>
> echo w >/proc/sysrq-trigger
>
> and find up what the kernel thinks that process is up to?
Unfortunately shortly after sending the bug report I had to switch off
the machine because I had to susp
On 2011-08-09 22:24:29 +0100, Ben Hutchings wrote:
> On Tue, Aug 09, 2011 at 06:15:13PM +0200, Jonathan Nieder wrote:
> > Vincent Lefevre wrote:
> > > In short: I've got a zombie process child of init. I suppose that's
> > > a kernel bug.
> >
> > Something's seriously weird there, but isn't this c
Ben Hutchings wrote:
>> Vincent Lefevre wrote:
>>> In short: I've got a zombie process child of init. I suppose that's
>>> a kernel bug.
[...]
> I suspect the process has hung somewhere along
> the exit path in the kernel, so that from userland it appears to have
> exited (Z state) but it hasn't y
On Tue, Aug 09, 2011 at 06:15:13PM +0200, Jonathan Nieder wrote:
> Vincent Lefevre wrote:
>
> > In short: I've got a zombie process child of init. I suppose that's
> > a kernel bug.
>
> Something's seriously weird there, but isn't this currently phrased as
> an init bug (i.e., "init" is not succe
Vincent Lefevre wrote:
> In short: I've got a zombie process child of init. I suppose that's
> a kernel bug.
Something's seriously weird there, but isn't this currently phrased as
an init bug (i.e., "init" is not successfully waiting on its child)?
[...]
> xvii:~> ps -ft pts/8
> UIDPID
Package: linux-2.6
Version: 3.0.0-1
Severity: normal
In short: I've got a zombie process child of init. I suppose that's
a kernel bug.
Here's what I did:
I've tried to run iceweasel under valgrind from zsh with:
valgrind --trace-children=yes --log-fd=3 3> vg.out iceweasel
then I quit the ice
6 matches
Mail list logo
