From: Andreas Bombe <aeb@debian.org>
To: Greg KH <greg@kroah.com>
Cc: linux-kernel@vger.kernel.org, Alan Cox <alan@lxorguk.ukuu.org.uk>,
Arnd Bergmann <arnd@arndb.de>
Subject: Re: tty_lock held during transmit wait in close: still unresolved
Date: Fri, 27 May 2011 02:29:29 +0200 [thread overview]
Message-ID: <20110527002928.GA4369@amos.fritz.box> (raw)
In-Reply-To: <20110526071104.GE29833@kroah.com>
On Thu, May 26, 2011 at 12:11:04AM -0700, Greg KH wrote:
> On Thu, May 26, 2011 at 01:59:22AM +0200, Andreas Bombe wrote:
> > A minimalist way to trigger this issue is with a serial port that has
> > nothing attached:
> >
> > stty -F /dev/ttyS0 crtscts
> > echo >/dev/ttyS0
> >
> > The echo triggers a 30 second timeout on close while the driver is
> > trying to flush the newline. Another way is developing an USB device
> > with a virtual serial port and having it stop (by debugger or
> > crash/lockup)...
> >
> > Any ideas on how to progress?
>
> Can you try Linus's tree right now? A number of changes went in during
> this merge window that might help out here I think.
I think I had those changes already in the last try (Wednesday's git)
but I tried again with the very latest. No noticeable change.
--
Andreas Bombe
next prev parent reply other threads:[~2011-05-27 0:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-25 23:59 tty_lock held during transmit wait in close: still unresolved Andreas Bombe
2011-05-26 7:11 ` Greg KH
2011-05-27 0:29 ` Andreas Bombe [this message]
2011-05-26 8:17 ` Alan Cox
2011-05-27 0:41 ` Andreas Bombe
2011-05-27 11:38 ` Arnd Bergmann
2011-05-27 12:11 ` Jiri Slaby
2011-05-27 13:53 ` Arnd Bergmann
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=20110527002928.GA4369@amos.fritz.box \
--to=aeb@debian.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=arnd@arndb.de \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.