From: "Jiri Slaby" <jirislaby@gmail.com>
To: "Jan Yenya Kasprzak" <kas@fi.muni.cz>
Cc: linux-kernel@vger.kernel.org, osv@javad.com
Subject: Re: [RFC 1/1] Char: mxser_new, fix recursive locking
Date: Sat, 14 Apr 2007 18:52:01 +0200 [thread overview]
Message-ID: <4af2d03a0704140952w6e2338c4g3037f4ba03e2fb1d@mail.gmail.com> (raw)
In-Reply-To: <20070414143719.GA5203@fi.muni.cz>
On 4/14/07, Jan Yenya Kasprzak <kas@fi.muni.cz> wrote:
> Works for me, altough it spits tons of (bogus, in this case)
> warnings about possibly uninitialized variable "flags".
This is a gcc problem. I has been thinking about flags = 0
initialization, but developers dislike this shutting gcc up.
> Additionally, I think it is overzealous to wrap _all_
> spin_lock_irqsave/irqrestore() with if (!in_interrupt()). Some of them are
> never called from the interrupt context (mxser_block_till_ready(), for example
> - it can block, so if it is ever called from the interrupt context, we have
> a different, an order of magnitude worse problem here :-)
Yes, I had a patch, which changed only some of locks, but there were
only 2 or 3 spin_locks remaining. It's not a problem to test it
everywhere for little overhead, but maybe yes, I'll remove it from
open, close and block_til_whatever for the final patch.
> 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.
regards,
--
http://www.fi.muni.cz/~xslaby/ Jiri Slaby
faculty of informatics, masaryk university, brno, cz
e-mail: jirislaby gmail com, gpg pubkey fingerprint:
B674 9967 0407 CE62 ACC8 22A0 32CC 55C3 39D4 7A7E
next prev parent reply other threads:[~2007-04-14 16:52 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 [this message]
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 ` [RFC 1/1] Char: mxser_new, fix recursive locking Jan Yenya Kasprzak
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=4af2d03a0704140952w6e2338c4g3037f4ba03e2fb1d@mail.gmail.com \
--to=jirislaby@gmail.com \
--cc=kas@fi.muni.cz \
--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
all inboxes | Powered by JetHome®