Re: [seL4] Unable to Run seL4test

2018-04-12 Thread Amit Goyal

Hi Adrian,

Yes, I understand that simulate-ia32 calls qemu-system-i386 ad I am 
running it on Intel i7 Processor on Ubuntu 16.04 LTS. Following are the 
versioning details of my system that you require:


1. gcc (Ubuntu 5.4.0-6ubuntu1~16.04.9) 5.4.0 20160609
2. GNU ld (GNU Binutils for Ubuntu) 2.26.1
3. QEMU emulator version 2.5.0 (Debian 1:2.5+dfsg-5ubuntu10.24)

So, I am running exactly on the same platform as yours.

--
Thanks and Regards,
Amit Goyal

On 2018-04-11 09:32, adrian.da...@data61.csiro.au wrote:

Hi Amit,

Unfortunately I cannot reproduce this problem myself. Can you provide
your version of GCC, binutils and qemu (note that make simulate-ia32
calls qemu-system-i386). For myself I am testing with
gcc (Ubuntu 5.4.0-6ubuntu1~16.04.9) 5.4.0 20160609
GNU ld (GNU Binutils for Ubuntu) 2.26.1
QEMU emulator version 2.5.0 (Debian 1:2.5+dfsg-5ubuntu10.24)

Adrian

On Wed 11-Apr-2018 1:46 AM, Amit Goyal wrote:

Hi Kofi,

I am getting the attached error (Error Log.txt) while running 
seL4test. Earlier it

used to run perfectly fine.

I am running the following commands:
$ repo init -u https://github.com/seL4/sel4test-manifest.git
$ repo sync
$ make clean
$ make ia32_simulation_release_xml_defconfig
$ make -j libmuslc && make
$ make simulate-ia32

Can you please look into this.



___
Devel mailing list
Devel@sel4.systems
https://sel4.systems/lists/listinfo/devel





___
Devel mailing list
Devel@sel4.systems
https://sel4.systems/lists/listinfo/devel


Re: [seL4] Unable to Run seL4test

2018-04-10 Thread Adrian.Danis
Hi Amit,

Unfortunately I cannot reproduce this problem myself. Can you provide your 
version of GCC, binutils and qemu (note that make simulate-ia32 calls 
qemu-system-i386). For myself I am testing with
gcc (Ubuntu 5.4.0-6ubuntu1~16.04.9) 5.4.0 20160609
GNU ld (GNU Binutils for Ubuntu) 2.26.1
QEMU emulator version 2.5.0 (Debian 1:2.5+dfsg-5ubuntu10.24)

Adrian

On Wed 11-Apr-2018 1:46 AM, Amit Goyal wrote:
> Hi Kofi,
> 
> I am getting the attached error (Error Log.txt) while running seL4test. 
> Earlier it
> used to run perfectly fine.
> 
> I am running the following commands:
> $ repo init -u https://github.com/seL4/sel4test-manifest.git
> $ repo sync
> $ make clean
> $ make ia32_simulation_release_xml_defconfig
> $ make -j libmuslc && make
> $ make simulate-ia32
> 
> Can you please look into this.
> 
> 
> 
> ___
> Devel mailing list
> Devel@sel4.systems
> https://sel4.systems/lists/listinfo/devel
> 
___
Devel mailing list
Devel@sel4.systems
https://sel4.systems/lists/listinfo/devel


[seL4] Unable to Run seL4test

2018-04-10 Thread Amit Goyal

Hi Kofi,

I am getting the attached error (Error Log.txt) while running seL4test. 
Earlier it

used to run perfectly fine.

I am running the following commands:
$ repo init -u https://github.com/seL4/sel4test-manifest.git
$ repo sync
$ make clean
$ make ia32_simulation_release_xml_defconfig
$ make -j libmuslc && make
$ make simulate-ia32

Can you please look into this.

--
Thanks and Regards,
Amit Goyalmake simulate-ia32
qemu-system-i386 \
-m 512 -nographic -kernel images/kernel-ia32-pc99 \
-initrd images/sel4test-driver-image-ia32-pc99
2 untypeds of size 12
4 untypeds of size 13
5 untypeds of size 14
3 untypeds of size 15
4 untypeds of size 16
4 untypeds of size 17
5 untypeds of size 18
5 untypeds of size 19
4 untypeds of size 20
3 untypeds of size 21
3 untypeds of size 22
4 untypeds of size 23
2 untypeds of size 24
3 untypeds of size 25
3 untypeds of size 26
3 untypeds of size 27
1 untypeds of size 28
6 untypeds of size 29
Switching to a safer, bigger stack... 
seL4 Test
=

vka_alloc_object_at_maybe_dev@object.h:59 Failed to allocate object of size 
2147483648, error 1

