From owner-freebsd-stable Fri Jul 27 12:18:47 2001 Delivered-To: freebsd-stable@freebsd.org Received: from smtp1.sentex.ca (smtp1.sentex.ca [199.212.134.4]) by hub.freebsd.org (Postfix) with ESMTP id 72B4037B403 for ; Fri, 27 Jul 2001 12:18:43 -0700 (PDT) (envelope-from mike@sentex.net) Received: from simoeon.sentex.net (pyroxene.sentex.ca [199.212.134.18]) by smtp1.sentex.ca (8.11.2/8.11.1) with ESMTP id f6RJIar79778; Fri, 27 Jul 2001 15:18:36 -0400 (EDT) (envelope-from mike@sentex.net) Message-Id: <5.1.0.14.0.20010727151142.030e0c40@marble.sentex.ca> X-Sender: mdtpop@marble.sentex.ca X-Mailer: QUALCOMM Windows Eudora Version 5.1 Date: Fri, 27 Jul 2001 15:13:00 -0400 To: "Shawn Ramsey" , From: Mike Tancsa Subject: Re: Crashing every two hours! In-Reply-To: <001201c116cc$71253d90$2248a93f@Shawn100> References: <5.1.0.14.0.20010727073615.029e9058@192.168.0.12> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I wonder if this commit today had anything to do with the problem you were seeing iedowse 2001/07/27 07:06:02 PDT Modified files: (Branch: RELENG_4) sys/kern kern_exit.c kern_sig.c Log: Back out kern_exit.c revision 1.92.2.4 and kern_sig.c revision 1.72.2.7 (SIGCHLD SIG_IGN signal handling changes) until the issue with "fault on nofault entry" panics in exit1() is resolved. The fault seems to occur when p->p_pptr->p_sigacts is dereferenced in exit1(). It is probably some kind of a race with the exiting of the parent, but I'm unsure of the details. Revision Changes Path 1.92.2.5 +4 -5 src/sys/kern/kern_exit.c 1.72.2.8 +4 -6 src/sys/kern/kern_sig.c At 11:46 AM 7/27/01 -0700, Shawn Ramsey wrote: >----- Original Message ----- >From: "Mike Tancsa" >To: "Shawn Ramsey" ; >Sent: Friday, July 27, 2001 4:37 AM >Subject: Re: Crashing every two hours! > > > > At 09:55 PM 7/26/2001 -0700, Shawn Ramsey wrote: > > >I just upgraded one of our servers from 4.1.1. That server had never > > > > > > Can you provide some more details about hardware, kernel config etc > > ? Also, see the handbook on how to provide a crash dump. With that info, > > people might be able to better diagnose what your problem is. > > > > ---Mike > >Well, I downgraded the system to 4.3-RELEASE. The only difference in the way >I did things was, I did not compile profiled libs, and I compiled the >compatibility libraries. I forgot to include the compatiblity libs when I >upgraded to Stable. Im not sure if using old compat libs would cause the >problems we were having, but going to 4.3 and compiling hte compat libs has >fixed the problem. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message