From: David F Barrera <dfbp@us.ibm.com>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: xen-devel <xen-devel@lists.xensource.com>
Subject: Re: xm dmesg output
Date: Tue, 29 Nov 2005 16:15:58 -0600 [thread overview]
Message-ID: <438CD31E.30001@us.ibm.com> (raw)
In-Reply-To: <520fab8eb58226fb4c917f1628d27477@cl.cam.ac.uk>
Keir Fraser wrote:
>
> On 28 Nov 2005, at 21:11, David F Barrera wrote:
>
>> I am seeing a series of messages in 'xm dmesg' on a couple of machines.
>> They look like informational messages, but I would like to ensure that
>> they are not problem diagnostics. Any ideas?
>
>
> Someone redirected serial input to Xen (CTRL-a three times) and then
> pressed 'r' over the serial line to dump scheduler information. That
> is the only way that info can get printed.
The interesting thing is that no one is doing anything to the serial
input! This is happening 'spontaneously' in my setup. Sounds like a bug?
>
> -- Keir
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>
--
Regards,
David F Barrera
Linux Technology Center
Systems and Technology Group, IBM
"The wisest men follow their own direction. "
Euripides
next prev parent reply other threads:[~2005-11-29 22:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-28 21:11 xm dmesg output David F Barrera
2005-11-29 10:26 ` Keir Fraser
2005-11-29 17:15 ` Adam Heath
2005-11-30 16:15 ` Anthony Liguori
2005-11-29 22:15 ` David F Barrera [this message]
2005-11-30 11:39 ` Keir Fraser
2005-12-01 17:49 ` David F Barrera
2005-12-01 18:37 ` Adam Heath
2005-12-01 19:04 ` David F Barrera
-- strict thread matches above, loose matches on Subject: below --
2005-11-29 17:58 Ian Pratt
2005-11-30 2:46 ` 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=438CD31E.30001@us.ibm.com \
--to=dfbp@us.ibm.com \
--cc=Keir.Fraser@cl.cam.ac.uk \
--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.