From: Chris Elmquist <chrise@pobox.com>
To: Jiri Slaby <jslaby@suse.cz>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Dave Jones <davej@redhat.com>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Jiri Slaby <jirislaby@gmail.com>
Subject: Re: serial ports now asserting DTR and RTS during boot; breaks connected hardware
Date: Wed, 4 Jan 2012 16:37:53 -0600 [thread overview]
Message-ID: <20120104223752.GA1149@n0jcf.net> (raw)
In-Reply-To: <4F04BC85.9060803@suse.cz>
On Wednesday (01/04/2012 at 09:54PM +0100), Jiri Slaby wrote:
> >> Jiri,
> >> We got this report from a user who notes a change in behaviour for
> >> his serial hardware over the last few kernel versions.
> >>
> >> https://bugzilla.redhat.com/show_bug.cgi?id=771010
> >>
> >> This sounds like it might be related to your DTR/RTS changes back in March 2011 maybe ?
> >
> > Looks like your userspace to me at first glance.
> >
> > ftdi_sio sets up the modem lines in set_termios. Set_termios is called
> > from ftdi_open. ftdi_open is triggered by userspace.
> >
> >> > The following code in the ftdi_sio driver is one suspect but this behavior
> >> > happens on 8250 UARTs also so it is systemic now,
> >
> > Likewise 8250 sets up the lines in serial8250_startup. This is called via
> > uart_startup which is called via open.
>
> Ok, let's apply the cut&paste rule. Does uninstalling ModemManager fix
> the issue?
I'm going with 'cut' :-)
Indeed, removing ModemManager fixes the issue. I removed it, rebooted,
and on an 8250 UART port, I never saw DTR or RTS assert during boot.
I'm not currently able to verify on an FTDI interface as I had a hardware
failure that has taken it offline (this is the actual radio interface that
was originally affected) but I will verify that soon once the hardware is
back online.
Note that if you 'yum remove' ModemManager it wants to take NetworkManager
out with it due to dependancy... which doesn't seem cool. I removed it
with 'rpm' and --nodeps. Probably better to disable it the correct way
which I am still learning due to the systemd/chkconfig changeover which has
slowed me down a bit.
Thanks guys. I think this will resolve the issue for me once I verify on
FTDI hardware.
Chris
--
Chris Elmquist
prev parent reply other threads:[~2012-01-04 22:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-03 15:37 serial ports now asserting DTR and RTS during boot; breaks connected hardware Dave Jones
2012-01-03 16:00 ` Jiri Slaby
2012-01-03 16:13 ` Dave Jones
2012-01-04 18:43 ` Jiri Slaby
2012-01-03 16:06 ` Alan Cox
2012-01-04 20:54 ` Jiri Slaby
2012-01-04 22:37 ` Chris Elmquist [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=20120104223752.GA1149@n0jcf.net \
--to=chrise@pobox.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=davej@redhat.com \
--cc=jirislaby@gmail.com \
--cc=jslaby@suse.cz \
--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 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.