[haiku-bugs] Re: [Haiku] #5506: Kernel panic "heap configuration invalid - max bin count reached"

  • From: "mmlr" <trac@xxxxxxxxxxxx>
  • Date: Tue, 02 Mar 2010 00:39:11 -0000

#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:3 drcouzelis]:
 > Since alpha 1 boots, how about I download old nightly images and find
 out when it stopped being able to boot on my computer? In theory, that
 should allow you to pinpoint what the change was that causes the bug.
 Shall I do that?

 If you want to invest that amount of time then that'd certainly be very
 much appreciated.

 > Is there a test I can do to see if I have memory corruption? I use Arch
 Linux as my primary OS, by the way.

 I more meant memory corruption due to Haiku bugs, not bad hardware. Of
 course that could theoretically be the case as well, though since the data
 in question really is static const and should be loaded and stay at a
 single location it'd be strange for it to work at first and then be gone
 later. A memory corruption due to some bug in the boot process is more
 likely.

 What you can do is to dump the memory that supposedly contains the
 configuration to see what it ends up being. That way we might get an idea
 as to who's overwriting it. To do that execute these commands in the
 kernel debugger:

 {{{
 symbol sHeapClasses
 dw _ 8
 }}}

 That should give some pointer to a string (you can dump it with {{{string
 <pointer>}}} if you're curious, it should read "small"), 0x32 -> 50 the
 initial percentage (unused in this case), 0x200 -> B_PAGE_SIZE / 8 the max
 allocation size, 0x1000 -> B_PAGE_SIZE the heap page size, 0x8 the min bin
 size, 0x4 the alignment, 0x8 the min count per page and 0x10 the max waste
 per page. If any of that doesn't match then something overwrote the
 config. If so please execute a {{{dw _ 64}}} to get a bit more context,
 take another screenshot and attach it here.

-- 
Ticket URL: <http://dev.haiku-os.org/ticket/5506#comment:4>
Haiku <http://dev.haiku-os.org>
Haiku - the operating system.

Other related posts: