From owner-freebsd-current Sun Sep 28 02:02:15 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id CAA19913 for current-outgoing; Sun, 28 Sep 1997 02:02:15 -0700 (PDT) Received: from critter.freebsd.dk (critter.freebsd.dk [195.8.129.26]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id CAA19906 for ; Sun, 28 Sep 1997 02:02:11 -0700 (PDT) Received: from critter.freebsd.dk (localhost.cybercity.dk [127.0.0.1]) by critter.freebsd.dk (8.8.7/8.8.7) with ESMTP id LAA18143 for ; Sun, 28 Sep 1997 11:01:27 +0200 (CEST) To: current@freebsd.org Subject: Come on guys... From: Poul-Henning Kamp Date: Sun, 28 Sep 1997 11:01:25 +0200 Message-ID: <18132.875437285@critter.freebsd.dk> Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk It's seemed to have become vogue lately to send emails that say "my kernel panics when ..." with no detail at all. So for any newcomers or old hands that might have forgotten: WHAT TO DO If your -current kernel panics: 1, Update to the absolutely latest sources, unless emails has been warning against this. 2. rm /lkm/* 3. If you have any local patches, back them out. 4. Recompile, from scratch, your kernel with DDB in it. (For extra points: use "config -g" and do not strip your kernel before booting) 5. Report all details from the panic. As a minimum all info from "show reg" and "trace" are mandatory. Try to secure a kernel-dump. Check the handbook for info on how to run gdb on it. Unless you do at least this, chances are pretty good that your email is a waste of time. Remember guys, you're asking somebody to use their spare-time on your problem, so make it easy for them. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop."