linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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: Tue, 25 Oct 2016 21:41:40 +0100	[thread overview]
Message-ID: <20161025204139.GA22268@gofer.mess.org> (raw)
In-Reply-To: <20161024214925.GA143272@stormcage.americas.sgi.com>

On Mon, Oct 24, 2016 at 04:49:25PM -0500, Nathan Zimmer wrote:
> [    0.974874] system 00:03: Plug and Play ACPI device, IDs PNP0c02 (active)
> [    0.975038] pnp 00:04: parse resource options
> [    0.975048] pnp 00:04:   dependent set 0 (acceptable) io  min 0x2f8 max 0x2f8 align 1 size 8 flags 0x1
> [    0.975056] pnp 00:04:   dependent set 0 (acceptable) irq 3 4 5 6 7 10 11 12 flags 0x1
> [    0.975060] pnp 00:04:   dependent set 0 (acceptable) dma <none> (bitmask 0x0) flags 0x0

So here the bios claims that the serial port can use any of 3 to 12 irqs.

> [    1.543636] Serial: 8250/16550 driver, 8 ports, IRQ sharing disabled

Why is this kernel compiled with irq sharing disabled?

> [    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?

We might be able to fix the problem with a pnp quirk but 3.7 is has not had
any releases for a long time. We will need a reproduction on a concurrent
kernel so a patch can be written for that.


Sean

  reply	other threads:[~2016-10-25 20:41 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 [this message]
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=20161025204139.GA22268@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).