-
Notifications
You must be signed in to change notification settings - Fork 257
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
falkon: insufficient kernel memory quota on Genode@NOVA #5455
Comments
Actually it should be just a warning, does Falkon afterwards still work or is it done ? What does 162cdc4 show for numbers regarding the kernel resource usage of Falkon. |
Falkon does not respond to mouse input anymore when it happens and the log messages keep repeating every 2 seconds or so:
|
When I clicked "Restart" in the Leitzentrale after the warnings appeared, I got the following log output and the browser did not start:
When I clicked "Restart" again, the browser started successfully. |
Well, for some reasons Falkon consumes a lot of kernel resources. When killing Falkon it will take a bit of time to free up all the resources (until all CPUs ack that the dead kernel objects in the RCU list can be freed). Can you please add commit 68af359, which will give some more details about which class of objects consumes what amount (first part will be core PD, second part will be Falkon PD) |
Yeah, I'm running the JetStream2 benchmark to trigger the problem, which probably consumes more resources than usual. Here's the output:
|
This is the output with 544dc59:
|
@cproc: can you please try to adjust in repos/base-nova/src/kernel/nova/target.mk the value of CONFIG_MEMORY_DYN_PER_MILL to some higher value (default is 1% of system memory is for the kernel), just to see whether the kernel memory ever will be sufficient. core will report the effective kernel memory during boot. |
I'm currently testing the Falkon web browser on current staging Sculpt and often get errors like the following:
I'm not sure how to fix this.
The text was updated successfully, but these errors were encountered: