From owner-freebsd-current Sun May 31 16:59:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA18103 for freebsd-current-outgoing; Sun, 31 May 1998 16:59:38 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from m2.findmail.com (m2.findmail.com [209.185.96.135]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id QAA18093 for ; Sun, 31 May 1998 16:59:35 -0700 (PDT) (envelope-from brianfeldman@hotmail.com) Received: (qmail 9457 invoked by uid 505); 31 May 1998 23:59:20 -0000 Date: 31 May 1998 23:59:20 -0000 Message-ID: <19980531235920.9456.qmail@m2.findmail.com> From: "Brian Feldman" Subject: Re: really bad inodedep crash In-Reply-To: To: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Nope, single CPU, single user (not boot -s, just me only using it), etc. Brian > thanks.. > Is this SMP? > > > On Sun, 31 May 1998, The Super-User wrote: > > > Well, there goes another crash. I got a VERY strange crash, something about inodedep, by pressing ^Z during a make in a port dir; I haven't been able to recreate this crash, and the core seemed to be corrupted (or maybe the system was actually that way) because a backtrace was showing two undefined functions continually looping. I'd know more, but this vmcore got corrupted I guess :-/. Ahh well, if I can ever find something else like this again, I'll post again. BTW, this is with SoftUpdates, but a few days ago my computer DID crash with no softupdates, and only async; go figure. > > > > Brian Feldman > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-current" in the body of the message > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message