From owner-freebsd-bugs Tue Feb 26 17:12:32 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 65E7437B405; Tue, 26 Feb 2002 17:12:30 -0800 (PST) Received: (from silby@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g1R18OJ68220; Tue, 26 Feb 2002 17:08:24 -0800 (PST) (envelope-from silby) Date: Tue, 26 Feb 2002 17:08:24 -0800 (PST) From: Message-Id: <200202270108.g1R18OJ68220@freefall.freebsd.org> To: ntoomey@chesapeake.net, silby@FreeBSD.org, freebsd-bugs@FreeBSD.org Subject: Re: kern/35354: 4.4/4.5 FreeBSD causes hard lock after 20+ hours of uptime 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 Synopsis: 4.4/4.5 FreeBSD causes hard lock after 20+ hours of uptime State-Changed-From-To: open->feedback State-Changed-By: silby State-Changed-When: Tue Feb 26 17:07:20 PST 2002 State-Changed-Why: Nick, we need a lot more information than that to even start diagnosing. To begin with, compile a kernel with DDB, then try to ctrl-alt-esc into the debugger and run a trace to see what the system is doing. http://www.FreeBSD.org/cgi/query-pr.cgi?pr=35354 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message