From owner-freebsd-current@FreeBSD.ORG Wed Dec 28 05:38:18 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org 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 02ECA16A41F for ; Wed, 28 Dec 2005 05:38:18 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (vc4-2-0-87.dsl.netrack.net [199.45.160.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9218F43D5F for ; Wed, 28 Dec 2005 05:38:17 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (localhost.village.org [127.0.0.1] (may be forged)) by harmony.bsdimp.com (8.13.3/8.13.3) with ESMTP id jBS5brJA024278; Tue, 27 Dec 2005 22:37:54 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Tue, 27 Dec 2005 22:38:03 -0700 (MST) Message-Id: <20051227.223803.77258153.imp@bsdimp.com> To: mph@lima.dyndns.dk From: "M. Warner Losh" In-Reply-To: <20051228002430.GA27330@echobase.hoth.dk> References: <20051224235153.GA46187@echobase.hoth.dk> <20051227001229.GF1496@FreeBSD.org> <20051228002430.GA27330@echobase.hoth.dk> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0 (harmony.bsdimp.com [127.0.0.1]); Tue, 27 Dec 2005 22:37:54 -0700 (MST) Cc: freebsd-current@freebsd.org Subject: Re: if_dc.c causes page fault while in kernel mode; coredump; reproducible X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 28 Dec 2005 05:38:18 -0000 In message: <20051228002430.GA27330@echobase.hoth.dk> "Martin P. Hansen" writes: : On Tue, 27 Dec 2005, Gleb Smirnoff wrote: : > please try out the attached patch. : : It works. Thank you very much. : : Just of curiosity, why is the NIC still active when the system shuts : down? I mean is the ``IFF_DRV_RUNNING'' _the_ method to stop an : interface? Just because an interface has been stopped, doesn't mean that its ISR won't be called because another (shared) interrupt happens. : I though in a simple setup one would disable the devices when : shutting down by disabling interrupts or raising the interrupt : priority level. Without shared interrupts, one can usually get away with this... Warner