Anna, Sure - I've tried a few different combinations, but the latest Genode 18.5 used seL4 9.0.1. I'm attempting to use this on an x86 machine that has a Xeon 1607 and a dedicated GPU. The thread I referenced in my initial post implied that UEFI might be an issue, but I've tried both UEFI and legacy boots without success. I tried using/building Genode 17.5 with whatever version of seL4 it acquires, but get the same error. Let me know if there's anything else I can provide
On Wed, Jul 4, 2018 at 7:51 PM <anna.ly...@data61.csiro.au> wrote: > Hi Jeremy, > > > Could you please provide more details about your setup? What version of > seL4 are you using? And which platform / configuration? > > > Thanks > > Anna. > > > ------------------------------ > *From:* Devel <devel-bounces@sel4.systems> on behalf of Jeremy Fields < > field...@critical.com> > *Sent:* Wednesday, 4 July 2018 10:34 PM > *To:* devel@sel4.systems > *Subject:* [seL4] Memory Region overlap error > > Hello- > > I'm trying to boot Genode/seL4 on hardware. I've tried a few different > combinations of versions, and GRUB configurations, without success. I keep > getting the same error despite these different combinations > > There was a thread that touched on this, but I couldn't find any > resolution http://sel4.systems/pipermail/devel/2017-December/001776.html > > @##################################### > Bender: Hello World. > framebuffer at [b8000+b8fa0) 80x25@16 > warning - unknown framebuffer type > framebuffer at [b8000+b8fa0) 80x25@16 > warning - unknown framebuffer type > > Boot config: parsing cmdline 'sel4 disable_iommu' > Boot config: console_port = 0x3f8 > â–’Boot config: debug_port = 0x3f8 > Boot config: disable_iommu = true > module #0: start=0xf8f0000 end=0xffff228 size=0x70f228 name='image.elf' > Physical Memory Region from 0 size 9ac00 type 1 > Physical Memory Region from 9ac00 size 5400 type 2 > Physical Memory Region from e0000 size 20000 type 2 > Physical Memory Region from 100000 size 18dbb000 type 1 > Adding physical memory region 0x100000-0x18ebb000 > Physical Memory Region from 18ebb000 size 12d000 type 4 > Physical Memory Region from 18fe8000 size 1000 type 1 > Adding physical memory region 0x18fe8000-0x18fe9000 > Physical Memory Region from 18fe9000 size 17000 type 4 > Physical Memory Region from 19000000 size 4ffd000 type 1 > Adding physical memory region 0x19000000-0x1dffd000 > Physical Memory Region from 1dffd000 size 3000 type 3 > Physical Memory Region from 1e000000 size 8e784000 type 1 > Adding physical memory region 0x1e000000-0x1f800000 > Physical Memory Region from ac784000 size 94000 type 2 > Physical Memory Region from ac818000 size fe8000 type 1 > Physical Memory Region from b0000000 size 4000000 type 2 > Physical Memory Region from fed20000 size 20000 type 2 > Physical Memory Region from fed50000 size 40000 type 2 > Physical Memory Region from ffa00000 size 40000 type 2 > Physical Memory Region from 1000000000 size 350000000 type 1 > Physical memory region not addressable > Adding physical memory region 0x0-0x1f800000 > seL4 failed assertion '!p_region_overlaps(reg)' at > /home/critical/Downloads/genode-18.05/contrib/sel4-c59276cc6e3aa138a1e56af8c8a56ce64cf327b8/src/kernel/sel4/src/ > arch/x86/kernel/boot.c:123 in function add_allocated_p_region > halting... > Kernel entry via Interrupt, irq 0 > @##################################### > > Any thoughts? Anything I can try? Any information I can provide to help > diagnose? > > > -- > Sincerely, > Jeremy > ______________________________ > Software Engineer > Critical Technologies Inc. > > -- Sincerely, Jeremy ______________________________ Software Engineer Critical Technologies Inc.
_______________________________________________ Devel mailing list Devel@sel4.systems https://sel4.systems/lists/listinfo/devel
