From: Dave Hansen <dave@sr71.net>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Dave Hansen <dave.hansen@intel.com>
Cc: One Thousand Gnomes <gnomes@lxorguk.ukuu.org.uk>,
Geert Uytterhoeven <geert+renesas@linux-m68k.org>,
LKML <linux-kernel@vger.kernel.org>,
linux-serial@vger.kernel.org, jslaby@suse.cz
Subject: Re: post 3.14 serial regression
Date: Wed, 09 Apr 2014 09:02:00 -0700 [thread overview]
Message-ID: <53456EF8.8060805@sr71.net> (raw)
In-Reply-To: <20140409003648.GB32273@kroah.com>
On 04/08/2014 05:36 PM, Greg Kroah-Hartman wrote:
>> > Looks like this just changed the detection order so my device went from
>> > ttyS2 to ttyS4:
>> >
>> > # cat /proc/tty/driver/serial
>> > serinfo:1.0 driver revision:
>> > 0: uart:16550A port:000003F8 irq:4 tx:0 rx:0 CTS|DSR|CD
>> > 1: uart:16550A port:000002F8 irq:3 tx:0 rx:0
>> > 2: uart:unknown port:000003E8 irq:4
>> > 3: uart:unknown port:000002E8 irq:3
>> > 4: uart:ST16650V2 port:00001008 irq:18 tx:0 rx:0
>> > 5: uart:ST16650V2 port:00001000 irq:19 tx:0 rx:0
> That's not good.
>
> Geert, any idea how to fix this? Or should I just revert your change to
> get back to the "working" behavior?
During some large bisects on previous kernels, I've noticed it make a
switch from ttyS2->ttyS4 before. In other words, this might have
restored some *old* behavior inadvertently.
The annoying thing is that these assignments *do* keep swapping around.
I don't really care whether or not we revert this, only that we pick
one order and stick with it.
next prev parent reply other threads:[~2014-04-09 16:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-08 0:23 post 3.14 serial regression Dave Hansen
2014-04-08 11:27 ` One Thousand Gnomes
2014-04-08 21:03 ` Dave Hansen
2014-04-08 21:38 ` Dave Hansen
2014-04-09 0:36 ` Greg Kroah-Hartman
2014-04-09 16:02 ` Dave Hansen [this message]
2014-04-09 19:41 ` Geert Uytterhoeven
2014-04-09 20:04 ` Dave Hansen
2014-04-09 20:59 ` Geert Uytterhoeven
2014-04-09 21:19 ` Dave Hansen
2014-04-10 11:14 ` One Thousand Gnomes
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=53456EF8.8060805@sr71.net \
--to=dave@sr71.net \
--cc=dave.hansen@intel.com \
--cc=geert+renesas@linux-m68k.org \
--cc=gnomes@lxorguk.ukuu.org.uk \
--cc=gregkh@linuxfoundation.org \
--cc=jslaby@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@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.