Xen 
 
Home About Xen.org Xen Xen Summit Wiki Mailing List Bug Tracker Xen Downloads
 
   
 

xen-devel

Re: [Xen-devel] xm dmesg output

To: David F Barrera <dfbp@xxxxxxxxxx>
Subject: Re: [Xen-devel] xm dmesg output
From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Date: Tue, 29 Nov 2005 10:26:23 +0000
Cc: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Tue, 29 Nov 2005 10:21:10 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <1133212285.16113.3.camel@dyn95341161>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <1133212285.16113.3.camel@dyn95341161>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx

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.

 -- Keir


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

<Prev in Thread] Current Thread [Next in Thread>