From: William Lee Irwin III <wli@holomorphy.com>
To: Andries Brouwer <aebr@win.tue.nl>
Cc: "Martin J. Bligh" <mbligh@aracnet.com>,
Helge Hafting <helgehaf@aitel.hist.no>,
linux-kernel@vger.kernel.org
Subject: Re: 2.5.37 won't run X?
Date: Sat, 21 Sep 2002 21:30:50 -0700 [thread overview]
Message-ID: <20020922043050.GU3530@holomorphy.com> (raw)
In-Reply-To: <20020921202353.GA15661@win.tue.nl>
On Sat, Sep 21, 2002 at 01:59:39PM -0500, Florin Iucha wrote:
>> X is not locked up, as it eats all the CPU. And 2.5.36 works just fine.
On Sat, Sep 21, 2002 at 10:23:53PM +0200, Andries Brouwer wrote:
> I noticed that the pgrp-related behaviour of some programs changed.
> Some programs hang, some programs loop. The hang occurs when they
> are stopped by SIGTTOU. The infinite loop occurs when they catch SIGTTOU
> (and the same signal is sent immediately again when they leave the
> signal routine).
> Have not yet investigated details.
Linus seems to have put out 2.5.38 with some X lockup fixes. Can you
still reproduce this? If so, are there non-X-related testcases where
you can trigger this? My T21 Thinkpad doesn't see this at all.
I'm still prodding the SIGTTOU path trying to trigger it until then.
Thanks,
Bill
next prev parent reply other threads:[~2002-09-22 4:32 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-21 10:10 2.5.37 won't run X? Helge Hafting
2002-09-21 13:41 ` Florin Iucha
2002-09-21 14:53 ` Martin J. Bligh
2002-09-21 16:17 ` Florin Iucha
2002-09-21 16:25 ` Martin J. Bligh
2002-09-21 18:59 ` Florin Iucha
2002-09-21 20:23 ` Andries Brouwer
2002-09-21 20:41 ` William Lee Irwin III
2002-09-22 4:30 ` William Lee Irwin III [this message]
2002-09-22 6:27 ` Florin Iucha
2002-09-23 4:56 ` Florin Iucha
2002-09-23 4:56 ` William Lee Irwin III
2002-09-22 12:18 ` Andries Brouwer
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=20020922043050.GU3530@holomorphy.com \
--to=wli@holomorphy.com \
--cc=aebr@win.tue.nl \
--cc=helgehaf@aitel.hist.no \
--cc=linux-kernel@vger.kernel.org \
--cc=mbligh@aracnet.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;
as well as URLs for NNTP newsgroup(s).