From mboxrd@z Thu Jan 1 00:00:00 1970 From: David F Barrera Subject: Re: xm dmesg output Date: Tue, 29 Nov 2005 16:15:58 -0600 Message-ID: <438CD31E.30001@us.ibm.com> References: <1133212285.16113.3.camel@dyn95341161> <520fab8eb58226fb4c917f1628d27477@cl.cam.ac.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <520fab8eb58226fb4c917f1628d27477@cl.cam.ac.uk> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Keir Fraser Cc: xen-devel List-Id: xen-devel@lists.xenproject.org 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