From: Jan Yenya Kasprzak <kas@fi.muni.cz>
To: Jiri Slaby <jirislaby@gmail.com>
Cc: linux-kernel@vger.kernel.org, osv@javad.com
Subject: Re: [RFC 1/1] Char: mxser_new, fix recursive locking
Date: Fri, 20 Apr 2007 17:02:57 +0200 [thread overview]
Message-ID: <20070420150257.GA5539@fi.muni.cz> (raw)
In-Reply-To: <4af2d03a0704140952w6e2338c4g3037f4ba03e2fb1d@mail.gmail.com>
Jiri Slaby wrote:
: On 4/14/07, Jan Yenya Kasprzak <kas@fi.muni.cz> wrote:
:
: > I have another problem with the driver - it probably sometimes
: >drops DCD signal on the serial line or something like that:
: >when the traffic on the serial console is heavy, it sometimes disconnects
: >me from the remote shell, and cu(1) displays the login prompt from the new
: >instance of mgetty of the remote machine. However, it does so both with
: >mxser.o and mxser_new.o (in 2.6.21-rc6, I think it worked in 2.6.19,
: >but I have to retest it). So this is another problem, different from
: >the one we are trying to solve now.
:
: There were some changes, however nothing significant in mxser.c, maybe
: some of tty or ldisc layer changes (but there is only termios ->
: ktermios switch + some other things), this would probably be hard to
: find without bisecting if 2.6.19 is really OK for you.
:
: The only idea I have right now is to nohup process, which will
: int fd = open("/dev/ttyMIXX", O_RDONLY | O_NONBLOCK);
: while (1) {
: ioctl(fd, TIOCMIWAIT, TIOCM_CD);
: ioctl(fd, TIOCMGET, &ret);
: printf("%ld: carrier has changed: %u\n", time(NULL), !!(ret & TIOCM_CD));
: }
: to prove, if the carrier really becomes low.
I ran the above code on both sides (on ttyMI0 of the server with
the MOXA card, and on ttyS0 of the server with the serial console).
I then logged in to the remote server using "cu -l ttyMI0 -s 38400",
and ran "find / -print" to generate some traffic. It went on without problems
for few minutes. But as soon as I pressed <enter> to the cu(1) (generating
traffic in the opposite direction), I was disconnected from the remote shell,
and the new mgetty has been started. The above program has reported
DCD change to 0 on both sides (in one direction it can be explained
by the fact that mgetty cycles DTR on startup, generating a DCD cycle
on the remote end of the null-modem connection).
-Yenya
--
| Jan "Yenya" Kasprzak <kas at {fi.muni.cz - work | yenya.net - private}> |
| GPG: ID 1024/D3498839 Fingerprint 0D99A7FB206605D7 8B35FCDE05B18A5E |
| http://www.fi.muni.cz/~kas/ Journal: http://www.fi.muni.cz/~kas/blog/ |
> I will never go to meetings again because I think face to face meetings <
> are the biggest waste of time you can ever have. --Linus Torvalds <
prev parent reply other threads:[~2007-04-20 15:03 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-14 4:27 MOXA: mxser_new lockup Jan Kasprzak
2007-04-14 6:51 ` Jiri Slaby
2007-04-14 10:25 ` Jan Kasprzak
2007-04-14 12:43 ` [RFC 1/1] Char: mxser_new, fix recursive locking, " Jiri Slaby
2007-04-14 14:37 ` [RFC 1/1] Char: mxser_new, fix recursive locking Jan Yenya Kasprzak
2007-04-14 16:52 ` Jiri Slaby
2007-04-14 19:55 ` Jan Yenya Kasprzak
2007-04-14 20:11 ` Jiri Slaby
2007-04-14 20:20 ` Jan Yenya Kasprzak
2007-04-14 20:23 ` Jiri Slaby
2007-04-14 20:24 ` Jan Yenya Kasprzak
2007-04-14 22:36 ` Jiri Slaby
2007-04-15 17:45 ` [RFC 1/1] Char: mxser_new, fix TIOCMIWAIT Jiri Slaby
2007-04-20 15:02 ` Jan Yenya Kasprzak [this message]
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=20070420150257.GA5539@fi.muni.cz \
--to=kas@fi.muni.cz \
--cc=jirislaby@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=osv@javad.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox