From owner-freebsd-stable@FreeBSD.ORG Tue Aug 17 11:48:04 2004 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 820F116A4CE for ; Tue, 17 Aug 2004 11:48:04 +0000 (GMT) Received: from gw02.mail.saunalahti.fi (gw02.mail.saunalahti.fi [195.197.172.116]) by mx1.FreeBSD.org (Postfix) with ESMTP id E686143D60 for ; Tue, 17 Aug 2004 11:48:03 +0000 (GMT) (envelope-from djv@mbnet.fi) Received: from [192.168.1.3] (DCLXIV.dsl.saunalahti.fi [62.142.242.64]) by gw02.mail.saunalahti.fi (Postfix) with ESMTP id 90D2217926; Tue, 17 Aug 2004 14:48:02 +0300 (EEST) Message-ID: <4121F07D.4040400@mbnet.fi> Date: Tue, 17 Aug 2004 14:48:13 +0300 From: Tuomo Latto User-Agent: Mozilla Thunderbird 0.7.2 (Windows/20040707) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Gary Kline References: <20040816193648.GA7737@nmt.edu> <20040816234322.GA34841@thought.org> <20040817045025.GA25236@nmt.edu> In-Reply-To: <20040817045025.GA25236@nmt.edu> X-Enigmail-Version: 0.84.2.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-stable@freebsd.org Subject: Re: 5.2.1-RELEASE-p9 and system crashes with samba X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Aug 2004 11:48:04 -0000 William D. Colburn (aka Schlake) wrote: > The memory was good when this was a linux box two weeks ago, and > memchecking it now found nothing. > > What I did find is that running samba causes a "fatal panic 12" in the > kernel, and it reboots. Since we know it is samba, and I can narrow it > down to a single compile time option, and make it happen at will now, I > can finally produce a good bug report! > > On Mon, Aug 16, 2004 at 04:43:22PM -0700, Gary Kline wrote: > >> It time for you to check your memory. memtest and memtest86 >> are one place to start. You might want to keep a log of >> your run and grep for "FAIL" after some hours. Considering that the system in question is CURRENT and there's a separate list for that branch, I think this thread should be moved there. -- Tuomo ... Scrute the inscrutable, eff the ineffable