linux-kernel - Re: serial ports now asserting DTR and RTS during boot; breaks connected hardware

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Wed, 4 Jan 2012 16:37:53 -0600
From:	Chris Elmquist <chrise@...ox.com>
To:	Jiri Slaby <jslaby@...e.cz>
Cc:	Alan Cox <alan@...rguk.ukuu.org.uk>, Dave Jones <davej@...hat.com>,
	Linux Kernel <linux-kernel@...r.kernel.org>,
	Jiri Slaby <jirislaby@...il.com>
Subject: Re: serial ports now asserting DTR and RTS during boot; breaks
 connected hardware

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

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/