From owner-freebsd-bugs Tue Feb 5 1:50:20 2002 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 02E7437B41C for ; Tue, 5 Feb 2002 01:50:07 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g159o6883660; Tue, 5 Feb 2002 01:50:06 -0800 (PST) (envelope-from gnats) Date: Tue, 5 Feb 2002 01:50:06 -0800 (PST) Message-Id: <200202050950.g159o6883660@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Sheldon Hearn Subject: Re: kern/34373: SMP lockup somewhat similar to bug #33986, unless vmware is running... Reply-To: Sheldon Hearn Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org The following reply was made to PR kern/34373; it has been noted by GNATS. From: Sheldon Hearn To: Jesse McConnell Cc: bug-followup@freebsd.org Subject: Re: kern/34373: SMP lockup somewhat similar to bug #33986, unless vmware is running... Date: Tue, 05 Feb 2002 11:52:23 +0200 On Thu, 31 Jan 2002 11:43:17 CST, Jesse McConnell wrote: > well, the lock up still occurs on the more sane NMBCLUSTERS. I just got > rid of the parameter and let the system take care of it. > > As for the lockup without the audio support, it hasn't happened yet...I > fear saying it won't since when it treats me this nice it generally > means it is waiting for me to do something important before > locking...But we are at 1:11 so far and no lock. Any news on whether the lockup appears to be audio-related? If it is, the best way forward will probably be for me to assign the PR to the audio maintainers will you build a kernel with the DDB debugger built in so you can break into the debugger and see where the kernel's stuck. Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message