qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Blue Swirl" <blauwirbel@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] qemu/target-sparc exec.h op.c op_helper.c op_me...
Date: Sat, 22 Sep 2007 15:07:55 +0300	[thread overview]
Message-ID: <f43fc5580709220507k33d962c2o4294babe93fbacd8@mail.gmail.com> (raw)
In-Reply-To: <20070922114954.GA12622@hall.aurel32.net>

On 9/22/07, Aurelien Jarno <aurelien@aurel32.net> wrote:
> On Fri, Sep 21, 2007 at 11:20:26PM +0200, Andreas Färber wrote:
> > Am 21.09.2007 um 23:07 schrieb Aurelien Jarno:
> >
> > >Aurelien Jarno a écrit :
> > >>On Fri, Sep 21, 2007 at 09:32:00PM +0200, Andreas Färber wrote:
> > >>>These changes appear to have broken sparc32-softmmu on OS X v10.4
> > >>>ppc: The OpenBIOS screen no longer appears.
> > >>>
> > >>
> > >>Could you try to see if qemu.log contains useful debug information
> > >>while
> > >>running in debug mode?
> > >>
> > >>I am currently building qemu-sparc on a powerpc (GNU/Linux) to try to
> > >>reproduce the problem, but my machine isn't really fast, it will take
> > >>some time.
> > >
> > >I am able to reproduce it, so it's probably an endianness problem.
> > >I am
> > >debugging...
> >
> > I have been unable to enter the monitor... If you need more
> > information from me, please provide detailed instructions how to
> > obtain the requested log file.
> >
>
> Unfortunately I don't have the same symptoms, so I am not sure it is the
> same problem. In my case the bug has been introduced by the iommu commit
> which does not consider big endian hosts.
>
> The patch below fixes the problem in my case. Could you please try it?

This should be it. Thanks a lot for debugging!

  reply	other threads:[~2007-09-22 12:07 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-21 19:10 [Qemu-devel] qemu/target-sparc exec.h op.c op_helper.c op_me Blue Swirl
2007-09-21 19:32 ` Andreas Färber
2007-09-21 20:25   ` Blue Swirl
2007-09-21 20:41     ` Andreas Färber
2007-09-21 20:26   ` Aurelien Jarno
2007-09-21 21:07     ` Aurelien Jarno
2007-09-21 21:20       ` Andreas Färber
2007-09-22 11:49         ` Aurelien Jarno
2007-09-22 12:07           ` Blue Swirl [this message]
2007-09-22 13:11           ` Andreas Färber
2007-09-22 17:50             ` Aurelien Jarno
2007-09-22 19:27               ` Andreas Färber
2007-09-22 20:06                 ` Aurelien Jarno
2007-09-22 20:23                   ` Andreas Färber
2007-09-22 20:34                     ` Aurelien Jarno
2007-09-22 21:21                       ` Andreas Färber
2007-09-22 21:41                       ` Aurelien Jarno
2007-09-22 21:58                         ` Andreas Färber
2007-09-22 23:11                           ` Aurelien Jarno
2007-09-23  8:44                             ` Andreas Färber
2007-09-25 17:45                             ` Andreas Färber
2007-09-26 11:05                               ` Aurelien Jarno
2007-09-28 14:37                                 ` Andreas Färber
  -- strict thread matches above, loose matches on Subject: below --
2008-02-24 14:10 Blue Swirl

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=f43fc5580709220507k33d962c2o4294babe93fbacd8@mail.gmail.com \
    --to=blauwirbel@gmail.com \
    --cc=qemu-devel@nongnu.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).