users

users@lists.genode.org

2285 discussions

import_from_depot size limitation
by Duss Pirmin 06 Aug '19

06 Aug '19

Hello Genodians Is there a limit to the size (number of bytes or number of files) that can be added via import_from_depot (ARCH: imx6, KERNEL: hw)? I had a problem with a run script that sometimes hung (mkfs never completing) or sometimes crashed in different components (ip pointing to Genode::ipc_reply_wait() in ld.lib.so) after upgrading from 19.05 to 19.07. To debug the error I created a small version and step by step increased its size until it was identical to the one with the error. The last difference I found was that the script with the error imported more depot archives. After reducing the list of imported archives the run script now works well. What I think is even stranger, at first I bisected the problem with the original run script. This resulted in commit ac0ecdf855f61 triggering the problem. But as non of my other run scripts showed this kind of error, I suspected that it only uncovered a hidden error in my run script. Could it be, that this is related to the size of the resulting image (about 50MiB for image.elf and 26MiB for uImage)? Best regards, Pirmin

2 4

mystique error during app load
by Alexander Tormasov 06 Aug '19

06 Aug '19

I write some sample application to run inside Genode over seL4 inside VM with 4Gb. and, I see a problem with LD, saying something with memory (in the end of log): [init -> test-go] Error: LD: exception during program load: 'Genode::Region_map::Region_conflict' any ideas what cause and how to get mode info? I suspect again incorrect config in runscript, while similar test-cache app runs ok thanks! <config> <parent-provides> <service name="LOG"/> <service name="CPU"/> <service name="PD"/> <service name="ROM"/> <service name="IO_MEM"/> </parent-provides> <default-route> <any-service> <parent/> </any-service> </default-route> <default caps="1000"/> <start name="test-go"> <resource name="RAM" quantum="128M"/> </start> </config> Bender: Hello World. Boot config: parsing cmdline 'sel4 disable_iommu' Boot config: console_port = 0x3f8 Boot config: debug_port = 0x3f8 Boot config: disable_iommu = true module #0: start=0xfd29000 end=0xffff330 size=0x2d6330 name='image.elf' Physical Memory Region from 0 size 9fc00 type 1 Physical Memory Region from 9fc00 size 400 type 2 Physical Memory Region from dc000 size 24000 type 2 Physical Memory Region from 100000 size afeec000 type 1 Adding physical memory region 0x100000-0xaffec000 Physical Memory Region from affec000 size 2000 type 2 Physical Memory Region from affee000 size d000 type 3 Physical Memory Region from afffb000 size 5000 type 4 Physical Memory Region from fec00000 size 1000 type 2 Physical Memory Region from fed00000 size 1000 type 2 Physical Memory Region from fed04000 size 1000 type 2 Physical Memory Region from fee00000 size 1000 type 2 Physical Memory Region from ffc00000 size 400000 type 2 Physical Memory Region from 1000000000 size 50000000 type 1 Adding physical memory region 0x100000000-0x150000000 Got framebuffer info in multiboot2. Current video mode is at physical address=b0000000 pitch=10240 resolution=2560x1600@32 type=1 Detected 1 boot module(s): ***WARNING*** SKIM window not enabled, this machine is probably vulernable to Meltdown (https://www.meltdownattack.com), consider enabling Kernel loaded to: start=0x200000 end=0xaa5000 size=0x8a5000 entry=0x201209 ACPI: RSDT paddr=0xaffee000 ACPI: RSDT vaddr=0xaffee000 ACPI: FADT paddr=0xaffee040 ACPI: FADT vaddr=0xaffee040 ACPI: FADT flags=0xd ACPI: MADT paddr=0xaffee200 ACPI: MADT vaddr=0xaffee200 ACPI: MADT apic_addr=0xfee00000 ACPI: MADT flags=0x1 ACPI: MADT_APIC apic_id=0x0 ACPI: MADT_IOAPIC ioapic_id=0 ioapic_addr=0xfec00000 gsib=0 ACPI: MADT_ISO bus=0 source=0 gsi=2 flags=0x0 ACPI: MADT_ISO bus=0 source=14 gsi=14 flags=0x4 ACPI: MADT_ISO bus=0 source=15 gsi=15 flags=0x4 ACPI: 1 CPU(s) detected ELF-loading userland images from boot modules: size=0x1140000 v_entry=0x2000018 v_start=0x2000000 v_end=0x3140000 p_start=0x10000000 p_end=0x11140000 Moving loaded userland images to final location: from=0x10000000 to=0xaa5000 size=0x1140000 Starting node #0 with APIC ID 0 Mapping kernel window is done vt-x: not supported Booting all finished, dropped to user space :phys_mem_16k: Allocator 0x2fe7730 dump: Block: [0000000000200000,0000000000240000) size=256K avail=256K max_avail=256K => mem_size=262144 (0 MB) / mem_avail=262144 (0 MB) Warning: memory in range [0000000100000000,0000000140000000) is unavailable (due to limited untyped cnode range) Warning: memory in range [0000000140000000,0000000148000000) is unavailable (due to limited untyped cnode range) Warning: memory in range [0000000148000000,000000014c000000) is unavailable (due to limited untyped cnode range) Warning: memory in range [000000014e000000,000000014f000000) is unavailable (due to limited untyped cnode range) Warning: memory in range [000000014f000000,000000014f400000) is unavailable (due to limited untyped cnode range) Warning: memory in range [000000014f400000,000000014f600000) is unavailable (due to limited untyped cnode range) Warning: memory in range [000000014f600000,000000014f700000) is unavailable (due to limited untyped cnode range) Warning: memory in range [000000014f700000,000000014f780000) is unavailable (due to limited untyped cnode range) Warning: memory in range [000000014f780000,000000014f7c0000) is unavailable (due to limited untyped cnode range) Warning: memory in range [000000014f7e0000,000000014f7e4000) is unavailable (due to limited untyped cnode range) Warning: memory in range [000000014f7e4000,000000014f7e5000) is unavailable (due to limited untyped cnode range) Warning: device memory in range [0000000150000000,0000000160000000) is unavailable (due to limited untyped cnode range) Warning: device memory in range [0000000160000000,0000000180000000) is unavailable (due to limited untyped cnode range) Warning: device memory in range [0000000180000000,0000000200000000) is unavailable (due to limited untyped cnode range) Warning: device memory in range [0000000200000000,0000000400000000) is unavailable (due to limited untyped cnode range) Warning: device memory in range [0000000400000000,0000000800000000) is unavailable (due to limited untyped cnode range) Warning: device memory in range [0000000800000000,0000001000000000) is unavailable (due to limited untyped cnode range) Warning: device memory in range [0000001000000000,0000002000000000) is unavailable (due to limited untyped cnode range) Warning: device memory in range [0000002000000000,0000004000000000) is unavailable (due to limited untyped cnode range) Warning: device memory in range [0000004000000000,0000008000000000) is unavailable (due to limited untyped cnode range) Warning: device memory in range [0000008000000000,0000408000000000) is unavailable (due to limited untyped cnode range) Warning: device memory in range [0000408000000000,0000608000000000) is unavailable (due to limited untyped cnode range) Warning: device memory in range [0000608000000000,0000708000000000) is unavailable (due to limited untyped cnode range) Warning: device memory in range [0000708000000000,0000788000000000) is unavailable (due to limited untyped cnode range) Warning: device memory in range [0000788000000000,00007c8000000000) is unavailable (due to limited untyped cnode range) Warning: device memory in range [00007c8000000000,00007e8000000000) is unavailable (due to limited untyped cnode range) Warning: device memory in range [00007e8000000000,00007f8000000000) is unavailable (due to limited untyped cnode range) Warning: device memory in range [00007f8000000000,0000800000000000) is unavailable (due to limited untyped cnode range) virtual address layout of core: overall [0000000000002000,0000000200000000) core image [0000000002000000,0000000003140000) ipc buffer [0000000003140000,0000000003141000) boot_info [0000000003141000,0000000003143000) stack area [0000000040000000,0000000050000000) Warning: need physical memory, but Platform object not constructed yet Warning: need physical memory, but Platform object not constructed yet Warning: need physical memory, but Platform object not constructed yet boot module 'config' (372 bytes) boot module 'test-go' (10088 bytes) boot module 'ld.lib.so' (1002416 bytes) boot module 'init' (345536 bytes) Warning: need physical memory, but Platform object not constructed yet Genode sculpt-19.07 <local changes> 2721 MiB RAM and 261141 caps assigned to init Warning: void Genode::Rpc_cap_factory::free(Genode::Native_capability) not implemented - resources leaked: 0x1 Warning: void Genode::Rpc_cap_factory::free(Genode::Native_capability) not implemented - resources leaked: 0x2 Warning: void Genode::Rpc_cap_factory::free(Genode::Native_capability) not implemented - resources leaked: 0x4 Warning: void Genode::Rpc_cap_factory::free(Genode::Native_capability) not implemented - resources leaked: 0x8 [init -> test-go] Error: LD: exception during program load: 'Genode::Region_map::Region_conflict' Kernel: Thread 'ep' died because of an uncaught exception [init -> test-go] Error: Uncaught exception of type 'Genode::Region_map::Region_conflict' [init -> test-go] Warning: abort called - thread: ep Warning: void Genode::Rpc_cap_factory::free(Genode::Native_capability) not implemented - resources leaked: 0x10 Warning: void Genode::Rpc_cap_factory::free(Genode::Native_capability) not implemented - resources leaked: 0x20 [init] child "test-go" exited with exit value 1 Sincerely, Alexander

