From owner-freebsd-current@freebsd.org Tue Jul 26 17:03:59 2016 Return-Path: Delivered-To: freebsd-current@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 75AC7BA5957 for ; Tue, 26 Jul 2016 17:03:59 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from bigwig.baldwin.cx (bigwig.baldwin.cx [IPv6:2001:470:1f11:75::1]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 568F71621 for ; Tue, 26 Jul 2016 17:03:59 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from ralph.baldwin.cx (c-73-231-226-104.hsd1.ca.comcast.net [73.231.226.104]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 191FCB95D; Tue, 26 Jul 2016 13:03:58 -0400 (EDT) From: John Baldwin To: freebsd-current@freebsd.org Cc: Randy Westlund , Jung-uk Kim Subject: Re: Panic when loading vboxdrv module Date: Tue, 26 Jul 2016 09:22:47 -0700 Message-ID: <2767658.4fcdAjrkcG@ralph.baldwin.cx> User-Agent: KMail/4.14.3 (FreeBSD/10.3-STABLE; KDE/4.14.3; amd64; ; ) In-Reply-To: <20160726030815.GB12568@gmail.com> References: <20160725191314.GA10757@gmail.com> <7875d0e7-6cbd-6184-3f34-a2fbd00788b1@niksun.com> <20160726030815.GB12568@gmail.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Tue, 26 Jul 2016 13:03:58 -0400 (EDT) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.22 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: Tue, 26 Jul 2016 17:03:59 -0000 On Monday, July 25, 2016 11:08:15 PM Randy Westlund wrote: > On Mon, Jul 25, 2016 at 07:43:32PM -0400, Jung-uk Kim wrote: > > Oops, I meant INVARIANTS. Anyway, it should be fixed in r419083. I > > understand you have a panic with aio(4) but that's a separate issue. > > > > Jung-uk Kim > > Should I create a new PR for virtualbox and aio, or is this already > known? Please. cc me on it since I've hacked on aio in 11/HEAD. -- John Baldwin