The following reply was made to PR kern/32162; it has been noted by GNATS.

From: Simon Burge <simonb@wasabisystems.com>
To: Andreas Wrede <andreas@planix.com>
Cc: gnats-bugs@NetBSD.org, Jason Thorpe <thorpej@shagadelic.org>,
	Manuel Bouyer <bouyer@antioche.eu.org>, kern-bug-people@NetBSD.org,
	gnats-admin@NetBSD.org, netbsd-bugs@NetBSD.org,
	Chuck Silvers <chuq@chuq.com>, Simon Burge <simonb@wasabisystems.com>
Subject: Re: kern/32162: [netbsd-3.0] kernel dead-lock in MP system 
Date: Tue, 14 Feb 2006 19:08:16 +1100

 Andreas Wrede wrote:
 
 > Is it possible that the problem Simon Burge describes in  
 > "Initialising the same pool multiple times" (http://mail- 
 > index.netbsd.org/tech-kern/2006/02/13/0003.html) is causing the  
 > random panic I am getting?
 
 I doubt this would be the case.  So far the only known call that
 initialises a pool more than once is in RAIDframe and only when there's
 more than one raid set.  It looks like you've only been using on
 RAIDframe set so you shouldn't have any problems.
 
 So far it's only had the effect of corrupting the pool list, of which
 "vmstat -m" is about the only thing affected.  I don't see how at
 this stage it could cause a random panic.
 
 Cheers,
 Simon.
 --
 Simon Burge                            <simonb@wasabisystems.com>
 NetBSD Support and Service:         http://www.wasabisystems.com/