From owner-freebsd-current@FreeBSD.ORG Sat Jan 14 04:35:53 2006 Return-Path: X-Original-To: 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 909B216A41F for ; Sat, 14 Jan 2006 04:35:53 +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 2CFDA43D45 for ; Sat, 14 Jan 2006 04:35:53 +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 k0E4XAhI049148; Fri, 13 Jan 2006 21:33:10 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Fri, 13 Jan 2006 21:33:27 -0700 (MST) Message-Id: <20060113.213327.22017826.imp@bsdimp.com> To: julian@elischer.org From: "M. Warner Losh" In-Reply-To: <43C718EF.9050301@elischer.org> References: <43C712A7.1050805@gddsn.org.cn> <43C718EF.9050301@elischer.org> 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]); Fri, 13 Jan 2006 21:33:15 -0700 (MST) Cc: current@freebsd.org Subject: Re: if_em panic 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: Sat, 14 Jan 2006 04:35:53 -0000 In message: <43C718EF.9050301@elischer.org> Julian Elischer writes: : Huang wen hui wrote: : : >hi, : >when I load if_em on TP42P got this panic: : > : > : : looks like the first interrupt occurs before the driver has finished : setting itself up.. : (just a first impression). : Scott'll probably nail it. : : I'm guessing it works fine if compiled in.. Fast interrupts are not masked during device configuration, but slow interrupts are. This is why people are seeing this now. Even if the em device itself didn't interrupt, it is possible (likely) that other devices that share an interrupt with it have... Warner