From: n0ano@indstorage.com
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] lost printk's
Date: Tue, 16 Oct 2001 14:27:20 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590698805350@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590698805347@msgid-missing>
Nathan-
I've used a Rocketport serial concentrator with a BigSur quite
successfully. A single Rocketport PCI card can handle up to
32 ports. I've never had an issue with 115200 baud, I set up
EFI to automatically boot Linux so I don't need to worry about
running EFI over the serial line and then just tell Linux to
run the serial line at 9600.
On Tue, Oct 16, 2001 at 08:08:04AM -0500, Nathan Straz wrote:
> On Tue, Oct 16, 2001 at 04:47:26PM +1000, Keith Owens wrote:
> > If a crash kills the user space tasks or the disk I/O subsystem then
> > your printk does not get to disk. Use a serial console and capture the
> > output on a second machine, that goes printk() -> console drivers ->
> > serial line.
>
> Can anyone recommend a console server that works well with Itanium
> machines? The problem with most console servers (or inversely EFI) is
> that they don't run at 115200 baud. Is everyone just running a line to
> another PC? Is there a console server that can handle several of these
> machines?
> --
> Nate Straz nstraz@sgi.com
> sgi, inc http://www.sgi.com/
> Linux Test Project http://ltp.sf.net/
>
> _______________________________________________
> Linux-IA64 mailing list
> Linux-IA64@linuxia64.org
> http://lists.linuxia64.org/lists/listinfo/linux-ia64
--
Don Dugger
"Censeo Toto nos in Kansa esse decisse." - D. Gale
n0ano@indstorage.com
Ph: 303/652-0870x117
next prev parent reply other threads:[~2001-10-16 14:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-16 6:16 [Linux-ia64] lost printk's Christian Hildner
2001-10-16 6:47 ` Keith Owens
2001-10-16 13:08 ` Nathan Straz
2001-10-16 14:27 ` n0ano [this message]
2001-10-16 15:37 ` Randolph Chung
2001-10-16 15:44 ` Nathan Straz
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=marc-linux-ia64-105590698805350@msgid-missing \
--to=n0ano@indstorage.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