From owner-freebsd-current@FreeBSD.ORG Fri Jan 16 12:19:18 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4377F1065670 for ; Fri, 16 Jan 2009 12:19:18 +0000 (UTC) (envelope-from matrix@itlegion.ru) Received: from corpmail.itlegion.ru (corpmail.itlegion.ru [84.21.226.211]) by mx1.freebsd.org (Postfix) with SMTP id 6EAB08FC18 for ; Fri, 16 Jan 2009 12:19:16 +0000 (UTC) (envelope-from matrix@itlegion.ru) Received: (qmail 52582 invoked from network); 16 Jan 2009 14:52:34 +0300 Received: from unknown (HELO ?192.168.0.12?) (192.168.0.12) by 84.21.226.211 with SMTP; 16 Jan 2009 14:52:34 +0300 Message-ID: <4970740D.8010609@itlegion.ru> Date: Fri, 16 Jan 2009 14:48:29 +0300 From: Artem Kuchin Organization: IT Legion User-Agent: Thunderbird 2.0.0.19 (Windows/20081209) MIME-Version: 1.0 To: Alexander Best References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: Re: FreeBSD panics with 64GiB of RAM X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Jan 2009 12:19:18 -0000 Alexander Best ?????: > unfortunately there's (probably) nobody here using a computer with that much > memory. finding the problem without using similar hardware in order to have a > closer look at the problem is very difficult i guess. > > But how do you know if it is really memory related? Take out half of the memory and see what happens. If it still crashed then take out all but one module and see.