From owner-freebsd-questions@FreeBSD.ORG Mon Jan 11 21:15:33 2010 Return-Path: Delivered-To: questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A69D61065672 for ; Mon, 11 Jan 2010 21:15:33 +0000 (UTC) (envelope-from onemda@gmail.com) Received: from mail-ew0-f213.google.com (mail-ew0-f213.google.com [209.85.219.213]) by mx1.freebsd.org (Postfix) with ESMTP id 3C0418FC0A for ; Mon, 11 Jan 2010 21:15:32 +0000 (UTC) Received: by ewy5 with SMTP id 5so11065923ewy.14 for ; Mon, 11 Jan 2010 13:15:27 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=rY4fWgNvUhv2qkIxVl68n5JwocMO7yKDkS8Gc/tmtro=; b=Q2R3uLuE1bLEmMACvAwMbhascP0D1uR3tnkzOmCxxEMCqpKxHNCQPjN+6L5Gfz9ohH xNTt3BjVRpoke0EWRh3lf36LMjjq3wm98X4ru+0kzy5BxTUqczPxANSnvZ5Xr5aw3nMi hjURfwCNWSwGcgkaeNp11ymJX7+FVARbZLYK0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=YCN37f85O+wKZCJuhVjxHGUU2OYlcoPfBYv8JW3DS9+POkAES8YgpJ9R1TkRnGrwaq gVoV4u03MZOy3U7uLAtMfEWwqUtMMQeS06yuwgSDCHTiTiC4OrN66nXtwkcCR6Sqz9H4 Gd5iEFBvXIat8Ov7DlBrhSf6KbK8+witfJyCM= MIME-Version: 1.0 Received: by 10.213.110.132 with SMTP id n4mr8587450ebp.88.1263244526415; Mon, 11 Jan 2010 13:15:26 -0800 (PST) In-Reply-To: <54db43991001111115y7acaf4ect4a033e43a6ec159@mail.gmail.com> References: <54db43991001111115y7acaf4ect4a033e43a6ec159@mail.gmail.com> Date: Mon, 11 Jan 2010 22:15:26 +0100 Message-ID: <3a142e751001111315u269d8c6ehfa5d5a8660676073@mail.gmail.com> From: Paul B Mahol To: Bob Johnson Content-Type: text/plain; charset=ISO-8859-1 Cc: FreeBSD Questions Subject: Re: NDIS panics (Was: Can I rescan for new PCI devices? Or should hotplugging Expresscards work?) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Jan 2010 21:15:33 -0000 On 1/11/10, Bob Johnson wrote: > On 1/9/10, Paul B Mahol wrote: >> On 12/16/09, Bob Johnson wrote: >>> I'm using an ExpressCard for wireless networking because there seems >>> to be no driver for the internal card in my laptop (and NDIS panics >>> the system). The Expresscard shows up as a PCI device and works fine, >> >> How are you using NDIS and when system panic what is displayed? > > I tried to use ndisgen with the internal Dell 1397 card. I don't have > details available right now, although if you need them I can try it > again. When I did the kldload the system spit out error messages about > unknown symbols and then panic-ed. I did some searching of the > archives and found a message describing the same symptoms, and the > response posted was that it indicated that the Windows driver made API > calls that were not implemented in the NDIS wrapper. > > This was a 64-bit Windows driver and an amd64 FreeBSD system. Similar > results in both > FreeBSD 7.2 and 8.0. > > It appears that kern/132672 is describing the same or a very similar > issue. It also suggests that there is a more fundamental problem than > the unrecognized symbols. > > I can try to reproduce the problem tonight if you want me to. > > Thanks, If you have debug kernel, then make breakpoint for MSCALL2 (kldload ndis.ko before that): `break MSCALL2' Then load ndisgen module. Then single step it with `s' it should panic after few steps. At least this is issue I'm experiencing on amd64, it fails in DriverEntry(). -- Paul B Mahol