From owner-freebsd-current@FreeBSD.ORG Fri Oct 8 06:19:01 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from green.homeunix.org (freefall.freebsd.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 33BDE16A4CE; Fri, 8 Oct 2004 06:19:01 +0000 (GMT) Received: from green.homeunix.org (green@localhost [127.0.0.1]) by green.homeunix.org (8.13.1/8.13.1) with ESMTP id i986J0YB001924; Fri, 8 Oct 2004 02:19:00 -0400 (EDT) (envelope-from green@green.homeunix.org) Received: (from green@localhost) by green.homeunix.org (8.13.1/8.13.1/Submit) id i986J0JE001923; Fri, 8 Oct 2004 02:19:00 -0400 (EDT) (envelope-from green) Date: Fri, 8 Oct 2004 02:18:59 -0400 From: Brian Fundakowski Feldman To: Maxim Maximov Message-ID: <20041008061859.GB980@green.homeunix.org> References: <41640976.7020004@mcsi.pp.ru> <20041006155125.GK47017@green.homeunix.org> <41641614.3050102@mcsi.pp.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <41641614.3050102@mcsi.pp.ru> User-Agent: Mutt/1.5.6i 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: Fri, 08 Oct 2004 06:19:01 -0000 On Wed, Oct 06, 2004 at 07:58:12PM +0400, Maxim Maximov wrote: > 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). > > It could conceivable be related to something this would fix: -- Brian Fundakowski Feldman \'[ FreeBSD ]''''''''''\ <> green@FreeBSD.org \ The Power to Serve! \ Opinions expressed are my own. \,,,,,,,,,,,,,,,,,,,,,,\