Subject: Re: kern/32162: [netbsd-3.0] kernel dead-lock in MP system
To: Manuel Bouyer <firstname.lastname@example.org>
From: Andreas Wrede <email@example.com>
Date: 11/26/2005 19:39:25
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
On Nov 26, 2005, at 18:08 , Manuel Bouyer wrote:
> On Sat, Nov 26, 2005 at 05:18:40PM -0500, Andreas Wrede wrote:
>> On Nov 26, 2005, at 15:29 , Manuel Bouyer wrote:
>>> On Fri, Nov 25, 2005 at 03:13:00AM +0000, Andreas Wrede wrote:
>>>> System: NetBSD whome.planix.com 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
>>>> 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
> Yes, if you have the problem I'm thinking about, it will only be
> detected if you have DIAGNOSTIC. But LOCKDEBUG and DEBUG can't hurt,
> maybe these will catch something else.
>> Not knowing much about kernel debugging, and since creating a core
>> dump is not possible,
> Why ? Have you tried reboot(0x104) ?
Yes - it locks the machine completely so that I cannot re-enter the
>> what commands should I run the next time the
>> dead-lock occurs?
> I can't see at anything more than what you have provided for now ...
content-type: application/pgp-signature; x-mac-type=70674453;
content-description: This is a digitally signed message part
content-disposition: inline; filename=PGP.sig
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (Darwin)
-----END PGP SIGNATURE-----