From owner-freebsd-current@FreeBSD.ORG Thu Jul 2 20:49:20 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 DEBCC1065676 for ; Thu, 2 Jul 2009 20:49:20 +0000 (UTC) (envelope-from pluknet@gmail.com) Received: from mail-bw0-f216.google.com (mail-bw0-f216.google.com [209.85.218.216]) by mx1.freebsd.org (Postfix) with ESMTP id 3877C8FC1D for ; Thu, 2 Jul 2009 20:49:20 +0000 (UTC) (envelope-from pluknet@gmail.com) Received: by bwz12 with SMTP id 12so1610393bwz.43 for ; Thu, 02 Jul 2009 13:49:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=PkfS81SUZtJL2i/hAuM6ZjANoHtZg9blE9wDynCQ70o=; b=T26Wxp+CLgUySHyAM0Y1/eD2gWfRPiki9oM7+NDh12oPfkJSE5w/8JbGlgZwskPaqc JIFnnsmFgJEcEQq7eSEAWDyp/MUH2pla5Gb88DN0wQ6g8EAs6odaHJ3t3ViiOGot2riH YNCOObhuA0dM0InSVJHs6GvDRNiGuhA6BVctU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=DaN8wiNna5523FbwI+U+ki2++8Bxjm910/bhXplR13z7iGjehcEWXSBFJKdXqpDRuI MkaSylqodRVoWYuMgbGcD3Sa23cvQ67t3OVkfB6jaqmYfWN955VbzqaphJ2LAOcxuEUp rQWFouEStknaRdNzRdPm3775/iBdcqnqcrvCo= MIME-Version: 1.0 Received: by 10.204.103.203 with SMTP id l11mr439059bko.71.1246567759288; Thu, 02 Jul 2009 13:49:19 -0700 (PDT) In-Reply-To: <20090702194444.GK2884@deviant.kiev.zoral.com.ua> References: <20090701192154.GW2884@deviant.kiev.zoral.com.ua> <20090702084149.GE2884@deviant.kiev.zoral.com.ua> <20090702194444.GK2884@deviant.kiev.zoral.com.ua> Date: Thu, 2 Jul 2009 20:49:19 +0000 Message-ID: From: pluknet To: Kostik Belousov Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: alc@freebsd.org, freebsd-current@freebsd.org Subject: Re: Panic during shutdown (cause identified) 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: Thu, 02 Jul 2009 20:49:21 -0000 2009/7/2 Kostik Belousov : > On Thu, Jul 02, 2009 at 11:37:01AM -0500, Greg Rivers wrote: >> Please let me know if I can help with further testing/debugging. BTW, I >> did not customize the amd configuration; I was using the stock >> configuration from the base system. > > The information you provided about amd(8) causing the problem was crusial. > The issue is that amd locks its pages with mlockall(2), and the code > neglected to account the wired mappings, but did not forgot to decrease > their swap share on unmapping. > > Patch below fixed the issue for me. I can confirm that simply staring amd(8) daemon and then reboot would cause such panic in swap accounting. I saw a dozen messages "negative vmsize for uid = 0" in time just before panic. This patch fixes that for me. my 2c. -- wbr, pluknet