From owner-freebsd-questions@FreeBSD.ORG Sat Jan 16 13:09:22 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 4FF0C106566C for ; Sat, 16 Jan 2010 13:09:22 +0000 (UTC) (envelope-from onemda@gmail.com) Received: from mail-ew0-f226.google.com (mail-ew0-f226.google.com [209.85.219.226]) by mx1.freebsd.org (Postfix) with ESMTP id D86F88FC16 for ; Sat, 16 Jan 2010 13:09:21 +0000 (UTC) Received: by ewy26 with SMTP id 26so1785215ewy.3 for ; Sat, 16 Jan 2010 05:09:10 -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=9eL5r3iMnADQNmmhLBKfx6vYKYgGx8hV7fX7XLl9X1s=; b=n6RJ+tQQ2IdDft4qQGov4a9uedN+1CgjC8tYhDgm32wwHs+HFaOCh8fthWrDmwqZMF H6JixkOAc1vy+WnKb9iJ3YPegd7oMIrPaTnNDguNxAmL5/u53tmi2IdY9rWFP08Wlbq3 XK1QtWtGrNMaZdKbDSEdvJpn5GXbJZkmZ86uU= 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=byP92ecRoU9pUeLamQ1LKgr3BfYeWiMFOdAmeKtyqMlJdV/05Ao4/b68Hpqv4jJWJZ Fak1HXs1O03CSMaqNJoiB02V6NsUS6oNXnWM8QOwzJAWJt8Xl7I3EF1OAn1rTSVDONui afgPQ3VEMY1WuYqVbz9ANiGj3qCSgcOSIR+Ow= MIME-Version: 1.0 Received: by 10.213.41.73 with SMTP id n9mr1082173ebe.8.1263647350755; Sat, 16 Jan 2010 05:09:10 -0800 (PST) In-Reply-To: <3a142e751001111315u269d8c6ehfa5d5a8660676073@mail.gmail.com> References: <54db43991001111115y7acaf4ect4a033e43a6ec159@mail.gmail.com> <3a142e751001111315u269d8c6ehfa5d5a8660676073@mail.gmail.com> Date: Sat, 16 Jan 2010 13:09:10 +0000 Message-ID: <3a142e751001160509g658e8883v5a9ed92303140d9c@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: Sat, 16 Jan 2010 13:09:22 -0000 On 1/11/10, Paul B Mahol wrote: > 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' Should be `break w86_64_call2' > 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(). with the same virtual address as in kern/132672. -- Paul B Mahol