Date: Tue, 26 May 2009 16:49:05 +0200 From: "Paul B. Mahol" <onemda@gmail.com> To: Adam K Kirchhoff <adamk@voicenet.com> Cc: freebsd-net@freebsd.org Subject: Re: kernel crashes with ndis & -CURRENT Message-ID: <3a142e750905260749r5e78536cwe14fb17c3939e72@mail.gmail.com> In-Reply-To: <20090526102901.6bf50586@voicenet.com> References: <20090526102901.6bf50586@voicenet.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 5/26/09, Adam K Kirchhoff <adamk@voicenet.com> wrote: > > In an attempt to get the native drivers working on a particular > wireless network at work I updated to -CURRENT to see if I'd have any > more luck ( http://www.freebsd.org/cgi/query-pr.cgi?pr=131153&cat= ). > > Unfortunately, that didn't work out so I was decided to revert to the > ndis drivers. I created a new module using the same sys and inf file > that mostly worked on -STABLE (with frequent UP and DOWN messages, but > better than nothing). Unfortunately, now I get a complete kernel panic. > > Please let me know if this is a better question for freebsd-current. > Here's the backtrace: Please update your kernel after r192765, this issue have been already fixed on CURRENT. -- Paul
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3a142e750905260749r5e78536cwe14fb17c3939e72>