From owner-freebsd-questions@FreeBSD.ORG Mon Feb 8 11:18:52 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 2E8531065670; Mon, 8 Feb 2010 11:18:52 +0000 (UTC) (envelope-from onemda@gmail.com) Received: from mail-ew0-f211.google.com (mail-ew0-f211.google.com [209.85.219.211]) by mx1.freebsd.org (Postfix) with ESMTP id 959168FC14; Mon, 8 Feb 2010 11:18:51 +0000 (UTC) Received: by ewy3 with SMTP id 3so3343176ewy.13 for ; Mon, 08 Feb 2010 03:18:50 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:cc:content-type; bh=P5/IJcO1phr223/3IFRng2/vV7F/P4cft8Wsxadfkxs=; b=JXuXO8A6XyUf3qFaFEXBYtg3sUS5ZYrEaDE0mI8c6Gkfv1RLwW3ltqWVGO3oozneJn AXU99D8Z6u8VmuQyIoSG1+5xMj+EOC68atVjsO+7y5lL0fcofGYhbly5wOuGYiltxuuO XereLqYPxeorgbiVwZiLNjvz0zIHYIorygATY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:cc:content-type; b=EtBFU8h33XsckVxUl2qSfHyszz1e3KE6KdH6TuHOvpS9p06R0lHsX99q4a8Il8Ui3B weutldrExF0zHllUWUaa3zdiuFEVdN7ia3covnIlP4JuEDarK4tX8td4+Bkp32AB+jpS TmAinbErc3wPFmNKpM6+DqUvU1cEXYHbYx2DA= MIME-Version: 1.0 Received: by 10.213.72.11 with SMTP id k11mr2572542ebj.38.1265627930562; Mon, 08 Feb 2010 03:18:50 -0800 (PST) Date: Mon, 8 Feb 2010 11:18:50 +0000 Message-ID: <3a142e751002080318g2e77999v73dd4d671c5a578@mail.gmail.com> From: Paul B Mahol To: fbsdlists@gmail.com, lothlorien@pvu.msk.ru Content-Type: text/plain; charset=ISO-8859-1 Cc: questions@freebsd.org, net@freebsd.org Subject: NDISulator bug on amd64 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, 08 Feb 2010 11:18:52 -0000 On 1/16/10, Paul B Mahol wrote: > 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. I fixed bug that caused panic on amd64 in DriverEntry(). Code is available from here: www.gitorious.org/NDISulator