From joel.bertrand at systella.fr Sat Dec 14 14:44:24 2013 From: joel.bertrand at systella.fr (=?ISO-8859-1?Q?BERTRAND_Jo=EBl?=) Date: Sat, 14 Dec 2013 14:44:24 +0100 Subject: [FreeVMS] Question about FreeVMS qemu image In-Reply-To: <523206CD.3060306@systella.fr> References: <523206CD.3060306@systella.fr> Message-ID: <52AC60B8.1050103@systella.fr> BERTRAND Jo?l a ?crit : > Lo?c Maury a ?crit : >> Hello, > > Hello, > >> I am new to the FreeVMS project, and I have tried the Qemu image. >> >> But it seem there are some issues ? >> >> Here is the last kernel messages in Qemu : >> >> %SYS-I-PAGEFLT, pagefault request from $3C at $0000000000800218 >> %SYS-I-PAGEFLT, pagefault request from $3C at $0000000000007FE8 >> %SYS-I-PAGEFLT, pagefault request from $3C at $0000000000801DB0 >> %SYS-I-PAGEFLT, pagefault request from $3C at $00000000008025F8 >> %SYS-I-PAGEFLT, pagefault request from $3C at $0000000000300000 >> %SYS-I-PAGEFLT, pagefault request from $3C at $000000000100C668 >> %RUN-S-STARTED, PAGER.SYS process started >> %PAGER-I-SWPADDR, setting swapper base address at $0000000007FFE000 >> %PAGER-I-SWPSIZE, setting swap size to 0 byte >> %RUN-S-STOPPED, PAGER.SYS process stopped > > It's normal. FreeVMS only creates system threads and tasks. It requires > a pager to be usable. And I have found a bug in git tree (SLAB hangs) I > haven't fixed until now. Bug fixed and commited in git tree. It was not in SLAB but in sys$mutex functions. Thanks to Bruno Ducrot. Regards, JKB From alex22_7 at hotmail.com Sat Dec 14 19:33:15 2013 From: alex22_7 at hotmail.com (Alessandro Sangiuliano) Date: Sat, 14 Dec 2013 19:33:15 +0100 Subject: [FreeVMS] build problem In-Reply-To: <52AC60B8.1050103@systella.fr> References: <523206CD.3060306@systella.fr> <52AC60B8.1050103@systella.fr> Message-ID: Hello, I follow the mailing list, because I still want to learn something of OS developing and L4, contributing to FreeVMS, the road is long but I try. However today I seen there was a bug fix, so I tried to build with the updated code. Unfortunately I fail to build the bootstrap when I give: make bootstrap the error is: checking if C symbols get an underscore after compilation? configure: error: gcc failed to produce assembly code. This problem occurred now that I updated my lynux system and the gcc version is now: 4.8.1 In the previous gcc version, but I don?t remember the version, this problem did not happen and the build process did complete with success. Cheers, Alex From alex22_7 at hotmail.com Sun Dec 15 10:45:17 2013 From: alex22_7 at hotmail.com (Alessandro Sangiuliano) Date: Sun, 15 Dec 2013 10:45:17 +0100 Subject: [FreeVMS] build problem In-Reply-To: References: <523206CD.3060306@systella.fr> <52AC60B8.1050103@systella.fr> Message-ID: Il giorno 14/dic/2013, alle ore 19:33, Alessandro Sangiuliano ha scritto: > Hello, I follow the mailing list, because I still want to learn something of OS developing and L4, contributing to FreeVMS, the road is long but I try. > > However today I seen there was a bug fix, so I tried to build with the updated code. > Unfortunately I fail to build the bootstrap when I give: > > make bootstrap > > the error is: > > checking if C symbols get an underscore after compilation? configure: error: gcc failed to produce assembly code. > > > This problem occurred now that I updated my lynux system and the gcc version is now: > > 4.8.1 > > In the previous gcc version, but I don?t remember the version, this problem did not happen and the build process did complete with success. > > Cheers, > > Alex > _______________________________________________ > FreeVMS mailing list > FreeVMS at rayleigh.systella.fr > https://www.systella.fr/cgi-bin/mailman/listinfo/freevms > On another system with gcc 4.7.3 I can build the kernel but when I run make bootstrap I get this error: make[5]: Leaving directory `/home/alex/FreeVMS/build/bootloader/grub-core/gnulib' make[4]: Leaving directory `/home/alex/FreeVMS/build/bootloader/grub-core/gnulib' make[3]: Leaving directory `/home/alex/FreeVMS/build/bootloader/grub-core/gnulib' Making all in . make[3]: Entering directory `/home/alex/FreeVMS/build/bootloader' make[3]: *** No rule to make target `grub-mkconfig_lib', needed by `all-am'. Stop. make[3]: Leaving directory `/home/alex/FreeVMS/build/bootloader' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/home/alex/FreeVMS/build/bootloader' make[1]: *** [all] Error 2 make[1]: Leaving directory `/home/alex/FreeVMS/build/bootloader' make: *** [bootstrap] Error 2 create a new version of this paste ----------------------------------------------------------------- A: "Hey dude, where are you from?" B: ?I?m from Uros? A: ?What?? B: ?Uros, the Uranos' world capital? A: ?Hey dude, you look so strange and white. You should eat some meat!? B: ?We don?t need to eat? A: ?Hey man, that dude looks so strange, He doesn?t need to eat? C: ?OMG! So strange, he also is so white!? D: ?Why do I have to hunt to eat and survive and he doesn?t need to eat to survive? I hate him!? -------------- next part -------------- An HTML attachment was scrubbed... URL: From joel.bertrand at systella.fr Sun Dec 15 10:49:51 2013 From: joel.bertrand at systella.fr (=?ISO-8859-1?Q?BERTRAND_Jo=EBl?=) Date: Sun, 15 Dec 2013 10:49:51 +0100 Subject: [FreeVMS] build problem In-Reply-To: References: <523206CD.3060306@systella.fr> <52AC60B8.1050103@systella.fr> Message-ID: <52AD7B3F.2060402@systella.fr> Hello, I haven't rebuilt bootstrap after the last patch I have sent to L4 devs to build L4 with gcc 4.7.x. I will check as soon as possible. Regards, JKB From joel.bertrand at systella.fr Sun Dec 15 12:13:50 2013 From: joel.bertrand at systella.fr (=?ISO-8859-1?Q?BERTRAND_Jo=EBl?=) Date: Sun, 15 Dec 2013 12:13:50 +0100 Subject: [FreeVMS] build problem In-Reply-To: References: <523206CD.3060306@systella.fr> <52AC60B8.1050103@systella.fr> Message-ID: <52AD8EEE.7050703@systella.fr> Your failure is not gcc related. I have downloaded git tree and built all FreeVMS with gcc-4.8.2 (I haven't checked if binaries are bootables). I have found two mistakes I have fixed in git today (freetype include directory has changed and grub configure is broken as aclocal has been upgraded on recent linux workstations). --- a/sources/bootloader/util/grub-mkfont.c +++ b/sources/bootloader/util/grub-mkfont.c @@ -39,7 +39,7 @@ #include FT_FREETYPE_H #include FT_TRUETYPE_TAGS_H #include FT_TRUETYPE_TABLES_H -#include +#include #undef __FTERRORS_H__ #define FT_ERROR_START_LIST const char *ft_errmsgs[] = { --- a/Makefile +++ b/Makefile @@ -62,6 +62,7 @@ bootstrap-clean: $(BUILDDIR)/kernel/Makefile $(BUILDDIR)/bootloader/Makefile bootstrap: $(SRCDIR)/kernel/config.h.in $(BUILDDIR)/kernel/Makefile \ $(BUILDDIR)/bootloader/Makefile @make -C $(BUILDDIR)/kernel + @$(BUILDDIR)/bootloader/autogen.sh @make -C $(BUILDDIR)/bootloader bootstrap-install: Regards, JKB From alex22_7 at hotmail.com Sun Dec 15 16:37:23 2013 From: alex22_7 at hotmail.com (Alessandro Sangiuliano) Date: Sun, 15 Dec 2013 16:37:23 +0100 Subject: [FreeVMS] build problem In-Reply-To: <52AD8EEE.7050703@systella.fr> References: <523206CD.3060306@systella.fr> <52AC60B8.1050103@systella.fr> <52AD8EEE.7050703@systella.fr> Message-ID: Il giorno 15/dic/2013, alle ore 12:13, BERTRAND Jo?l ha scritto: > Your failure is not gcc related. I have downloaded git tree and built all FreeVMS with gcc-4.8.2 (I haven't checked if binaries are bootables). > > I have found two mistakes I have fixed in git today (freetype include directory has changed and grub configure is broken as aclocal has been upgraded on recent linux workstations). > Thanks for the fix, I no more have the grub-mkconfig_li error, but another kind of error. Effectively the build process on grub configuration looks broken, or at least on my system. Actually I get the error on autogen.sh, it says: make /home/alex/FrreVMS/build/bootloader/autogen.sh Command non found. I looked in that directory and effectively there is no autogen.sh, instead it is in sources/bootloader/, so I tired to change from $(BUILDDIR)/etc/etc to $(SRCDIR)/etc/etc, at least the build process continued until it says another error: po/POTFILES.in not found? effectively this file is sources/bootloader/po/ but seems that the build system is looking in the root of the project, so in the FreeVMS/po/POTFILES.in. I tried to move the ?po? dir in the root of the project and the build phases continued until it says another error: util/import_unocode.py not found. so it is again looking for the util dir n the root of the project, but it is in the sources/bootloader/. To build I follow the instruction you provided, what is the wrong thing? What system are you using? Regards. > --- a/sources/bootloader/util/grub-mkfont.c > +++ b/sources/bootloader/util/grub-mkfont.c > @@ -39,7 +39,7 @@ > #include FT_FREETYPE_H > #include FT_TRUETYPE_TAGS_H > #include FT_TRUETYPE_TABLES_H > -#include > +#include > > #undef __FTERRORS_H__ > #define FT_ERROR_START_LIST const char *ft_errmsgs[] = { > > --- a/Makefile > +++ b/Makefile > @@ -62,6 +62,7 @@ bootstrap-clean: $(BUILDDIR)/kernel/Makefile $(BUILDDIR)/bootloader/Makefile > bootstrap: $(SRCDIR)/kernel/config.h.in $(BUILDDIR)/kernel/Makefile \ > $(BUILDDIR)/bootloader/Makefile > @make -C $(BUILDDIR)/kernel > + @$(BUILDDIR)/bootloader/autogen.sh > @make -C $(BUILDDIR)/bootloader > > bootstrap-install: > > Regards, > > JKB > _______________________________________________ > FreeVMS mailing list > FreeVMS at rayleigh.systella.fr > https://www.systella.fr/cgi-bin/mailman/listinfo/freevms > ----------------------------------------------------------------- A: "Hey dude, where are you from?" B: ?I?m from Uros? A: ?What?? B: ?Uros, the Uranos' world capital? A: ?Hey dude, you look so strange and white. You should eat some meat!? B: ?We don?t need to eat? A: ?Hey man, that dude looks so strange, He doesn?t need to eat? C: ?OMG! So strange, he also is so white!? D: ?Why do I have to hunt to eat and survive and he doesn?t need to eat to survive? I hate him!? -------------- next part -------------- An HTML attachment was scrubbed... URL: From joel.bertrand at systella.fr Sun Dec 15 16:56:56 2013 From: joel.bertrand at systella.fr (=?windows-1252?Q?BERTRAND_Jo=EBl?=) Date: Sun, 15 Dec 2013 16:56:56 +0100 Subject: [FreeVMS] build problem In-Reply-To: References: <523206CD.3060306@systella.fr> <52AC60B8.1050103@systella.fr> <52AD8EEE.7050703@systella.fr> Message-ID: <52ADD148.5080906@systella.fr> Alessandro Sangiuliano a ?crit : > > Il giorno 15/dic/2013, alle ore 12:13, BERTRAND Jo?l > > ha scritto: > >> Your failure is not gcc related. I have downloaded git tree and built >> all FreeVMS with gcc-4.8.2 (I haven't checked if binaries are bootables). >> >> I have found two mistakes I have fixed in git today (freetype include >> directory has changed and grub configure is broken as aclocal has been >> upgraded on recent linux workstations). >> > Thanks for the fix, I no more have the grub-mkconfig_li error, but > another kind of error. > > Effectively the build process on grub configuration looks broken, or at > least on my system. > > Actually I get the error on autogen.sh, it says: > make /home/alex/FrreVMS/build/bootloader/autogen.sh Command non found. > > I looked in that directory and effectively there is no autogen.sh, > instead it is in sources/bootloader/, so I tired to change from > $(BUILDDIR)/etc/etc to $(SRCDIR)/etc/etc, at least the build process > continued until it says another error: Right. I have done a mistake. > po/POTFILES.in not found? effectively this file is sources/bootloader/po/ > but seems that the build system is looking in the root of the project, > so in the FreeVMS/po/POTFILES.in. I suppose that autogen.sh is broken. Please replace in main Makefile $(SRCDIR)/bootloader/autogen.sh by @(cd $(SRCDIR)/bootloader && autogen.sh). > I tried to move the ?po? dir in the root of the project and the build > phases continued until it says another error: > > util/import_unocode.py not found. so it is again looking for the util > dir n the root of the project, but it is in the sources/bootloader/. > > To build I follow the instruction you provided, what is the wrong thing? > What system are you using? Debian/jessie. Regards, JKB From alex22_7 at hotmail.com Mon Dec 16 00:11:03 2013 From: alex22_7 at hotmail.com (Alessandro Sangiuliano) Date: Mon, 16 Dec 2013 00:11:03 +0100 Subject: [FreeVMS] build problem In-Reply-To: <52ADD148.5080906@systella.fr> References: <523206CD.3060306@systella.fr> <52AC60B8.1050103@systella.fr> <52AD8EEE.7050703@systella.fr> <52ADD148.5080906@systella.fr> Message-ID: Il giorno 15/dic/2013, alle ore 16:56, BERTRAND Jo?l ha scritto: > Alessandro Sangiuliano a ?crit : >> >> Il giorno 15/dic/2013, alle ore 12:13, BERTRAND Jo?l >> > ha scritto: >> >>> Your failure is not gcc related. I have downloaded git tree and built >>> all FreeVMS with gcc-4.8.2 (I haven't checked if binaries are bootables). >>> >>> I have found two mistakes I have fixed in git today (freetype include >>> directory has changed and grub configure is broken as aclocal has been >>> upgraded on recent linux workstations). >>> >> Thanks for the fix, I no more have the grub-mkconfig_li error, but >> another kind of error. >> >> Effectively the build process on grub configuration looks broken, or at >> least on my system. >> >> Actually I get the error on autogen.sh, it says: >> make /home/alex/FrreVMS/build/bootloader/autogen.sh Command non found. >> >> I looked in that directory and effectively there is no autogen.sh, >> instead it is in sources/bootloader/, so I tired to change from >> $(BUILDDIR)/etc/etc to $(SRCDIR)/etc/etc, at least the build process >> continued until it says another error: > > Right. I have done a mistake. > >> po/POTFILES.in not found? effectively this file is sources/bootloader/po/ >> but seems that the build system is looking in the root of the project, >> so in the FreeVMS/po/POTFILES.in. > > I suppose that autogen.sh is broken. Please replace in main Makefile $(SRCDIR)/bootloader/autogen.sh by @(cd $(SRCDIR)/bootloader && autogen.sh). Thanks, $(SRCDIR)/bootloader/autogen.sh by @(cd $(SRCDIR)/bootloader && autogen.sh), not worked so I modified in this way: $(SRCDIR)/bootloader/autogen.sh by @(cd $(SRCDIR)/bootloader && ./autogen.sh) After a while, the output resulted in a lot of error of the kind ?No such file or directory? on files like: .deps-util/grub_fstest-grub_fstest_init.Po, and similar. So, maybe I can confirm that the autogen.sh is broken > >> I tried to move the ?po? dir in the root of the project and the build >> phases continued until it says another error: >> >> util/import_unocode.py not found. so it is again looking for the util >> dir n the root of the project, but it is in the sources/bootloader/. >> >> To build I follow the instruction you provided, what is the wrong thing? >> What system are you using? > > Debian/jessie. > > Regards, > > JKB > Regards, Alex (Slex) ----------------------------------------------------------------- A: "Hey dude, where are you from?" B: ?I?m from Uros? A: ?What?? B: ?Uros, the Uranos' world capital? A: ?Hey dude, you look so strange and white. You should eat some meat!? B: ?We don?t need to eat? A: ?Hey man, that dude looks so strange, He doesn?t need to eat? C: ?OMG! So strange, he also is so white!? D: ?Why do I have to hunt to eat and survive and he doesn?t need to eat to survive? I hate him!? -------------- next part -------------- An HTML attachment was scrubbed... URL: From joel.bertrand at systella.fr Mon Dec 16 10:35:33 2013 From: joel.bertrand at systella.fr (=?windows-1252?Q?BERTRAND_Jo=EBl?=) Date: Mon, 16 Dec 2013 10:35:33 +0100 Subject: [FreeVMS] build problem In-Reply-To: References: <523206CD.3060306@systella.fr> <52AC60B8.1050103@systella.fr> <52AD8EEE.7050703@systella.fr> <52ADD148.5080906@systella.fr> Message-ID: <52AEC965.9080700@systella.fr> Alessandro Sangiuliano a ?crit : > > Il giorno 15/dic/2013, alle ore 16:56, BERTRAND Jo?l > > ha scritto: > >> Alessandro Sangiuliano a ?crit : >>> >>> Il giorno 15/dic/2013, alle ore 12:13, BERTRAND Jo?l >>> >>> > ha scritto: >>> >>>> Your failure is not gcc related. I have downloaded git tree and built >>>> all FreeVMS with gcc-4.8.2 (I haven't checked if binaries are >>>> bootables). >>>> >>>> I have found two mistakes I have fixed in git today (freetype include >>>> directory has changed and grub configure is broken as aclocal has been >>>> upgraded on recent linux workstations). >>>> >>> Thanks for the fix, I no more have the grub-mkconfig_li error, but >>> another kind of error. >>> >>> Effectively the build process on grub configuration looks broken, or at >>> least on my system. >>> >>> Actually I get the error on autogen.sh, it says: >>> make /home/alex/FrreVMS/build/bootloader/autogen.sh Command non found. >>> >>> I looked in that directory and effectively there is no autogen.sh, >>> instead it is in sources/bootloader/, so I tired to change from >>> $(BUILDDIR)/etc/etc to $(SRCDIR)/etc/etc, at least the build process >>> continued until it says another error: >> >> Right. I have done a mistake. >> >>> po/POTFILES.in not found? effectively this file is sources/bootloader/po/ >>> but seems that the build system is looking in the root of the project, >>> so in the FreeVMS/po/POTFILES.in. >> >> I suppose that autogen.sh is broken. Please replace in main Makefile >> $(SRCDIR)/bootloader/autogen.sh by @(cd $(SRCDIR)/bootloader && >> autogen.sh). > > Thanks, $(SRCDIR)/bootloader/autogen.sh by @(cd $(SRCDIR)/bootloader && > autogen.sh), not worked so I modified in this way: > > $(SRCDIR)/bootloader/autogen.sh by @(cd $(SRCDIR)/bootloader && > ./autogen.sh) > > After a while, the output resulted in a lot of error of the kind ?No > such file or directory? on files like: > .deps-util/grub_fstest-grub_fstest_init.Po, and similar. > > So, maybe I can confirm that the autogen.sh is broken. I think in a first time you have to delete build/bootloader. Your tree is broken as you should have grub_fstest-grub_fstest_init.Po in build/bootloader/.deps-util Regards, JKB From alex22_7 at hotmail.com Mon Dec 16 12:12:40 2013 From: alex22_7 at hotmail.com (alex) Date: Mon, 16 Dec 2013 12:12:40 +0100 Subject: [FreeVMS] build problem In-Reply-To: <52AEC965.9080700@systella.fr> References: <523206CD.3060306@systella.fr> <52AC60B8.1050103@systella.fr> <52AD8EEE.7050703@systella.fr> <52ADD148.5080906@systella.fr> <52AEC965.9080700@systella.fr> Message-ID: Il 16/12/2013 10:35, BERTRAND Jo?l ha scritto: > Alessandro Sangiuliano a ?crit : >> >> Il giorno 15/dic/2013, alle ore 16:56, BERTRAND Jo?l >> > ha >> scritto: >> >>> Alessandro Sangiuliano a ?crit : >>>> >>>> Il giorno 15/dic/2013, alle ore 12:13, BERTRAND Jo?l >>>> >>>> > ha scritto: >>>> >>>>> Your failure is not gcc related. I have downloaded git tree and built >>>>> all FreeVMS with gcc-4.8.2 (I haven't checked if binaries are >>>>> bootables). >>>>> >>>>> I have found two mistakes I have fixed in git today (freetype include >>>>> directory has changed and grub configure is broken as aclocal has >>>>> been >>>>> upgraded on recent linux workstations). >>>>> >>>> Thanks for the fix, I no more have the grub-mkconfig_li error, but >>>> another kind of error. >>>> >>>> Effectively the build process on grub configuration looks broken, >>>> or at >>>> least on my system. >>>> >>>> Actually I get the error on autogen.sh, it says: >>>> make /home/alex/FrreVMS/build/bootloader/autogen.sh Command non found. >>>> >>>> I looked in that directory and effectively there is no autogen.sh, >>>> instead it is in sources/bootloader/, so I tired to change from >>>> $(BUILDDIR)/etc/etc to $(SRCDIR)/etc/etc, at least the build process >>>> continued until it says another error: >>> >>> Right. I have done a mistake. >>> >>>> po/POTFILES.in not found? effectively this file is >>>> sources/bootloader/po/ >>>> but seems that the build system is looking in the root of the project, >>>> so in the FreeVMS/po/POTFILES.in. >>> >>> I suppose that autogen.sh is broken. Please replace in main Makefile >>> $(SRCDIR)/bootloader/autogen.sh by @(cd $(SRCDIR)/bootloader && >>> autogen.sh). >> >> Thanks, $(SRCDIR)/bootloader/autogen.sh by @(cd $(SRCDIR)/bootloader && >> autogen.sh), not worked so I modified in this way: >> >> $(SRCDIR)/bootloader/autogen.sh by @(cd $(SRCDIR)/bootloader && >> ./autogen.sh) >> >> After a while, the output resulted in a lot of error of the kind ?No >> such file or directory? on files like: >> .deps-util/grub_fstest-grub_fstest_init.Po, and similar. >> >> So, maybe I can confirm that the autogen.sh is broken. > > I think in a first time you have to delete build/bootloader. Your > tree is broken as you should have grub_fstest-grub_fstest_init.Po in > build/bootloader/.deps-util > > Regards, > > JKB > > Actually I switched to the most recent Ubuntu (should it point jessie?), installed gcc4.7, modified in my locale the include in the grub-mkfont.c to be again and finally I got the system compiled. After that, I made the image, and copied the grub.cfg from the freevms-img on the site. Grub gives me the selection of FreeVMS, but when I boot the system I have this error: alex at omega:~$ qemu-system-x86_64 -hdc image.img -smp 1 -serial stdio -m 128M -k it 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=00000000000000000000000000000000 XMM01=00000000000000000000000000000000 XMM02=00000000000000000000000000000000 XMM03=00000000000000000000000000000000 XMM04=00000000000000000000000000000000 XMM05=00000000000000000000000000000000 XMM06=00000000000000000000000000000000 XMM07=00000000000000000000000000000000 What I wrong? It says is trying to execute code out of the ram. -------------- next part -------------- An HTML attachment was scrubbed... URL: From joel.bertrand at systella.fr Mon Dec 16 12:51:42 2013 From: joel.bertrand at systella.fr (=?windows-1252?Q?BERTRAND_Jo=EBl?=) Date: Mon, 16 Dec 2013 12:51:42 +0100 Subject: [FreeVMS] build problem In-Reply-To: References: <523206CD.3060306@systella.fr> <52AC60B8.1050103@systella.fr> <52AD8EEE.7050703@systella.fr> <52ADD148.5080906@systella.fr> <52AEC965.9080700@systella.fr> Message-ID: <52AEE94E.9010305@systella.fr> alex a ?crit : > > Il 16/12/2013 10:35, BERTRAND Jo?l ha scritto: >> Alessandro Sangiuliano a ?crit : >>> >>> Il giorno 15/dic/2013, alle ore 16:56, BERTRAND Jo?l >>> > ha >>> scritto: >>> >>>> Alessandro Sangiuliano a ?crit : >>>>> >>>>> Il giorno 15/dic/2013, alle ore 12:13, BERTRAND Jo?l >>>>> >>>>> > ha scritto: >>>>> >>>>>> Your failure is not gcc related. I have downloaded git tree and built >>>>>> all FreeVMS with gcc-4.8.2 (I haven't checked if binaries are >>>>>> bootables). >>>>>> >>>>>> I have found two mistakes I have fixed in git today (freetype include >>>>>> directory has changed and grub configure is broken as aclocal has >>>>>> been >>>>>> upgraded on recent linux workstations). >>>>>> >>>>> Thanks for the fix, I no more have the grub-mkconfig_li error, but >>>>> another kind of error. >>>>> >>>>> Effectively the build process on grub configuration looks broken, >>>>> or at >>>>> least on my system. >>>>> >>>>> Actually I get the error on autogen.sh, it says: >>>>> make /home/alex/FrreVMS/build/bootloader/autogen.sh Command non found. >>>>> >>>>> I looked in that directory and effectively there is no autogen.sh, >>>>> instead it is in sources/bootloader/, so I tired to change from >>>>> $(BUILDDIR)/etc/etc to $(SRCDIR)/etc/etc, at least the build process >>>>> continued until it says another error: >>>> >>>> Right. I have done a mistake. >>>> >>>>> po/POTFILES.in not found? effectively this file is >>>>> sources/bootloader/po/ >>>>> but seems that the build system is looking in the root of the project, >>>>> so in the FreeVMS/po/POTFILES.in. >>>> >>>> I suppose that autogen.sh is broken. Please replace in main Makefile >>>> $(SRCDIR)/bootloader/autogen.sh by @(cd $(SRCDIR)/bootloader && >>>> autogen.sh). >>> >>> Thanks, $(SRCDIR)/bootloader/autogen.sh by @(cd $(SRCDIR)/bootloader && >>> autogen.sh), not worked so I modified in this way: >>> >>> $(SRCDIR)/bootloader/autogen.sh by @(cd $(SRCDIR)/bootloader && >>> ./autogen.sh) >>> >>> After a while, the output resulted in a lot of error of the kind ?No >>> such file or directory? on files like: >>> .deps-util/grub_fstest-grub_fstest_init.Po, and similar. >>> >>> So, maybe I can confirm that the autogen.sh is broken. >> >> I think in a first time you have to delete build/bootloader. Your >> tree is broken as you should have grub_fstest-grub_fstest_init.Po in >> build/bootloader/.deps-util >> >> Regards, >> >> JKB >> >> > > Actually I switched to the most recent Ubuntu (should it point jessie?), > installed gcc4.7, modified in my locale the include in the grub-mkfont.c > to be again and finally I got the system compiled. > > > After that, I made the image, and copied the grub.cfg from the > freevms-img on the site. > > Grub gives me the selection of FreeVMS, but when I boot the system I > have this error: > > > > alex at omega:~$ qemu-system-x86_64 -hdc image.img -smp 1 -serial stdio -m > 128M -k it > 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=00000000000000000000000000000000 > XMM01=00000000000000000000000000000000 > XMM02=00000000000000000000000000000000 > XMM03=00000000000000000000000000000000 > XMM04=00000000000000000000000000000000 > XMM05=00000000000000000000000000000000 > XMM06=00000000000000000000000000000000 > XMM07=00000000000000000000000000000000 > > > > What I wrong? It says is trying to execute code out of the ram. Very strange. I don't know what is your grub.cfg. Mine is : set timeout=10 menuentry 'FreeVMS' { multiboot /boot/kickstart maxmem=128M kmem=8M module /boot/x86-kernel module /boot/sigma0 module /boot/vmskernel.sys vmskernel.sys root=dqa0.0 console=opa0 \ nodbg\$virtual_memory \ dbg\$sys_pagefault dbg\$vms_pagefault module /boot/pager.sys pager.sys module /boot/init.exe init.exe #?module /boot/drv/dq\$pxii.sys #?module /boot/drv/dp\$pc99.sys #?module /boot/drv/fs\$ext2.sys } menuentry 'FreeVMS-test' { multiboot /boot/kickstart maxmem=128M kmem=8M module /boot/x86-kernel-test module /boot/sigma0 module /boot/vmskernel.sys vmskernel.sys root=dqa0.0 console=opa0 \ nodbg\$virtual_memory \ dbg\$sys_pagefault dbg\$vms_pagefault module /boot/pager.sys pager.sys module /boot/init.exe init.exe #?module /boot/drv/dq\$pxii.sys #?module /boot/drv/dp\$pc99.sys #?module /boot/drv/fs\$ext2.sys } kickstart is used to map all modules into memory. Today, it requires two arguments : maxmem (amount of memory) and kmem (reserved kernel memory). I suppose you have forgotten these arguments (or maxmem has a erroneous value). Indeed, in some cases, kickstart is not able to determine these values. On console, you should have : - grub - kickstart 'version' and some memory indications On serial line, you should obtain : riemann:[~/openvms] > ./qemu L4Ka::Pistachio - built on Jun 23 2013 22:23:41 by bertrand at riemann using gcc version 4.7.3 // comes from L4/X2 (and of course sigma0) // Following lines come from freevms.sys, init.exe and pager.sys >>> FreeVMS 0.4.0 (R) %SYSBOOT-I-SYSBOOT, leaving kernel privileges %SYSBOOT-I-SYSBOOT, launching FreeVMS kernel with executive privileges %SYSBOOT-I-SYSBOOT, booting main processor %SYSBOOT-I-SYSBOOT, computing page size: 4096 bytes %SYSBOOT-I-SYSBOOT, booting 1 secondary processor %SYSBOOT-I-SYSBOOT, CPU0 EXTFREQ=1001 MHz, INTFREQ=1649 MHz %SYSBOOT-I-SYSBOOT, CPU1 EXTFREQ=1001 MHz, INTFREQ=1648 MHz %SYSBOOT-I-SYSBOOT, parsing command line: vmskernel.sys root=dqa0.0 console=opa0 nodbg$virtual_memory dbg$sys_pagefault dbg$vms_pagefault %SYSBOOT-I-SYSBOOT, selecting root device: DQA0.0 %SYSBOOT-I-SYSBOOT, selecting console device: OPA0 %SYSBOOT-I-SYSBOOT, initializing memory ... Regards, JKB From alex22_7 at hotmail.com Mon Dec 16 13:16:28 2013 From: alex22_7 at hotmail.com (Alessandro Sangiuliano) Date: Mon, 16 Dec 2013 13:16:28 +0100 Subject: [FreeVMS] build problem In-Reply-To: <52AEE94E.9010305@systella.fr> References: <523206CD.3060306@systella.fr> <52AC60B8.1050103@systella.fr> <52AD8EEE.7050703@systella.fr> <52ADD148.5080906@systella.fr> <52AEC965.9080700@systella.fr> <52AEE94E.9010305@systella.fr> Message-ID: Il 16/12/2013 12:51, BERTRAND Jo?l ha scritto: > alex a ?crit : >> >> Il 16/12/2013 10:35, BERTRAND Jo?l ha scritto: >>> Alessandro Sangiuliano a ?crit : >>>> >>>> Il giorno 15/dic/2013, alle ore 16:56, BERTRAND Jo?l >>>> > ha >>>> scritto: >>>> >>>>> Alessandro Sangiuliano a ?crit : >>>>>> >>>>>> Il giorno 15/dic/2013, alle ore 12:13, BERTRAND Jo?l >>>>>> >>>>>> > ha scritto: >>>>>> >>>>>>> Your failure is not gcc related. I have downloaded git tree and >>>>>>> built >>>>>>> all FreeVMS with gcc-4.8.2 (I haven't checked if binaries are >>>>>>> bootables). >>>>>>> >>>>>>> I have found two mistakes I have fixed in git today (freetype >>>>>>> include >>>>>>> directory has changed and grub configure is broken as aclocal has >>>>>>> been >>>>>>> upgraded on recent linux workstations). >>>>>>> >>>>>> Thanks for the fix, I no more have the grub-mkconfig_li error, but >>>>>> another kind of error. >>>>>> >>>>>> Effectively the build process on grub configuration looks broken, >>>>>> or at >>>>>> least on my system. >>>>>> >>>>>> Actually I get the error on autogen.sh, it says: >>>>>> make /home/alex/FrreVMS/build/bootloader/autogen.sh Command non >>>>>> found. >>>>>> >>>>>> I looked in that directory and effectively there is no autogen.sh, >>>>>> instead it is in sources/bootloader/, so I tired to change from >>>>>> $(BUILDDIR)/etc/etc to $(SRCDIR)/etc/etc, at least the build process >>>>>> continued until it says another error: >>>>> >>>>> Right. I have done a mistake. >>>>> >>>>>> po/POTFILES.in not found? effectively this file is >>>>>> sources/bootloader/po/ >>>>>> but seems that the build system is looking in the root of the >>>>>> project, >>>>>> so in the FreeVMS/po/POTFILES.in. >>>>> >>>>> I suppose that autogen.sh is broken. Please replace in main Makefile >>>>> $(SRCDIR)/bootloader/autogen.sh by @(cd $(SRCDIR)/bootloader && >>>>> autogen.sh). >>>> >>>> Thanks, $(SRCDIR)/bootloader/autogen.sh by @(cd >>>> $(SRCDIR)/bootloader && >>>> autogen.sh), not worked so I modified in this way: >>>> >>>> $(SRCDIR)/bootloader/autogen.sh by @(cd $(SRCDIR)/bootloader && >>>> ./autogen.sh) >>>> >>>> After a while, the output resulted in a lot of error of the kind ?No >>>> such file or directory? on files like: >>>> .deps-util/grub_fstest-grub_fstest_init.Po, and similar. >>>> >>>> So, maybe I can confirm that the autogen.sh is broken. >>> >>> I think in a first time you have to delete build/bootloader. Your >>> tree is broken as you should have grub_fstest-grub_fstest_init.Po in >>> build/bootloader/.deps-util >>> >>> Regards, >>> >>> JKB >>> >>> >> >> Actually I switched to the most recent Ubuntu (should it point jessie?), >> installed gcc4.7, modified in my locale the include in the grub-mkfont.c >> to be again and finally I got the system compiled. >> >> >> After that, I made the image, and copied the grub.cfg from the >> freevms-img on the site. >> >> Grub gives me the selection of FreeVMS, but when I boot the system I >> have this error: >> >> >> >> alex at omega:~$ qemu-system-x86_64 -hdc image.img -smp 1 -serial stdio -m >> 128M -k it >> 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=00000000000000000000000000000000 >> XMM01=00000000000000000000000000000000 >> XMM02=00000000000000000000000000000000 >> XMM03=00000000000000000000000000000000 >> XMM04=00000000000000000000000000000000 >> XMM05=00000000000000000000000000000000 >> XMM06=00000000000000000000000000000000 >> XMM07=00000000000000000000000000000000 >> >> >> >> What I wrong? It says is trying to execute code out of the ram. > > Very strange. > > I don't know what is your grub.cfg. Mine is : > > set timeout=10 > > menuentry 'FreeVMS' { > multiboot /boot/kickstart maxmem=128M kmem=8M > module /boot/x86-kernel > module /boot/sigma0 > module /boot/vmskernel.sys vmskernel.sys root=dqa0.0 console=opa0 \ > nodbg\$virtual_memory \ > dbg\$sys_pagefault dbg\$vms_pagefault > module /boot/pager.sys pager.sys > module /boot/init.exe init.exe > #?module /boot/drv/dq\$pxii.sys > #?module /boot/drv/dp\$pc99.sys > #?module /boot/drv/fs\$ext2.sys > } > > menuentry 'FreeVMS-test' { > multiboot /boot/kickstart maxmem=128M kmem=8M > module /boot/x86-kernel-test > module /boot/sigma0 > module /boot/vmskernel.sys vmskernel.sys root=dqa0.0 console=opa0 \ > nodbg\$virtual_memory \ > dbg\$sys_pagefault dbg\$vms_pagefault > module /boot/pager.sys pager.sys > module /boot/init.exe init.exe > #?module /boot/drv/dq\$pxii.sys > #?module /boot/drv/dp\$pc99.sys > #?module /boot/drv/fs\$ext2.sys > } > > kickstart is used to map all modules into memory. Today, it > requires two arguments : maxmem (amount of memory) and kmem (reserved > kernel memory). I suppose you have forgotten these arguments (or > maxmem has a erroneous value). Indeed, in some cases, kickstart is not > able to determine these values. > > On console, you should have : > - grub > - kickstart 'version' and some memory indications > > On serial line, you should obtain : > > riemann:[~/openvms] > ./qemu > > L4Ka::Pistachio - built on Jun 23 2013 22:23:41 by bertrand at riemann > using gcc version 4.7.3 > // comes from L4/X2 (and of course sigma0) > > // Following lines come from freevms.sys, init.exe and pager.sys > >>> FreeVMS 0.4.0 (R) > > %SYSBOOT-I-SYSBOOT, leaving kernel privileges > %SYSBOOT-I-SYSBOOT, launching FreeVMS kernel with executive privileges > %SYSBOOT-I-SYSBOOT, booting main processor > %SYSBOOT-I-SYSBOOT, computing page size: 4096 bytes > %SYSBOOT-I-SYSBOOT, booting 1 secondary processor > %SYSBOOT-I-SYSBOOT, CPU0 EXTFREQ=1001 MHz, INTFREQ=1649 MHz > %SYSBOOT-I-SYSBOOT, CPU1 EXTFREQ=1001 MHz, INTFREQ=1648 MHz > %SYSBOOT-I-SYSBOOT, parsing command line: vmskernel.sys root=dqa0.0 > console=opa0 nodbg$virtual_memory dbg$sys_pagefault dbg$vms_pagefault > %SYSBOOT-I-SYSBOOT, selecting root device: DQA0.0 > %SYSBOOT-I-SYSBOOT, selecting console device: OPA0 > %SYSBOOT-I-SYSBOOT, initializing memory > ... > > Regards, > > JKB > > This is the mine: set timeout=10 menuentry 'FreeVMS' { multiboot /boot/kickstart maxmem=128M kmem=8M module /boot/x86-kernel module /boot/sigma0 module /boot/vmskernel.sys vmskernel.sys root=dqa0.0 console=opa0 \ nodbg\$virtual_memory \ dbg\$sys_pagefault dbg\$vms_pagefault module /boot/pager.sys pager.sys module /boot/init.exe init.exe #?module /boot/drv/dq\$pxii.sys #?module /boot/drv/dp\$pc99.sys #?module /boot/drv/fs\$ext2.sys } I will check later if something gone wrong Regards, Alex From alex22_7 at hotmail.com Mon Dec 16 23:30:58 2013 From: alex22_7 at hotmail.com (Alessandro Sangiuliano) Date: Mon, 16 Dec 2013 23:30:58 +0100 Subject: [FreeVMS] build problem In-Reply-To: <52AEE94E.9010305@systella.fr> References: <523206CD.3060306@systella.fr> <52AC60B8.1050103@systella.fr> <52AD8EEE.7050703@systella.fr> <52ADD148.5080906@systella.fr> <52AEC965.9080700@systella.fr> <52AEE94E.9010305@systella.fr> Message-ID: Il giorno 16/dic/2013, alle ore 12:51, BERTRAND Jo?l ha scritto: > alex a ?crit : >> >> Il 16/12/2013 10:35, BERTRAND Jo?l ha scritto: >>> Alessandro Sangiuliano a ?crit : >>>> >>>> Il giorno 15/dic/2013, alle ore 16:56, BERTRAND Jo?l >>>> > ha >>>> scritto: >>>> >>>>> Alessandro Sangiuliano a ?crit : >>>>>> >>>>>> Il giorno 15/dic/2013, alle ore 12:13, BERTRAND Jo?l >>>>>> >>>>>> > ha scritto: >>>>>> >>>>>>> Your failure is not gcc related. I have downloaded git tree and built >>>>>>> all FreeVMS with gcc-4.8.2 (I haven't checked if binaries are >>>>>>> bootables). >>>>>>> >>>>>>> I have found two mistakes I have fixed in git today (freetype include >>>>>>> directory has changed and grub configure is broken as aclocal has >>>>>>> been >>>>>>> upgraded on recent linux workstations). >>>>>>> >>>>>> Thanks for the fix, I no more have the grub-mkconfig_li error, but >>>>>> another kind of error. >>>>>> >>>>>> Effectively the build process on grub configuration looks broken, >>>>>> or at >>>>>> least on my system. >>>>>> >>>>>> Actually I get the error on autogen.sh, it says: >>>>>> make /home/alex/FrreVMS/build/bootloader/autogen.sh Command non found. >>>>>> >>>>>> I looked in that directory and effectively there is no autogen.sh, >>>>>> instead it is in sources/bootloader/, so I tired to change from >>>>>> $(BUILDDIR)/etc/etc to $(SRCDIR)/etc/etc, at least the build process >>>>>> continued until it says another error: >>>>> >>>>> Right. I have done a mistake. >>>>> >>>>>> po/POTFILES.in not found? effectively this file is >>>>>> sources/bootloader/po/ >>>>>> but seems that the build system is looking in the root of the project, >>>>>> so in the FreeVMS/po/POTFILES.in. >>>>> >>>>> I suppose that autogen.sh is broken. Please replace in main Makefile >>>>> $(SRCDIR)/bootloader/autogen.sh by @(cd $(SRCDIR)/bootloader && >>>>> autogen.sh). >>>> >>>> Thanks, $(SRCDIR)/bootloader/autogen.sh by @(cd $(SRCDIR)/bootloader && >>>> autogen.sh), not worked so I modified in this way: >>>> >>>> $(SRCDIR)/bootloader/autogen.sh by @(cd $(SRCDIR)/bootloader && >>>> ./autogen.sh) >>>> >>>> After a while, the output resulted in a lot of error of the kind ?No >>>> such file or directory? on files like: >>>> .deps-util/grub_fstest-grub_fstest_init.Po, and similar. >>>> >>>> So, maybe I can confirm that the autogen.sh is broken. >>> >>> I think in a first time you have to delete build/bootloader. Your >>> tree is broken as you should have grub_fstest-grub_fstest_init.Po in >>> build/bootloader/.deps-util >>> >>> Regards, >>> >>> JKB >>> >>> >> >> Actually I switched to the most recent Ubuntu (should it point jessie?), >> installed gcc4.7, modified in my locale the include in the grub-mkfont.c >> to be again and finally I got the system compiled. >> >> >> After that, I made the image, and copied the grub.cfg from the >> freevms-img on the site. >> >> Grub gives me the selection of FreeVMS, but when I boot the system I >> have this error: >> >> >> >> alex at omega:~$ qemu-system-x86_64 -hdc image.img -smp 1 -serial stdio -m >> 128M -k it >> 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=00000000000000000000000000000000 >> XMM01=00000000000000000000000000000000 >> XMM02=00000000000000000000000000000000 >> XMM03=00000000000000000000000000000000 >> XMM04=00000000000000000000000000000000 >> XMM05=00000000000000000000000000000000 >> XMM06=00000000000000000000000000000000 >> XMM07=00000000000000000000000000000000 >> >> >> >> What I wrong? It says is trying to execute code out of the ram. > > Very strange. > > I don't know what is your grub.cfg. Mine is : > > set timeout=10 > > menuentry 'FreeVMS' { > multiboot /boot/kickstart maxmem=128M kmem=8M > module /boot/x86-kernel > module /boot/sigma0 > module /boot/vmskernel.sys vmskernel.sys root=dqa0.0 console=opa0 \ > nodbg\$virtual_memory \ > dbg\$sys_pagefault dbg\$vms_pagefault > module /boot/pager.sys pager.sys > module /boot/init.exe init.exe > #?module /boot/drv/dq\$pxii.sys > #?module /boot/drv/dp\$pc99.sys > #?module /boot/drv/fs\$ext2.sys > } > > menuentry 'FreeVMS-test' { > multiboot /boot/kickstart maxmem=128M kmem=8M > module /boot/x86-kernel-test > module /boot/sigma0 > module /boot/vmskernel.sys vmskernel.sys root=dqa0.0 console=opa0 \ > nodbg\$virtual_memory \ > dbg\$sys_pagefault dbg\$vms_pagefault > module /boot/pager.sys pager.sys > module /boot/init.exe init.exe > #?module /boot/drv/dq\$pxii.sys > #?module /boot/drv/dp\$pc99.sys > #?module /boot/drv/fs\$ext2.sys > } > > kickstart is used to map all modules into memory. Today, it requires two arguments : maxmem (amount of memory) and kmem (reserved kernel memory). I suppose you have forgotten these arguments (or maxmem has a erroneous value). Indeed, in some cases, kickstart is not able to determine these values. > > On console, you should have : > - grub > - kickstart 'version' and some memory indications > > On serial line, you should obtain : > > riemann:[~/openvms] > ./qemu > > L4Ka::Pistachio - built on Jun 23 2013 22:23:41 by bertrand at riemann using gcc version 4.7.3 > // comes from L4/X2 (and of course sigma0) > > // Following lines come from freevms.sys, init.exe and pager.sys > >>> FreeVMS 0.4.0 (R) > > %SYSBOOT-I-SYSBOOT, leaving kernel privileges > %SYSBOOT-I-SYSBOOT, launching FreeVMS kernel with executive privileges > %SYSBOOT-I-SYSBOOT, booting main processor > %SYSBOOT-I-SYSBOOT, computing page size: 4096 bytes > %SYSBOOT-I-SYSBOOT, booting 1 secondary processor > %SYSBOOT-I-SYSBOOT, CPU0 EXTFREQ=1001 MHz, INTFREQ=1649 MHz > %SYSBOOT-I-SYSBOOT, CPU1 EXTFREQ=1001 MHz, INTFREQ=1648 MHz > %SYSBOOT-I-SYSBOOT, parsing command line: vmskernel.sys root=dqa0.0 console=opa0 nodbg$virtual_memory dbg$sys_pagefault dbg$vms_pagefault > %SYSBOOT-I-SYSBOOT, selecting root device: DQA0.0 > %SYSBOOT-I-SYSBOOT, selecting console device: OPA0 > %SYSBOOT-I-SYSBOOT, initializing memory > ... > > Regards, > > JKB 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: qemu: fatal: Trying to execute code outside RAM or ROM at 0x00000000c061e950 I?m wronging something, but still not discovered what. Regarrds, Alex ----------------------------------------------------------------- A: "Hey dude, where are you from?" B: ?I?m from Uros? A: ?What?? B: ?Uros, the Uranos' world capital? A: ?Hey dude, you look so strange and white. You should eat some meat!? B: ?We don?t need to eat? A: ?Hey man, that dude looks so strange, He doesn?t need to eat? C: ?OMG! So strange, he also is so white!? D: ?Why do I have to hunt to eat and survive and he doesn?t need to eat to survive? I hate him!? -------------- next part -------------- An HTML attachment was scrubbed... URL: From alex22_7 at hotmail.com Mon Dec 16 23:30:59 2013 From: alex22_7 at hotmail.com (Alessandro Sangiuliano) Date: Mon, 16 Dec 2013 23:30:59 +0100 Subject: [FreeVMS] build problem In-Reply-To: <52AEE94E.9010305@systella.fr> References: <523206CD.3060306@systella.fr> <52AC60B8.1050103@systella.fr> <52AD8EEE.7050703@systella.fr> <52ADD148.5080906@systella.fr> <52AEC965.9080700@systella.fr> <52AEE94E.9010305@systella.fr> Message-ID: Il giorno 16/dic/2013, alle ore 12:51, BERTRAND Jo?l ha scritto: > alex a ?crit : >> >> Il 16/12/2013 10:35, BERTRAND Jo?l ha scritto: >>> Alessandro Sangiuliano a ?crit : >>>> >>>> Il giorno 15/dic/2013, alle ore 16:56, BERTRAND Jo?l >>>> > ha >>>> scritto: >>>> >>>>> Alessandro Sangiuliano a ?crit : >>>>>> >>>>>> Il giorno 15/dic/2013, alle ore 12:13, BERTRAND Jo?l >>>>>> >>>>>> > ha scritto: >>>>>> >>>>>>> Your failure is not gcc related. I have downloaded git tree and built >>>>>>> all FreeVMS with gcc-4.8.2 (I haven't checked if binaries are >>>>>>> bootables). >>>>>>> >>>>>>> I have found two mistakes I have fixed in git today (freetype include >>>>>>> directory has changed and grub configure is broken as aclocal has >>>>>>> been >>>>>>> upgraded on recent linux workstations). >>>>>>> >>>>>> Thanks for the fix, I no more have the grub-mkconfig_li error, but >>>>>> another kind of error. >>>>>> >>>>>> Effectively the build process on grub configuration looks broken, >>>>>> or at >>>>>> least on my system. >>>>>> >>>>>> Actually I get the error on autogen.sh, it says: >>>>>> make /home/alex/FrreVMS/build/bootloader/autogen.sh Command non found. >>>>>> >>>>>> I looked in that directory and effectively there is no autogen.sh, >>>>>> instead it is in sources/bootloader/, so I tired to change from >>>>>> $(BUILDDIR)/etc/etc to $(SRCDIR)/etc/etc, at least the build process >>>>>> continued until it says another error: >>>>> >>>>> Right. I have done a mistake. >>>>> >>>>>> po/POTFILES.in not found? effectively this file is >>>>>> sources/bootloader/po/ >>>>>> but seems that the build system is looking in the root of the project, >>>>>> so in the FreeVMS/po/POTFILES.in. >>>>> >>>>> I suppose that autogen.sh is broken. Please replace in main Makefile >>>>> $(SRCDIR)/bootloader/autogen.sh by @(cd $(SRCDIR)/bootloader && >>>>> autogen.sh). >>>> >>>> Thanks, $(SRCDIR)/bootloader/autogen.sh by @(cd $(SRCDIR)/bootloader && >>>> autogen.sh), not worked so I modified in this way: >>>> >>>> $(SRCDIR)/bootloader/autogen.sh by @(cd $(SRCDIR)/bootloader && >>>> ./autogen.sh) >>>> >>>> After a while, the output resulted in a lot of error of the kind ?No >>>> such file or directory? on files like: >>>> .deps-util/grub_fstest-grub_fstest_init.Po, and similar. >>>> >>>> So, maybe I can confirm that the autogen.sh is broken. >>> >>> I think in a first time you have to delete build/bootloader. Your >>> tree is broken as you should have grub_fstest-grub_fstest_init.Po in >>> build/bootloader/.deps-util >>> >>> Regards, >>> >>> JKB >>> >>> >> >> Actually I switched to the most recent Ubuntu (should it point jessie?), >> installed gcc4.7, modified in my locale the include in the grub-mkfont.c >> to be again and finally I got the system compiled. >> >> >> After that, I made the image, and copied the grub.cfg from the >> freevms-img on the site. >> >> Grub gives me the selection of FreeVMS, but when I boot the system I >> have this error: >> >> >> >> alex at omega:~$ qemu-system-x86_64 -hdc image.img -smp 1 -serial stdio -m >> 128M -k it >> 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=00000000000000000000000000000000 >> XMM01=00000000000000000000000000000000 >> XMM02=00000000000000000000000000000000 >> XMM03=00000000000000000000000000000000 >> XMM04=00000000000000000000000000000000 >> XMM05=00000000000000000000000000000000 >> XMM06=00000000000000000000000000000000 >> XMM07=00000000000000000000000000000000 >> >> >> >> What I wrong? It says is trying to execute code out of the ram. > > Very strange. > > I don't know what is your grub.cfg. Mine is : > > set timeout=10 > > menuentry 'FreeVMS' { > multiboot /boot/kickstart maxmem=128M kmem=8M > module /boot/x86-kernel > module /boot/sigma0 > module /boot/vmskernel.sys vmskernel.sys root=dqa0.0 console=opa0 \ > nodbg\$virtual_memory \ > dbg\$sys_pagefault dbg\$vms_pagefault > module /boot/pager.sys pager.sys > module /boot/init.exe init.exe > #?module /boot/drv/dq\$pxii.sys > #?module /boot/drv/dp\$pc99.sys > #?module /boot/drv/fs\$ext2.sys > } > > menuentry 'FreeVMS-test' { > multiboot /boot/kickstart maxmem=128M kmem=8M > module /boot/x86-kernel-test > module /boot/sigma0 > module /boot/vmskernel.sys vmskernel.sys root=dqa0.0 console=opa0 \ > nodbg\$virtual_memory \ > dbg\$sys_pagefault dbg\$vms_pagefault > module /boot/pager.sys pager.sys > module /boot/init.exe init.exe > #?module /boot/drv/dq\$pxii.sys > #?module /boot/drv/dp\$pc99.sys > #?module /boot/drv/fs\$ext2.sys > } > > kickstart is used to map all modules into memory. Today, it requires two arguments : maxmem (amount of memory) and kmem (reserved kernel memory). I suppose you have forgotten these arguments (or maxmem has a erroneous value). Indeed, in some cases, kickstart is not able to determine these values. > > On console, you should have : > - grub > - kickstart 'version' and some memory indications > > On serial line, you should obtain : > > riemann:[~/openvms] > ./qemu > > L4Ka::Pistachio - built on Jun 23 2013 22:23:41 by bertrand at riemann using gcc version 4.7.3 > // comes from L4/X2 (and of course sigma0) > > // Following lines come from freevms.sys, init.exe and pager.sys > >>> FreeVMS 0.4.0 (R) > > %SYSBOOT-I-SYSBOOT, leaving kernel privileges > %SYSBOOT-I-SYSBOOT, launching FreeVMS kernel with executive privileges > %SYSBOOT-I-SYSBOOT, booting main processor > %SYSBOOT-I-SYSBOOT, computing page size: 4096 bytes > %SYSBOOT-I-SYSBOOT, booting 1 secondary processor > %SYSBOOT-I-SYSBOOT, CPU0 EXTFREQ=1001 MHz, INTFREQ=1649 MHz > %SYSBOOT-I-SYSBOOT, CPU1 EXTFREQ=1001 MHz, INTFREQ=1648 MHz > %SYSBOOT-I-SYSBOOT, parsing command line: vmskernel.sys root=dqa0.0 console=opa0 nodbg$virtual_memory dbg$sys_pagefault dbg$vms_pagefault > %SYSBOOT-I-SYSBOOT, selecting root device: DQA0.0 > %SYSBOOT-I-SYSBOOT, selecting console device: OPA0 > %SYSBOOT-I-SYSBOOT, initializing memory > ... > > Regards, > > JKB 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: qemu: fatal: Trying to execute code outside RAM or ROM at 0x00000000c061e950 I?m wronging something, but still not discovered what. Regarrds, Alex ----------------------------------------------------------------- A: "Hey dude, where are you from?" B: ?I?m from Uros? A: ?What?? B: ?Uros, the Uranos' world capital? A: ?Hey dude, you look so strange and white. You should eat some meat!? B: ?We don?t need to eat? A: ?Hey man, that dude looks so strange, He doesn?t need to eat? C: ?OMG! So strange, he also is so white!? D: ?Why do I have to hunt to eat and survive and he doesn?t need to eat to survive? I hate him!? -------------- next part -------------- An HTML attachment was scrubbed... URL: From joel.bertrand at systella.fr Tue Dec 17 10:19:41 2013 From: joel.bertrand at systella.fr (=?windows-1252?Q?BERTRAND_Jo=EBl?=) Date: Tue, 17 Dec 2013 10:19:41 +0100 Subject: [FreeVMS] build problem In-Reply-To: References: <523206CD.3060306@systella.fr> <52AC60B8.1050103@systella.fr> <52AD8EEE.7050703@systella.fr> <52ADD148.5080906@systella.fr> <52AEC965.9080700@systella.fr> <52AEE94E.9010305@systella.fr> Message-ID: <52B0172D.8090104@systella.fr> 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 ... 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) Now, L4/X2 is running and lanching sigma0 (sigma0 has no output) and roottask (freevms.sys) that prints all other informations. When do you obtain your error ? This information is very important. Indeed, kickstart should relocated kernel. For example : riemann:[~/openvms/mnt/boot] > readelf -l x86-kernel Type de fichier ELF est EXEC (fichier ex?cutable) Point d'entr?e 0xd17000 Il y a 6 en-t?tes de programme, d?butant ? l'adresse de d?calage64 Type de fichier ELF est EXEC (fichier ex?cutable) Point d'entr?e 0xd17000 Il y a 6 en-t?tes de programme, d?butant ? l'adresse de d?calage64 En-t?tes de programme: Type D?calage Adr.virt Adr.phys. Taille fichier Taille m?moire Fanion Alignement LOAD 0x00000000000001a0 0xffffffffc0600000 0x0000000000600000 0x000000000002d560 0x000000000002d560 RWE 20 LOAD 0x000000000002d700 0xffffffffc0800000 0x0000000000800000 0x0000000000000903 0x0000000000000903 R E 10 LOAD 0x000000000002f000 0xffffffffc0a00000 0x0000000000a00000 0x00000000000051b4 0x00000000000051b4 RW 1000 LOAD 0x0000000000035000 0xffffffffc0c00000 0x0000000000c00000 0x0000000000016450 0x0000000000016450 RWE 1000 LOAD 0x000000000004c000 0x0000000000d17000 0x0000000000d17000 0x0000000000007cf0 0x0000000000007cf0 RWE 1000 GNU_STACK 0x0000000000000000 0x0000000000000000 0x0000000000000000 0x0000000000000000 0x0000000000000000 RWE 8 and kickstart should indicates the same informations : ... -> 0x00600000-0x0062d560 ... -> 0x00800000-0x00800903 ... Please note that Adr.phys. always should be accessible (in the first 128 MB in your case). If not, your linker script is broken. Can you send here ELF header of your kernel ? Some addresses are configured by : cd $(BUILDDIR)/kernel && $(SRCDIR)/kernel/configure \ --with-kickstart-linkbase=0x00100000 \ --with-s0-linkbase=0x00080000 \ --with-roottask-linkbase=0x00200000 Regards, JKB From joel.bertrand at systella.fr Tue Dec 17 16:01:53 2013 From: joel.bertrand at systella.fr (=?windows-1252?Q?BERTRAND_Jo=EBl?=) Date: Tue, 17 Dec 2013 16:01:53 +0100 Subject: [FreeVMS] build problem In-Reply-To: References: <523206CD.3060306@systella.fr> <52AC60B8.1050103@systella.fr> <52AD8EEE.7050703@systella.fr> <52ADD148.5080906@systella.fr> <52AEC965.9080700@systella.fr> <52AEE94E.9010305@systella.fr> <52B0172D.8090104@systella.fr> Message-ID: <52B06761.40101@systella.fr> 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 From joel.bertrand at systella.fr Tue Dec 17 16:31:23 2013 From: joel.bertrand at systella.fr (=?windows-1252?Q?BERTRAND_Jo=EBl?=) Date: Tue, 17 Dec 2013 16:31:23 +0100 Subject: [FreeVMS] build problem In-Reply-To: References: <523206CD.3060306@systella.fr> <52AC60B8.1050103@systella.fr> <52AD8EEE.7050703@systella.fr> <52ADD148.5080906@systella.fr> <52AEC965.9080700@systella.fr> <52AEE94E.9010305@systella.fr> <52B0172D.8090104@systella.fr> <52B06761.40101@systella.fr> Message-ID: <52B06E4B.6070002@systella.fr> Alessandro Sangiuliano a ?crit : > > Il 17/12/2013 16:01, BERTRAND Jo?l ha scritto: >> 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 >> >> > I'm using gcc-4.7-3 to compile all the system. > > Why kickstart is not able to launch l4? > I don't know. If I build L4 with gcc 4.7, it works. With gcc 4.8, it doesn't. I'll investifate. JKB From alex22_7 at hotmail.com Tue Dec 17 16:33:15 2013 From: alex22_7 at hotmail.com (Alessandro Sangiuliano) Date: Tue, 17 Dec 2013 16:33:15 +0100 Subject: [FreeVMS] build problem In-Reply-To: <52B06BB6.10100@hotmail.com> References: <523206CD.3060306@systella.fr> <52AC60B8.1050103@systella.fr> <52AD8EEE.7050703@systella.fr> <52ADD148.5080906@systella.fr> <52AEC965.9080700@systella.fr> <52AEE94E.9010305@systella.fr> <52B0172D.8090104@systella.fr> <52B06761.40101@systella.fr> <52B06BB6.10100@hotmail.com> Message-ID: Il 17/12/2013 16:20, Alessandro Sangiuliano ha scritto: > > Il 17/12/2013 16:01, BERTRAND Jo?l ha scritto: >> 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 I'm using gcc-4.7 to compile all the system. Why kickstart is not able to launch l4? (Sorry, forgot again to CC the mail, I changed the mailer, seems it can't add automatically the CC) From joel.bertrand at systella.fr Sun Dec 22 17:00:14 2013 From: joel.bertrand at systella.fr (=?ISO-8859-1?Q?BERTRAND_Jo=EBl?=) Date: Sun, 22 Dec 2013 17:00:14 +0100 Subject: [FreeVMS] L4Ka does not boot if built by gcc 4.8 Message-ID: <52B70C8E.6000805@systella.fr> Hello, FreeVMS is running as a roottask over L4Ka. I haven't built a new microkernel for my patch to build L4Ka with gcc 4.7. Last week, Alessandro Sangiuliano has reported on FreeVMS mailing list that L4Ka does not work as expected when its build with gcc 4.8. Thus, I have tried to build L4 with gcc 4.8. Without any result. With the same options, L4Ka runs as expected when it is built by gcc 4.7 and does not when it is built by gcc 4.8. Just after kickstart, I obtain : fatal: Trying to execute code outside RAM or ROM at 0x00000000c062e730 For information : riemann:[~/openvms/mnt/boot] > readelf -l x86-kernel-gcc-48 Type de fichier ELF est EXEC (fichier ex?cutable) Point d'entr?e 0xd1a000 Il y a 6 en-t?tes de programme, d?butant ? l'adresse de d?calage64 En-t?tes de programme: Type D?calage Adr.virt Adr.phys. Taille fichier Taille m?moire Fanion Alignement LOAD 0x00000000000001a0 0xffffffffc0600000 0x0000000000600000 0x0000000000050580 0x0000000000050580 RWE 20 LOAD 0x0000000000050720 0xffffffffc0800000 0x0000000000800000 0x0000000000000903 0x0000000000000903 R E 10 LOAD 0x0000000000052000 0xffffffffc0a00000 0x0000000000a00000 0x00000000000051b4 0x00000000000051b4 RW 1000 LOAD 0x0000000000058000 0xffffffffc0c00000 0x0000000000c00000 0x0000000000019a50 0x0000000000019a50 RWE 1000 LOAD 0x0000000000072000 0x0000000000d1a000 0x0000000000d1a000 0x0000000000008dd8 0x0000000000008ee0 RWE 1000 GNU_STACK 0x0000000000000000 0x0000000000000000 0x0000000000000000 0x0000000000000000 0x0000000000000000 RWE 10 Section ? la projection de segement: Sections de segment... 00 .text .text._ZN9x86_mmu_t13has_long_modeEv .text.startup .text._Z19__tbuf_record_eventmmPKcz .text._ZN5tcb_t16init_saved_stateEv .text._ZN13exregs_ctrl_t6stringEv .text._Z15get_cpu_mailboxt .text._Z12xcpu_requesttPFvP14cpu_mb_entry_tEP5tcb_tmmmmmmmm .text._ZN15hs_sched_ktcb_t16delay_preemptionEP5tcb_t .text._ZN11scheduler_t8scheduleEv .text._ZN11scheduler_t8scheduleEP5tcb_th .text._ZN14thread_state_t6stringEv .text._ZN10spinlock_t4lockEv .text._ZN5tcb_t17get_saved_partnerEm .text._ZN5tcb_t6get_mrEm .text._ZN5tcb_t6set_mrEmm .text._Z12xcpu_requesttPFvP14cpu_mb_entry_tEP5tcb_tmmm .text._ZN14hs_scheduler_t15dequeue_timeoutEP5tcb_t .text._ZN12sched_ktcb_t11set_timeoutE6time_t .text._ZN11scheduler_t8scheduleEP5tcb_tS1_h .text._ZN14hs_scheduler_t15enqueue_timeoutEP5tcb_t .text._ZN13smp_requeue_t12enqueue_headEP5tcb_t .text._ZN5tcb_t7set_cpuEt .rodata .kip 01 .syscalls 02 .cpulocal 03 .data .kdebug .sets 04 .init .bss._ZZN14tbuf_handler_t9dump_tbufEmmmbE6tb_str 05 riemann:[~/openvms/mnt/boot] > Fault comes from .text._ZN9x86_mmu_t13has_long_modeEv address entry point. When kernel is built with gcc 4.7, executable does not contains this segment. I don't understand why gcc produces this segment as this function is inlined in source code. Any idea ? Best regards, JKB