From owner-freebsd-stable Sun Feb 18 11:36:53 2001 Delivered-To: freebsd-stable@freebsd.org Received: from earth.backplane.com (earth-nat-cw.backplane.com [208.161.114.67]) by hub.freebsd.org (Postfix) with ESMTP id 2DD7437B491 for ; Sun, 18 Feb 2001 11:36:51 -0800 (PST) Received: (from dillon@localhost) by earth.backplane.com (8.11.2/8.9.3) id f1IJanm31380; Sun, 18 Feb 2001 11:36:49 -0800 (PST) (envelope-from dillon) Date: Sun, 18 Feb 2001 11:36:49 -0800 (PST) From: Matt Dillon Message-Id: <200102181936.f1IJanm31380@earth.backplane.com> To: Mike Meyer Cc: stable@FreeBSD.ORG Subject: Re: Suggestions for diagnosing lockups References: <14991.58225.783986.487533@guru.mired.org> 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 :... Try doing the 'edit crontab to run daily in the next minute' trick after switching out of X into a VT. e.g. 'crontab -e' and create a dummy entry to run the daily script at a particular time that will just happen to occur in a minute or two. I also recommend using 4.2-Stable rather then 4.2-Release. 4.2-Release has a number of bugs and security holes relative to stable. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message