Jean Wolter jw5 at os.inf.tu-dresden.de
Mon Nov 16 11:23:10 CET 1998

Harald Fritzsche <Harald.Fritzsche at mpd.de> writes:

> Hallo Hackers,
> I found (i hope so) the reason for the kbd: sig_sched: invalid
> ext_preempter in
> L4-Linux,  reported earlier.
> In file :
>     linux/arch/l4-i386/lib/task.c
> in function:
>     start_linux_server_thread()
> is used the variable
>     l4_threadid_t     foo_id
> uninitialized.
> I set foo_id to L4_INVALID_ID and the sig_sched disappears. But i don't
> if this is intended from the authors.

Thanks for reporting this. Since L4/Intel never used the value of
'external preempter' we (at least I) have not seen this 'error'.

> Also the null-pointer test gives an error message.

Could you provide some more details? If everything works correctly you
should see a complained from the root pager (something like 'Hmm,
strange, that shouldn't happen anymore' on a hercules monitor) and a
message from the linux server 'mem_init: null pointer dereference
detection seems to work'.

If you see 'mem_init: null pointer check failed' then something is
wrong and the zero page was not flushed correctly. That's something
Michael should be interested in.

I get up each morning, gather my wits.
Pick up the paper, read the obits.
if I'm not there I know I'm not dead.
So I eat a good breakfast and go back to bed. Peete Seeger

More information about the l4-hackers mailing list