3.1.0 to 3.2.0 (x86) upgrade issue
Hello, after upgrading the seL4 kernel (x86) from 3.1.0 to 3.2.0 we get for the very first invocation of seL4_X86_Page_Map an errorcode of *3* (seL4_IllegalOperation). We bisected the commits between 3.1.0 and 3.2.0 and [0] is the first bad commit for us. If we use the 3.2.0 release with [0] reverted on top than everything works as before - so no changes to Genode/seL4 as used for the 3.1.0 kernel are necessary. It's a know issue, or maybe something changed which must be adjusted in userland/roottask ? Thanks, Alex. [0] https://github.com/seL4/seL4/commit/c8819792d76ae5aecd89bcff656ca561e62959a5
Hi Alex, That commit will have potentially changed the invocation number for mapping a page. Can you double check that you are using the new version of the generated headers from libsel4 and are fully rebuilding your user space with them? Adrian On Thu 21-Jul-2016 11:55 PM, Alexander Boettcher wrote: Hello, after upgrading the seL4 kernel (x86) from 3.1.0 to 3.2.0 we get for the very first invocation of seL4_X86_Page_Map an errorcode of *3* (seL4_IllegalOperation). We bisected the commits between 3.1.0 and 3.2.0 and [0] is the first bad commit for us. If we use the 3.2.0 release with [0] reverted on top than everything works as before - so no changes to Genode/seL4 as used for the 3.1.0 kernel are necessary. It's a know issue, or maybe something changed which must be adjusted in userland/roottask ? Thanks, Alex. [0] https://github.com/seL4/seL4/commit/c8819792d76ae5aecd89bcff656ca561e62959a5 _______________________________________________ Devel mailing list Devel@sel4.systemsmailto:Devel@sel4.systems https://sel4.systems/lists/listinfo/devel ________________________________ The information in this e-mail may be confidential and subject to legal professional privilege and/or copyright. National ICT Australia Limited accepts no liability for any damage caused by this email or its attachments.
Hi Adrian, I found the issue on our side. We seem to somehow mixed up already in the initial port the --arch and --sel4-arch options in the invocation of tools/invocation_header_gen.py in our build system. Doing it the same way as in your Makefile solves the issue. Thanks, Alex. On 22.07.2016 02:48, Adrian Danis wrote:
Hi Alex,
That commit will have potentially changed the invocation number for mapping a page. Can you double check that you are using the new version of the generated headers from libsel4 and are fully rebuilding your user space with them?
Adrian
On Thu 21-Jul-2016 11:55 PM, Alexander Boettcher wrote:
Hello,
after upgrading the seL4 kernel (x86) from 3.1.0 to 3.2.0 we get for the very first invocation of seL4_X86_Page_Map an errorcode of *3* (seL4_IllegalOperation).
We bisected the commits between 3.1.0 and 3.2.0 and [0] is the first bad commit for us. If we use the 3.2.0 release with [0] reverted on top than everything works as before - so no changes to Genode/seL4 as used for the 3.1.0 kernel are necessary.
It's a know issue, or maybe something changed which must be adjusted in userland/roottask ?
Thanks,
Alex.
[0] https://github.com/seL4/seL4/commit/c8819792d76ae5aecd89bcff656ca561e62959a5
_______________________________________________ Devel mailing list Devel@sel4.systemsmailto:Devel@sel4.systems https://sel4.systems/lists/listinfo/devel
________________________________
The information in this e-mail may be confidential and subject to legal professional privilege and/or copyright. National ICT Australia Limited accepts no liability for any damage caused by this email or its attachments.
participants (2)
-
Adrian Danis
-
Alexander Boettcher