mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Dave Jones <davej@redhat.com>
Cc: Jiri Slaby <jslaby@suse.cz>, Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: serial ports now asserting DTR and RTS during boot; breaks connected hardware
Date: Tue, 3 Jan 2012 16:06:55 +0000	[thread overview]
Message-ID: <20120103160655.69107c93@pyramind.ukuu.org.uk> (raw)
In-Reply-To: <20120103153707.GA12771@redhat.com>

On Tue, 3 Jan 2012 10:37:07 -0500
Dave Jones <davej@redhat.com> 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.

I think a necessary first step would be to test a current kernel on FC14,
or boot a sane simple kernel and test image and see what that does so all
the udev and system startup stuff can be eliminated. Wouldn't surprise me
at all however if something like udev triggered poking around for UPS
devices or 3G modems wasn't the trigger ?

Alan

  parent reply	other threads:[~2012-01-03 16:06 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-03 15:37 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 [this message]
2012-01-04 20:54   ` Jiri Slaby
2012-01-04 22:37     ` Chris Elmquist

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=20120103160655.69107c93@pyramind.ukuu.org.uk \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=davej@redhat.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 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®