From owner-freebsd-current@FreeBSD.ORG Wed Oct 6 15:04:41 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 C90F716A4CE for ; Wed, 6 Oct 2004 15:04:40 +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 7605D43D55 for ; Wed, 6 Oct 2004 15:04:39 +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 i96F4SUq081874 for ; Wed, 6 Oct 2004 19:04:29 +0400 (MSD) (envelope-from mcsi@mcsi.pp.ru) Message-ID: <41640976.7020004@mcsi.pp.ru> Date: Wed, 06 Oct 2004 19:04:22 +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: current@freebsd.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 Subject: 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:04:41 -0000 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. -- Maxim Maximov