Date: Sat, 9 Dec 2000 18:11:15 -0800 From: "Crist J. Clark" <cjclark@reflexnet.net> To: Matt Harrington <matt@msg.ucsf.edu> Cc: freebsd-questions@FreeBSD.ORG Subject: Re: how to troubleshoot freezes? Message-ID: <20001209181115.E96105@149.211.6.64.reflexcom.com> In-Reply-To: <20001208190203.B349@msg.ucsf.edu>; from matt@msg.ucsf.edu on Fri, Dec 08, 2000 at 07:02:03PM -0800 References: <20001208190203.B349@msg.ucsf.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Dec 08, 2000 at 07:02:03PM -0800, Matt Harrington wrote: > > > 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: Freezes and NFS have a long association. How are you mounting the NFSs? > 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. But you implied had a freeze and not crash? -- Crist J. Clark cjclark@alum.mit.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20001209181115.E96105>