One does not Simply Run Unicorn in DFBSD Posted on 2012-05-26 by nanaya Um, yeah. Running Unicorn on DFBSD (in VMware) caused kernel panic. I have no idea why.
I think it’s a panic that has been fixed recently (triggered by TCP_NOPUSH socket opt) and was fixed some time ago (on both master and the release branch): http://gitweb.dragonflybsd.org/dragonfly.git/commit/3533a1834a0ba3a7c441ede5120c3720d8a34c4c So depending on whether this box is running 3.1 or 3.0, you will need to either update the system to latest master or latest RELEASE-3.0 branch.
Really !? Can you get a dump and report that please?
Sure, just tell me the steps required to get the dump and where to report.
Type ‘t’ at the db> prompt and show us the output.
Here it is: http://i.imgur.com/of3fU.png
I think it’s a panic that has been fixed recently (triggered by TCP_NOPUSH socket opt) and was fixed some time ago (on both master and the release branch):
http://gitweb.dragonflybsd.org/dragonfly.git/commit/3533a1834a0ba3a7c441ede5120c3720d8a34c4c
So depending on whether this box is running 3.1 or 3.0, you will need to either update the system to latest master or latest RELEASE-3.0 branch.
Indeed, upgrading to latest 3.0 branch solved the problem. Thanks!