From owner-freebsd-emulation@freebsd.org Thu Apr 20 13:57:08 2017 Return-Path: Delivered-To: freebsd-emulation@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 558B9D48AC7 for ; Thu, 20 Apr 2017 13:57:08 +0000 (UTC) (envelope-from arcade@b1t.name) Received: from limbo.b1t.name (limbo.b1t.name [78.25.32.206]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 017CC361 for ; Thu, 20 Apr 2017 13:57:06 +0000 (UTC) (envelope-from arcade@b1t.name) Received: from [172.29.1.87] (probe.42.lan [172.29.1.87]) by limbo.b1t.name (Postfix) with ESMTPSA id 4510295 for ; Thu, 20 Apr 2017 16:56:52 +0300 (EEST) Subject: Re: core dump in vboxdrv memory management on 11-STABLE To: freebsd-emulation@freebsd.org References: <5e20615e-9d8e-fe84-8d86-ec0571906646@b1t.name> From: Volodymyr Kostyrko Message-ID: <2ee19cd9-c1c7-62f3-d95f-c7f562302a3d@b1t.name> Date: Thu, 20 Apr 2017 16:56:52 +0300 User-Agent: Mozilla/5.0 (X11; DragonFly x86_64; rv:49.0) Gecko/20100101 Firefox/49.0 SeaMonkey/2.46 MIME-Version: 1.0 In-Reply-To: <5e20615e-9d8e-fe84-8d86-ec0571906646@b1t.name> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=b1t.name; s=dkim; t=1492696613; bh=HieXJCXNFqutPylwtVc3OvySb+/vSTmudIgJcXld+QA=; h=Subject:To:References:From:Message-ID:Date:MIME-Version:In-Reply-To:Content-Type:Content-Transfer-Encoding; b=Bk1hO8+K7MdJPHex1uye38c9PfpCWdLMmTqJPe52z1J7jZU9dqQBhfslinTQjxgo7VZvJKOFz7iyfQ5yvC/VsycPGNk2xGA8awichkHdWNn6nPv00xTx8wPAiT7zBogK6cRu2U7FGxBWuIjWhWsqL9mEbyo0zwpLQEQ6q773BYc= X-BeenThere: freebsd-emulation@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Development of Emulators of other operating systems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Apr 2017 13:57:08 -0000 Volodymyr Kostyrko wrote: > Hi all. > > Is anyone else seeing this or that's me breaking something? > > Unread portion of the kernel message buffer: > panic: page 0xfffff80404001980 is PG_FICTITIOUS or PG_MARKER > cpuid = 1 Just in case someone would step into it: my kernel was based off MINIMAL which has full debugging enabled. Turning all debugging off in the kernel cleared the problem. -- Sphinx of black quartz judge my vow.