From owner-freebsd-security@FreeBSD.ORG Sun Apr 30 10:53:42 2006 Return-Path: X-Original-To: freebsd-security@freebsd.org Delivered-To: freebsd-security@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 98F4116A400 for ; Sun, 30 Apr 2006 10:53:42 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3436C43D46 for ; Sun, 30 Apr 2006 10:53:42 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id 0533246C66; Sun, 30 Apr 2006 06:53:41 -0400 (EDT) Date: Sun, 30 Apr 2006 11:53:40 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: "Andrej (Andy) Brodnik" In-Reply-To: <20060430095658.GA18736@Svarun.Gotska.IJP.SI> Message-ID: <20060430115137.N11416@fledge.watson.org> References: <20060428122811.P40418@fledge.watson.org> <44527E6D.9070001@cloudview.com> <20060429095912.C63668@fledge.watson.org> <20060430095658.GA18736@Svarun.Gotska.IJP.SI> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-security@freebsd.org, John Pettitt Subject: Re: Looking for tor users experiencing crashes X-BeenThere: freebsd-security@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Security issues \[members-only posting\]" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 30 Apr 2006 10:53:42 -0000 On Sun, 30 Apr 2006, Andrej (Andy) Brodnik wrote: > However, on my 6.0 I wanted to install recently the WLAN card using ndis. > The card I wanted to use was dlink (AIRPLUS driver). The generation of the > driver using ndisgen went through smoothly, but when I wanted to load the > kernel module, the machine simply hang. Any suggestions/proposals would > really nice to get. If you haven't already, and perhaps even if you have, send a report of this to stable@FreeBSD.org. Normally, the debugging instructions at that point will be to build a kernel with the debugger and various debugging features, and see if a more useful failure made can be found (i.e., drop to the debugger / break to the debugger rather than hang), which will help track it down to something more specific. Ideally a bug in FreeBSD and not in the driver, from your perspective, because getting FreeBSD fixed is probably easier :-). Robert N M Watson