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 majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
