linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nathan <nzimmer@sgi.com>
To: Sean Young <sean@mess.org>
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: Sun, 30 Oct 2016 11:01:39 -0500	[thread overview]
Message-ID: <532703ec-357f-24a9-cd0e-268d0430e194@sgi.com> (raw)
In-Reply-To: <20161029211647.GA25740@gofer.mess.org>



On 10/29/2016 04:16 PM, Sean Young wrote:
> On Fri, Oct 28, 2016 at 02:42:25PM -0500, Nathan Zimmer wrote:
>> On Thu, Oct 27, 2016 at 09:19:16PM +0100, Sean Young wrote:
>>> On Wed, Oct 26, 2016 at 01:16:16PM -0500, Nathan Zimmer wrote:
>>>> On 10/25/2016 03:41 PM, Sean Young wrote:
>>>>> On Mon, Oct 24, 2016 at 04:49:25PM -0500, Nathan Zimmer wrote:
>>>>>> [    1.565062] serial8250: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
>>>>> The isa probe driver find the serial port.
>>>>>
>>>>>> [    1.566453] serial 00:04: pnp_assign_resources, try dependent set 0
>>>>>> [    1.567383] serial 00:04:   couldn't assign io 0 (min 0x2f8 max 0x2f8)
>>>>> But then decides that the port is already in use (the existing serial driver).
>>>>>> [    1.568366] serial 00:04: pnp_assign_resources failed (-16)
>>>>>> [    1.569188] serial 00:04: unable to assign resources
>>>>>> [    1.569924] serial: probe of 00:04 failed with error -16
>>>>> Please try and boot 3.7.0 with "8250.share_irqs=1", maybe it will pick
>>>>> irq 3 and it will be happy again, but that is just a guess.
>>>>>
>>>>> I think I have not fully understood what the failure is. Does the serial
>>>>> port not work or does the boot hang? What are the symptoms?
>>>> With console=ttyS1 the boot will "hang", sometimes it makes it all the way
>>>> through but may take 30 minutes, instead of the 2-4 minutes this box
>>> Where does it hang? Any error messages?
>>>
>> Shortly after mounting the root.
>> After that I get no more output...
>>
>> Here is a failure log from 4.8.
> So does the console on the serial port work on 4.8? Also what does
> "cat /proc/interrupts" say with and without my change of ordering the
> serial pnp probe before the isa probe?
>
> It could be that the serial driver picking a different irq caused another
> driver to be forced to pick another irq which does not work.
>
>
> Sean

Works is a strong word.  It produces output until it hangs in boot.

It certainly could be another driver but I don't see another irq12 in 
the dmesg log.

I'll grab some data once I back in the office tomorrow.


Nate

  reply	other threads:[~2016-10-30 16:01 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 [this message]
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=532703ec-357f-24a9-cd0e-268d0430e194@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=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).