From: Michael Hanselmann <linux-kernel@hansmi.ch>
To: Russell King <rmk+lkml@arm.linux.org.uk>
Cc: linux-serial@vger.kernel.org
Subject: Re: Hang in uart_block_til_ready()
Date: Sun, 2 Apr 2006 17:17:39 +0200 [thread overview]
Message-ID: <20060402151739.GA402@hansmi.ch> (raw)
In-Reply-To: <20060402143827.GA3565@flint.arm.linux.org.uk>
[-- Attachment #1: Type: text/plain, Size: 1204 bytes --]
Hello Russell
On Sun, Apr 02, 2006 at 03:38:27PM +0100, Russell King wrote:
> On Sun, Apr 02, 2006 at 03:51:38PM +0200, Michael Hanselmann wrote:
> > I've discovered a problem where I'm not sure wether it's an error in the
> > kernel or in the hardware.
> It's neither - it's a bug in your test program. If you want "callout"
> semantics, open the port using O_NONBLOCK mode.
I've now patched screen(1) and it works, but one thing is amazing me.
The other computer I wrote about has the serial console on ttyS0 and
starting screen(1) on the serial console works. Here's the relevant
strace part:
screen-strace:open("/dev/ttyS0", O_RDWR|O_NONBLOCK) = 3
screen-strace.23801:open("/dev/ttyS0", O_RDWR) = 3
This doesn't work on the HP box with the serial console on ttyS2. After
adding O_NONBLOCK, it works. Here's the strace:
screen-strace:open("/dev/ttyS2", O_RDWR|O_NONBLOCK) = 3
screen-strace.31830:open("/dev/ttyS2", O_RDWR|O_NONBLOCK) = 3
Am I going correct that this is a bug in screen(1) and it only works on
the first box by some mysterious reason? Mabye some timing issue?
Thanks,
Michael
--
Gentoo Linux developer, http://hansmi.ch/, http://forkbomb.ch/
[-- Attachment #2: Type: application/pgp-signature, Size: 191 bytes --]
next prev parent reply other threads:[~2006-04-02 15:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-02 13:51 Hang in uart_block_til_ready() Michael Hanselmann
2006-04-02 14:38 ` Russell King
2006-04-02 15:17 ` Michael Hanselmann [this message]
2006-04-02 15:23 ` Russell King
2006-04-02 15:42 ` Michael Hanselmann
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=20060402151739.GA402@hansmi.ch \
--to=linux-kernel@hansmi.ch \
--cc=linux-serial@vger.kernel.org \
--cc=rmk+lkml@arm.linux.org.uk \
/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.