From: Jiri Slaby <jslaby@suse.cz>
To: Andreas Bombe <aeb@debian.org>
Cc: Jiri Slaby <jirislaby@gmail.com>,
gregkh@suse.de, linux-serial@vger.kernel.org,
linux-kernel@vger.kernel.org, Alan Cox <alan@linux.intel.com>,
Arnd Bergmann <arnd@arndb.de>
Subject: Re: [PATCH v2 1/6] TTY: serial, remove BTM from wait_until_sent
Date: Wed, 10 Aug 2011 11:46:44 +0200 [thread overview]
Message-ID: <4E425384.3040909@suse.cz> (raw)
In-Reply-To: <20110810010933.GA4733@amos.fritz.box>
On 08/10/2011 03:09 AM, Andreas Bombe wrote:
> On Mon, Aug 08, 2011 at 03:21:22PM +0200, Jiri Slaby wrote:
>> On 07/19/2011 02:35 AM, Andreas Bombe wrote:
>>> On Thu, Jul 14, 2011 at 02:35:10PM +0200, Jiri Slaby wrote:
>>>> This should also fix the issue Andreas is seeing (BTM in comparison to
>>>> BKL doesn't have any hidden functionality like unlocking during
>>>> sleeping).
>>>
>>> I tested the patch series and it does not appear to make a difference
>>> for the internal (16550A) serial ports on my system. Also, I am still
>>> unclear on why it freezes the X display during the timeout period.
>>
>> Sorry for the delay. Could you attach output of sysrq-t when this
>> happens? I mean with a kernel patched by my patch.
>
> I did my simple test on ttyS0 again: "stty -F /dev/ttyS0 crtscts" then
> "echo >/dev/ttyS0". I attached the gzipped sysrq-t list in case you need
> the complete output. This is just the process while it is trying to
> close the device (bash's internal echo):
>
> [ 321.948012] bash S ffff8800bcc85e80 0 4000 2828 0x00000000
> [ 321.948012] ffff880127079c38 0000000000000046 ffff880127079c50 0000000100002fff
> [ 321.948012] ffff880127079fd8 0000000000011fc0 ffff880127079fd8 0000000000011fc0
> [ 321.948012] ffff8801270dde80 ffff8800bcc85e80 ffff880127079c38 0000000100002fff
> [ 321.948012] Call Trace:
> [ 321.948012] [<ffffffff813cdf2e>] schedule_timeout+0xb5/0xf2
> [ 321.948012] [<ffffffff8104ae2b>] ? call_timer_fn+0x154/0x154
> [ 321.948012] [<ffffffff81255d60>] tty_wait_until_sent+0xa3/0xec
> [ 321.948012] [<ffffffff8105a190>] ? __init_waitqueue_head+0x46/0x46
> [ 321.948012] [<ffffffff81268c05>] uart_close+0x12b/0x243
> [ 321.948012] [<ffffffff81250454>] ? __tty_fasync+0x5c/0x124
> [ 321.948012] [<ffffffff81251a00>] tty_release+0x1d3/0x4d7
> [ 321.948012] [<ffffffff813cfbd8>] ? _raw_spin_unlock+0x43/0x51
> [ 321.948012] [<ffffffff8110db81>] ? dput+0xfe/0x11d
> [ 321.948012] [<ffffffff810fdc86>] __fput+0x107/0x1a2
> [ 321.948012] [<ffffffff810fdd36>] fput+0x15/0x17
> [ 321.948012] [<ffffffff810fb014>] filp_close+0x69/0x75
> [ 321.948012] [<ffffffff81109654>] sys_dup3+0x12b/0x153
> [ 321.948012] [<ffffffff811096d5>] sys_dup2+0x59/0x60
> [ 321.948012] [<ffffffff813d0a12>] system_call_fastpath+0x16/0x1b
>
>
> [ 321.948012] Sched Debug Version: v0.10, 3.1.0-rc1+ser-00011-g37ed45d #87
What tree is this? I cannot see the path through the code.
thanks,
--
js
suse labs
next prev parent reply other threads:[~2011-08-10 9:46 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-14 12:35 [PATCH v2 1/6] TTY: serial, remove BTM from wait_until_sent Jiri Slaby
2011-07-14 12:35 ` [PATCH v2 2/6] TTY: msm_serial, remove unneeded console set Jiri Slaby
2011-07-14 12:35 ` [PATCH v2 3/6] TTY: serial, remove tasklet for tty_wakeup Jiri Slaby
2011-07-19 16:34 ` Alan Cox
2011-08-31 14:43 ` Jiri Slaby
2011-07-14 12:35 ` [PATCH v2 4/6] TTY: ami_serial, remove BTM from wait_until_sent Jiri Slaby
2011-07-14 12:35 ` [PATCH v2 5/6] TTY: remove tty_locked Jiri Slaby
2011-07-19 16:35 ` Alan Cox
2011-07-14 12:35 ` [PATCH v2 6/6] TTY: mxser+cyclades remove wait_until_sent debug code Jiri Slaby
2011-07-14 13:24 ` [PATCH v2 1/6] TTY: serial, remove BTM from wait_until_sent Arnd Bergmann
2011-07-19 0:35 ` Andreas Bombe
2011-08-08 13:21 ` Jiri Slaby
2011-08-10 1:09 ` Andreas Bombe
2011-08-10 9:46 ` Jiri Slaby [this message]
2011-08-10 12:25 ` Andreas Bombe
2011-08-10 14:43 ` Jiri Slaby
2011-08-10 18:07 ` Andreas Bombe
2011-08-10 18:10 ` Jiri Slaby
2011-08-11 1:06 ` Andreas Bombe
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=4E425384.3040909@suse.cz \
--to=jslaby@suse.cz \
--cc=aeb@debian.org \
--cc=alan@linux.intel.com \
--cc=arnd@arndb.de \
--cc=gregkh@suse.de \
--cc=jirislaby@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@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