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: Wed, 19 Oct 2016 10:07:19 +0100	[thread overview]
Message-ID: <20161019090719.GA1764@gofer.mess.org> (raw)
In-Reply-To: <20161018192930.GA207959@stormcage.americas.sgi.com>

On Tue, Oct 18, 2016 at 02:29:30PM -0500, Nathan Zimmer wrote:
> On Tue, Oct 18, 2016 at 07:05:18PM +0100, Sean Young wrote:
> > On Tue, Oct 18, 2016 at 11:40:04AM -0500, Nathan Zimmer wrote:
> > > 3.7.0
> > > cat /sys/bus/pnp/drivers/serial/*/resources
> > > state = active
> > > io 0x2f8-0x2ff
> > > irq 12
> > > dma disabled
> > > 
> > > 3.6.0
> > > :~ # cat /sys/bus/pnp/drivers/serial/*/resources
> > > cat: /sys/bus/pnp/drivers/serial/*/resources: No such file or directory
> > 
> > irq 12 for ttyS1? That should be irq 3. The bios is putting bogus information
> > in pnp. Maybe there is rubbish in the bios setup or maybe it's fixed in a 
> > newer bios update.
> > 
> > So before this change, the kernel would assume irq 3. After this change,
> > the kernel first uses the information in pnp to see where the serial
> > port is. It gets told that it's irq 12 and presumably it runs into all
> > sorts of problems then. If memory serves that's the irq for the ps/2 mouse.
> > 
> > The interesting bit is in 3.6.0:
> > 
> > setserial
> > /dev/ttyS1, UART: 16550A, Port: 0x02f8, IRQ: 3
> > 
> > becomes in 3.7.0:
> > 
> > setserial
> > /dev/ttyS1, UART: 16550A, Port: 0x02f8, IRQ: 12
> > 
> > You should be able to set the right irq with setserial, but obviously
> > that doesn't help you if it fails in early boot. It's not immediately
> > obvious to me what can be done in the kernel for this. Maybe the dmesg
> > output could inspire, thanks.
> 
> Yea the changing irq seemed weird to me too but I couldn't manage a guess to why.
> 
> Here are the dmesgs.

So with 3.6.0:

> [    2.079980] Serial: 8250/16550 driver, 8 ports, IRQ sharing disabled
> [    2.100887] serial8250: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
> [    2.101715] serial 00:04: unable to assign resources
> [    2.102174] serial: probe of 00:04 failed with error -16

The pnp probe fails for some reason. I don't understand why.

With 3.7.0:

> [    2.062700] Serial: 8250/16550 driver, 8 ports, IRQ sharing disabled
> [    2.063250] serial 00:04: [io  0x02f8-0x02ff]
> [    2.063875] serial 00:04: [irq 12]
> [    2.064345] serial 00:04: [dma 18446744073709551615 disabled]
> [    2.065540] serial 00:04: activated
> [    2.086442] 00:04: ttyS1 at I/O 0x2f8 (irq = 12) is a 16550A

Now the pnp probe succeeds (with broken irq from pnp).

Can you please check if there is a wrong irq configured in the bios setup
or if there is a bios update available? I don't know why this worked in
the first place.


Sean

  reply	other threads:[~2016-10-19 15:03 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 [this message]
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
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=20161019090719.GA1764@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).