From: "Maciej W. Rozycki" <macro@linux-mips.org>
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: Sat, 5 Nov 2016 23:44:34 +0000 (GMT) [thread overview]
Message-ID: <alpine.LFD.2.20.1611052336380.17811@eddie.linux-mips.org> (raw)
In-Reply-To: <CAKU3ayWH9najj+Gpw8Zmpxgq40s8J_dXAyo9oBbbdG55brO6Sw@mail.gmail.com>
On Fri, 4 Nov 2016, Peter Hurley wrote:
> > These bios screens do not have any mention of PNP settings.
> > I am getting output over the console (via ipmi) until the boot hangs.
>
> Yeah, probably the device actually decodes io address access anyway,
> but in the disabled state probably has not routed IRQ.
>
> I have no idea how to help you with the bios, sorry.
I'd look out for serial port, Super-I/O or COM1 port (which is how PC-DOS
named the device some 35 years ago) settings rather than anything to do
with PNP. Typically you'd be able to choose from a few classic combined
I/O space address and IRQ assignments in addition to a `Disabled' setting.
There might be a genuine BIOS bug there as well of course as serial ports
seem to be less used these days and the issue may have escaped validation.
Maciej
next prev parent reply other threads:[~2016-11-05 23:44 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
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 [this message]
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=alpine.LFD.2.20.1611052336380.17811@eddie.linux-mips.org \
--to=macro@linux-mips.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=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;
as well as URLs for NNTP newsgroup(s).