From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Sasha Levin <levinsasha928@gmail.com>
Cc: gregkh <gregkh@linuxfoundation.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Dave Jones <davej@redhat.com>
Subject: Re: New tty ldisc lockup on 3.5-rc3
Date: Fri, 22 Jun 2012 15:42:19 +0100 [thread overview]
Message-ID: <20120622154219.779965bb@pyramind.ukuu.org.uk> (raw)
In-Reply-To: <1340373489.27031.40.camel@lappy>
> [ 242.702289] [<ffffffff83696d15>] schedule+0x55/0x60
> [ 242.702921] [<ffffffff81b2a026>] tty_ldisc_ref_wait+0x76/0xa0
> [ 242.703685] [<ffffffff81b22624>] ? redirected_tty_write+0x84/0xc0
These are all what I'd expect - the tty write is waiting to get access to
the ldisc
> [ 242.735143] [<ffffffff81107d52>] ? prepare_to_wait+0x72/0x80
> [ 242.737060] [<ffffffff81b29c50>] tty_ldisc_wait_idle+0x80/0xd0
And the hangup is waiting for the line discipline to idle so it can
complete a hangup triggered by vhangup in its syscall path. All seems
sane so far. The ldisc code is behaving as I'd expect, you may also have
a printk indicating who was waiting too long as we will log that, loop
and retry if it fails in wait fo idle for too long
The real question is "who has the reference" and none of your threads
show anyone who does. That would suggest you are looking for something
like a faulty error handling path in a driver or a buggy ldisc.
What ldisc is attached to the line when it fails ?
Alan
prev parent reply other threads:[~2012-06-22 14:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-22 13:58 Sasha Levin
2012-06-22 14:42 ` Alan Cox [this message]
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=20120622154219.779965bb@pyramind.ukuu.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=davej@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=levinsasha928@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®