Hi Matthias & Stefan,
thanks for your help.
Am 05.07.2018 um 12:46 schrieb Stefan Kalkowski:
Hello Johannes & Matthias,
On Thu, Jul 05, 2018 at 09:52:16AM +0200, Matthias Lange wrote:
Hi Johannes,
On [04-07-2018 15:06], Johannes Kliemann wrote:
Hi all,
I tried to use Fiasco.OC without the kernel debugger, respectively with the following config changes:
diff --git a/repos/base-foc/config/x86_64.kernel b/repos/base-foc/config/x86_64.kernel index 07159da20d..8b8b1c8c50 100644 --- a/repos/base-foc/config/x86_64.kernel +++ b/repos/base-foc/config/x86_64.kernel @@ -56,12 +56,7 @@ CONFIG_STACK_DEPTH=y # CONFIG_IRQ_SPINNER is not set # CONFIG_WATCHDOG is not set CONFIG_SERIAL=y -CONFIG_JDB=y -CONFIG_JDB_LOGGING=y -CONFIG_JDB_DISASM=y -CONFIG_JDB_GZIP=y -# CONFIG_JDB_ACCOUNTING is not set -CONFIG_JDB_MISC=y +# CONFIG_JDB is not set CONFIG_POWERSAVE_GETCHAR=y # CONFIG_WARN_NONE is not set CONFIG_WARN_WARNING=y
It compiles without any errors but the execution fails with multiple messages of:
KERNEL: Warning: nothing mapped: (Obj_space) from [0xffffffff81fd1e90/ffffffffffffffff]: 000000000000000a size: 0000000000000001 to [0xffffffff81fd1d80/ffffffffffffffff]
This message indicates that somebody is trying to map a capability without sufficient rights or the mapped capability is the invalid cap.
Maybe a component has a hard dependency on the 'jdb' capability?
Indeed, core maps that capability to each component, but it is not critical. The capability is only used for testing purposes. Normally it is not used. Thereby the warning can be ignored. If I uncomment the mapping the warning vanishes. Moreover, core sets names to ease debugging for all threads in the kernel debugger. I've prepared an interims commit for you to use Genode/Fiasco.OC without kernel debugger:
https://github.com/skalk/genode/commit/e38ebf4a2de0029f46afdc5b6b6f3c480388f...
Anyway, you won't see any messages on serial line from Genode, because it uses the kernel debugger's outstring method.
So it still runs but doesn't produce any log output. That explains why I thought it didn't work at all (I tried run/log). That solves the issue for me, thanks.
Regards, Johannes