linux-serial.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Niklas Söderlund" <niklas.soderlund@ragnatech.se>
To: Rob Herring <robh@kernel.org>
Cc: Vinod Koul <vinod.koul@intel.com>,
	"open list:MEDIA DRIVERS FOR RENESAS - FCP"
	<linux-renesas-soc@vger.kernel.org>,
	"linux-serial@vger.kernel.org" <linux-serial@vger.kernel.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Peter Hurley <peter@hurleysoftware.com>
Subject: Re: Problem with 761ed4a (tty: serial_core: convert uart_close to use tty_port_close)
Date: Tue, 27 Sep 2016 19:16:33 +0200	[thread overview]
Message-ID: <20160927171633.GH16263@bigcity.dyn.berto.se> (raw)
In-Reply-To: <CAL_JsqKWjJ3Qo44=gjqLVJK6utUtrJF5nB=EVEE1wOmFpqw-+A@mail.gmail.com>

Hi Rob,

Thanks for your reply.

On 2016-09-27 10:57:56 -0500, Rob Herring wrote:
> On Tue, Sep 27, 2016 at 6:01 AM, Niklas Söderlund
> <niklas.soderlund@ragnatech.se> wrote:
> > Hi Rob and Vinod,
> >
> > While testing on Renesas Koelsch board Vinods 'next' branch at
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/vkoul/slave-dma.git
> >
> > I ran into some problems with Robs patch 761ed4a (tty: serial_core:
> > convert uart_close to use tty_port_close) and my systemd based init
> > system. The kernel starts fine, mounts the NFS root and starts init but
> > then the serial console go silent and I'm not able to communicate with
> > the system.
> 
> There's a fix later in Greg's tree that's not in this tree. If that
> doesn't fix it, can you try reverting the hunk that sets the
> tty_port.console flag.

I tried Greg's branch tty-next from 

git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty.git

Which contains the commit I think you are referring to, a5a2b13 (serial: 
core: fix potential NULL pointer dereference). Unfortunately it dose not 
fix the problem I see.

I also tried your other suggestion by reverting the chunk that sets the 
tty_port.console flag (on top of tty-next branch), like this:

@@ -2746,8 +2746,6 @@ int uart_add_one_port(struct uart_driver *drv, struct uart_port *uport)
        uport->cons = drv->cons;
        uport->minor = drv->tty_driver->minor_start + uport->line;
 
-       port->console = uart_console(uport);
-
        /*
         * If this port is a console, then the spinlock is already
         * initialised.

The problem still unfortunately persists :-(

I can still revert the commits a5a2b13 (serial: core: fix potential NULL 
pointer dereference) and 761ed4a (tty: serial_core: convert uart_close 
to use tty_port_close) from the top of the tty-next branch and the 
system boots fine.

The configuration I'm using for all tests are shmobile_defconfig + 
CONFIG_CGROUPS + CONFIG_SECCOMP. 

-- 
Regards,
Niklas Söderlund

      reply	other threads:[~2016-09-27 17:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-27 11:01 Problem with 761ed4a (tty: serial_core: convert uart_close to use tty_port_close) Niklas Söderlund
2016-09-27 15:57 ` Rob Herring
2016-09-27 17:16   ` Niklas Söderlund [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=20160927171633.GH16263@bigcity.dyn.berto.se \
    --to=niklas.soderlund@ragnatech.se \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=peter@hurleysoftware.com \
    --cc=robh@kernel.org \
    --cc=vinod.koul@intel.com \
    /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;
as well as URLs for NNTP newsgroup(s).