From owner-freebsd-bugs@FreeBSD.ORG Fri Apr 23 21:30:28 2004 Return-Path: Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AB12916A4CE for ; Fri, 23 Apr 2004 21:30:28 -0700 (PDT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id A251B43D3F for ; Fri, 23 Apr 2004 21:30:28 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) i3O4USbv079132 for ; Fri, 23 Apr 2004 21:30:28 -0700 (PDT) (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.12.10/8.12.10/Submit) id i3O4USDW079131; Fri, 23 Apr 2004 21:30:28 -0700 (PDT) (envelope-from gnats) Date: Fri, 23 Apr 2004 21:30:28 -0700 (PDT) Message-Id: <200404240430.i3O4USDW079131@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org From: Kris Kennaway Subject: Re: kern/65801: 5.2.1 locks up with SMP kernel X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Kris Kennaway List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 24 Apr 2004 04:30:28 -0000 The following reply was made to PR kern/65801; it has been noted by GNATS. From: Kris Kennaway To: Russell Francis Cc: freebsd-gnats-submit@FreeBSD.org Subject: Re: kern/65801: 5.2.1 locks up with SMP kernel Date: Fri, 23 Apr 2004 21:27:09 -0700 On Mon, Apr 19, 2004 at 06:44:38PM -0700, Russell Francis wrote: > >Description: > The machine which is a dual PIII "locks up" after a day or so when it is compiled with an SMP kernel. I have been unable to duplicate this with a UP kernel. When I say lock up, the following things occur. > > - Screen goes black. > > - Keyboard becomes unresponsive [Numlock/capslock] don't toggle lights on the keyboard. > > - The machine becomes unpingable and ssh into the machine no longer works. The machine is probably either panicking, or deadlocking due a locking error. Enable WITNESS, DDB, INVARIANTS and kernel crashdumping, and try to obtain debugging information. Leaving the machine out of X Windows may also help, because you'll see the panic message on the system console. See the Developer's Handbook and for more details. Kris