From owner-freebsd-current@freebsd.org Thu May 31 11:04:48 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 48BC0F71C24 for ; Thu, 31 May 2018 11:04:48 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: from mail-pl0-x22b.google.com (mail-pl0-x22b.google.com [IPv6:2607:f8b0:400e:c01::22b]) (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 B30287DEF8; Thu, 31 May 2018 11:04:47 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: by mail-pl0-x22b.google.com with SMTP id 31-v6so3113537plc.4; Thu, 31 May 2018 04:04:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=W8AyVLcRiZv/WWc0nuIn26WGQt+vv7MNFnzB6TM8qxQ=; b=vGMZlJDnPNAsBv8qAlu6uy+EN2+pnPI+shNpP5ED1hZ+LKv+FF7G+85aKURyNu4kEh l7jqjCQO8mTaN62KooCIDPfv6DAOqCtC4rX6qBTJ04xotekq9zWcjpZ59uzjGWbYyTDk m8cuWnOukimA94nA5DAqlIofZ/fm40qu/RuRUwCGdc9tS84XODYtP0s+X06U8xjD41Me H0dkvEhsV4M+3RgG9a1Dk3+9T4/w7zMwktUHFqcQMwCtfnHBsWbbbTf9wiDVrw5yOrvM 8mhzrLWXYcvnU0e09IeH/cDiSMJo3du5wugOw9w8shDd5/0ai4kUbKW+QvqVwoGegTUQ a7dg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:date:from:to:cc:subject:message-id :references:mime-version:content-disposition:in-reply-to:user-agent; bh=W8AyVLcRiZv/WWc0nuIn26WGQt+vv7MNFnzB6TM8qxQ=; b=YV/7x2PqXpCwgvzb2Y86MdkUjlzzeKxVuDbwsKP+WVLII+TdzNmTI8Xqty6ljVwuEl hQqHA2HOpML/q4NnvsKq2bBZsCOb65fZ/8RQsClym9jmM8gyf5822eyWZO5C6kuoY0+s RZ7KK+6ZTCTT8jwiQtIuYotslL9F5nkyy55DgPCEy+VBOpWoJgV4nFcvw5LnjB1I/Ew4 K40ndh22t4PTujbWpH+5hOU2oAyUCa4A+SMM1DK+TuvLGx9R4kZ7HFsCn7MutzXiYAat 6k2/ZjdP2rVCuGwl6Dc7FU32+swQC215gGxwIbXm/K7cpYq7IBZ6NvC7UIprF98vbkXt ChOA== X-Gm-Message-State: ALKqPwfe0eJF1URpGXtvV4MpfWuV7HwpxQz3UOKUhloks9WrrdBp9Sga 6+/kTIgoH+AyCpyDpceog9hsPA== X-Google-Smtp-Source: ADUXVKJh7PIaPVa4Y61FR9LdDcziDqx5S3m1NNMdv/NXLE63RW5TvssJP5x5CEECVe5+TUljm1zH5g== X-Received: by 2002:a17:902:7841:: with SMTP id e1-v6mr6644539pln.197.1527764686405; Thu, 31 May 2018 04:04:46 -0700 (PDT) Received: from raichu (toroon0560w-lp140-02-70-49-169-156.dsl.bell.ca. [70.49.169.156]) by smtp.gmail.com with ESMTPSA id z192-v6sm1522375pgz.6.2018.05.31.04.04.45 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 31 May 2018 04:04:45 -0700 (PDT) Sender: Mark Johnston Date: Thu, 31 May 2018 07:04:40 -0400 From: Mark Johnston To: Andriy Gapon Cc: "Jonathan T. Looney" , FreeBSD Current Subject: Re: panic: vm_phys_free_pages: page 0x... has unexpected order 0 Message-ID: <20180531110433.GA41152@raichu> References: <932853d2-16f9-67c0-fcf8-745bb5e358d4@FreeBSD.org> <783f525c-d1ab-f4cd-9e3e-64d2e70f549b@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <783f525c-d1ab-f4cd-9e3e-64d2e70f549b@FreeBSD.org> User-Agent: Mutt/1.9.5 (2018-04-13) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 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, 31 May 2018 11:04:48 -0000 On Thu, May 31, 2018 at 10:10:40AM +0300, Andriy Gapon wrote: > On 31/05/2018 05:04, Jonathan T. Looney wrote: > > On Tue, May 29, 2018 at 10:18 AM, Andriy Gapon > > wrote: > > > > > > [ping] > > > > On 21/05/2018 11:44, Andriy Gapon wrote: > > > > > > FreeBSD 12.0-CURRENT amd64 r332472 > > > Does this panic ring a bell to anyone? > > > Has it already been fixed? > > > Thank you! > > > > > > Is there any chance that r333703 fixes this problem for you? It fixes a race > > that can manifest itself in other ways. I'm honestly not sure whether it could > > also cause this problem. > > Thank you for the suggestion. > I guess it's worth trying that fix. > I'll report back in a while. r333703 fixes a bug in r332974, while the problem was reported on r332472, so it won't address the crash.