WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] No console with xen-3.2

To: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Subject: Re: [Xen-devel] No console with xen-3.2
From: Stefan Berger <stefanb@xxxxxxxxxx>
Date: Tue, 13 Nov 2007 14:01:46 -0500
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, Jan Beulich <jbeulich@xxxxxxxxxx>, xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 13 Nov 2007 11:02:38 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <C35F9B98.185A9%Keir.Fraser@xxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx

xen-devel-bounces@xxxxxxxxxxxxxxxxxxx wrote on 11/13/2007 01:21:12 PM:

> Oh, you’re just doing ‘hg update <changeset>’? You could use binary
> chop in the range 16215-16300. :-) I’ll have a quick look and see if
> any changesets are very suspect in that range.... 16287,16266,16259,
> 16249. I think you’re best off doing a binary chop. It should only
> take you half a dozen tries.


On my machine 16259 causes the crash, 16258 still works.

   Stefan

>
>  -- Keir
>
> On 13/11/07 18:14, "Stefan Berger" <stefanb@xxxxxxxxxx> wrote:

> So I have tried the following versions and hope I did not do
> anything wrong on the way:
>
> 16146  works
> 16147  works
> 16156  works
> 16215  works
> 16300  does not work
>
> So, it would take me ld(85) more tries to hopefully find the CS that
> caused it. Any hints, though?

> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel