From owner-freebsd-questions Fri Dec 8 18:53:52 2000 From owner-freebsd-questions@FreeBSD.ORG Fri Dec 8 18:53:49 2000 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from msg.ucsf.edu (msg.ucsf.edu [128.218.69.41]) by hub.freebsd.org (Postfix) with SMTP id 2A2E937B401 for ; Fri, 8 Dec 2000 18:53:49 -0800 (PST) Received: (qmail 438 invoked by uid 391); 9 Dec 2000 03:02:03 -0000 Date: Fri, 8 Dec 2000 19:02:03 -0800 From: Matt Harrington To: freebsd-questions@freebsd.org Subject: how to troubleshoot freezes? Message-ID: <20001208190203.B349@msg.ucsf.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG My 4.2-stable server froze up this evening while under heavy NFS load. I was a few hours into a "glimpseindex -o" on an NFS filesystem. The load average hovered nicely at around 1.0. since this is our main server, it had 49 NFS filesystems mounted. anyhow, what does one do to troubleshoot freezes? there is nothing useful in /var/log/messages, but i had seen many entries like the following earlier this week: Dec 4 16:10:19 msg /kernel: got bad cookie vp 0xcf29ae00 bp 0xc643ba60 Dec 4 16:24:48 msg /kernel: got bad cookie vp 0xcf319cc0 bp 0xc64a2ca0 Dec 4 16:24:51 msg /kernel: got bad cookie vp 0xcf319cc0 bp 0xc649b950 hardware = athlon 750, abit ka7-100, mylex raid controller, 256MB ECC ram. or am i S.O.L. since it's PC hardware? i'm used to computers from DEC and SGI which tell you nice things when crashing like, "SIMM in slot 2 is bad". unfortunately i haven't seen such capable diagnostics on PC hardware except on high-end IBM servers. ---Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message