From mboxrd@z Thu Jan 1 00:00:00 1970 From: Matt Ayres Subject: Re: Kernel error with todays -unstable. Date: Fri, 22 Sep 2006 10:36:08 -0400 Message-ID: <4513F4D8.3080201@tektonic.net> References: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: 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@lists.xensource.com" List-Id: xen-devel@lists.xenproject.org Keir, Have you any update on this bug I would label as _CRITICAL_ seeing as the same hardware, config file, and 2.6.16.13 worked just fine. Even the newer hypervisor and 2.6.16.13 from previous -unstable tree boots fine. Thanks, Matt Keir Fraser wrote: > > > On 21/9/06 19:52, "Keir Fraser" wrote: > >>> Got this changing from 2.6.16.13 to 2.6.16.29.. running .13 under the >>> same xen binary works fine. >> Is the Xen binary built from a recent repository (i.e., which includes >> 2.6.16.29), or an older Xen version? It shouldn't matter, but if you run >> 2.6.16.29 okay with latest Xen but not with older Xen then it probably >> indicates a compatibility issue that we should look into. > > Ok, actually the logs you posted are sufficient to see that the Xen and > Linux are a 'matched pair'. So... Did you modify the Linux config at all? > > -- Keir > >