From owner-freebsd-current Tue Jul 20 10:12:21 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id A23EE14EAB for ; Tue, 20 Jul 1999 10:12:17 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id KAA05617; Tue, 20 Jul 1999 10:11:35 -0700 (PDT) (envelope-from dillon) Date: Tue, 20 Jul 1999 10:11:35 -0700 (PDT) From: Matthew Dillon Message-Id: <199907201711.KAA05617@apollo.backplane.com> To: "Reginald S. Perry" Cc: freebsd-current@FreeBSD.ORG Subject: Re: Panics on my SMP system References: <199906130048.RAA15241@trane.lambdawerks.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Hi there, : : I recently had a crash on my SMP system. Actually, I have had a :number of crashes over the past six months, but have just recently had :time to configure the system to get the crash dumps. Like a good :citizen, I filed a problem report (kern/12127). I have now gotten :another crash. I have attached the backtrace from the crash dump. If :you refer to kern/12127, you will get all of the gory details about my :setup.I would like to know two things. Should I file a separate :problem report for this crash? Second, is there somewhere that I :should upload the vmcores and the kernel.debug for the relevant :developer to examine? : :Thanks, : -Reggie How old is your -CURRENT source tree ? Fixes to the pipe code have been made, though they are not 100% complete. If your -CURRENT source tree is more then a few days old I recommend updating it. A number of significant reliability fixes have gone in, including fixes to the pipe code and fixes to certain atomic operations that weren't atomic. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message