From owner-freebsd-current@FreeBSD.ORG Wed Oct 6 15:58:25 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6280D16A4CE; Wed, 6 Oct 2004 15:58:25 +0000 (GMT) Received: from portpc-design.spb.ru (ns2.portpc-design.spb.ru [195.161.118.232]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8A70643D48; Wed, 6 Oct 2004 15:58:24 +0000 (GMT) (envelope-from mcsi@mcsi.pp.ru) Received: from [83.237.13.114] (ppp83-237-13-114.pppoe.mtu-net.ru [83.237.13.114]) (authenticated bits=0) by portpc-design.spb.ru (8.13.1/8.13.1) with ESMTP id i96FwHgB085064; Wed, 6 Oct 2004 19:58:17 +0400 (MSD) (envelope-from mcsi@mcsi.pp.ru) Message-ID: <41641614.3050102@mcsi.pp.ru> Date: Wed, 06 Oct 2004 19:58:12 +0400 From: Maxim Maximov User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.2) Gecko/20040929 X-Accept-Language: ru, en-us, en MIME-Version: 1.0 To: Brian Fundakowski Feldman References: <41640976.7020004@mcsi.pp.ru> <20041006155125.GK47017@green.homeunix.org> In-Reply-To: <20041006155125.GK47017@green.homeunix.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, hits=-4.9 required=5.0 tests=BAYES_00 autolearn=ham version=2.64 X-Spam-Checker-Version: SpamAssassin 2.64 (2004-01-11) on portpc-design.spb.ru cc: current@freebsd.org Subject: Re: NDIS/UMA related panic X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Oct 2004 15:58:25 -0000 Brian Fundakowski Feldman wrote: > On Wed, Oct 06, 2004 at 07:04:22PM +0400, Maxim Maximov wrote: > >>Hello. >> >> System running kernel >> >>FreeBSD ultra.domain 6.0-CURRENT FreeBSD 6.0-CURRENT #11: Fri Oct 1 >>19:17:59 MSD 2004 mcsi@ultra.domain:/usr/obj/usr/src/sys/ULTRA i386 >> >> is sometimes experiencing following panic on boot after ppp starts >> and sends first packet to ndis0 (hand-transcribed): >> >>kernel trap 12: page fault >>db> trace >>ntoskrnl_queue_dpc(0xdeadc0de, 0, 0, 0, 0xd6b96330) +0x9 >>ntoskrnl_timercall(0xc1fb51f0) +0x7a >>softclock(0) +0x17a >>ithread_loop >>fork_exit >>fork_trampoline >> >> I'll update kernel and will re-post if the problem continues. I'm >>posting this now because I think someone might be interested in seeing >>0xdeadc0de in stack trace. > > > That very much looks like an NDIS driver bug. Did the vendor only provide > one version to try? Yes. This is ASUS L5G notebook. Driver page with the one and only Wireless driver is here: http://www.asus.com/support/download/item.aspx?ModelName=L5G I'm running NDIS for about 1.5 months. And this panic first happens only yesterday, so I thought this is not the driver bug. BTW, here it is: ndis0: mem 0xfeaf8000-0xfeaf9fff irq 17 at device 2.0 on pci2 ndis0: NDIS API version: 5.0 ndis0: Ethernet address: 00:0e:a6:c2:00:e4 ndis0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps ndis0: 11g rates: 6Mbps 9Mbps 12Mbps 18Mbps 36Mbps 48Mbps 54Mbps Full dmesg is at http://mcsi.pp.ru/dmesg.boot > I wouldn't be surprised if NT has kernel code that > specifically tries to recover from timers going off that were stored in > memory that got freed (before they went off). > -- Maxim Maximov