I'm running into the same issue, with likely the same cause. I wanted to see if there is any further insight that can be given on this? I'm guessing there hasn't been any updates to seL4's memory allocation in this aspect. (I'm using seL4 9.0.1)

My naive attempt of commenting out that particular check in seL4 just results in the machine hard resetting when it runs (if only it were that easy).

>Unfortunately I cannot say that we will get around to fixing this in a particularly timely manner. (2016)

Any chance this is on a roadmap?

--