From owner-freebsd-current@FreeBSD.ORG Wed Jul 7 16:25:38 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 87E2F16A4CE for ; Wed, 7 Jul 2004 16:25:38 +0000 (GMT) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3FA0443D53 for ; Wed, 7 Jul 2004 16:25:38 +0000 (GMT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (localhost [127.0.0.1]) by fledge.watson.org (8.12.11/8.12.11) with ESMTP id i67GOxAx041714; Wed, 7 Jul 2004 12:24:59 -0400 (EDT) (envelope-from robert@fledge.watson.org) Received: from localhost (robert@localhost)i67GOxL7041711; Wed, 7 Jul 2004 12:24:59 -0400 (EDT) (envelope-from robert@fledge.watson.org) Date: Wed, 7 Jul 2004 12:24:59 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: Daniel Lang In-Reply-To: <20040707162154.GB45200@atrbg11.informatik.tu-muenchen.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: current@freebsd.org Subject: Re: panic: m_copym, length > size of mbuf chain X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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: Wed, 07 Jul 2004 16:25:38 -0000 On Wed, 7 Jul 2004, Daniel Lang wrote: > Dear Robert, > > Robert Watson wrote on Wed, Jul 07, 2004 at 11:11:02AM -0400: > > What kernel configuration are you running with, and what system tunables? > [..] > > Bruce Simpson has asked the same thing. I'll just attach my answer to > him to this mail. > > It does not, however, include the system tunables, and I cannot include > a sysctl -a output right now (the machine just crashed again, this time > again inside of WITNESS, a separate email will document this). But IIRC > I have removed all tunables from /etc/sysctl.conf and /boot/loader.conf > > As I told Bruce, I have never set debug.mpsafenet (in case you are > especially interested in this tunable). Yeah, that's one of the ones I was particularly interested in :-). Just to try ruling out possibilities -- have you run an extensive set of hardware diagnostics? Most server class hardware ships with a decent diagnostics disk, and I'm sure we can find some for you in the event your hardware didn't come with some. While it's quite possibly a software problem, tracking hardware problems using software symptoms constitutes undesirable pain and so it wouldn't hurt to give that a spin. I remember seing your earlier e-mails about running with WITNESS increasing the chances of pain -- this could be a bug in WITNESS as you suggest, or it could be that WITNESS increases the opportunities for a variety of locking related races by increasing the cost of lock/unlock operations. Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Principal Research Scientist, McAfee Research