[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20161024214925.GA143272@stormcage.americas.sgi.com>
Date: Mon, 24 Oct 2016 16:49:25 -0500
From: Nathan Zimmer <nzimmer@....com>
To: Sean Young <sean@...s.org>
Cc: Nathan Zimmer <nzimmer@....com>, linux-kernel@...r.kernel.org,
linux-serial@...r.kernel.org, gregkh@...uxfoundation.org,
alan@...ux.intel.com
Subject: Re: console issue since 3.6, console=ttyS1 hangs
On Mon, Oct 24, 2016 at 02:52:35PM +0100, Sean Young wrote:
> 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@...2n0) (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
In going back and forth for builds I had become confused about the status of
CONFIG_PNP_DEBUG_MESSAGES.
Here is a better dmesg.
Nate
View attachment "dmegs_pnp_3.6.0" of type "text/plain" (92710 bytes)
Powered by blists - more mailing lists