[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20120508170442.409ccbe4@bob.linux.org.uk>
Date: Tue, 8 May 2012 17:04:42 +0100
From: Alan Cox <alan@...ux.intel.com>
To: Stephen Warren <swarren@...dotorg.org>
Cc: Alan Cox <alan@...rguk.ukuu.org.uk>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Arnd Bergmann <arnd@...db.de>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-tegra@...r.kernel.org" <linux-tegra@...r.kernel.org>
Subject: Re: Regression due to d29f3ef "tty_lock: Localise the lock"
On Tue, 08 May 2012 09:46:51 -0600
Stephen Warren <swarren@...dotorg.org> wrote:
> On 05/08/2012 03:35 AM, Alan Cox wrote:
> > On Mon, 07 May 2012 17:06:38 -0600
> > Stephen Warren <swarren@...dotorg.org> wrote:
> >
> >> Alan,
> >>
> >> Commit d29f3ef "tty_lock: Localise the lock" appears to cause a
> >> problem for me.
> >>
> >> With this commit (as in next-20120507), I can no longer log into my
> >> system (NVIDIA Tegra device with ARM CPU) over the serial console,
> >> since the login prompt no longer appears. If I wait a few minutes,
> >> I see the following console spew:
> >
> > Eep. If it's reproducable can you test whether adding the
> > unlock/relock in drivers/tty/pty.c does the trick ?
> >
> > ie:
> > tty_unlock(tty);
> > tty_vhangup(tty);
> > tty_lock(tty);
>
> Yes, that change in pty_close() solves the problem.
Ok Greg - I think we should go with putting that unlock back until we
understand exactly what is going on.
Alan
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists