users

users@lists.genode.org

7 participants
2332 discussions

An ISO Image Related Remark
by Martin Vahi 22 Aug '17

22 Aug '17

Dear whoever reads this, The only purpose of my current letter is to note that the GenodeOS gets beaten by the MINIX3 at getting newcomers on-board due to the fact that the MINIX3 has an ISO image that people can install to VirtualBox and the GenodeOS lacks such downloadable image. Actually, I once obtained one such GenodeOS image in 2010, but today is 2017. I haven't exhaustively tested the GenodeOS book, but at first glance it seems that the book assumes, at least from paths' point of view, a person is required to run a copy of the GenodeOS before building the GenodeOS. For example, after cloning the https://github.com/genodelabs/genode and following instructions on page 24 of the 2017_08_22 version of the (Chapter 2.3, "Using the build system") http://genode.org/documentation/genode-foundations-17-05.pdf namely ./tool/create_builddir x86_64 cd ./build/x86_64 nice -n20 make I get an error message ---citation---start---- /bin/bash: /usr/local/genode-gcc/bin/genode-x86-g++: No such file or directory ---citation---end------ Obviously I AM NOT running GenodeOS, if I'm a newcomer and want to try out the GenodeOS for the very first time. As I wasn't given an ISO image to to try the GenodeOS, then my next step is to follow the official instructions, which in this case is to build the GenodeOS myself. Yet, the build system assumes that I'm building the GenodeOS WHILE RUNNING GENODEOS, because hardly any Linux or BSD distribution has a path like /usr/local/genode-gcc available by default. A chicken and an egg. There's a need for a grown up bird to lay the egg, but if the whole path of software-/bio-evolution is to be skipped, then a lamb must be able to give birth to a non-mammal, a lizard, a bird, a fish, to make fast bootstrapping possible, not to mention "The Alien Option": https://youtu.be/zCqoA-FGgoc?t=20s Thank You for reading my comment :-)

2 1

Fwd: Re: create_uboot dependencies?
by Martin Stein 18 Aug '17

18 Aug '17

Hi Steven, Thank you for this hint! It's obviously a bug in the 'create_uboot' tool. The tool uses the Genode tool chain and since the last update of this tool cain I didn't test whether they're still fine with each other. One quick work-around for you would be to download the 16.05 toolchain [1], unpack it to an individual directory (no 'P' flag) [2], and adapt your create_uboot to use the other tool chain [3]. I will have a more detailed look at the problem these days and provide a long-term fix as soon as possible. I hope this helped? Cheers, Martin [1] https://sourceforge.net/projects/genode/files/genode-toolchain/16.05/ [2] tar xfj genode-toolchain-<version>-<arch>.tar.bz2 [3] diff --git a/tool/create_uboot b/tool/create_uboot index f52d8e0..0e6490c 100755 --- a/tool/create_uboot +++ b/tool/create_uboot @@ -59,7 +59,7 @@ endif UBOOT_MAKE := \ $(VERBOSE)make ARCH=$(ARCH) \ - CROSS_COMPILE=/usr/local/genode-gcc/bin/genode-$(ARCH)- \ + CROSS_COMPILE=<YOUR_GENODE_GCC_16_05_DIR>/bin/genode-$(ARCH)- \ O=$(UBOOT_BUILD_DIR) \ -j4 Am 16.08.2017 um 19:53 schrieb Steven Harp: > > In genode 17.05, I'm having difficulties with tool "create_uboot". > Perhaps there are some preparatory steps or usage guidelines > that I am missing.... The error manifests as (below). > Any suggestions about what might be amiss? (Goal is preparing an > image for wand quad.) > > > $ ~/genode/tool/create_uboot wand_quad > Already on 'genode_wand_quad' > Your branch is up-to-date with 'origin/genode_wand_quad'. > Building U-Boot config... > make[1]: Entering directory '/home/user/genode/contrib/uboot' > make[2]: Entering directory '/home/user/genode/contrib/uboot/build/wand_quad' > GEN ./Makefile > # > # configuration written to .config > # > make[2]: Leaving directory '/home/user/genode/contrib/uboot/build/wand_quad' > make[1]: Leaving directory '/home/user/genode/contrib/uboot' > Building U-Boot images... > make[1]: Entering directory '/home/user/genode/contrib/uboot/build/wand_quad' > GEN ./Makefile > scripts/kconfig/conf --silentoldconfig Kconfig > CHK include/config.h > GEN include/autoconf.mk > GEN include/autoconf.mk.dep > GEN spl/include/autoconf.mk > In file included from /home/user/genode/contrib/uboot/include/linux/compiler.h:54:0, > from /home/user/genode/contrib/uboot/include/linux/byteorder/little_endian.h:12, > from /home/user/genode/contrib/uboot/arch/arm/include/asm/byteorder.h:29, > from /home/user/genode/contrib/uboot/include/compiler.h:125, > from /home/user/genode/contrib/uboot/include/image.h:19, > from /home/user/genode/contrib/uboot/include/common.h:82: > /home/user/genode/contrib/uboot/include/linux/compiler-gcc.h:114:30: fatal error: linux/compiler-gcc6.h: No such file or directory > #include gcc_header(__GNUC__) > ^ > compilation terminated. > > ... Repeats ...

1 0

create_uboot dependencies?
by Steven Harp 16 Aug '17

16 Aug '17

In genode 17.05, I'm having difficulties with tool "create_uboot". Perhaps there are some preparatory steps or usage guidelines that I am missing.... The error manifests as (below). Any suggestions about what might be amiss? (Goal is preparing an image for wand quad.) $ ~/genode/tool/create_uboot wand_quad Already on 'genode_wand_quad' Your branch is up-to-date with 'origin/genode_wand_quad'. Building U-Boot config... make[1]: Entering directory '/home/user/genode/contrib/uboot' make[2]: Entering directory '/home/user/genode/contrib/uboot/build/wand_quad' GEN ./Makefile # # configuration written to .config # make[2]: Leaving directory '/home/user/genode/contrib/uboot/build/wand_quad' make[1]: Leaving directory '/home/user/genode/contrib/uboot' Building U-Boot images... make[1]: Entering directory '/home/user/genode/contrib/uboot/build/wand_quad' GEN ./Makefile scripts/kconfig/conf --silentoldconfig Kconfig CHK include/config.h GEN include/autoconf.mk GEN include/autoconf.mk.dep GEN spl/include/autoconf.mk In file included from /home/user/genode/contrib/uboot/include/linux/compiler.h:54:0, from /home/user/genode/contrib/uboot/include/linux/byteorder/little_endian.h:12, from /home/user/genode/contrib/uboot/arch/arm/include/asm/byteorder.h:29, from /home/user/genode/contrib/uboot/include/compiler.h:125, from /home/user/genode/contrib/uboot/include/image.h:19, from /home/user/genode/contrib/uboot/include/common.h:82: /home/user/genode/contrib/uboot/include/linux/compiler-gcc.h:114:30: fatal error: linux/compiler-gcc6.h: No such file or directory #include gcc_header(__GNUC__) ^ compilation terminated. ... Repeats ...

1 0

ACPI _PS0 failing with UNINITIALIZED_ARG
by Johannes Kliemann 16 Aug '17

16 Aug '17

Hi again, first, I have posted this question already on Stackoverflow [1] and Reddit [2] but forgot to put it on the mailing list. > I have a touchscreen controller (which is an I2C slave) that I need to enable via APCI. This should be done by calling the _PS0 ACPI method. I call this method by using AcpiEvaluateObject with no arguments and no return values. > > When calling this method on the parent object (I2C4), everything goes fine but calling it on the touch screen controller (TCS2), it fails. What also makes me wonder is that it returns AE_AML_UNINITIALIZED_ARG even though it doesn't take any args (according to the DSDT). > > Calling the _CRS method on the same object also works without any problems. I also looked into the Linux kernel source how they change ACPI power states and they use the exact same mechanism. It boils down to the use of acpi_evaluate_object in acpi_dev_pm_explicit_set which also seems to work on the touchscreen device. > > what am I missing to successfully enable the touchscreen device via ACPI? Is there something the Linux kernel is initializing implicitly (I couldn't find something like this)? The current workaround for this issue is to use the GPIO pins to enable the controller. But this isn't the desired way since it requires an additional GPIO driver that takes ~100 LOC and also a separate ACPI initialization for this driver. Besides that other functions that are needed to get initial parameters return errors. On the specific device I have the following examples: > \_SB_.I2C4.SSCN > \_SB_.I2C4.FMCN > \_SB_.I2C4.FPCN > \_SB_.I2C4.HSCN Similar things also happen on the GPIO device (\_SB_.GPO1). Regards, Johannes [1]: https://stackoverflow.com/questions/44382881/acpi-ps0-failing-with-uninitia… [2]: https://www.reddit.com/r/osdev/comments/6mtlv7/acpi_psx_function_returns_ae… DSDT: https://gist.github.com/jklmnn/15ed561202e04390e7bc366c0f803577#file-dsdt-d…

2 3

Receiving message written by writev() in multiple chunks
by Alexander Senier 16 Aug '17

16 Aug '17

Hi all, when using writev() on a TCP socket, I get a behavior that is unexpected, although it may OK by the specification. My test program is using the libc_lwip_loopback plugin. I create a TCP socket, bind it so some address/port and put it into listening mode. Then, I create another socket, connect to that port and write and IOVEC referencing 3 buffers using writev(). The buffers have a total length of 17 which is returned as a length by the writev(). When reading from the socket using recv(), I'd expect it to return 17 bytes with are identical with the content of the IOVEC. Instead, I need to perform two recv() calls, the first returning the first buffer of the IOVEC and the second returning the buffers 2 and 3 of the IOVEC concatenated. Find example code here [1]. As I said, this may be perfectly legal behavior. OTOH, Linux and Android behave as expected and there may be code relying on it. Any thoughts on this issue? Thanks! Cheers, Alex [1] https://github.com/senier/componolit/blob/issue16/src/test/mfe/writev_socke…

2 2

error on building tool_chain_rump
by Jan-Ralph Sroka 15 Aug '17

15 Aug '17

Hello everyone, following the release-notes 14.05 I try to build the tool_chain_rump. I am running Ubuntu 16.04 LTS. Maybe someone can point out my mistake or refer me to a file with instructions since i was not able to find one myself. I get the following Output: ./mkremote.sh fsck_ext2fs rumpsrc/sbin/fsck_ext2fs/fsck_ext2fs.ro rump/lib/libutil.a ( cd rumpsrc/sbin/fsck_ffs && /home/j-r/UNI/genode/contrib/rumprun/rumptools/rumpmake LIBCRT0= BUILDRUMP_CFLAGS="-fPIC -std=gnu99 -D__NetBSD__ " fsck_ffs.ro ) compile fsck_ffs/dir.o compile fsck_ffs/inode.o inode.c: In function 'swap_dinode2': inode.c:378:21: error: iteration 2u invokes undefined behavior [-Werror=aggressive-loop-optimizations] dp2->di_extb[j] = bswap64(dp2->di_extb[j]); ^ inode.c:377:4: note: containing loop for (j = 0; j < (UFS_NDADDR + UFS_NIADDR + UFS_NXADDR); j++) ^ inode.c: In function 'swap_dinode1': inode.c:362:22: error: iteration 12u invokes undefined behavior [-Werror=aggressive-loop-optimizations] dp1->di_db[j] = bswap32(dp1->di_db[j]); ^ inode.c:361:4: note: containing loop for (j = 0; j < (UFS_NDADDR + UFS_NIADDR); j++) ^ cc1: all warnings being treated as errors *** Failed target: inode.o *** Failed command: /home/j-r/UNI/genode/contrib/rumprun/rumptools/bin/x86_64--netbsd-gcc -O2 -g -fPIC -std=gnu99 -D__NetBSD__ -std=gnu99 -Werror -Wno-unused-but-set-variable -Wno-unused-local-typedefs -Wno-maybe-uninitialized -I/home/j-r/UNI/genode/contrib/rumprun/rumptools/compat/include -D__NetBSD__ -Ulinux -U__linux -U__linux__ -U__gnu_linux__ -DHAVE_POSIX_MEMALIGN -DHAVE_PTHREAD_SETNAME_2 --sysroot=/home/j-r/UNI/genode/contrib/rumprun/rumptools/dest -I/home/j-r/UNI/genode/contrib/rumprun/rumpsrc/sbin/fsck -I/home/j-r/UNI/genode/contrib/rumprun/rumpsrc/sbin/dump -DPROGRESS -DWAPBL_DEBUG_PRINT=0 -c inode.c *** Error code 1 Stop. nbmake[2]: stopped in /home/j-r/UNI/genode/contrib/rumprun/rumpsrc/sbin/fsck_ffs Makefile:128: recipe for target 'rumpsrc/sbin/fsck_ffs/fsck_ffs.ro' failed make[1]: *** [rumpsrc/sbin/fsck_ffs/fsck_ffs.ro] Error 1 make[1]: Leaving directory '/home/j-r/UNI/genode/contrib/rumprun' tool/tool_chain_rump:86: recipe for target 'contrib/rumprun/.compile.tag' failed make: *** [contrib/rumprun/.compile.tag] Error 2 Thank you in advance, Jan

2 1

Re: run/demo on NOVA failed
by Jan-Ralph Sroka 13 Aug '17

13 Aug '17

Hi Ivan, thank you for the fast and helpful reply. Your suggestion brought me onto the right track. Regards, Jan --------------------------------------------------- Hi Jan, looks like you need to install syslinux on the host. Ð²Ñ, 13 Ð°Ð²Ð³. 2017 Ð³. Ð² 11:35, Jan-Ralph Sroka <Jan-Ralph.Sroka@...6...>: Hello, as stated I try to run the Demo on NOVA. I've been following the guide on the homepage and: - prapared the ports for nova and x86emu - prepared libc - uncommented 'REPOSITORIES += $(GENODE_DIR)/repos/libports' in the config file - made the builddirectory - made the kernel - successful run the demo on a Linux Kernel System: I am using Ubuntu 16.04 LTS I am getting the following error output: -------------------------------------------------------------------------------- Program lib/ld/nova/ld-nova make[1]: Verzeichnis â/home/j-r/UNI/genode/build/nova_x86_32â wird verlassen genode build completed using 'core-nova.o' as 'core.o' using 'ld-nova.lib.so' as 'ld.lib.so' using 'nova_timer_drv' as 'timer' install bootloader creating ISO image... Warning: -follow-links does not always work correctly; be careful. Size of boot image is 4 sectors -> No emulation Total translation table size: 2048 Total rockridge attributes bytes: 1624 Total directory bytes: 6882 Path table size(bytes): 50 Max brk space used 23000 3916 extents written (7 MB) make[1]: isohybrid: Befehl nicht gefunden make[1]: *** [iso] Fehler 127 Error: ISO image creation failed Makefile:309: die Regel fÃ¼r Ziel ârun/demoâ scheiterte make: *** [run/demo] Fehler 251 --------------------------------------------------------------------------------------- I am clearly missing something but can't figure out what exactly. cheers, Jan ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ genode-main mailing list genode-main(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/genode-main ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot_______________________________________________ genode-main mailing list genode-main(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/genode-main

1 0

run/demo on NOVA failed
by Jan-Ralph Sroka 13 Aug '17

13 Aug '17

Hello, as stated I try to run the Demo on NOVA. I've been following the guide on the homepage and: - prapared the ports for nova and x86emu - prepared libc - uncommented 'REPOSITORIES += $(GENODE_DIR)/repos/libports' in the config file - made the builddirectory - made the kernel - successful run the demo on a Linux Kernel System: I am using Ubuntu 16.04 LTS I am getting the following error output: -------------------------------------------------------------------------------- Program lib/ld/nova/ld-nova make[1]: Verzeichnis â/home/j-r/UNI/genode/build/nova_x86_32â wird verlassen genode build completed using 'core-nova.o' as 'core.o' using 'ld-nova.lib.so' as 'ld.lib.so' using 'nova_timer_drv' as 'timer' install bootloader creating ISO image... Warning: -follow-links does not always work correctly; be careful. Size of boot image is 4 sectors -> No emulation Total translation table size: 2048 Total rockridge attributes bytes: 1624 Total directory bytes: 6882 Path table size(bytes): 50 Max brk space used 23000 3916 extents written (7 MB) make[1]: isohybrid: Befehl nicht gefunden make[1]: *** [iso] Fehler 127 Error: ISO image creation failed Makefile:309: die Regel fÃ¼r Ziel ârun/demoâ scheiterte make: *** [run/demo] Fehler 251 --------------------------------------------------------------------------------------- I am clearly missing something but can't figure out what exactly. cheers, Jan

2 1

gdb with Qt
by Johannes Kliemann 11 Aug '17

11 Aug '17

Hi, I currently try to debug a Qt application with gdb. I adapted the setup from `ports/run/gdb_monitor_interactive.run?` and tried it with the framebuffer test and tetrix. The framebuffer test worked fine but with tetrix it hangs after the first continue and doesn't seem to break at `binary_ready_hook_for_gdb`. There's also no further output in Genode so I suspect that nothing is executed anymore. This seems only to happen with Qt applications. Did anyone had a similar problem? Regards, Johannes

1 0

Error unable to initialize cap quota of PD
by Jörg-Christian Böhme 09 Aug '17

09 Aug '17

My setup/environment: - Source: Branch: master Date: Thu Jun 29 00:18:26 2017 +0200 commit 0d1be4abe2294155e36bc0eb0c1cd61499f08d93 - Target-genode-System: nova x86_64 - Host-System: genode-x86-gcc (GCC) 6.3.0 Ubuntu 17.04 QEMU emulator version 2.8.0(Debian 1:2.8+dfsg-3ubuntu2.3) Hi @all, I try to run following system scenario: make run/launcher KERNEL=nova but it fails with endless loop of following warning: ... Warning: PD (init -> drivers) cap limit (used=44, limit=46) exceeded during transfer_quota(4) ... I want to fix that and try to understand what is the root cause for this warning. I read the documentation, mainly 6.2.2. Resource assignment -> Capability budget. But I'm not smart enough to understand this ;-), again I'm a newbie :-). Is there some other documentation or another chapter that I should read ? By the way, I read the hole old documentation 16.05 before. What I try/understand: In [BUILD_DIR]/var/run/launcher.run I see following: ... <default caps="50"/> ... <start name="drivers" caps="300"> ... At start time I see following output: ... 5072 MiB RAM and 63254 caps assigned to init ... [init -> drivers] Warning: platform_drv: assigned caps (200) exceed available caps (123) [init -> drivers] Warning: fb_drv: assigned caps (100) exceed available caps (0) [init -> drivers] Warning: ps2_drv: assigned caps (60) exceed available caps (0) [init -> drivers] Warning: usb_drv: assigned caps (100) exceed available caps (0) [init -> drivers] Warning: input_filter: assigned caps (80) exceed available caps (0) Warning: PD (init -> drivers) cap limit (used=44, limit=70) exceeded during transfer_quota(28) [init -> drivers] Error: acpi_drv: unable to initialize cap quota of PD Warning: PD (init -> drivers) cap limit (used=44, limit=46) exceeded during transfer_quota(4) [init -> drivers] resource_request: cap_quota=4 [init] child "drivers" requests resources: cap_quota=4 Warning: PD (init -> drivers) cap limit (used=44, limit=46) exceeded during transfer_quota(4) [init -> drivers] resource_request: cap_quota=4 [init] child "drivers" requests resources: cap_quota=4 Warning: PD (init -> drivers) cap limit (used=44, limit=46) exceeded during transfer_quota(4) [init -> drivers] resource_request: cap_quota=4 [init] child "drivers" requests resources: cap_quota=4 [init -> drivers] Warning: re-attempted CPU session request 2 times (args: diag=0, label="ps2_drv", ram_quota=36K, cap_quota=4) Warning: PD (init -> drivers) cap limit (used=44, limit=46) exceeded during transfer_quota(4) [init -> drivers] resource_request: cap_quota=4 [init] child "drivers" requests resources: cap_quota=4 Warning: PD (init -> drivers) cap limit (used=44, limit=46) exceeded during transfer_quota(4) [init -> drivers] resource_request: cap_quota=4 [init] child "drivers" requests resources: cap_quota=4 [init -> drivers] Warning: re-attempted CPU session request 4 times (args: diag=0, label="ps2_drv", ram_quota=36K, cap_quota=4) Warning: PD (init -> drivers) cap limit (used=44, limit=46) exceeded during transfer_quota(4) First, I didn't found any <start> configuration for: - platform_drv - fb_drv - usb_drv - input_filter But I see at startup time that they are loaded into rom fs: ... :rom_fs: ROM modules: ... ROM: [000000007fb45000,000000007fb86db0) fb_drv ... ROM: [000000007ffe2000,000000007ffff740) input_filter ... ROM: [000000007f6e3000,000000007f71d6d0) platform_drv ... ROM: [000000007fe03000,000000007fef5830) usb_drv ... I think the root cause is following Error: [init -> drivers] Error: acpi_drv: unable to initialize cap quota of PD I understand that the acpi_drv component need X caps to transfer to the drivers component. But how many caps ? Then I try to understand the warning for example: [init -> drivers] Warning: ps2_drv: assigned caps (60) exceed available caps (0) What I understand after reading the documentation: ps2_drv try to give the drivers component 60 caps but they have only 0 caps left? Also I try to understand the following warning: Warning: PD (init -> drivers) cap limit (used=44, limit=70) exceeded during transfer_quota(28) I understand: The drivers component used 44 caps. The component need additional caps of 28 but the limit of 70 caps is exceeded. (44 + 28 = 72 > 70) Why limit 70? In the start configuration we set for the drivers component 300 caps. So I read in the documentation, that we can enable a diagnostic mode for the PD session. I try this but even then, I did not understand the logs. Here what I get: ... Genode 17.05-86-g0d1be4abe <local changes> 5072 MiB RAM and 63254 caps assigned to init PD (init -> drivers) consumed RPC cap (used=7, limit=280) PD (init -> drivers) consumed RPC cap (used=8, limit=280) PD (init -> drivers) consumed signal-source cap (used=10, limit=280) PD (init -> drivers) consumed RPC cap (used=11, limit=280) PD (init -> drivers) consumed signal-context cap (used=12, limit=280) PD (init -> drivers) transferred 3 caps to 'init' (used=12, limit=277) PD (init -> drivers) transferred 3 caps to 'init' (used=13, limit=280) ... PD (init -> drivers) consumed signal-context cap (used=14, limit=280) PD (init -> drivers) consumed signal-context cap (used=15, limit=280) PD (init -> drivers) consumed signal-context cap (used=16, limit=280) ... PD (init -> drivers) consumed RPC cap (used=18, limit=280) PD (init -> drivers) consumed RPC cap (used=19, limit=280) PD (init -> drivers) consumed RPC cap (used=21, limit=280) PD (init -> drivers) consumed RPC cap (used=22, limit=280) PD (init -> drivers) consumed RPC cap (used=24, limit=280) [init -> drivers] Warning: platform_drv: assigned caps (200) exceed available caps (123) PD (init -> drivers) consumed RPC cap (used=25, limit=280) PD (init -> drivers) consumed RPC cap (used=26, limit=280) PD (init -> drivers) consumed RPC cap (used=28, limit=280) [init -> drivers] Warning: fb_drv: assigned caps (100) exceed available caps (0) PD (init -> drivers) consumed RPC cap (used=30, limit=280) PD (init -> drivers) consumed RPC cap (used=31, limit=280) [init -> drivers] Warning: ps2_drv: assigned caps (60) exceed available caps (0) PD (init -> drivers) consumed RPC cap (used=33, limit=280) PD (init -> drivers) consumed RPC cap (used=34, limit=280) [init -> drivers] Warning: usb_drv: assigned caps (100) exceed available caps (0) PD (init -> drivers) consumed RPC cap (used=38, limit=280) PD (init -> drivers) consumed RPC cap (used=39, limit=280) PD (init -> drivers) consumed RPC cap (used=41, limit=280) [init -> drivers] Warning: input_filter: assigned caps (80) exceed available caps (0) PD (init -> drivers) consumed RPC cap (used=42, limit=280) PD (init -> drivers) consumed RPC cap (used=43, limit=280) PD (init -> drivers) transferred 13 caps to 'init' (used=44, limit=267) PD (init -> drivers) transferred 0 caps to 'init -> drivers -> input_filter' (used=44, limit=267) PD (init -> drivers) transferred 13 caps to 'init' (used=44, limit=254) PD (init -> drivers) transferred 0 caps to 'init -> drivers -> usb_drv' (used=44, limit=254) PD (init -> drivers) transferred 13 caps to 'init' (used=44, limit=241) PD (init -> drivers) transferred 0 caps to 'init -> drivers -> ps2_drv' (used=44, limit=241) PD (init -> drivers) transferred 13 caps to 'init' (used=44, limit=228) PD (init -> drivers) transferred 0 caps to 'init -> drivers -> fb_drv' (used=44, limit=228) PD (init -> drivers) transferred 13 caps to 'init' (used=44, limit=215) PD (init -> drivers) transferred 91 caps to 'init -> drivers -> platform_drv' (used=44, limit=124) PD (init -> drivers) transferred 13 caps to 'init' (used=44, limit=111) PD (init -> drivers) transferred 28 caps to 'init -> drivers -> report_rom' (used=44, limit=83) PD (init -> drivers) transferred 13 caps to 'init' (used=44, limit=70) Warning: PD (init -> drivers) cap limit (used=44, limit=70) exceeded during transfer_quota(28) [init -> drivers] Error: acpi_drv: unable to initialize cap quota of PD PD (init -> drivers) transferred 4 caps to 'init' (used=44, limit=66) PD (init -> drivers) transferred 2 caps to 'init' (used=44, limit=64) PD (init -> drivers) transferred 3 caps to 'init' (used=44, limit=61) PD (init -> drivers) transferred 3 caps to 'init' (used=44, limit=58) PD (init -> drivers) transferred 4 caps to 'init' (used=44, limit=54) PD (init -> drivers) transferred 2 caps to 'init' (used=44, limit=52) PD (init -> drivers) transferred 3 caps to 'init' (used=44, limit=49) PD (init -> drivers) transferred 3 caps to 'init' (used=44, limit=46) Warning: PD (init -> drivers) cap limit (used=44, limit=46) exceeded during transfer_quota(4) [init -> drivers] resource_request: cap_quota=4 [init] child "drivers" requests resources: cap_quota=4 Warning: PD (init -> drivers) cap limit (used=44, limit=46) exceeded during transfer_quota(4) [init -> drivers] resource_request: cap_quota=4 [init] child "drivers" requests resources: cap_quota=4 Warning: PD (init -> drivers) cap limit (used=44, limit=46) exceeded during transfer_quota(4) [init -> drivers] resource_request: cap_quota=4 [init] child "drivers" requests resources: cap_quota=4 [init -> drivers] Warning: re-attempted CPU session request 2 times (args: diag=0, label="ps2_drv", ram_quota=36K, cap_quota=4) Warning: PD (init -> drivers) cap limit (used=44, limit=46) exceeded during transfer_quota(4) [init -> drivers] resource_request: cap_quota=4 I start to read and understand the first line... PD (init -> drivers) consumed RPC cap (used=7, limit=280) The drivers component create/consumed a RPC cap and after that they used 7 caps with a limit of 280. Again, why the limit is set to 280 and not 300 ? How many caps are needed for the "RPC consumed" ? Because I see also following line: ... PD (init -> drivers) consumed RPC cap (used=39, limit=280) PD (init -> drivers) consumed RPC cap (used=41, limit=280) ... After consumed RPC cap and using of 39 caps, there is additional consumed RPC with a used of 41 ? Why not 40 ? Next confusing lines for me: PD (init -> drivers) transferred 3 caps to 'init' (used=12, limit=277) Drivers transferred 3 caps from the limit of 277 to init? After that we get a limit of 280? PD (init -> drivers) transferred 3 caps to 'init' (used=13, limit=280) etc. I add the full log below. I'm really sure I missed something, but I don't know what. Maybe the root cause is somewhere else. Hopefully somebody give me a hint and/or explain me the log output of "caps" warning. I found the log in the source but even that, I'm not fully understand the purpose of the log. Thanks Regards Jörg NOVA Microhypervisor v7-0d1be4a (x86_64): Aug 1 2017 07:27:06 [gcc 6.3.0] [MBI] [ 0] TSC:2807562 kHz BUS:1005026 kHz (measured) [ 0] TSC:2000000 kHz BUS:1000000 kHz (adjusted due to instable TSC) [ 0] CORE:0:0:0 6:f:b:0 [0] Intel(R) Core(TM)2 Duo CPU T7700 @ 2.40GHz Hypervisor reports 1x1 CPU Warning: CPU has no invariant TSC. CPU ID (genode->kernel:package:core:thread) remapping remap (0->0:0:0:0) boot cpu Hypervisor info page contains 10 memory descriptors: core image [0000000000100000,0000000000bcc000) binaries region [0000000000226000,0000000000bcc000) free for reuse detected physical memory: 0x0000000000000000 - size: 0x000000000009fc00 use physical memory: 0x0000000000000000 - size: 0x000000000009f000 detected physical memory: 0x0000000000100000 - size: 0x00000000bfee0000 use physical memory: 0x0000000000100000 - size: 0x00000000bfee0000 detected physical memory: 0x0000000100000000 - size: 0x0000000080000000 use physical memory: 0x0000000100000000 - size: 0x0000000080000000 :virt_alloc: Allocator 0x1e78f0 dump: Block: [0000000000002000,0000000000003000) size=4K avail=0 max_avail=0 Block: [0000000000003000,0000000000004000) size=4K avail=0 max_avail=0 Block: [0000000000004000,0000000000005000) size=4K avail=0 max_avail=0 Block: [0000000000005000,0000000000006000) size=4K avail=0 max_avail=0 Block: [0000000000006000,0000000000007000) size=4K avail=0 max_avail=0 Block: [0000000000007000,0000000000008000) size=4K avail=0 max_avail=0 Block: [0000000000008000,0000000000009000) size=4K avail=0 max_avail=0 Block: [0000000000009000,000000000000a000) size=4K avail=0 max_avail=0 Block: [000000000000a000,000000000000b000) size=4K avail=0 max_avail=0 Block: [000000000000b000,000000000000c000) size=4K avail=0 max_avail=0 Block: [000000000000c000,000000000000d000) size=4K avail=0 max_avail=0 Block: [000000000000d000,000000000000e000) size=4K avail=0 max_avail=0 Block: [000000000000e000,000000000000f000) size=4K avail=0 max_avail=0 Block: [000000000000f000,0000000000010000) size=4K avail=0 max_avail=0 Block: [0000000000010000,0000000000011000) size=4K avail=0 max_avail=0 Block: [0000000000011000,0000000000012000) size=4K avail=0 max_avail=0 Block: [0000000000012000,0000000000013000) size=4K avail=0 max_avail=0 Block: [0000000000013000,0000000000014000) size=4K avail=0 max_avail=137434760164K Block: [0000000000014000,0000000000015000) size=4K avail=0 max_avail=0 Block: [0000000000015000,0000000000016000) size=4K avail=0 max_avail=0 Block: [0000000000016000,0000000000017000) size=4K avail=0 max_avail=0 Block: [0000000000017000,0000000000018000) size=4K avail=0 max_avail=0 Block: [0000000000018000,0000000000019000) size=4K avail=0 max_avail=0 Block: [0000000000019000,000000000001a000) size=4K avail=0 max_avail=0 Block: [000000000001a000,000000000001b000) size=4K avail=0 max_avail=0 Block: [000000000001b000,000000000001c000) size=4K avail=0 max_avail=0 Block: [000000000001c000,000000000001d000) size=4K avail=0 max_avail=0 Block: [000000000001d000,000000000001e000) size=4K avail=0 max_avail=0 Block: [000000000001e000,000000000001f000) size=4K avail=0 max_avail=0 Block: [000000000001f000,0000000000020000) size=4K avail=0 max_avail=0 Block: [0000000000020000,0000000000021000) size=4K avail=0 max_avail=0 Block: [0000000000021000,0000000000022000) size=4K avail=0 max_avail=0 Block: [0000000000022000,0000000000023000) size=4K avail=0 max_avail=0 Block: [0000000000023000,0000000000024000) size=4K avail=0 max_avail=0 Block: [0000000000024000,0000000000025000) size=4K avail=0 max_avail=0 Block: [0000000000025000,0000000000026000) size=4K avail=0 max_avail=137434760164K Block: [0000000000026000,0000000000027000) size=4K avail=0 max_avail=0 Block: [0000000000027000,0000000000028000) size=4K avail=0 max_avail=0 Block: [0000000000028000,0000000000029000) size=4K avail=0 max_avail=0 Block: [0000000000029000,000000000002a000) size=4K avail=0 max_avail=0 Block: [000000000002a000,000000000002b000) size=4K avail=0 max_avail=0 Block: [000000000002b000,000000000002c000) size=4K avail=0 max_avail=836K Block: [000000000002c000,000000000002d000) size=4K avail=0 max_avail=0 Block: [000000000002d000,000000000002e000) size=4K avail=0 max_avail=836K Block: [000000000002e000,000000000002f000) size=4K avail=0 max_avail=0 Block: [000000000002f000,0000000000100000) size=836K avail=836K max_avail=836K Block: [0000000000226000,0000000000227000) size=4K avail=0 max_avail=0 Block: [0000000000227000,0000000000228000) size=4K avail=0 max_avail=137434760164K Block: [0000000000228000,0000000000229000) size=4K avail=0 max_avail=0 Block: [0000000000229000,00000000a0000000) size=2619228K avail=2619228K max_avail=2619228K Block: [00000000b0000000,00000000bfeff000) size=261116K avail=261116K max_avail=137434760164K Block: [00000000bff04000,00007fffbfffd000) size=137434760164K avail=137434760164K max_avail=137434760164K => mem_size=140736144932864 (134216446 MB) / mem_avail=140736144736256 (134216446 MB) :phys_alloc: Allocator 0x1e6820 dump: Block: [0000000000001000,0000000000002000) size=4K avail=0 max_avail=0 Block: [0000000000002000,0000000000003000) size=4K avail=0 max_avail=0 Block: [0000000000003000,0000000000004000) size=4K avail=0 max_avail=0 Block: [0000000000004000,0000000000005000) size=4K avail=0 max_avail=0 Block: [0000000000005000,0000000000006000) size=4K avail=0 max_avail=0 Block: [0000000000006000,0000000000007000) size=4K avail=0 max_avail=0 Block: [0000000000007000,0000000000008000) size=4K avail=0 max_avail=0 Block: [0000000000008000,0000000000009000) size=4K avail=0 max_avail=0 Block: [0000000000009000,000000000000a000) size=4K avail=0 max_avail=0 Block: [000000000000a000,000000000000b000) size=4K avail=0 max_avail=0 Block: [000000000000b000,000000000000c000) size=4K avail=0 max_avail=0 Block: [000000000000c000,000000000000d000) size=4K avail=0 max_avail=0 Block: [000000000000d000,000000000000e000) size=4K avail=0 max_avail=0 Block: [000000000000e000,000000000000f000) size=4K avail=0 max_avail=0 Block: [000000000000f000,0000000000010000) size=4K avail=0 max_avail=0 Block: [0000000000010000,0000000000011000) size=4K avail=0 max_avail=0 Block: [0000000000011000,0000000000012000) size=4K avail=0 max_avail=0 Block: [0000000000012000,0000000000013000) size=4K avail=0 max_avail=0 Block: [0000000000013000,0000000000014000) size=4K avail=0 max_avail=0 Block: [0000000000014000,0000000000015000) size=4K avail=0 max_avail=0 Block: [0000000000015000,0000000000016000) size=4K avail=0 max_avail=0 Block: [0000000000016000,0000000000017000) size=4K avail=0 max_avail=0 Block: [0000000000017000,0000000000018000) size=4K avail=0 max_avail=0 Block: [0000000000018000,0000000000019000) size=4K avail=0 max_avail=2G Block: [0000000000019000,000000000001a000) size=4K avail=0 max_avail=0 Block: [000000000001a000,000000000001b000) size=4K avail=0 max_avail=0 Block: [000000000001b000,000000000001c000) size=4K avail=0 max_avail=0 Block: [000000000001c000,000000000001d000) size=4K avail=0 max_avail=0 Block: [000000000001d000,000000000001e000) size=4K avail=0 max_avail=0 Block: [000000000001e000,000000000001f000) size=4K avail=0 max_avail=0 Block: [000000000001f000,0000000000020000) size=4K avail=0 max_avail=0 Block: [0000000000020000,0000000000021000) size=4K avail=0 max_avail=0 Block: [0000000000021000,0000000000022000) size=4K avail=0 max_avail=0 Block: [0000000000022000,0000000000023000) size=4K avail=0 max_avail=0 Block: [0000000000023000,0000000000024000) size=4K avail=0 max_avail=0 Block: [0000000000024000,0000000000025000) size=4K avail=0 max_avail=2G Block: [0000000000025000,0000000000026000) size=4K avail=0 max_avail=0 Block: [0000000000026000,0000000000027000) size=4K avail=0 max_avail=0 Block: [0000000000027000,0000000000028000) size=4K avail=0 max_avail=0 Block: [0000000000028000,0000000000029000) size=4K avail=0 max_avail=0 Block: [0000000000029000,000000000002a000) size=4K avail=0 max_avail=0 Block: [000000000002a000,000000000002b000) size=4K avail=0 max_avail=0 Block: [000000000002b000,000000000002c000) size=4K avail=0 max_avail=0 Block: [000000000002c000,000000000002d000) size=4K avail=0 max_avail=444K Block: [000000000002d000,000000000002e000) size=4K avail=0 max_avail=0 Block: [000000000002e000,000000000002f000) size=4K avail=0 max_avail=444K Block: [000000000002f000,0000000000030000) size=4K avail=0 max_avail=0 Block: [0000000000030000,000000000009f000) size=444K avail=444K max_avail=444K Block: [0000000000100000,0000000000101000) size=4K avail=0 max_avail=2G Block: [0000000000101000,0000000000102000) size=4K avail=0 max_avail=0 Block: [0000000000102000,0000000001000000) size=15352K avail=15352K max_avail=15352K Block: [0000000003400000,0000000003401000) size=4K avail=0 max_avail=2G Block: [0000000003401000,000000007f533000) size=2032840K avail=2032840K max_avail=2032840K Block: [0000000080001000,00000000bffe0000) size=1048444K avail=1048444K max_avail=2G Block: [0000000100000000,0000000180000000) size=2G avail=2G max_avail=2G => mem_size=5319098368 (5072 MB) / mem_avail=5318893568 (5072 MB) :io_mem_alloc: Allocator 0x1e89d8 dump: Block: [0000000000000000,0000000000001000) size=4K avail=4K max_avail=4K Block: [000000000009f000,0000000000100000) size=388K avail=388K max_avail=388K Block: [00000000bffe0000,0000000100000000) size=1048704K avail=1048704K max_avail=18014398503190524K Block: [0000000180000000,fffffffffffff000) size=18014398503190524K avail=18014398503190524K max_avail=18014398503190524K => mem_size=18446744068341370880 (17592186039296 MB) / mem_avail=18446744068341370880 (17592186039296 MB) :rom_fs: ROM modules: ROM: [000000007ff33000,000000007ff49448) acpi_drv ROM: [000000007fbdf000,000000007fbf5e58) backdrop ROM: [000000007fb09000,000000007fb0b1ae) config ROM: [000000007f65a000,000000007f688850) decorator ROM: [000000007f819000,000000007f819357) decorator_init.config ROM: [000000007ff4b000,000000007ffc7ba8) device_pd ROM: [000000007ffc8000,000000007ffc923e) drivers.config ROM: [000000007fa83000,000000007fa845d1) en_us.chargen ROM: [000000007fb45000,000000007fb86db0) fb_drv ROM: [000000007ff4a000,000000007ff4a033) fb_drv.config ROM: [000000007fab2000,000000007fad0b68) floating_window_layouter ROM: [000000007faed000,000000007faf1d38) genode_logo.png ROM: [000000007fa85000,000000007fa85246) grid.png ROM: [000000000002e000,000000000002f000) hypervisor_info_page ROM: [000000007fef6000,000000007ff326d0) init ROM: [000000007ffe2000,000000007ffff740) input_filter ROM: [000000007f83e000,000000007f83e1e5) input_filter.config ROM: [000000007fc54000,000000007fc96580) launcher ROM: [000000007f71e000,000000007f7cbb70) launchpad ROM: [000000007f9d7000,000000007fa82b28) ld.lib.so ROM: [000000007fc97000,000000007fdc8068) libc.lib.so ROM: [000000007f7f1000,000000007f8184a0) libm.lib.so ROM: [000000007fc2a000,000000007fc53cb0) libpng.lib.so ROM: [000000007fb0c000,000000007fb44eb0) liquid_fb ROM: [000000007fdc9000,000000007fdebd00) menu_view ROM: [000000007f82f000,000000007f83e000) menu_view_styles.tar ROM: [000000007f6c8000,000000007f6e20d8) nit_fader ROM: [000000007fbf6000,000000007fc0d9c8) nit_fb ROM: [000000007fc0e000,000000007fc29310) nitlog ROM: [000000007f689000,000000007f6c72d0) nitpicker ROM: [000000007f6e3000,000000007f71d6d0) platform_drv ROM: [000000000002c000,000000000002d000) platform_info ROM: [000000007fbb5000,000000007fbc4ce0) pointer ROM: [000000007fbc5000,000000007fbddcf8) ps2_drv ROM: [000000007ffca000,000000007ffe1770) report_rom ROM: [000000007fdec000,000000007fe02ba0) rom_filter ROM: [000000007f83f000,000000007f9d6148) scout ROM: [000000007fad1000,000000007faec5f8) status_bar ROM: [000000007f7cc000,000000007f7f0740) test-libpng_static ROM: [000000007fba1000,000000007fbb4088) testnit ROM: [000000007f81a000,000000007f82e6a8) timer ROM: [000000007fe03000,000000007fef5830) usb_drv ROM: [000000007fa86000,000000007fab18a0) wm ROM: [000000007fbde000,000000007fbdec92) wm.config ROM: [000000007fb87000,000000007fba0268) xray_trigger ROM: [000000007faf2000,000000007fb08208) zlib.lib.so Genode 17.05-86-g0d1be4abe <local changes> 5072 MiB RAM and 63254 caps assigned to init PD (init -> drivers) consumed RPC cap (used=7, limit=280) PD (init -> drivers) consumed RPC cap (used=8, limit=280) PD (init -> drivers) consumed signal-source cap (used=10, limit=280) PD (init -> drivers) consumed RPC cap (used=11, limit=280) PD (init -> drivers) consumed signal-context cap (used=12, limit=280) PD (init -> drivers) transferred 3 caps to 'init' (used=12, limit=277) PD (init -> drivers) transferred 3 caps to 'init' (used=13, limit=280) [init] child "decorator_config" announces service "ROM" [init] child "report_rom" announces service "Report" [init] child "report_rom" announces service "ROM" PD (init -> drivers) consumed signal-context cap (used=14, limit=280) PD (init -> drivers) consumed signal-context cap (used=15, limit=280) PD (init -> drivers) consumed signal-context cap (used=16, limit=280) [init -> report_rom] Warning: parsing legacy <rom> policies [init] child "timer" announces service "Timer" [init -> report_rom] Warning: parsing legacy <rom> policies [init -> report_rom] Warning: parsing legacy <rom> policies [init -> report_rom] Warning: parsing legacy <rom> policies [init -> report_rom] Warning: parsing legacy <rom> policies [init -> decorator_config] upgrading quota donation for PD session (0 bytes, 4 caps) [init -> decorator_config] resource_request: ram_quota=0, cap_quota=4 [init] child "decorator_config" requests resources: ram_quota=0, cap_quota=4 [init -> report_rom] Warning: parsing legacy <rom> policies [init -> report_rom] Warning: parsing legacy <rom> policies Warning: PD (init -> layouter) cap limit (used=18, limit=18) exceeded during transfer_quota(3) [init -> layouter] resource_request: cap_quota=3 [init] child "layouter" requests resources: cap_quota=3 PD (init -> drivers) consumed RPC cap (used=18, limit=280) PD (init -> drivers) consumed RPC cap (used=19, limit=280) PD (init -> drivers) consumed RPC cap (used=21, limit=280) PD (init -> drivers) consumed RPC cap (used=22, limit=280) PD (init -> drivers) consumed RPC cap (used=24, limit=280) [init -> drivers] Warning: platform_drv: assigned caps (200) exceed available caps (123) PD (init -> drivers) consumed RPC cap (used=25, limit=280) PD (init -> drivers) consumed RPC cap (used=26, limit=280) PD (init -> drivers) consumed RPC cap (used=28, limit=280) [init -> drivers] Warning: fb_drv: assigned caps (100) exceed available caps (0) PD (init -> drivers) consumed RPC cap (used=30, limit=280) PD (init -> drivers) consumed RPC cap (used=31, limit=280) [init -> drivers] Warning: ps2_drv: assigned caps (60) exceed available caps (0) PD (init -> drivers) consumed RPC cap (used=33, limit=280) PD (init -> drivers) consumed RPC cap (used=34, limit=280) [init -> drivers] Warning: usb_drv: assigned caps (100) exceed available caps (0) PD (init -> drivers) consumed RPC cap (used=38, limit=280) PD (init -> drivers) consumed RPC cap (used=39, limit=280) PD (init -> drivers) consumed RPC cap (used=41, limit=280) [init -> drivers] Warning: input_filter: assigned caps (80) exceed available caps (0) PD (init -> drivers) consumed RPC cap (used=42, limit=280) PD (init -> drivers) consumed RPC cap (used=43, limit=280) PD (init -> drivers) transferred 13 caps to 'init' (used=44, limit=267) PD (init -> drivers) transferred 0 caps to 'init -> drivers -> input_filter' (used=44, limit=267) PD (init -> drivers) transferred 13 caps to 'init' (used=44, limit=254) PD (init -> drivers) transferred 0 caps to 'init -> drivers -> usb_drv' (used=44, limit=254) PD (init -> drivers) transferred 13 caps to 'init' (used=44, limit=241) PD (init -> drivers) transferred 0 caps to 'init -> drivers -> ps2_drv' (used=44, limit=241) PD (init -> drivers) transferred 13 caps to 'init' (used=44, limit=228) PD (init -> drivers) transferred 0 caps to 'init -> drivers -> fb_drv' (used=44, limit=228) PD (init -> drivers) transferred 13 caps to 'init' (used=44, limit=215) PD (init -> drivers) transferred 91 caps to 'init -> drivers -> platform_drv' (used=44, limit=124) PD (init -> drivers) transferred 13 caps to 'init' (used=44, limit=111) PD (init -> drivers) transferred 28 caps to 'init -> drivers -> report_rom' (used=44, limit=83) PD (init -> drivers) transferred 13 caps to 'init' (used=44, limit=70) Warning: PD (init -> drivers) cap limit (used=44, limit=70) exceeded during transfer_quota(28) [init -> drivers] Error: acpi_drv: unable to initialize cap quota of PD PD (init -> drivers) transferred 4 caps to 'init' (used=44, limit=66) PD (init -> drivers) transferred 2 caps to 'init' (used=44, limit=64) PD (init -> drivers) transferred 3 caps to 'init' (used=44, limit=61) PD (init -> drivers) transferred 3 caps to 'init' (used=44, limit=58) PD (init -> drivers) transferred 4 caps to 'init' (used=44, limit=54) PD (init -> drivers) transferred 2 caps to 'init' (used=44, limit=52) PD (init -> drivers) transferred 3 caps to 'init' (used=44, limit=49) PD (init -> drivers) transferred 3 caps to 'init' (used=44, limit=46) Warning: PD (init -> drivers) cap limit (used=44, limit=46) exceeded during transfer_quota(4) [init -> drivers] resource_request: cap_quota=4 [init] child "drivers" requests resources: cap_quota=4 Warning: PD (init -> drivers) cap limit (used=44, limit=46) exceeded during transfer_quota(4) [init -> drivers] resource_request: cap_quota=4 [init] child "drivers" requests resources: cap_quota=4 Warning: PD (init -> drivers) cap limit (used=44, limit=46) exceeded during transfer_quota(4) [init -> drivers] resource_request: cap_quota=4 [init] child "drivers" requests resources: cap_quota=4 [init -> drivers] Warning: re-attempted CPU session request 2 times (args: diag=0, label="ps2_drv", ram_quota=36K, cap_quota=4) Warning: PD (init -> drivers) cap limit (used=44, limit=46) exceeded during transfer_quota(4) [init -> drivers] resource_request: cap_quota=4 [init] child "drivers" requests resources: cap_quota=4 Warning: PD (init -> drivers) cap limit (used=44, limit=46) exceeded during transfer_quota(4) [init -> drivers] resource_request: cap_quota=4 [init] child "drivers" requests resources: cap_quota=4 [init -> drivers] Warning: re-attempted CPU session request 4 times (args: diag=0, label="ps2_drv", ram_quota=36K, cap_quota=4) Warning: PD (init -> drivers) cap limit (used=44, limit=46) exceeded during transfer_quota(4) [init -> drivers] resource_request: cap_quota=4 [init] child "drivers" requests resources: cap_quota=4 Warning: PD (init -> drivers) cap limit (used=44, limit=46) exceeded during transfer_quota(4) [init -> drivers] resource_request: cap_quota=4 [init] child "drivers" requests resources: cap_quota=4 Warning: PD (init -> drivers) cap limit (used=44, limit=46) exceeded during transfer_quota(4) [init -> drivers] resource_request: cap_quota=4 [init] child "drivers" requests resources: cap_quota=4 Warning: PD (init -> drivers) cap limit (used=44, limit=46) exceeded during transfer_quota(4) [init -> drivers] resource_request: cap_quota=4 [init] child "drivers" requests resources: cap_quota=4 [init -> drivers] Warning: re-attempted CPU session request 8 times (args: diag=0, label="ps2_drv", ram_quota=36K, cap_quota=4) Warning: PD (init -> drivers) cap limit (used=44, limit=46) exceeded during transfer_quota(4) [init -> drivers] resource_request: cap_quota=4 [init] child "drivers" requests resources: cap_quota=4 Warning: PD (init -> drivers) cap limit (used=44, limit=46) exceeded during transfer_quota(4) [init -> drivers] resource_request: cap_quota=4 [init] child "drivers" requests resources: cap_quota=4 Warning: PD (init -> drivers) cap limit (used=44, limit=46) exceeded during transfer_quota(4) [init -> drivers] resource_request: cap_quota=4 [init] child "drivers" requests resources: cap_quota=4 Warning: PD (init -> drivers) cap limit (used=44, limit=46) exceeded during transfer_quota(4) [init -> drivers] resource_request: cap_quota=4 [init] child "drivers" requests resources: cap_quota=4 Warning: PD (init -> drivers) cap limit (used=44, limit=46) exceeded during transfer_quota(4) [init -> drivers] resource_request: cap_quota=4 [init] child "drivers" requests resources: cap_quota=4 Warning: PD (init -> drivers) cap limit (used=44, limit=46) exceeded during transfer_quota(4) [init -> drivers] resource_request: cap_quota=4 [init] child "drivers" requests resources: cap_quota=4 Warning: PD (init -> drivers) cap limit (used=44, limit=46) exceeded during transfer_quota(4) [init -> drivers] resource_request: cap_quota=4 [init] child "drivers" requests resources: cap_quota=4 Warning: PD (init -> drivers) cap limit (used=44, limit=46) exceeded during transfer_quota(4) [init -> drivers] resource_request: cap_quota=4 [init] child "drivers" requests resources: cap_quota=4 [init -> drivers] Warning: re-attempted CPU session request 16 times (args: diag=0, label="ps2_drv", ram_quota=36K, cap_quota=4) Warning: PD (init -> drivers) cap limit (used=44, limit=46) exceeded during transfer_quota(4) [init -> drivers] resource_request: cap_quota=4 [init] child "drivers" requests resources: cap_quota=4 Warning: PD (init -> drivers) cap limit (used=44, limit=46) exceeded during transfer_quota(4) [init -> drivers] resource_request: cap_quota=4 [init] child "drivers" requests resources: cap_quota=4 Expect: 'interact' received 'strg+c' and was cancelled

2 2

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

users