Date: Fri, 13 Jan 2006 21:33:27 -0700 (MST) From: "M. Warner Losh" <imp@bsdimp.com> To: julian@elischer.org Cc: current@freebsd.org Subject: Re: if_em panic Message-ID: <20060113.213327.22017826.imp@bsdimp.com> In-Reply-To: <43C718EF.9050301@elischer.org> References: <43C712A7.1050805@gddsn.org.cn> <43C718EF.9050301@elischer.org>
next in thread | previous in thread | raw e-mail | index | archive | help
In message: <43C718EF.9050301@elischer.org>
Julian Elischer <julian@elischer.org> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060113.213327.22017826.imp>