Date: Fri, 23 Jan 2004 01:11:58 -0800
From: Andrew Morton <akpm@osdl.org>
To: David Woodhouse <dwmw2@infradead.org>
Cc: glennpj@charter.net, linux-kernel@vger.kernel.org
Subject: Re: 2.6.2-rc1-mm1 oops with X
Message-Id: <20040123011158.665ad574.akpm@osdl.org>
In-Reply-To: <1074848612.23073.81.camel@imladris.demon.co.uk>
References: <20040123061927.GA7025@gforce.johnson.home>
	<20040122231814.149c8e8d.akpm@osdl.org>
	<1074848612.23073.81.camel@imladris.demon.co.uk>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 944
Lines: 23

David Woodhouse <dwmw2@infradead.org> wrote:
>
> On Thu, 2004-01-22 at 23:18 -0800, Andrew Morton wrote:
> > It is maddeningly hard to debug even when you can reproduce it, which I can
> > no longer do.
> 
> This is what GDB watchpoints were invented for, surely?
> 

I suppose that might help.  But for me the bug triggered towards the end of
initscripts (it moves around) after we've been through that code path a
zillion times.  It probably needs to be solved by inspection.  If one can
get it to happen reliably.

I found that sysfs-class-10-vc.patch caused it to happen and
use-kthread-primitives.patch made it go away again.  Neither patch has
anything to do with tty refcounting and locking.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/