[FreeVMS] build problem

[BERTRAND Joël]

Alessandro Sangiuliano a écrit :
>
> Il 17/12/2013 10:19, BERTRAND Joël ha scritto:
>> Alessandro Sangiuliano a écrit :
>>> This evening I cloned the L4Ka git repo, where pistachio resides.
>>>
>>> I built it, set up an image with grub2, kickstart, sigma0 and pingpong,
>>> but I get the same error that I get with FreeVMS:
>>
>> You cannot obtain another output with L4Ka as last important L4Ka
>> patch was sent by me ;-)
>>
>>> qemu: fatal: Trying to execute code outside RAM or ROM at
>>> 0x00000000c061e950
>>>
>>> I’m wronging something, but still not discovered what.
>>
>> Can you answer my question ? I don't know what program tries to
>> execute code outside memory.
>>
>> I have checked that kickstart works fine under qemu. It detects memory
>> without error.
>>
>> When you start qemu with :
>>
>> qemu-system-x86_64 -cpu kvm64 -hdc freevms.img -smp 2 -serial stdio -m
>> 128M
>>
>> you should obtain 'two' consoles :
>> - 1st : graphical one
>> - 2nd : serial line
>>
>> Both are driven by libearly, but the firts lines have to be different.
>> Indeed, kickstart prints information on screen and L4/X2 on serial line.
>>
>> Can you confirm that you can read on console :
>> KickStart 0.12.56
>> Detected multiboot compliant loader
>> Kernel ....
>> ...
>> sigma0 ...
>> ...
>> roottask ...
>
> On the console I can see grub, kickstart and its version, the memory
> limit (128M) and the kernel reserved memory (8M).
>
> Then I see:
> kernel and some addresses; they are the same of the output of read -l
> x86-kernel; I will post this outoput in this email, at the end.
>
> I see sigma0 and addresses.
> I see roottask and some addresses.
>>
>> After that, you should obtain on serial line :
>> L4Ka::Pistachio - built on Jun 23 2013 22:23:41 by bertrand at riemann
>> using gcc version 4.7.3
>> (with your build information of course)
>
> On the serial I just see this:
>
> qemu: fatal: Trying to execute code outside RAM or ROM at
> 0x00000000c061e950
>
> EAX=000000b0 EBX=00d16000 ECX=00000f00 EDX=000003fe
> ESI=00000000 EDI=00010000 EBP=00000000 ESP=00d163f4
> EIP=c061e950 EFL=00200042 [---Z---] CPL=0 II=0 A20=1 SMM=0 HLT=0
> ES =0018 00000000 ffffffff 00cf9300 DPL=0 DS [-WA]
> CS =0010 00000000 ffffffff 00cf9a00 DPL=0 CS32 [-R-]
> SS =0018 00000000 ffffffff 00cf9300 DPL=0 DS [-WA]
> DS =0018 00000000 ffffffff 00cf9300 DPL=0 DS [-WA]
> FS =0018 00000000 ffffffff 00cf9300 DPL=0 DS [-WA]
> GS =0018 00000000 ffffffff 00cf9300 DPL=0 DS [-WA]
> LDT=0000 00000000 0000ffff 00008200 DPL=0 LDT
> TR =0000 00000000 0000ffff 00008b00 DPL=0 TSS32-busy
> GDT= 0011abf0 00000020
> IDT= 00000000 00000000
> CR0=00000011 CR2=00000000 CR3=00000000 CR4=00000000
> DR0=0000000000000000 DR1=0000000000000000 DR2=0000000000000000
> DR3=0000000000000000
> DR6=00000000ffff0ff0 DR7=0000000000000400
> CCS=00000018 CCD=00d163f8 CCO=CLR
> EFER=0000000000000000
> FCW=037f FSW=0000 [ST=0] FTW=00 MXCSR=00001f80
> FPR0=0000000000000000 0000 FPR1=0000000000000000 0000
> FPR2=0000000000000000 0000 FPR3=0000000000000000 0000
> FPR4=0000000000000000 0000 FPR5=0000000000000000 0000
> FPR6=0000000000000000 0000 FPR7=0000000000000000 0000
> XMM00=00000000000000000glue/v4-x86/x64/linker.lds000000000000000
> XMM01=00000000000000000000000000000000
> XMM02=00000000000000000000000000000000
> XMM03=00000000000000000000000000000000
> XMM04=00000000000000000000000000000000
> XMM05=00000000000000000000000000000000
> XMM06=00000000000000000000000000000000
> XMM07=00000000000000000000000000000000

	OK. KickStart loads kernel and modules into memory but is not able to 
launch L4/X2.

	I think I have found a bug. If I build L4 with gcc-4.7, it runs fine. 
With 4.8, it doesn't.

	JKB