From owner-freebsd-mobile@FreeBSD.ORG Sat Oct 30 02:25:06 2004 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A2AF816A4CE; Sat, 30 Oct 2004 02:25:06 +0000 (GMT) Received: from tinker.exit.com (tinker.exit.com [206.223.0.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id B220A43D49; Sat, 30 Oct 2004 02:25:05 +0000 (GMT) (envelope-from frank@exit.com) Received: from realtime.exit.com (realtime [206.223.0.5]) by tinker.exit.com (8.13.1/8.12.9) with ESMTP id i9U2Sec0081100; Fri, 29 Oct 2004 19:28:41 -0700 (PDT) (envelope-from frank@exit.com) Received: from realtime.exit.com (localhost [127.0.0.1]) by realtime.exit.com (8.13.1/8.12.9) with ESMTP id i9U2OxVF004732; Fri, 29 Oct 2004 19:24:59 -0700 (PDT) (envelope-from frank@realtime.exit.com) Received: (from frank@localhost) by realtime.exit.com (8.13.1/8.13.1/Submit) id i9U2Ox24004731; Fri, 29 Oct 2004 19:24:59 -0700 (PDT) (envelope-from frank) From: Frank Mayhar Message-Id: <200410300224.i9U2Ox24004731@realtime.exit.com> In-Reply-To: <200410280416.i9S4GjKZ044574@realtime.exit.com> To: mobile@freebsd.org, current@freebsd.org Date: Fri, 29 Oct 2004 19:24:59 -0700 (PDT) X-Copyright0: Copyright 2004 Frank Mayhar. All Rights Reserved. X-Copyright1: Permission granted for electronic reproduction as Usenet News or email only. X-Mailer: ELM [version 2.4ME+ PL119 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Subject: Re: NDISulator crashness. X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: frank@exit.com List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 30 Oct 2004 02:25:06 -0000 To follow this up, I did manage to reproduce the real problem, a kernel panic down in the underlying Windows driver. See PR i386/73298, "Fatal trap 12: page fault while in kernel mode in NDIS" for details. I also uncovered another lock order reversal, this one in ndis_start(), which I've added to PR i386/73224. Unfortunately I can't take this problem any further since, one, I don't have the time and, two, I just don't know enough about NDIS in general or the NDISulator in particular. As for myself, I'm going to an Atheros-based card (which I'm using now). -- Frank Mayhar frank@exit.com http://www.exit.com/ Exit Consulting http://www.gpsclock.com/ http://www.exit.com/blog/frank/