kqueue panic at boot time?

From: George V. Neville-Neil <gnn_at_neville-neil.com> Date: Sat, 21 Aug 2004 00:53:32 -0700 · This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:38:07 UTC

Howdy,

	Is anyone else seeing this?

kdb_enter(c07ef1cf) at kdb_enter+0x2b
panic(c07ee670,c07ff512,c07ec570,537,c1472b28) at panic+0x131
_mtx_assert(c08af7e0,1,c07ec570,537,c1472b28) at _mtx_assert+0x5c
kqueue_close(c1472b27,c14496e0) at kqueue_close+0x28
fdrop_locked(c1472b28,c14496e0,c12a43b8,0,c07ec160) at fdrop_locked+0x84
fdrop(c1472b28,c14496e0,694,c08bb1e0,0) at fdrop+0x24
closef(c1472b28,c14496e0,0,c07ec160) at closef+0x20b
close(c14496e0,cc15ad14,1,17,296) at close+0xba
syscall(2f,2f,2f8111000,bfbfbd50) at syscall+0x217
Xint0x80_syscall() at Xint0x80_syscall+0x1f
--- syscall (6, FreeBSD ELF2, close), eip = 0x2828256f, esp = 0xbfbfbccc, ebp= 0xbfbfc388 ---

There may be typos, I had to type that all in.

This all claims to happen because of:

	GIANT_REQUIRED;

in kqueue_close() at line 1336.  

Thoughts?

Thanks,
George