From owner-freebsd-hackers@FreeBSD.ORG Fri Feb 15 11:22:56 2013 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 296679B0 for ; Fri, 15 Feb 2013 11:22:56 +0000 (UTC) (envelope-from mike@urgle.com) Received: from cheddar.urgle.com (cheddar.urgle.com [IPv6:2001:470:967d:b:21c:c4ff:fed7:6d44]) by mx1.freebsd.org (Postfix) with ESMTP id E47FF23B for ; Fri, 15 Feb 2013 11:22:55 +0000 (UTC) Received: from mike by cheddar.urgle.com with local (Exim 4.80.1 (FreeBSD)) (envelope-from ) id 1U6JNW-000G72-GQ for freebsd-hackers@freebsd.org; Fri, 15 Feb 2013 11:22:54 +0000 Date: Fri, 15 Feb 2013 11:22:54 +0000 From: Mike Bristow To: "freebsd-hackers@freebsd.org" Subject: Re: dot.core ?? Message-ID: <20130215112254.GA23913@cheddar.urgle.com> References: <1360926085.23144.18.camel@Nerz-PC.home> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <1360926085.23144.18.camel@Nerz-PC.home> User-Agent: Mutt/1.5.21 (2010-09-15) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Feb 2013 11:22:56 -0000 On Fri, Feb 15, 2013 at 12:01:25PM +0100, Loïc BLOT wrote: > Hello, > i have strange problem on one of my FreeBSD 9.1 install. > The server randomly hard reboots. > When i look at dmesg i don't find anything, but there is a strange > entry: > > pid 24931 (dot), uid 0: exited on signal 11 (core dumped) [snip similar] > There is also a dot.core in /root "dot" is a program in the graphviz suit, probably. Someone or something is running it as root, and it attempts to access memory which it has no permission to access, so it is killed and a core dump generated. This memory access is likly to be caused by one of two things: 1) a bug in dot; 2) hardware memory corruption I suggest you boot memtest86 or similar to see if you can prove the hardware fault - especially if you can track down who or what is running dot and show that it fails randomly (e.g., if you run it with the same input it does not fail all the time). Cheers, Mike -- Mike Bristow mike@urgle.com http://www.urgle.com/~mike/CV/