3 4

Re: Sculpt - Boot from USB and Save configurations for a reboot
by Nanfang Hu 31 Jul '19

31 Jul '19

I have used USB to boot up Sculpt demo. I have a problem to use USB to add more components since the system keeps complaining downloading error. Instead I am using RAM and adding more components to Sculpt. How to save Scuplt configurations for system reboot. Thanks Nanfang On Mon, Jul 29, 2019 at 5:24 PM Nanfang Hu <nhu2000(a)gmail.com> wrote: > I have used USB to boot up Sculpt demo. > > I have a problem to use USB to add more components since the system keeps > complaining downloading error. Instead I am using RAM and adding more > components to Sculpt. > > How to save Scuplt configurations for system reboot. > > Thanks > Nanfang > >

2 1

Dynamic linker for child components | Genode 16.08 with Fiasco.OC
by Fesl, Matthias 30 Jul '19

30 Jul '19

Hello everyone, I am struggling with starting a component as a child from another component. At runtime the following error appears: Error: attempt to start dynamic executable without dynamic linker When I am starting the child component directly from init, it works. Does anyone know where the error could come from or where I need to start searching? Tank you in advance, with best regards, Matthias Fesl

1 0

Dynamic linker for child components | Genode 16.08 with Fiasco.OC
by Fesl, Matthias 30 Jul '19

