From owner-freebsd-stable Thu Oct 26 21:30:54 2000 Delivered-To: freebsd-stable@freebsd.org Received: from dsl-64-193-123-121.telocity.com (dsl-64-193-123-121.telocity.com [64.193.123.121]) by hub.freebsd.org (Postfix) with ESMTP id 0C35037B479 for ; Thu, 26 Oct 2000 21:30:51 -0700 (PDT) Received: (from brueggma@localhost) by dsl-64-193-123-121.telocity.com (8.11.1/8.11.1) id e9R4Uno27033 for freebsd-stable@freebsd.org; Thu, 26 Oct 2000 23:30:49 -0500 (CDT) (envelope-from brueggma) Date: Thu, 26 Oct 2000 23:30:49 -0500 From: Eric Brueggmann To: freebsd-stable@freebsd.org Subject: reboot. Message-ID: <20001026233049.A21967@snoopie.yi.org> Reply-To: brueggma@snoopie.yi.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ok.. This is getting a little wierd. A user typed "quota" and the machine rebooted. Before I recompile the kernel as stated below, is anyone haveing similar problems? Typing "du" and "quota" reboot the machine. Eric B. # uname -a FreeBSD dsl-64-193-123-121.telocity.com 4.1.1-STABLE FreeBSD 4.1.1-STABLE #0: Fri Oct 20 12:11:58 CDT 2000 root@dsl-64-193-123-121.telocity.com:/usr/src/sys/compile/BEAST i386 >On Thu, 26 Oct 2000, Eric Brueggmann wrote: > >> Hello again, >> >> I'm experiencing some more df problems. I just typed "df -h" for the >> second time in the past 2 days, and the machine rebooted. No messages in the >> logs, nothing. > > That's really bad. Could you take a look at the instructions for >setting up kernel debugging in the handbook (dumpdev in /etc/rc.conf*, >etc.) and add the following to your kernel config: > ># Add extra debugging information to the kernel >options DIAGNOSTIC > ># The INVARIANTS option is used in a number of source files to enable ># extra sanity checking of internal structures. >options INVARIANTS >options INVARIANT_SUPPORT > ># Kernel debugger >options DDB > ># Don't drop into DDB for a panic. Intended for unattended operation ># where you may want to drop to DDB from the console, but still want ># the machine to recover from a panic >options DDB_UNATTENDED > >The last option is only necessary if you are concerned about this >happening when you are not at the console. It would actually be better to >leave this out if you are going to have physical access to the machine. > > Assuming that you can actually get information out of DDB, please >send it to freebsd-stable@freebsd.org. I realize that this is a lot of >work for you, but really it's the only way we can get the data we need to >trace the problem. I alias df to 'df -h' on all my machines, running many >vintages of RELENG_4 and RELENG_5, and I've never seen this panic, which >is why I think the stack trace of a dead kernel is our only option here. > >Doug >-- > "The dead cannot be seduced." >From igor_tomrli- Kai, "Lexx" > > Do YOU Yahoo!? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message