From owner-freebsd-current Sun Mar 14 13:18:38 1999 Delivered-To: freebsd-current@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id 7AC3615757 for ; Sun, 14 Mar 1999 13:18:37 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id NAA03022; Sun, 14 Mar 1999 13:12:16 -0800 (PST) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdKi3019; Sun Mar 14 21:12:07 1999 Date: Sun, 14 Mar 1999 13:12:04 -0800 (PST) From: Julian Elischer To: Matthew Dillon Cc: freebsd-current@FreeBSD.org Subject: Re: Checklist for testing new -4.x kernels ( -current ). In-Reply-To: <199903141954.LAA93753@apollo.backplane.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 14 Mar 1999, Matthew Dillon wrote: > Exceptions are made for people who really know what they are doing, verses > only think that they know what they are doing :-) > > * Do not use any loadable modules, compile the needed modules into the > kernel directly. To double check, run 'kldstat' after booting the > system and make sure that only the kernel is listed. This does not mean that modules are thought to be broken, just that it obscures debugging > > * Make sure to install the new boot blocks and new /boot directory from > the latest source. The 3rd stage bootloader one presumes as the 2nd doesn't look at the kernel. > > * Large 'maxusers' kernel configurations ( > 128 ), or kernels > with >= 512MB of ram have experienced instability in the past, be sure > you are using the latest kernel and try lowering the maxusers > paramater to 64 first, before reporting the crash. > > * If weird crashes occur with the splash screen, try disabling it. > > * If weird crashes occur during boot, try diasbling the parallel port > stuff and see if that fixes the problem. > > * When reporting crashes, please include information on the machine's > configuration including any special devices ( such as VN ) that you > may be using, and your disk configuration ( df ), and the memory & > device configuration ( dmesg ). > > * When reporting crashes that occur from testing -- for example, you > are testing the system by running buildworlds, please include the > exact test script / make / whatever that you are doing along with the > system configuration info. > > * Make sure your systems are backed up. > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message