From owner-freebsd-current@FreeBSD.ORG Tue Mar 4 05:13:47 2008 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 9305A1065675; Tue, 4 Mar 2008 05:13:47 +0000 (UTC) (envelope-from sam@errno.com) Received: from ebb.errno.com (ebb.errno.com [69.12.149.25]) by mx1.freebsd.org (Postfix) with ESMTP id 75BC38FC14; Tue, 4 Mar 2008 05:13:47 +0000 (UTC) (envelope-from sam@errno.com) Received: from trouble.errno.com (trouble.errno.com [10.0.0.248]) (authenticated bits=0) by ebb.errno.com (8.13.6/8.12.6) with ESMTP id m245Dkb9067042 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 3 Mar 2008 21:13:46 -0800 (PST) (envelope-from sam@errno.com) Message-ID: <47CCDA8A.60004@errno.com> Date: Mon, 03 Mar 2008 21:13:46 -0800 From: Sam Leffler User-Agent: Thunderbird 2.0.0.9 (X11/20071125) MIME-Version: 1.0 To: Marcel Moolenaar References: <47CCB187.8070808@FreeBSD.org> <723D012C-7907-4CFC-B134-C5E5A0B486D9@mac.com> In-Reply-To: <723D012C-7907-4CFC-B134-C5E5A0B486D9@mac.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-DCC--Metrics: ebb.errno.com; whitelist Cc: re@freebsd.org, "current@freebsd.org" , "George V. Neville-Neil" Subject: Re: IPSEC/crypto is broken in FreeBSD/powerpc 7.0-RELEASE! 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: Tue, 04 Mar 2008 05:13:47 -0000 Marcel Moolenaar wrote: > > On Mar 3, 2008, at 6:18 PM, Maxim Sobolev wrote: > >> Hi, >> >> It appears to be that "options IPSEC" along with "device crypto" >> breaks FreeBSD/powerpc kernel badly. When enabling these options, >> apparently kernel doesn't perform any initialization tasks (I don't >> see usual probe/init sequence output) but jumps straight into root fs >> mounting after initing crypto(4) and ipsec(4), which is not usable >> since no devices has been attached. Keyboard is not working either. > > The problem is with device crypto. It attaches to nexus(4) and > expects to be the only child. As you can see from the log, all > children of nexus suddenly become instantiations of cryptosoft(4) > rather then the usual drivers that attach. > > The swcr_probe() function should check that the device it gets > is really the one created for it. > Don't know about "expects to be the only child" but I did was jhb said was right. If you know otherwise please fix it. Sam