From: Sean Young <sean@mess.org>
To: Nathan Zimmer <nzimmer@sgi.com>
Cc: linux-kernel@vger.kernel.org, linux-serial@vger.kernel.org,
gregkh@linuxfoundation.org, alan@linux.intel.com
Subject: Re: console issue since 3.6, console=ttyS1 hangs
Date: Mon, 24 Oct 2016 14:52:35 +0100 [thread overview]
Message-ID: <20161024135235.GA29984@gofer.mess.org> (raw)
In-Reply-To: <49f038af-5cb7-e76f-e4e9-57fad876710d@sgi.com>
On Fri, Oct 21, 2016 at 10:55:40AM -0500, Nathan Zimmer wrote:
> It didn't seem to make a difference as far as output.
> Did I miss a config option? or something else?
>
> [ 0.000000] Linux version 3.6.0 (root@r1i2n0) (gcc version 4.3.4
> [gcc-4_3-branch revision 152973] (SUSE Linux) ) #3 SMP Mon Oct 17 20:43:34
> EDT 2016
> [ 0.000000] Command line:
> root=/dev/disk/by-id/ata-WDC_WD5000BHTZ-04JCPV1_WD-WXA1E54KKR60-part2
> resume=/dev/disk/by-id/ata-WDC_WD5000BHTZ-04JCPV1_WD-WXA1E54KKR60-part1
> crashkernel=256M-:128M loglevel=8 pnp.debug=1
> ...
> [ 2.076084] Serial: 8250/16550 driver, 8 ports, IRQ sharing disabled
> [ 2.097001] serial8250: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
> [ 2.097844] serial 00:04: unable to assign resources
> [ 2.098303] serial: probe of 00:04 failed with error -16
Ehm is this kernel compiled with CONFIG_PNP_DEBUG_MESSAGES? Are you
getting any debug messages? You could try ignore_loglevel.
Sean
next prev parent reply other threads:[~2016-10-24 13:52 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 [this message]
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=20161024135235.GA29984@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 \
/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).