On Fri, Feb 18, 2022 at 6:41 PM <[email protected]> wrote: > > Hi guys, > > I was trying to boot a custom Linux 4.9.302 Kernel and fot this horrible > message: > > "libsel4muslcsys: Error attempting syscall 215" > > hugo@dev:~/seL4/sel4webserver_hugusmaximus_fork/build$ sudo ./simulate > --extra-qemu-args="-netdev tap,id=mynet0,ifname=tap0,script=no,downscript=no > -device > virtio-net,netdev=mynet0,mac=52:55:00:d1:55:01,disable-modern=on,disable-legacy=off" > [sudo] contraseña para hugo: > ./simulate: qemu-system-aarch64 -machine > virt,virtualization=on,highmem=off,secure=off -cpu cortex-a53 -nographic -m > size=2048 -netdev tap,id=mynet0,ifname=tap0,script=no,downscript=no -device > virtio-net,netdev=mynet0,mac=52:55:00:d1:55:01,disable-modern=on,disable-legacy=off > -kernel images/capdl-loader-image-arm-qemu-arm-virt > ELF-loader started on CPU: ARM Ltd. Cortex-A53 r0p4 > paddr=[61bf9000..631120af] > No DTB passed in from boot loader. > Looking for DTB in CPIO archive...found at 61d3a2b8. > Loaded DTB from 61d3a2b8. > paddr=[60243000..60244fff] > ELF-loading image 'kernel' to 60000000 > paddr=[60000000..60242fff] > vaddr=[ff8060000000..ff8060242fff] > virt_entry=ff8060000000 > ELF-loading image 'capdl-loader' to 60245000 > paddr=[60245000..617fdfff] > vaddr=[400000..19b8fff] > virt_entry=408f38 > Enabling hypervisor MMU and paging > Jumping to kernel-image entry point... > > Bootstrapping kernel > Warning: Could not infer GIC interrupt target ID, assuming 0. > Booting all finished, dropped to user space > <<seL4(CPU 0) [decodeUntypedInvocation/205 T0xff80bf815400 "rootserver" > @4006f8]: Untyped Retype: Insufficient memory (1 * 2097152 bytes needed, 0 > bytes available).>> > Loading Linux: 'linux' dtb: 'linux-dtb' > [email protected]:655 module name: map_frame_hack > [email protected]:655 module name: init_ram > [email protected]:655 module name: cross_vm_connections > libsel4muslcsys: Error attempting syscall 215 > libsel4muslcsys: Error attempting syscall 215 > [email protected]:266 Failed to find any untyped capable of > creating an object at address 0x8020000 > > as this is purely an seL4 error message (musl libc seL4 code?) then I would > appreciate any hint about what can be going on. >
Hi Hugo, libsel4muslcsys is a library that emulates some system calls for our fork of musl libc via intercepting them and translating them into a function call. So that error is referring to an unimplemented system call being encountered. The return value the caller will see would be ENOSYS. In this case the unimplemented syscall is munmap. The mmap implementation that libsel4muslcsys provides is very basic and only supports anonymous memory allocation without freeing. > P.S.: I have run my seL4 qemu aarch64 with several Linux kernel versions and > never had this problem until now. > _______________________________________________ > Devel mailing list -- [email protected] > To unsubscribe send an email to [email protected] _______________________________________________ Devel mailing list -- [email protected] To unsubscribe send an email to [email protected]
