From: Manuel McLure <manuel@mclure.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Kernel hang on multi-threaded X process crash
Date: Mon, 23 Apr 2001 08:24:05 -0700 [thread overview]
Message-ID: <20010423082405.C979@ulthar.internal.mclure.org> (raw)
In-Reply-To: <20010422230014.A979@ulthar.internal.mclure.org> <E14rcnO-0007fb-00@the-village.bc.nu>
In-Reply-To: <E14rcnO-0007fb-00@the-village.bc.nu>; from alan@lxorguk.ukuu.org.uk on Mon, Apr 23, 2001 at 02:38:11 -0700
On 2001.04.23 02:38 Alan Cox wrote:
> Strange trace but it looks like a bug in the -ac experimental
> multithreaded
> core dump patches. I've got a couple of other reports consistent with
> them
> being broken somewhere
>
> Does it have to be something like mozilla (xmms also probably breaks it)
> that
> does this. If so I suspect its specific to multithreaded apps and its a
> bug
> in the core dump changes.
>
> If so I guess I revert them
Both mozilla and aviplay (which are both multithreaded) trigger this - I
haven't tried with xmms. Simpler programs like xclock or cat don't trigger
it.
To answer the question in your other email, I don't have DRI enabled (since
tdfx.o won't load for me due to rwsem fixes - see other thread).
Thanks for your help.
--
Manuel A. McLure KE6TAW | ...for in Ulthar, according to an ancient
<manuel@mclure.org> | and significant law, no man may kill a cat.
<http://www.mclure.org> | -- H.P. Lovecraft
next prev parent reply other threads:[~2001-04-23 15:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-23 1:55 Manuel McLure
2001-04-23 2:27 ` Manuel McLure
2001-04-23 3:17 ` Manuel McLure
2001-04-23 3:23 ` Manuel McLure
2001-04-23 4:28 ` idalton
2001-04-23 6:00 ` Manuel McLure
2001-04-23 9:38 ` Alan Cox
2001-04-23 15:24 ` Manuel McLure [this message]
2001-04-23 15:40 ` Alan Cox
2001-04-24 0:34 ` Don Dugger
2001-04-23 9:23 ` Alan Cox
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=20010423082405.C979@ulthar.internal.mclure.org \
--to=manuel@mclure.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®