-current panic: kernel diagnostic assertion "kq->kq_count == 0" failed

[Thomas Klausner <tk%giga.or.at@localhost>]

Hi!

Tonight my -current/amd64 from Nov 28 paniced this night while I
wasn't watching, with:

panic: kernel diagnostic assertion "kq->kq_count == 0" failed: file "/usr/src/sys/kern/kern_event.c", line 1482

I have a crashdump, the backtrace is

(gdb) target kvm netbsd.core
0xffffffff8011a2d5 in cpu_reboot (howto=howto@entry=260, bootstr=bootstr@entry=0x0) at /usr/src/sys/arch/amd64/amd64/machdep.c:678
678                     dumpsys();
(gdb) bt
#0  0xffffffff8011a2d5 in cpu_reboot (howto=howto@entry=260, bootstr=bootstr@entry=0x0) at /usr/src/sys/arch/amd64/amd64/machdep.c:678
#1  0xffffffff80897a3c in vpanic (fmt=0xffffffff80ed32d8 "kernel %sassertion \"%s\" failed: file \"%s\", line %d ", ap=ap@entry=0xfffffe862576cc98)
    at /usr/src/sys/kern/subr_prf.c:342
#2  0xffffffff80bd83c5 in kern_assert (fmt=fmt@entry=0xffffffff80ed32d8 "kernel %sassertion \"%s\" failed: file \"%s\", line %d ")
    at /usr/src/sys/lib/libkern/kern_assert.c:51
#3  0xffffffff808454ef in kqueue_close (fp=<optimized out>) at /usr/src/sys/kern/kern_event.c:1482
#4  0xffffffff808405fb in closef (fp=0xfffffe872e114240) at /usr/src/sys/kern/kern_descrip.c:831
#5  0xffffffff8084321a in fd_free () at /usr/src/sys/kern/kern_descrip.c:1561
#6  0xffffffff8084a615 in exit1 (l=l@entry=0xfffffe821638b2c0, exitcode=2, signo=signo@entry=0) at /usr/src/sys/kern/kern_exit.c:286
#7  0xffffffff8084aefe in sys_exit (l=0xfffffe821638b2c0, uap=0xfffffe862576cf00, retval=<optimized out>) at /usr/src/sys/kern/kern_exit.c:186
#8  0xffffffff8013eeac in sy_call (rval=0xfffffe862576ceb0, uap=0xfffffe862576cf00, l=0xfffffe821638b2c0, sy=0xffffffff811d6c38 <sysent+24>)
    at /usr/src/sys/sys/syscallvar.h:65
#9  sy_invoke (code=1, rval=0xfffffe862576ceb0, uap=0xfffffe862576cf00, l=0xfffffe821638b2c0, sy=0xffffffff811d6c38 <sysent+24>)
    at /usr/src/sys/sys/syscallvar.h:94
#10 syscall (frame=0xfffffe862576cf00) at /usr/src/sys/arch/x86/x86/syscall.c:156
#11 0xffffffff80100761 in Xsyscall ()

What's the problem here?

Is it already fixed?
 Thomas