Return to BSD News archive
Newsgroups: comp.os.386bsd.questions Path: sserve!newshost.anu.edu.au!munnari.oz.au!network.ucsd.edu!sdd.hp.com!saimiri.primate.wisc.edu!zaphod.mps.ohio-state.edu!wupost!uunet!quack!mrapple From: mrapple@quack.kfu.com (Nick Sayer) Subject: panic, panic, panic Message-ID: <f0zoLRd@quack.kfu.com> Organization: The Duck Pond public unix: +1 408 249 9630, log in as 'guest'. Date: 15 Mar 1993 00:52:39 UTC Lines: 29 I am running bsd386 on a 486 with 16M of RAM. I obtained the bin01 and src01 distributions as well as patchkit-0.2.1.tar.Z and patchset84-110-fixed89.tar. I have reconfiged, recompiled and installed the new kernel (I still have to manually create vers.c. The Makefile does not attempt to run newvers.sh). I have recompiled all of the source, except usr.bin. I can't get it to go all the way through 'make ; make install' on usr.bin. The system will consistently panic while building usr.bin. Not in the same place every time, but nevertheless, it won't make it all the way through. And it's seemingly a different panic most of the time. I've seen four trap panics, two syscall panics, and the rest happen either while I was logged in remotely (and therefore couldn't see what the message was. Not that being there would have helped. It goes by so damn quickly. And naturally savecore isn't saving an image in /var/crash for some reason. That would be FAR too easy) or because the message doesn't stay around long enough to be readable. The good news is that it used to freeze up. Now it just panics too often to be useful. This is starting to get really rediculously frustrating. -- Nick Sayer <mrapple@quack.kfu.com> | "We sacrifice every third N6QQQ @ N0ARY.#NOCAL.CA.USA.NOAM | religious nut. The second one +1 408 249 9630, log in as 'guest' | just left." PGP 2.1 public key via finger | -- sign on door.