30 Jul '19

2 1

Re: Issues to build Sculpt with Sel4 kernel
by Alexander Boettcher 29 Jul '19

29 Jul '19

Hello, On 29.07.19 01:31, Nanfang Hu wrote: > I am trying to build Sculpt with Sel4 kernel. > Sculpt OS is not tested with seL4 and is not supposed to get far. > sudo make -C build/x86_64 run/sculpt KERNEL=sel4 BOARD=pc Please don't use sudo - our tooling support is supposed to work without root rights. (If you nevertheless need root rights, please tell us which tool requires it). > > I run into error, "Could not allocate block in ext2 filesystem" Either increase the image size to some fixed value in your build/x86_64/etc/build.conf, something like: RUN_OPT += --image-disk-size 64 or increase the value of the ext2_overhead variable in tool/run/image/disk Cheers, -- Alexander Boettcher Genode Labs https://www.genode-labs.com - https://www.genode.org Genode Labs GmbH - Amtsgericht Dresden - HRB 28424 - Sitz Dresden Geschäftsführer: Dr.-Ing. Norman Feske, Christian Helmuth

1 0

Issues to build Sculpt with Sel4 kernel
by Nanfang Hu 28 Jul '19

28 Jul '19

I am trying to build Sculpt with Sel4 kernel. sudo make -C build/x86_64 run/sculpt KERNEL=sel4 BOARD=pc I run into error, "Could not allocate block in ext2 filesystem" It seems that I have increased file system size. Where is the place to make that change? Thanks Nanfang

