Re: kern/40552 (Early kernel panic with POOL_DIAGNOSTIC option)

[rmind%NetBSD.org@localhost]

Synopsis: Early kernel panic with POOL_DIAGNOSTIC option

State-Changed-From-To: open->analyzed
State-Changed-By: rmind%NetBSD.org@localhost
State-Changed-When: Sun, 15 Nov 2009 01:43:02 +0000
State-Changed-Why:
While initialising in kmeminit(), subsystem calls itself, that is, malloc()s
via uvm_km_vacache_init().  Moving uvm_km_vacache_init() further or setting
kmem_map later (which is checked in pool_init(), before allocating) might fix
the problem.  However, looking at how long it was unnoticed, I wonder if
POOL_DIAGNOSTIC helps a lot these days?