[DragonFlyBSD - Bug #2296] panic: assertion "m->wire_count > 0" failed

[Thomas Nikolajsen via Redmine <bugtracker-admin@xxxxxxxxxxxxxxxxxxxxx>]

Issue #2296 has been updated by Thomas Nikolajsen.


Got panic while testing w/o NFS use.
This time 1st round (of make release) succeded;
got panic early in 2nd round (during buildworld 4a).

A wild guess: I usually run shell script doing some sysctl's, to see system load, like cpu freq (running powerd); didn't do that on 1st round, maybe sysctl can be part of trigger (saw other sysctl related bug on bugs@).

Anyway: doing test on x86_64 now to see if it's clean; didn't do much testing for this bug there yet.

----------------------------------------
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