From: Nathan Zimmer <nzimmer@sgi.com>
To: Peter Hurley <peter@hurleysoftware.com>
Cc: Nathan Zimmer <nzimmer@sgi.com>, Sean Young <sean@mess.org>,
Linux kernel mailing list <linux-kernel@vger.kernel.org>,
"linux-serial@vger.kernel.org" <linux-serial@vger.kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Alan Cox <alan@linux.intel.com>,
"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>
Subject: Re: console issue since 3.6, console=ttyS1 hangs
Date: Fri, 4 Nov 2016 16:33:48 -0500 [thread overview]
Message-ID: <20161104213348.GA30383@stormcage.americas.sgi.com> (raw)
In-Reply-To: <CAKU3ayVEsv0Qpk7AU9NwbAX5nOBkHVaj0SA2QnYFuHCQSWjv7A@mail.gmail.com>
On Thu, Nov 03, 2016 at 06:25:46PM -0600, Peter Hurley wrote:
> On Wed, Nov 2, 2016 at 9:29 AM, Nathan Zimmer <nzimmer@sgi.com> wrote:
> > On Mon, Oct 31, 2016 at 08:55:49PM -0600, Peter Hurley wrote:
> >> On Mon, Oct 31, 2016 at 2:27 PM, Sean Young <sean@mess.org> wrote:
> >> > 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.
> >>
> >> Hi Nathan,
> >>
> >> Couple of questions:
> >> 1. Was login over serial console setup and working on SLES 11? or was
> >> the 'console=ttyS1' only for debug output?
> >> I ask because console output doesn't use IRQs; iow, maybe the serial
> >> port w/ driver never actually worked.
> >> 2. Can you post dmesg for the SLES 11 setup? That would show if there
> >> were probe errors even on that.
> >>
> >> An alternative that should be equivalent to your previous setup is to
> >> build w/ CONFIG_SERIAL_8250_PNP=n
> >> Seems like your ACPI BIOS is buggy, but also that something else is using IRQ 3?
> >>
> >> Regards,
> >> Peter Hurley
> >
> >
> >
> > 1) Yes I can confirm I used it to login sometimes.
> >
> > I built with CONFIG_SERIAL_8250_PNP=n and that seemed to work better, in that the system did not hang.
> > However I couldn't login on the serial and got these error messages, I suspect I broke something while trying different permutations.
> >
> > gdm[5206]: WARNING: GdmDisplay: display lasted 0.136636 seconds
> > gdm[5206]: WARNING: GdmDisplay: display lasted 0.180955 seconds
> > gdm[5206]: WARNING: GdmDisplay: display lasted 0.161415 seconds
> > gdm[5206]: WARNING: GdmLocalDisplayFactory: maximum number of X display failures reached: check X server log for errors
> >
> > It did boot all the way though.
> >
> > 2) attached log
>
> So I'm confused where this leaves us.
>
> In your OP, you claim to have gotten it working with a partial revert
> of commit 835d844d1a28 (but you didn't attach the partial revert so no
> one knows what you did); however, my suggestion should have been
> equivalent.
I apologize, if I was unclear. Your suggestion of CONFIG_SERIAL_8250_PNP=n did successfully boot and provide messages
across the console, and yes is basically equivelent to the revert.
Those warnings I just noticed in the dmesg and they weren't there before.
>
> Note that you have the serial port disabled in BIOS; that's why you're
> getting the probe error for PNP.
>
> Regards,
> Peter Hurley
Now when you say its diabled in bios, how can I be sure and double check that?
These bios screens do not have any mention of PNP settings.
I am getting output over the console (via ipmi) until the boot hangs.
Nate
next prev parent reply other threads:[~2016-11-04 21:33 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-17 14:49 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-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 [this message]
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=20161104213348.GA30383@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@vger.kernel.org \
--cc=peter@hurleysoftware.com \
--cc=rafael.j.wysocki@intel.com \
--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
Powered by JetHome