public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: Russell King <rmk+lkml@arm.linux.org.uk>
Cc: Marc Haber <mh+linux-kernel@zugschlus.de>, linux-kernel@vger.kernel.org
Subject: Re: ttyS0 not working any more, LSR safety check engaged
Date: Sat, 11 Nov 2006 13:06:56 -0800	[thread overview]
Message-ID: <20061111130656.c9bae39f.akpm@osdl.org> (raw)
In-Reply-To: <20061111153005.GA28277@flint.arm.linux.org.uk>

On Sat, 11 Nov 2006 15:30:05 +0000
Russell King <rmk+lkml@arm.linux.org.uk> wrote:

> On Sat, Nov 11, 2006 at 01:34:55PM +0100, Marc Haber wrote:
> > On Sat, Nov 11, 2006 at 11:50:16AM +0000, Russell King wrote:
> > > Maybe something to do with PNP?  Maybe ACPI?  Both of those I know
> > > nothing about, but I suggest that if you have PNP enabled, you
> > > build and use the 8250_pnp module, even if your port is detected
> > > by the legacy detection methods in 8250.
> > 
> > How do I configure that?
> > 
> > I have:
> >   ? ?<*> 8250/16550 and compatible serial support                         ? ?
> >   ? ?[*]   Console on 8250/16550 and compatible serial port               ? ?
> >   ? ?<*>   8250/16550 PCI device support                                  ? ?
> >   ? ?<*>   8250/16550 PNP device support                                  ? ?
> 
> That's fine.
> 
> > $ grep -i 'nov 11.*\(8250\|serial\|ttyS\|pnp\)' /var/log/syslog/syslog
> > pnp: PnP ACPI init
> > pnp: PnP ACPI: found 15 devices
> > PnPBIOS: Disabled by ACPI PNP
> > pnp: 00:0d: ioport range 0x4d0-0x4d1 has been reserved
> > pnp: 00:0d: ioport range 0x1000-0x107f could not be reserved
> > pnp: 00:0d: ioport range 0x1100-0x113f has been reserved
> > pnp: 00:0d: ioport range 0x1200-0x121f has been reserved
> > isapnp: Scanning for PnP cards...
> > isapnp: No Plug & Play device found
> > Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing disabled
> > serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
> 
> ttyS0 detected via legacy ISA probes.
> 
> > serial8250: ttyS2 at I/O 0x3e8 (irq = 4) is a 16550A
> 
> ttyS2 detected via legacy ISA probes.
> 
> > 00:02: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
> 
> ttyS0 detected via PNP device 00:02.
> 
> > ttyS0: LSR safety check engaged!
> > ttyS2: LSR safety check engaged!
> 
> and then it mysteriously disappears on us.
> 
> It's certainly a mystery.  Suggest you git bisect to find the offending
> change - I doubt it'll be serial/8250 itself.

/proc/ioports and /proc/iomem might contain hints - can we see those please?

  reply	other threads:[~2006-11-11 21:07 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-11 11:43 ttyS0 not working any more, LSR safety check engaged Marc Haber
2006-11-11 11:50 ` Russell King
2006-11-11 12:34   ` Marc Haber
2006-11-11 15:30     ` Russell King
2006-11-11 21:06       ` Andrew Morton [this message]
2006-11-11 22:04         ` Russell King
2006-11-14 12:34         ` Marc Haber
2006-11-21 12:18 ` Marc Haber

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=20061111130656.c9bae39f.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mh+linux-kernel@zugschlus.de \
    --cc=rmk+lkml@arm.linux.org.uk \
    /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