#5506: Kernel panic "heap configuration invalid - max bin count reached" ---------------------------+------------------------------------------------ Reporter: drcouzelis | Owner: mmlr Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1/Development Keywords: | Blockedby: Platform: x86 | Blocking: ---------------------------+------------------------------------------------ Comment(by mmlr): Replying to [comment:5 drcouzelis]: > I've narrowed it down to somewhere between r34837 (1 Jan) and r34934 (7 Jan). There were four builds inbetween them. I will download them while I sleep and check them out tomorrow. Cool thanks for that! > I will attach a screenshot from the "dw" command. Everything seems to match up with what you said it should be. Ok that's interesting. It indeed looks just as it should. Then I can only imagine that the class passed to the function would be incorrect, as the calculations are really all fixed and don't change from machine to machine. Can you please run the following command: {{{ call 12 -5 }}} This should give the arguments passed to heap_create_allocator(). To make sure I'm not completely off, please run the first argument through the {{{string}}} command. It should output "grow". The second argument is the allocation base which can vary, then the size which should be 0x100000 (1MB), then the heap_class pointer which is supposed to be equal to the pointer you get from {{{symbol sHeapClasses}}} and then 0 (false) for not allocating the allocator structure on the heap. -- Ticket URL: <http://dev.haiku-os.org/ticket/5506#comment:6> Haiku <http://dev.haiku-os.org> Haiku - the operating system.