#8345: PANIC: ASSERT FAILED ... x86/paging/pae/x86VMTranslationMapPAE.cpp:231 -----------------------------+------------------------------ Reporter: kallisti5 | Owner: bonefish Type: bug | Status: assigned Priority: critical | Milestone: R1/beta1 Component: System/Kernel | Version: R1/Development Resolution: | Keywords: vm pae Blocked By: | Blocking: 9435, 9520, 9677 Has a Patch: 1 | Platform: x86 -----------------------------+------------------------------ Comment (by bonefish): Replying to [comment:42 phoudoin]: > Now that it seems more reproducible, may be interesting to trace pageTable value and pageTableEntry index in that table: is there a pattern regarding pageTable or PTE position or not. The page table is simply some physical page allocated for that purpose. There aren't any address restrictions, so it can be any page. The PTE's address depends on page table address and mapped virtual address. If you mean, whether there's a patter wrt. where the errors occur, I haven't seen any. > AFAIK, only kernel land stuffs or DMA access could change these PAE tables content over VM shoulder, right? I think the most likely case is that somehow a physical page is doubly- used -- e.g. handed out twice by the page allocation code or not correctly unmapped by someone -- for a page table and at the same time by someone else. -- Ticket URL: <http://dev.haiku-os.org/ticket/8345#comment:43> Haiku <http://dev.haiku-os.org> Haiku - the operating system.