From owner-freebsd-current@FreeBSD.ORG Wed Oct 6 15:51:28 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 8AD1016A4CE; Wed, 6 Oct 2004 15:51:28 +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 i96FpRrU063716; Wed, 6 Oct 2004 11:51:27 -0400 (EDT) (envelope-from green@green.homeunix.org) Received: (from green@localhost) by green.homeunix.org (8.13.1/8.13.1/Submit) id i96FpPsM063715; Wed, 6 Oct 2004 11:51:25 -0400 (EDT) (envelope-from green) Date: Wed, 6 Oct 2004 11:51:25 -0400 From: Brian Fundakowski Feldman To: Maxim Maximov Message-ID: <20041006155125.GK47017@green.homeunix.org> References: <41640976.7020004@mcsi.pp.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <41640976.7020004@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: Wed, 06 Oct 2004 15:51:29 -0000 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? 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). -- Brian Fundakowski Feldman \'[ FreeBSD ]''''''''''\ <> green@FreeBSD.org \ The Power to Serve! \ Opinions expressed are my own. \,,,,,,,,,,,,,,,,,,,,,,\