1 0

Re: users Digest, Vol 15, Issue 17
by Nanfang Hu 28 Jul '19

28 Jul '19

Thanks, Johanne. It works. On Thu, Jul 25, 2019 at 6:00 PM <users-request(a)lists.genode.org> wrote: > Send users mailing list submissions to > users(a)lists.genode.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.genode.org/listinfo/users > or, via email, send a message with subject or body 'help' to > users-request(a)lists.genode.org > > You can reach the person managing the list at > users-owner(a)lists.genode.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of users digest..." > > > Today's Topics: > > 1. Re: Fwd: Issue for run demo (Johannes Kliemann) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Thu, 25 Jul 2019 10:11:24 +0200 > From: Johannes Kliemann <kliemann(a)componolit.com> > To: users(a)lists.genode.org > Subject: Re: Fwd: Issue for run demo > Message-ID: <4361356.Lc3VtfIeQD@aamon> > Content-Type: text/plain; charset="utf-8" > > Hi Nanfang, > > I had that issue, too. On the newest Genode you also need to select a > board to > run on which is "linux" for Linux. So you could try > > "make KERNEL=linux BOARD=linux run/demo" > > Regards, > Johannes > > > Hi > > > > I am a newbie to genode and need help to set up. > > > > I have cloned and compiled genode. > > > > When I try to run demo by command "make KERNEL=linux run/demo", I had an > > error, see attached. > > > > I have ubuntu 16.04 and IBM Thinkpad 520. > > > > Thanks > > Nanfang > >

1 0

Fwd: Issue for run demo
by Nanfang Hu 25 Jul '19

25 Jul '19

Hi I am a newbie to genode and need help to set up. I have cloned and compiled genode. When I try to run demo by command "make KERNEL=linux run/demo", I had an error, see attached. I have ubuntu 16.04 and IBM Thinkpad 520. Thanks Nanfang

2 1

Can QT-based "textedit" run successfully on Rpi 3 B+ ?
by kimberly nNA 22 Jul '19

22 Jul '19

Dear Genode team, I am Kimberly. I modified and added "textedit" on demo.run The link below is about the complete content of demo.run, textedit.config, runtime log, and also a result graph. https://docs.google.com/document/d/1gtQJOXG3IK2_h5xV5CLI1zy54Vil_Xu6HSJ3My6… The genode version is https://github.com/tomga/genode/tree/rpi3bplus_19.02 I tried this commands : $ ./tool/create_builddir *rpi3bplus* $ make run/demo KERNEL=hw This case successfully run on Rpi3 B+ But it had some errors when running textedit. I used USB to TTL Serial Cable to see the runtime log : =========================================== ... [init -> launchpad] starting textedit with quota 177873K [init -> launchpad] using unique child name "textedit" [init -> launchpad] Warning: textedit: service File_system not available [init -> launchpad -> textedit] Error: File_system-session creation failed (ram_quota=163840, cap_quota=12, tx_buf_size=131072, label="rw", root="", writeable=1) [init -> launchpad -> textedit] Error: failed to create <fs> VFS node [init -> launchpad -> textedit] Error: label="rw" ... ============================================ because of the errors, I couldn't "save" a new file. I wrote the config of "ram_fs" in demo.run : <start name="ram_fs"> <resource name="RAM" quantum="10M"/> <provides><service name="File_system"/></provides> <config>  <policy label="textedit -> root" root="/" /> </config> </start> something wrong with the node ? I am not familiar with writing the 'policy'. Thanks a lot ! 😊

2 1

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

users