From owner-freebsd-current@FreeBSD.ORG Fri Oct 8 08:06:10 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 2E14516A4CE; Fri, 8 Oct 2004 08:06:10 +0000 (GMT) Received: from zombie.ezone.ru (zombie.ezone.ru [195.128.162.78]) by mx1.FreeBSD.org (Postfix) with ESMTP id C7DAC43D1F; Fri, 8 Oct 2004 08:06:08 +0000 (GMT) (envelope-from mcsi@mcsi.pp.ru) Received: from [172.16.4.26] (ultra.domain [172.16.4.26] (may be forged)) by zombie.ezone.ru (8.12.11/8.12.11) with ESMTP id i98862Qn042657; Fri, 8 Oct 2004 12:06:02 +0400 (MSD) (envelope-from mcsi@mcsi.pp.ru) Message-ID: <41664A59.7090409@mcsi.pp.ru> Date: Fri, 08 Oct 2004 12:05:45 +0400 From: Maxim Maximov User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.1) Gecko/20040707 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Brian Fundakowski Feldman References: <41640976.7020004@mcsi.pp.ru> <20041006155125.GK47017@green.homeunix.org> <41641614.3050102@mcsi.pp.ru> <20041008061859.GB980@green.homeunix.org> In-Reply-To: <20041008061859.GB980@green.homeunix.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.64 X-Spam-Checker-Version: SpamAssassin 2.64 (2004-01-11) on zombie.ezone.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: Fri, 08 Oct 2004 08:06:10 -0000 Brian Fundakowski Feldman wrote: > 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: > > Thanks, I'll try to reproduce the panic with the recent kernel first. Then if new kernel will still panicing, I'll apply your patch. -- Maxim Maximov