From owner-freebsd-questions Mon Oct 16 1:59:14 2000 Delivered-To: freebsd-questions@freebsd.org Received: from guru.mired.org (okc-27-149-77.mmcable.com [24.27.149.77]) by hub.freebsd.org (Postfix) with SMTP id D336E37B66C for ; Mon, 16 Oct 2000 01:59:10 -0700 (PDT) Received: (qmail 57015 invoked by uid 100); 16 Oct 2000 08:59:10 -0000 From: Mike Meyer MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14826.50014.195908.611522@guru.mired.org> Date: Mon, 16 Oct 2000 03:59:10 -0500 (CDT) To: Robert LaThanh Cc: questions@freebsd.org Subject: Re: Crash every 45 days in 4.0-RELEASE (sometimes sooner) In-Reply-To: <130095636@toto.iv> X-Mailer: VM 6.75 under 21.1 (patch 10) "Capitol Reef" XEmacs Lucid X-face: "5Mnwy%?j>IIV\)A=):rjWL~NB2aH[}Yq8Z=u~vJ`"(,&SiLvbbz2W`;h9L,Yg`+vb1>RG% *h+%X^n0EZd>TM8_IB;a8F?(Fb"lw'IgCoyM.[Lg#r\ Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Robert LaThanh writes: > (I'm not sure if this is the right group to be posting to, can someone > tell me which group would be more appropriate?) No, this is the right group. > My web server used to be running Red Hat Linux 5.2 and had reached an > uptime of about 150 days. This summer I switched over to FreeBSD > 4.0-RELEASE and I haven't been able to get an uptime of more than 45 > days. While browsing through kernel code I noticed a comment that read: > "Increment time in/out of memory and sleep time (if sleeping). We ignore [...] > About 6 times a day I get the message "/kernel: dc0: TX underrun -- > resetting". It doesn't seem to be affecting the availability of my > server at all, it still seems to perform as expected, otherwise. Could > this have anything to do with the crashing? Check the dc(4) man page. It's the driver reacting to the host not getting data to the NIC fast enough. It's almost certainly ignorable. > Where should I look for the cause of my crashes? I only know to look > at /var/log/messages, but the only unusual messages there are the TX > underrun ones. The best place to look is in the crash dump your system is taking after each crash. The "crash" man page discusses how to do that, as well as providing pointers to how to enable crash dumps if you haven't done so.