From mboxrd@z Thu Jan 1 00:00:00 1970 From: Konrad Rzeszutek Wilk Subject: Re: Scrubbing free ram Date: Mon, 3 May 2010 13:38:46 -0400 Message-ID: <20100503173846.GA24574@phenom.dumpdata.com> References: <20100429144859.GA28499@phenom.dumpdata.com> <20100429162449.GN17817@reaktio.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <20100429162449.GN17817@reaktio.net> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?= Cc: Xen Devel , Bei Guan , Keir Fraser List-Id: xen-devel@lists.xenproject.org > > Was this kernel boot line the same as the previous kernel you used? > > Also, please consult the http://wiki.xensource.com/xenwiki/XenParavirtOps > > which Pasi refered to you earlier, and look in the "Are there more debugging > > options I could enable to troubleshoot booting problems?" > > > > I wonder if "earlyprintk=xen" for the pvops dom0 kernel would help here.. The 'debug' by itself makes Linux print by majority most of the warnings/errors/debugs. etc. So he should definitly use that. > And since you seem to be using a serial console make it "earlyprintk=xen console=hvc0"