Date: Fri, 23 Mar 2007 18:59:57 -0700 From: Sam Leffler <sam@errno.com> To: Rajkumar S <rajkumars@gmail.com> Cc: freebsd-questions@freebsd.org Subject: Re: safe0 and kernel panic Message-ID: <4604861D.3020805@errno.com> In-Reply-To: <64de5c8b0703220913g1c954092xbd5653404f9acabb@mail.gmail.com> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
Rajkumar S wrote: > On 3/22/07, Sam Leffler <sam@errno.com> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4604861D.3020805>