All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sean Young <sean@mess.org>
To: Nathan <nzimmer@sgi.com>
Cc: linux-kernel@vger.kernel.org, linux-serial@vger.kernel.org,
	gregkh@linuxfoundation.org, alan@linux.intel.com,
	"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>
Subject: Re: console issue since 3.6, console=ttyS1 hangs
Date: Mon, 31 Oct 2016 20:27:06 +0000	[thread overview]
Message-ID: <20161031202706.GA10263@gofer.mess.org> (raw)
In-Reply-To: <c73bc50a-51fb-78db-b872-277af3fb06bc@sgi.com>

On Sun, Oct 30, 2016 at 10:33:02AM -0500, Nathan wrote:
> I think this should be PNP0501 instead of PNP0c02.
> Once I alter that then when I boot the serial comes up on irq 3. However it
> still hangs.
> I'll keep digging.

Well that's that theory out of the window. I'm not sure where to look now,
I would start by enabling as many as possible of the "kernel hacking" config
options and see if anything gets caught.

Looking at your earlier messages, you have a collection of percpu allocation
failures. That might be worth resolving before anything else.


Sean

  reply	other threads:[~2016-10-31 20:27 UTC|newest]

Thread overview: 35+ 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
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-19 22:13               ` Nathan Zimmer
2016-10-20 20:10               ` Sean Young
2016-10-21 15:55                 ` Nathan Zimmer
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-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-30 16:01                                   ` Nathan
2016-10-28 19:55                             ` Nathan
2016-10-28 19:55                               ` Nathan
2016-10-30 15:33                             ` Nathan
2016-10-30 15:33                               ` Nathan
2016-10-31 20:27                               ` Sean Young [this message]
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=20161031202706.GA10263@gofer.mess.org \
    --to=sean@mess.org \
    --cc=alan@linux.intel.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=nzimmer@sgi.com \
    --cc=rafael.j.wysocki@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 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.