All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Hansen <dave@sr71.net>
To: Geert Uytterhoeven <geert+renesas@linux-m68k.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	LKML <linux-kernel@vger.kernel.org>,
	linux-serial@vger.kernel.org, jslaby@suse.cz
Subject: post 3.14 serial regression
Date: Mon, 07 Apr 2014 17:23:11 -0700	[thread overview]
Message-ID: <5343416F.8010201@sr71.net> (raw)

Hi Geert,

I have a piece of hardware where the two normal serial ports are
inaccessible and buried inside the system somewhere.  I put a PCIe
serial port card in which is normally detected as a ST16650V2:

[   17.939057] 0000:13:00.0: ttyS2 at I/O 0x1008 (irq = 18, base_baud =
115200) is a ST16650V2

I normally boot with both a console= and earlyprintk=.  Since the card
is at a non-standard I/O port, I have to use the I/O port directly in
the earlyprintk arguments instead of ttySXX:

	console=ttyS2,115200 earlyprintk=serial,0x1008,115200

However, after 3.14, commit 5f5c9ae56c3:

> commit 5f5c9ae56c38942623f69c3e6dc6ec78e4da2076
> Author: Geert Uytterhoeven <geert+renesas@linux-m68k.org>
> Date:   Fri Feb 28 14:21:32 2014 +0100
> 
>     serial_core: Unregister console in uart_remove_one_port()

the system to appears to hang at boot:

...
> [    0.000000] NR_IRQS:16640 nr_irqs:2728 16
> [    0.000000] Console: colour VGA+ 80x25
> [    0.000000] console [ttyS2] enabled
> [    0.000000] bootconsole [earlyser0] disabled

Here's a boot with earlyprintk=...,keep so that I can get *some* output:

	http://sr71.net/~dave/intel/pre-3.15-console-dead.txt

At the end, you can see that init is somehow dying.  If I revert this
patch, init is happy again and doesn't die, and the serial console works
like before.  Could init somehow be angry that its console is gone or
broken somehow?  Also, if I boot without console=ttyS2,115200, the
system boots happily.

Here's the .config:

	http://sr71.net/~dave/intel/pre-3.15-console-dead.config.txt

             reply	other threads:[~2014-04-08  0:23 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-08  0:23 Dave Hansen [this message]
2014-04-08 11:27 ` post 3.14 serial regression 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
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=5343416F.8010201@sr71.net \
    --to=dave@sr71.net \
    --cc=geert+renesas@linux-m68k.org \
    --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.