Date: 31 May 1998 23:59:20 -0000 From: "Brian Feldman" <brianfeldman@hotmail.com> To: freebsd-current@FreeBSD.ORG Subject: Re: really bad inodedep crash Message-ID: <19980531235920.9456.qmail@m2.findmail.com> In-Reply-To: <Pine.BSF.3.95.980531160709.11289H-100000@current1.whistle.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19980531235920.9456.qmail>