From: Horms <horms@verge.net.au>
To: linux-ia64@vger.kernel.org, linux-serial@vger.kernel.org
Cc: Bjorn Helgaas <bjorn.helgaas@hp.com>,
Russell King <rmk+kernel@arm.linux.org.uk>
Subject: IA64: Broken Serial Console
Date: Fri, 02 Jun 2006 11:48:06 +0000 [thread overview]
Message-ID: <20060602114805.GA1462@verge.net.au> (raw)
In-Reply-To: <20060313040825.GA31703@verge.net.au>
Hi,
I have noticed that the serial console on my ia64 machine seems
to have broken since 2.6.16. Thanks to git bisect I have been
able to track this problem down to 111c9bf8c5cfa92363b3719c8956d29368b5b9de
[SERIAL] remove 8250_acpi (replaced by 8250_pnp and PNPACPI)
With the combination of PNPACPI and 8250_pnp, we no longer need
8250_acpi.
Signed-off-by: Bjorn Helgaas <bjorn.helgaas@hp.com>
Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
I haven't had time to look into the code and I have to leave
my desk shortly, so I thought I would post here to see if anyone
has any ideas.
I am boot using the following command line:
console=tty0 console=uart,io,0x2f8 console=ttyS0
Althogh I'm pretty sure I really only need:
console=uart,io,0x2f8
A failed boot looks like this:
io scheduler anticipatory registered (default)
Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing enabled
isa bounce pool size: 16 pages
RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
mice: PS/2 mouse device common for all mice
EFI Variables Facility v0.08 2004-May-17
No ttyS device at I/O port 0x2f8 for console
And a successful boot looks like this:
io scheduler anticipatory registered (default)
Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing enabled
acpi_serial_port: zero-length IO port range?
serial8250: ttyS0 at I/O 0x3f8 (irq = 44) is a 16550A
acpi_serial_port: zero-length IO port range?
serial8250: ttyS1 at I/O 0x2f8 (irq = 45) is a 16550A
isa bounce pool size: 16 pages
RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
mice: PS/2 mouse device common for all mice
EFI Variables Facility v0.08 2004-May-17
Adding console on ttyS1 at I/O port 0x2f8 (options '115200')
prompt #
The machine in question is a Trus64-21. Sorry I don't have an English
link handy, but if you need me to dig up details please ask.
http://www.plathome.co.jp/factory/ser/tru_ita64_21.html
--
Horms http://www.vergenet.net/~horms/
next prev parent reply other threads:[~2006-06-02 11:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-10 8:24 [RFC] IA64: Use early_parm to handle mvec_name and nomca Horms
2006-03-10 9:54 ` Jes Sorensen
2006-03-11 3:43 ` Horms
2006-03-11 8:51 ` Jes Sorensen
2006-03-11 20:17 ` Chen, Kenneth W
2006-03-13 4:08 ` Horms
2006-06-02 11:48 ` Horms [this message]
2006-06-02 11:53 ` IA64: Broken Serial Console Matthew Wilcox
2006-06-04 4:57 ` Horms
2006-06-02 11:59 ` Francois WELLENREITER
2006-03-13 6:33 ` [RFC] IA64: Use early_parm to handle mvec_name and nomca Chen, Kenneth W
2006-03-13 8:12 ` Horms
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=20060602114805.GA1462@verge.net.au \
--to=horms@verge.net.au \
--cc=bjorn.helgaas@hp.com \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=rmk+kernel@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