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: "Jan Beulich" <jbeulich@xxxxxxxxxx>
Subject: Re: [Xen-devel] No console with xen-3.2
From: Stefan Berger <stefanb@xxxxxxxxxx>
Date: Tue, 13 Nov 2007 13:14:12 -0500
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 13 Nov 2007 10:15:38 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <4739EA51.76E4.0078.0@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

xen-devel-bounces@xxxxxxxxxxxxxxxxxxx wrote on 11/13/2007 12:17:53 PM:

> >>> Keir Fraser <Keir.Fraser@xxxxxxxxxxxx> 13.11.07 17:32 >>>
> >Changesets 16215, 16156, 16147 have to be suspected. Could one of you try
> >backing those out one by one (cumulatively, not individually) and see if Xen
> >springs back to life? My fear is that shifting the location of the boot
> >trampoline has screwed us on some boxes. But then again I have no reason to
> >think that 0x8c000 isn't a safe place to stick the trampoline...
>
> 16215 appears to be innocent - it's sufficiently isolated for reverting alone.
> The others I'll try tomorrow, unless Stefan beats me.


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?

   Stefan


>
> In any case - setting a video mode works, so the problem is likely on the
> return path from real mode.
>
> Jan
>
>
> _______________________________________________
> 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