From: "karl malbrain" <karl@petzent.com>
To: <linux-kernel@vger.kernel.org>
Subject: 2.6.9: serial_core: uart_open
Date: Tue, 12 Jul 2005 11:36:51 -0700 [thread overview]
Message-ID: <02ad01c58710$ab9851c0$4b010059@petzent.com> (raw)
The uart_open code loops waiting for CD to be asserted (whenever CLOCAL
is not set). The bottom of the loop contains the following code:
up(&state->sem);
schedule();
down(&state->sem);
if( signal_pending(current) )
break;
When I issue an open("/dev/ttyS1", O_RDWR) from a terminal session on
the console, the system seems to come to a stop in this loop until the
process is killed. I suspect that the scheduler is choosing this process
to run again because of an elevated console priority of some sort.
Is there a kernel mechanism to put a process to sleep until awakened by
an event to replace this looping behaviour?
Thanks, karl malbrain, malbrain-at-yahoo-dot-com
next reply other threads:[~2005-07-12 18:37 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-12 18:36 karl malbrain [this message]
2005-07-12 21:03 ` 2.6.9: serial_core: uart_open Russell King
2005-07-12 21:17 ` karl malbrain
-- strict thread matches above, loose matches on Subject: below --
2005-07-12 19:27 karl malbrain
2005-07-12 20:32 karl malbrain
[not found] <Pine.LNX.4.61.0507130850110.18969@chaos.analogic.com>
2005-07-13 17:53 ` karl malbrain
2005-07-14 8:26 ` Russell King
2005-07-14 17:16 ` karl malbrain
2005-07-14 18:57 ` Russell King
2005-07-14 19:30 ` karl malbrain
2005-07-14 22:35 ` karl malbrain
2005-07-15 7:28 ` Russell King
2005-07-15 16:02 ` karl malbrain
2005-07-15 20:32 ` Russell King
2005-07-15 20:48 ` karl malbrain
2005-07-15 16:20 ` karl malbrain
[not found] <Pine.LNX.4.61.0507151150290.11664@chaos.analogic.com>
2005-07-15 16:57 ` karl malbrain
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='02ad01c58710$ab9851c0$4b010059@petzent.com' \
--to=karl@petzent.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