vka_alloc_object_at_maybe_dev@object.h:59 Failed to allocate object of size 
1073741824, error 1

vka_alloc_object_at_maybe_dev@object.h:59 Failed to allocate object of size 
536870912, error 1

vka_alloc_object_at_maybe_dev@object.h:59 Failed to allocate object of size 
268435456, error 1

vka_alloc_object_at_maybe_dev@object.h:59 Failed to allocate object of size 
134217728, error 1

vka_alloc_object_at_maybe_dev@object.h:59 Failed to allocate object of size 
67108864, error 1

vka_alloc_object_at_maybe_dev@object.h:59 Failed to allocate object of size 
33554432, error 1

vka_alloc_object_at_maybe_dev@object.h:59 Failed to allocate object of size 
16777216, error 1

vka_alloc_object_at_maybe_dev@object.h:59 Failed to allocate object of size 
8388608, error 1

vka_alloc_object_at_maybe_dev@object.h:59 Failed to allocate object of size 
4194304, error 1

vka_alloc_object_at_maybe_dev@object.h:59 Failed to allocate object of size 
2097152, error 1

vka_alloc_object_at_maybe_dev@object.h:59 Failed to allocate object of size 
1048576, error 1

vka_alloc_object_at_maybe_dev@object.h:59 Failed to allocate object of size 
524288, error 1

vka_alloc_object_at_maybe_dev@object.h:59 Failed to allocate object of size 
262144, error 1

vka_alloc_object_at_maybe_dev@object.h:59 Failed to allocate object of size 
131072, error 1

vka_alloc_object_at_maybe_dev@object.h:59 Failed to allocate object of size 
65536, error 1

vka_alloc_object_at_maybe_dev@object.h:59 Failed to allocate object of size 
32768, error 1

vka_alloc_object_at_maybe_dev@object.h:59 Failed to allocate object of size 
16384, error 1

vka_alloc_object_at_maybe_dev@object.h:59 Failed to allocate object of size 
8192, error 1

vspace_reserve_range_at@vspace.h:645 vspace is NULL
create_reservations@elf.c:254 Failed to make reservation: 0x8048000, 512000
elf_reserve_regions_in_vspace@elf.c:447 Failed to create reservations
sel4utils_elf_reserve@elf.c:482 Failed to reserve regions
Starting test suite sel4test
Starting test 0: Test that there are tests
Starting test 1: SYSCALL
Starting test 2: SYSCALL0001
Starting test 3: SYSCALL0002
Starting test 4: SYSCALL0003
Starting test 5: SYSCALL0004
Starting test 6: SYSCALL0005
Starting test 7: SYSCALL0006
Starting test 8: SYSCALL0010
Starting test 9: SYSCALL0011
Starting test 10: SYSCALL0012
Starting test 11: SYSCALL0013
Starting test 12: SYSCALL0014
Starting test 13: SYSCALL0015
Starting test 14: SYSCALL0016
Starting test 15: SYSCALL0017
Starting test 16: BIND0001
sel4utils_copy_path_to_process@process.c:136 Failed to copy cap

Starting test 17: BIND0002
sel4utils_copy_path_to_process@process.c:136 Failed to copy cap

Starting test 18: BIND0003
sel4utils_copy_path_to_process@process.c:136 Failed to copy cap

Starting test 19: BIND0004
sel4utils_copy_path_to_process@process.c:136 Failed to copy cap

Starting test 20: CANCEL_BADGED_SENDS_0001
sel4utils_copy_path_to_process@process.c:136 Failed to copy cap

Starting test 21: CANCEL_BADGED_SENDS_0002
sel4utils_copy_path_to_process@process.c:136 Failed to copy cap

Starting test 22: CNODEOP0001
sel4utils_copy_path_to_process@process.c:136 Failed to copy cap

Starting test 23: CNODEOP0002
sel4utils_copy_path_to_process@process.c:136 Failed to copy cap

Starting test 24: CNODEOP0003
sel4utils_copy_path_to_process@process.c:136 Failed to copy cap

Starting test 25: CNODEOP0004
sel4utils_copy_path_to_process@process.c:136 Failed to copy cap

Starting test 26: CNODEOP0005
sel4utils_copy_path_to_process@process.c:136 Failed to copy cap

Starting test 27: CNODEOP0006
sel4utils_copy_path_to_process@process.c:136 Failed to copy cap

Starting test 28: CNODEOP0007
sel4utils_copy_path_to_process@process.c:136 Failed to copy cap

Starting test 29: CNODEOP0008
sel4utils_copy_path_to_process@process.c:136 Failed to copy cap

Starting test 30: CNODEOP0009
sel4utils_copy_path_to_process@p