From owner-freebsd-stable@FreeBSD.ORG Sat Jun 20 07:23:43 2015 Return-Path: Delivered-To: stable@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 63784412 for ; Sat, 20 Jun 2015 07:23:43 +0000 (UTC) (envelope-from trtrmitya@gmail.com) Received: from mail-la0-x230.google.com (mail-la0-x230.google.com [IPv6:2a00:1450:4010:c03::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id DC087E12 for ; Sat, 20 Jun 2015 07:23:42 +0000 (UTC) (envelope-from trtrmitya@gmail.com) Received: by labko7 with SMTP id ko7so85644094lab.2 for ; Sat, 20 Jun 2015 00:23:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date :content-transfer-encoding:message-id:references:to; bh=azvKkBG5IUe8h14Qka8ePCgZWXGNm75u+r8fBp3UQVg=; b=wwmQWHbi2JrOeR4ONaHMFCmyHqPkdEM0748TT1vD+JLouWC1N+x36CC3/bB0S8P0MO QtXjAdPf8TulcISFqMjH1GoTJmI4sl16bcDdCfYJxuUp+QmNj+382jIiJyzdSZgDZAjX B72NAhM2ZfmCbdXd2b/zAXYS2HeMgvagDfwFmGco4dSOvC59AIuTQKuBnWMLmr0XnxCa WRX/AHreTSa8Loyt/ncmh515Avj4wtddsZDI/wLPgqWRkDKknHf3NINPT1vD/kOqdjSl WeH1DDVY6kzVV7G5/aXTcNkIp8Jzzk9+JLIwvL53noMpSZPxGumryP+i6/JnaaZ9ncRe CDYw== X-Received: by 10.112.171.101 with SMTP id at5mr21496690lbc.66.1434785021018; Sat, 20 Jun 2015 00:23:41 -0700 (PDT) Received: from [10.0.1.6] (broadband-5-228-251-108.nationalcablenetworks.ru. [5.228.251.108]) by mx.google.com with ESMTPSA id q3sm3027669laa.30.2015.06.20.00.23.40 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 20 Jun 2015 00:23:40 -0700 (PDT) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2098\)) Subject: Re: panic: wm_page_unwire From: Dmitry Sivachenko In-Reply-To: <8436D969-5AF2-4189-A509-B44669906AEB@gmail.com> Date: Sat, 20 Jun 2015 10:23:39 +0300 Content-Transfer-Encoding: quoted-printable Message-Id: <60FB4B9C-CC80-4269-8C94-F9DE3D98EE0D@gmail.com> References: <8436D969-5AF2-4189-A509-B44669906AEB@gmail.com> To: FreeBSD Stable ML X-Mailer: Apple Mail (2.2098) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 20 Jun 2015 07:23:43 -0000 > On 19 =D0=B8=D1=8E=D0=BD=D1=8F 2015 =D0=B3., at 22:57, Dmitry = Sivachenko wrote: >=20 > Hello, >=20 > got this panic today on my 10.1-STABLE #0 r279956 box: >=20 > Well, I tracked this down a bit. Rather easy way to panic -stable box = (mine is r279956), but I can't reliably reproduce this. It happens when there is a process running which mmap()+mlock() some = file, and while it is running this file is modified on disk (not rm+mv, but open the same file, truncate and write some other data = into it). After process exits, system will panic with high probability. So far I got 2 cases: 1) run process which mlock()'s a file; modify that file; stop process = and system panics 2) run process which mlock()'s a file; modify that file; stop process = [no panic so far]; modify that file again and system panics. Panic message is the same: panic: vm_page_unwire: page 's wire = count is zero=