From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Carl Holtje ;021;vcsg6;" Subject: Re: Breakage in -unstable for Transmeta Date: Thu, 23 Jun 2005 20:23:44 -0400 (EDT) Message-ID: References: <91682d35640728e6b4e763e88bbcb465@cl.cam.ac.uk> Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII 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 On Thu, 23 Jun 2005, Keir Fraser wrote: > > On 23 Jun 2005, at 21:45, Carl Holtje ;021;vcsg6; wrote: > > > Alright.. So where do you suggest I look to try solving this?.. I was > > setting waypoints in x86_32.S by printing a character and it seems to > > be > > that code that it broke at. Since those lines reference the page table > > stuff at the bottom, I'm not entirely sure where else to poke at.. > > > > I generated a diff between what I know works (on the Transmeta) and my > > most recent bk pull -- the changes seem to be more applicable to SMP > > than > > anything else... > > It's hard to believe that things are failing that early. If you put > your debugging code at the same point(s) in x86_32.S in a working > version of Xen, does that still work? (i.e., could it be your debugging > code at fault?) Yes, it still works.. like I mentioned, my code simply writes a character to the framebuffer.. different characters in different locations provide waypoints.. The only exception to 'it still works' is if I print waypoint characters before the multiboot check (because I was using that register).. everything else works fine.. Thanks! Carl - -- "There are 10 types of people in the world: Those who understand binary and those that don't."