From: Russell King <rmk@arm.linux.org.uk>
To: Andrew Morton <akpm@zip.com.au>
Cc: William Lee Irwin III <wli@holomorphy.com>, linux-kernel@vger.kernel.org
Subject: Re: [BUG] mysterious tty deadlock
Date: Thu, 29 Aug 2002 01:20:48 +0100 [thread overview]
Message-ID: <20020829012048.B28773@flint.arm.linux.org.uk> (raw)
In-Reply-To: <3D6D6558.B2CE77B6@zip.com.au>; from akpm@zip.com.au on Wed, Aug 28, 2002 at 05:05:44PM -0700
On Wed, Aug 28, 2002 at 05:05:44PM -0700, Andrew Morton wrote:
> Well Bill's trace is claiming that we're doing a schedule_timeout(0x7fffffff)
> for some reason.
Umm, I didn't see that:
wli> #0 schedule_timeout (timeout=-150765944) at timer.c:864
wli> #1 0xc01a28a3 in uart_wait_until_sent (tty=0xf7669000, timeout=2147483647)
wli> at core.c:1320
Its legal for uart_wait_until_sent to be called with 2147483647 (it means
"wait until all characters are sent no matter what"). However, we'll
still call schedule_timeout with a really small value (one character
time) which means we'll be waking up pretty regularly there.
> But yes, he seems to be able to hit it too frequently for this to be
> the cause.
wli - please let me know if Andrew's patch makes any difference for you.
--
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:[~2002-08-29 0:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-28 22:01 [BUG] mysterious tty deadlock William Lee Irwin III
2002-08-28 22:25 ` Andrew Morton
2002-08-28 23:21 ` Russell King
2002-08-29 0:05 ` Andrew Morton
2002-08-29 0:20 ` Russell King [this message]
2002-09-01 2:42 ` William Lee Irwin III
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=20020829012048.B28773@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=akpm@zip.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=wli@holomorphy.com \
/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.