From mboxrd@z Thu Jan 1 00:00:00 1970 From: Zachary Amsden Subject: Re: Kernel panic while compiling kernel Date: Tue, 17 Feb 2004 17:49:00 -0800 Sender: xen-devel-admin@lists.sourceforge.net Message-ID: <4032C48C.8000602@cisco.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: Errors-To: xen-devel-admin@lists.sourceforge.net List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , List-Archive: To: Keir Fraser Cc: =?windows-1252?Q?=22Tvrtko_A=2E_Ur=9Aulin=22?= , xen-devel@lists.sourceforge.net List-Id: xen-devel@lists.xenproject.org Just an observation - I've noticed that several of the include files include linux/config.h and some include xeno/config.h - also for some other included files this is the case. Also, -nostdinc only seems to be applied to the arch/i386 branch - which means the drivers may be getting a different set of include paths. Perhaps some of your config settings are different in different .c files as a result with non-standard config options. Although I kind of doubt the problem is this simple, it seems reasonable to clean up the build tree so that it has a well isolated include structure. I think I just volunteered myself unless anyone else is already working on it. Zachary Amsden zamsden@cisco.com Keir Fraser wrote: >>>*BUT* take it as a reminder to list everything non-standard about your >>>build and environment when reporting a bug. >>> >>> >>Ok, I understand. >> >> >> >>>PS. Can you try building your own Xenolinux with all your config >>>changes _except_ the ones listed above? i.e. you should have >>>CONFIG_M686=y and CONFIG_X86_L1_CACHE_SHIFT=5. I expect that the >>>resulting kernel should not crash. >>> >>> >>It does crash. :) >> >> > >If you're sure that the CPU config options were set to the default, >and that you booted the correct kernel, then a useful thing to do is >the following: >Incrementally remove your config options (i.e. move towards the >default Xenolinux configuration) until your kernel image no longer >crashes. >Or alternatively: >Starting from teh default Xenolinux configuration, incrementally add >your desired extra config options until the resulting kernel image >starts to crash. > >In this way we can pinpoint which kernel config option is causing >Xenolinux to fail. > > -- Keir > > >------------------------------------------------------- >SF.Net is sponsored by: Speed Start Your Linux Apps Now. >Build and deploy apps & Web services for Linux with >a free DVD software kit from IBM. Click Now! >http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click >_______________________________________________ >Xen-devel mailing list >Xen-devel@lists.sourceforge.net >https://lists.sourceforge.net/lists/listinfo/xen-devel > > ------------------------------------------------------- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps & Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click