All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Carl Holtje ;021;vcsg6;" <cwh0803@cs.rit.edu>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: xen-devel@lists.xensource.com
Subject: Re: Breakage in -unstable for Transmeta
Date: Thu, 23 Jun 2005 20:23:44 -0400 (EDT)	[thread overview]
Message-ID: <Pine.GSO.4.58.0506232019290.18321@moxie.cs.rit.edu> (raw)
In-Reply-To: <bd9c262c7aa8c86c6db4332f23614cc7@cl.cam.ac.uk>

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

  reply	other threads:[~2005-06-24  0:23 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-22 18:50 Breakage in -unstable for Transmeta Carl Holtje ;021;vcsg6;
2005-06-23 10:22 ` Keir Fraser
2005-06-23 20:45   ` Carl Holtje ;021;vcsg6;
2005-06-23 22:18     ` Keir Fraser
2005-06-24  0:23       ` Carl Holtje ;021;vcsg6; [this message]
2005-06-24  9:33         ` Keir Fraser
2005-06-24 13:30           ` Carl Holtje ;021;vcsg6;
2005-06-24 13:55             ` Keir Fraser
2005-06-24 15:57               ` Carl Holtje ;021;vcsg6;
2005-06-24 16:15                 ` Keir Fraser
2005-06-24 19:22                   ` Breakage in -unstable for Transmeta -- Solution Carl Holtje ;021;vcsg6;
2005-06-24 20:33                     ` Keir Fraser
2005-06-25  1:57                       ` Carl Holtje ;021;vcsg6;
2005-06-25  9:21                         ` Keir Fraser
2005-06-27 15:55                           ` Carl Holtje ;021;vcsg6;

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Pine.GSO.4.58.0506232019290.18321@moxie.cs.rit.edu \
    --to=cwh0803@cs.rit.edu \
    --cc=Keir.Fraser@cl.cam.ac.uk \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.