From owner-freebsd-stable@freebsd.org Mon Jul 10 20:00:32 2017 Return-Path: Delivered-To: freebsd-stable@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 A88C1DAFEC7 for ; Mon, 10 Jul 2017 20:00:32 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: from mail-qt0-x22d.google.com (mail-qt0-x22d.google.com [IPv6:2607:f8b0:400d:c0d::22d]) (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 5CACB7632C; Mon, 10 Jul 2017 20:00:32 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: by mail-qt0-x22d.google.com with SMTP id i2so82361601qta.3; Mon, 10 Jul 2017 13:00:32 -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:content-transfer-encoding:in-reply-to :user-agent; bh=rL1pz4DhiF5mV9zXFOhEM9yvFJ/aFje8iTs4Y+aa6ns=; b=iLtXkgp45yITJKwI9tmtoqqW4VNYFqUQ46dC9lTndpV/2y8bi0qkYy/oPsVN/O8n1S Uf47PQF7iO/+NTYFbhFL0eyN5fsg2bUpKuydUAApEex/CqVgncmVs4Ul+Gym65E3b+5Q Rjrw3rrPHTrzSUm4Ko2FTkjyi2M4WMX5qDBWbOWlhhweZ4IvO+oUTem63ZhbAsPmhhVz l5MTX1ej8xC/TsRNGFeeM5U2WFjTGxh9S/zmcIR5FU8xMgxdprQJ2hBN/eN36+/29efk sLXQwE3w66SlLq8t0Zp1WAPiPJBwHonwTHN+N6/DTW/aErj5QS7VIqOlfEcd6ySCW5dD PfuA== 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 :content-transfer-encoding:in-reply-to:user-agent; bh=rL1pz4DhiF5mV9zXFOhEM9yvFJ/aFje8iTs4Y+aa6ns=; b=IfAdSBsySzx9kH26XYthgxGUWx8/BxKiVgcgdCOXPPZE2WqvEcOIsJ7DBanbmeC5+j tIggTdjMlEhhmiqiCavOAArYB2PuRXNvu53ly3ST4TeJfS4nketX5jh6wgPGAHTYMG2C inLK2Es2p2w1cMoab3j1/sOjXX6syWDrPENM0re8mfmnfX3+F0nwrEcYluTwa4Si9MBv 07++uhegMThtLDXze3Vz2FMDmcMHsUJv3WfBsWBLrw/FueOSNSgbYvKKin3eayRP7EFH IHRYupR+m4EilsEN8NLF1eFaxwxEAHVgTCglrsWNjMFwVm7PS7xjGj7n3DBFT+EsKGvY Vivw== X-Gm-Message-State: AIVw112yKj1Jhay5urIntFyIt055aBB6Jw2vW36SwJROo1YZYNspsxdE SHAiftdz5xAsGQ== X-Received: by 10.237.61.91 with SMTP id h27mr7121287qtf.1.1499716830178; Mon, 10 Jul 2017 13:00:30 -0700 (PDT) Received: from wkstn-mjohnston.west.isilon.com (c-76-104-201-218.hsd1.wa.comcast.net. [76.104.201.218]) by smtp.gmail.com with ESMTPSA id b42sm3067786qkb.17.2017.07.10.13.00.28 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 10 Jul 2017 13:00:29 -0700 (PDT) Sender: Mark Johnston Date: Mon, 10 Jul 2017 13:00:05 -0700 From: Mark Johnston To: =?iso-8859-1?Q?Jos=E9_G=2E?= Juanino Cc: David Boyd , "David.Boyd49@twc.com" , "freebsd-stable@freebsd.org" , kib@FreeBSD.org, re@FreeBSD.org Subject: Re: [SOLVED] Re: Panic with FreeBSD 11.0-RC2 VM-IMAGE when starting vboxservice Message-ID: <20170710200005.GA82530@wkstn-mjohnston.west.isilon.com> References: <1499636909729.64073@secc.org> <20170710192441.3wglwfwv7jpnt7tb@riemann> <20170710194750.xwuopzrwapnh3c6k@riemann> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20170710194750.xwuopzrwapnh3c6k@riemann> User-Agent: Mutt/1.8.3 (2017-05-23) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Jul 2017 20:00:32 -0000 On Mon, Jul 10, 2017 at 09:47:50PM +0200, José G. Juanino wrote: > El Monday 10 de July a las 21:24:41 CEST, José G. Juanino escribió: > >El Sunday 09 de July a las 23:48:29 CEST, David Boyd escribió: > >>With latest VM-IMAGE (vmdk) for 11.1-RC2 system panics. I haven't > >>been able to process the panic completely, but the backtrace looks > >>mysteriously similar to those provided with PR219146. > >> > >> > >>Initially, the VM-IMAGE booted just fine. The VM-IMAGE is then > >>configured as a VirtualBox client. The panic occurs on subsequent > >>reboots when attempting to start vboxservice. > >> > >> > >>Additionally, during the custom configuration process, lsof hangs > >>for more than 2 minutes each time that it is invoked. > >> > >> > >>Please let me know exactly what information is needed to correct > >>this problem. I will be able to provide that information no later > >>than Tuesday morning. > >> > > > >Hi, I am also suffering this panic. > > > >I use everyday my Windows 7 host Virtualbox with a FreeBSD guest. I > >upgraded from 11.0 -> 11.1-BETA1 -> 11.1-BETA2 -> 11.1-RC1 with no > >issues. > > > >But after to upgrade to 11.1-RC2, the system panics just after to > >start vboxservice. I have disabled the service at boot in > >/etc/rc.conf, but it does not help: the system crashes just after > >"service vboxservice start" command. > > > >You can get a full crash dump here: > > > >https://pastebin.com/MkxS9GZn > > > >At this moment, I am going to rebuild the virtualbox-ose-additions > >port (running 11.1-RC2) and I will let you know if there is some > >difference. > > I confirm that after rebuild virtualbox-ose-additions port, the panic > goes away. Regards. I suspect that this is a result of r320763. That change removed a field from struct vm_map_entry, which is embedded in struct vm_map. Virtualbox does not reference the fields of struct vm_map directly, but it does call vm_map_pmap(), which is an inline accessor.