qemu-ppc
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-ppc] Booting AIX on qemu-system-ppc, kernel not started succes


From: Liang Guo
Subject: Re: [Qemu-ppc] Booting AIX on qemu-system-ppc, kernel not started successfully
Date: Thu, 23 Feb 2012 16:01:26 +0800

On Thu, Feb 23, 2012 at 3:35 PM, Alexander Graf <address@hidden> wrote:
>
> On 23.02.2012, at 08:32, Liang Guo wrote:
>
>> On Thu, Feb 23, 2012 at 3:14 PM, Alexander Graf <address@hidden> wrote:
>>>
>>> On 23.02.2012, at 08:13, Liang Guo wrote:
>>>
>>>> On Thu, Feb 23, 2012 at 2:26 PM, Alexander Graf <address@hidden> wrote:
>>>>>
>>>>> It looks like the disassembler in gdb is configured for something odd, 
>>>>> yeah. POWER1 maybe.
>>>>>
>>>>> Try to run "log in_asm,cpu,int" on the qemu monitor right at the AIX 
>>>>> entry point. The disassembly log should be in /tmp/qemu.log then.
>>>>>
>>>>> Alternatively, you can of course try to use a gdb that works ;).
>>>>>
>>>>> Alex
>>>>
>>>> Too more information generated with log in_asm,cpu,int. the qemu.log is
>>>> attached, hope it is useful. but the asm code is buggy too.
>>>
>>> Hrm, I don't see the CPU states and interrupt information in here. Mind to 
>>> post the complete log somewhere? At http://paste.debian.net for example :)
>>>
>>>
>>> Alex
>>>
>>
>> it is too large, more than 1G, the log may interruppted, for my /tmp
>> is full, I'll generated it asap
>> and upload it to somewhere
>
> Well, we're only interested in the first few hundred lines. After that it's 
> stuck in an endless loop and just prints out its cpu state needlessly. Just 
> cut it off after a few iterations of:
>
>  0x000000000000004c:  blt+    0x40
>
>
> Alex
>
This is the log between 0x3c with several loop between  0x40 and 0x48
http://paste.debian.net/157274/,

the most part of the log is between 0x2c and 0x38, it is about 1.6G

Thanks,
-- 
Liang Guo
http://bluestone.cublog.cn



reply via email to

[Prev in Thread] Current Thread [Next in Thread]