From: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
To: linux-kernel@vger.kernel.org, Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: tty related hangs with 2.6.31-rc3
Date: Wed, 15 Jul 2009 19:32:12 +0530 [thread overview]
Message-ID: <20090715140212.GA11734@skywalker> (raw)
In-Reply-To: <20090715132956.GA10004@skywalker>
On Wed, Jul 15, 2009 at 06:59:56PM +0530, Aneesh Kumar K.V wrote:
> Hi,
>
> I am finding tty related hangs with 2.6.31-rc3. This didn't happen
> before. This happen when i close the emacs session. The /proc/<pid>/stack
> content is below
>
> [<c0362c5b>] process_echoes+0x2b/0x2e0
> [<c03638cb>] n_tty_write_wakeup+0xb/0x40
> [<c0360a88>] tty_wakeup+0x58/0x70
> [<c0368347>] pty_write+0x67/0x70
> [<c035f1cb>] tty_put_char+0x2b/0x40
> [<c036291f>] do_output_char+0xef/0x200
> [<c0362d4e>] process_echoes+0x11e/0x2e0
> [<c0364292>] n_tty_receive_char+0x102/0x710
> [<c0364ac0>] n_tty_receive_buf+0x220/0x410
> [<c036059c>] tiocsti+0x8c/0xa0
> [<c0361aca>] tty_ioctl+0x25a/0x310
> [<c01e52c8>] vfs_ioctl+0x28/0x80
> [<c01e54f4>] do_vfs_ioctl+0x64/0x1c0
> [<c01e56a3>] sys_ioctl+0x53/0x70
> [<c0102e3c>] sysenter_do_call+0x12/0x28
> [<ffffffff>] 0xffffffff
>
Another hang
[<c0362c5b>] process_echoes+0x2b/0x2e0
[<c03639ff>] n_tty_write+0x6f/0x2b0
[<c0361cb2>] tty_write+0x132/0x1e0
[<c01d8966>] vfs_write+0x96/0x190
[<c01d8b1d>] sys_write+0x3d/0x70
[<c0102e3c>] sysenter_do_call+0x12/0x28
[<ffffffff>] 0xffffffff
-aneesh
next prev parent reply other threads:[~2009-07-15 14:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-15 13:29 tty related hangs with 2.6.31-rc3 Aneesh Kumar K.V
2009-07-15 14:02 ` Aneesh Kumar K.V [this message]
2009-07-15 15:11 ` Alan Cox
2009-07-15 16:53 ` Aneesh Kumar K.V
[not found] ` <20090715204902.GA4205@skywalker>
2009-07-16 17:57 ` Aneesh Kumar K.V
2009-07-17 11:06 ` Takashi Iwai
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=20090715140212.GA11734@skywalker \
--to=aneesh.kumar@linux.vnet.ibm.com \
--cc=alan@lxorguk.ukuu.org.uk \
--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