From owner-freebsd-stable Sun Feb 18 7: 0: 7 2001 Delivered-To: freebsd-stable@freebsd.org Received: from guru.mired.org (okc-65-26-235-186.mmcable.com [65.26.235.186]) by hub.freebsd.org (Postfix) with SMTP id 2C66137B401 for ; Sun, 18 Feb 2001 07:00:03 -0800 (PST) Received: (qmail 26200 invoked by uid 100); 18 Feb 2001 15:00:01 -0000 From: Mike Meyer MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14991.58225.783986.487533@guru.mired.org> Date: Sun, 18 Feb 2001 09:00:01 -0600 To: stable@freebsd.org Subject: Suggestions for diagnosing lockups X-Mailer: VM 6.89 under 21.1 (patch 14) "Cuyahoga Valley" 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-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've got a box that's been running FreeBSD relatively problem-free for the last couple of years. I installed 4.2-R about a week ago, and started having lockups every night. A second box is checking on the problem box once a minute, and logging a message if it famils to connect. I can therefore determine that the lockup occurs reliably a shortly (less than a minute) after the periodic daily run starts. Running the periodic script by hand works fine. So does "make world". I've enabled DDB in the kernel, verified that it worked, then watched the system freeze. However, I normally leave X running on the box, and I got no response from DDB this morning. Am I correct in assuming this is the normal behavior, and I need to shut down X (and probably log out) before the freeze. If that's not the case, and the freeze is locking the system up so hard that I can't get to DDB, any other suggestions for debugging this would be greatly appreciated. Thanx,