From owner-freebsd-questions@FreeBSD.ORG Sat Mar 24 01:59:58 2007 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id BCA6316A412 for ; Sat, 24 Mar 2007 01:59:58 +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 948E013C44B for ; Sat, 24 Mar 2007 01:59:58 +0000 (UTC) (envelope-from sam@errno.com) Received: from [10.0.0.178] ([10.0.0.178]) (authenticated bits=0) by ebb.errno.com (8.13.6/8.12.6) with ESMTP id l2O1xvig041688 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 23 Mar 2007 18:59:57 -0700 (PDT) (envelope-from sam@errno.com) Message-ID: <4604861D.3020805@errno.com> Date: Fri, 23 Mar 2007 18:59:57 -0700 From: Sam Leffler Organization: Errno Consulting User-Agent: Thunderbird 1.5.0.10 (Macintosh/20070221) MIME-Version: 1.0 To: Rajkumar S References: <64de5c8b0703160732o789f6993hcd926c6b3bc123f3@mail.gmail.com> <448xdtti2d.fsf@be-well.ilk.org> <64de5c8b0703192308ya58c0b0l8a49bda8d1a4b6e1@mail.gmail.com> <64de5c8b0703200326ie3e1fb3o400033ae64836e0c@mail.gmail.com> <44lkhpbari.fsf@be-well.ilk.org> <4602A7B5.6060107@errno.com> <64de5c8b0703220913g1c954092xbd5653404f9acabb@mail.gmail.com> In-Reply-To: <64de5c8b0703220913g1c954092xbd5653404f9acabb@mail.gmail.com> X-Enigmail-Version: 0.94.2.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-questions@freebsd.org Subject: Re: safe0 and kernel panic X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 24 Mar 2007 01:59:58 -0000 Rajkumar S wrote: > On 3/22/07, Sam Leffler wrote: >> I have no context. I see a device not attaching for some reason. Then >> /dev/crypto not being present (is cryptodev loaded in the kernel?). But >> a subject line about a panic. > > The device is not attaching because bus_dma_tag_create function fails > with the error ENOMEM. (in line 300, safe.c). I have changed > BUS_DMA_ALLOCNOW flag in bus_dma_tag_create to BUS_DMA_COHERENT and > the panic disappears. BUS_DMA_COHERENT was just taken randomly (as in > some other flag) with no idea about it's use or purpose. Removing BUS_DMA_ALLOCNOW appears to just just hide the problem by deferring the allocation. Since other drivers are getting similar failures it's unlikely this is a safe bug. > >> If you've submitted a PR please send me a pointer. Otherwise you might >> consider submitting one w/ details like what version of freebsd you're >> running. > > The PR Number is 110662. I have tried to put as much information as > possible, I am always ready to provide additional details or do some > testing/debugging. Thank you. I'll have to dig out one of my cards to test. Sam