Subject: Re: kern/32162: [netbsd-3.0] kernel dead-lock in MP system
To: None <,,>
From: Andreas Wrede <>
List: netbsd-bugs
Date: 11/26/2005 22:19:01
The following reply was made to PR kern/32162; it has been noted by GNATS.

From: Andreas Wrede <>
To: Manuel Bouyer <>
Subject: Re: kern/32162: [netbsd-3.0] kernel dead-lock in MP system
Date: Sat, 26 Nov 2005 17:18:40 -0500

 Content-Transfer-Encoding: 7bit
 Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
 On Nov 26, 2005, at 15:29 , Manuel Bouyer wrote:
 > On Fri, Nov 25, 2005 at 03:13:00AM +0000, Andreas Wrede wrote:
 >>> Environment:
 >> System: NetBSD 3.0_RC3 NetBSD 3.0_RC3  
 >> (PLANIX.MPACPI) #0: Thu Nov 24 20:57:09 EST 2005  
 >> obj.i386/PLANIX.MPACPI i386
 >> Architecture: i386
 >> Machine: i386
 >>> Description:
 >> 	Over the last week I have experienced 3 kernel dead-locks on a  
 >> NetBSD 3.0_RC1/2/3 system.
 >> The motherboard is a Tylan K8S Pro S2882G3NR with 2 AMD Opteron  
 >> 244 CPUs installed. The kernel
 >> is differs from GENERIC.MPACPI in the value for some SYSVSEM  
 >> variables, maxusers and some
 >> other variables.
 > Can you try a kernel with DIAGNOSTIC, DEBUG and LOCKDEBUG ?
 Right now, I am running with LOCKDEBUG. I will add DIAGNOSTIC and DEBUG.
 Not knowing much about kernel debugging, and since creating a core  
 dump is not possible, what commands should I run the next time the  
 dead-lock occurs?
 I looked for info on, all I found was the "What Goes  
 In A Problem Report" page (  
 probably need some updating.
 content-type: application/pgp-signature; x-mac-type=70674453;
 content-description: This is a digitally signed message part
 content-disposition: inline; filename=PGP.sig
 content-transfer-encoding: 7bit
 Version: GnuPG v1.4.1 (Darwin)