From: Jeremy Fitzhardinge Subject: Re: [Xen-devel] Re: [PATCH 00 of 36] x86/paravirt: groundwork for 64-bit Xen support Date: Fri, 27 Jun 2008 09:02:10 -0700 Message-ID: <48650F02.5080200@goop.org> References: <20080625084253.GA11524@elte.hu> <20080625152212.GA3442@elte.hu> <4862A6A9.1030109@goop.org> <20080626105722.GA12640@elte.hu> <20080626105818.GA13805@elte.hu> <4863A8E6.1010807@goop.org> <20080627155656.GA19180@elte.hu> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20080627155656.GA19180@elte.hu> Sender: linux-kernel-owner@vger.kernel.org To: Ingo Molnar Cc: Nick Piggin , Mark McLoughlin , xen-devel , Eduardo Habkost , Vegard Nossum , Stephen Tweedie , x86@kernel.org, LKML , Yinghai Lu List-Id: xen-devel@lists.xenproject.org Ingo Molnar wrote: > i'm testing on multiple systems in parallel, each is running randconfig > kernels. One 64-bit system found a build bug, the other one found a boot > crash. > > This can happen if certain configs build fine (but crash), certain > configs dont even build. Each system does a random walk of the config > space. > Yes, but the URL for both the crash and the build failure pointed to the same config. Is one of them a mistake? > I've applied your two fixes and i'm re-testing. > Thanks, J