Issue #2296 has been updated by Thomas Nikolajsen.
Note: on v3.0.1 i386 system building dfly v3.0.1 (which I understand we are going to release) once (to install on UP stable system here) caused this panic during buildworld. This was on 8 core system using my usual params, -j10, did new build using -j4, which succeded. This is somewhat ironic, but just what should be expected from earlier observations on this bug. If we release v3.0.1 we might consider not supporting i386 w/ more than 4 cores, until this bug is resolved. ---------------------------------------- Bug #2296: panic: assertion "m->wire_count > 0" failed http://bugs.dragonflybsd.org/issues/2296 Author: Thomas Nikolajsen Status: New Priority: High Assignee: Category: Target version: With recent (29/1-12) master and rel3_0 I get this panic during parallel make release and buildworld, e.g.: 'make MAKE_JOBS=10 release' (i.e. make -j10) i386 STANDARD (custom kernel, includes INCLUDE_CONFIG_FILE) on 8 core host (opteron). Got this panic twice; succeeds w/o MAKE_JOBS Core dump at leaf: ~thomas:crash/octopus.i386.3 -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account
