From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Jan Beulich" Subject: Re: No console with xen-3.2 Date: Tue, 13 Nov 2007 17:17:53 +0000 Message-ID: <4739EA51.76E4.0078.0@novell.com> References: <4739DBA1.76E4.0078.0@novell.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: Content-Disposition: inline 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 , Stefan Berger Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org >>> Keir Fraser 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. In any case - setting a video mode works, so the problem is likely on the return path from real mode. Jan