From owner-freebsd-hackers Mon Apr 10 11:39:52 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id EF4B737BC2C; Mon, 10 Apr 2000 11:39:47 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id LAA17853; Mon, 10 Apr 2000 11:40:59 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) To: Brian Fundakowski Feldman Cc: hackers@FreeBSD.ORG Subject: Re: somewhat random mostly-lockups in 5.0 In-reply-to: Your message of "Sun, 09 Apr 2000 21:03:04 EDT." Date: Mon, 10 Apr 2000 11:40:59 -0700 Message-ID: <17850.955392059@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > The syptoms are that the machine locks up. Hard. But there's a catch: Erm, Brian, You *know* nobody can debug a problem like this without hard information. It's like calling a mechanic on the phone and saying "My car won't go. It just doesn't move at all! Tell me what's wrong!" Compile in the kernel debugger and start hunting around when the system "locks up" next time. Just figuring out which wait address processes are stuck on would be a BIG HELP. Saying your machine locks up but is still pingable narrows it down to only several thousand lines of code. Even jlemon's "diagnosis" is of only marginal help without actually having access to the failing machine. - Jordan P.S. My -current box from April 6th has yet to do anything like this. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message