From: Keith Owens <kaos@sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Out of order console initialization on HP CX2600
Date: Wed, 01 Dec 2004 11:02:35 +0000 [thread overview]
Message-ID: <7077.1101898955@ocs3.ocs.com.au> (raw)
This problem has been reported against the SLES9 SP1 Beta3 ia64 debug
kernel on HP CX2600. The ttySn ports are detected long after
console_init() has run, kdb detects no console and shuts down.
Why do the ttySn ports get detected after console_init() on HP?
Is there anything that can be done to detect ttySn before
console_init()? EARLY_PRINTK is not an option, the kernel is compiled
for CONFIG_IA64_GENERIC, which disables EARLY_PRINK.
<4>Kernel command line: BOOT_IMAGE=scsi1:\efi\SuSE\vmlinuz-2.6.5-7.118-debug root=/dev/sda4 console=ttyS1,9600n8 ro
<3>kdb: Initialization failed - no console. kdb is disabled.
<4>kdb version 4.4 by Keith Owens, Scott Lurndal. Copyright SGI, All Rights Reserved
<4>ttyS0 at MMIO 0xf4050000 (irq = 49) is a 16550A
<4>ttyS1 at MMIO 0xff5e0000 (irq = 59) is a 16550A
<4>ttyS2 at MMIO 0xff5e2000 (irq = 60) is a 16550A
<4>ttyS3 at MMIO 0xf4051000 (irq = 49) is a 16550A
Boot logging started on /dev/ttyS1(/dev/console) at Tue Nov 30 17:49:25 2004
/dev/ttyS0 at 0x0000 (irq = 49) is a 16550A
/dev/ttyS1 at 0x0000 (irq = 59) is a 16550A
/dev/ttyS2 at 0x0000 (irq = 60) is a 16550A
/dev/ttyS3 at 0x0000 (irq = 49) is a 16550A
Boot logging started on /dev/ttyS1(/dev/console) at Tue Nov 30 17:49:35 2004
next reply other threads:[~2004-12-01 11:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-01 11:02 Keith Owens [this message]
2004-12-01 17:57 ` Out of order console initialization on HP CX2600 Bjorn Helgaas
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=7077.1101898955@ocs3.ocs.com.au \
--to=kaos@sgi.com \
--cc=linux-ia64@vger.kernel.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