Re: 2.5.37 won't run X?

From: florin@iucha.net (Florin Iucha)
To: William Lee Irwin III <wli@holomorphy.com>,
	Andries Brouwer <aebr@win.tue.nl>,
	"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: Sun, 22 Sep 2002 23:56:17 -0500	[thread overview]
Message-ID: <20020923045617.GA726@iucha.net> (raw)
In-Reply-To: <20020922062702.GA652@iucha.net>

[-- Attachment #1: Type: text/plain, Size: 1968 bytes --]

On Sun, Sep 22, 2002 at 01:27:02AM -0500, Florin Iucha wrote:
> On Sat, Sep 21, 2002 at 09:30:50PM -0700, William Lee Irwin III wrote:
> > 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.
> 
> Weird. 2.5.38 works just fine but the head from few hours ago (which
> supposedly had the fix) doesn't. Oh well, it works fine now on both the
> desktop and the laptop.

I take that back. 2.5.38 works fine on the laptop. On the desktop the
situation is tricky:
   * I have compiled 2.5.38 under 2.5.34+xfs,
   * rebooted with 2.5.38 and
   * spent all day long in 2.5.38,
   * rebooted temporarily in Windows
   * then all boots into 2.5.38 resulted in a lock up.
The lockup happens with all kernels since 2.5.35 and it is random. It
happens in xdm waiting for login, in starting up KDE, in starting up
daemons at boot up.

Even when hanging in X, the Alt-SysRq still works to SUB.

2.5.34+xfs (from the SGI CVS) works fine. I will try a recent snapshot
from them, with a more recent kernel.

florin

-- 

"If it's not broken, let's fix it till it is."

41A9 2BDE 8E11 F1C5 87A6  03EE 34B3 E075 3B90 DFE4

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]