From owner-freebsd-drivers@FreeBSD.ORG  Sun Oct 14 21:25:05 2007
Return-Path: <owner-freebsd-drivers@FreeBSD.ORG>
Delivered-To: freebsd-drivers@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 5312E16A419
	for <freebsd-drivers@freebsd.org>; Sun, 14 Oct 2007 21:25:05 +0000 (UTC)
	(envelope-from marcin@studio4plus.com)
Received: from pe78.opole.sdi.tpnet.pl (pe78.opole.sdi.tpnet.pl
	[217.96.240.78])
	by mx1.freebsd.org (Postfix) with ESMTP id C913313C448
	for <freebsd-drivers@freebsd.org>; Sun, 14 Oct 2007 21:25:04 +0000 (UTC)
	(envelope-from marcin@studio4plus.com)
Received: from [89.79.52.87] (helo=[192.168.0.102])
	by pe78.opole.sdi.tpnet.pl with esmtpa (Exim 4.63 (FreeBSD))
	(envelope-from <marcin@studio4plus.com>) id 1IhAgI-0006jQ-Hn
	for freebsd-drivers@freebsd.org; Sun, 14 Oct 2007 23:07:38 +0200
Message-ID: <471284EF.2010009@studio4plus.com>
Date: Sun, 14 Oct 2007 23:06:55 +0200
From: Marcin Simonides <marcin@studio4plus.com>
User-Agent: Thunderbird 2.0.0.6 (X11/20070828)
MIME-Version: 1.0
To: freebsd-drivers@freebsd.org
Content-Type: text/plain; charset=ISO-8859-2; format=flowed
Content-Transfer-Encoding: 7bit
Subject: NDIS: intel 4965 panic
X-BeenThere: freebsd-drivers@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Writing device drivers for FreeBSD <freebsd-drivers.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-drivers>, 
	<mailto:freebsd-drivers-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-drivers>
List-Post: <mailto:freebsd-drivers@freebsd.org>
List-Help: <mailto:freebsd-drivers-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-drivers>,
	<mailto:freebsd-drivers-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 14 Oct 2007 21:25:05 -0000

I've tried using an XP ndis wrapper for my intel 4965 wifi adapter. 
After loading the driver the device is recognized and then kernel panics 
during driver attachement.

I'm using RELENG6 that has been updated a couple of months ago. I'll 
probably update it soon and then try again.

This is the most important (AFAIK) information (I had to put this 
information down on a piece of paper, so it's not complete, I'll try to 
figure out a way to dump ddb output to a file):

First an error from NDIS is printed:
NDIS API version: 5.1
NDIS ERROR: 4000167c (internal error)

then the kernel paniced:

Fatal trap 12: page fault while in kernel mode
fault code =  supervisor read, page not present

stopped at device_get_softc+0x6 movl 0x48(%eax),%eax

the backtrace shows:
device_get_softc
NdisMAllocateSharedMemory
_end
[...]
NETw4x32_sys_drv_data_start

NETw4x32_sys is the module name.


I've seen in the pr database that there are many similar problems (i.e. 
ndis wrapper not working with certain drivers). Should I send a PR 
related to this particular wifi card I have?

Is there any more information that I could provide to help the 
developers with enabling support for more wifi cards?
(I'll try to take a peek into the driver code but as I've never done any 
kernel programming this may yield no useful results).

Thanks for your time :)
-- 
Marcin Simonides