From owner-freebsd-current@FreeBSD.ORG Sat Aug 10 20:25:28 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 106FFC91 for ; Sat, 10 Aug 2013 20:25:28 +0000 (UTC) (envelope-from freebsd-current@m.gmane.org) Received: from plane.gmane.org (plane.gmane.org [80.91.229.3]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id C36F32ECD for ; Sat, 10 Aug 2013 20:25:27 +0000 (UTC) Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1V8Fj3-0003Y7-CS for freebsd-current@freebsd.org; Sat, 10 Aug 2013 22:25:25 +0200 Received: from a91-154-115-217.elisa-laajakaista.fi ([91.154.115.217]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sat, 10 Aug 2013 22:25:25 +0200 Received: from rakuco by a91-154-115-217.elisa-laajakaista.fi with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sat, 10 Aug 2013 22:25:25 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-current@freebsd.org From: Raphael Kubo da Costa Subject: Re: panic on boot with fresh current Date: Sat, 10 Aug 2013 23:25:13 +0300 Lines: 6 Message-ID: <864nax2t06.fsf@orwell.Elisa> References: <20130810112410.GA27286@devbox.vnode.local> <52066DE0.2060305@shatow.net> <52067537.2070309@shatow.net> <20130810174407.GD4972@kib.kiev.ua> <20130810174547.GE4972@kib.kiev.ua> <20130810182109.GG4972@kib.kiev.ua> Mime-Version: 1.0 Content-Type: text/plain X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: a91-154-115-217.elisa-laajakaista.fi User-Agent: Gnus/5.130008 (Ma Gnus v0.8) Emacs/24.3 (berkeley-unix) Cancel-Lock: sha1:FyZEHboDmJBXMfWIQ6yVdYr4sSg= X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 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: Sat, 10 Aug 2013 20:25:28 -0000 Konstantin Belousov writes: > The right fix looks to be just what the panic message told, please try > this: The patch managed to fix the crash here at least.