From owner-freebsd-stable@FreeBSD.ORG Wed Jul 23 06:38:00 2008 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1F328106564A for ; Wed, 23 Jul 2008 06:38:00 +0000 (UTC) (envelope-from royce@alaska.net) Received: from malik.acsalaska.net (malik.acsalaska.net [209.112.173.227]) by mx1.freebsd.org (Postfix) with ESMTP id F0D528FC08 for ; Wed, 23 Jul 2008 06:37:59 +0000 (UTC) (envelope-from royce@alaska.net) Received: from [192.168.254.100] (66-230-109-191-rb1.nwc.dsl.dynamic.acsalaska.net [66.230.109.191]) by malik.acsalaska.net (8.14.1/8.14.1) with ESMTP id m6N6bwrM014450 for ; Tue, 22 Jul 2008 22:37:59 -0800 (AKDT) (envelope-from royce@alaska.net) Message-ID: <4886D1E9.1090905@alaska.net> Date: Tue, 22 Jul 2008 22:38:33 -0800 From: Royce Williams User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.14) Gecko/20080421 Lightning/0.8 Thunderbird/2.0.0.14 Mnenhy/0.7.5.0 MIME-Version: 1.0 To: freebsd-stable@FreeBSD.org References: <488638DA.7010005@alaska.net> <20080723053404.GA46617@eos.sc1.parodius.com> In-Reply-To: <20080723053404.GA46617@eos.sc1.parodius.com> X-Enigmail-Version: 0.95.6 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-ACS-Spam-Status: no X-ACS-Scanned-By: MD 2.63; SA 3.2.3; spamdefang 1.122 Cc: Subject: Re: 6.3-RELEASE-p3 recurring panics on multiple SM PDSMi+ X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Jul 2008 06:38:00 -0000 Jeremy Chadwick wrote, on 7/22/2008 9:34 PM: > On Tue, Jul 22, 2008 at 11:45:30AM -0800, Royce Williams wrote: >> We have 10 SuperMicro PDSMi+ 5015M-MTs that are panic'ing every few >> days. This started shortly after upgrade from 6.2-RELEASE to >> 6.3-RELEASE with freebsd-update. > > We use the same hardware (board and chassis), and have no such problems > running both RELENG_6 and RELENG_7. > > I don't think your issue is specific to the board or chassis. Kris's > explanation makes a lot more sense. :-) Jeremy/Kris/Clifton - Looks like we have consensus. :-) Thanks, all of you, for your helpful insight. I've bumped vm.kmem_size up to 400M on half of the affected boxes, leaving the other half as a control group. I'll report back once I have something to report. Royce -- Royce D. Williams - http://royce.ws/ I learn by going where I have to go. - Theodore Roethke