[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <201006191432.04685.arnd@arndb.de>
Date: Sat, 19 Jun 2010 14:32:04 +0200
From: Arnd Bergmann <arnd@...db.de>
To: Tony Luck <tony.luck@...el.com>
Cc: Alan Cox <alan@...rguk.ukuu.org.uk>,
Frederic Weisbecker <fweisbec@...il.com>,
linux-kernel@...r.kernel.org, Greg KH <gregkh@...e.de>,
Thomas Gleixner <tglx@...utronix.de>,
Andrew Morton <akpm@...ux-foundation.org>,
John Kacur <jkacur@...hat.com>,
Al Viro <viro@...iv.linux.org.uk>, Ingo Molnar <mingo@...e.hu>
Subject: Re: [PATCH] tty: avoid recursive BTM in pty_close
On Friday 18 June 2010 22:25:22 Tony Luck wrote:
> On Fri, Jun 18, 2010 at 11:35 AM, Arnd Bergmann <arnd@...db.de> wrote:
> > Do you know if this was a problem with the original series or
> > something that got introduced by my last patch?
>
> Problem was there before. Looks like it was not in next-20100616
> but began with next-20100617.
Ok, so it's certainly in one of the patches from Alan or me.
> > Also, if you don't mind, could you try if the problem also exists
> > with CONFIG_TTY_MUTEX enabled?
> With CONFIG_TTY_MUTEX=y kernel with both your patches builds
> and boots with no unusual messages. Application output still gets
> garbled.
ok.
> > Which serial driver do you use?
> I boot with a "console=uart,io,0x3f8" argument, so I start out using
> 8250_early.c. Looks like it switched to 8250.c based on seeing
> this:
>
> Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
>
> on the console log.
Good, so it's something I should be able to reproduce on a PC.
Arnd
--
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