From owner-freebsd-current@FreeBSD.ORG Wed Sep 12 07:56:59 2012 Return-Path: Delivered-To: current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C1F371065673 for ; Wed, 12 Sep 2012 07:56:59 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 1B2138FC17 for ; Wed, 12 Sep 2012 07:56:58 +0000 (UTC) Received: from porto.starpoint.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id KAA05590; Wed, 12 Sep 2012 10:56:56 +0300 (EEST) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1TBhoe-0006HL-EX; Wed, 12 Sep 2012 10:56:56 +0300 Message-ID: <50504047.3020409@FreeBSD.org> Date: Wed, 12 Sep 2012 10:56:55 +0300 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:15.0) Gecko/20120901 Thunderbird/15.0 MIME-Version: 1.0 To: =?ISO-8859-1?Q?Olivier_Cochard-Labb=E9?= References: <20120911161234.GA1313@glenbarber.us> <20120911161954.GP44854@FreeBSD.org> <20120911163237.GA1256@glenbarber.us> In-Reply-To: X-Enigmail-Version: 1.4.3 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Cc: current@FreeBSD.org Subject: Re: [panic] 10-CURRENT r239865: General protection fault (sysctl) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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: Wed, 12 Sep 2012 07:56:59 -0000 on 12/09/2012 10:30 Olivier Cochard-Labbé said the following: > On Tue, Sep 11, 2012 at 6:32 PM, Glen Barber wrote: >>> >>> I'd blame this one: >>> >>> http://lists.freebsd.org/pipermail/svn-src-head/2012-September/040236.html >>> >> >> Yes, reverting that commit allows the system to boot. >> > > Hi, > > Same problem on my side (under Virtualbox or on an IBM 3550 M2). This should be fixed already. Sorry for the breakage and for not writing about the fix to this thread. -- Andriy Gapon