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: Stefan Berger <stefanb@xxxxxxxxxx>, Jan Beulich <jbeulich@xxxxxxxxxx>
Subject: Re: [Xen-devel] No console with xen-3.2
From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Date: Tue, 13 Nov 2007 18:21:12 +0000
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 13 Nov 2007 10:26:00 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <OFB5FAC91B.E96BE1BA-ON85257392.0063D90F-85257392.00642CD8@xxxxxxxxxx>
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
Thread-index: AcgmIfg0NooqFJIVEdytjwAX8io7RQ==
Thread-topic: [Xen-devel] No console with xen-3.2
User-agent: Microsoft-Entourage/11.3.6.070618
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.

 -- 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