DragonFlyBSD

This is the list of panics we've been accumulating. It's particularly hard for i386 and UFS.
This is a good list of items to be fixed before next release.

#2296: panic: assertion "m->wire_count > 0" failed in pmap_unwire_pte at /usr/src/sys/platform/pc32/i386/pmap.c:1091
core available (~marino/crash, ~thomas/crash
(carried over from 3.0.1, 3.0.2, 3.0.3 showstopper lists)
#2364: panic: lockmgr: locking against myself
core available (~marino/crash)
#2374: Panic where softdep_update_inodeblock() called bwrite() with a NULL buffer
core available (~marino/crash) uploaded today
#2374: panic: flush_pagedep_deps: MKDIR_BODY
core available (~marino/crash)
#2370: panic: ffs_valloc: dup alloc
core available (~marino/crash)
#2350 panic: assertion "m->flags & PG_BUSY" failed in vm_page_protect at /usr/src/sys/vm/vm_page.h:532
core available (~pavalos/crash)

Leftover from 3.0.3 showstopper:
#2353 panic: assertion "gd->gd_spinlocks_wr == 0" failed in bsd4_schedulerclock
core available (~jaydg/crash)
#2388 panic: lockmgr: LK_RELEASE: no lock held
No core.
#2399 Panic on lwkt_reltoken from vm_mmap
core available (limited use)

Leftover from 3.0.1 showstopper:
#2284 panic: general protection fault (3.0 showstopper)
core available on ylem/var/crash, request to put on leaf didn't happen (?)

Other panics:
#2352 panic: Bad link elm 0xffffffe0a3775670 next->prev != elm
core available (~jaydg/crash)
#2369 panic: Bad link elm 0xffffffe07edf6068 next->prev != elm
core available (~jaydg/crash)
#2355 panic: rtrequest1_msghandler: rtrequest table error was cpu4, err 17
core available (~jaydg/crash)
#2083 panic: zone: entry not free
core might be available
#2358 panic: hammer: insufficient undo FIFO space!
NO CORE
#2345 panic: assertion "len <= nmp->nm_size" failed in nfs_writerpc_bio at ....
NO CORE
#2300 EHCI module unload panic
Supposed core availble on request