From: Nathan Zimmer <nzimmer@sgi.com>
To: Sean Young <sean@mess.org>
Cc: Nathan Zimmer <nzimmer@sgi.com>,
linux-kernel@vger.kernel.org, linux-serial@vgr.kernel.org,
gregkh@linuxfoundation.org, alan@linux.intel.com
Subject: Re: console issue since 3.6, console=ttyS1 hangs
Date: Mon, 17 Oct 2016 11:41:40 -0500 [thread overview]
Message-ID: <20161017164140.GA35950@stormcage.americas.sgi.com> (raw)
In-Reply-To: <20161017151906.GA19082@gofer.mess.org>
Ok I'll get that sometime tomorrow. Right now they pulled it down maintenance...
On Mon, Oct 17, 2016 at 04:19:07PM +0100, Sean Young wrote:
> On Mon, Oct 17, 2016 at 09:49:51AM -0500, Nathan Zimmer wrote:
> > A cluster client recently tried to update from Sles11 to Sles12 and found in
> > some cases the boxes would hang in early boot. It came down to console=ttyS1
> > on the command line. After a bisection I found it happended in here:
> >
> > commit 835d844d1a28efba81d5aca7385e24c29d3a6db2
> > Author: Sean Young <sean@mess.org>
> > Date: Fri Sep 7 19:06:23 2012 +0100
> >
> > 8250_pnp: do pnp probe before legacy probe
> >
> >
> > I found I can revert the part of the patch in 8250.c (now 8250_core.c) and
> > the hangs do not happen.
> >
> > Bios of the offending box ( I don't know if there a bios update )
> > Version 2.15.1234. Copyright (C) 2012 American Megatrends, Inc.
> > BIOS Date: 02/05/2014 13:45:09
> > Ver: ma2e2054.16I
> >
> > I don't have much more info but will collect anything that is asked.
> > Any help would be appeciated.
>
> The console output would be helpful (both before 3.6 and with 3.6). It
> could be that what the bios provides in pnp does not match the actual
> config.
>
> The output of:
>
> cat /sys/bus/pnp/drivers/serial/*/resources
>
> Would be helpful, thanks.
>
>
> Sean
next prev parent reply other threads:[~2016-10-17 16:41 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-17 14:49 console issue since 3.6, console=ttyS1 hangs Nathan Zimmer
2016-10-17 15:19 ` Sean Young
2016-10-17 16:41 ` Nathan Zimmer [this message]
2016-10-18 16:40 ` Nathan Zimmer
2016-10-18 18:05 ` Sean Young
2016-10-18 19:29 ` Nathan Zimmer
2016-10-19 9:07 ` Sean Young
2016-10-19 22:13 ` Nathan Zimmer
2016-10-20 20:10 ` Sean Young
2016-10-21 15:55 ` Nathan Zimmer
2016-10-24 13:52 ` Sean Young
2016-10-24 21:49 ` Nathan Zimmer
2016-10-25 20:41 ` Sean Young
2016-10-26 18:16 ` Nathan Zimmer
2016-10-27 20:19 ` Sean Young
2016-10-28 19:42 ` Nathan Zimmer
2016-10-29 21:16 ` Sean Young
2016-10-30 16:01 ` Nathan
2016-10-28 19:55 ` Nathan
2016-10-30 15:33 ` Nathan
2016-10-31 20:27 ` Sean Young
2016-11-01 2:55 ` Peter Hurley
2016-11-02 15:29 ` Nathan Zimmer
2016-11-04 0:25 ` Peter Hurley
2016-11-04 21:33 ` Nathan Zimmer
2016-11-04 22:18 ` Peter Hurley
2016-11-05 23:44 ` Maciej W. Rozycki
2016-11-07 15:40 ` Nathan Zimmer
2016-11-22 15:30 ` Nathan Zimmer
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=20161017164140.GA35950@stormcage.americas.sgi.com \
--to=nzimmer@sgi.com \
--cc=alan@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vgr.kernel.org \
--cc=sean@mess.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;
as well as URLs for NNTP newsgroup(s).