From: Erland Lewin <erl@voxi.com>
To: Manfred Spraul <manfred@colorfullife.com>
Cc: linux-kernel@vger.kernel.org,
Ulrich Weigand <Ulrich.Weigand@de.ibm.com>,
Christian Robottom Reis <kiko@async.com.br>
Subject: Re: /proc/<pid>/stat read hang with Mozilla in 2.4.14
Date: Thu, 06 Dec 2001 19:05:45 +0100 [thread overview]
Message-ID: <3C0FB379.4675B275@voxi.com> (raw)
In-Reply-To: <3C0F510C.E535A9A8@voxi.com> <3C0F9A53.10508@colorfullife.com>
I wrote of hangs reading various /proc/<pid>/files after a Mozilla
crash.
Manfred Spraul replied:
>
> Could you check if mozilla was in the middle of a coredump? There is a
> deadlock in the coredump handler, perhaps mozilla triggered it.
> Could you search for a recent coredump file?
>
Yes, I found a matching core dump (core.8770).
Is there any other information I can help with?
What is the status of the deadlock problem - has it been fixed in the
latest kernel?
> Or check if PF_DUMPCORE is set in tsk->flags. (Probably difficult
> without access to /proc/n/stat)
/Erland
prev parent reply other threads:[~2001-12-06 16:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-06 11:05 /proc/<pid>/stat read hang with Mozilla in 2.4.14 Erland Lewin
[not found] ` <3C0F9A53.10508@colorfullife.com>
2001-12-06 18:05 ` Erland Lewin [this message]
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=3C0FB379.4675B275@voxi.com \
--to=erl@voxi.com \
--cc=Ulrich.Weigand@de.ibm.com \
--cc=kiko@async.com.br \
--cc=linux-kernel@vger.kernel.org \
--cc=manfred@colorfullife.com \
/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