From: Aurelien Jarno <aurelien@aurel32.net>
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 19:50:18 +0200 [thread overview]
Message-ID: <46F555DA.50508@aurel32.net> (raw)
In-Reply-To: <3B4277C4-223D-4907-9473-00C0CA2FC623@web.de>
Andreas Färber a écrit :
> Am 22.09.2007 um 13:49 schrieb Aurelien Jarno:
>
>> 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?
>
> I tried Blue Swirl's commit thereof and it still fails for me, same
> symptoms. The virtual CPU load is at about 80% and nothing happens,
> no graphical or textual output (after "starting qemu..."), it just
> hangs.
>
> I can't say exactly which commit introduced the breakage but it
> must've been one this week... And x86 is not affected.
>
> Could it be related to the slavio keyboard handling changes? I'm
> using an Apple keyboard.
>
> Or maybe the 64-bit flag extension patch by Alexander Graf? Wildly
> guessing here...
>
> Would recording serial output to a file help? Or does that apply only
> to boot problems with an OS? Anything else that could help?
>
The main think that would help is to find which commit has broken qemu
on OS X, or in other words the latest version that is working. Then it
would be a lot more easier to find what is wrong in the code.
--
.''`. Aurelien Jarno | GPG: 1024D/F1BCDB73
: :' : Debian developer | Electrical Engineer
`. `' aurel32@debian.org | aurelien@aurel32.net
`- people.debian.org/~aurel32 | www.aurel32.net
next prev parent reply other threads:[~2007-09-22 17:50 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
2007-09-22 13:11 ` Andreas Färber
2007-09-22 17:50 ` Aurelien Jarno [this message]
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=46F555DA.50508@aurel32.net \
--to=aurelien@aurel32.net \
--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).