From owner-freebsd-questions@FreeBSD.ORG Fri Sep 14 20:47:51 2007 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 02B3816A421 for ; Fri, 14 Sep 2007 20:47:51 +0000 (UTC) (envelope-from iaccounts@ibctech.ca) Received: from pearl.ibctech.ca (pearl.ibctech.ca [208.70.104.210]) by mx1.freebsd.org (Postfix) with ESMTP id 9461F13C47E for ; Fri, 14 Sep 2007 20:47:50 +0000 (UTC) (envelope-from iaccounts@ibctech.ca) Received: (qmail 86490 invoked by uid 1002); 14 Sep 2007 20:47:50 -0000 Received: from iaccounts@ibctech.ca by pearl.ibctech.ca by uid 89 with qmail-scanner-1.22 (spamassassin: 2.64. Clear:RC:1(208.70.104.100):. Processed in 11.3834 secs); 14 Sep 2007 20:47:50 -0000 Received: from unknown (HELO ?192.168.30.110?) (steve@ibctech.ca@208.70.104.100) by pearl.ibctech.ca with (DHE-RSA-AES256-SHA encrypted) SMTP; 14 Sep 2007 20:47:38 -0000 Message-ID: <46EAF373.3000903@ibctech.ca> Date: Fri, 14 Sep 2007 16:47:47 -0400 From: Steve Bertrand User-Agent: Thunderbird 2.0.0.6 (Windows/20070728) MIME-Version: 1.0 To: Ian Lord References: <0b9d01c7f6f1$6ecedb30$6400a8c0@msdi.local> In-Reply-To: <0b9d01c7f6f1$6ecedb30$6400a8c0@msdi.local> X-Enigmail-Version: 0.95.3 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-questions@freebsd.org Subject: Re: kernel log messages X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Sep 2007 20:47:51 -0000 > +pid 85092 (httpd), uid 80: exited on signal 11 pid 85097 (httpd), uid > > +80: exited on signal 11 pid 85099 (httpd), uid 80: exited on signal 11 > > Is this something I should care about ? First time I see this, and since the > os mention it to me, I guess it's something important :-) In almost every case I've seen posted to this list regarding sig 11 problems, the response has nearly always been replace memory. Even in a case of my own a few years back, said recommendation fixed my problem. (I think mine was during a buildworld). Aside from that, I've also heard of heat (as already stated this thread), and flaky power supply. Steve