From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeremy Fitzhardinge Subject: Re: problem using compiled kernel -- Sisu Date: Mon, 02 Aug 2010 08:37:03 -0700 Message-ID: <4C56E61F.2090205@goop.org> References: <20100728174900.GA23130@phenom.dumpdata.com> <4C521E3B.7060400@goop.org> <20100802144949.GC4227@phenom.dumpdata.com> <4C56E32D.4020009@goop.org> <20100802152934.GA9122@phenom.dumpdata.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20100802152934.GA9122@phenom.dumpdata.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Konrad Rzeszutek Wilk Cc: Sander Eikelenboom , "xen-devel@lists.xensource.com" , Keir Fraser , Sisu Xi List-Id: xen-devel@lists.xenproject.org On 08/02/2010 08:29 AM, Konrad Rzeszutek Wilk wrote: > On Mon, Aug 02, 2010 at 08:24:29AM -0700, Jeremy Fitzhardinge wrote: >> On 08/02/2010 07:49 AM, Konrad Rzeszutek Wilk wrote: >>> On Fri, Jul 30, 2010 at 04:20:06PM -0500, Sisu Xi wrote: >>>> Hi, all: >>>> >>>> Sorry to trouble you again. But I really tried very hard on installing >>>> xen on my machine. I reformatted my whole disk, install Ubuntu 10.04, >>>> and compile Xen and Kernel from the source code. >>> Ok.. why? Why didn't you just re-build? >>> >>>> it gives out info this time, saying something about >>>> BUG: scheduling while atomic: rsyslogd/565/0x10000001 >>>> kernel BUG at arch/x86/mm/highmem_32.c:45! >>> The .config that Pasi pointed has this: >>> >>> # CONFIG_HIGHPTE is not set >>> >>> That is what you need in your .config file. >> Why? That shouldn't be necessary, and is disabled at runtime even >> if you enable it. > Didn't we have some trouble with this? We had trouble with it being enabled; my recommendation has been to leave it off. But now we disable it at runtime by just not allocating ptes in high memory, so we don't need to deal with them any more. But I haven't looked at this specific BUG; what's the failure? J > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel >