From: Russell King <rmk@arm.linux.org.uk>
To: Chuck Ebbert <76306.1226@compuserve.com>
Cc: Bernhard Kaindl <bernhard.kaindl@gmx.de>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Problem: strace -ff fails on 2.4.21-rc1
Date: Mon, 12 May 2003 09:20:21 +0100 [thread overview]
Message-ID: <20030512092020.A10073@flint.arm.linux.org.uk> (raw)
In-Reply-To: <200305112106_MC3-1-3868-D6B1@compuserve.com>; from 76306.1226@compuserve.com on Sun, May 11, 2003 at 09:03:12PM -0400
On Sun, May 11, 2003 at 09:03:12PM -0400, Chuck Ebbert wrote:
> Proc; minicom
> >>EIP; c01183a1 <schedule+351/3b0> <===== ignore this bogus address
> Trace; c0122f24 <schedule_timeout+14/a0>
> Trace; c0134a31 <__alloc_pages+41/170>
> Trace; c021195b <tty_wait_until_sent+9b/e0>
> Trace; c0220d79 <rs_close+129/1f0>
> Trace; c020d997 <release_dev+247/500>
> Trace; c011690d <do_page_fault+11d/43b>
> Trace; c020e01a <tty_release+2a/60>
> Trace; c013c52e <fput+4e/100>
> Trace; c013b1d5 <filp_close+95/a0>
> Trace; c013b23b <sys_close+5b/70>
> Trace; c0108b73 <system_call+33/38>
>
> It's hung up somewhere inside schedule().
Wait 30 seconds and see if it exits by itself. I bet you have hardware
RTS/CTS handshaking enabled on the serial port, but without anything
connected.
When a port is closed, we wait up to 30 seconds (or a user specified time
period) for any characters in the transmit queue to be sent. If CTS is
inactive and we're using RTS/CTS handshaking, we can't send any characters,
so we'll wait the full timeout.
--
Russell King (rmk@arm.linux.org.uk) The developer of ARM Linux
http://www.arm.linux.org.uk/personal/aboutme.html
next prev parent reply other threads:[~2003-05-12 8:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-12 1:03 Problem: strace -ff fails on 2.4.21-rc1 Chuck Ebbert
2003-05-12 8:20 ` Russell King [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-05-12 11:28 Chuck Ebbert
2003-05-11 15:37 Chuck Ebbert
2003-05-11 23:50 ` Bernhard Kaindl
2003-05-12 0:33 ` Daniel Jacobowitz
2003-05-09 9:11 Chuck Ebbert
2003-05-09 12:15 ` Carl-Daniel Hailfinger
2003-05-09 7:50 Chuck Ebbert
2003-05-07 14:08 Chuck Ebbert
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=20030512092020.A10073@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=76306.1226@compuserve.com \
--cc=bernhard.kaindl@gmx.de \
--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;
as well as URLs for NNTP newsgroup(s).