All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Walrond <andrew@walrond.org>
To: Andrew Walrond <andrew@walrond.org>
Cc: Russell King <rmk@arm.linux.org.uk>, linux-kernel@vger.kernel.org
Subject: Re: 2.5.44 serial driver bug with asus pr-dls m/b
Date: Tue, 12 Nov 2002 12:52:23 +0000	[thread overview]
Message-ID: <3DD0F987.3050409@walrond.org> (raw)
In-Reply-To: 3DD0F03F.9000604@walrond.org

OK;

Previously described behavior is with remote console = ENABLED in the bios.
Changing to remote console = POST ONLY in the bios, (and disabling 2nd 
serial port which doesn't have a DB9 anyway) I get

Serial: 8250/16550 driver $Revision: 1.90 $ IRQ sharing disabled
ttyS0: autoconf (0x03f8, 0x00000000): iir=3 iir1=6 iir2=6 type=16550A
tts/0 at I/O 0x3f8 (irq = 4) is a 16550A
ttyS1: autoconf (0x02f8, 0x00000000): IER test failed (ff, ff) type=unknown
ttyS2: autoconf (0x03e8, 0x00000000): IER test failed (ff, ff) type=unknown
ttyS3: autoconf (0x02e8, 0x00000000): IER test failed (ff, ff) type=unknown

Which looks good to me. And I get some serial console output from the 
kernel as it boots, but only upto...

.
.
Serial: 8250/16550 driver $Revision: 1.90 $ IRQ sharing disabled
ttyS0: autoconf (0x03f8, 0x00000000): :^

...where the serial output hangs. I presume the serial driver does 
something to the hardware which breaks the serial console output. The 
kernel does however proceed and boot normally. I'm using the kernel 
parameters
    console=ttyS0,115200n8 console=tty0

Comments?

Andrew Walrond


  reply	other threads:[~2002-11-12 12:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-24 19:48 2.5.44 serial driver bug with asus pr-dls m/b Andrew Walrond
2002-10-24 19:58 ` Andrew Walrond
2002-11-03 13:58 ` Russell King
2002-11-06 21:30   ` Andrew Walrond
2002-11-12 11:43   ` Andrew Walrond
2002-11-12 12:12     ` Andrew Walrond
2002-11-12 12:52       ` Andrew Walrond [this message]
     [not found]         ` <3DD106FA.5060809@walrond.org>
2002-11-12 14:33           ` Russell King

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=3DD0F987.3050409@walrond.org \
    --to=andrew@walrond.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rmk@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.