From: Andy Smith <andy@strugglers.net>
To: xen-devel@lists.xensource.com
Subject: Re: Losing serial console boot output / sync_console
Date: Sat, 2 Jul 2011 23:40:07 +0000 [thread overview]
Message-ID: <20110702234007.GJ5935@bitfolk.com> (raw)
In-Reply-To: <CA3564E8.1D643%keir.xen@gmail.com>
Hi Keir,
On Sun, Jul 03, 2011 at 12:14:32AM +0100, Keir Fraser wrote:
> On 02/07/2011 21:04, "Andy Smith" <andy@strugglers.net> wrote:
> > About two months ago I sent this email to the Xen users lists
> > regarding a problem I was having losing some of my serial console
> > output on boot:
> >
> > http://lists.xensource.com/archives/html/xen-users/2011-04/msg00340.html
>
> If your serial line is very slow (I don't know why you're limited to 9600
> baud -- 115200 baud at least is usually possible) and there is a lot of boot
> output then you can expect some of it to be discarded. We prefer to discard
> data rather than spin-wait to send it as that can indeed cause other
> time-critical services to be delayed too long.
Fair enough. I'm not really concerned about things being slow during
boot, more if sync_console would introduce strange latencies during
normal operation even without excessive ongoing console output.
Unfortunately I have no control over the terminal server
configuration in this instance otherwise I'd certainly be using a
higher baud rate. Having never had this problem with earlier
versions of Xen or anything else I thought I better ask.
> If you want to capture all Xen's boot output, the safest way is to increase
> the serial transmit buffer size. Try adding serial_tx_buffer=64k to the Xen
> command line.
Thanks, I'll try that.
Cheers,
Andy
prev parent reply other threads:[~2011-07-02 23:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-02 20:04 Losing serial console boot output / sync_console Andy Smith
2011-07-02 23:14 ` Keir Fraser
2011-07-02 23:40 ` Andy Smith [this message]
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=20110702234007.GJ5935@bitfolk.com \
--to=andy@strugglers.net \
--cc=xen-devel@lists.xensource.com \
/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.